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

Red Sea / Bab el-Mandeb

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

Version recorded 15 Oct 2026 · 15:37 UTC. Related source records show their available archive versions.

Links use the site’s current access permissions.
SOURCE SIGNALSREVIEW DUETrend · NOT ESTABLISHED
PARTIAL COLLECTIONSources checked 15 Oct 2026 · 15:37 UTCEvidence review 07 Oct 2026 · 18:54 UTCLatest source evidence 15 Oct 2026 · 09:55 UTC

The collection does not establish the current operating condition. No recent account is not evidence of safe passage or a closed casualty.

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

The principal intelligence question is whether the vessel has returned to normal movement or requires assistance.

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

DATED EVIDENCE

Current vessel condition is not established by the retained case evidence.

No supporting current observation attached.
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

GAP

No current theatre-wide hazard-clearance or recovery status has been verified in the attached assessments.

No supporting current observation attached.
Collection requirement & decision trigger

Collect · Obtain current navigation notices, casualty follow-up and relevant salvage confirmation.

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

Trade & feeder connectivity

GAP

Regional access, service reliability and insurance conditions cannot be measured from incident-notice counts.

No supporting current observation attached.
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

GAP

A current release, footprint and coastal exposure are not established by this collection.

No supporting current observation attached.
Collection requirement & decision trigger

Collect · A dated authority statement, cargo information and geolocated repeat observations with acquisition time, sensor and metocean context.

Revise when · Verified discharge or clearance, repeat discriminated observations or confirmed coastal impact would change response priorities.

LINKED INCIDENTS / CASE FOLLOW-UP

Cases in this theatre

DATED CASE · OUTCOME TO RECHECKEXPLICIT TAG
Close-range Red Sea encounter leaves onward vessel status unresolvedEvent / record date · 07 Oct 2026 · 06:15 UTC · Case confidence MODERATE

The principal intelligence question is whether the vessel has returned to normal movement or requires assistance.

Explicit theatre tag in the publication record.
DATED CASE · OUTCOME TO RECHECKEXPLICIT TAG
Suspicious Activity notification puts Red Sea & Gulf of Aden on the maritime watchEvent / record date · 04 Oct 2026 · 16:50 UTC · Case confidence LOW

ALERT 126/26 MSCIO has received information regarding an incident at approximately 16:50 UTC on 4 October 2026, 60NM south of Al Mukha, Yemen.

Explicit theatre tag in the publication record.
DATED CASE · OUTCOME TO RECHECKEXPLICIT TAG
Piracy notification puts Red Sea & Gulf of Aden on the maritime watchEvent / record date · 2026-09-28 13:52 · source timezone unspecified · Case confidence LOW

ALERT 98/26 MSCIO has received information regarding an incident 136NM east of Al Mukalla, Yemen, in the Gulf of Aden.

Explicit theatre tag in the publication record.
DATED CASE · OUTCOME TO RECHECKEXPLICIT TAG
Suspicious Activity notification puts Red Sea & Gulf of Aden on the maritime watchEvent / record date · 17 Sept 2026 · 13:59 UTC · Case confidence LOW

ALERT 111/26 MSCIO has received information regarding an incident at approximately 13:59 UTC on 17 September 2026, 75NM east of Aden, Yemen.

Explicit theatre tag in the publication record.
CLOSURE REPORTEDEXPLICIT TAG
Source reports resolution or release following ALERT 107/26 in Red Sea & Gulf of AdenEvent / record date · 10 Sept 2026 · 09:18 UTC · Case confidence LOW

ALERT 107/26 MSCIO has received information regarding a piracy incident at approximately 09:18 UTC on 10 September 2026, 38NM southwest of Balhaf, Yemen.

Explicit theatre tag in the publication record.
DATED CASE · OUTCOME TO RECHECKEXPLICIT TAG
Hijacking reported · Around 136nm East of Mukalla, Gulf of AdenEvent / record date · 20 Aug 2026 · time not supplied · Case confidence LOW

IMB 047-26 records hijacking reported involving a tanker in Around 136nm East of Mukalla, Gulf of Aden on 2026-08-20.

Explicit theatre tag in the publication record.
DATED CASE · OUTCOME TO RECHECKEXPLICIT TAG
Cargo vessel struck by unidentified projectile in Red Sea & Gulf of AdenEvent / record date · 17 Aug 2026 · 11:00 UTC · Case confidence LOW

ALERT 97/26 MSCIO has received information regarding an incident at approximately 11:00 UTC on 17 August 2026, approximately 40NM southeast of Al Mukha, Yemen.

Explicit theatre tag in the publication record.
DATED CASE · OUTCOME TO RECHECKEXPLICIT TAG
Attack notification puts Red Sea & Gulf of Aden on the maritime watchEvent / record date · 11 Aug 2026 · time not supplied · Case confidence LOW

ALERT 90/26 MSCIO has received information regarding an attack on a Tanzania-flagged cargo vessel off Al Mokha, Yemen, in the Southern Red Sea, on 11 August 2026.

Explicit theatre tag in the publication record.

Key judgments

  1. The principal intelligence question is whether the vessel has returned to normal movement or requires assistance.
Geographic context around the source-reported positionAPPROXIMATE AREASOURCE MAP / GEOGRAPHIC CONTEXT

Approximate source-map area: 13.0°, 43.0°. Approximate source-map area, rounded to 0.5 degrees. Source map coordinates vary between retrievals; no precise incident fix is established. Static basemap; not a satellite image of the incident.

Original report · MSCIOBasemap imagery: NASA GIBS / Blue MarbleReuse terms

Previous baseline

The principal intelligence question is whether the vessel has returned to normal movement or requires assistance.

What changed

Close-range Red Sea encounter leaves onward vessel status unresolved

Maritime operating picture

Source-reported encounters, local vessel condition and regional access are separate layers. 0 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

Bab el-Mandeb
Connects Red Sea traffic with the Gulf of Aden.

Southern Red Sea approaches
Reported encounters must be linked by vessel and event time.

Suez route
Diversion and access effects need operator or authority evidence.

Relevant actors

Coastal and port authorities
Establish access conditions and restrictions.

Maritime security centres
Publish reported encounters and subsequent corrections.

Naval coalitions
Official communications describe their activity; effectiveness needs separate evidence.

Environmental exposure

A current release, footprint and coastal exposure are not established by this collection.

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

  • Vessel identity and time-stamped confirmation of damage, propulsion and onward movement.
  • A second independently identified close-range attack, or a more specific authority warning.
  • Any source correction, request for assistance or report of renewed contact.
  • Comparable encounters involving independently identified ships.
  • Port access or transit guidance changes.
  • Named-operator diversions and confirmed assistance requests.

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

  • No vessel name, IMO number, damage assessment or current position is available.
  • The attacker, weapon type and motive are unresolved; regional coverage is context, not corroboration.
  • MSCIO map coordinates vary between retrievals; the map shows an approximate area.
  • Theatre-wide traffic, insurance and environmental coverage are incomplete. No direct HUMINT has been collected for this dossier.

Material-change timeline

07 Oct 2026 · 18:54 UTCClose-range Red Sea encounter leaves onward vessel status unresolved

The principal intelligence question is whether the vessel has returned to normal movement or requires assistance.

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: IMB · Worldwide piracy & armed robbery, MARAD · U.S. DOT. Retained records may predate the latest check.

Reference-only sources represented here: Reuters · editorial selection. These are not connected live readers.

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.

v10 · 16 Oct 2026 · 18:53 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv9 · 16 Oct 2026 · 07:56 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv8 · 16 Oct 2026 · 07:36 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv7 · 16 Oct 2026 · 00:03 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv6 · 15 Oct 2026 · 19:58 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv5 · 15 Oct 2026 · 15:37 UTC · REVISED ASSESSMENT · evidence or analytical scope changedv4 · 15 Oct 2026 · 11:13 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 · 30The Maritime Executive · 16 Oct 2026 · 18:46 UTCWar in Yemen Now Impacting the Whole Gulf RegionSplash 247 · 16 Oct 2026 · 05:43 UTCLiquimar lines up suezmax trio at New HantongThe Maritime Executive · 15 Oct 2026 · 19:45 UTCBab el-Mandeb interception: defensive engagement is not proof of an attempted strikegCaptain · 15 Oct 2026 · 18:00 UTCHow the Houthis are Helping Iran Turn Saudi Arabia Into a Pressure PointThe Maritime Executive · 14 Oct 2026 · 00:25 UTCSuez container recovery is real but remains directional, service-specific and security-dependentBBC · 12 Oct 2026 · 16:28 UTCOn Yemen's desert battlefield, a war with global consequences is being wagedReuters · 12 Oct 2026 · 12:19 UTCSaudi Arabia’s Pipeline Ambition: Export Optionality, Red Sea Exposure and the Resilience OpportunityMSCIO · 2026-10-07 08:48 · source timezone unspecifiedClose-range Red Sea encounter leaves onward vessel status unresolvedMSCIO · 2026-10-04 20:53 · source timezone unspecifiedSuspicious Activity notification puts Red Sea & Gulf of Aden on the maritime watchMSCIO · 2026-09-28 13:52 · source timezone unspecifiedPiracy notification puts Red Sea & Gulf of Aden on the maritime watchCMF · 25 Sept 2026 · 12:26 UTCCTF 151 rehearses a coordinated piracy response in the Gulf of AdenMARAD · 23 Sept 2026 · time not suppliedCommercial-vessel attack risk remains in MARAD guidance for Red Sea & Gulf of Aden

Assessment source references

  1. MSCIOAttributed source · 2026-10-07 08:48 · source timezone unspecified
  2. IMO · Red Sea maritime securityContext reference
  3. EIA · World Oil Transit ChokepointsContext reference · 03 Mar 2026 · time not supplied
  4. Industry · BMP Maritime Security guidanceContext reference

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
Red Sea / Bab el-Mandeb theatre dossier | Intelligence.Navy