ECDIS Safety Parameters
Most ECDIS-assisted groundings share an uncomfortable feature: the equipment worked exactly as configured. The alarm did not sound because the safety contour was set to a value that made the hazard invisible, or because the check scale was wrong, or because the officer had muted the look-ahead alarm after hundreds of nuisance activations in confined water. ECDIS does not run ships aground; parameters chosen by people do. Accident investigation reports — the Ovit grounding on the Varne Bank among the better-known — repeatedly find safety settings that were never adjusted from defaults, never understood, or set once at handover and inherited blindly by every subsequent watchkeeper. This article explains the parameters that actually control what the ECDIS warns you about: the safety contour and how it differs from safety depth, the shallow and deep contours that frame the picture, and the cross-track distance and look-ahead settings that define the safety frame around your planned route. It covers the alarm fatigue problem honestly — an ECDIS that cries wolf on every leg teaches watchkeepers to silence it, and the fix is better settings and better route checking. It lists the setup errors found in audits: default values never changed, safety contour shallower than the ship's draft logic requires, unchecked route legs, and scale mismatches between planning and monitoring views. Written for second officers who plan routes and senior officers who verify them, this is the configuration conversation your bridge team needs before the next pilotage, not after the next investigation.
ECDIS has not eliminated groundings; it has changed their flavour. The modern pattern is a ship in full control of her navigation, with a functioning ECDIS, running aground because the safety parameters told the machine that the danger was not a danger. The settings are the seamanship now.
Safety contour versus safety depth
These two are confused constantly, and the confusion matters:
- Safety contour is the chart contour the ECDIS uses to divide the display into safe and unsafe water for your ship. Water on your side of it is drawn as safe; across it, unsafe. The anti-grounding look-ahead function alarms when your safety frame crosses this contour. It is derived from your draft, required under-keel clearance, and allowance for squat, sea state, and chart uncertainty.
- Safety depth controls which individual soundings are displayed in bold. Soundings shallower than the safety depth are emphasised as hazards. It does not drive the grounding alarm — the contour does.
- Shallow and deep contours frame the display shading (the two or four shade depth bands). They make the picture readable but, again, are not the alarm logic.
The classic error is a safety contour set shallower than the ship's own UKC calculation justifies — sometimes the manufacturer's default, never touched since commissioning. The ECDIS then cheerfully shows safe water over depths the ship cannot safely cross, and the look-ahead alarm stays silent all the way to the bank. Your safety contour value must come out of the bridge procedures manual UKC policy, be recalculated when draft changes, and be verified at every watch handover.
Alarms: set them to mean something
Alarm fatigue is the quiet killer in ECDIS operations. A route checked with an oversized cross-track distance or a look-ahead sector that sweeps the whole anchorage will alarm constantly in confined or congested water. Watchkeepers respond rationally: they acknowledge without reading, mute, or reduce settings informally. The fix is configuration, not exhortation:
- Cross-track distance (XTD) should reflect the water you are in — wider in open sea, narrower where the charted corridor allows, and set deliberately per leg or per area in the route plan, not one number for the whole voyage.
- Look-ahead time or distance should be long enough to act on an alarm and short enough not to alarm on traffic, charted features, and distant legs you will never follow. An alarm that fires hourly for no reason will be disabled within a week.
- Every alarm acknowledged is read aloud and logged — make that the bridge standard, so that silencing without reading is visible behaviour, not private habit.
Route checking and scale discipline
The route check function only examines the route against the safety parameters active at the time of checking, on the chart scale being used. Two audit findings recur: routes checked once at planning and never re-checked after parameters changed, and plans made on small-scale charts where dangers are not displayed, so the check passes a leg that a larger scale would fail. Discipline: plan and check on the best scale available for each leg, re-run the check after any change to draft, UKC policy, or settings, and have a second officer verify the plan against the parameters, not just the line.
The grounding pattern to avoid
Read a few investigation reports and the same anatomy appears: inherited settings nobody owned, a safety contour divorced from the ship's UKC calculation, alarms muted in confined water and never restored, and a watchkeeper monitoring a display whose parameters they never set and never questioned. At handover, the safety contour, safety depth, XTD, and alarm status should be stated out loud as part of the watch handover, the same way course and speed are. If the relieving officer cannot say what the safety contour is set to and why, the handover is not finished. ECDIS will do exactly what you tell it — which is why the telling is the job.