All Sectors

The Chart Had a Gap, and So Did the Passage Plan: The Meshka Grounding

🕑 5 min read words Safety • Incident

Vessel: Meshka (bulk carrier, in ballast)
Date & location: 31 May 2025, the Öresund, off Landskrona, Sweden — Tarragona to Vysotsk passage
Outcome: Grounded in 3m of water (7m draft). Refloated 7 June, no substantial damage, no pollution
Human factors: Normalisation · Situational Awareness · Communication (office-to-ship)
Source: SHK 2026:10e, published 15 June 2026

7 decision points2 outcome paths — catch the drift / miss it~8 min read + Knowledge Checker

First Transit, Missing Chart Cells, Three Metres of Water

On 31 May 2025, the bulk carrier Meshka was in ballast, southbound through the Öresund on a passage from Tarragona, Spain, to Vysotsk, Russia. The Sound is narrow, busy, and unforgiving of small navigation errors. It was the first time this vessel, and this crew, had transited it. Just before 10:00, the Swedish Maritime Administration's traffic centre noticed Meshka drifting outside the designated shipping lane and issued a warning. The ship continued off-course and grounded in water only three metres deep — on a vessel with a seven-metre draft.

What SHK Found

The investigation traced the grounding to inadequate voyage planning, compounded by a specific and avoidable gap: the vessel's ECDIS lacked detailed chart cells for the Öresund. That alone should have been caught during passage planning or chart ordering. It wasn't. Investigators also found insufficient crew knowledge of the ECDIS system's limitations, poor adherence to navigation procedures, and deficient bridge teamwork — meaning even as the vessel began drifting off track, no one on the bridge caught it in time. SOUNDREP, the Sound's ship reporting system, did try to intervene, but the warning came too late to prevent the grounding.

Behind the immediate navigational failure, SHK identified underlying causes in the company's implementation of its Safety Management System, and shortcomings in how charts were ordered in the first place. This wasn't a single bridge team having a bad morning — it was a chain that started in the office, with what got put on board before the vessel ever left port.

The Cost — and What Was Avoided

Meshka was refloated on 7 June after ballast discharge and towing, with no substantial damage to the vessel and no pollution detected, despite carrying roughly 938,000 litres of oil in its fuel and lubricating tanks. It was, in the end, a grounding without a disaster attached to it. That outcome depended on shallow, forgiving ground and a fast, well-executed salvage — not on anything the bridge team did right.

Recommended Actions

SHK directed recommendations at four separate parties — reflecting a causal chain that ran well beyond the bridge:

Shipping company (Makareb Shipmanagement DMCC): strengthen crew training on ECDIS limitations and reinforce the chart selection and ordering procedure ahead of unfamiliar passages
ECDIS manufacturer (Danelec): review how system limitations and chart coverage gaps are surfaced to the user, rather than assumed understood
Chart provider (Elcome): review chart cell selection and delivery procedures for narrow, high-traffic waters like the Öresund
Swedish Transport Agency: review whether existing international regulation adequately addresses chart coverage verification before a first transit of a narrow strait

Human Element Analysis

Normalisation

A first transit is, almost by definition, unfamiliar — yet the passage plan and watchkeeping that day proceeded as though it were routine. SHK's finding of “poor adherence to navigation procedures” on a route this vessel and crew had never sailed suggests the extra scrutiny a first transit demands wasn't actually applied.

Situational Awareness

The bridge team did not catch the vessel drifting outside the shipping lane before an external party — the Sound's own traffic centre — did. Whatever cross-checking was happening on the bridge wasn't independent enough to catch a developing track deviation before it became a grounding.

Communication (Office to Ship)

SHK's underlying causes point to the chart ordering process and the company's SMS implementation — decisions made ashore, before the voyage began, that left a gap the bridge team then had to work around without knowing it existed. The failure travelled from the office to the chart table without anyone flagging it in between.

How This Pattern Repeats

Industry	Incident	The parallel
Aviation	Korean Air Flight 801, Guam, 1997	Crew relied on a glideslope system that was out of service, on an unfamiliar approach, without independently cross-checking their actual position — a system limitation combined with insufficient scrutiny on unfamiliar ground.
Space	Mars Climate Orbiter, 1999	A unit-conversion error between two teams (metric and imperial) was never caught before it reached the spacecraft — a data gap introduced upstream, similar to a chart-ordering gap that reaches the bridge only once it's too late to matter.
Rail	Santiago de Compostela derailment, Spain, 2013	A driver approaching a known high-risk curve outside the territory of the train's automatic protection system didn't reduce speed in time — unfamiliar or unprotected ground catching out an otherwise experienced operator.

See How You'd Handle It

The scenario opens with the passage plan for a first transit of a narrow strait: what do you specifically verify about ECDIS chart coverage before departure? Seven decision points follow the bridge team through the transit, ending at the moment the vessel begins to drift off track.

What This Means for Any Bridge Team on an Unfamiliar Passage

Chart coverage is not something to assume — verify ECDIS chart cells cover the full intended route, in detail, before departure, especially in narrow or high-traffic waters
A first transit of any strait, sound, or narrow channel is exactly when passage planning needs the most scrutiny, not the least
Know your ECDIS's specific limitations — a system that looks fully functional can still be missing the detail that matters most in confined waters
Bridge teamwork means someone is independently cross-checking the vessel's actual track against the planned one — not just monitoring the same display the OOW is watching
An external warning, like a traffic centre call, is a last line of defence, not a first one — by the time it arrives, options are already narrowing