A successful transit is evidence, not clearance
Historical JMIC Advisory 009-26 described a southern corridor in June 2026 as confirmed clear of mines and said transits along stated waypoints had proven safe. That language belonged to a dated advisory with specific conditions, mine information and coordination.
It did not mean that any merchant ship’s wake became a permanent safe corridor. Mines can move, new hazards can appear, route notices can expire and the threat environment can change. The May industry guidance continues to identify errant mines not detected during original clearance operations as a possible condition.
A trailing vessel should therefore require its own effective route instruction, threat assessment, chart check and authority coordination. A track shared by another master, agent or messaging group is not an official navigational warning.
The ship should distinguish:
- a route formally issued by a competent authority; - a hydrographic or mine-clearance statement; - a reported successful transit; - an AIS track reconstructed by a commercial provider; and - an informal claim that a vessel “went through safely.”
Each has different evidential value. None removes the master’s responsibility.
Do not treat AIS history as a swept path
Commercial AIS plots can be delayed, simplified, interpolated or based on spoofed positions. The ship ahead may also transmit incorrect GNSS-derived data during regional interference.
Current MARAD guidance reports significant GNSS spoofing and jamming and tells US-flagged vessels to cross-check ECDIS inputs with radar, visual bearings and secondary methods. That advice reinforces a basic rule for all operators: an electronic trail must be independently verified before it influences the passage plan.
The bridge should not import another vessel’s waypoints directly into ECDIS. Coordinates must be checked against the current official route, chart, warnings, safety contours, territorial limits and the vessel’s own draft and manoeuvring requirements.
If the leading ship’s displayed track diverges from the authorised route, the trailing vessel should not follow simply because the leader remains afloat.
Maintain a collision-safe following interval
Following distance must allow for the relative speed, stopping distance, vessel size, visibility, traffic, route width and possible emergency action by the ship ahead. A fixed distance copied across a fleet is not enough.
The trailing bridge should consider what happens if the leader:
1. stops or loses propulsion; 2. alters sharply for a contact or warning; 3. is struck and blocks the route; 4. reduces speed to answer a military hail; 5. turns toward an abort point; or 6. transmits misleading movement data.
The interval should preserve time to detect, assess and act without cutting into opposing traffic or a separation zone. A laden tanker may need substantially more room than a small coaster.
The ship ahead remains an ordinary COLREG target. Radar and visual observations should establish range, bearing, CPA and speed trend. AIS may add identification but should not be the sole collision source.
If traffic sequencing or a security window compresses the interval below the master’s minimum, the vessel should delay entry or seek new instructions rather than accept a close formation that was never assessed.
Avoid the convoy illusion
Two ships travelling in the same direction are not necessarily a convoy. A convoy normally involves planned command, spacing, communications and protection or coordination arrangements. Informally following another merchant ship does not transfer responsibility or create naval protection.
The trailing vessel should not assume that an attack would target the first ship or that the leader provides physical protection. Clustering can create a more visible group, concentrate consequences and limit evasive options.
Communications should be concise and necessary. A VHF exchange may clarify speed or awareness, but it does not make the leading master responsible for the route. Sensitive security details should not be broadcast merely to coordinate an informal formation.
If a competent authority establishes grouping or convoy procedures, the ship should follow those specific instructions and understand the command relationship. It should not invent them.
Plan for the leader becoming a casualty
The passage plan should include action if the ship ahead is disabled, attacked, grounds, drops anchor or stops in the route. The correct response depends on range, traffic, sea room, depth, hazards and official instructions.
The bridge should identify:
- the minimum distance for early speed reduction; - safe stopping or abort areas; - whether overtaking is prohibited or unsafe; - communications and distress-monitoring duties; - reporting to coastal authorities and UKMTO; - rescue obligations consistent with safety; and - the route for following traffic.
A sudden turn around the casualty may expose the ship to mines, opposing traffic or an unassessed corridor. The master should not leave a verified route unless necessary and safe under the circumstances.
The trailing ship may be the first source of direct evidence. Reports should distinguish observation from attribution: “projectile impact observed” is different from identifying the attacker.
Commercial teams should stop schedule messages during the emergency and support the master with authorities, insurers, cargo interests and crisis response.
Compare vessel-specific differences
The same route can present different risks based on draft, beam, manoeuvring, cargo and flag instructions. A shallow-draft vessel’s lateral margin does not prove adequate under-keel clearance for a laden tanker.
War-risk cover may also contain different notice or route conditions. The leading ship’s insurer approval has no bearing on the follower’s policy. Charter instructions, sanctions screening and port plans can differ as well.
Before using another transit as supporting evidence, the operator should state which characteristics are comparable and which are not. Anecdote becomes misleading when the differences are hidden.
ZeaClub can help by linking official route versions, vessel particulars, verified transit observations and incident reports. It can show that a similar vessel passed at a recorded time, but it should never label the follower’s route safe or copy waypoints without controlled verification.
Record what was learned without overstating it
After transit, the ship should record observed traffic, environmental set, communications, navigation anomalies, route deviations and hazards. This can improve planning for later vessels.
The report should avoid the phrase “route clear” unless a competent authority has issued that finding and its scope is quoted accurately. “No hazard observed from this vessel during this transit” is narrower and more defensible.
Absence of an incident is not proof that every control was effective. The ship may have passed despite an undetected risk. Lessons should compare the plan with actual execution and identify uncertainty.
If fleet operators share tracks, they should preserve timestamps, position sources, accuracy limitations and route versions. Stale data should expire rather than remain on a bridge folder as an apparent recommendation.
Commercial conclusion
Following another ship can support traffic awareness, but it cannot replace route authority, mine information, independent navigation or safe separation. The preceding vessel’s survival is one observation, not a guarantee.
Owners should prevent informal AIS tracks from becoming unofficial passage plans. Masters should preserve enough distance to respond if the leader stops and should navigate using their own verified route. Charterers should not pressure a vessel to “follow the one ahead” because a slot appears to be closing.
The commercially defensible decision is to use current authoritative routing, assess the ship’s own limitations and treat every preceding transit as time-limited evidence with stated uncertainty. A wake is visible. Safety beneath and around it is not.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- Joint Maritime Information Center, Advisory Note 009-26, 18 June 2026Accessed 2026-11-19
- Industry Guidance on the Safe Management of Vessel Transit through the Strait of Hormuz, May 2026Accessed 2026-11-19
- US Maritime Administration, Advisory 2026-011Accessed 2026-11-19
- International Maritime Organization, Operational FAQs for the Strait of Hormuz Evacuation PlanAccessed 2026-11-19
- Sultanate of Oman, Notice to Mariners on Controlled Hormuz Evacuation, 23 June 2026Accessed 2026-11-19
- International Maritime Organization, Update to Council 137 on Protection of Vital Shipping LanesAccessed 2026-11-19
- UKMTO, Recent IncidentsAccessed 2026-11-19