Man Overboard, Spill or Storm: One Emergency Matrix for Port Areas

Why three emergencies should share one operating system

When an incident actually happens in a port, nobody opens a binder — people act on memory, habit and whoever raises their voice first. A person falling from a berth, a failing bunker line and a forecast storm surge each sit in a different document, yet all three demand the same underlying capabilities: a way to detect what happened, someone to declare it, one coordinator who owns the decision, a notification list that is already agreed, resources that can be moved, and a log of everything done. Keeping these functions fragmented is why plans look good on paper but real responses fall apart.

The answer is to think in a matrix rather than in separate files: the columns are the hazards — man overboard, pollution, storm — and the rows are common command functions. International practice already leans this way. Under the ISPS Code and SOLAS, port facilities are expected to rehearse drills, hold contingency plans that keep operations moving through an emergency and coordinate with security and marine agencies; IMO-supported training programmes run full-day simulations that test whole response chains and stakeholder coordination rather than single-department checklists.

The natural rows of the matrix are: detection and raising the alarm; declaring the event and its level; naming a single command point; running the notification tree and regulator contact; staging resources; executing the action sequence; and recording with handover.

The spine both sides of the fender: command, notification, records

The core of the matrix is a single port crisis or coordination cell that activates for all three events. Inside it, a leader and deputies are named for each shift in advance, so nobody at three in the morning has to argue about who owns the decision. The storm-surge operation of the port of Hamburg shows the value of structure: a dedicated port authority cell takes technical and organisational decisions, while a warning service (WADI) issues forecasts roughly eight to nine hours before the expected peak — lead time is bought with a clear command structure, not with individual heroics.

The second pillar is the notification tree, identical in logic for all three scenarios and differing only in addressees and deadlines. For a man overboard, medical and rescue services are called within minutes. For a spill, the regulator and the response organisation are notified within the mandated window and the time of the call is logged. For a storm, warnings go out in advance by forecast — to berth operators, tenants, residents and emergency services, zone by zone. Contact lists must live on an up-to-date wall chart and in phones, not in an outdated annex.

The third pillar is disciplined recording. One log with timestamps — when the event was detected, who was declared coordinator, who was notified, what resources deployed, what was done and to whom command passed — is the single source of truth for the debrief, for inspections and for revising the matrix. Anything not logged is treated as not done.

Man overboard — the case counted in minutes

Inside a port basin the man-overboard problem is compressed. Berths, moored ships, tugs and jetties mean a person falls close to infrastructure yet is often hidden behind hulls and fenders, while currents and propeller wash complicate recovery. The response is choreographed: the witness shouts, throws a buoyant ring with a self-igniting light and never stops pointing; the bridge presses the man-overboard marker, sounds the alarm, posts lookouts and begins a recovery turn — Williamson, Anderson or Scharnow depending on visibility and on when the fall was noticed.

The regulatory floor is explicit. SOLAS requires regular man-overboard drills, at least monthly, and ships must carry plans and procedures to recover persons from the water, including someone from another vessel. Equipment must be ready: lifebuoy with light and smoke, a bridge position marker, a davit-launched rescue boat and a horizontal recovery device. The reason for horizontal lifting is physiology: a hypothermic casualty raised vertically can suffer circum-rescue collapse, a fatal drop in blood pressure and cardiac output, so recovery is done flat, handled gently, dried, warmed and followed by a radio request for medical advice.

In port there is a shore-side half to the sequence. Quayside staff must raise the alarm on the pilot and vessel-traffic channel, the coordinator must clear the lane of other traffic, and the same notification tree that flags a spill must flag a person in the water to medical and rescue services. Because the outcome is decided in minutes, the matrix must assign in advance who calls whom and who launches which boat, rather than leave it to improvisation under panic.

Oil spill — the case with an expanding footprint

An oil spill is rarely an instant catastrophe; it is a footprint that grows with current, wind and the delay before containment. The first minutes still matter — shut the source, stop pumping, close valves, lay absorbents and deploy containment boom around the discharge — but the real race is against the slick moving toward sensitive berths, water intakes and the harbour entrance.

The legal frame is layered. Under Annex I of MARPOL, oil tankers of 150 gross tonnage and above and other ships of 400 gross tonnage and above must carry an approved shipboard oil pollution emergency plan covering the reporting procedure, the authorities to contact, immediate actions to control or reduce the discharge, and how to coordinate with national and local authorities. In states party to the OPRC convention, ports typically keep their own contingency plans and stockpiles — boom, skimmers, dispersant — and name the authority to be notified of a discharge.

For the matrix, the decisive point is that the notification tree matters more than the volume of equipment, because regulators impose deadlines and response organisations must be mobilised in hours. Decide in advance at what spill volume external oil-spill removal organisations are called, who is named on-scene coordinator, and where recovered oil and contaminated waste go for storage and disposal. Different jurisdictions layer their own reporting windows and drill intervals on top of the international frame; confirm the current national requirements before locking your matrix.

Storm and storm surge — the forecastable case

A storm or storm surge is the hazard with the most lead time and the whole territory in scope. Where a man overboard is decided in minutes and a spill in hours, a storm arrives on forecasts available a day or more ahead — and the characteristic failure is doing nothing because the weather has not yet struck. The cure is pre-agreed thresholds rather than decisions made under pressure.

Concrete limits show the method. The port of Dover stops ship movements when sustained wind inside the harbour exceeds about 40 knots, recommends vacating its most exposed berths at about 45 knots, and closes the port entirely from certain directions at about 55 knots (force 11); its tugs have a practical swell limit near 1.5 metres and movements are restricted below roughly 500 metres visibility, while bunkering above about 25 knots proceeds only after assessment. These numbers are specific to berths and wind directions — the lesson is that each port derives its own thresholds from its layout, not that Dover's figures transfer everywhere.

Storm-surge practice in the port of Hamburg is the reference for staged decision-making. A water level above 4.5 metres above sea level counts as a severe surge; the warning service issues forecasts up to about nine hours ahead; roads and zones close in steps — partial closure and evacuation from around +5 metres, full evacuation of the inner zone at +5.5 to +6.5 metres and closure of the whole port at +6.5 metres — and only certified emergency staff with identification remain on site. The precautionary principle rules: sail or secure vessels, lash cranes and cargo, suspend bunkering and move people out before conditions make exit impossible.

Turning the matrix into muscle memory: thresholds, drills, learning

A matrix proves itself only in exercises. Even where no single rule covers every hazard, the international frame already sets a rhythm — SOLAS man-overboard drills at least monthly and port spill drills under OPRC-derived national schemes. The test is not whether the paper is correct but who actually arrives, what actually starts and where the delays are.

Design scenarios that combine hazards — a man overboard during a turn as a storm approaches, or a spill in poor visibility — because real emergencies do not arrive one at a time. After every drill and every real event, run a structured debrief: what completed within the agreed time, which thresholds were unrealistic, which contacts had changed. Exercise logs with timestamps are the same instrument as the live incident log; fold updated thresholds and lists into the matrix before the next cycle rather than when someone gets around to it.

Scope and jurisdiction matter. This article is general operational guidance, not professional or legal advice: the examples (Dover wind limits, Hamburg surge levels) illustrate method and are tied to specific ports and directions. International instruments such as SOLAS, MARPOL, the ISPS Code and the OPRC convention are layered with national rules, so confirm current thresholds, reporting windows and drill requirements with your regulator before implementing the matrix.

• Re-verify notification phone numbers every month and after every roster change.
• Re-derive wind, visibility and surge thresholds at least once a year against observed conditions.
• Rotate drill scenarios and include night and degraded-visibility variants.
• Log the timestamp of every step in one journal and compare it against the target time.