Emerald Princess cruise ship accidents, incidents and law news reports relate to a passenger vessel with IMO number 9333151, owned by the Princess Cruises line (a Carnival Corporation brand). Among the unfortunate events at sea are fire, Norovirus illness outbreaks, crew and passenger incidents (deaths, injuries, crimes), collision, shore excursion incidents, machinery malfunctions.
Here you can also track MS Emerald Princess position at sea.using the AIS live ships tracker of VesselFinder. The 113,560-ton 3080-passenger Princess cruise ship Emerald was built in 2007 by the Fincantieri shipbuilding company in Italy.
Emerald Princess accidents & incidents
At the Emerald Princess CruiseMinus page you will find a complete list of this Princess cruise 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 USCG (Coast Guard) reports.
Here we also post updates on Emerald Princess 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 Emerald Princess ship incidents (negative cruise experience reports) via the Cruise Minus “contact us” form.
This is link to the ship’s official site Princess.com.
- October 3, 2014, the shiponer Princess Cruises officially announced, that the vessel experienced 2 technical incidents (engine failures) which caused 2 fires in the engine room. Both fires were quickly extinguished, with no injuries reported. The line said both incidents didn’t pose any safety threat. All systems remain operational. The emergency response procedures were operated properly. The ship was safe. On September 16, the Captain called crew to muster stations due to an engine room fire emergency. Passengers were informed via the PA system about a “technical issue”. This incident, occurred ~7 hours after the ship left homeport Southampton England. On September 20, the second fire incident occurred. The ship was on a 14-day Mediterranean cruise round-trip from UK.
- September 17, 2016, at ~11:30 pm, a fire broke out while the vessel was en-route from Southampton to Las Palmas de Gran Canaria (Canary Islands). Via the PA system, the Captain ordered all crew to the muster stations. A passenger reported (unofficially) about a fuel leak causing an engine room fire. Fire doors were automatically closed, the diesel generators 1 and 4 were shut down. Smoke was detected aft on the lower decks, as well as on deck 16 near the funnels (where is also the Movies under the Stars / outdoor movie screen). The engine room’s fire detection and suppression system quickly extinguished the fire. As source for the accident was cited “combusted ventilation supply fan belt” (located on Deck 16). No injurious or any serious damages were officially reported by the Princess Cruises company.
- July 25, 2010, while en-route from homeport Fort Lauderdale (Port Everglades Florida) to Bahamas, at 6:30 pm the vessel experienced a power loss incident caused by a computer glitch. It took the crew ~4 hours to fix the problem. During the incident, all elevators and the air conditioning system were inoperational and lighting was limited. All onboard toilets were preferably not to be used since there was no water supply for flushing and washing. An itinerary change had to be made, dropping the call port Princess Cays (private island) in Bahamas.
- May 17, 2011, operating in Baltic Sea, the vessel was docked in call port St Petersburg, Russia, when a fuel barge hit it. While in the collision incident the ship’s hull didn’t sustain damages, on the superstructure two of the starboard life boats (numbers 6 and 7) were seriously damaged and rendered inoperational. After examination, Russian port authorities cleared the cruise ship as she had inflatable life rafts with enough capacity.
- October 11, 2016, the ship did a “Piracy Attack Drill” intended to prepare its passengers to act accordingly in case of eventual attack by pirates in the waters near Yemen. The World Cruise 2016 itinerary from UK to Australia (48-day Southampton to Sydney) started on Sept 28 and ended on Nov 15. During the cruise, Emerald Princess passed through Gulf of Aden (off the Somalian coast) at night.
- October 30-31, 2016, while sailing in Thailand, the vessel suffered a power failure en-route from Koh Samui Island to Laem Chabang (Bangkok). Vesselfinder’s AIS tracking showed slowing down the cruising speed from 19-21 kn (22-24 mph / 35-39 kph) to 2 kn (2 mph / 4 kph) on several times during the night.
- February 9, 2017, the same day when a crew was killed in Port Chalmers NZ (see in “death accidents” below), the ship stroke a rock in Milford Sound NZ. Fortunately, the hull sustained only a minor damage.
Crew & Passenger Death accidents
- December 14, 2010, a 59-year-old male passenger died in an accident ashore when the ship was docked in call port Kralendijk (Bonaire). The man (Timothy Scheibel) fell and suffered a severe neck injury. He was immediately flown to Miami by an air ambulance, but died in the hospital during surgery. He was traveling with his wife (both from Santa Clarita CA) to celebrate his 60th birthday.
- February 9, 2017, at ~ 5 pm. a male crew died onboard while the ship was berthed at Port Chalmers (Dunedin, New Zealand). The accident happened on Promenade Deck 7, where a 45 kg / 100 pound gas cylinder (full with compressed nitrogen) exploded, became a projectile and hit the man, killing him instantly. The cylinder was later found on the docking wharf, with a blown out base. The gas cylinder was used to power a gantry crane that lowers and lifts the ship’s lifeboats. The cruise ship sustained no damage. Princess Cruises’ official announcement said it happened during technical works on the tender boats’ hydraulic launching system. The next day, a Maritime New Zealand team boarded the ship to investigate the accident. As the cruise ship left Dunedin a day later than scheduled, the itinerary was altered, with the next port of call (Milford Sound) being dropped. An expert analysis concluded that the failure was due to “overload caused by corrosion thinning”.
Crew & Passenger incidents (injuries, crimes)
- February 19, 2017, a 68-year-old female passenger was medevaced from the cruise ship in Dunedin Harbour NZ. The woman was offloaded and transported to Port Chalmers via one of the ship’s tender boats.
Norovirus cruise illness outbreaks
- December 2007, CDC reported on the voyage Dec 16 to 26, a Norovirus outbreak (gastrointestinal illness) infected 156 passengers (out of 3209, or 4,9%) and 22 crew (out of 1211, or 1,8%). All sick suffered from Norovirus symptoms (vomiting, diarrhea). The ship was on 10-day round-trip Panama Canal cruise from homeport Port Everglades (Fort Lauderdale Florida).
- June 28, 2009, a Russian news media reported when the ship docked in call port St Petersburg, local authorities were notified about 14 crew suffering from swine flu (H1N1 pig influenza) symptoms – fever, chills, headache, coughing. The sick were quarantined on the ship and not allowed to disembark the vessel.
- May 6, 2011, according to an online news media, on the 16-days Transatlantic repositioning cruise from Florida to Europe, ~400 passengers (~16% of all) were reported with symptoms of Noro virus. To prevent the illness spread, the ship initiated an extensive sanitizing.
- December 2012, CDC reported on voyage Dec 17 to 27, a Norovirus outbreak affected 189 passengers (out of 3235, or 5,8%) and 31 crew (out of 1189, or 2,6%). All sick were quarantined to their cabins. The ship was on a 10-day round-trip from homeport Fort Lauderdale.
- Note: When the itinerary doesn’t include US cruise ports, the ship is not required to report to CDC, thus no official illness report would be issued.
On the above map you can track the Emerald Princess cruise ship’s position now. It shows the vessel’s current location at sea (or in port) by live tracking of its IMO number 9333151. If you lose the ship on the map, please reload this page.