All Sectors

Algoma Verity: The Pilot Kept Saying "We're Going to Be Fine" — He Was Wrong Twice

🕑 5 min read words Safety • Incident • Navigation

Vessel: Algoma Verity (dry bulk carrier, 623ft, Canadian-operated)
Date & location: 8 January 2025, Delaware River near Philadelphia, Pennsylvania, USA
Outcome: Grounded twice within 15 minutes; refloated after 3 days; $6.6 million in hull/structural damage; no injuries, no pollution
Human factors: Expectation Bias · Bridge Resource Management (Communication) · Deference to Authority
Source: NTSB Marine Investigation Report MIR-26-06, published 4 March 2026 (case no. DCA25FM015)

6 decision points2 outcome paths — take the conn / trust the pilot~9 min read + Knowledge Checker

"We're Out of the Channel." "Yeah, But It Shouldn't Be That Bad."

At 1745 on 8 January 2025, a Delaware River pilot handed over the conn of the laden bulk carrier Algoma Verity to a second pilot – 25 years' experience, a Special Duty qualification, no drugs or alcohol involved, a full night's sleep every night that week. Twenty-nine minutes later, the ship was aground for the first time. Fifteen minutes after that, it was aground again, taking on water through a ruptured hull.

This is not a story about an unqualified pilot or a mechanical failure. It's a story about what happens when a plan formed in someone's head keeps getting defended against evidence that it isn't working – and about a Master who saw the problem developing, said so four separate times, and still didn't take the conn.

The Plan: Use the Current, Not Fight It

North of the Benjamin Franklin Bridge, the Delaware River channel bends to starboard. Pilot 2 told investigators he deliberately steered the Algoma Verity outside the channel, to starboard, because he expected the flood current to push the vessel back to port as it approached the bend – using the river's own current to make the turn, rather than fighting it with rudder alone. As the ship approached the bridge, he said, it was “in the position I wanted to be in.”

It never got pushed back. The current's effect on the ship was weaker than the pilot expected, and the vessel kept drifting further outside the channel – 140 feet out, then 200 feet, then 290 feet – despite a stream of rudder orders (starboard 10, starboard 20, port 20, port 10, back to starboard 20) that should have been correcting it.

The Warning the Ship Gave Before It Grounded

At 1812:35, with the bow 290 feet outside the channel, the ship's speed began to slow and the pilot heard a “rumble.” The Master and Third Officer both felt a “jerk.” The pilot asked if there was an engine problem; the Master confirmed the engine was still running. Ninety seconds later, at 1813:53, the pilot himself said: “We may have some problems here.” The Master replied: “We are out of the channel.” The pilot's response: “Yeah, but where it shouldn't be that bad.” At 1814:26, the ship's forward progress stopped entirely. The Master said: “ … aground.”

Refloated, Repositioned, Grounded Again

A tug pushed the bow off, the pilot worked the ship back toward the channel, and by 1822:53 the vessel was moving again at 4 knots, roughly parallel to but still 250 feet outside the channel. The Master began repeatedly voicing concern about the ship's position. Each time, the pilot told him it was going to return to the channel. At 1826:59, the Master pointed out that the channel's own marker buoy was “fine on the starboard bow” – a specific, checkable fact contradicting the pilot's read of the situation. The pilot's answer: “We're going to be fine.”

Three minutes later, at 1828:12, the crew heard air escaping from the bilge tank vents. The ship's speed continued dropping despite rudder and engine orders. At 1829:00, the Algoma Verity came to a stop, hard aground for the second time – and according to the Master, he had been about to take the conn from the pilot at that exact moment. Four ballast tanks and a fuel tank on the starboard side, all empty during the transit, flooded through ruptured bottom plating. The ship listed to starboard and stayed there for three days.

NTSB's Finding

NTSB determined the probable cause was the pilot maneuvering the vessel outside the channel into shallow water, "likely due to expectation bias that the current and the vessel's maneuvering characteristics would have more impact on the bulker's movement" than they actually did. The report's own lessons-learned section is direct: expectation bias occurs when a person responds consistently with what they expect rather than what is actually happening, and the countermeasures are active questioning of the operational environment, recognising conflicting cues, and clear, unambiguous communication – the core components of bridge resource management.

Recommended Actions

Per NTSB's lessons-learned findings:

  1. Actively question, don't just monitor. Training that reinforces active questioning of what's actually happening – not passive confirmation that a plan is still on track – is the direct countermeasure to expectation bias.
  2. Treat conflicting cues as information, not noise. A rumble, a jerk, a buoy visibly out of position – each of these was a specific, checkable signal that contradicted the pilot's expectation. None of them changed the plan until it was too late.
  3. Establish a shared mental model before and during the maneuver. Good bridge resource management means the pilot and bridge team openly share information both before and throughout the transit, so a deviation from the plan gets discussed, not just individually noticed.
  4. A Master's repeated, specific concern is an escalation, not a comment. The Master raised the same concern four times, with increasingly specific evidence. Under the ISM Code and standard BRM practice, the Master retains ultimate authority to intervene – and did not, until the exact moment the ship grounded a second time.

Human Element Analysis

Expectation Bias

The pilot expected the flood current to push the ship to port as it rounded the bend. When the ship kept drifting the wrong way instead, the information that reached him – a rumble, a jerk, a slowing speed – got interpreted through that existing expectation rather than treated as evidence the plan wasn't working. “It shouldn't be that bad” is the sound of a mental model resisting correction in real time.

Bridge Resource Management (Communication)

The Master raised the same concern four separate times – using increasingly specific, checkable evidence (the buoy's bearing, the vessel's vibration, its position relative to the channel) – and each time received a reassurance rather than a change in plan. The information was shared; it just wasn't acted on. A shared mental model requires the deviation to actually change what happens next, not just be acknowledged.

Deference to Authority

The Master was, by his own account, about to take the conn from the pilot at the exact moment of the second grounding. Under maritime convention the pilot advises and the Master retains ultimate command authority – but that authority is only a safeguard if it's exercised before the outcome is already determined, not after.

Cross-Industry Parallels

IndustryIncidentThe parallel
AviationBritish Midland Flight 92, Kegworth, UK, 1989The flight crew shut down the wrong engine, based on their expectation from experience with an earlier aircraft variant’s systems – not the instrument evidence actually in front of them on this variant.
NuclearThree Mile Island partial meltdown, USA, 1979Operators read an indicator light as confirming a valve was closed – matching their expectation – when it only showed that a close command had been sent, masking an actual loss of reactor coolant for hours.
OffshoreDeepwater Horizon, Gulf of Mexico, 2010The crew interpreted an ambiguous negative-pressure test as a pass, consistent with what they expected and wanted, despite contradictory readings that a more skeptical read would have caught.

Try It Yourself

Same waterway, same pressure, your call at each point the Master or pilot had to decide: hold the plan, or act on what you're actually seeing. Play the Algoma Verity decision simulator and see whether you'd have taken the conn sooner.

Test Your Knowledge

Think you'd have caught it? Put it to the test in Crew Connect's free Knowledge Checker — try a quick navigation round and see how you score.

Related Reading

What Would You Do?

This report has been turned into rank-tagged "what if" questions in Crew Connect's free Knowledge Checker. Create a free profile to test your judgement against this scenario.

Create Free Profile & Try Incident Case Review

Could You Have Prevented It?

Test your judgement in Crew Connect's Decision Simulator — real incident patterns, real consequences, free to try.

Try the Decision Simulator Free →

Ready to advance your maritime career?

Free verified profile. Certificate tracking. Get found directly by shipping companies — no crewing agent, no placement fees.

Create Free Profile — 60 Seconds

Browse maritime jobs by rank & sector

Chief Officer Jobs DP Operator Jobs Chief Engineer Jobs Offshore Crew Jobs Superyacht Crew Jobs Wind Farm CTV Jobs Jobs for Filipino Seafarers Jobs for UK Seafarers