Pacific Aria accidents and incidents
CruiseMapper's Pacific Aria cruise ship accidents, incidents and law news reports relate to a 1512-passenger vessel owned by P&O Australia (P&O Cruises). Our Pacific Aria accidents page contains reports made by using official data from renown online news media sources, US Coast Guard and Wikipedia.
Here are also reported latest updates on cruise law news related to ashore and shipboard crimes still investigated by the police. Among those could be arrests, filed lawsuits against the shipowner / cruise line company, charges and fines, grievances, settled / withdrawn legal actions, lost cases, virus outbreaks, etc.
- fires - 2003, 2013
- ship listing - 2003
- propulsion/power loss - 2002, 2006, 2007, 2012
- sea pollution (Alaska) - 2002, 2012 (3)
- Norovirus (passengers/crew) - 2002 (total 356 / 39), 2005 (272 / 37), 2006 (total 166 / 18), 2007 (total 355 / 47), 2008 (113 / 8), 2011 (total 217 / 17), 2015 (NA)
- deaths - 2011 (Belize snorkeling), 2014 (overboard crew), 2015 (murder-suicide)
- injuries/crimes - 2010 (released anchor), 2017 (rape)
- medevacs - 2014
During its service history, this cruise ship was also known as “MS Ryndam” (launched 1994) being constructed for the Holland America Line. HAL operated the vessel until 2015 when it was transferred by the shipowner Carnival Corporation to the P&O Australia cruise line’s fleet.
The vessel is of the same class as the Holland America ships Maasdam and Statendam (currently CMV Vasco da Gama). For Holland America, Ryndam operated on Caribbean cruises from Florida (during winter) and on Alaskan cruises from Vancouver BC Canada (during summer). Before its transfer to P&O, HAL's Ryndam ship was drydocked for refurbishment in Singapore, then renamed to “Pacific Aria”. The P&O Pacific Aria ship naming ceremony was in Sydney (on November 25, 2015).
|29 May 2017||Crew / Passenger Crimes|
(sexual) On May 29, 2017, an Australian news media reported that a 33-year-old male passenger was arrested and charged with raping. He allegedly abused his cabin mate (travel companion) – a woman in her 40s, The incident occurred while the ship was off Queensland Australia’s coast, operating on 4-day Cruise to Nowhere from homeport Brisbane.
|30 December 2015||Structural and Technical Issues|
On January 7, 2016, an Australian news media reported an iPhone video footage of stormwater cascading down stairs and spilling into the corridors of the ship. The incident was video recorded on December 30, while the ship was en-route from Cairns to Brisbane. According to P&O Australia, the accident was due to a huge downpour during the storm. As compensation, on Dec 31 the ship provided free drinks for a period of 6 hours.
|02 April 2015||Crew / Passenger Deaths|
(MS Ryndam) On April 2, 2015, a couple was found dead in their cabin. The murder-suicide accident occurred while the ship was berthed in call port San Juan Puerto Rico. The couple (man and woman in their 50s) were from Cleveland Ohio (USA). How they died remained unclear. The bodies were found by the crew. The ship was on 14-day Southern Caribbean cruise roundtrip from homeport Tampa to Key West FL, followed by 2 sea days before San Juan.
|January 2015||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) On July 1, 2015, the vessel was forced to shorten a 14-day roundtrip voyage from Harwich, UK, due to Norovirus (gastrointestinal illness) outbreak. The ship returned to homeport Harwich a day early (on July 3), so the staff could perform deep cleaning before the next voyage (14-day "Voyage of the Midnight Sun", departure July 4).
According to the cruise company's official statement, during the 14-day "Northern Isle" cruise from Harwich (departure June 20), a "high number of guests" reported to the infirmary Norovirus symptoms (stomach cramps, vomiting, diarrhea).
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.
|21 December 2014||Crew / Passenger Deaths|
(MS Ryndam / overboard) On December 21, 2014, a 27-year-old male crew (from Thane India) was reported missing and presumably overboard. The accident occurred in the Caribbean Sea, while the ship was returning to homeport Tampa Florida. The man’s body was found on December 26 - along Sand Key Park (Clearwater Beach, Florida).
|10 June 2014||Coast Guard Medevacs|
(MS Ryndam) On June 10, 2014, while en-route to call port Stavanger Norway, due to a medical emergency the ship had to turn back to call port Kristiansand Norway, ~30 min after departure. A male passenger (suffering from acute illness) was disembarked and taken by an ambulance to Sorlandet Hospital Kristiansand.
|07 June 2013||Fire Accident|
(MS Ryndam) On June 7, 2013, the vessel suffered a fire accident during 7-day Norwegian Fjords cruise (itinerary June 1-8) roundtrip from homeport Dover (England UK). The accident occurred at ~ 0:20 am when the ship’s fire alarm sounded. The fire was in the funnel’s exhaust pipe. Flames were soon extinguished. The whole incident lasted ~40 min. The itinerary was not affected.
|18 November 2012||Propulsion / Power Loss|
(MS Ryndam) On November 18, 2012, USCG reported the vessel experiencing maneuverability problems.
|December 2011||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) In December 2011, CDC reported on itinerary December 11-18, a Norovirus outbreak affected 69 passengers (out of 1298, or 5,3%) and 6 crew (out of 574, or 1,1%).
|November 2011||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) November 2011 CDC reported on itinerary November 3-20, an epidemic Norovirus outbreak infected 148 passengers (out of 1188, or 12,5%) and 11 crew (out of 574, or 1,9%).
|02 February 2011||Crew / Passenger Deaths|
(MS Ryndam) On February 2, 2011, a 60-year-old female passenger died ashore while the ship was berthed in call port Belize City. The accident occurred at ~2 pm in the waters of Goff’s Caye, where the snorkeling woman got caught in the tour boat’s propeller, cutting her in pieces. Badly injured, she was taken by an ambulance to Belize Medical Associates (private hospital) where she succumbed to the injuries. The woman and her husband were on a snorkeling excursion on a 65-ft catamaran boat. The woman was snorkeling with 3 other cruise ship tourists when went under the tour boat.
|27 November 2010||Crew / Passenger Crimes|
(MS Ryndam) On November 27, 2010, a 44-year-old male passenger (while in an intoxicated condition) broke into a control room (at 5:25 am) and released the cruise ship’s stern anchor. The vessel was in the Caribbean Sea, en-route from Mexico (Costa Maya) back to homeport Tampa Florida.
The man (Rick Ehlert, from Thousand Oaks California) was traveling together with his girlfriend and admitted to the crime. He was charged with a 3-count indictment – for attempting “damage, destroy, disable, or wreck a vessel”. Releasing the anchor on a moving ship could have damaged its navigation and propulsion (rudder and propeller), thus, disabling its ability to maneuver. Also possible was hull damage (by the anchor) causing flooding or even sinking.
(MS Ryndam) In 2009 (July 21) and 2010 (May 20, August 20) the vessel was reported for water pollution in Alaska – exceeding the monthly allowable levels for ammonia and E-coli bacteria.
|February 2008||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) In February 2008, CDC reported on itinerary February 15-25, an epidemic Norovirus outbreak infected 113 passengers (out of 1226, or 9,2%) and 8 crew (out of 556, or 1,4%).
|11 April 2007||Propulsion / Power Loss|
(MS Ryndam) On April 11, 2007, at ~1 pm, the ship shuddered, slowed and eventually stopped. After a while, it continued at reduced speed. The accident resulted in ~4-hours late arrival in homeport San Diego CA, where the vessel was assisted by tugboats during entering and berthing. As the incident was caused by Azipod (propulsion unit) malfunction, an ABB specialist was flown from Finland to fix the problem.
|March 2007||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) In March 2007, CDC reported on itinerary March 3-13, a Norovirus outbreak affected 61 passengers (out of 1209, or 5,1%) and 7 crew (out of 593, or 1,2%).
On March 13, 2007, due to cleaning procedures following the gastrointestinal illness outbreak, the ship’s scheduled March 13 departure was changed to March 15. All booked passengers were allowed to cancel (with a full refund) or receive a 2-day refund in addition to onboard credit per person.
|March 2007||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) February-March 2007, CDC reported on itinerary February 21-March 3, an epidemic Norovirus outbreak infected 184 passengers (out of 1260, or 14,6%) and 26 crew (out of 579, or 4,5%).
|February 2007||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) January-February 2007, CDC reported on itinerary January 22-February 21, an epidemic Norovirus outbreak infected 110 passengers (out of 1153, or 9,5%) and 14 crew (out of 573, or 2,4%).
|09 December 2006||Propulsion / Power Loss|
(MS Ryndam) On December 9, 2006, due to the engine and electrical problems, the ship remained anchored overnight in Tampa Bay. Engine problems occurred ~1 hour after the departure from homeport Tampa Florida. After the ship’s power was restored, the USCG forced the vessel to remain moored overnight for further investigation.
|01 August 2006||Propulsion / Power Loss|
(MS Ryndam) On August 1, 2006, the vessel suffered propulsion motor failure while navigating in Alaska (en-route from Ketchikan to Juneau). Operating with just 1 Azipod motor, the ship continued on the voyage while the crew unsuccessfully tried to make repairs. On Aug 2, the technical team from the unit’s manufacturer (ABB) was sent to Juneau and fixed it.
|June 2006||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) May-June 2006, CDC reported on itinerary May 28 - June 4, a Norovirus outbreak affected 64 passengers (out of 1230, or 5,2%) and 5 crew (out of 574, or 0,9%).
|May 2006||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) In May 2006, CDC reported on itinerary May 14-21, an epidemic Norovirus outbreak infected 102 passengers (out of 1279, or 8%) and 13 crew (out of 570, or 2,3%).
|January 2005||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) In January 2005, CDC reported on itinerary January 13-29, an epidemic Norovirus outbreak infected 272 passengers (out of 1223, or 22,2%) and 37 crew (out of 574, or 6,4%).
|February 2004||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) In February 2004, CDC reported on itinerary February 7-14, a Norovirus outbreak affected 73 passengers (out of 1260, or 5,8%) and 9 crew (out of 550, or 1,6%).
|July 2003||Fire Accident|
(MS Ryndam) In July 2003, during its Alaskan inaugural cruise season, the ship reported a fire accident. It occurred in an onboard storage area on service deck 3 (B Deck) during berthing in call port Juneau Alaska. Damages were minor and the fire was quickly extinguished. The itinerary was not affected.
|13 March 2003||Ship Listing|
(MS Ryndam) On March 13, 2003, at ~6:30 pm, the ship listed portside. The accident resulted in crew and passenger injuries, broken tableware, damaged furniture, empty swimming pool, flooded elevator shafts (damaged lifts portside). The accident was caused by a mechanical failure during switching between manual navigation and autopilot.
|17 August 2002||Sea Pollution|
(MS Ryndam) On August 17, 2002, the vessel was reported for water pollution in Alaska – sewage sludge was discharged into Juneau harbor.
|August 2002||Propulsion / Power Loss|
(MS Ryndam) In August 2002, while in Alaska (Lynn Canal) the ship lost power (including all propulsion). The vessel drifted for ~20 min as the sea was too deep to anchor. It was tugged to Auke Bay, where was inspected by USCG. As a result, the scheduled Glacier Bay was replaced with Tracy Arm Fjord and Sawyer Glacier.
|2002||Cruise Illness / Norovirus Outbreaks|
(MS Ryndam) In 2002, CDC reported 3 norovirus outbreaks – itinerary April 7-24 (NA), itinerary July 1825 (167 passengers, 9 crew), itinerary July 25-August 1 (189 passengers, 30 crew).
You can add more details on reported here accident or submit new / your own Pacific Aria ship incident ("Cruise Minus" report) via CruiseMapper's contact form.