The United Kingdom Maritime Trade Operations published Warning 181-26 as an ATTACK product. The working primary is the numbered PDF dated 23 October 2026, 20261023-ukmto_warning_attack-181-26.pdf. The incident date is 22 October 2026. The incident time is 1715 UTC. The source line is Company Security Officer. UKMTO says it has received a time-late report of an incident 7 nautical miles northeast of Limah, Oman. A tanker has reported being hit by an unknown projectile whilst transiting outbound in the Strait of Hormuz. The tanker was able to continue its voyage to the next port of call. 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, a damage volume, a crew line, a pollution line, an attacker, nor a coordinate pair beyond the Limah offset.
This is a Strait of Hormuz outbound / western Gulf of Oman file. 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 Advisory 178-26, the dedicated Duqm military-interaction file. It is not Thursday morning’s dedicated IRGC Navy 4+3 claim piece, which this desk treated as an unverified statement because UKMTO had not then issued 181-26. It is not Friday’s dedicated Khoryv or Umm Al Quwain files. JMIC Update 107, ICOD 221300 UTC on 22 October, cuts off more than four hours before 1715 UTC and does not list this product. The IMO highlighted-incidents board, as at 22 October, remains 120 confirmed incidents and 24 confirmed seafarer fatalities, with SOYIA and CHLOE still the newest named rows. Do not brief Friday’s Limah product as Update 107, as an IMO-board move past 120, as a naming of Al Dasma or Soyia, or as a completed IRGC seven-tanker confirmation.
What UKMTO actually printed
The confirmed tape is short. ATTACK. 181-26. 22 October 2026. 1715 UTC. Source: Company Security Officer. Time-late. 7 nautical miles northeast of Limah, Oman. Tanker. Unknown projectile. Outbound in the Strait of Hormuz. Continued voyage to the next port of call. Transit with caution. Report suspicious activity to UKMTO. Authorities investigating. That is the product. Stay with the PDF’s 22 October 1715 UTC incident line and the 23 October product date. Do not invent a hull because Anadolu Agency, Iran International, Middle East Eye and Shafaq News reprinted the same numbered warning without a name. Those wires do not print a cargo. They do not print a fire. They do not print an attacker. Clearwater Dynamics Alert 037-(Oct 26) reprints the same UKMTO geometry and tags the aggressor as military; that is industry colour. UKMTO did not name a service.
The product type is the first briefing fact. 181-26 is an Attack, the same family as 174-26 through 177-26, 179-26 and 180-26, not the Advisory family that ran 178-26 and 163-26. UKMTO says the tanker was hit. It also says the tanker continued to the next port of call. Those two lines sit together on the same product. They are not a finding that the projectile missed, and they are not a completed class survey. They are not a crew-safe line. 180-26 printed crew safe and no reported damage. 179-26 printed a fire extinguished, a tanker at anchor and all crew safe. 181-26 prints neither. A DPA who briefs Friday as “no damage, all well” has filled a gap the PDF left open. A DPA who briefs Friday as a completed wreck or a crew evacuation has over-read a continue-voyage line.
Time-late from a company security officer is the second briefing fact. 180-26 was a time-late Master report. 181-26 is a time-late CSO report. The ship was struck at 1715 UTC on Thursday and only appears as a numbered Attack when the centre publishes the Friday PDF. That is a reporting-gap problem for the next hull in the same outbound lane. 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 CSO delay as evidence that the event was minor.
Geography is the second briefing trap
Limah sits on the eastern coast of Oman’s Musandam Peninsula, facing the Gulf of Oman. Seven nautical miles northeast of that point is an outbound Hormuz / western Gulf of Oman offset, not 11 nautical miles west of Bukha and not 30 nautical miles southeast of Al Faw. Bukha faces the Strait. Limah faces the Gulf of Oman. Do not move Al Dasma onto 181-26 because both files use Musandam mileposts. Do not move Soyia onto 181-26 because both files are unnamed tanker Attacks in the same week. Do not move Chloe onto 181-26 because both files sit off Oman. Chloe remains 121 nautical miles east of Duqm on dedicated Advisory 178-26 and on Thursday’s IMO 120-count. 181-26 is a new numbered Attack on a new clock and a new coastal offset.
Thursday morning’s dedicated IRGC Navy piece remains a claim file. Reuters split that statement as four vessels said to have been hit during “illegal oil transfers” in the northern Persian/Arabian Gulf and three further vessels said to have collided with mines west of Hormuz. UKMTO had not then issued 181-26. Friday’s numbered Attack is an outbound tanker 7 nautical miles northeast of Limah, reported by a CSO as hit by an unknown projectile. It is not a mine product. It is not an STS fire product. It is not a seven-hull confirmation. CENTCOM’s mine rebuttal and 95-percent transit line stay on Thursday’s claim piece. Do not collapse the IRGC 4+3 statement onto 181-26, and do not brief 181-26 as the instrument that verified that statement.
Operational implications
For a CSO with tonnage still using the southern Omani corridor outbound through Hormuz, Thursday 1715 UTC is a projectile problem in the outbound lane off Limah, not a Bukha fire-and-anchor problem and not an Al Faw holding-ground problem. Update 107 remains the last numbered JMIC note. It does not list 181-26. The IMO 120-count as at 22 October does not list 181-26. Plan the next outbound Hormuz run on Update 107 plus Warning 181-26 plus the dedicated 120-count piece, not on a headline that JMIC has already absorbed Thursday evening or that the IMO sheet has moved past 120.
Continue-voyage is the practical watch, not a clearance. A tanker that takes a hit at 1715 UTC and proceeds to the next port of call is still a reporting, damage-survey and war-risk problem when it arrives. P&I, class and the receiving terminal will want a written account that the public PDF does not contain: where the projectile struck, whether the crew were injured, whether there is a leak, whether the ship went to refuge or completed the intended voyage. The missing crew and damage lines are omissions. They are not a completed “all well.” Watch a PDF revision, a flag or class note, a NAVAREA, a JMIC Update 108, or an IMO-board row before briefing the tanker as clear, holed, or mistaken identity.
Time-late remains the other watch. A CSO who reports after the event leaves the next outbound hull in the same TSS without a live numbered product for the hours between 1715 UTC Thursday and the Friday PDF. That is the same reporting-gap this desk already treated on 180-26. 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.
Keep the dedicated files on their own lines. 179-26 / Al Dasma remains the dedicated 22 October 03:30 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; IMO’s Soyia naming remains wrap on Thursday’s 120-count. 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 Saturday’s Jubayl numbers. Thursday morning’s IRGC 4+3 claim remains a claim file. Friday’s Khoryv and Umm Al Quwain pieces remain Black Sea and UAE-coast files. Do not collapse Thursday 1715 UTC onto any of them.
Do not recast 22 October 1715 UTC as a Bukha increment, as a rewrite of 174-26 through 180-26, as Update 107, as an IMO-board move, as a verified mine, as a naming of the IRGC seven-tanker claim, or as a Hormuz closure. The confirmed facts are Warning 181-26, 22 October, 1715 UTC, Company Security Officer, time-late, tanker, unknown projectile, 7 nautical miles northeast of Limah, outbound in the Strait of Hormuz, continued voyage to the next port of call, no hull name, JMIC still Update 107 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 off Limah, not a Bukha or Al Faw file. Warning 181-26. 22 October 2026. 1715 UTC. Source: Company Security Officer. Time-late. Tanker hit by an unknown projectile approximately 7 nautical miles northeast of Limah, Oman, whilst transiting outbound in the Strait of Hormuz. The tanker continued to the next port of call. UKMTO printed neither hull, IMO, flag, cargo, projectile type, fire, crew, pollution nor attacker. Anadolu Agency, Iran International, Middle East Eye and Shafaq News reprint the same numbered product without a name.
- Treat “hit” and “continued voyage” as two open lines, not a completed all-well. The public tape does not say the projectile missed. It does not print a crew-safe line. It does not print a damage or pollution line. It does not say the ship went NUC, to anchor, or to refuge. Watch a PDF revision, a flag or class note, a NAVAREA, or a JMIC Update 108 before briefing the tanker as clear, holed, or mistaken identity.
- Do not merge 181-26 onto Al Dasma, Soyia, Chloe or Thursday’s IRGC 4+3 claim. Al Dasma remains the dedicated 179-26 Bukha fire, 11 NM west of Bukha, later at anchor 1.3 NM west of Bukha on NAVAREA IX 396/26. Soyia remains the dedicated 180-26 Al Faw Attack, 30 NM southeast of Al Faw. Chloe remains the dedicated 178-26 Duqm Advisory. The IRGC Navy Thursday statement remains a claim file. 181-26 is a new numbered Attack on a new clock and a new Musandam-east offset.
- Keep Update 107 and the 120-count in the master’s pack, and do not stretch them to this product. Update 107’s information cut-off is 221300 UTC on 22 October, more than four hours before 1715 UTC. Hormuz remains SEVERE and the Arabian Gulf SUBSTANTIAL on that note. The IMO board as at 22 October is 120 confirmed / 24 dead and does not print a Limah 22 October row. 181-26 sits after both cut-offs. Transit with caution. Report to UKMTO.
- Put the outbound Omani corridor back on the night orders as a projectile envelope. Time-late from a CSO means the next ship in the same TSS may only hear the Attack after it is over. Answer UKMTO and the DPA while the event is happening. Do not treat “continue passage” or “file when clear of the strait” as a risk-reducing phrase on this coast.
- Leave 174-26 through 180-26 on their dedicated pieces. 174-26 / ST3 and 175-26 / Loyalty remain Saturday’s 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 is the new Limah Attack number. Watch the next numbered warning, a JMIC Update 108, or a named-hull primary — not an Al Dasma or IRGC-claim rewrite.
Regulas Shipping will keep lining Warning 181-26 against Update 107’s earlier 221300 UTC cut-off and against Thursday’s IMO 120-count so operators can treat Friday’s Limah tape as a numbered unnamed tanker Attack on an outbound Hormuz transit, not as a Bukha rewrite or a completed IRGC naming.
