All Sectors

Numerous Opportunities: El Faro and Hurricane Joaquin

🕑 5 min read words Safety • Incident

Vessel: SS El Faro (US-flagged cargo ship, operated by TOTE Maritime)
Date & location: 1 October 2015, Atlantic Ocean, approx. 40 NM northeast of Crooked Island, Bahamas
Outcome: Sank in Hurricane Joaquin after losing propulsion and taking on flooding. All 33 crew died
Human factors: Plan Continuation Bias · Authority Gradient / Hedging Language · Organisational Safety Culture
Source: US National Transportation Safety Board, Marine Accident Report NTSB/MAR-17/01

9 decision points5 outcome paths~10 min read + Knowledge Checker

A Twelve-Hour-Old Forecast

El Faro sailed from Jacksonville, Florida for San Juan, Puerto Rico on 29 September 2015, on her usual route, as Hurricane Joaquin was developing in the Atlantic. Captain Michael Davidson planned his route based on a weather forecast package projecting the storm would take a sharp northward turn before reaching the Bahamas — and held to that plan even as the hours passed and the information in hand grew steadily more out of date, in places relying on a forecast package roughly twelve hours old.

Mates Raised It. The Captain Held Course.

As conditions worsened overnight, officers on watch raised the option of diverting further west, into the Old Bahamas Channel, for more sea room and a later, safer transit. Recovered voyage data recorder audio shows the crew's concerns expressed in hedging, indirect language rather than a direct challenge to the Master's plan. Davidson did not change course.

Propulsion Lost, Water Coming In

By the early hours of 1 October, El Faro had taken a severe list. The main engine's lube oil sump lost suction as the list increased, and propulsion was lost. Water began entering a cargo hold through an open scuttle, and downflooding developed through ventilation closures elsewhere on the ship. The crew's chances, already reduced by the loss of propulsion in hurricane-force conditions, were reduced further by the ship's survival craft: open, uncovered lifeboats, which met carriage requirements but were never going to be usable in these conditions.

What the Investigation Found

The NTSB concluded the sinking “was caused by the captain's failure to avoid sailing into a hurricane, despite numerous opportunities to route the vessel away from the hazardous weather.” Contributing safety issues named in the report included the captain's use of non-current weather information, a late decision to muster the crew, ineffective bridge resource management, and inadequate oversight from the vessel's operator, TOTE Maritime, whose safety management system did not intervene in the routing decision as the storm developed.

Recommended Actions

Use current, verified weather information when routing near a tropical system — check the currency of a forecast package before relying on it, not just its content
A structured Bridge Resource Management process that empowers officers to challenge a Master's routing decision directly, with an unambiguous means to escalate a genuine safety concern
Company oversight of a vessel's routing decisions near severe weather should be active, not left solely to the Master's judgement once underway
Vessels on routes exposed to tropical storm risk should be fitted with enclosed lifeboats, not open ones
A documented, drilled damage control plan for flooding scenarios, including cargo hold ventilation closures, should be in place before it's needed

Human Element Analysis

Plan Continuation Bias

Captain Davidson had committed to a route before the storm's true track was known, and held to it even as newer information suggested it needed to change. A plan made early under less information is not automatically the safest plan once more information exists — but it takes a deliberate decision to abandon it, and that decision was never made.

Authority Gradient / Hedging Language

Officers who were concerned raised the option of an alternate route in indirect, hedging language rather than a direct challenge. This is a well-documented pattern in high-authority-gradient bridge teams: a genuine concern gets softened into a suggestion, and a suggestion is easier for a confident senior figure to not act on.

Organisational Safety Culture

TOTE Maritime's safety management system did not actively monitor or intervene in the vessel's routing near a developing hurricane. A Master's judgement, alone, was the only safeguard between the vessel and the storm — and the company's own system offered no independent check on it.

How This Pattern Repeats

Industry	Incident	The parallel
Aviation	Air France Flight 447, 2009	A crew continued into deteriorating conditions with available warning information not fully acted on, and a breakdown in effective crew resource management under high stress that followed.
Nuclear	Fukushima Daiichi disaster, 2011	Reliance on historical hazard assumptions rather than updated, current risk information, in a situation where the assumptions had already been overtaken by events.
Offshore	Deepwater Horizon disaster, 2010	Schedule and commercial pressure from the operating company influenced a safety-critical decision made under time pressure, with warning signs available but not acted on.

See How You'd Handle It

The scenario opens the night before, with a forecast package already hours old and a storm still developing. Do you seek a fresher update before committing further, or proceed on the plan you have? Try the Decision Simulator and see how the different branches play out.

Test Your Knowledge

Think you've got this covered? Put it to the test in Crew Connect's free Knowledge Checker — try a quick navigation round and see how you score.