{"id":966,"date":"2026-10-11T03:32:11","date_gmt":"2026-10-11T03:32:11","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-logs-a-projectile-fire-on-an-outbound-hormuz-tanker-after-warning-162-26\/"},"modified":"2026-10-11T03:33:11","modified_gmt":"2026-10-11T03:33:11","slug":"ukmto-logs-a-projectile-fire-on-an-outbound-hormuz-tanker-after-warning-162-26","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-logs-a-projectile-fire-on-an-outbound-hormuz-tanker-after-warning-162-26\/","title":{"rendered":"UKMTO logs a projectile fire on an outbound Hormuz tanker after Warning 162-26"},"content":{"rendered":"

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.<\/p>\n

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\u2019s dedicated Warning 160-26 west of Al Jazeera, not a rewrite of Wednesday\u2019s dedicated Warning 158-26 north of Qatar, and not a later-tape increment of Thursday\u2019s 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\u2019s unnamed IRGC mine claim as a UKMTO naming of this hull.<\/p>\n

What UKMTO published on Saturday, and what it did not<\/h2>\n

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\u2019s 160-26, and a worse fire snapshot than Friday\u2019s 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.<\/p>\n

Hold the source tag. Warning 160-26 on Friday was source third party. Saturday\u2019s product is source Master. That is a stronger confirmation bar than Friday, not a reason to invent a name. Stay with \u201cunknown projectile.\u201d UKMTO did not name a UAV, a missile, a mine or IRGC. Ynet\u2019s Reuters-fed paraphrase that printed \u201cunknown missile\u201d and a fire \u201con deck\u201d is over-specification. The official PDF says projectile and fire on board. No group has claimed Saturday\u2019s 1920 UTC product on the English primaries used. Do not back-fit Wednesday\u2019s 158-26 multiple-projectile casualty, Tuesday\u2019s dedicated On Peace India\/Oman casualty, Monday\u2019s 156-26 engine-room fire, or Friday\u2019s Al Jazeera third-party fire onto Saturday\u2019s unnamed outbound tanker.<\/p>\n

A Hormuz TSS file, not a UAE-coast reprint<\/h2>\n

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\u2019 inner coast and not the Fujairah \/ Gulf of Oman roadstead. Friday\u2019s dedicated 160-26 sat 13 nautical miles west of Al Jazeera, United Arab Emirates, inside the Arabian Gulf. Saturday\u2019s 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.<\/p>\n

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\u2019s 1920 UTC product sits outside that cut-off, as did Friday\u2019s 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\u2019s table; Saturday is a new numbered Attack file, not a 159-26 rewrite.<\/p>\n

Saturday\u2019s IRGC mine claim is a competing narrative, not this warning<\/h2>\n

Hours earlier on Saturday, Iran\u2019s Islamic Revolution Guard Corps Navy said, via Sepah News as carried by Xinhua, Anadolu and Iran International, that a \u201cviolating\u201d crude supertanker attempting to exit the Strait of Hormuz on an \u201cunauthorized\u201d 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.<\/p>\n

That Saturday-afternoon IRGC product is colour on the same day\u2019s 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\u2019s dedicated IRGC naming of LPG carrier NV Sunshine remains Friday\u2019s file. Saturday\u2019s mine claim does not rewrite it, and 162-26 does not confirm it.<\/p>\n

What this is not<\/h2>\n

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.<\/p>\n

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\u2019s 35-ship vessel-level permit, Thursday\u2019s OFAC\/State 22-tanker package, Oman\u2019s Article 10 AIS-on territorial-water rule, or Iran\u2019s Persian Gulf Strait Authority declaration channel. Those are crude-export, documentation, sanctions and coastal-state products. Saturday\u2019s 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.<\/p>\n

Operational implications<\/h2>\n

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\u2019s 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.<\/p>\n

Managers who later recognise the 162-26 hull as theirs should assume flag, class and P&I will ask for the master\u2019s 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.<\/p>\n

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\u2019s 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.<\/p>\n

What Operators Should Note<\/h2>\n