INTELLIGENCE.NAVYA portal by Maritime IntelligenceBack to In Focus
THEATRE DOSSIER / HISTORICAL VERSION 7

Gulf of Oman / Musandam

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

Version recorded 16 Oct 2026 · 17:58 UTC. Related source records show their available archive versions.

Links use the site’s current access permissions.
DOCUMENTED CASUALTYRECENT EVIDENCE REVIEWTrend · NOT ESTABLISHED
PARTIAL COLLECTIONSources checked 16 Oct 2026 · 17:58 UTCEvidence review 16 Oct 2026 · 16:58 UTCLatest source evidence 15 Oct 2026 · time not supplied

A confirmed casualty is documented in this theatre. The label describes local exposure, not a corridor-wide threat score.

Reports to follow up · 7D
12
Accounts, not unique incidents
Reviewed products · 7D
3
Case-level analytical updates
Evidence gaps
1 / 4
Operating dimensions to verify
HISTORICAL ASSESSMENT

The MTCIT-attributed warning adds a reported handling hazard near Ras Al Sheikh Masoud to the existing containers-adrift picture. It supports local avoidance and authority-led follow-up, not a finding of chemical discharge, a defined exclusion zone or regional closure. The original ministerial notice was not retrieved. [E4, E5, E6] 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. 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. GFS PRIDE adds direct container-feeder exposure and a reported wreck/containers hazard. Regional connectivity effects remain unmeasured; attribution, environmental condition and casualty-specific satellite linkage remain open.

Confidence belongs to individual claims and cases below. No separately reviewed theatre-wide threat rating or comparable trend baseline is attached; event confidence is not inherited by the whole region.

No comparable, independently reviewed theatre baseline establishes improving or deteriorating conditions. A new source report or review date alone does not demonstrate a trend.

EVIDENCE → IMPLICATION → NEXT DECISION

Operating indicators

Evidence states, not live sensor readings or a regional risk score. Each indicator states what would change the judgment.

Security & vessel condition

DOCUMENTED

A confirmed casualty establishes physical exposure at vessel level. This does not establish attack attribution, corridor closure or the condition of every transit.

Evidence · ALERT 146/2613 Oct 2026 · 17:00 UTCEvidence · ALERT 145/2613 Oct 2026 · 16:40 UTCEvidence · ALERT 144/2613 Oct 2026 · time not supplied
Collection requirement & decision trigger

Collect · A dated authority or operator update matching vessel identity and event time; reconcile related notices and follow-up.

Revise when · Confirmed damage, assistance, release or a formal navigation restriction changes the vessel-level assessment.

Navigation & recovery

DATED EVIDENCE

Baseline: HYDROPAC warnings on 14 October reported the wreck and containers adrift. Their current validity or clearance must be checked against the revised assessment; the original warning is not a live hazard feed.

Evidence · IN-HOR-IA-2026-1014-0113 Oct 2026 · time not supplied
Collection requirement & decision trigger

Collect · Check the latest warning revision or cancellation, wreck stability and the authority responsible for container recovery.

Revise when · A revised hazard position, warning cancellation or verified recovery outcome changes the navigation picture.

Trade & feeder connectivity

GAP

Loss of a feeder hull creates direct schedule, salvage and cargo exposure. The record does not quantify network-wide capacity loss, port closure or regional service disruption.

Evidence · IN-HOR-IA-2026-1014-0113 Oct 2026 · time not supplied
Collection requirement & decision trigger

Collect · Dated named-operator schedule changes, port notices, missed calls or comparable traffic windows; verify insurance conditions separately.

Revise when · A confirmed service suspension, port restriction or sustained comparable routing change would support a wider connectivity judgment.

Environment & observation

REVIEWED ANALYSIS

Case analysis reviewed 2026-10-16 · Analytical inference · IMO's no-pollution entry is dated 14 October. The later warning does not document breached packaging, contamination, exposure measurements or coastal impact. Treat the cargo-hazard report and the environmental condition separately rather than converting one into the other. Reported · MPA's casualty account remains the anchor for sinking and crew outcome. The later Omani reports date the sinking to 14 October; MPA dates the strike to 13 October Singapore time. Strike, sinking and publication are different milestones; no precise sinking time is established here.

Evidence · IN-HOR-IA-2026-1014-0113 Oct 2026 · time not supplied
Collection requirement & decision trigger

Collect · The original MTCIT notice, issue time, technical basis and current revisions were not retrieved; media accounts share a single claimed origin. Dangerous-goods classes, UN numbers, quantities, packaging condition and specific container identities remain unavailable.

Revise when · Retrieve the original dated MTCIT notice and its revisions, contact details and any formal recovery or navigation directions.

LINKED INCIDENTS / CASE FOLLOW-UP

Cases in this theatre

SOURCE REPORT · FOLLOW-UP OPENAPPROXIMATE POSITION
Attack notification puts Hormuz & Arabian Gulf on the maritime watchEvent / record date · 13 Oct 2026 · 17:00 UTC · Case confidence LOW

ALERT 146/26 MSCIO has received a time-late report of an attack at approximately 17:00 UTC on 13 October 2026 in the Strait of Hormuz.

Source position falls within the broad Musandam / Gulf of Oman approaches. This is a selection area, not a jurisdictional boundary.
SOURCE REPORT · FOLLOW-UP OPENAPPROXIMATE POSITION
Container ship struck by unidentified projectile in Hormuz & Arabian GulfEvent / record date · 13 Oct 2026 · 16:40 UTC · Case confidence LOW

ALERT 145/26 MSCIO has received a time-late report regarding an incident at approximately 16:40 UTC on 13 October 2026 in the Strait of Hormuz.

Source position falls within the broad Musandam / Gulf of Oman approaches. This is a selection area, not a jurisdictional boundary.
SOURCE REPORT · FOLLOW-UP OPENAPPROXIMATE POSITION
Tanker struck by unidentified projectile in Hormuz & Arabian GulfEvent / record date · 13 Oct 2026 · time not supplied · Case confidence LOW

ALERT 144/26 MSCIO has received information regarding an incident on 13 October 2026 in the Strait of Hormuz.

Source position falls within the broad Musandam / Gulf of Oman approaches. This is a selection area, not a jurisdictional boundary.
SOURCE REPORT · FOLLOW-UP OPENAPPROXIMATE POSITION
Container ship struck by unidentified projectile in Hormuz & Arabian GulfEvent / record date · 13 Oct 2026 · time not supplied · Case confidence LOW

ALERT 143/26 MSCIO has received information regarding an incident on 13 October 2026 in the Strait of Hormuz.

Source position falls within the broad Musandam / Gulf of Oman approaches. This is a selection area, not a jurisdictional boundary.
CONFIRMED SINKING · HAZARD FOLLOW-UPEXPLICIT TAG
GFS PRIDE: reported hazardous containers sharpen the local response requirement off MusandamEvent / record date · 13 Oct 2026 · time not supplied · Case confidence MODERATE

The MTCIT-attributed warning adds a reported handling hazard near Ras Al Sheikh Masoud to the existing containers-adrift picture. It supports local avoidance and authority-led follow-up, not a finding of chemical discharge, a defined exclusion zone or regional closure. The original ministerial notice was not retrieved. [E4, E5, E6]

Explicit Musandam / Gulf of Oman theatre tag; shared with Hormuz where appropriate.
SOURCE REPORT · FOLLOW-UP OPENAPPROXIMATE POSITION
Crude oil tanker struck by unidentified projectile in Hormuz & Arabian GulfEvent / record date · 11 Oct 2026 · time not supplied · Case confidence LOW

ALERT 142/26 MSCIO has received a time-late report regarding an incident on 11 October 2026 in the Strait of Hormuz.

Source position falls within the broad Musandam / Gulf of Oman approaches. This is a selection area, not a jurisdictional boundary.
SOURCE REPORT · FOLLOW-UP OPENAPPROXIMATE POSITION
Tanker struck by unidentified projectile in Hormuz & Arabian GulfEvent / record date · 11 Oct 2026 · time not supplied · Case confidence LOW

ALERT 141/26 MSCIO has received a time-late report regarding an incident on 11 October 2026 in the Strait of Hormuz.

Source position falls within the broad Musandam / Gulf of Oman approaches. This is a selection area, not a jurisdictional boundary.
SOURCE REPORT · FOLLOW-UP OPENAPPROXIMATE POSITION
Container vessel struck by unidentified projectile in Hormuz & Arabian GulfEvent / record date · 11 Oct 2026 · time not supplied · Case confidence LOW

ALERT 140/26 MSCIO has received a time-late report regarding an incident on 11 October 2026 in the Strait of Hormuz.

Source position falls within the broad Musandam / Gulf of Oman approaches. This is a selection area, not a jurisdictional boundary.
Shared approaches · Hormuz / Arabian Gulf ↗Southern Oman / Caroline Bezengi dossier ↗

Key judgments

  1. The MTCIT-attributed warning adds a reported handling hazard near Ras Al Sheikh Masoud to the existing containers-adrift picture. It supports local avoidance and authority-led follow-up, not a finding of chemical discharge, a defined exclusion zone or regional closure. The original ministerial notice was not retrieved. [E4, E5, E6]
  2. 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.
  3. 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.
  4. GFS PRIDE adds direct container-feeder exposure and a reported wreck/containers hazard. Regional connectivity effects remain unmeasured; attribution, environmental condition and casualty-specific satellite linkage remain open.
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.

Original report · Intelligence.NavyIntelligence.Navy · reconstruction from HYDROPAC 2978/26, 2981/26 and 2982/26Reuse terms

Previous baseline

The MTCIT-attributed warning adds a reported handling hazard near Ras Al Sheikh Masoud to the existing containers-adrift picture. It supports local avoidance and authority-led follow-up, not a finding of chemical discharge, a defined exclusion zone or regional closure. The original ministerial notice was not retrieved. [E4, E5, E6] 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. 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. GFS PRIDE adds direct container-feeder exposure and a reported wreck/containers hazard. Regional connectivity effects remain unmeasured; attribution, environmental condition and casualty-specific satellite linkage remain open.

What changed

GFS PRIDE: reported hazardous containers sharpen the local response requirement off Musandam

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 this theatre on the map

Critical nodes

Musandam approaches
The reported GFS PRIDE wreck position links this dossier with Hormuz; this is one casualty, not a second incident.

Gulf of Oman ports and approaches
Access, response and container connections require dated operator or authority evidence.

Relevant actors

Omani maritime and environmental authorities
Dated notices establish local restrictions and response responsibilities.

Navigation-warning services and ship operators
Separate a reported hazard position from verified clearance or service continuity.

Environmental exposure

Case analysis reviewed 2026-10-16 · Analytical inference · IMO's no-pollution entry is dated 14 October. The later warning does not document breached packaging, contamination, exposure measurements or coastal impact. Treat the cargo-hazard report and the environmental condition separately rather than converting one into the other. Reported · MPA's casualty account remains the anchor for sinking and crew outcome. The later Omani reports date the sinking to 14 October; MPA dates the strike to 13 October Singapore time. Strike, sinking and publication are different milestones; no precise sinking time is established here.

Sanctions & insurance

No verified current premium, P&I change or sanctions-impact metric is attached. Vessel designation, insurance terms and operational effects require separate dated evidence.

Indicators & watch next

  • Retrieve the original dated MTCIT notice and its revisions, contact details and any formal recovery or navigation directions.
  • Obtain container identities, cargo declarations/IMDG classes and dated inspections of packaging and containment.
  • Check official warning revision/cancellation against physical recovery status; message expiry alone is not clearance.
  • Seek a named authority/salvor appointment and a dated recovery log, with quantities and locations.
  • A new or cancelled navigation warning for the GFS PRIDE wreck and drifting containers.
  • A dated authority or salvor update on wreck stability and container recovery.
  • Cargo documentation and time-matched observations if pollution is suspected.

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

  • The original MTCIT notice, issue time, technical basis and current revisions were not retrieved; media accounts share a single claimed origin.
  • Dangerous-goods classes, UN numbers, quantities, packaging condition and specific container identities remain unavailable.
  • No current pollution survey, confirmed cargo/bunker release, drift field, wreck stability report or recovery appointment was obtained.
  • Reporting telephone numbers differ across secondary versions; no unverified emergency number is endorsed in this draft.
  • Casualty-specific satellite linkage, attribution and direct HUMINT remain unverified; no image is treated as evidence here.
  • No measured network disruption, current insurance premium change or actual operator suspension is established.
  • Theatre-wide traffic, insurance and environmental coverage are incomplete. No direct HUMINT has been collected for this dossier.

Material-change timeline

16 Oct 2026 · 16:58 UTCGFS PRIDE: reported hazardous containers sharpen the local response requirement off Musandam

UPDATED · HUMAN REVIEW · 2026-10-16 · The MTCIT-attributed warning adds a reported handling hazard near Ras Al Sheikh Masoud to the existing containers-adrift picture. It supports local avoidance and authority-led follow-up, not a finding of chemical discharge, a defined exclusion zone or regional closure. The original ministerial notice was not retrieved. [E4, E5, E6]

12 Oct 2026 · 20:18 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.

12 Oct 2026 · 20:18 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.

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.

Unavailable readers represented here: UKMTO. Retained records may predate the latest check.

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.

v8 · 16 Oct 2026 · 19:08 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv7 · 16 Oct 2026 · 17:58 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv6 · 16 Oct 2026 · 17:05 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv5 · 16 Oct 2026 · 10:07 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv4 · 15 Oct 2026 · 19:58 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv3 · 15 Oct 2026 · 11:13 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv2 · 09 Oct 2026 · 09:03 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv1 · 08 Oct 2026 · 18:55 UTC · INITIAL ASSESSMENT · archive begins here
Related source records · 51MSCIO · 2026-10-14 11:04 · source timezone unspecifiedAttack notification puts Hormuz & Arabian Gulf on the maritime watchMSCIO · 2026-10-14 11:01 · source timezone unspecifiedContainer ship struck by unidentified projectile in Hormuz & Arabian GulfMSCIO · 2026-10-14 06:52 · source timezone unspecifiedTanker struck by unidentified projectile in Hormuz & Arabian GulfMSCIO · 2026-10-14 06:44 · source timezone unspecifiedContainer ship struck by unidentified projectile in Hormuz & Arabian GulfIntelligence.Navy · 14 Oct 2026 · time not suppliedHazardous containers adrift off Musandam turn GFS PRIDE from a shipping casualty into a multi-hazard maritime response problemMSCIO · 2026-10-13 06:46 · source timezone unspecifiedCrude oil tanker struck by unidentified projectile in Hormuz & Arabian GulfMSCIO · 2026-10-13 06:44 · source timezone unspecifiedTanker struck by unidentified projectile in Hormuz & Arabian GulfMSCIO · 2026-10-13 06:41 · source timezone unspecifiedContainer vessel struck by unidentified projectile in Hormuz & Arabian GulfMSCIO · 2026-10-13 06:38 · source timezone unspecifiedTanker struck by unidentified projectile in Hormuz & Arabian GulfMSCIO · 2026-10-12 07:40 · source timezone unspecifiedAttack notification puts Indian Ocean on the maritime watchMSCIO · 2026-10-11 17:06 · source timezone unspecifiedALERT 137/26 extends outbound-tanker exposure into 11 October, but remains vessel-anonymous and single-chain reportedMSCIO · 2026-10-11 08:20 · source timezone unspecifiedALERT 136/26 adds a later outbound-tanker strike, but not a vessel identity or independent confirmation

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 confirmed incidentsContext 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. MSCIOAttributed source · 2026-10-08 14:57 · source timezone unspecified
  19. EIA · World Oil Transit Chokepoints · March 2026 review; 1H25 baselineContext reference · 03 Mar 2026 · time not supplied
  20. IEA · Middle East Maritime Chokepoints Shipping Monitor · 16 September 2026 editionContext reference · 16 Sept 2026 · time not supplied
  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.

INTELLIGENCE.NAVYA portal by Maritime Intelligence

Public sources. Clear provenance. Informed human judgment.

Naval intelligence · Satellite intelligence · Publication archive · Follow via RSS
Maritime Intelligence · MaritimeIntelligence.orgLinked to Geopolitics FoundationAbout the portal© 2026 INTELLIGENCE.NAVY
Gulf of Oman / Musandam theatre dossier | Intelligence.Navy