Operating indicators, linked cases and evidence-led collection priorities.
Version recorded 19 Oct 2026 · 19:01 UTC. Related source records show their available archive versions.
Links use the site’s current access permissions.
REPORTED EXPOSURERECENT EVIDENCE REVIEWTrend · NOT ESTABLISHED
PARTIAL COLLECTIONSources checked 19 Oct 2026 · 19:01 UTCEvidence review 18 Oct 2026 · 21:55 UTCLatest source evidence 19 Oct 2026 · 18:54 UTC
Recent source accounts retain open follow-up questions. They are not a confirmed count of unique, currently active incidents.
Reports to follow up · 7D
1
Accounts, not unique incidents
Reviewed products · 7D
1
Case-level analytical updates
Evidence gaps
3 / 4
Operating dimensions to verify
HISTORICAL ASSESSMENT
MSCIO 149/26 reports an armed approach and withdrawal, not an onboard blaze. NAVAREA adds a nearby caution point; UKMTO's candidate adds an LNG classification but an unresolved location crosswalk. Retain the notices separately until vessel, time and position are reconciled. [mscio,nav383,ukmto176] 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
REPORTED
Source accounts describe recent vessel-level exposure. Match identities and event times before treating notices as separate incidents.
MSCIO 149/26 reports an armed approach and withdrawal, not an onboard blaze. NAVAREA adds a nearby caution point; UKMTO's candidate adds an LNG classification but an unresolved location crosswalk. Retain the notices separately until vessel, time and position are reconciled. [mscio,nav383,ukmto176]
The principal intelligence question is whether the vessel has returned to normal movement or requires assistance.
APPROXIMATE AREASOURCE MAP / GEOGRAPHIC CONTEXT
Approximate source-map area: 13.0°, 47.5°. 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.
MSCIO 149/26 reports an armed approach and withdrawal, not an onboard blaze. NAVAREA adds a nearby caution point; UKMTO's candidate adds an LNG classification but an unresolved location crosswalk. Retain the notices separately until vessel, time and position are reconciled. [mscio,nav383,ukmto176] The principal intelligence question is whether the vessel has returned to normal movement or requires assistance.
What changed
MSCIO 149/26 describes gunfire, not a shipboard blaze; nearby notices remain unmatched
Maritime operating picture
Source-reported encounters, local vessel condition and regional access are separate layers. 1 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.
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
A cross-referenced MSCIO/UKMTO/NAVAREA correction providing vessel name/IMO, event hour and reconciled position.
Operator or flag-state confirmation of crew welfare, damage inspection and onward-voyage status.
Any boarding, detention, assistance or disruption report specifically matching this vessel and event; do not import other regional incidents.
NAVAREA 383/26's stated cancellation at 23 October 2026, 23:59 UTC, or an earlier replacement/cancellation; notice expiry is not an independently verified security all-clear.
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
Vessel name/IMO, flag, operator, actual cargo and loading condition are unverified. UKMTO's LNG classification is not assigned to MSCIO.
MSCIO gives17October without event hour; its publication timestamp has no timezone. NAVAREA's17:00UTC issue time is not the event time.
The one-nautical-mile position difference and missing cross-reference leave NAVAREA/MSCIO identity unresolved; underlying reporting independence is unknown.
UKMTO's indexed southwest reference conflicts with Anadolu's southeast wording. Direct UKMTO incident text and two PDF revisions could not be retrieved.
MSCIO reports vessel/crew safe; no separate damage survey, medical outcome or onward voyage was obtained. No reported fire is not proof of no damage.
Original MSCIO page unavailable; retained narrative used. UKMTO and Pakistan's hydrographic office are absent from the intake issuer directory; no substitute registration attempted.
Theatre-wide traffic, insurance and environmental coverage are incomplete. No direct HUMINT has been collected for this dossier.
Public readers use the existing hourly collection cycle and five-minute refresh while the main watch is open. Unavailable readers retain dated records.
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.
Reviewed case judgments feed the dossier. Event confidence, editorial priority and a theatre-wide threat rating remain separate.
Changed evidence, corrections and analytical states enter the version history. A repeated source check does not become a new analytical review.
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.
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.
Red Sea / Bab el-Mandeb theatre dossier | Intelligence.Navy
INTELLIGENCE.NAVYA portal by Maritime IntelligenceBack to In FocusPrivate intelligence environments · In preparation