What SAINT-TUDY's Crew Got Right — And How You Actually Build That Kind of Readiness

An Investigation Report That Reads Differently

Most incident reports exist because something went wrong. BEAmer's investigation into a bearing fire aboard the passenger ferry SAINT-TUDY is genuinely different — not because nothing happened, but because of how directly the investigation credits the crew's own response for the fact that 35 passengers barely knew anything had happened at all.

Lorient–Groix, 25 November 2012 — 12:50

SAINT-TUDY, a 44.5m car ferry certified for up to 319 people, was on a routine crossing with 35 passengers and a handful of vehicles aboard. The captain and helmsman were on the bridge; the chief engineer and a greaser were on their normal duties below. At 12:50, the fire alarm for the Aquamaster propulsion compartment triggered. Both the bridge and the machinery control station had camera feeds and fire alarm repeaters — and both the captain and the chief engineer saw thick smoke on their screens within moments of each other.

What Actually Happened Next

Within three minutes, the captain had declutched both engines and the chief engineer had physically confirmed the source: bearing No. 9 on the starboard shaft line, glowing red, with heavy smoke. He reported it to the bridge immediately. The captain shut down the affected engine, brought the port engine up to bring the vessel in, and notified the company's shore-based Designated Person Ashore — all within about five minutes of the alarm first sounding. A crew member in full firefighting kit went below with a dry powder extinguisher and put out the flames that had just started to appear. The vessel was alongside at Port-Tudy within fifteen minutes of the alarm, passengers disembarked calmly, and local firefighters were called only to help clear smoke from the compartment — not to fight an active fire.

Before deciding how to get the vessel and her 97 return passengers back to Lorient, the captain did one more thing worth noticing: he consulted directly with the chief engineer and with CROSS Étel's shore-based duty officer before choosing to return on a single engine, even though the damaged engine could technically have been used. BEAmer's own conclusion states plainly that the crew's response was well managed, ‘in line with a good safety policy’ within the company — and specifically credits the general cleanliness of the machinery space with limiting how far the fire could have spread.

Why This Is the Story Worth Studying

Every individual action here is describable, repeatable, and teachable — which is exactly what makes it valuable. Recognise the alarm and the visual confirmation together, not one without the other. Declutch and isolate fast, before assessing further. Report up the chain immediately, not once things are already under control. Use the equipment you're trained on rather than improvising. And when a real decision has to be made — one engine or two, for a return crossing carrying passengers — bring in the people who can actually inform that decision instead of deciding alone under pressure.

How Crew Connect Builds This, Not Just Talks About It

This is precisely the gap between knowing a procedure exists and being able to execute it under real pressure — and it's the reason Crew Connect's Decision Simulator and Knowledge Checks exist in the form they do. A Knowledge Check question can test whether you know a bearing overheat should trigger an immediate engine shutdown. It can't test whether you'd actually do it, calmly, in the right order, while smoke is showing on a screen and passengers are aboard. That's what the Decision Simulator is built for — real branching scenarios, sourced from real investigation reports like this one, where the pressure of an unfolding situation is part of what's being tested, not just the textbook answer. SAINT-TUDY's crew didn't get this right by accident; they got it right because the response had clearly been drilled until it was closer to instinct than to memory. Building that same readiness, deliberately, before the real version of this moment ever happens, is exactly what this training is for.

Check Your Vessel

• All crew: Do you know, specifically, what your own first three actions would be if a machinery-space fire alarm triggered right now — not generally, but in the actual order you'd do them?
• Officers: Is your vessel's camera/alarm repeater setup actually monitored in a way that would catch a developing fault this fast, or does it depend on someone happening to be looking at the right screen?
• Masters: When a real operational decision follows an emergency — continue the voyage, return on reduced power, divert — do you have an established habit of consulting your engineer and shore support before deciding, the way SAINT-TUDY's captain did?

Source: BEAmer (Bureau d'Enquêtes sur les Événements de Mer, France) — Rapport simplifié, Incendie d'un palier de ligne d'arbre à bord du transbordeur SAINT-TUDY, 25 November 2012, published April 2013.