All Sectors

Storm Force, No Propulsion, 115 Injured: What Spirit of Discovery Teaches Every Senior Officer About Heavy Weather Decisions

🕑 5 min read words Safety • Incident

Bay of Biscay, 4 November 2023 — 12:30

Spirit of Discovery, a 58,119 gross tonne cruise vessel carrying 943 passengers and 503 crew, was crossing the Bay of Biscay in a Force 10 westerly with a long, heavy swell when its port propulsion pod shut down automatically and rotated 90° across the vessel’s heading.

The bridge team had not expected the rotation. Six minutes later, the starboard pod did the same. The vessel was now beam to the sea in hurricane-force conditions, pitching heavily and rolling violently. An announcement went out asking passengers to sit down and minimise movement.

In The Grand Dining Room, tables and chairs were already moving.

Within 20 minutes of losing propulsion, 115 passengers had been injured. The ship’s medical team of four were treating casualties across multiple public spaces without a triage system in place. The Mass Casualty Incident Plan existed. No one activated it.

One passenger, 85-year-old Trevor Gilks, fell from a high-backed chair when the vessel rolled to 10–13°. He reported severe neck and shoulder pain. A nurse arrived, examined him, and helped him stand. He was walked back to his chair. He was not placed on a spinal board.

He died on 8 November 2023, four days after the vessel docked in Portsmouth. His cause of death was recorded as complete cervical spine injury.

MAIB Report 6/2026 was published in March 2026. It found four failures that stacked to produce one death and 115 injuries, and it names each one precisely.

What the Investigation Found: Four Failures

1. A Passage Plan That Was Not Effectively Challenged

The story of how Spirit of Discovery came to be crossing the Bay of Biscay in those conditions is one of good intentions reversed under pressure.

The captain had shown early good judgement. In late October, he had discussed the weather forecast with Saga’s team ashore and agreed to cancel the Las Palmas port call, bringing the vessel into A Coruña early so that it could wait out the storm before sailing to Portsmouth. On 1 November, that plan was in place.

On 3 November, A Coruña announced its port would be closed — the forecast 6–9m wave height exceeded the pilot transfer limit. The captain discussed the change with Saga and the DPA, and agreed a direct passage to Portsmouth, crossing the Bay of Biscay. The weather routing service advised against the crossing. Table 3 in the MAIB report shows the alternative: a 12–24 hour delay would have allowed the storm to pass and the crossing to be made in significantly better conditions.

No officer on board formally challenged the revised plan. The DPA agreed it. The weather routing advice was logged but not acted upon. The MAIB’s finding is direct: the decision was not effectively challenged despite information available to the senior team that should have prompted a harder look.

2. A Propulsion Cascade the Crew Had Seen Before

Spirit of Discovery’s propulsion system — two Siemens SISHIP eSiPOD azimuth drives — had rated transient operating limits of +/- 22.5° of roll and +/- 7.5° of pitch. At 12:30, in conditions that were exceeding those limits, the port pod’s Water Leakage Stop (WLS) sequence alarm activated.

The Engineering Officer of the Watch advised the OOW that the WLS alarm was not a concern and could be acknowledged. Very shortly afterwards, the port pod’s propeller overspeed alarm activated. The pod automatically shut down, applied its shaft brake — and then rotated so that the propeller was oriented 90° inboard to the vessel’s heading. This last part was not expected by the bridge team. It had not been briefed as part of heavy weather preparations. It was not in the operating instructions the OOW had access to.

It had, however, happened before. In February 2023, Spirit of Discovery had experienced an identical propulsion overspeed sequence, including the 90° rotation. A non-conformance report had been raised. The technical issue had been reviewed. The cascade — specifically, that acknowledging the WLS alarm in the observed operating condition would lead to overspeed and pod rotation — had not been incorporated into the bridge team’s procedures, briefings, or operating instructions.

Nine months later, the same thing happened again. This time in Force 12 conditions with 943 passengers aboard.

3. A Mass Casualty Plan That Was Never Activated

115 passengers were injured in the first 20 minutes. The medical team of four — a doctor, a senior nurse, and two nurses — were treating casualties across multiple public spaces. Code Alpha medical emergency announcements were going out every few minutes. 23% of injured passengers later said the medical treatment they received was inadequate; they attributed this to the medical team being overwhelmed.

The Mass Casualty Incident Plan existed. Saga’s head of safety and policy assurance had emailed the senior leadership team the evening before, specifically suggesting they refresh themselves on the MCIP. It was not activated during the emergency.

The MAIB’s finding is precise: the MCIP was not implemented, and this contributed to the medical team becoming overstretched. A Mass Casualty Incident Plan is not bureaucracy — it is the structure that prevents a small, capable medical team from being paralysed by unstructured demand. Without it, triage does not happen, roles are not assigned, and the most critically injured patients are not necessarily seen first. That is what happened on Spirit of Discovery.

4. A Spinal Injury Managed Incorrectly for Four Hours

At 17:10, Trevor Gilks fell backwards from a high-backed chair when the vessel rolled to approximately 10–13°. The main impact was to his neck. A nurse arrived three minutes later, examined him, and — with crew assistance — helped him stand and return to the chair.

At 21:19, having been unable to move to the bathroom unassisted, he was taken to the medical centre in a wheelchair. His head had slumped forward, chin almost on his chest, and he was having difficulty breathing. The doctor fitted a neck collar.

Between 17:10 and 21:19 — four hours and nine minutes — Trevor Gilks had moved from the floor of the Living Room to a chair, to his cabin, and to the medical centre. He had been mobile with a fractured cervical spine.

The MAIB found that the initial nursing assessment did not identify the potential for a spinal injury. Clinical guidelines — including NICE and ATLS protocols — specify that any fall involving a significant mechanism of injury to the head or neck should be treated as a suspected spinal injury with immobilisation until exclusion by a qualified clinician. That did not happen. The MAIB concluded that the delay in identifying the severity of the injury and the movement that followed “may have contributed to the severity of his spinal injury.”

What If? — The Decisions That Could Have Changed the Outcome

What if the weather routing advice had been formally assessed against Spirit of Discovery’s specific operational limits before the revised plan was agreed? A 12-hour delay would have been achievable. The information existed. What was missing was a formal process that required someone to ask: “Here are our propulsion motion limits and the weather routing advice — do these support the plan?”

What if the February 2023 propulsion cascade had been incorporated into bridge operating procedures? The OOW on 4 November did not know that acknowledging the WLS alarm would lead to pod overspeed and then unexpected rotation to 90°. A non-conformance report is not a procedure update. A procedure update is not training. All three are needed for a previous incident to change what the next crew does.

What if the Mass Casualty Incident Plan had been activated at the first Code Alpha call? Activation would have established triage, assigned crew roles, and allowed the small medical team to focus on the most serious cases first. The 23% of passengers who felt the medical response was inadequate may have had a different experience.

What if Trevor Gilks had been immobilised in place when he fell? Clinical guidelines are unambiguous: a fall with a significant mechanism of injury to the head or neck is a suspected spinal injury until excluded by a clinician. The correct action is to immobilise the patient where they are, not to help them stand.

Role-Based Lessons

For Masters

Effective challenge of a passage plan means more than raising a concern informally — it means documenting the challenge, the risk assessment behind it, and the decision made in response. Your ISM Code Section 5.2 overriding authority is not a mechanism to bypass that assessment — it is the mechanism for resolving a disagreement between commercial pressure and safety.

When a concurrent propulsion emergency and mass casualty event occur, you cannot manage both from the bridge alone. Activate the MCIP early through the staff captain — not when the medical team are already overwhelmed.

For Chief Engineers and EOOWs

When you advise the bridge to acknowledge an alarm, you are responsible for everything that follows the acknowledgement. If you know that acknowledging an alarm in the current operating condition will trigger a cascade, communicate that cascade before the bridge acts on your advice.

If a previous incident revealed a cascade or unexpected behaviour, ensure that information reaches the bridge team’s operating procedures, heavy weather briefings, and training — not just an NCR.

For Officers of the Watch

When an engineering officer advises you to acknowledge an alarm, it is entirely reasonable to ask: “What happens next?” before acting on that advice. If your vessel is not fitted with an electronic inclinometer, flag it through your ISM defect reporting system.

For All Crew in Passenger Spaces

If a passenger falls and hits their head or neck, do not help them stand. Call the medical team immediately, keep the passenger still, and document the time and mechanism of injury.

Vessel Checks: Do These Before Your Next Heavy Weather Passage

Propulsion limits and instrumentation: What are your vessel’s propulsion system motion limits? Is there a digital instrument on the bridge that measures roll and pitch in real time?
MCIP activation trigger: What triggers your Mass Casualty Incident Plan? Who activates it? When was it last drilled as a full exercise?
Alarm cascade knowledge: For each propulsion alarm your OOWs might receive advice to acknowledge, do they know what follows? If a previous incident revealed an unexpected cascade, is it in operating procedures?

Test Your Knowledge

Think you know how you’d handle a concurrent propulsion emergency and mass casualty event? Test yourself at Crew Connect — try a quick safety round with questions from this investigation at Master, Chief Engineer, and OOW level.