Authenticate the route before engineering it
The operator should first verify the issuing authority, publication time, effective period, direction of travel, coordinates, datum, vessel restrictions and reporting requirements. A route copied from a message, tracking plot or old advisory should not enter the bridge system without provenance.
Current MARAD guidance asks US-flagged ships to coordinate with NAVCENT NCAGS, avoid hazard areas and conform to provided routes. That does not remove the master’s responsibility to turn the provided route into a safe vessel-specific plan.
Historical JMIC Advisory 009-26 illustrates the issue. It published a June southern corridor and mine information under conditions then in force. Those waypoints are evidence of a historical arrangement, not November instructions.
The bridge should compare every coordinate against current official charts and navigational warnings. Transposition errors, latitude-longitude reversal, wrong hemisphere, minute-decimal format and chart datum can produce a plausible but dangerous route.
Any discrepancy should be resolved through an authenticated channel before the ship commits.
Convert waypoint intersections into turn geometry
A waypoint drawn at the intersection of two straight legs is not necessarily where the helm should be put over. The ship begins turning before that geometric point so that its curved track joins the next leg.
The wheel-over position depends on:
- alteration angle; - planned speed; - advance, transfer and tactical diameter; - rudder or rate-of-turn plan; - draft, trim and loading condition; - wind, current and shallow-water effects; - machinery and steering response; and - the width of safe water.
The bridge should use approved vessel manoeuvring data and recent operational experience, not a generic turning radius. A route appropriate for a coaster can be impossible for a laden VLCC at the same speed.
For each significant alteration, the plan should show wheel-over, expected rate of turn, track limits, clearing bearings or parallel indexes and the action if the vessel does not respond as predicted.
If safe geometry cannot fit inside the route, the answer is not to increase rudder blindly. The ship may need lower speed, a revised waypoint, different sequence or authority clarification.
Validate a corridor wider than the monitoring alarm
ECDIS route validation checks charted dangers within the cross-track corridor selected by the navigator. It does not prove that water outside that corridor is safe, and it may not understand every security notice, temporary mine warning or uncharted threat.
MCA guidance recommends adapting cross-track corridors to each leg and notes that the system will not scan outside the defined corridor. It may be prudent to scan a wider corridor for contingency margin, then set the narrower monitoring limit appropriate for execution.
The validation should use the correct safety depth and contour for the vessel’s draft, squat, heel in turns and required under-keel clearance. Chart scale and hydrographic quality also affect the margin.
A wheel-over arc can extend beyond the straight-line corridor even when both legs validate. The navigator must inspect the actual turn, not only the waypoint and leg lines.
The team should check both the primary and backup system. A route that exists only on one ECDIS or differs between ship and shore is not ready.
Test every leg against non-charted constraints
Electronic route check cannot evaluate all operational restrictions. The bridge and company should manually compare the route with:
1. current coastal-state and naval instructions; 2. mine and maritime-security warnings; 3. military standoff requirements; 4. traffic-lane direction and separation zones; 5. no-overtaking or no-crossing controls; 6. pilot and reporting points; 7. communications and route-change triggers; and 8. insurance or charter conditions affecting movement.
A coordinate may be navigationally clear but operationally invalid because its authority period has expired. Another may be authorised but incompatible with the ship’s draft or turning circle.
The plan should distinguish charted hazard, reported threat, assessment and hypothetical contingency. A reported mine position is not the same as a surveyed obstruction, but both can affect route approval according to current guidance.
The master should approve the complete plan after these checks, not merely acknowledge receipt of the waypoint file.
Prepare for degraded GNSS at each alteration
A wheel-over point derived only from GNSS position may become unusable when the signal is spoofed. The plan should provide alternative cues wherever practicable.
Radar ranges, parallel indexes, visual bearings, clearing lines, depth trends and dead reckoning can support the turn. The selected methods should account for object identification, radar performance and chart accuracy.
The bridge should identify which alterations require maximum position reliability and set fix intervals accordingly. A turn near a corridor edge may need continuous cross-checking; an open-water alteration may permit a wider margin.
Current MARAD advice reports significant regional GNSS interference and recommends traditional navigation methods. The Hormuz guidance tells vessels to cross-check GNSS against gyro, log and radar and maintain dead reckoning.
If the position cannot be established to the plan’s minimum standard before wheel-over, the master should use the defined delay, abort or continuation option. Guessing the turn based on another vessel’s movement is not a substitute.
Control late route revisions
A route received close to the transit window should trigger a formal change process. The company should not compress validation because the slot appears scarce.
The revised plan needs:
- source and version identification; - comparison with the superseded route; - chart and warning check; - recalculated turns, speed and under-keel clearance; - cross-track and contingency validation; - bridge-team briefing; - update of primary and backup systems; and - master approval.
Changed waypoints should be highlighted, not hidden inside a full replacement file. Old versions should be marked superseded but retained for evidence.
If the time available is insufficient, the ship should seek delay or clarification. A route window is not permission to sail with an unchecked plan.
Shore teams should avoid editing coordinates by hand to “smooth” a route. Any deviation from authority-issued geometry requires confirmation and a documented operational basis.
Execute by monitoring the turn, not trusting it
During each alteration, the bridge should compare actual rate of turn, speed, set and track with the planned values. An autopilot or track-control system may calculate a turn, but the team remains responsible for monitoring it and understanding the active parameters.
The conning officer should receive clear reports of distance to wheel-over, verified position, traffic, rudder response and cross-track trend. Manual steering and engine readiness may be appropriate under the approved plan.
The team should know the maximum deviation that remains inside validated water. If the ship overshoots, corrective action must be checked against traffic and the opposite corridor boundary. A rapid return to the line can create a second unsafe turn.
Following vessels may expect predictable movement. Significant speed reduction or abnormal alteration should be communicated through applicable channels where useful, without relying on VHF agreement to replace COLREG.
After the turn, the bridge should confirm the vessel is steady on the new leg and that position integrity remains sound.
Preserve the commercial and technical record
The voyage file should retain the authoritative waypoint source, route versions, validation results, safety settings, turn calculations, master approval and material execution differences.
This evidence supports casualty investigation, insurance notice and charter analysis. It can show whether delay arose from authority routing, vessel limitations, inadequate planning time or a later threat change.
The record should not overstate ECDIS validation. “Route scan completed with stated settings” is accurate. “ECDIS certified the route safe” is not.
ZeaClub can manage route versions, coordinate provenance, ship-specific turn data and approval timestamps. It can flag a sharp alteration, inconsistent waypoint or missing backup update, but it should not alter official coordinates or approve the passage.
Commercial conclusion
Waypoints are control points, not a complete navigational solution. Safe Hormuz execution requires the vessel to connect them with verified turn geometry, adequate depth and cross-track margin, independent fixing and a workable contingency.
Owners should provide enough time and qualified personnel for validation. Charterers should recognise that a late route can move the transit window. Authorities and agents should preserve coordinate format and version clarity.
The most defensible plan is not the one loaded fastest. It is the one whose every turn can fit inside checked water at the vessel’s actual speed and condition, even when the primary position input becomes unreliable.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- International Maritime Organization, Resolution A.893(21): Guidelines for Voyage PlanningAccessed 2026-11-19
- Industry Guidance on the Safe Management of Vessel Transit through the Strait of Hormuz, May 2026Accessed 2026-11-19
- UK Maritime and Coastguard Agency, MGN 379 Amendment 1: Use of Electronic Navigational AidsAccessed 2026-11-19
- US Maritime Administration, Advisory 2026-011Accessed 2026-11-19
- Joint Maritime Information Center, Advisory Note 009-26, 18 June 2026Accessed 2026-11-19
- UK Maritime and Coastguard Agency, MGN 610 Amendment 1: SOLAS Chapter V GuidanceAccessed 2026-11-19