All Sectors

MV WAKASHIO — The Twelve Days Between a Grounding and a Disaster

🕑 5 min read words Safety • Incident

Vessel: WAKASHIO, Panama-flagged capesize bulk carrier, 299.95m LOA, 203,000 tonnes deadweight, built 2007
Date & location: Grounded 25 July 2020, Pointe d'Esny reef, south-east coast of Mauritius
Outcome: Approximately 1,000 tonnes of low-sulphur fuel oil spilled into the Indian Ocean; ship broke in two on 15 August. Three crew members later died when the recovery tug Sir Gaëtan Duval sank on 31 August
Human factors: Complacency · Overconfidence · Normalisation of deviation
Source: Panama Maritime Authority investigation report (released 2023); IMO incident briefing

7 decision points4 outcome paths~7 min read + Knowledge Checker

Six Years Ago Today

On 25 July 2020 — six years to the day before this article was published — the capesize bulk carrier WAKASHIO grounded on a coral reef off Pointe d'Esny, Mauritius, roughly 900 metres from shore. She was in ballast, en route to Brazil, carrying no cargo but 3,894 tonnes of low-sulphur fuel oil, 207 tonnes of diesel and 90 tonnes of lubricant oil in her bunkers.

The grounding itself didn't spill a drop. What happened in the twelve days that followed is the part of this story worth sitting with.

What Actually Caused the Grounding

Panama Maritime Authority's investigation, released three years after the incident, concluded the grounding was “most probably a result of human factor” — and didn't soften what that meant in practice. On the night of the grounding, the Master had attended a crew birthday party and consumed four alcoholic drinks — two whiskies at the party, two more once back on the bridge. He deliberately sailed the ship close to the Mauritius coast specifically to get a mobile phone signal, entering the country's territorial waters without notifying local authorities. The Chief Officer was preoccupied with the same goal — accessing mobile internet — rather than maintaining proper navigational watch. A Cadet Officer was allowed to skip lookout duty to stay at the party. When the ship was 1.5 miles from shore and closing, the Master still hadn't assumed command as required.

The investigation also flagged an absence of large-scale charts on board and over-reliance on an over-zoomed electronic chart display — a navigational picture that looked fine at the zoom level the bridge team had it set to, and wasn't.

The Window That Mattered Most

Here is the detail that gets lost in most retellings: WAKASHIO grounded on 25 July. Oil did not begin leaking from her hull until 6 August — twelve days later. For most of that window, the ship sat on the reef with her fuel still contained, and the question was never really “will she spill” so much as “how much of this is still preventable.”

It wasn't prevented, and the reasons why sit squarely outside the ship herself. Mauritius's national oil spill contingency plan was, by the time it was actually needed, nearly two decades out of date. The National Coast Guard had the vessel visible on radar during her approach and didn't flag the danger. Once the leak began, coordination between authorities was slow and, at points, contradictory — mitigation efforts were delayed by disagreement, not just by circumstance. By 10 August, an estimated 1,000 tonnes had spilled, the slick covered 27 square kilometres, and 5-metre waves had halted cleanup entirely.

Local fishermen, divers and NGOs built floating containment barriers from cloth stuffed with straw and human hair — a genuinely improvised response while formal mechanisms caught up. India, France (via Réunion) and Japan all sent personnel and equipment. On 15 August the ship broke in two. On 31 August, during recovery operations, the tug Sir Gaëtan Duval sank, killing three crew.

What This Means for a SOPEP That Actually Works

Every ship above the MARPOL Annex I Regulation 37 threshold carries a Shipboard Oil Pollution Emergency Plan. WAKASHIO's story isn't a case of the plan failing on board — it's a case of the shoreside half of the response (coastal state contingency planning, inter-agency coordination, the currency of a national plan) mattering just as much as anything the crew does, and being just as capable of failing. A Master's own SOPEP response can be executed perfectly and still run into a coastal state response that's two decades stale.

Human Element Analysis

Normalisation of deviation

Sailing close to shore for a phone signal wasn't a one-time lapse invented that night — it reads as a habit that had never previously produced a consequence, right up until it did. Each previous close pass that didn't end in a grounding made the next one feel a little more like standard practice.

The gap between grounding and disaster is where the real decisions live

Twelve days sat between the grounding and the first leak. The story that gets told is usually just “the ship grounded, then it spilled” — collapsing a real, actionable window into a single inevitable event. It wasn't inevitable. It was a sequence of separate decisions and failures, most of them made ashore, not aboard.

Cross-Industry Parallels

IndustryIncidentThe parallel
NuclearFukushima Daiichi (2011)An outdated risk assessment (tsunami wall height based on historical, not current, hazard modelling) left a real response window under-resourced when the actual event arrived — the same shape of failure as a 20-year-stale national oil spill contingency plan.
AviationAlcohol/fitness-for-duty regulation generallyAviation's zero-tolerance bridge/cockpit alcohol rules exist precisely because of cases like this one — a Master's blood alcohol level factoring directly into a grounding is the exact scenario aviation's rest/fitness rules were hardened to prevent.
RailSouthall rail crash (1997, UK)A driver distracted by an unrelated task (in that case, packing a bag) missed a critical signal — directly analogous to a bridge team preoccupied with phone signal instead of navigation.

Try the Decision Simulator

You're the Chief Officer on watch, and the Master has just suggested altering course closer to shore. Play through the real decision points and see which ending you land on.

Test Your Knowledge

Think you've got this covered? Put it to the test in Crew Connect's free Knowledge Checker — try a quick MARPOL 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