Rule 10 limits routine use

Under COLREG Rule 10, a vessel should not use an inshore traffic zone when it can safely use the appropriate lane in the adjacent traffic separation scheme. Vessels under 20 metres, sailing vessels and vessels engaged in fishing may use the zone.

A larger merchant vessel may use an inshore traffic zone when travelling to or from a port, offshore installation, structure, pilot station or another place situated within the zone, or to avoid immediate danger. These are defined circumstances, not a commercial shortcut around slower traffic.

The phrase “can safely use” requires a genuine assessment. Security threats, a verified mine warning, a closed route or immediate danger may affect that assessment. A higher war-risk premium or a more convenient ETA alone does not convert the inshore zone into the proper lane.

Rule 10 also does not displace the other collision rules. Lookout, safe speed, collision-risk assessment and responsibilities between vessels continue to apply. Fishing and small vessels may be concentrated inshore, so leaving the main traffic lane can increase rather than reduce encounter risk.

Verify what the chart actually shows

Before discussing route preference, the navigator should inspect current official charts, notices and routeing information. The proposed track should identify:

- the limits of the traffic lanes, separation zone and any inshore traffic zone; - charted depths, dangers and under-keel-clearance constraints; - territorial-sea limits relevant to the route; - prohibited, restricted, anchoring or military areas; - pilot stations, port approaches and crossing traffic; - current mine or navigational warnings; and - the authority responsible for traffic instructions.

A label used in a commercial email is not proof of route status. “Oman-side route,” “southern corridor,” “coastal lane” and “inshore traffic zone” may describe different things.

The ship should also verify the effective time of any alternative routing. In May and June 2026, JMIC and naval advisories described time-specific routes south of the traffic separation scheme and coordination with Oman. Those publications demonstrate how security routing can change. They should not be copied as November sailing instructions unless a current authority confirms them.

ECDIS route checks must use corrected data, but the bridge should also compare the route with source notices. A technically clear line on a display can still be based on an expired corridor or misunderstood category.

Security advice does not cancel navigation risk

Moving closer to a coast may increase radar and visual fixing opportunities when GNSS is degraded. It may also reduce sea room, increase small-craft encounters, bring the ship closer to shore-based threats and create more crossing traffic from ports or local routes.

The May industry guidance says alternate routing outside the Hormuz traffic separation scheme may be recommended by competent authorities depending on threats. It also states that any designated route can carry elevated risk and must be assessed before transit. Both northern and southern routes had reported incidents in 2026.

That means “south” or “inshore” is not a complete risk control. The assessment should compare:

1. verified hostile-activity reporting; 2. mines and underwater hazards; 3. depth and manoeuvring room; 4. traffic density and vessel mix; 5. coastal-state coordination; 6. rescue, tug and salvage access; 7. electronic interference and position-fixing options; and 8. the ship’s draft, cargo and technical condition.

The result may differ by direction and vessel. A route acceptable for a shallow-draft coaster may be unsuitable for a laden tanker. A recommendation for US-flagged ships cannot be assumed to govern another flag.

Plan entry, transit and exit as separate hazards

If use is justified, the ship still needs a complete route. Entering from the main lane may involve crossing or leaving-lane geometry under Rule 10. The transit may require lower speed, additional lookouts and closer depth monitoring. Rejoining the main flow can create a difficult merge.

The plan should mark:

- entry and exit points; - crossing courses and expected traffic; - no-overtaking and no-crossing sectors; - parallel indexes and manual position-fixing intervals; - minimum under-keel clearance and echo-sounder triggers; - abort points and safe alternatives; and - actions if the route is suspended while the vessel is inside.

Radar and visual checks should support GNSS. AIS should not be the sole source for position or collision assessment in an environment where official guidance reports spoofing and false targets.

Speed must preserve steerage, stopping options and safe interaction with local craft. A deep-sea vessel should not assume that smaller traffic will keep clear merely because it is following a security-recommended track.

Do not use “immediate danger” as a standing policy

Rule 10 permits inshore-zone use to avoid immediate danger, but that exception should not become a permanent company label applied to every Hormuz voyage. Conditions and evidence change.

A standing risk assessment can identify scenarios in which the option may be considered. The actual decision should use current intelligence, position, traffic and authority guidance. If the danger is not immediate, the company has time to seek a properly coordinated alternative route rather than invoke an emergency rationale.

If the master acts urgently, the contemporaneous log should capture the hazard, source, time, position and options available. Later reports should distinguish verified facts from allegations. “Projectile observed approaching” differs from “route changed because an unverified message alleged an attack.”

Once the immediate danger passes, the vessel should reassess whether continued inshore use remains justified and safe. It should not remain there solely because returning to the main lane would delay the voyage.

Allocate commercial consequences before transit

An inshore or coastal route may change distance, speed, pilotage, tug requirements, port reporting, insurance conditions and fuel. It may also affect contractual warranties or trading limits. Owners and charterers should identify who bears those consequences under the actual charter wording.

A route ordered by an authority, selected by the master for safety or requested by a charterer can have different legal significance. The operating record should preserve the decision chain without asking navigators to make contractual conclusions.

Brokers and traders should avoid describing the coastal option as a guaranteed shortcut. Capacity models should allow for route authentication, waiting, slower navigation and possible re-entry delays. Insurers should receive the route and material changes required by the policy.

ZeaClub can maintain a version-controlled record linking the charted route category, current authority notice, risk assessment, insurer response and charter notices. It can flag an expired instruction or an undefined “inshore route,” but it should not decide legal eligibility or navigational safety.

Commercial conclusion

A deep-sea ship may use an inshore traffic zone only when the rules and facts support it. The operator must first verify that the proposed water is actually a charted inshore traffic zone, then establish the Rule 10 basis, applicable coastal-state instructions and vessel-specific navigational safety.

Closer to shore is not synonymous with safer. It can reduce one threat while increasing grounding, collision, small-craft and jurisdictional exposure. The commercially defensible choice is the route with a current legal and operational basis, adequate depth and sea room, authenticated coordination and a documented reason for every deviation from the normal traffic lane.

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

Sources