U.S. blockade enforcement against Iranian ports and coastal areas now moves from declaration to vessel-level operating risk.
From 2000Z on July 14, Gulf-linked voyages face visit, search, diversion, capture and documentation exposure.
1. Iranian Port Calls Now Carry Boarding Risk
• JMIC Advisory 015-26 says U.S. Central Command will begin enforcing a naval blockade of all Iranian ports and Iranian coastal areas from 2000Z on July 14, 2026.
• The enforcement area covers the Gulf, Strait of Hormuz, Gulf of Oman and North Arabian Sea.
• The blockade applies to all vessel traffic regardless of flag, so neutral registry does not remove exposure if the voyage is assessed as Iran-linked.
• Vessels suspected of entering or departing the blockaded area without authorization may face interception, diversion or capture.
• Non-compliant vessels may be compelled by force, making bridge response, document control and shore-side escalation immediate operational requirements.
2. Hormuz Transit Remains Open, But Not Routine
• JMIC says neutral transit through the Strait of Hormuz to or from non-Iranian destinations will not be impeded.
• That distinction matters: Hormuz passage may remain available, but vessels still need clean voyage intent, cargo-document readiness, clear AIS behavior and disciplined communications.
• Masters should treat naval hailing, VHF challenge, approach by military craft or boarding instruction as a controlled event requiring immediate company, flag, P&I and charterer notification.
• Passage plans should separate neutral Hormuz transit from Iranian-port exposure, including destination, last port, next port, cargo origin, receiver, charterer, beneficial ownership and STS history.
• The July 13 GFS Galaxy attack remains the immediate security context, but DeepDraft has already reported that incident and it should not be repeated as today’s lead.
3. Charterparty, Insurance and Cargo Screening Move to the Front
• Chartering desks must now price Iranian-port exposure as a live enforcement risk, not only as a sanctions or war-risk background condition.
• Voyage orders involving Iran, Iranian cargo, Iranian receivers, Iranian coastal waters, Iranian terminals, Iranian bunkering or Iranian-linked STS operations should be rechecked before the vessel enters the advisory area.
• Owners and managers should confirm whether P&I, H&M, war-risk and detention-related cover remain valid for the exact voyage, cargo, ownership chain, charterer and port call.
• Bills of lading, cargo manifests, certificates of origin, STS records, LOIs, agent instructions, voyage orders and AIS history may become part of a boarding or detention review.
• Charterparty clauses covering deviation, delay, off-hire, unsafe port, war risk, sanctions, lawful orders, force majeure and cargo refusal should be checked before any Iran-linked movement is performed.
4. Maersk WAF6 Return Shows Route Decisions Are Splitting by Corridor
• Maersk said it will resume its WAF6 service through the Red Sea, adding another signal that liner operators are selectively rebuilding trans-Suez services.
• The WAF6 service links the Middle East, Mediterranean and West Africa, making the return relevant for shippers comparing Suez, Red Sea and Cape routing options.
• This is not a Gulf blockade signal by itself, but it shows operators are making corridor-specific risk decisions rather than applying one global security rule.
• Container cargo owners should expect uneven routing outcomes, with some services returning through Suez while Gulf-linked voyages face separate enforcement and insurance tests.
• The split matters commercially: Red Sea service restoration may reduce voyage time on selected lanes, while Hormuz and Iranian-port exposure can still trigger delay, denial, diversion or detention risk.
Strategic Summary & Actions Required
• Masters approaching Hormuz, the Gulf of Oman, the North Arabian Sea or Iranian-linked routes should revalidate passage intent, destination, cargo papers, AIS status and VHF response procedures before entering the advisory area.
• Ship managers should run an immediate voyage-screening check for Iranian port calls, Iranian cargo exposure, STS history, beneficial ownership, charterer identity, insurance validity and flag-state instructions.
• Charterers and operators should review deviation, delay, unsafe port, war-risk, sanctions, force majeure, lawful-order and off-hire language before issuing or accepting Iran-linked voyage orders.
• CSO, DPA and legal teams should prepare boarding-response instructions that preserve records, protect the Master from unsupported certification and keep communications routed through authorized shore contacts.
• Container and tanker desks should separate Red Sea route-restoration decisions from Gulf blockade exposure; trans-Suez normalization does not remove Hormuz enforcement risk.
Operational Status
RED – Iran Blockade Enforcement / Hormuz Transit Control / Visit and Search Exposure / Charterparty, Insurance and Boarding-Response Risk
Latest DeepDraft Analysis
When Bridge Windows Look the Wrong Way
Related DeepDraft Articles & Analysis
Sources
JMIC, UKMTO, Reuters, Maersk, The DeepDraft
This update is part of the DeepDraft SITREP series covering developing maritime operational situations.
Leave a Reply