What SSAS actually does

Verified fact: IMO describes SSAS as a system designed to raise an alarm ashore in response to a security threat or incident. Activation transmits the ship’s identity, location and an indication that its security is threatened or compromised to a competent authority designated by the flag Administration.

The alert is covert. It should not raise an alarm aboard, notify surrounding ships or directly alert nearby coastal States. IMO performance standards require at least two activation points, including one on the bridge. The flag Administration’s arrangements determine which competent authority initially receives and processes the transmission.

That design distinguishes SSAS from GMDSS distress alerts, Mayday traffic and communications with UKMTO. Those channels solve related but different problems. SSAS tells an authorized shore chain that the ship faces a security threat, particularly where visible communication may endanger the crew or be controlled by an attacker.

Activation is not a substitute for distress traffic

A ship struck by a projectile may simultaneously face security, fire, flooding, collision and medical emergencies. SSAS alone will not tell nearby vessels what assistance is required. Where safe and appropriate, the master may also need GMDSS distress communications, VHF traffic, coastal authority contact, company emergency calls and a UKMTO incident report.

The May 2026 industry guidance for Hormuz advises vessels to activate SSAS and notify UKMTO in the event of attack, incident or suspicious activity. MARAD’s active advisory gives similar direction to U.S.-flagged ships and adds the U.S. Fifth Fleet Battle Watch.

These recommendations do not make every channel interchangeable. A covert alert may be correct during a hostile boarding when open radio traffic would reveal resistance. A Mayday may be essential after an engine-room fire when immediate rescue is needed. The ship security plan and the master’s judgment should coordinate both tracks.

Use ship-specific thresholds

The approved ship security plan should define procedures for SSAS use and protect the location of its activation points. IMO guidance says those procedures are agreed with the Administration and should ideally be individual to the ship. A generic fleet poster cannot replace them.

The company security officer and master should translate the approved plan into simple decision cues without circulating sensitive technical details. Typical cues for immediate consideration include:

- an actual or attempted unauthorized boarding; - coercive diversion or detention by an apparently hostile actor; - a projectile, drone or uncrewed surface craft attack; - a credible bomb, sabotage or seizure threat; - loss of control over the bridge or communications; and - other events that meet the Administration-approved definition of a security threat or compromise.

A suspicious approach may develop too quickly for perfect classification. The relevant question is not whether the crew can prove attribution. It is whether observed conduct, capability, proximity and intent create the threat described by the plan.

Distinguish observation from interpretation

Verified fact: On 16 November 2026, UKMTO reported that a tanker in the Strait of Hormuz was struck by an unknown projectile and suffered an engine-room fire. Its initial public report did not attribute the weapon or attacker.

Operational implication: A crew does not need to solve attribution before taking protective action. It can report “flash and impact on port quarter, fire confirmed” rather than claim a missile, drone or named perpetrator without evidence.

This discipline matters for SSAS follow-up. The automatic alert carries limited data. Subsequent communications should separate direct observations, instrument indications, third-party reports and conclusions. A false narrative created in the first minutes can distort military response, insurance investigation and public reporting.

Scenario, not a reported incident: If a master sees an unidentified aircraft at distance but no hostile behavior, the plan may call for heightened watch and reporting rather than immediate activation. If the aircraft releases an object, repeatedly dives toward the bridge or an explosion occurs, the threshold changes. The decision rests on evidence and the approved procedure, not the label “drone.”

Covert activation requires a practiced shore chain

The technical transmission is only the start. The competent authority and company need a tested protocol to authenticate the alert, locate the vessel, avoid compromising the crew and notify the appropriate coastal State or security authority.

A good response card specifies:

1. the alert recipient and 24-hour backup; 2. the source used to verify current position and voyage; 3. whether and how the ship may be contacted covertly; 4. escalation to the flag Administration, coastal authorities and security centers; 5. company crisis-team roles; 6. family, insurer and charterer notification thresholds; and 7. the authority and method for cancellation.

Calling the bridge immediately and asking, “Did you press SSAS?” may be dangerous if armed personnel are present. Companies need pre-agreed duress phrases, silent checks or alternative channels consistent with flag guidance. No public statement should identify a covert response in progress.

Prevent accidental alerts without creating hesitation

SSAS must be testable, yet a poorly managed test can trigger a real security response. IMO maintains separate guidance on message priority and testing. Tests should follow Administration and service-provider procedures, carry the prescribed test indication, and be coordinated with the receiving authority.

Companies should investigate accidental activations as system events rather than automatically blaming the individual. Possible causes include unclear controls, poor guarding, confusing test procedures, maintenance errors or weak familiarization.

Corrective action may include better controlled instructions, revised drills, equipment service and clearer handover records. It must not disclose activation-point locations to people without a need to know. Nor should fear of discipline make a seafarer hesitate during a genuine threat.

An accidental activation should be cancelled through the approved chain promptly. The original alert and cancellation should remain in the security record, with the cause and corrective action documented.

Train for decision quality, not button memory

Crew familiarization needs to cover the purpose and decision pathway while preserving restricted security information. Relevant officers should understand who may activate, what happens ashore, which other messages are still required and how to behave if normal communications are unsafe.

Tabletop scenarios should vary the evidence:

- an unverified nearby explosion; - an approaching armed skiff; - a projectile impact followed by fire; - a military helicopter directing a diversion; - a crew member discovering suspected sabotage; and - a coercive boarding with communications monitored.

The exercise should ask what is observed, which plan threshold applies, whether covert or open communication is safer, who acts if the master is unavailable, and what follow-up information can be sent. A drill that only asks someone to identify the button does not test the real decision.

Build commercial readiness around the security response

Owners should ensure that the company security officer and alternate can receive and act on an alert at all times. Charterers and brokers do not belong in the initial covert security chain, but they need a controlled notification process when voyage performance, cargo, port arrival or contractual obligations are affected.

Insurers should receive notice in accordance with policy requirements once doing so will not prejudice the response. The company must preserve SSAS transmissions, position data, bridge records, communications and system maintenance evidence for later casualty and claims analysis.

Commercial teams should not delay activation while seeking approval. They also should not demand sensitive plan details as proof that action was taken. A timestamped confirmation from the responsible security officer can protect legitimate contractual interests without exposing restricted information.

Review the response after every activation

The post-incident review should compare the first observed cue with the approved threshold, transmission receipt, shore reaction, parallel distress calls and external notifications. It should identify delay, duplication, unsafe contact attempts and any mismatch between the ship’s equipment and shore database.

The review must distinguish an outcome from the quality of the decision. An alert that proves unnecessary may still have been reasonable on the evidence available. Conversely, a ship that escaped harm despite delayed activation has not demonstrated a sound procedure.

ZeaClub can record the source-stamped incident chronology, decision cues, notification acknowledgements and corrective actions in controlled workflows. It cannot receive SSAS alerts, reveal protected plan details or replace the flag-approved response chain.

Commercial conclusion

SSAS should be activated according to the ship’s approved procedure when security is threatened or compromised, not only after attribution or damage is certain. It is a covert shore alert, not a complete distress response.

The strongest operators connect three things before sailing: clear ship-specific thresholds, a practiced 24-hour shore chain and parallel emergency communications. That preparation lets the crew act quickly during an ambiguous Gulf incident without confusing SSAS with Mayday traffic, public reporting or commercial permission.

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

Sources