The master first stabilizes the situation

The first duty is safe command, not perfect classification. The master or officer in charge should establish what is happening, place the vessel in the safest practicable condition and activate the relevant shipboard response.

Immediate priorities can include:

- maintaining navigational control and avoiding secondary collision or grounding; - sounding the appropriate alarm under the ship’s plan; - moving personnel from exposed areas; - assessing injuries, fire, flooding, pollution and propulsion; - increasing watertight integrity and damage-control readiness; - monitoring the threat by visual and radar means; - preserving safe communications; and - preparing to manoeuvre where lawful and safe.

Actions must fit the threat. A suspected boarding requires different movement and crew protection from a missile impact, GNSS deception or suspicious package. The plan should prevent a familiar piracy checklist from being applied automatically to every Gulf incident.

The master retains professional judgment. IMO’s ISPS explanation states that the master should not be constrained by the company, charterer or another person in decisions necessary to maintain ship security.

Distinguish distress from a covert security alert

The SSAS sends a covert ship-to-shore alert indicating that security is threatened or compromised. IMO performance standards say it should not raise an alarm aboard or alert nearby ships. Its procedures and activation points are specified in the approved ship security plan.

SSAS does not replace every distress or urgency communication. If people need rescue, the ship is on fire, collision risk is immediate or pollution response is required, GMDSS and nearby-authority communications may also be necessary under the applicable emergency procedures.

The team must know which system it is using and why. A covert alert may be appropriate during an attempted seizure when an audible onboard alarm could worsen danger. A Mayday may be essential after a disabling strike with lives at risk. The master should follow the plan and actual circumstances.

The company should test SSAS and emergency communications before entering the risk area, while protecting sensitive activation details. A system not understood by the watch team cannot be relied on under pressure.

Send a minimum viable incident report

A first report should be accurate enough to support assistance and warning, even if cause and attribution remain unknown.

The minimum information is:

1. ship name, IMO number, flag and call sign where required; 2. UTC event and report times; 3. independently verified position where possible; 4. course, speed and navigation status; 5. observable event and direction of threat; 6. known damage, casualties, fire or pollution; 7. action being taken; 8. assistance required; and 9. reliable contact channel.

If GNSS interference is suspected, the report should state how position was verified or label it approximate. If no crew check is complete, use “casualty status being verified” rather than “all safe.”

UKMTO’s form specifically requests UTC, position, course, speed and a brief description for suspicious activity. It also invites imagery where possible. Imagery should never distract the bridge, expose crew or delay an urgent call.

Language should separate fact from assessment. “Explosion heard on port side; smoke visible; cause unknown” is more useful than an unsupported attribution.

Use one communication coordinator

An incident can generate simultaneous calls from the company, security adviser, charterer, insurer, agent and authorities. The bridge cannot safely answer them all.

The master should assign one person or shore contact to manage external information where staffing permits. The bridge sends the verified operational report to the designated authority channels and company. The company security officer then coordinates internal escalation and commercial notification.

IMO guidance says vessel operators should implement procedures for reporting and recording security incidents. It also advises a master at sea to alert the nearest coastal State or authorities and, where appropriate, vessels nearby while activating the response.

US-flagged ships should follow the current MARAD contact sequence and their approved plans. Other ships must use their flag and company arrangements. Contact lists should be current and available offline because internet or satellite service may be degraded.

Closed-loop communication matters. The ship should know which authority received the report and whether instructions are advisory, mandatory or still being authenticated.

Protect the bridge from shore-side overload

The first company response should be: “Report received; continue emergency actions; next update at the agreed time unless conditions change.” It should not be a stream of speculative questions.

Shore teams can perform tasks that do not require bridge attention:

- notify the flag State and designated security recipient; - confirm UKMTO or naval coordination receipt; - review nearby warnings and route hazards; - alert emergency response, medical or salvage support; - preserve insurer and legal notification deadlines; - prepare a fleet warning using verified facts; and - establish a controlled information log.

Charterers and brokers should receive an operational holding message through the designated commercial contact. Direct calls to the master can distract from navigation and produce inconsistent accounts.

No public statement should name an attacker, weapon or casualty count before verification. The company can acknowledge an incident and state that assessment is continuing.

Preserve evidence without delaying safety action

Evidence supports investigation, insurance and lessons learned, but life safety comes first.

Where practicable, the crew should retain VDR data, radar and ECDIS screenshots, AIS and communications logs, CCTV, photographs, alarm histories, machinery readings and the exact wording of hails. Original files should be protected from alteration with times and custodians recorded.

The bridge should not change course merely to improve a photograph or send crew into exposed areas to inspect damage. A safe copy of electronic records can follow once the vessel is stable.

The incident log should record when each fact became known. Later corrections should supplement, not overwrite, the original entry. This distinguishes a reasonable initial decision from hindsight.

Sensitive security-plan details should not be attached to broad email chains. Evidence distribution needs access control.

Warn the fleet with a controlled message

Nearby company ships may need immediate warning before the incident is fully confirmed. The alert should state the source, UTC, location, observable event, current verification status and required action.

A useful first fleet alert might read: “Master report received at 1022 UTC of an explosion at the stated position. Damage assessment ongoing; cause and attribution unknown. Ships within the defined review area are to check current authority warnings, increase readiness and contact the company before committing to transit.”

That communicates urgency without inventing facts. It also gives a review boundary and action.

UKMTO warnings are designed to alert masters and company security officers to incidents in the voluntary reporting area. Companies should link to the official product when issued, then correct or close their internal alert visibly as information changes.

Fleet messages should not include sensitive routes, crew names or unverified casualty details beyond operational need.

Connect the first report to commercial controls

A prompt notice can protect insurance and contractual positions, but it should not concede causation, fault or coverage.

Owners should check war, hull, P&I, kidnap, pollution and loss-of-hire reporting obligations. Charterers may need notice under employment, war-risk, deviation or cargo clauses. Each depends on wording and facts.

The first commercial estimate should be labeled preliminary. Time lost, fuel, repair, salvage, cargo damage and port consequences may be unknown. Brokers and traders should not treat a public AIS stop or forwarded message as confirmation of total loss.

ZeaClub can preload contact roles, required fields and approved holding messages. It can time-stamp updates, prevent conflicting versions and route commercial questions away from the bridge. It cannot decide whether to transmit distress, activate SSAS or manoeuvre the ship.

Commercial conclusion

The first 15 minutes should produce control, protection and a reliable information channel, not a complete investigation.

The master stabilizes the ship and people. The designated systems alert authorities. A concise factual report gives position, event, condition and assistance needs. Shore teams absorb communications, warn the fleet and preserve commercial rights without overwhelming the bridge.

The best preparation is a drilled sequence with current contacts, tested equipment and prewritten fields. When the real event arrives, disciplined brevity is safer than a flood of uncertain information.

This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.

Sources