Human editorial review before publication · Member of the Intelligence.Navy Maritime Intelligence Team · 12 Oct 2026 · 20:18 UTC. Incident verification remains separate.
Research context & editorial review- Event
- 10 Oct 2026 · 19:20 UTC
- Original source published
- 2026-10-11 08:20 · source timezone unspecified
- Analysis reviewed
- 11 Oct 2026 · 09:02 UTC
- Human review
- 12 Oct 2026 · 20:18 UTC
- Added to portal
- 11 Oct 2026 · 08:59 UTC
- Source check
- 13 Oct 2026 · 07:16 UTC
External source reporting used in this assessment
Key judgment
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 reported an outbound tanker struck on the port side by an unknown projectile at about 19:20 UTC on 10 October in the Strait of Hormuz, causing a fire; crew were reported safe and damage and environmental impact were unknown.
The indexed UKMTO WARNING 162-26 carries the same time, direction, impact side, fire and crew status as ALERT 136/26.
Approximate source-map area: 26.5°, 56.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.
What we learned
The source record alone can be mistaken for another version of the preceding tanker-fire notices. Chronology and attributes separate it: ALERT 135/26 concerned 9 October at 10:00 UTC west of Al Jazeera, reported the fire extinguished and left crew status unknown; ALERT 136/26 concerns 10 October at 19:20 UTC inside the Strait, an outbound tanker struck on the port side, with crew safe but no fire-resolution statement. The exact overlap between MSCIO and UKMTO shows dissemination of the same master report, not independent observation. No named owner, flag, port, pollution authority or IMO entry yet closes the identity or consequence gaps.
Maritime implication
For outbound tanker voyages, the new report sustains a requirement for enhanced bridge watch, rapid fire and machinery assessment, damage-control readiness and immediate reporting during the Hormuz transit. It does not establish a lane closure or identify a specific tanker: the portal still observed one inbound crossing at 08:58:48 UTC on 11 October, but that bounded AIS count cannot measure unobserved traffic or be linked to the casualty.
Confidence & evidence limits
MODERATE · Two official maritime-security channels carry matching particulars, supporting the occurrence and chronology, and the crew-safe status comes from the master-originated report. Confidence is limited because both notices reflect the same reporting chain; the vessel remains unnamed; and no authoritative follow-up confirms fire control, propulsion, damage, pollution, attribution or subsequent movement.
Evidence & analytical reasoning
Reported · MSCIO reported an outbound tanker struck on the port side by an unknown projectile at about 19:20 UTC on 10 October in the Strait of Hormuz, causing a fire; crew were reported safe and damage and environmental impact were unknown.[1]
Reported · The indexed UKMTO WARNING 162-26 carries the same time, direction, impact side, fire and crew status as ALERT 136/26.[2]
Analytical inference · The exact factual overlap indicates that MSCIO and UKMTO are relaying one master-originated event and should not be counted as independent confirmation of two attacks.[1][2]
Analytical inference · Differences in date, time, location detail, transit direction, fire status and crew status make ALERT 136/26 analytically distinct from ALERT 135/26 unless a later authoritative identity link proves otherwise.[1][3]
Analytical inference · The safe-crew report narrows immediate human risk but does not resolve the vessel’s fire, machinery, stability, cargo-containment or pollution outcome.[1][2]
Analytical inference · One observed inbound AIS crossing on the following partial day is evidence that a passage was observed, not proof of normal traffic or evidence about the attacked tanker.[5]
Next decision indicators
- A named UKMTO or MSCIO update to WARNING 162-26 / ALERT 136/26 with vessel identity, fire status and movement.
- Owner, flag, class, P&I, port or coastal-authority reporting on damage, propulsion, towage and safe-port status.
- Pollution-response or satellite evidence with acquisition time and source that confirms or rules out a release.
- IMO addition of the 10 October event with ship name, IMO number and outcome.
- Authenticated AIS or port-call history linked to a confirmed IMO number rather than proximity alone.
- Any official correction showing that ALERTS 135/26 and 136/26 concern the same vessel or event.
Publication history · 10 captured versions
Loading captured versions…
Evidence & references
- [1] MSCIO ALERT 136/26 — Attack reported in Hormuz & Arabian GulfSource account
- [2] UKMTO WARNING 162-26 — outbound tanker struck in the Strait of HormuzCandidate linkage · unconfirmed
- [3] MSCIO ALERT 135/26 — 9 October incident west of Al JazeeraContext reference
- [4] IMO Middle East highlighted confirmed incidentsContext reference
- [5] Intelligence.Navy Hormuz AIS traffic snapshotContext reference
Evidence scope & unresolved questions
- The tanker name, IMO number, flag, owner, operator, cargo and exact coordinates are not published in the retrieved official notices.
- MSCIO and UKMTO appear to carry the same master-originated particulars; no independent sensor, authority or named-vessel confirmation was found.
- The notice does not say whether the fire was extinguished, whether propulsion or steering were available, or whether assistance was required.
- Hull damage, cargo containment, bunker or cargo release and environmental impact remain unknown.
- Projectile type, launch point and attribution remain unconfirmed.
- The IMO table was current only through 9 October and therefore cannot yet confirm or refute the 10 October incident.
AI-assisted research, followed by recorded human editorial approval. Approval is not independent verification of the incident.. AI-assisted synthesis with recorded human editorial review; event verification remains limited by the attached sources.
Location basis: Approximate source-map area, rounded to 0.5 degrees. Source map coordinates vary between retrievals; no precise incident fix is established.
MSCIO ALERT 136/26 — Attack reported in Hormuz & Arabian Gulf: Retained portal source record. The notice does not name the tanker, give coordinates, identify the projectile or attacker, say whether the fire was extinguished, or provide a later vessel or pollution status.
UKMTO WARNING 162-26 — outbound tanker struck in the Strait of Hormuz: Indexed excerpt; live page content was not verified. The live UKMTO incident feed was not server-readable through the portal. The indexed warning repeats the same master-originated particulars and is corroboration of the reporting chain, not independent confirmation from another observer.
MSCIO ALERT 135/26 — 9 October incident west of Al Jazeera: Indexed excerpt; live page content was not verified. The earlier alert remains vessel-anonymous. It must not be merged with ALERT 136/26 or a named ship without an authoritative identity link.
IMO Middle East highlighted confirmed incidents: Indexed excerpt; live page content was not verified. The table predates the 10 October event and may update with delay. Absence is not evidence that the incident did not occur and provides no vessel identity for ALERT 136/26.
Intelligence.Navy Hormuz AIS traffic snapshot: Retained portal source record. The counts are coverage-bounded and do not identify the attacked tanker. A single observed crossing neither measures total traffic nor proves normal corridor conditions.