The United Kingdom Maritime Trade Operations centre issued Warning 162-26 on Saturday, 10 October. It is an Attack product, source Master, timed at 1920 UTC. UKMTO said it had received a report of an incident within the Strait of Hormuz. The master of an outbound tanker reported being struck on the port side by an unknown projectile, causing a fire on board. Crew were reported safe. Damage assessment and environmental impact were unknown at the time of the product. Authorities were investigating. Vessels were advised to transit with caution and report any suspicious activity to UKMTO. The official PDF named neither hull, flag, cargo, projectile type, fire location nor a responsible party.
Reuters, carried on Devdiscourse and in a Ynet paraphrase, Iran International and Anadolu Agency all carried the same unnamed Saturday-evening master report. That is the working primary. 162-26 is a Strait of Hormuz file, not a reprint of Friday’s dedicated Warning 160-26 west of Al Jazeera, not a rewrite of Wednesday’s dedicated Warning 158-26 north of Qatar, and not a later-tape increment of Thursday’s dedicated Joint Maritime Information Center Update 103. The useful facts for a DPA and a Hormuz master are the outbound tanker, the port-side projectile, the fire still described as on board, and a crew line that is reported safe. Do not invent an attacker from market colour, and do not treat Saturday afternoon’s unnamed IRGC mine claim as a UKMTO naming of this hull.
What UKMTO published on Saturday, and what it did not
162-26 is an Attack warning, not a suspicious-activity note. The master line is short: outbound tanker, unknown projectile, port side, fire on board, Strait of Hormuz, crew safe, damage and environment unknown, investigating. That combination is a fire-main and cargo-integrity problem with a better medical snapshot than Friday’s 160-26, and a worse fire snapshot than Friday’s extinguished line. UKMTO did not say the fire was out. It did not say the fire was in the engine room. It did not say the ship was underway, adrift, or at anchor after the hit. It did not report how many people were on board. The unknown-damage and unknown-environment lines are omissions, not a completed class survey and not a completed MARPOL finding.
Hold the source tag. Warning 160-26 on Friday was source third party. Saturday’s product is source Master. That is a stronger confirmation bar than Friday, not a reason to invent a name. Stay with “unknown projectile.” UKMTO did not name a UAV, a missile, a mine or IRGC. Ynet’s Reuters-fed paraphrase that printed “unknown missile” and a fire “on deck” is over-specification. The official PDF says projectile and fire on board. No group has claimed Saturday’s 1920 UTC product on the English primaries used. Do not back-fit Wednesday’s 158-26 multiple-projectile casualty, Tuesday’s dedicated On Peace India/Oman casualty, Monday’s 156-26 engine-room fire, or Friday’s Al Jazeera third-party fire onto Saturday’s unnamed outbound tanker.
A Hormuz TSS file, not a UAE-coast reprint
The geography is the operational point. UKMTO placed the incident within the Strait of Hormuz. That is the traffic-separation and Musandam corridor, not the Emirates’ inner coast and not the Fujairah / Gulf of Oman roadstead. Friday’s dedicated 160-26 sat 13 nautical miles west of Al Jazeera, United Arab Emirates, inside the Arabian Gulf. Saturday’s product does not reuse that range and does not reuse that reference point. Do not invent a latitude and longitude, a TSS lane, a named Omani or Iranian coastal mark, or a territorial-sea call. UKMTO did not make a coastal-state finding.
Update 103, information cut-off 081500 UTC on Thursday, 8 October, is still the last numbered JMIC regional note on the bridge. It held the Strait of Hormuz at SEVERE and the Arabian Gulf at MODERATE, printed confirmed files through 158-26, and asked for continued monitoring. Saturday’s 1920 UTC product sits outside that cut-off, as did Friday’s 160-26. Do not treat Update 103 as a Saturday all-clear for outbound Hormuz legs, and do not treat an Arabian Gulf MODERATE rating as a finding that the strait is quiet. Do not rewrite Update 103 on the strength of one later master warning. 159-26 remains an unused time-late 6 October Hormuz crude product that is not on Update 103’s table; Saturday is a new numbered Attack file, not a 159-26 rewrite.
Saturday’s IRGC mine claim is a competing narrative, not this warning
Hours earlier on Saturday, Iran’s Islamic Revolution Guard Corps Navy said, via Sepah News as carried by Xinhua, Anadolu and Iran International, that a “violating” crude supertanker attempting to exit the Strait of Hormuz on an “unauthorized” southern route had struck naval mines, suffered a massive explosion and caught fire. Anadolu said the IRGC described the ship as capable of carrying around two million barrels of oil and said it had switched off its navigation systems before the crossing. The explosion was described as visible from coastal areas. The IRGC did not name the hull, the flag, the crew, a casualty count or a position. Iran International said the account could not immediately be independently verified.
That Saturday-afternoon IRGC product is colour on the same day’s tape. It is not a UKMTO naming of 162-26. The mechanisms differ: UKMTO printed an unknown projectile on the port side at 1920 UTC, source Master; the IRGC printed mines on an unauthorized southern route, AIS/GPS off, with no clock that matches the 1920 UTC master report. Do not collapse the two into one hull. Do not brief Saturday evening as a confirmed mine strike, a confirmed IRGC naming, or a published southern-route ban. Friday’s dedicated IRGC naming of LPG carrier NV Sunshine remains Friday’s file. Saturday’s mine claim does not rewrite it, and 162-26 does not confirm it.
What this is not
162-26 sits after a week of Hormuz and Gulf Attack products that already have dedicated files. Warning 158-26, 7 October, 1900 UTC, source verified, unnamed tanker 51 nautical miles north of Madinat ash Shamal, multiple projectiles, casualties reported. Warning 160-26, 9 October, 1000 UTC, source third party, unnamed vessel 13 nautical miles west of Al Jazeera, fire extinguished, crew unknown. Warning 159-26 remains unused as a dedicated piece. Update 103 named 157-26 as ON PEACE and left 158-26 name-withheld. Saturday is a new numbered product, not a naming of 158-26, not a 159-26 rewrite, not a 160-26 increment, and not a JMIC Update 104.
Do not collapse 162-26 into On Peace, Maran Gas Mystras, Acers-matching colour on 158-26, GEM NO.2 industry matching on 160-26, NV Sunshine, or the unused Fujairah-roadstead fire colour on Marshall Islands VLCC Dhalkut. Do not fold Saturday into Yanbu loadings, the UAE MPCI container-filing mandate, Japan’s 35-ship vessel-level permit, Thursday’s OFAC/State 22-tanker package, Oman’s Article 10 AIS-on territorial-water rule, or Iran’s Persian Gulf Strait Authority declaration channel. Those are crude-export, documentation, sanctions and coastal-state products. Saturday’s file is an unnamed outbound tanker, unknown projectile, port-side hit, fire on board, crew safe, damage and environment unknown, in the Strait of Hormuz.
Operational implications
A port-side projectile hit with a fire still described as on board and a crew line that is reported safe is a different night order from Friday’s extinguished fire with an unknown crew line. Masters already committed to an outbound Hormuz transit need a written projectile watch on the port quarter and after end, not only a lookout for a disabled hull west of Al Jazeera. Citadel, fire-main isolation, inert-gas and cargo-tank integrity, emergency generator and steering-gear redundancy are the standing orders. The unknown-damage line means the ship may need tugs, a diversion to Fujairah, Khor Fakkan or an Omani port, or a request for firefighting assistance. UKMTO did not say which. The unknown-environment line means a pollution watch even though no MARPOL volume was published.
Managers who later recognise the 162-26 hull as theirs should assume flag, class and P&I will ask for the master’s report, the VDR, the last position before the hit, the time the fire was fought or contained, the casualty list if any despite the safe line, and whether emergency power and steering were restored. Charterers still stemming Gulf crude or products through the southern Omani corridor should treat Saturday as another kinetic day on a strait that Update 103 left at SEVERE. Do not brief the combination of a reported-safe crew and a missing pollution line as a reason to drop BMP, war-risk clauses or a lookout for a tanker that may be AIS-dark after a port-side hit.
Hold the published hygiene from Update 103 for the strait itself: neutral transit, prompt answers to military queries, NAVCENT NCAGS for any Iran-port humanitarian exception, and no cargo loaded in Iran beyond fuel and stores on an approved exemption. Saturday’s file does not rewrite that blockade picture. It also does not convert a Hormuz range into an Iran-port call. An outbound tanker is already in the waterway. The next inbound behind her has a possible disabled hull, a possible smoke column and a possible uncoordinated VHF picture to plan around. Advisory 161-26, issued 30 minutes earlier off Ras Al Khaimah, is a separate UAE-coast Suspicious Activity product. Do not brief the RAK VHF move as the cause of the 1920 UTC hit, and do not brief the hit as proof that the RAK broadcast was a prelude.
What Operators Should Note
- Log a new Saturday Attack product, not a Friday reprint. Warning 162-26, 10 October, 1920 UTC, source Master, outbound tanker in the Strait of Hormuz, unknown projectile, port side, fire on board, crew safe, damage and environment unknown, investigating. Transit with caution and report to UKMTO. Do not invent a name, flag, cargo or attacker to fill the UKMTO gap.
- Treat the still-burning fire and the safe-crew line as the operational difference. UKMTO did not say the fire was extinguished. Plan for boundary cooling, a possible disabled hull and a possible pollution watch even though no environmental line was published. That omission is a snapshot, not a completed MARPOL finding.
- Keep the IRGC mine claim labelled as a competing Saturday narrative. Sepah News / Xinhua / Anadolu / Iran International: unnamed crude supertanker, about two million barrels, navigation systems off, unauthorized southern route, mines, explosion visible from the coast, no identity. That is not a UKMTO naming and not a JMIC print. Do not brief Saturday evening as a confirmed mine strike.
- Put the projectile watch back on the Hormuz outbound, not only on the UAE inner coast. 162-26 is a Strait of Hormuz file. 160-26 remains the west-of-Al-Jazeera file. Do not collapse the two geometries, and do not treat Friday’s inner-Gulf hit as covering Saturday’s TSS transit.
- Do not rewrite Update 103. ICOD remains 081500 UTC 8 October. Hormuz SEVERE. Arabian Gulf MODERATE, with 158-26 already called an unusual disruption to monitor. 162-26 sits outside that cut-off. Replace nothing in the master’s JMIC pack until Update 104, a naming of 162-26, or a threat-level change appears.
- Stay with unknown projectile and no claim. Do not recast Saturday as a UKMTO-named hull, a confirmed IRGC mine, a Hormuz reopen, a 160-26 rewrite, a 159-26 increment, or a completed weekly tape. Keep 161-26 on its own advisory desk.
Regulas Shipping will keep lining Warning 162-26 against the unnamed Hormuz Attack products and Update 103 so operators can treat the 1920 UTC port-side fire on an outbound tanker as a new Strait of Hormuz casualty warning, not as a completed mine finding or a reason to assume the southern corridor has gone quiet.
