MSC Lirica

MSC Lirica
5 (100%) 1 vote

MSC Lirica cruise ship accidents, incidents and law news reports relate to a passenger vessel with IMO number 9246102, owned by the MSC Crociere line company (subsidiary of the MSC shipping company). Among the unfortunate events at sea are collisions, crew and passenger incidents (deaths, injuries, crimes), machinery malfunctions.

Here you can also track MSC Lirica position at sea.using the AIS live ships tracker of VesselFinder. The 58,850-ton 2070-passenger MSC cruise ship Lirica was built in 2003 by the Chantiers de l’Atlantique shipbuilding company in France.

MSC Lirica accidents & incidents

MSC Lirica accidents and incidents - Cruise MinusAt the MSC Lirica CruiseMinus page you will find a complete list of MSC Cruises Lirica ship’s major accidents and cruise incidents. Reports are made by our own staff using official data from major online news media sources, Wikipedia and Coast Guard reports.

Here we also post updates on MSC Lirica cruise law news. They are related to recent crimes being investigated. Among those could be arrests, filed lawsuits, charges and fines, grievances, settled /withdrawn legal actions, lost cases, etc.

You can add more details or submit your own MSC Lirica ship incidents (negative cruise experience reports) via the Cruise Minus “contact us” form.

This is link to the ship’s official site

Pier collision accident

  • April 29, 2012, upon maneuvering for docking in call port Civitavecchia (port to Rome Italy), strong winds pushed the ship against the pier. The vessel sustained hull damages in the area between its bow and bulwarks (portside extension above deck level). The collision was reported to the Italian authorities and the ship was inspected before the departure. The last Mediterranean cruise (scheduled for Nov 10) was cancelled, allowing the vessel entered drydock for repairs in November 12, 2012. Immediately after the dry-dock (Nov 17) followed the Transatlantic repositioning cruise to Florida ending in homeport Port Everglades (Fort Lauderdale) on Dec 4.

Technical incidents

  • March 25, 2002, a near collision situation was reported, involving two MSC vessels – the Lirica and the container ship MSC Lauren (12400 TEU capacity). The incident occurred in the Mediterranean waters, south of Sicily, where both ships pass at less than 33 ft / 100 m from each other. The MSC containership Lauren approached the Lirica aft starboard. Apparently, the cargo vessel saluted the cruise vessel this way, also blowing its whistles. However, there’s a potential risk for a ship collision accident in case of power loss, engine or propulsion-navigation system failure on one of the vessels. After doing a similar “salute”, in January 2012 the Costa Crociere ship Costa Concordia hit a rock and subsequently sank near the Isola del Giglio, Italy.
  • August-November 2015, during its Palermo Sicily dry-dock stay, the MSC Cruises Lirica ship was stretched. An ~80 ft / 25 m long prefabricated middle-section was added. The refit resulted in an increased passenger capacity (new cabins), new shops, a Water Park with slides and waterfalls. Following the overhaul, the Lirica ship re-entered service on November 4, 2015, leaving from Genoa Italy on a 19-days Transatlantic repositioning cruise to South America (ending in Rio de Janeiro Brazil on Nov 23). The list of other stretched (elongated) cruise ships includes the fleetmates MSC ArmoniaMSC Opera, MSC Sinfonia, the Phoenix Reisen’s Albatros, the Royal Caribbean’s Enchantment of The Seas and the Fred Olsen ships Black Watch, Balmoral, Boudicca, Braemar.

Crew & Passenger Death accidents

  • Fortunately, no such tragic accidents were officially reported so far.

Crew & Passenger incidents (injuries, crimes)

  • Fortunately, no such major incidents were officially reported so far.

MSC Lirica current position

On the above map you can track the MSC Lirica cruise ship’s position now. It shows the vessel’s current location at sea (or in port) by live tracking of its IMO number 9246102. If you lose the ship on the map, please reload this page.