The call may be genuine and still need checking

Hormuz coordination can involve coastal States, UKMTO, MICA, naval forces and ships in congested water. A caller may know the vessel's name and position from AIS or public data. Familiar details prove access to information, not authority to change course.

Current instructions are time-sensitive

IMO's operational FAQ says its coordinated evacuation plan is paused and tells vessels not to initiate movement at that stage. It also describes direct contact by UKMTO or MICA and, in certain circumstances, VHF Channel 16 contact with coastal-State assistance.

Channel 16 has a narrow purpose

IMO Resolution A.954(23) reserves Channel 16 for distress, urgency, very brief safety communications and calling to establish another communication. Routine detail should move to an appropriate working channel.

Congestion is a safety hazard

Repeated long calls can mask distress traffic and make genuine coordination harder. Record the initial hail, identify the working channel and keep transmissions concise.

Start with identity

Capture claimed station, call sign, vessel addressed, time, channel, position and exact instruction. Ask the caller to repeat unclear elements using standard marine phrases.

Call back through a published route

Where procedures permit, verify through a number, email, reporting portal or channel published by IMO, UKMTO, MICA or the relevant coastal authority. Do not use contact details supplied only by the questionable caller.

Separate contact from clearance

A ship may be hailed to establish communications without receiving movement authority. Record who can issue the route, who manages traffic and what further confirmation is required.

Read back the full instruction

IMO Standard Marine Communication Phrases distinguish instruction, advice, warning and information and prescribe full responses. Read back route, waypoint, speed, time, reporting point and constraints so both sides can detect error.

Message markers reduce ambiguity

Ask whether a statement is an instruction, advice, warning or information. A naval warning about a hazard is not automatically a coastal-State routing clearance.

Coordinates require disciplined repetition

Confirm datum, degrees, minutes, decimals, north or east designators and sequence. Plot the instruction independently before acknowledging that the ship can comply.

A plausible route may still be stale

Mine status, congestion and clearance can change. JMIC's 18 June 2026 advisory was explicitly dated and described then-current routes, mines and possible naval hailing. It is evidence of that operational phase, not perpetual authority.

The bridge must test navigational safety

Authentication does not make an unsafe order safe. Compare the route with official warnings, current charts, assessed corridors, draft, traffic, position integrity and master's risk assessment.

Never disclose more than necessary

An unknown caller may ask for cargo, crew nationality, security team, machinery condition or destination. Provide information required by verified procedures, while protecting sensitive details until authority and need are established.

Voice familiarity is weak proof

Accent, terminology, background noise and knowledge of local geography can be copied or replayed. Authentication should rely on procedures and independent channels, not intuition about how an official sounds.

AIS identity can be borrowed

A caller may reference a displayed MMSI or transmit under a false identity. Correlate radio claims with radar, visual contact, published stations and established reporting systems.

GNSS disruption can corrupt the conversation

If the ship and caller use different or compromised positions, both may speak confidently about the wrong location. State the position source and uncertainty, and cross-check with radar or terrestrial fixes.

Establish a challenge phrase before transit

Company and authority procedures may include reference numbers, expected sequence, callback routes or pre-arranged verification data. Avoid inventing cryptographic-sounding codes that no receiving authority recognizes.

Use two-person verification

One officer handles the radio while another plots, checks the source and records the exchange. The master approves material movement changes under the ship's command procedures.

Keep the engine team informed

An unexpected speed reduction, holding pattern or abort manoeuvre affects machinery readiness. Communications authentication is not only a bridge task.

Protect the distress watch

Maintain required DSC and listening watches and avoid occupying Channel 16. If the working channel becomes unreliable, follow proper calling procedures rather than conducting a prolonged argument on the distress channel.

Record noncompliance pressure

Threats of detention, attack, delay or loss of sequence should be logged exactly. Pressure increases urgency but does not prove identity.

Escalate without broadcasting the dispute

Contact company security, recognized coordination centres and the relevant authority through established routes. Publicly accusing a caller over open VHF can worsen confusion and reveal the ship's uncertainty.

Owners need a communications matrix

Before sailing, list current authorities, published contacts, expected channels, decision rights, reporting formats and fallback paths. Version and time-stamp it because crisis contacts change.

Charterers should not relay operational orders

A commercial message saying that local agents heard the Strait is open is not a navigational clearance. Charterers should pass the source and time, allowing the owner and master to verify it.

Brokers must label hearsay

Market chat about a convoy, corridor or naval escort can move freight decisions quickly. State whether information comes from an official advisory, a ship report or an unverified third party.

Insurers need notification, not command

An underwriter may impose reporting or cover conditions, but does not authenticate a VHF route. Preserve notifications separately from the master's navigation record.

Traders should plan for verification delay

Authenticating instructions can cost minutes or a sailing sequence. Build that safety time into nominations and delivery scenarios instead of rewarding immediate compliance with uncertain calls.

Hypothetical: the convincing naval call

A caller names the ship, cargo and owner, then orders a turn toward a northern waypoint. The bridge requests the published authentication path, maintains the safe plan and alerts the coordinator. Commercial detail was available from outside the bridge.

Hypothetical: the real call with one wrong digit

A genuine authority transmits a coordinate incorrectly. Full read-back exposes the mismatch before the vessel turns. Authentication and content verification are separate controls.

Hypothetical: the blocked working channel

After a valid Channel 16 hail, the assigned channel is jammed or congested. The vessel uses the documented fallback and does not improvise a route from the fragmentary initial call.

Forecast

Future VDES and digitally signed traffic messages may strengthen source authentication. Voice will remain necessary for immediacy, distress and degraded systems, so bridge teams will still need procedural verification and precise read-back.

ZeaClub view

The right response to an unexpected call is neither blind compliance nor automatic rejection. Identify, record, read back, verify through a published independent path, test navigational safety and preserve the master's authority. In crowded, mined or electronically degraded water, authentication time is part of safe passage.

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

Sources