The distance is a planning control, not a license to maneuver blindly
MARAD’s active advisory tells US-flagged vessels in the Persian Gulf, Strait of Hormuz, and Gulf of Oman to maintain a minimum 30-nautical-mile standoff from US military vessels to reduce the risk of being mistaken for a threat. JMIC’s November 15 update repeated a 30-nautical-mile recommendation from US units in its regional assessment.
A merchant ship should incorporate that instruction early in route and timing decisions. It should not wait until a warship is close and then make an abrupt alteration that creates a collision, grounding, routeing, or mine exposure.
The number also needs its source and scope. MARAD’s wording expressly addresses US-flagged vessels and US military vessels. JMIC provides broader situational guidance. Other flags should check their own Administration, company, and current authority instructions rather than assume every naval unit or every sea area carries an identical rule.
A recommended standoff does not cancel the Collision Regulations, the master’s safety authority, coastal-state traffic management, or a specific instruction from an authenticated authority. If physical geography or traffic makes the distance unavailable, the bridge and shore team need coordination, not a fictitious claim of compliance.
Start with the actual route and operating picture
Thirty nautical miles is a large distance in a congested chokepoint environment. Plotting a circle around every reported naval position may show that a proposed route conflicts with military activity, anchorages, coastal waters, hazards, or other traffic. The result should trigger planning and liaison, not an improvised detour.
The voyage team needs the latest official route information, navigational warnings, authority coordination, known military operating areas where available, traffic, draft, weather, and electronic-interference assessment. Warship positions can change and commercial tracking may be delayed, incomplete, or intentionally limited. A static screenshot is not a reliable tactical plan.
MARAD advises US-flagged ships to coordinate closely with NAVCENT NCAGS, consider recommendations, avoid hazard areas, and conform to provided routes when possible. That coordination can help reconcile the standoff with the route before the ship commits to a constrained approach.
The bridge plan should identify decision points at which speed or timing can be adjusted safely. Delaying departure or reducing speed in suitable open water may preserve separation more safely than turning near the strait. Any speed change must account for traffic, maneuverability, security exposure, and the risk of becoming stationary or predictable.
Collision avoidance and routeing remain mandatory concerns
The IMO Collision Regulations require proper assessment of collision risk and appropriate action. Rule 10 addresses conduct in and near traffic separation schemes. A security recommendation does not permit a ship to cross traffic unsafely, impede another vessel, or enter a charted hazard.
The Hormuz traffic separation scheme has a long international history. IMO adopted the original scheme in 1968, and its July 2026 Council statement again referred to the internationally recognized TSS. During parts of the 2026 crisis, authorities also issued temporary instructions because of reported mines and evacuation arrangements. This changing history reinforces the need to use current navigational directions rather than assuming the peacetime lane or an old temporary route is available.
If a naval unit approaches despite the planned standoff, the bridge should maintain navigation, monitor Channel 16, identify the caller, and respond according to current flag and government guidance. MARAD says US-flagged ships should answer calls from coalition navies. The team should avoid ambiguous maneuvers and make its intentions clear where appropriate.
A warship’s status does not allow the merchant bridge to stop monitoring all other targets. Small craft, tugs, fishing vessels, and commercial ships may create the immediate collision risk while attention is focused on a military contact.
Define exceptions, escalation, and evidence
The company’s passage plan can define an exception process for cases in which 30 nautical miles cannot be maintained. The master notifies the relevant authority and company, states the navigational constraint, requests guidance, and records the response. The process should never imply that shore management can order an unsafe maneuver merely to satisfy a plotted radius.
Triggers for escalation may include an unplanned naval approach, conflicting hails, loss of reliable position, route closure, a military exercise or engagement, high-speed craft, or inability to identify a unit. The vessel security plan and government guidance determine the response.
Records should include the advisory version, plotted route, information cutoff, military contact reports, communications, closest-point calculations, actions taken, and the master’s reasons. Sensitive information requires controlled distribution. A public article should not reveal live naval positions or a ship’s tactical route.
Commercial teams also need careful language. “The vessel will always remain 30 miles from every warship” may be impossible to promise. A better fixture assumption is that the vessel will comply with applicable official guidance and coordinate routing, with time and cost consequences treated under the contract.
Insurance notices may require the operator to disclose route or security arrangements. Owners should confirm what information the underwriter needs, how long approval remains valid, and whether a change in naval coordination reopens the quotation.
Convert the radius into a managed commercial dependency
A standoff can affect ETA, bunker consumption, arrival windows, and passage availability. It may require a speed adjustment, delayed approach, or revised route supplied through official coordination. These are real voyage inputs, but they should not be estimated from an arbitrary semicircle drawn around an old naval position.
Scenario planning can test a normal coordinated passage, a delay while military separation is restored, and a suspended transit after escalation. Each case should show assumptions rather than invent an observed delay or additional premium.
Brokers can help by asking whether the vessel is subject to the US advisory, whether coordination has occurred, and whether the estimate includes a security timing allowance. They should not request or circulate sensitive tactical information.
Zeaclub’s direction in agentic maritime workflows can support this control by linking current government guidance to the vessel’s flag, alerting planners when a proposed route conflicts with a reported restriction, and recording authority coordination and expiry. It should not generate live avoidance maneuvers or infer naval positions from incomplete public tracks. The bridge and competent authorities must manage the actual encounter.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- US MARAD Advisory 2026-011Accessed 2026-11-18
- JMIC Advisory Update 114, November 15, 2026Accessed 2026-11-18
- IMO overview of COLREG collision-prevention rulesAccessed 2026-11-18
- IMO Council statement on the recognized Hormuz traffic separation schemeAccessed 2026-11-18
- IMO Resolution A.161(ES.IV), 1968 Hormuz routeing schemeAccessed 2026-11-18