Royal Princess cruise ship accidents, incidents and law news reports relate to a passenger vessel with IMO number 9584712, owned by Carnival Corporation and operated by its subsidiary the Princess Cruises line company. Among the unfortunate events at sea are crew and passenger incidents (deaths, injuries, crimes), machinery malfunctions.
Here you can also track MS Royal Princess position at sea.using the AIS live ships tracker of VesselFinder. The 142,700-ton 3600-passenger Princess cruise ship Royal was built in 2013 by the Fincantieri shipbuilding company in Italy.
Royal Princess accidents & incidents
At the Royal 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 Royal 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 Royal 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.
History, technical incidents
- The first Royal Princess cruise itinerary had duration of 2 nights (June 9 to 11, 2013) leaving round-trip from Southampton to St Peter Port (Guernsey, Channel Islands). The “Inaugural Cruise” was on June 16, 2013 (a Mediterranean round-trip out of Southampton England) visiting ports in Portugal and Spain – Vigo, Lisbon, Gibraltar (UK), Malaga, Barcelona
- Note: This vessel is the third one carrying this exact name. It was preceded by a 1984-built ship (currently MV Artania) and a 2001-built ship (currently MV Adonia). With the same design and similar facilities and amenities are the ships Regal Princess (launched 2014) and also Majestic Princess (launched 2017).
- August 20, 2013, after leaving call port Piraeus (Athens, Greece), at ~9:30 pm the ship experienced a power outage for ~5 min. After the lights came back, the Captain announced that the vessel lost a power generator and that the emergency generator’s power output will be prioritarily used by the navigation and propulsion systems. After the announcement, the lighting went out again, then after ~10 min it was back on. The Captain made another announcement that ship will reduce speed in order to save power for the hotel services. This lasted for ~30 min until the problem was fixed. Then power was restored and the ship regained its normal cruising speed.
- September 22, 2013, the ship was operating in the Mediterranean Sea (Europe), on a 12-days cruise from Venice to Barcelona (Sept 15 to 27). When it was en-route from Mykonos Greece to Naples Italy, the vessel experienced a total power loss. The incident occurred at ~1:30 pm, and lasted for ~3 1/2 hours. During the power outage, the ship’s emergency generators provided power for all the passenger services on board. It was reported that prior to the power outage, the anchor motor failed, leaving 90 ft / 27 m of anchor to hang out. It took the crew ~4 hours to replace the motor with a new one. Princess Cruises decided to cancel the second leg on the Mediterranean cruise, dropping all the remaining call ports along the itinerary (Civitavecchia-Rome, Livorno and Toulon). After late arrival in Naples, Princess (covering all travel expenses) flew the passengers back home with flights leaving from Naples and also from Rome. After Naples, the ship continued directly to Barcelona, with the crew doing repair works on the way. The next departure (out of Barcelona to Venice) was according to schedule. During the accident, the ship had a total of 3594 passengers and 1336 crew. As compensation, all passengers received a full refund, plus a 25% future Princess cruise booking discount.
- March 31, 2014, the vessel was docked in homeport San Francisco CA, when a heavy storm caused its mooring lines to snap. The incident occurred at ~1 pm. Port authorities were called for assistance. Similar incident affected the Cunard Queen Victoria ship (also berthed there). After the Cunard ship broke its mooring ropes, it began listing starboard towards the San Francisco Bay.
- May 2014, the Royal Princess liner was featured in a 4-part documentary series aired in prime time on ITV1 in May. The documentary’s name was “The Cruise Ship” – filmed onboard the ship. The series showed a behind the scenes look at the crew’s daily routines and also interviews with Princess cruise passengers. Similar 6-part documentary was filmed onboard the Regal Princess liner (named “The Cruise”) and was screened at prime time on ITV in March 2016. In both documentaries the Princess cruise company had no editorial control over the production.
- May 18, 2015, the ship reported one of its all 11 tender boats (used for ship to shore passenger transportation) experienced a power loss.
Crew & Passenger Death accidents
- December 3, 2016, a 64-year-old male passenger died ashore while snorkeling in Aruba. The man (Martin Brutosky, of NYC, US origin) together with his wife arrived in St Johns, Antigua – call port on the ship’s 15-day Caribbean cruise from Fort Lauderdale (itinerary Nov 26 – Dec 10). The accident occurred in the afternoon, on a Stingray City snorkeling tour. The woman allerted the police after noticing that her husband stopped moving, after some 10 min in the water. She brought him to the surface and called for help. One of the boat tour’s staff members administered CPR, but the man remained unresponsive. He was ambulanced to Jumby Bay, then to Mount St John Medical Centre where was pronounced dead.
Crew & Passenger incidents (injuries, crimes)
- Fortunately, no such major incidents were officially reported so far.
On the above map you can track the Royal 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 9584712. If you lose the ship on the map, please reload this page.