Pods stuck at 90° after overspeed trip and a latched water-leak stop (Spirit of Discovery)

Propulsion & ThrustersAutomation / PLCSiemens SISHIp eSiPOD (SiPOD-M10)Pod water leakage stop (WLS) sequence alarm, then propeller overspeed

Contents
  1. What happened
  2. Diagnosis
  3. Root cause
  4. Timeline / response
  5. Lessons
  6. Comments · 0

What happened#

Cruise ship with two Siemens eSiPOD pods (6,500 kW each, no rudder), crossing the Bay of Biscay in force 8–9 wind and 8–9 m waves. At 12:30 the port pod gave a WLS sequence alarm. Very soon after, it tripped on overspeed. Shaft brake on, pod turned 90° to the heading, emergency seal inflated. At 12:36 the starboard pod did the same.

The ship lost steering and fell off nearly beam on to the sea. Until 04:20 next morning the pods tripped 8 more times. 115 people were injured; one later died.

Diagnosis#

  • Before the first shutdowns, rpm shot past the trip point (132 rpm, 110 % of rated 120 rpm), almost certainly from propeller emergence. Overspeed protection caused every loss of propulsion.
  • Roll up to 13°, pitch up to 4°: inside the SOLAS design limits (22.5° / 7.5°).
  • The WLS request was stored in the PCS. The next stop of any kind ran the WLS shutdown, with no override and no restart until the sensor was reset.
  • About 100 ml of oil and water was pumped from each motor unit. The bilge suction probably did not reach it, and the motion likely threw it onto the low level sensor.
  • The maker's manual said WLS shutdown starts only when STOP PROP is pressed.
  • After the first trip, below 12 kts, the OOW switched to manoeuvre mode (faster ramp) to use the bow thrusters and turn the pods beyond 35°. This might have contributed to the later trips.

Root cause#

Heavy pitching lifted the propellers out of the water. Rpm rose faster than the PCS could ramp it down, and the overspeed trip cut the motor. On its own that could likely have been reset quickly. But residual liquid had most likely reached the low bilge sensor and latched a WLS request, so the trip became a full WLS shutdown.

The manual described the WLS logic wrongly. The ship had overspeed trips and an unexpected WLS shutdown in February 2023, but the maker's fixes came only after this accident.

Timeline / response#

TimeEvent
12:30Port pod WLS alarm; very shortly after, overspeed trip and pod parks at 90°.
12:36Starboard pod trips and parks the same way.
~12:45Warning override used, starboard pod restarted; engineers start pumping out both motor-unit bilges.
13:08Port pod back at reduced speed.
13:00–04:208 more trips, each reset in about 10–15 min. Both pods out 17:18–17:27.
05:15 (5 Nov)Passage resumed.

Lessons#

  1. Know what each alarm latches. If it is standing and the drive trips, what happens? Treat a pod WLS alarm in heavy weather as urgent.
  2. Check the manual against the real logic. Get the automatic shutdown sequences from the maker into your emergency checklist.
  3. Keep pod motor-unit bilges dry. Compare bilge suction height with sensor height. The maker has since moved the sensors. Until then, plan fast pumping out; rigging portable pumps delayed the restart here.
  4. Think before switching to manoeuvre mode in heavy seas. Its faster ramp lets rpm reach the trip sooner when the propellers emerge; the switch probably made the pods more vulnerable.
  5. Record and report every overspeed trip and unexpected WLS start. Save the rpm trend, sea state and mode. Write an on-board instruction for use until the maker's fix is fitted.

A latched alarm can turn a resettable trip into a shutdown you cannot override.

Source: MAIB report 6/2026 — Loss of propulsion in heavy weather experienced by the passenger vessel Spirit of Discovery, leading to over 100 injuries and one fatality. Contains public sector information licensed under the Open Government Licence v3.0.

Comments · 0

No comments yet.

Sign in to comment, vote and confirm fixes.Sign in