The United Kingdom Maritime Trade Operations published Warning 182-26 as an ATTACK product. The working primary is the numbered PDF dated 26 October 2026, 20261026-ukmto_warning-182-26.pdf. The incident date is 23 October 2026. The incident time is 0839 UTC. The source line is Verified. UKMTO says it has received a verified time-late report of an incident in the Strait of Hormuz. A tanker transiting outbound was struck by an unknown projectile, disabling the vessel. The crew have been reported safe. There is no damage assessment or environmental impact report at present. Vessels are advised to transit with caution and report any suspicious activity to UKMTO while authorities investigate. UKMTO printed neither a ship name, an IMO number, a flag, a cargo grade, a heading, a projectile type, a fire line, an attacker, nor a coordinate pair beyond the Strait of Hormuz itself.
This is a Strait of Hormuz outbound file with a disablement line. It is not Warning 181-26, Friday’s dedicated unnamed tanker Attack 7 nautical miles northeast of Limah, which continued to the next port of call and later sat on Sunday’s dedicated Update 108 as an unnamed LPG tanker at anchor off Khor Fakkan. It is not Warning 179-26, the dedicated Bukha Attack 11 nautical miles west of Bukha. It is not Warning 180-26, the dedicated northern-Gulf Attack 30 nautical miles southeast of Al Faw. It is not Saturday’s dedicated NAVAREA IX 403/26 Cape Dao “reported sunk” row or 404/26 Ghana Prosperity anchorage 4.5 nautical miles south of Jazirat Musandam. JMIC Update 108, ICOD 251300 UTC on 25 October, cuts off before Monday’s PDF and does not list 182-26. The IMO highlighted-incidents board, as at 22 October, remains 120 confirmed incidents and 24 confirmed seafarer fatalities. Do not brief Monday’s product as Update 108, as Update 109, as an IMO-board move past 120, as a naming of the Limah hull, or as a Hormuz closure.
What UKMTO actually printed
The confirmed tape is short. ATTACK. 182-26. 23 October 2026. 0839 UTC. Source: Verified. Time-late. Strait of Hormuz. Tanker. Outbound. Unknown projectile. Disabled the vessel. Crew reported safe. No damage assessment at present. No environmental impact report at present. Transit with caution. Report suspicious activity to UKMTO. Authorities investigating. That is the product. Stay with the PDF’s 23 October 0839 UTC incident line and the 26 October product date. Do not invent a hull because Iran International reprinted the same numbered warning at 09:34 GMT on Monday without a name. That wire does not print a cargo. It does not print a fire. It does not print an attacker. Clearwater Dynamics Alert 038-(Oct 26) reprints the same UKMTO clock and tags the aggressor as military; that is industry colour. UKMTO did not name a service. Ambrey’s 23 October 07:35 entry of a merchant vessel impacted by a projectile in Omani territorial waters is a different clock and a different type line. Do not collapse it onto 182-26 as a naming, a coordinate, or a confirmation that the hull was inside Oman’s territorial sea. Desk colour that recast the projectile as gunfire is not on the PDF. Stay with “unknown projectile.”
The product type is the first briefing fact. 182-26 is an Attack, the same family as 174-26 through 177-26, 179-26, 180-26 and 181-26, not the Advisory family that ran 178-26 and 163-26. UKMTO says the tanker was struck. It also says the strike disabled the vessel. Those two lines sit together on the same product. They are not a finding that the projectile missed. They are not a completed class survey. They are not a wreck. They are not a continue-voyage line. 181-26 printed a hit and a continued voyage to the next port of call. 180-26 printed crew safe and no reported damage. 179-26 printed a fire extinguished, a tanker at anchor and all crew safe. 182-26 prints disabled, crew safe, and no damage or environmental assessment at present. A DPA who briefs Monday as “no damage, all well, proceeding” has filled a gap the PDF left open and has borrowed Friday’s continue-voyage language. A DPA who briefs Monday as a completed sinking or a crew evacuation has over-read a disablement line that sits next to a crew-safe sentence and an open assessment.
Time-late and verified is the second briefing fact. 181-26 was a time-late Company Security Officer report published the next day. 182-26 is a verified time-late report published three days after the 0839 UTC clock. The ship was struck on Friday morning and only appears as a numbered Attack when the centre publishes the Monday PDF. That is a longer reporting gap than Friday’s Limah file. Channel 16, the UKMTO emergency line and the company duty officer still have to be on the night orders while the ship is in the TSS. Do not treat a three-day delay as evidence that the event was minor. Do not treat “verified” as a hull naming.
Geography and the files this is not
182-26 prints Strait of Hormuz and outbound. It does not print Limah, Bukha, Musandam, Khor Fakkan, Al Faw or a latitude/longitude. Do not move the Friday 7-nautical-mile northeast-of-Limah offset onto this number because both files are outbound Hormuz tanker Attacks. Do not move Al Dasma onto 182-26 because both files use the strait. Do not move Ghana Prosperity onto 182-26 because Saturday’s dedicated NAVAREA IX 404/26 already placed that named hull at anchor 4.5 nautical miles south of Jazirat Musandam after an earlier security incident. Do not move Cape Dao onto 182-26 because Saturday’s dedicated 403/26 already printed that hull as reported sunk. 182-26 is a new numbered Attack on a new clock with a disablement line the earlier Hormuz products did not carry.
Sunday’s dedicated Update 108 remains the last numbered JMIC note. Its confirmed-incidents table added one file since Update 107: 181-26, name withheld, LPG tanker, 7 nautical miles northeast of Limah, now at anchor off Khor Fakkan. Update 108’s information cut-off is 251300 UTC on 25 October. Monday’s 182-26 PDF sits after that cut-off. The 156-incident tally on Update 108 does not absorb Friday 0839 UTC. The IMO board as at 22 October still does not carry 181-26, and it does not carry 182-26. Those are different counters. Hold them separately. Do not invent Update 109 because a later Attack appeared.
CENTCOM colour from the same news cycle stays colour. Iran International and TradeWinds carried Admiral Brad Cooper’s 25 October overflight, a six-month “more than 3,000” facilitated-transit line, a “more than 1.5 billion barrels” Gulf-export line, a mines-cleared sentence and a recent-months “more than 95 percent” safe-passage line. Update 108 still printed NCAGS at about 28 assisted transits a day, 101 U.S.-facilitated Hormuz transits for 22–24 October, and the 17 October CENTCOM blockade line of 138 redirected / four disabled. Do not add Monday’s disablement into that four-disabled figure. Do not brief 182-26 as the instrument that verified or cancelled the overflight talking points. They are different products.
Operational implications
For a CSO with tonnage still using the southern Omani corridor outbound through Hormuz, Friday 0839 UTC is a projectile-and-disablement problem in the outbound lane, not a Limah continue-voyage problem and not a Bukha fire-and-anchor problem. Update 108 remains the last numbered JMIC note. It does not list 182-26. The IMO 120-count as at 22 October does not list 182-26. Plan the next outbound Hormuz run on Update 108 plus Warning 181-26 plus Warning 182-26 plus the dedicated 120-count piece, not on a headline that JMIC has already absorbed Friday morning or that the IMO sheet has moved past 120.
Disablement is the practical watch, not a wreck finding. A tanker that takes a hit at 0839 UTC and is printed as disabled is a reporting, damage-survey, tow, refuge and war-risk problem before anyone has a public class note. P&I, class and the receiving terminal will want a written account that the public PDF does not contain: where the projectile struck, whether propulsion or steering is lost, whether the ship went NUC, whether a tug is assigned, whether there is a leak, and where the hull is now. The missing damage and pollution lines are omissions. They are not a completed “all well.” The crew-safe line is a crew line. It is not a machinery line. Watch a PDF revision, a flag or class note, a NAVAREA, a JMIC Update 109, or an IMO-board row before briefing the tanker as proceeding, holed, under tow, or mistaken identity.
Time-late remains the other watch. A verified report that lands on Monday for a Friday 0839 UTC clock leaves the next outbound hull in the same TSS without a live numbered product for the weekend. That is a longer gap than Friday’s Limah CSO delay. Masters still have to answer UKMTO and the DPA while the event is happening. Do not treat “we will file when we are clear of the strait” as a risk-reducing phrase on this coast, and do not treat a Monday PDF as proof that Friday morning was quiet.
Keep the dedicated files on their own lines. 181-26 remains Friday’s dedicated Limah Attack; Update 108’s LPG / Khor Fakkan status remains wrap on Sunday’s dedicated note, and the PDF still says continued voyage. 179-26 / Al Dasma remains the dedicated Bukha Attack; NAVAREA IX 396/26 remains the 1.3-nautical-mile west-of-Bukha anchorage caution. 180-26 / Soyia remains the dedicated Al Faw Attack. 178-26 / Chloe remains the dedicated Duqm Advisory. 177-26 / Jif Barracuda remains Khor Fakkan. 176-26 remains the unnamed Mukalla LNG number. 174-26 / ST3 and 175-26 / Loyalty remain the Jubayl numbers. Saturday’s 403/26 and 404/26 remain the Cape Dao and Ghana Prosperity hydrographic files. Sunday’s ARN 155/2026 remains the Khoryv wreck-move file. Do not collapse Friday 0839 UTC onto any of them.
Do not recast 23 October 0839 UTC as a Limah increment, as a rewrite of 174-26 through 181-26, as Update 108, as Update 109, as an IMO-board move, as a Ghana Prosperity naming, as a verified mine, or as a Hormuz closure. The confirmed facts are Warning 182-26, 23 October, 0839 UTC, Verified, time-late, tanker, unknown projectile, outbound in the Strait of Hormuz, vessel disabled, crew safe, no damage or environmental assessment at present, no hull name, JMIC still Update 108 with an earlier cut-off, IMO board still 120 as at 22 October without this file.
What Operators Should Note
- Log a numbered UKMTO Attack with a disablement line, not a Limah continue-voyage file. Warning 182-26. 23 October 2026. 0839 UTC. Source: Verified. Time-late. Tanker struck by an unknown projectile whilst transiting outbound in the Strait of Hormuz. The vessel was disabled. Crew reported safe. No damage assessment or environmental impact report at present. UKMTO printed neither hull, IMO, flag, cargo, projectile type, fire, attacker nor a Limah or Musandam offset. Iran International reprinted the same numbered product without a name.
- Treat “disabled” and “crew safe” as two open lines, not a completed all-well. The public tape does not say the projectile missed. It does not print a continue-voyage line. It does not print a NUC, tow, refuge or wreck line. It does not print a damage or pollution volume. Watch a PDF revision, a flag or class note, a NAVAREA, or a JMIC Update 109 before briefing the tanker as proceeding, under tow, or mistaken identity.
- Do not merge 182-26 onto 181-26, Ghana Prosperity, Cape Dao or Al Dasma. 181-26 remains Friday’s dedicated Limah Attack, 7 NM northeast of Limah, 1715 UTC 22 October, continued voyage; Update 108 later typed that hull as an unnamed LPG tanker at anchor off Khor Fakkan. Ghana Prosperity remains Saturday’s dedicated NAVAREA IX 404/26 anchorage. Cape Dao remains Saturday’s dedicated 403/26 reported-sunk row. Al Dasma remains the dedicated 179-26 Bukha fire. 182-26 is a new numbered Attack on a new Friday-morning clock.
- Keep Update 108 and the 120-count in the master’s pack, and do not stretch them to this product. Update 108’s information cut-off is 251300 UTC on 25 October. Hormuz remains SEVERE and the Arabian Gulf SUBSTANTIAL on that note. The 156-incident tally absorbs 181-26, not 182-26. The IMO board as at 22 October is 120 confirmed / 24 dead and does not print a 23 October Hormuz row. Transit with caution. Report to UKMTO.
- Put the outbound Hormuz corridor back on the night orders as a projectile-and-disablement envelope. A three-day verified delay means the next ship in the same TSS may only hear the Attack after the weekend. Answer UKMTO and the DPA while the event is happening. Do not treat “file when clear of the strait” as a risk-reducing phrase on this coast.
- Leave 174-26 through 181-26 on their dedicated pieces. 174-26 / ST3 and 175-26 / Loyalty remain the Jubayl numbers. 176-26 remains Mukalla. 177-26 / Jif Barracuda remains Khor Fakkan. 178-26 / Chloe remains the Duqm Advisory. 179-26 / Al Dasma remains Bukha. 180-26 / Soyia remains Al Faw. 181-26 remains Limah. 182-26 is the new outbound disablement number. Watch the next numbered warning, a JMIC Update 109, or a named-hull primary — not a Limah or Ghana Prosperity rewrite.
Regulas Shipping will keep lining Warning 182-26 against Update 108’s earlier 251300 UTC cut-off and against Friday’s dedicated Limah Attack so operators can treat Monday’s tape as a numbered unnamed tanker disablement on an outbound Hormuz transit, not as a 181-26 rewrite or a completed class survey.
