Begin with the route’s legal and charted structure
In an IMO-adopted traffic separation scheme, Rule 10 requires a vessel to proceed in the appropriate lane in the general direction of traffic flow and, as far as practicable, keep clear of the separation line or zone. It does not order every ship to follow the exact lane centre.
The chart and current route information should identify:
- traffic-lane boundaries and the separation zone; - inshore traffic zones or adjacent coastal waters; - safety contours, charted dangers and deep-water constraints; - lane terminations, bends and merge points; - crossing routes and port approaches; - current temporary corridors or excluded areas; and - applicable coastal-state reporting instructions.
A temporary security route may not share the same boundaries or legal character as the standard traffic lane. The bridge must use the effective instruction and charted coordinates rather than assume ordinary TSS positioning rules describe every corridor.
Do not confuse distance from Iran with distance from risk
MARAD’s current recommendation to US-flagged ships is specific and qualified by navigational safety. Other flags should consult their own authorities. Even for a US-flagged ship, “as far as possible” is not a coordinate.
A more southerly position may reduce proximity to Iranian waters or units. It may also bring the vessel closer to Oman-side traffic, land, small craft, pilot movements or shallow water. Both northern and southern Hormuz routes have had reported incidents during 2026, according to industry guidance.
The security assessment should therefore compare threat exposure across the entire feasible corridor. It should use current official reporting, not infer that one lane edge is safe because no incident was reported there during a short period.
A position chosen for security must remain predictable to surrounding traffic and consistent with COLREG.
Preserve collision-avoidance room on both sides
The centre of available safe water can provide balanced room to alter, but it is not always the best track. Traffic density, overtaking, crossing vessels and depth may justify a different position.
The bridge should test likely encounters before transit. If a vessel ahead stops, can the ship slow without being trapped against a boundary? If a crossing vessel approaches, is there room for an early substantial alteration? If another ship overtakes, does the planned track leave adequate passing space without entering the separation zone?
Rule 10 does not relieve any vessel of other COLREG duties. A ship cannot insist on its planned lateral position when collision avoidance requires action. Nor should it routinely hug a boundary so closely that every encounter forces a breach.
The passage plan should mark no-overtaking, no-crossing and constrained sectors. In those areas, speed and sequencing may be better controls than lateral movement.
Detect lateral movement independently
Official and industry guidance reports GNSS interference around Hormuz. A displayed cross-track error may represent real drift, spoofed position, gyro error or a wrong route version.
The bridge should monitor the corridor with radar ranges, parallel indexes, visual bearings, dead reckoning and echo-sounder trends as available. An ECDIS line cannot prove that the ship remains in safe water if its position source is false.
Parallel indexes should reference verified fixed objects and be set for both relevant sides where practical. They show lateral relationship to the planned track but not progress along it, so independent fixes remain necessary.
The team should define an inner warning limit and an outer action or abort limit. Waiting for the outer edge to alarm can leave too little room for a large ship to correct without overshoot.
Course corrections should be early and measured. Repeated small changes can create a weaving track and confuse nearby vessels. A larger correction must be checked against collision risk and route boundaries before execution.
Respond to pressure from other ships carefully
A military unit, coastal authority, pilot, vessel traffic service or another merchant ship may request a lateral change. The bridge should identify the caller and understand whether the message is an order, traffic information, recommendation or informal request.
Where time allows, unexpected routing directions should be authenticated through recognised channels. MARAD gives US-flagged vessels specific advice on certain Iranian hails and NCAGS reporting. That instruction should not be generalised to ships under other flags or to every communication.
If immediate danger requires movement, the master should act using the safest available option and report afterward. The log should distinguish the verified message, direct observation and later attribution.
Commercial staff should not ask the vessel to “edge south” merely because a tracking screen makes that side look quieter.
Update the track when the route or threat changes
A changed mine warning, attack report, traffic restriction or authority route can invalidate the preferred position. The company and master should review the whole corridor, not add a waypoint that creates a sharp dogleg.
The update should verify effective time, source, coordinates, depth, collision geometry, current, communications and insurance or charter implications. All bridge displays and printed plans should use the same version.
If the change arrives after an abort point, continuing to a wider area may be safer than an immediate lateral move. The plan should contain decision gates rather than presume every route update can be implemented instantly.
Historical route information should remain archived for evidence but clearly marked superseded. A track that was acceptable under a June mine-clearance plan should not reappear as a November alternative through an old attachment.
ZeaClub can link route versions, official notices, cross-track limits, vessel draft and approval records. It can flag inconsistent boundaries across ship and shore copies, but it should not choose the lane position or issue helm advice.
Record the reason for the chosen position
The passage record should explain the planned corridor and any significant departure. Relevant evidence includes chart and route versions, draft, safety settings, threat advice, traffic, verified position, communications and the master’s decision.
A record that says only “kept south for safety” is too vague. It should identify the applicable guidance, navigational limits and how the selected track balanced them.
This evidence supports later claims and performance analysis. Lateral route changes may affect distance, fuel, speed and arrival time, but cost allocation depends on the contract and facts. The bridge should not be required to optimise a narrow commercial metric at the expense of sea room.
Fleet analysis can compare observed traffic and sensor performance, provided it does not turn historical tracks into an unofficial recommended lane.
Commercial conclusion
There is no universally safe side of a Hormuz lane. The correct position is the vessel-specific track that complies with the current route, keeps clear of prohibited or separation areas, preserves depth and collision room, and implements applicable security advice without creating a greater navigational hazard.
Owners should define checked corridors rather than single lines. Charterers should avoid demanding lateral shortcuts from shore. Insurers need evidence that deviations were assessed and communicated.
The best track is not the one farthest from a headline threat in isolation. It is the one that leaves the master the most credible safe options when traffic, sensors or the threat picture changes.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- US Coast Guard Navigation Center, Amalgamated Navigation Rules, Rule 10Accessed 2026-11-19
- International Maritime Organization, Convention on the COLREGsAccessed 2026-11-19
- International Maritime Organization, Ships’ RouteingAccessed 2026-11-19
- US Maritime Administration, Advisory 2026-011Accessed 2026-11-19
- Industry Guidance on the Safe Management of Vessel Transit through the Strait of Hormuz, May 2026Accessed 2026-11-19
- Joint Maritime Information Center, Advisory Note 004-26, 4 May 2026Accessed 2026-11-19
- Joint Maritime Information Center, Advisory Note 009-26, 18 June 2026Accessed 2026-11-19