INTELLIGENCE.NAVYA portal by Maritime IntelligenceBack to In FocusPrivate intelligence environments · In preparation
THEATRE DOSSIER / HISTORICAL VERSION 6

Strait of Hormuz / Arabian Gulf

Operating indicators, linked cases and evidence-led collection priorities.

Version recorded 14 Oct 2026 · 22:30 UTC. Related source records show their available archive versions.

Links use the site’s current access permissions.
STATUS ELEVATEDTREND SHIFTINGCONFIDENCE MODERATE

Individual evidence review 14 Oct 2026 · 22:18 UTC · Collection 17 Oct 2026 · 22:59 UTC

HISTORICAL ASSESSMENT

The intelligence significance is not that container shipping had previously been risk-free. It is that the threat has now produced a confirmed sinking within the feeder segment that distributes cargo between Gulf hubs and regional ports. Recent maritime risk reporting has focused heavily on crude, products and LNG. GFS PRIDE demonstrates that the same operating environment can generate direct losses and recovery problems for container services whose strategic role lies in regional connectivity rather than energy carriage.

HIGH confidence in the sinking and crew outcome, confirmed by MPA. Attribution, dangerous cargo and pollution remain intelligence gaps.

Key judgments

  1. The loss of one 2,824-TEU feeder does not create a system-wide capacity shortage. It does confirm that Hormuz risk now includes direct physical loss, schedule disruption, salvage exposure and higher insurance uncertainty within the regional feeder network. The strategic consequence is therefore larger than the capacity of one hull, but it should not be overstated as a general breakdown of Gulf container connectivity.
Editorial geospatial reconstruction based on reported navigation-warning positions. The connecting line represents the approximate displacement between two reported positions, not a continuously observed vessel track.STATIC EVIDENCE MAP

Editorial geospatial reconstruction based on reported navigation-warning positions. The connecting line represents the approximate displacement between two reported positions, not a continuously observed vessel track.

Previous baseline

The source record alone resembles the preceding outbound-tanker report closely enough to create a duplication risk. Chronology and outcome wording separate them: ALERT 136/26 concerns 19:20 UTC on 10 October and reports a fire with environmental impact unknown; ALERT 137/26 concerns 12:00 UTC on 11 October, reports vessel damage without a fire statement, and says no environmental impact was reported. UKMTO WARNING 164-26 confirms that the later report originated with a company security officer, but adds no vessel identity, coordinates or post-incident movement. UKMTO ADVISORY 163-26 is a separate Gulf of Oman tanker-and-military-forces notice and cannot be merged with this Hormuz projectile report or with Ocean Molica without an authoritative identity link. Outbound tanker operators face a continuing short-interval projectile threat and should sustain enhanced bridge watch, damage-control readiness, redundant navigation checks and rapid reporting through the Hormuz transit. The crew-safe and no-environmental-impact statements narrow the immediate casualty and pollution picture only at the reporting time; they do not establish intact propulsion, cargo containment or safe onward passage. The portal still recorded one inbound and two outbound crossings for the partial day, which shows observed passage rather than normal corridor conditions or any link to the casualty.

What changed

GFS PRIDE SINKING BROADENS THE HORMUZ THREAT FROM ENERGY SHIPPING TO REGIONAL TRADE CONNECTIVITY

Maritime operating picture

Source-reported encounters, local vessel condition and regional access are separate layers. 12 source accounts with open follow-up questions fall within the last seven days. They may concern the same event; missing follow-up does not establish that an incident remains active.

Open Hormuz baseline indicatorsOpen this theatre on the map

Critical nodes

Strait of Hormuz
Gulf access and energy transit depend on this passage.

Gulf energy terminals
Loading continuity must be checked separately from transit counts.

Musandam approaches
Connect the strait with the Gulf of Oman; reported positions can be approximate.

Relevant actors

Maritime reporting centres
Publish vessel accounts and navigation guidance; a notice is not an independent observation.

Coastal authorities
Confirm passage rules, casualty status and response coordination.

Ship operators and insurers
Operator decisions and dated cover conditions can test wider corridor effects.

Environmental exposure

A casualty can create a release pathway. No spill extent, coastal exposure or drift is inferred without a verified discharge and time-matched observations.

Sanctions & insurance

No verified current premium, P&I change or sanctions-impact metric is attached to this dossier. Source reporting and designated-vessel identity need separate verification.

Indicators & watch next

  • Authoritative vessel-status updates and confirmed release or damage.
  • Dated passage restrictions and named-operator route changes.
  • Sustained AIS crossing changes over complete, comparable UTC windows.

Trigger: a dated authority update or a verified operational change that alters the baseline. Unobserved indicators have no assigned direction or warning score.

Intelligence gaps

  • precise incident time;
  • weapon type, launch point and attribution;
  • whether either vessel was deliberately selected;
  • Coverage of pollution, insurance and AIS-independent physical traffic is incomplete.

Material-change timeline

14 Oct 2026 · 22:18 UTCGFS PRIDE SINKING BROADENS THE HORMUZ THREAT FROM ENERGY SHIPPING TO REGIONAL TRADE CONNECTIVITY

The loss of one 2,824-TEU feeder does not create a system-wide capacity shortage. It does confirm that Hormuz risk now includes direct physical loss, schedule disruption, salvage exposure and higher insurance uncertainty within the regional feeder network. The strategic consequence is therefore larger than the capacity of one hull, but it should not be overstated as a general breakdown of Gulf container connectivity.

11 Oct 2026 · 18:11 UTCALERT 137/26 extends outbound-tanker exposure into 11 October, but remains vessel-anonymous and single-chain reported

MSCIO ALERT 137/26 is best treated provisionally as a later incident report at 12:00 UTC on 11 October, distinct from ALERT 136/26 at 19:20 UTC on 10 October. UKMTO WARNING 164-26 reproduces the later time, outbound direction, port-side impact, damage, crew-safe status and no reported environmental impact from a company security officer, so MSCIO and UKMTO represent one reporting chain rather than independent confirmation. The record extends the observed hazard window for outbound tankers, but it does not identify the vessel, establish attribution, confirm its ability to proceed or demonstrate closure of the Strait.

11 Oct 2026 · 09:02 UTCALERT 136/26 adds a later outbound-tanker strike, but not a vessel identity or independent confirmation

MSCIO ALERT 136/26 is best treated as a new, vessel-anonymous incident at 19:20 UTC on 10 October, not as an update to the 9 October Al Jazeera/Gem No.2 case. UKMTO WARNING 162-26 reproduces the same time, direction, impact side, fire and crew status from the master, so the two notices describe one reporting chain rather than two independently confirmed attacks. The safe-crew report reduces the immediate casualty concern, but the unresolved fire, damage, propulsion and pollution status leave the tanker’s operational outcome open.

09 Oct 2026 · 17:34 UTCHormuz tanker strike: casualty exposure before corridor disruption

This report warrants vessel-level casualty and containment follow-up. It supports an additional dated exposure signal for Hormuz, but a corridor disruption judgment requires evidence of restrictions or sustained operating changes.

06 Oct 2026 · time not suppliedHormuz tanker attack puts casualty control and regional response on the same clock

The intelligence significance lies in the interval between the attack and confirmation of a stable vessel.

How this dossier is updated
  1. Public readers use the existing hourly collection cycle and five-minute refresh while the main watch is open. Unavailable readers retain dated records.
  2. Records are linked by named area, explicit theatre tag or reported position. Approximate positions remain labelled. Shared geography does not duplicate the article or establish a shared incident.
  3. Reviewed case judgments feed the dossier. Event confidence, editorial priority and a theatre-wide threat rating remain separate.
  4. Changed evidence, corrections and analytical states enter the version history. A repeated source check does not become a new analytical review.
  5. Open gaps guide the research queue. New substantive assessments follow the existing research stages and human publication approval.
Assessment versions & corrections

Changed analytical states are preserved from activation, up to the latest 60 versions. A collection check does not create a revision when the assessment is unchanged. Source-publication versions remain in the existing archive.

v20 · 17 Oct 2026 · 22:31 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv19 · 17 Oct 2026 · 20:05 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv18 · 17 Oct 2026 · 15:56 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv17 · 17 Oct 2026 · 08:18 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv16 · 16 Oct 2026 · 19:55 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv15 · 16 Oct 2026 · 19:08 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv14 · 16 Oct 2026 · 17:05 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv13 · 16 Oct 2026 · 10:07 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv12 · 16 Oct 2026 · 06:16 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv11 · 15 Oct 2026 · 19:58 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv10 · 15 Oct 2026 · 17:39 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv9 · 15 Oct 2026 · 12:15 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv8 · 15 Oct 2026 · 11:13 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv7 · 15 Oct 2026 · 10:37 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv6 · 14 Oct 2026 · 22:30 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv5 · 12 Oct 2026 · 20:18 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv4 · 09 Oct 2026 · 17:56 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv3 · 09 Oct 2026 · 09:03 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv2 · 08 Oct 2026 · 18:55 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv1 · 08 Oct 2026 · 18:55 UTC · INITIAL ASSESSMENT · archive begins here
Related source records · 68gCaptain · 17 Oct 2026 · 14:44 UTCIran’s Guards Say Two Tankers Hit Mines In Strait Of HormuzMSCIO · 2026-10-17 08:17 · source timezone unspecifiedAttack notification puts Hormuz & Arabian Gulf on the maritime watchMSCIO · 2026-10-17 08:15 · source timezone unspecifiedTanker struck by unidentified projectile in Hormuz & Arabian GulfgCaptain · 16 Oct 2026 · 18:53 UTCFog of War Deepens in Hormuz as UKMTO Says Most Ship Attacks Go UnreportedgCaptain · 16 Oct 2026 · 15:50 UTCIEA Moves to Accelerate Oil Reserve Releases as Hormuz Crisis Drags OngCaptain · 16 Oct 2026 · 12:07 UTCSingapore fuel deliveries qualify the HSFO squeeze: procurement risk is grade- and port-specificSplash 247 · 16 Oct 2026 · 07:45 UTCSplash Wrap: A missile from RiyadhBBC · 16 Oct 2026 · 05:00 UTCShip attack reports near Hormuz reach record high as oil exports slowThe Maritime Executive · 14 Oct 2026 · 22:51 UTCU.S. Forces Destroy a Dhow Suspected of Conducting Surveillance for IranNYT · 14 Oct 2026 · 18:20 UTCAttacks on Ships in Strait of Hormuz Escalate SharplyBBC · 14 Oct 2026 · 15:34 UTCContainer ship hit by projectile sinks in Strait of Hormuz, Singapore saysThe Maritime Executive · 14 Oct 2026 · 14:47 UTCIran Claims Containership Hit Mine and Sank in Strait of Hormuz

Assessment source references

  1. MPA Singapore · two Singapore-registered vessels struckAttributed source
  2. HYDROPAC 2978/26 · initial fire/adrift warning (cancelled)Attributed source
  3. HYDROPAC 2981/26 · GFS PRIDE sunkAttributed source
  4. HYDROPAC 2982/26 · containers adriftAttributed source
  5. Reuters · GFS PRIDE and separate Cape Dao casualtyContext reference
  6. AD Ports Group · ownership and feeder-network contextAttributed source
  7. IMO · Middle East highlighted incidents · board as at 14 October 2026Context reference
  8. Reuters Connect · corrected Copernicus Sentinel-2 handout captionContext reference · 14 Oct 2026 · time not supplied
  9. MTCIT warning, attributed by Times of Oman · 16 October 2026Context reference · 16 Oct 2026 · time not supplied
  10. Oman Maritime Law · Royal Decree 19/2023, Article 185Attributed source · 30 Mar 2023 · time not supplied
  11. Ministry of Health capability, reported by Times of Oman · 15 October 2026Context reference · 15 Oct 2026 · time not supplied
  12. MSCIO ALERT 137/26 — Attack reported in Hormuz & Arabian GulfAttributed source
  13. UKMTO · UKMTO 156-26Context reference · 05 Oct 2026 · time not supplied
  14. MSCIO ALERT 136/26 — Attack reported in Hormuz & Arabian GulfAttributed source
  15. MARAD · 2026-011Context reference · 09 Sept 2026 · time not supplied
  16. Intelligence.Navy Hormuz AIS traffic snapshotContext reference
  17. MSCIO ALERT 135/26 — 9 October incident west of Al JazeeraContext reference
  18. MSCIO · ALERT 134/26 · retained notice and dated prior assessmentAttributed source
  19. UKMTO WARNING 159-26 · 6 October 2026, 1709 UTCContext reference
  20. JMIC · Update 104 to Advisory Note · 11 October 2026 · ICOD 15:00 UTCContext reference
  21. MSCIOAttributed source · 2026-10-05 19:57 · source timezone unspecified
  22. EIA · World Oil Transit ChokepointsContext reference · 03 Mar 2026 · time not supplied
  23. IMO · Preparing for marine pollution incidentsContext reference
  24. Reuters · Oman tanker pollution comparatorContext reference · 12 Aug 2026 · time not supplied
  25. JMIC · Public maritime information productsContext reference
  26. Global Fishing Watch · AIS data caveatsContext reference
  27. Reuters · Reuters reports a higher weekly concentration of tanker attacks in HormuzContext reference · 07 Oct 2026 · time not supplied
  28. BBC · Three reasons Middle East oil supply is nearly back to pre-Iran war levelsContext reference · 02 Oct 2026 · 15:29 UTC
  29. NYT · Oil Flows Are Up, but Iran Is Still Menacing the Strait of HormuzContext reference · 02 Oct 2026 · time not supplied

AI-assisted synthesis of dated case evidence. No separate human analyst sign-off or theatre-wide risk rating. Node and actor profiles explain strategic relevance; they do not disclose live asset status.