Mayday communicates distress
IMO’s Standard Marine Communication Phrases use Mayday to announce a distress message. The standard structure identifies the vessel, position, nature of distress, assistance required and other information that may facilitate rescue.
After a strike, Mayday may be appropriate where the ship is on fire, flooding, sinking, disabled in immediate navigational danger, abandoning, or where people require urgent rescue. The threshold depends on the casualty, not on whether the attacker or weapon has been identified.
Verified example: UKMTO Warning 191-26 reported that a merchant-vessel master relayed a Mayday stating another vessel had been struck by an unknown projectile in the Strait of Hormuz on 1 November 2026. The public warning does not provide the casualty’s complete condition, but it demonstrates how distress traffic can become the first regional indication of an attack.
A Mayday message should state observable danger. “Engine-room fire after explosion, propulsion lost, 22 persons aboard, require immediate firefighting and towing assistance” gives rescuers more than an unsupported attribution.
Pan-Pan communicates urgency
ITU describes Pan-Pan as the urgency signal for a very urgent message concerning the safety of a mobile unit or person. It ranks below distress but above routine traffic.
Pan-Pan may be appropriate when the ship has sustained damage or lost capability and needs assistance, yet the master does not assess grave and imminent danger. Examples could include a controlled fire, propulsion defect with adequate sea room, or a medical need that is urgent but not presently life-threatening.
This is not a checklist substitute for judgment. A drifting tanker near traffic and shoal water may move rapidly from urgency to distress. A contained fire may reignite. The bridge should set explicit escalation triggers and continuously reassess.
The IMO examples include an urgency message from a vessel that has collided and needs a tug. The message still needs identity, position and a clear description of the urgent problem.
SSAS is covert and goes ashore
SSAS alerts a designated shore authority that the ship’s security is threatened or compromised. It is designed not to sound an onboard alarm or notify surrounding ships.
Current Hormuz industry guidance advises activation of SSAS and notification of UKMTO for attack, incident or suspicious activity. That security chain complements GMDSS.
A covert alert cannot request immediate help from a nearby merchant vessel in the way distress traffic can. Conversely, open Mayday traffic may be unsafe during a hostile boarding because it can reveal the crew’s actions. The ship security plan and circumstances guide the combination.
The bridge team should know that pressing SSAS does not complete its radio duties.
UKMTO reporting builds the regional picture
UKMTO warnings inform other vessels and authorities about attacks, boardings and suspicious activity. Reporting supports verification and a shared threat picture, but UKMTO is not a replacement rescue coordination center.
A company security officer may report while the master manages the casualty. The report should include time, position, crew status, damage, environmental impact and what remains unknown.
The same incident may therefore generate Mayday traffic, SSAS, an RCC exchange, a UKMTO report and company notifications. This is not duplication if responsibilities and messages are coordinated.
A communications log should record which channel carried which purpose, the recipient, acknowledgement and outstanding action.
Put one officer in charge of communications
During fire, blackout or attack, multiple people may transmit conflicting positions and status. If staffing permits, the master should assign one qualified communicator while retaining overall command.
A short communications card can show:
1. distress or urgency threshold; 2. primary and backup GMDSS equipment; 3. current position sources; 4. SSAS procedure; 5. UKMTO, RCC, coastal authority and company contacts; 6. message owner and log keeper; and 7. update and cancellation procedure.
The card must align with approved plans and flag guidance. It should not expose protected SSAS activation details.
If GNSS is unreliable, the message should state how position was obtained and its confidence. A confidently wrong position can misdirect responders.
Update as the casualty changes
The initial category is not permanent. A Pan-Pan should be upgraded if danger becomes grave and imminent. A Mayday can be followed by status updates when fire is controlled, people are rescued or assistance is no longer required.
The master should not cancel distress solely because propulsion has restarted. Hidden fire, structural damage, ordnance or loss of redundancy may remain. Coordinate with the responsible RCC and follow prescribed procedures.
An inadvertent DSC alert requires immediate cancellation through the correct radio process. Calling the company alone does not clear it from the rescue system.
The log should preserve the original alert and every correction. A later downgrade does not mean the original Mayday was unreasonable.
Manage nearby assistance safely
Distress traffic can draw merchant ships toward an active attack area. The casualty and coordinating authority should share enough threat information to prevent rescuers from entering blindly.
A potential assisting master must balance the duty to render assistance with serious danger to that ship and crew. Safe stand-off, relay of communications, recovery from a safer direction or waiting for security coordination may be more effective than an uncontrolled close approach.
Scenario, not a reported event: A tanker with a contained fire may request tug support by Pan-Pan while warning traffic to keep clear. If the fire breaches a fuel boundary and abandonment begins, Mayday becomes appropriate. The security origin has not changed; the casualty threshold has.
Train decisions, not just phrases
Officers need the standard words, but exercises should test changing facts. Begin with an unexplained impact and no damage, add steering loss, then smoke and an injured person. Require the team to select channels, compose messages and update them.
Review whether the message gave position, danger, assistance required and persons aboard. Test satellite and terrestrial backups, DSC follow-up and degraded GNSS.
The company should include shore roles so the CSO does not duplicate or contradict the bridge. Drills must distinguish real equipment tests from live alerts.
ZeaClub can maintain communications matrices, message drafts, acknowledgements and the incident chronology. It cannot transmit distress alerts, receive SSAS or decide the master’s emergency classification.
Commercial conclusion
After a Gulf strike, the correct signal follows the ship’s condition. Mayday is for distress and immediate assistance, Pan-Pan for urgent safety traffic, and Sécurité for navigational or safety information. SSAS and UKMTO reporting address the security chain.
A master may need several channels at once. Clear purpose, observable facts, continuous reassessment and disciplined updates help rescuers act while protecting the crew and the later evidence record.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- IMO Resolution A.918(22), Standard Marine Communication PhrasesAccessed 2026-11-19
- ITU, Emergency and Disaster Relief Special SupplementAccessed 2026-11-19
- IMO Resolution A.474(XII), Proper Use of VHF Channels at SeaAccessed 2026-11-19
- UKMTO Warning 191-26, 1 November 2026Accessed 2026-11-19
- Industry Guidance on the Safe Management of Vessel Transit through the Strait of Hormuz, May 2026Accessed 2026-11-19
- International Maritime Organization, GMDSS circularsAccessed 2026-11-19