Strait of Hormuz / Arabian Gulf

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. 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.

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.

Key judgments

1. 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.

Maritime operating picture

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

Indicators & watch next

• Authoritative vessel-status updates and confirmed release or damage.
• Dated passage restrictions and named-operator route changes.
• Sustained AIS crossing changes over complete, comparable UTC windows.

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 tanker name, IMO number, flag, owner, operator, cargo and exact position are unpublished; MSCIO and UKMTO appear to carry the same company-security-officer report, with no independent observer, sensor or coastal authority found.
• The difference from ALERT 136/26 supports a separate event, but vessel anonymity prevents duplicate reporting from being excluded conclusively.
• Damage location beyond the port side, propulsion, steering, stability, cargo containment, assistance and onward movement remain unknown.
• Coverage of pollution, insurance and AIS-independent physical traffic is incomplete.

Material-change timeline