The United Kingdom Maritime Trade Operations centre published Warning 189-26 as a numbered PDF on its product board, filename 20261030-ukmto_warning_189-26.pdf. The face of the product is titled 189-26 — ATTACK. The incident date is 28 October 2026. The incident time is TBC. The source line is Verified. UKMTO states that it has received a time-late report of an incident in the Strait of Hormuz. A verified source has informed UKMTO that a crude oil tanker was struck by an unknown projectile whilst completing an outbound transit of the Strait of Hormuz. Vessels are advised to transit with caution and report any suspicious activity to UKMTO, whilst authorities investigate. Emergency contacts printed on the product remain [email protected] and +44 (0)2392222060.
That is the working primary. Friday evening’s second Warning, issued after 188-26, is a time-late Attack on a Wednesday Hormuz clock, not a rewrite of Friday night’s Lavan Island file and not a late naming of Thursday’s unused 186-26. It does not name a merchant hull, an IMO number, a flag, a cargo grade, an attacker, a fire, a NUC or tow line, an anchorage, a latitude/longitude, or a keep-clear radius. Last night’s dedicated 188-26 piece on this desk, published about 23:38 UTC, still told operators that UKMTO ended at Attack 188-26, 40 nautical miles south of Lavan Island. 189-26 was not on that note. Masters who brief Saturday morning as a rewrite of the Lavan projectile, as a named RITI wreck, as a Louise 1 conversion, as unused 186-26 finally named, or as Update 110 will have merged five other series into a back-dated Hormuz clock.
What the warning actually printed
The confirmed tape is the body of 189-26. UKMTO has received a time-late report of an incident in the Strait of Hormuz. A verified source has informed UKMTO that a crude oil tanker was struck by an unknown projectile whilst completing an outbound transit of the Strait of Hormuz. Vessels are advised to transit with caution and report any suspicious activity to UKMTO, whilst authorities investigate. That is the product. Stay with that wording. Do not invent a hull. Do not invent a flag. Do not invent an LPG or products type. The PDF prints “crude oil tanker,” not vessel and not LPG. Do not invent a UAV, a mine, a small-boat device or a boarding. Do not invent a lat/long on the UKMTO PDF. 189-26 does not print one. Do not invent a keep-clear radius around Musandam or Khasab. The PDF does not print one. Do not invent a crew-safe line, a fire-extinguished line, or a no-environmental-impact line. Those sentences sit on 186-26, 187-26 and 188-26. They do not sit on 189-26.
The product type is the first briefing fact. 189-26 is Attack, the same family that ran 174-26 through 177-26, 179-26, 180-26, 181-26, 182-26, Thursday afternoon’s unused 186-26, Friday morning’s dedicated 187-26 and Friday evening’s dedicated 188-26, not the Suspicious Activity family that ran 183-26 and Thursday morning’s dedicated 185-26, and not the Advisory family that ran 184-26 and 178-26. UKMTO says an unknown projectile struck a crude oil tanker on an outbound Hormuz transit. It does not say a small boat attached devices. It does not say a mine in the water. It does not say a UAV. It does not say the ship is at anchor, NUC, under tow, sunk, on fire, or continuing to the next port of call. A DPA who briefs Saturday as “another Hormuz attached-device hit, crew safe” has borrowed 187-26’s method and all-clear lines and has dropped the time-late / TBC clock that is the whole of this PDF. A DPA who briefs Saturday as a completed salvage because later products printed crew-safe lines has under-read a numbered Attack that still withholds crew, fire and pollution.
Time-late, TBC and Verified is the second briefing fact. The report sits on a Wednesday incident date published on a Friday evening product, not on Friday’s 1800 UTC Lavan clock and not on Thursday’s 1600 UTC unused 186-26 clock. Channel 16, the UKMTO emergency line and the company duty officer still have to be on the night orders for any hull working an outbound Hormuz transit, the southern Omani corridor, or the approaches to Fujairah and Khor Fakkan. Do not treat “Verified” as a hull naming. Do not treat “time-late” as a closed damage file. Do not treat the missing crew and pollution lines as a clean bunker survey. The public PDF does not say whether the ship is still making way, whether propulsion is available, or where the ship went after Wednesday.
The geography is the third briefing fact. 189-26 prints Strait of Hormuz and an outbound transit. It does not print Khasab, Limah, Bukha, Ra’s Tahir, Lavan Island, or a TSS waypoint. Last night’s dedicated 188-26 remains an Arabian Gulf Attack 40 nautical miles south of Lavan Island. Friday morning’s dedicated 187-26 remains a Hormuz Attack 25 nautical miles northeast of Khasab. Thursday afternoon’s unused 186-26 remains a CSO Hormuz Attack with a Khasab, Oman footer. 189-26 is a Hormuz Attack. It is not a Lavan Attack. JMIC Update 109 still prints the Strait of Hormuz SEVERE and the Arabian Gulf SUBSTANTIAL. A passage plan that only carried Friday night’s Lavan offset, or that treated Wednesday as empty because Update 109’s last 96-hour list ended at 185-26, has not budgeted a time-late outbound-tanker projectile on 28 October.
Industry colour of the same clock, held separately: Iran International restated the UKMTO time-late 28 October crude-oil-tanker, unknown-projectile, outbound-Hormuz sentences and added that the incident was separate from Friday’s 40-nautical-mile south-of-Lavan Attack. Tilt restated the same PDF and added a “southern corridor” gloss that the product does not print. Those reprints are not a naming. Treat them as industry colour of the public PDF. Do not collapse them onto 189-26 as a completed identification, a southern-TSS plot, or a crew-status line.
What this is not
This is not a rewrite of 188-26, and it is not a Lavan Island file. Last night’s dedicated Warning 188-26 remains an unnamed vessel Attack, 1800 UTC 30 October, 40 nautical miles south of Lavan Island, unknown projectile on the port side, fire onboard, crew reported safe, no reported environmental impact at this time, source Master, location footer Lavan Island, Iran. Forty nautical miles south of Lavan is Arabian Gulf water. It is not an outbound Hormuz transit. A Friday 1800 UTC Master report is not a Wednesday TBC Verified report. Do not merge Friday evening’s Gulf Attack onto Friday evening’s later time-late Hormuz Attack because both print unknown projectile and sit on a 30 October product clock.
This is not a rewrite of 187-26, and it is not a Khasab attached-device file. Friday morning’s dedicated Warning 187-26 Update 001 remains an unnamed outbound tanker Attack, 2212 UTC 29 October, 25 nautical miles northeast of Khasab, port-side small boat, two explosive devices attached above the waterline, engine-room fire, temporarily disabled, fire extinguished, crew safe, no environmental impact, continuing to next port of call. Twenty-five nautical miles northeast of Khasab is not a TBC outbound plot. An attached-device method is not an unknown projectile. A continuing tanker with a crew-safe line is not a crude-oil tanker whose crew and onward status the PDF does not print. Do not merge Thursday night’s Hormuz Attack onto Wednesday’s time-late Attack because both print outbound.
This is not a rewrite of unused 186-26, and it is not NAVAREA IX 420/26. Thursday afternoon’s unused Warning 186-26 remains a CSO Attack: tanker struck by an unknown projectile at 1600 UTC 29 October whilst completing an outbound Hormuz transit, no reported injuries, no environmental impact report, location footer Khasab, Oman. 186-26 is 29 October. 189-26 is 28 October. 186-26 is CSO. 189-26 is Verified. 186-26 prints a 1600 UTC clock and a crew/environment line. 189-26 prints TBC and withholds both. Do not convert 186-26 onto 189-26 as a late naming. Do not convert 189-26’s unnamed crude oil tanker into 186-26’s Thursday afternoon CSO tanker. 186-26 remains unused as a dedicated file unless a later PDF names that hull, upgrades the damage line, or a NAVAREA plots it. 420/26, issued 300300 UTC 30 October and dedicated on last night’s companion piece, names oil tanker RITI, security incident causing fire onboard, anchored in 26-24.07N 056-24.72E, approximately 1 nautical mile northwest of Ra’s Tahir, mariners cautioned. 189-26 prints no name, no lat/long and no anchorage. Do not convert RITI onto 189-26 as a UKMTO naming.
This is not 185-26, and it is not Friday morning’s companion dhow wreck. Thursday late-morning’s dedicated Warning 185-26 remains a Suspicious Activity fire sighting 9 nautical miles north of Khasab at 0300 UTC, Third Party, unnamed vessel. Friday morning’s dedicated NAVAREA IX 417/26, issued 291500 UTC, is the working wreck instrument on dhow MSV Quba, MNV 2183, reported sunk in 26-19.95N 056-16.82E, about 3.5 nautical miles west of Jazirat Um Al Ghanam. 189-26 prints a crude oil tanker, Strait of Hormuz, outbound, Attack, unknown projectile. A dhow wreck off Um Al Ghanam is not a time-late tanker projectile. Do not merge the Quba wreck onto this Attack because both sit on a late-October Hormuz board.
This is not Update 110, and it is not an International Maritime Organization 122-count. JMIC Update 109, JMIC# 001 26, ICOD 291300 UTC 29 October, remains the last numbered public periodic note, with Hormuz SEVERE, the Arabian Gulf SUBSTANTIAL, the Gulf of Oman MODERATE and 160 incidents since 1 March. Update 109’s last 96-hour list ends at 185-26 as Unknown / Suspicious activity / 9 nautical miles north of Khasab. 186-26 at 1600 UTC 29 October, 187-26 at 2212 UTC, 188-26 at 1800 UTC 30 October and 189-26’s Wednesday incident all sit off that list as published. They are not a completed Update 110. Wednesday afternoon’s dedicated JMIC Advisory Note 016-26 remains the blockade visit-and-search document pack. The IMO highlighted-incidents board is still 121 confirmed / 24 seafarer fatalities as at 27 October, with Leonora Kosan still the newest named row. 189-26 does not fill those slots. This is not Thursday’s dedicated Contship Jet or Khoryv Black Sea files. NAVWARN 768/26 and 766/26 are Kaliakra and Shabla products. They do not belong on a Hormuz Attack. 184-26 / 416/26 remains the Gulf of Aden PAG keep-clear through 032359 UTC 3 November.
Operational implications
For a master already shaping an outbound Hormuz transit, or holding at Fujairah, Khor Fakkan, Sohar or the southern Omani corridor this morning, Saturday is a time-late Attack on a Wednesday clock, on top of Friday night’s 40-nautical-mile south-of-Lavan projectile, Friday morning’s 25-nautical-mile northeast-of-Khasab attached-device Attack, and Thursday afternoon’s unused 186-26 outbound-Hormuz projectile. Update 109 remains the last numbered JMIC note and still prints Hormuz SEVERE. 016-26 remains the working blockade document pack for hulls that still need the Strait: continuous VHF 16, follow US forces, be prepared to alter, stop or come dead in the water, and have the six signed-or-stamped PDFs ready. 189-26 adds a verified time-late report that a crude oil tanker was already hit on an outbound transit two days before Friday’s Lavan Attack reached the board. A passage plan that only carried Update 109’s 185-26 cut-off, or that treated Wednesday as quiet because no Warning carried a 28 October timestamp until Friday night, has not budgeted a back-dated outbound projectile.
Unknown projectile on an outbound crude-oil tanker is a standoff watchkeeping problem before it is a war-risk rewrite. 189-26 is not 187-26’s alongside, slow-speed, above-waterline device problem. It is a lookout, CPA, AIS-on/AIS-off, citadel and possible-disablement problem at the same time as it is a missing-damage-line problem. BMP MS projectile and citadel guidance remains the working industry pack; 189-26 does not reprint it and does not order an armed team. It also does not authorise a master to treat every radar contact in the Strait as a confirmed Attack. Log the Warning number, the 28 October date, the TBC clock, the Verified source line, the time-late wording, the crude-oil-tanker type, the unknown-projectile method, and the outbound-Hormuz transit. Do not log RITI, Louise 1, Ghana Prosperity, a small-boat device, a mine in the water, a Lavan offset, a crew-safe line, or an IRGC attribution that the PDF does not print.
The missing crew, fire and pollution lines are the practical damage watch, not a completed all-clear. The public PDF says none of those things. It does not say whether the ship is making way, whether propulsion or steering is available, whether a tug was offered, whether the hull is holed, or where the ship went after Wednesday. Those missing lines are omissions. They are not a completed “all well,” and they are not a NUC. Next-port authorities will want a written account that 189-26 does not contain. Charterers and war-risk underwriters will now ask whether the ship was on an outbound Hormuz transit on 28 October, whether it reported, and whether it was following Update 109 and 016-26. They will not be answered by Friday night’s 188-26 Lavan Attack, by Friday morning’s 187-26 Khasab Attack, by Tuesday’s 121-count, or by Monday’s 183-26 Al-Faw fire.
For a DPA and an operator with crude, products, LPG or any merchant hull still using the Strait, the reporting split is the operational content. Sightings of projectiles, fire, smoke, a disabled hull or pollution go to UKMTO on the 189-26 action line and to the company security officer. NAVCENT NCAGS remains the 016-26 blockade mailbox for hulls that still need the Strait. MSCIO remains the EU ATALANTA registration and alert desk. Registering with one mailbox is not a substitute for the others. 189-26 does not order a daylight-only transit, a deviation around a published circle, or a halt to visit-and-search compliance. Keep Update 109 Hormuz SEVERE / Arabian Gulf SUBSTANTIAL and 016-26 visit-and-search in the master’s pack. Watch a PDF revision that names a hull, prints a time, a lat/long, a NUC, a tow, a fire or a crew line; a NAVAREA that plots this tanker rather than RITI or Quba; a flag or class note; a JMIC Update 110; or an IMO-board row — not a headline that Friday night closed the Wednesday file.
Keep the dedicated files on their own lines. 188-26 remains last night’s unnamed vessel Attack 40 nautical miles south of Lavan Island. 187-26 remains Friday morning’s unnamed outbound-tanker Attack 25 nautical miles northeast of Khasab. 417/26 remains Friday morning’s dedicated MSV Quba wreck. 420/26 remains last night’s dedicated RITI fire-and-anchor NAVAREA. 186-26 remains the unused 1600 UTC unknown-projectile Attack. 185-26 remains Thursday’s 9-nautical-mile north-of-Khasab fire sighting. 184-26 / 416/26 remains the Gulf of Aden PAG keep-clear through 3 November. 183-26 remains the 26 October Al-Faw fire. 182-26 remains the 23 October outbound-Hormuz disablement, now named Ghana Prosperity on Update 109 as wrap, not as an 189-26 hull. 181-26 / Leonora Kosan remains Limah. 179-26 / Al Dasma remains Bukha. Cape Dao remains 403/26 / the 23 September IMO row. Update 109 remains the last periodic threat note, Hormuz still SEVERE, Arabian Gulf still SUBSTANTIAL. 016-26 remains Wednesday afternoon’s blockade document pack. Thursday’s 768/26 and 766/26 remain the Kaliakra and Shabla Black Sea files. Do not recast 31 October morning as a named RITI, as a Louise 1 conversion, as unused 186-26 finally published, as Update 110, as an IMO 122-count, or as a Strait closure.
What Operators Should Note
- Log 189-26 as a time-late Hormuz Attack on a crude oil tanker, not as a Lavan rewrite and not as a RITI naming. UKMTO Warning 189-26, incident 28 October 2026, time TBC, source Verified. Filename
20261030-ukmto_warning_189-26.pdf. Time-late report. Strait of Hormuz. Crude oil tanker. Unknown projectile. Outbound transit. Transit with caution. Report suspicious activity to UKMTO, [email protected] / +44 (0)2392222060. Authorities are investigating. UKMTO printed neither hull, IMO, flag, cargo grade, attacker, lat/long, anchorage, NUC, tow, fire, crew status, environmental line, nor a keep-clear radius. This is not 188-26, not 187-26, not 186-26, not 420/26, not 417/26, and not Update 109. - Hold the clock and the water. 189-26 is Attack, not Suspicious Activity. The working date is 28 October. The working time is TBC. The working source is Verified, not Master and not CSO. The working water is the Strait of Hormuz on an outbound transit, not 40 nautical miles south of Lavan Island and not 25 nautical miles northeast of Khasab. Do not brief Saturday as “Friday’s Lavan hit, filed late.” Do not brief Saturday as quiet because the PDF withholds crew and fire.
- Hold Iran International / Tilt colour separately. Iran International restated the PDF and said the incident was separate from Friday’s Lavan Attack. Tilt added a southern-corridor gloss that the product does not print. Neither reprint named a hull, a flag or a cargo grade. Do not promote a wire rewrite to an 189-26 naming, a TSS plot, or a crew line.
- Do not collapse 188-26, 187-26, 186-26 or 420/26 onto this number. 188-26 remains the dedicated 1800 UTC unnamed vessel Attack 40 nautical miles south of Lavan Island, port-side projectile, fire, crew safe. 187-26 remains the dedicated 2212 UTC attached-device Attack 25 nautical miles northeast of Khasab, continuing. 186-26 remains the unused 1600 UTC 29 October CSO unknown-projectile Attack on an outbound Hormuz tanker, Khasab footer. 420/26 remains last night’s dedicated RITI fire-and-anchor at 26-24.07N 056-24.72E. Four Friday or Thursday products are four products. Do not make them one hull.
- Do not merge this watch onto Quba, Aden, Al-Faw, Limah, Bukha or Cape Dao. 417/26 remains the dedicated MSV Quba sunk file, 26-19.95N 056-16.82E. 185-26 remains the 0300 UTC 9-nautical-mile north-of-Khasab fire. 184-26 / 416/26 remains the Gulf of Aden PAG keep-clear through 3 November. 183-26 remains the 63-nautical-mile Al-Faw fire. 182-26 remains the outbound disablement, Ghana Prosperity on Update 109 as wrap only. 181-26 / Leonora Kosan remains Limah. 179-26 / Al Dasma remains Bukha. Cape Dao remains the 23 September 15-nautical-mile northeast-of-Khasab IMO wreck. IMO still 121 / 24 as at 27 October. Update 109 ICOD remains 291300 UTC 29 October. 016-26 remains the blockade document pack.
- Treat the missing crew, fire and onward-status lines as open damage lines. The public tape does not print a crew-safe sentence, a fire, a survey, a hole size, a NUC interval, a tug, a next-port name or a class note. Keep Update 109 Hormuz SEVERE / Arabian Gulf SUBSTANTIAL and 016-26 visit-and-search in the master’s pack. Watch a PDF revision that names a hull or prints a time or lat/long; a NAVAREA that plots this tanker; a flag or class note; a JMIC Update 110; or an IMO-board row — not a headline that Friday night closed Wednesday’s outbound file or completed a salvage.
Regulas Shipping will keep lining Warning 189-26 against last night’s dedicated 188-26 Lavan Attack and against Update 109’s earlier 291300 UTC cut-off so operators can treat Saturday’s tape as a numbered time-late crude-oil-tanker Attack on a Wednesday outbound Hormuz transit, not as a Lavan rewrite, a named RITI, or a completed class survey.
