ALERT 137/26 extends outbound-tanker exposure into 11 October, but remains vessel-anonymous and single-chain reported

What we learned

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.

Maritime implication

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.

Confidence & evidence limits

MODERATE · MSCIO and the indexed UKMTO warning agree on the later event particulars, and the 16-hour-40-minute separation plus different consequence wording support treating ALERT 137/26 as distinct from ALERT 136/26. Confidence remains moderate because both channels reflect the same company-security-officer reporting chain, the vessel and coordinates are unpublished, no independent authority or sensor confirms the incident, and no follow-up establishes damage, propulsion, cargo, pollution, attribution or onward movement.

Evidence & analytical reasoning

Reported · MSCIO reported an outbound tanker struck on the port side by an unknown projectile at approximately 12:00 UTC on 11 October, with vessel damage, crew safe and no environmental impact reported at publication.^[1]

Reported · Indexed reporting of UKMTO WARNING 164-26 carries the same time, direction, impact side, damage, crew and environmental particulars and attributes the report to a company security officer.^[2]

Analytical inference · The matching particulars indicate that MSCIO and UKMTO are relaying one reporting chain and must not be counted as two independent confirmations.^[1][2]

Analytical inference · The 16-hour-40-minute time separation and different fire and environmental wording support treating ALERT 137/26 as distinct from ALERT 136/26 unless later identity evidence shows duplication.^[1][3]

Analytical inference · The later report extends the observed outbound-tanker threat window into 11 October but does not establish a closed Strait, a named casualty or attribution.^[1][2][6]

Analytical inference · Crew-safe and no-environmental-impact reporting at the initial notice does not resolve propulsion, cargo containment, hull condition or the vessel's subsequent movement.^[1][2]

Analytical inference · The current regional guidance supports enhanced voyage planning, bridge watch, navigation cross-checks and immediate reporting, but it is not incident-specific confirmation.^[5]