Viking Star

Viking Star
3.5 (70%) 4 votes

MV Viking Star cruise ship accidents, incidents and law news reports relate to a passenger vessel with IMO number 9650418, owned by the Viking Ocean Cruises line. Among the unfortunate events at sea are crew and passenger incidents (deaths, injuries, crimes), machinery malfunctions.

Here you can also track MV Viking Star position at sea.using the AIS live ships tracker of VesselFinder. The 47,800-ton 940-passenger Viking Ocean cruise ship Viking Star was built in 2015 by the Fincantieri shipbuilding company in Italy.

MV Viking Star accidents & incidents

MV Viking Star accidents and incidents - Cruise MinusAt the MV Viking Star CruiseMinus page you will find a complete list of this Viking Ocean 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 Viking Ocean Star ship 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 Viking Star ship incidents (negative cruise experience reports) via the Cruise Minus “contact us” form.

This is link to the ship’s official site

Technical incidents

  • Note: Among the vessel’s innovative marine technologies are its energy-saving hybrid engines, top-deck solar panels, pollution-minimizing exhaust system. This ship also uses seawater as a lubricant for its propeller shaft bearings. This technology lowers the vessel’s maintenance costs and also the risk of pollution. Replacing the biodegradable oils, the water is being directly discharged into the ocean. The other Viking Ocean ships (with the same design) are named Viking Sea (2016), Viking Sky (2017) and Viking Sun (2017)
  • July 29, 2015, during a 14-days Baltic and Norway cruise (Stockholm to Bergen, starting July 25), the ship experienced a power loss accident. It was reported that one of the starboard engines malfunctioned (electric transformers blew up). The incident occurred at dinner time (~7:30 pm) when after a boom the lights started flickering. Soon after the fire alarms were activated and the fire doors closed. The ship continued at greatly reduced speed. The Captain reported at ~8 pm that they have a mechanical problem and the arrival in Tallinn will be delayed. After arriving in call port Tallinn, Estonia, passengers were informed that the ship will stay there at least until Aug 4, waiting for a spare part to be delivered. Some of the sponsored by Viking shore excursions and tours were cancelled. Passengers were given the option to stay on the ship or cancel (without penalty). On Aug 2, the sailing was officially cancelled by Viking Ocean due to “mechanical issues”. As compensation, all passengers received a 50% refund, plus 50% future Viking cruise booking discount. All passengers were offered complimentary airfare if they wish to flight back home from Tallinn. They were also allowed to stay on the ship until Aug 4, then Viking Cruises (complimentary) flew them to Bergen Norway. All guests were put in local hotels, with meals and tours arranged for the remainder of the cruise (ending Aug 8). Over 500 cruise passengers were flown from Estonia to Norway via commercial and charter flights. On August 10, the ship arrived in Copenhagen Denmark to embark passengers for the next (changed) itinerary to Kiel Canal and Le Havre (Paris). Passengers booked on the Aug 8 sailing received US$200 in onboard credit as compensation for the revised itinerary.
  • August 2015, several passengers reported one and the same cabin bathroom incident – the shower stall’s glass (in the side panel) shattered without any provocation. The Viking Ocean line asked for consultation the ship’s designers and the glass manufacturer, and also independent glass experts. The conclusion was that the incidents were isolated, and don’t correlate to a particular category of cabins or their deck location. Glass failures were caused by the new cruise ship’s settling process and incorrect glass fitting. As a preventive measure for future incidents of this kind, the line decided to remove the shower glass in all cruise cabins and replace it with new materials
  • October 12, 2016, at night, while passing through Cape Cod Canal (Massachusetts, USA) the ship scraped Buzzards Bay Railroad Bridge. The contact with the bridge was made by an aluminum mast (light pole). After the incident, the bridge was inspected and no damages were reported.

Crew & Passenger Death accidents

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

Crew & Passenger incidents (injuries, crimes)

  • September 18, 2015, Norwegian media news reported that Ms Trude Drevland (Bergen’s mayor), and Mr Inge Tangeraas (Bergen’s harbor master) were both charged with corruption. The incident relates to the Viking Star cruise ship’s launching (June 23, 2014) at the shipbuilding yard in Venice Italy. The official christening ceremony took place in Bergen Norway (May 17, 2015). Allegedly, Ms Drevland accepted a Viking Ocean’s (shipowner) paid-for-trip to Venice and a luxury hotel stay there, plus a 2-days long Norway cruise (Bergen to Oslo) and a 7-days long Mediterranean cruise (later turned down). Allegedly, Ms Drevland also tried to influence other Norwegian government agencies on the Viking cruise line’s behalf. If found guilty, she faces up to 10 years in prison. The charges allege Mr Torstein Hagen (Viking Cruises chairman) picked up in his private jet Ms Drevland, her son and Mr Tangeraas and flew them to Venice as his personal guests for the ship’s launch. Allegedly, they all stayed in a luxury Venice hotel at the Viking’s expense. Drevland and Tangeraas rejected the charges.

MV Viking Star current position

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