The November Risk Picture Was Uneven, Not Uniform

JMIC's 12 November regional overview assessed the Strait of Hormuz at severe, meaning deliberate hostile action was considered highly likely under current conditions. It assessed the Gulf of Aden and Bab el-Mandeb or southern Red Sea at substantial, meaning an attack or maritime-security incident was a strong possibility.

The same overview assessed the Gulf of Oman and Arabian Sea at moderate. A ship could therefore pass through zones with materially different threat judgments during one voyage.

These labels are useful only with the underlying detail. In Hormuz, JMIC cited continued attacks, navigation interference, mining vigilance, hailing, and routing pressure. In the Gulf of Aden, piracy-related events and Houthi activity contributed to the assessment. In Bab el-Mandeb, the concern included attacks, maintained capability, and territorial developments in Yemen.

The plan must change as the threat mechanism changes.

One Voyage Needs Multiple Decision Gates

A single approval at the load port is inadequate for a voyage lasting days or weeks in a rapidly changing conflict.

ZeaClub recommends at least four gates:

- before entering or leaving the Strait of Hormuz; - after reaching the lower-risk Arabian Sea, when route alternatives can be reviewed; - before entering the Gulf of Aden reporting and security environment; - before committing to Bab el-Mandeb and the southern Red Sea.

Each gate should revalidate official advisories, recent incidents, route status, weather, fuel, machinery, crew readiness, insurance, and commercial instructions. Approval should expire if a defined event occurs, such as a new attack, route warning, loss of cover, major electronic interference, or material change in ship affiliation risk.

The ocean space between chokepoints is not dead time. It is the decision window in which the company can update evidence and preserve alternatives.

Targeting Logic Can Change Between the Straits

MARAD's September Red Sea advisory identified elevated Houthi risk for vessels with Israeli, US, UK, or Saudi associations and for fleets linked to Saudi port calls. It also described missiles, UAVs, unmanned surface and underwater vehicles, small-arms fire, explosive boats, and illegal boarding or seizure threats.

Hormuz advisories in 2026 addressed a different combination of Iranian attacks, US blockade enforcement, IRGC monitoring, naval hails, mines, electronic interference, and misidentification risk.

A ship's risk profile can therefore change without any alteration to flag or ownership. Loading in a Saudi port, belonging to a fleet with relevant calls, or receiving cargo through a particular chain may matter more at Bab el-Mandeb. An Iranian-port link, blockade question, or proximity to military forces may matter differently in Hormuz.

Screening should be zone-specific and repeated after cargo, charter, or routing changes.

AIS Policy Cannot Be Copied From One Zone to Another

The MARAD Red Sea advisory strongly advised US-flagged ships to switch AIS off where the master judged continued operation would compromise safety or security, while observing applicable SOLAS, flag-state, and navigation responsibilities. It noted that AIS-on vessels could be easier to track, although attacks had occurred whether AIS was on or off.

Hormuz guidance has included different considerations, including blockade verification, naval monitoring, collision risk, and elevated targeting concerns for AIS-on ships. JMIC has also reported extensive spoofing and interference.

A fleet-wide slogan such as "AIS always on" or "AIS always off" is not a sufficient policy. The master needs zone-specific guidance, legal and flag-state context, current official advice, and authority to decide based on safety. Other commercial systems that transmit location may also need review.

Any change should be logged with time, position, reason, and notifications required by the safety-management system.

Reporting Must Follow the Whole Route

MARAD advised US ships to register with UKMTO before entering the Indian Ocean Voluntary Reporting Area and to include estimated arrival times for Hormuz, Bab el-Mandeb, and Suez, plus navigation constraints and security-plan information where relevant.

Even for ships under other flags, the broader principle is valuable: reporting should describe the entire intended risk route, not only the next waypoint. Security centers and company teams need accurate movement intentions to provide relevant information and respond to an incident.

Contact lists must be checked before departure and again before each reporting boundary. The bridge should know which organization is responsible for what, how to authenticate an unexpected communication, and what fallback exists if satellite or VHF communications fail.

Crew Fatigue Accumulates Across Chokepoints

A high-alert Hormuz transit can involve extra lookouts, security teams, communications, route changes, and interrupted rest. If the ship then accelerates toward Bab el-Mandeb without a recovery plan, fatigue may peak at the second difficult passage.

The IMO confirmed fatal attacks in both the Hormuz region and Red Sea during 2026. Its 12 August statement following the attack on TIHAMAH emphasized thorough risk assessment and appropriate best management practices.

Crew readiness is therefore a gating condition. The plan should include protected rest after Hormuz, medical and welfare checks, drills timed to avoid exhaustion, relief for key bridge and engine-room roles, and honest reporting of fatigue. A commercial schedule that consumes the recovery window creates a new hazard.

Fuel and Diversion Must Be Planned Before Hormuz Departure

A vessel that exits Hormuz with fuel sufficient only for the Suez route may have little flexibility if Bab el-Mandeb deteriorates. The Cape of Good Hope alternative can add substantial distance and time, depending on the ship's position and destination.

The bunker plan should examine at least the intended route, a pre-Bab el-Mandeb hold or diversion, and a Cape alternative. It should consider safe bunkering locations, availability, war-risk exposure, speed changes, weather margins, and the effect of prolonged waiting.

This does not mean every ship must carry enough fuel for every theoretical route. It means the commercial team should understand when the decision becomes irreversible and avoid crossing that point without a current risk approval.

Insurance Approval Should Cover the Route Sequence

War-risk terms, additional premiums, notice requirements, warranties, and geographic limits may differ across the Gulf, Arabian Sea, Gulf of Aden, Red Sea, and adjacent waters. A quotation for Hormuz does not necessarily approve Bab el-Mandeb.

Owners and brokers should present the intended sequence, time windows, route options, cargo, affiliation analysis, security measures, and possible diversion. If conditions change after Hormuz, the company should know whether a renewed notice or approval is required.

Charterers need the same route logic. An order through Suez may become unsafe or commercially impracticable after the ship has left the Gulf. The charter should be reviewed before the crisis, not first interpreted when the vessel approaches the second gate.

Piracy and Conflict Controls Must Coexist

The Gulf of Aden and Somali Basin can present piracy or armed-robbery risks alongside conflict-linked threats. Protective measures optimized for one hazard may not fully address another.

A route farther from a hostile coastline may change piracy exposure. AIS, lighting, speed, physical hardening, watchkeeping, and communications may involve different tradeoffs. The ship security assessment and voyage plan should integrate current best management practices rather than select one threat and ignore the rest.

JMIC's November overview explicitly linked the Gulf of Aden substantial rating to piracy events as well as Houthi rhetoric and attacks. That combined environment makes single-threat planning inadequate.

A Hypothetical Laden Tanker

Assume a tanker loads in the Arabian Gulf for the Mediterranean. It receives approval to use a recognized Hormuz route and completes the transit without incident. During its passage across the Arabian Sea, a fatal attack is confirmed near Bab el-Mandeb and the insurer requests a revised security plan.

The successful Hormuz transit is irrelevant to whether the next gate is acceptable. The owner updates association screening, recent incidents, route advice, AIS policy, crew fatigue, fuel, and Cape diversion economics. The charterer is asked for timely instructions within the contract, and the master receives authority to hold outside the higher-risk area while the review is completed.

If the ship lacks fuel for a safe alternative, the earlier bunker decision has already constrained the security decision. That is why two-chokepoint planning begins before loading.

Commercial Analysis Must Avoid Double Counting and Blind Spots

Freight and voyage models should not simply add two generic war-risk premiums. Some costs overlap, such as security preparation and insurance administration. Others are sequential: extra fuel, waiting, separate premiums, additional crew burden, or a later Cape deviation.

Traders should model delivery uncertainty as a range with decision points. Brokers should state which chokepoints and routes a rate assumption covers. Insurers need the actual voyage rather than an incomplete label such as "Arabian Gulf to Europe."

The greatest blind spot is assuming the lower-risk Arabian Sea segment means the danger has ended. It may merely be the interval between two different threat systems.

The ZeaClub View

Hormuz and Bab el-Mandeb should be managed as connected but distinct gates. One integrated voyage plan must contain two threat assessments, two sets of controls, and a decision window between them.

The ship's flag and cargo may be unchanged, while its targeting profile, AIS judgment, reporting duties, insurance terms, and route alternatives change materially. Crew fatigue and fuel link the zones even when the attackers do not.

A successful first transit is not evidence that the second is safe. The professional standard is to preserve choice until the latest practical moment, revalidate before commitment, and never let the schedule turn yesterday's approval into today's assumption.

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

Sources