A hail can be routine, coercive, mistaken, or deceptive

Merchant ships approaching the Strait of Hormuz can receive calls from naval forces, coastal authorities, vessel traffic services, nearby ships, or unidentified stations. The bridge team cannot assume that every call is hostile, but it also cannot treat every voice on Channel 16 as an authenticated authority.

Active MARAD guidance illustrates the distinction for US-flagged ships. It says they should answer VHF calls from US and coalition navies, which may make maritime-awareness queries or approaches. The same advisory says that if Iranian forces operating over the horizon hail or email a US-flagged vessel with instructions to divert or submit voyage information, the ship should ignore the demand and continue if safe, while updating NAVCENT NCAGS.

That is flag-specific government guidance, not a universal script for every vessel. Other ships must follow their flag, company, coastal-state, and current official instructions. JMIC’s November 15 update said neutral ships could expect monitoring, verification queries, and increased hailing, and warned that vessels might receive directed calls toward the northern Iranian-controlled route.

The operational challenge is to identify the caller, protect safety, avoid unnecessary disclosure, and escalate quickly without blocking distress traffic or surrendering the master’s judgment.

Prepare the communications plan before arrival

A bridge team should not design its response during the first ambiguous call. The voyage risk assessment can identify expected authorities, call signs, reporting centers, working channels, contact numbers, authentication methods where available, and the information the ship is authorized to provide.

Contact details must come from current official sources. The May 2026 industry guidance says established voluntary reporting mechanisms should be used and contact details verified against the latest official publication. The plan should distinguish emergency reporting, routine position reporting, route coordination, naval liaison, company escalation, and port or coastal-state communication.

Roles need to be assigned. One officer handles the radio, another maintains navigation and collision avoidance, and another records the exchange if bridge manning permits. The master and company security officer should have clear escalation thresholds. A call must not distract the entire bridge team during a constrained maneuver.

Standard Marine Communication Phrases and the phonetic alphabet reduce ambiguity. IMO guidance on proper VHF use says Channel 16 should be reserved for distress, urgency, very brief safety communications, and calling before moving to an appropriate working channel. Long arguments or commercial discussions on Channel 16 can obstruct urgent traffic.

The team should rehearse loss of contact, conflicting instructions, language difficulty, interference, and a call coinciding with GNSS anomalies or a suspicious approach.

Authenticate without escalating the encounter

The officer should record the time, channel, claimed identity, call sign, language, signal quality, content, requested action, and ship’s actual position derived from cross-checked navigation. If safe, the officer can request the caller’s identity and repeat the instruction back for confirmation. The bridge should avoid speculation, threats, or unnecessary argument.

Authentication may involve checking the expected call against prior coordination, contacting the recognized authority through a separately verified channel, or consulting the company and reporting center. A telephone number or email supplied by the unknown caller should not be the only verification path.

The response must follow applicable official guidance. A US-flagged vessel should not generalize MARAD’s instruction beyond its actual wording. The advisory distinguishes coalition hails from Iranian over-the-horizon diversion or information demands and conditions continuation on safety. The master still has to avoid collision, comply with lawful obligations, and respond to the immediate navigational situation.

If the caller claims the strait is closed, the statement should be reported and checked. A February UKMTO advisory said reported VHF broadcasts claiming closure could not then be independently verified and did not by themselves constitute a legally binding closure. That historical notice shows why a radio claim must be separated from verified legal and operational facts. It does not establish the status on a later date.

Protect voyage information and preserve evidence

A ship may legitimately need to provide identity, position, course, destination, cargo or documentation to an authorized body under applicable rules or a coordination arrangement. The communications plan should state what can be released, by whom, and through which channel. Over-disclosure to an unverified caller can increase security exposure.

Email presents similar risks. Sender addresses can be imitated, attachments can contain malware, and a message can quote real vessel details without being authentic. Route changes should never rest solely on an unexpected email. The company should verify the sender using known contact data and preserve the original message with headers for security review.

Evidence should include the radio log, bridge log, audio recording where lawfully and technically available, screenshots or photographs of relevant equipment, copies of emails, and reports sent to authorities. The record must not displace navigation duties. Notes can be completed once the immediate situation is stable.

MARAD instructs US-flagged vessels to report attacks, incidents, or suspicious activity to specified military and UKMTO contacts and to activate the Ship Security Alert System in an attack or qualifying incident. The precise action depends on what occurred and the ship’s approved plans. An ambiguous hail may require reporting and monitoring, while an imminent threat can require emergency procedures.

Resolve conflicting instructions through a hierarchy

The company can build an instruction hierarchy that reflects flag guidance, coastal-state requirements, authenticated naval coordination, the ship security plan, and the master’s overriding safety and security authority. The hierarchy should identify conflicts that require immediate shore or authority clarification.

No hierarchy eliminates real-time judgment. Two authenticated bodies may issue incompatible directions, communications may fail, or the safest maneuver may differ from the planned response. The master must retain freedom to act for safety while seeking clarification and documenting the reasons.

Commercial desks should remain outside the radio decision loop unless asked for specific support. A charterer or broker does not authenticate a naval hail and should not pressure the bridge to comply or refuse based on schedule consequences. Their role is to manage contracts and customers after the safety response is established.

Zeaclub’s direction in agentic workflows can support a controlled communications log, compare caller details with verified directories, flag abnormal requests, and route an incident simultaneously to authorized shore teams. It should not impersonate the master, answer a security hail autonomously, or decide that a caller is genuine from a familiar name alone. In Hormuz, good automation shortens verification time while keeping navigation and command with trained people.

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

Sources