Hormuz remained technically passable, but the commercial operating chain tightened again.
Visible commodity traffic fell to two crossings, merchant ships suffered further attacks with crew casualties, war-risk costs increased, and Gulf of Oman ship-to-ship capacity reached its limit as additional crude volumes were pushed through the Strait. For masters, operators, charterers and insurers, passage now depends on whether security approval, insurance, receiving tonnage and marine-service capacity can all be aligned on the same voyage plan.
That question of operational clarity also runs through this week’s DeepDraft analysis. A ship can meet the formal requirements for navigation lights and still become difficult for another bridge team to interpret when working, accommodation or security lighting overwhelms the prescribed visual picture.
Weekly Analysis
Navigating in a Sea of Visual Pollution
The week’s flagship analysis examines a familiar bridge problem that receives less attention than individual navigation-light defects: the complete light profile of a vessel at sea.
COLREG navigation lights are designed to communicate aspect and movement quickly. That function weakens when deck lighting, container access lights, passenger-vessel illumination, powerful fishing lights or continuous security lighting compete with the prescribed lights. A vessel may therefore be highly visible while still taking longer to understand from another bridge.
The operational consequence goes directly to lookout, safe speed, collision assessment and the time available for avoiding action. The casualty record discussed in the analysis shows that excessive deck or working lighting has previously made vessel aspect and navigation lights harder to distinguish. The issue matters to masters and bridge teams, but also to ship managers, vetting departments, Port State Control and regulators because inspection regimes generally examine individual navigation-light compliance more closely than the ship’s complete appearance under normal sea-passage conditions.
Full analysis available on DeepDraft:
This Week in Maritime: Timeline of Escalation
September 22 — LR STEPHANIE Hit During Hormuz Transit
LR STEPHANIE was confirmed damaged during an inbound Strait of Hormuz transit, with two seafarers injured and no pollution reported. The vessel remained under its own power, keeping the immediate focus on crew safety, transit approval, war-risk review and preservation of bridge and voyage evidence rather than disabled-vessel response.
September 23 — Hormuz Commodity Traffic Falls to Two Crossings
Visible commodity traffic dropped to two reported crossings as Iran offered a conditional seven-day reopening and Saudi Arabia restored part of its western export bypass. Operators were left assessing three imperfect routes: restricted Hormuz passage, conditional reopening arrangements or limited alternative export capacity.
September 24 — CAPE DAO Attack Raises the Crew-Risk Level
The bulk carrier CAPE DAO was attacked off Oman’s Musandam Governorate, causing an engine-room fire and killing one crew member; 27 people were evacuated. The casualty reinforced that Hormuz remained a direct seafarer-safety problem even while diplomatic and commercial efforts focused on restoring traffic.
September 25 — Reopening Talks Meet Higher War-Risk Exposure
US and Iranian negotiators were reported to be examining a phased reopening arrangement, while dozens of countries pressed for restoration of passage. At the same time, Saudi-linked tanker war cover on alternative Red Sea routing increased sharply, leaving commercial planners to compare conditional Gulf access against increasingly expensive diversion exposure.
September 26 — Gulf of Oman STS Capacity Reaches Its Limit
Gulf of Oman crude-transfer capacity reached practical limits as higher Saudi export volumes increased demand for receiving tonnage and marine services. DeepDraft cited estimates that the additional flow could require roughly 36–40 more VLCCs, while transfer cycles around the Gulf of Oman had stretched toward ten days and buyers began examining alternative STS locations around India and Malaysia.
Full Live Wire coverage for the week:
DeepDraft Live Wire / SITREP archive
Additional Maritime Context
The Gulf was not the week’s only active crew-security file. Puntland maritime forces freed the Eritrea-flagged, US-sanctioned tanker Sibu 1 after a counter-piracy operation off Somalia. Reporting citing Puntland authorities said all 20 crew members were safe. The case keeps Gulf of Aden and Somali Basin piracy preparedness relevant even while attention remains concentrated on Hormuz.
At the UN, Indian External Affairs Minister S. Jaishankar and Liberia announced a Group of Friends focused on the safety and security of shipping and seafarers. Jaishankar cited attacks affecting commercial shipping across the Gulf, Red Sea and Black Sea and called for them to stop, adding a formal seafarer-security track to the wider diplomatic response.
Weekly Maritime Insight
The main operational implication is that Hormuz access, marine security, insurance and transfer infrastructure now have to be managed as one voyage-execution problem. A route may be physically available while the voyage remains commercially constrained by war-risk approval, receiving-vessel availability, STS slots, tug and equipment capacity, or rapidly changing operating instructions.
The risk carrying into next week is operational ambiguity. The week’s security picture and the flagship navigation analysis arrive at the same practical point from different directions: formal availability or compliance has limited value unless the situation can also be interpreted and executed safely by the people responsible for the ship.
This report is part of the DeepDraft Weekly Maritime Brief series tracking operational, regulatory, and security developments across global shipping.
Leave a Reply