{"id":1145,"date":"2026-10-30T23:38:02","date_gmt":"2026-10-30T23:38:02","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-188-26-records-a-projectile-hit-40-nm-south-of-lavan-island\/"},"modified":"2026-10-30T23:38:02","modified_gmt":"2026-10-30T23:38:02","slug":"ukmto-188-26-records-a-projectile-hit-40-nm-south-of-lavan-island","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-188-26-records-a-projectile-hit-40-nm-south-of-lavan-island\/","title":{"rendered":"UKMTO 188-26 records a projectile hit 40 NM south of Lavan Island"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre published Warning 188-26 as a numbered PDF on its product board, filename 20261030-ukmto_warning_188.pdf<\/code>. The face of the product is titled 188-26 \u2014 ATTACK. The incident date is 30 October 2026. The incident time is 1800 UTC. The source line is Master. UKMTO states that it has received a report of an incident 40 nautical miles south of Lavan Island, Iran. A vessel has been hit by an unknown projectile on the port side, which has caused a fire onboard. The crew of the vessel have been reported as safe and there is no reported environmental impact at this time. Vessels are advised to transit with caution and report any suspicious activity to UKMTO, whilst authorities investigate. The location footer on the PDF is Lavan Island, Iran. Emergency contacts printed on the product remain watchkeepers@ukmto.org and +44 (0)2392222060.<\/p>\n

That is the working primary. Friday evening\u2019s product is a Warning typed as Attack, not a Suspicious Activity file and not an Advisory. It does not name a merchant hull, an IMO number, a flag, a ship type beyond \u201cvessel,\u201d a cargo, an attacker, a NUC or tow line, an anchorage, or a latitude\/longitude beyond the 40-nautical-mile south-of-Lavan-Island offset. Friday morning\u2019s dedicated 187-26 piece on this desk, published about 11:41 UTC, still told operators that UKMTO ended at Attack Update 001 on 187-26, 25 nautical miles northeast of Khasab. 188-26 was not on that board when that note was written. Masters who brief Friday night as a rewrite of the Khasab attached-device Attack, as a named RITI wreck, as a Louise 1 conversion, or as Update 110 will have merged four other series into a new Arabian Gulf clock.<\/p>\n

What the warning actually printed<\/h2>\n

The confirmed tape is the body of 188-26. UKMTO has received a report of an incident 40NM south of Lavan Island, Iran. UKMTO has received a report that a vessel has been hit by an unknown projectile on the port side which has caused a fire onboard. The crew of the vessel have been reported as safe and there is no reported environmental impact at this time. 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 a tanker, LPG or products type. The PDF prints \u201cvessel,\u201d not tanker. Do not invent a UAV, a mine, a small-boat device or a boarding. Do not invent a lat\/long on the UKMTO PDF. 188-26 does not print one. Do not invent a keep-clear radius around Lavan Island. The PDF does not print one.<\/p>\n

The product type is the first briefing fact. 188-26 is Attack, the same family that ran 174-26 through 177-26, 179-26, 180-26, 181-26, 182-26, Thursday afternoon\u2019s unused 186-26 and Friday morning\u2019s dedicated 187-26, not the Suspicious Activity family that ran 183-26 and Thursday morning\u2019s dedicated 185-26, and not the Advisory family that ran 184-26 and 178-26. UKMTO says an unknown projectile hit the port side and caused a fire. 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, or continuing to the next port of call. A DPA who briefs Friday night as \u201canother Hormuz attached-device hit, crew safe\u201d has borrowed 187-26\u2019s method line and has dropped the Lavan Island offset that is the whole of this PDF. A DPA who briefs Friday night as a completed salvage because the crew are safe has under-read a numbered Attack that already puts a burning vessel 40 nautical miles south of Lavan Island on the board.<\/p>\n

Master, 1800 UTC and Lavan Island is the second briefing fact. The report sits on a Friday evening Arabian Gulf clock, not on a Thursday night Hormuz clock. Channel 16, the UKMTO emergency line and the company duty officer still have to be on the night orders for any hull working the northern and central Arabian Gulf, Lavan, Kharg, the Saudi and Qatari coasts, or the approaches to the Strait of Hormuz from the west. Do not treat \u201cMaster\u201d as a hull naming. Do not treat \u201ccrew reported as safe\u201d as a completed class survey or as a closed damage file. Do not treat \u201cno reported environmental impact at this time\u201d as a clean bunker survey. The public PDF does not say whether the fire is out, whether propulsion is available, or where the ship is heading.<\/p>\n

The geography is the third briefing fact. Lavan Island is an Iranian oil-terminal island in the northern Arabian Gulf, not a Musandam or Khasab offset and not a Strait of Hormuz TSS waypoint. Forty nautical miles south of Lavan is central-to-northern Gulf water, on the order of 150 nautical miles west of Ra\u2019s Tahir and well west of Friday morning\u2019s 25-nautical-mile northeast-of-Khasab Attack. JMIC Update 109 still prints the Arabian Gulf SUBSTANTIAL and the Strait of Hormuz SEVERE. 188-26 is an Arabian Gulf Attack. It is not a Hormuz Attack. A passage plan that only carried Update 109\u2019s Hormuz SEVERE line, or that treated the Gulf as quiet because the last dedicated Arabian Gulf Attack files on this desk were mid-October\u2019s 174-26 and 175-26 off Al Jubayl, has not budgeted a Friday 1800 UTC projectile hit 40 nautical miles south of Lavan Island.<\/p>\n

Industry colour of the same clock, held separately: Reuters and Newsquawk restated the UKMTO 40-nautical-mile south-of-Lavan, unknown-projectile, port-side, fire, crew-safe and no-immediate-environmental-impact sentences without adding a hull, a flag, a cargo or an attacker. Those reprints are not a naming. Treat them as industry colour of the public PDF. Do not collapse them onto 188-26 as a completed identification.<\/p>\n

What this is not<\/h2>\n

This is not a rewrite of 187-26, and it is not a Khasab attached-device file. Friday morning\u2019s 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 40 nautical miles south of Lavan Island. An attached-device method is not an unknown projectile. A continuing tanker is not a vessel whose onward status the PDF does not print. Do not merge Thursday night\u2019s Hormuz Attack onto Friday evening\u2019s Arabian Gulf Attack because both print port side and fire.<\/p>\n

This is not a rewrite of 186-26, and it is not NAVAREA IX 420\/26. Thursday afternoon\u2019s unused Warning 186-26 remains a CSO Attack: tanker struck by an unknown projectile at 1600 UTC whilst completing an outbound Hormuz transit, no reported injuries, no environmental impact report, location footer Khasab, Oman. 420\/26, issued 300300 UTC 30 October, names oil tanker RITI, security incident causing fire onboard, anchored in 26-24.07N 056-24.72E, approximately 1 nautical mile northwest of Ra\u2019s Tahir, mariners cautioned. 188-26 prints no name, no lat\/long and no anchorage. It prints Lavan Island, not Ra\u2019s Tahir. Do not convert RITI onto 188-26 as a UKMTO naming. Do not convert 188-26\u2019s unnamed vessel into 420\/26\u2019s anchored tanker. Hold 420\/26 as a separate Friday NAVAREA naming. 186-26 remains unused as a dedicated file unless a later PDF names that hull, upgrades the damage line, or a NAVAREA plots it.<\/p>\n

This is not 185-26, and it is not Friday\u2019s companion dhow wreck. Thursday late-morning\u2019s dedicated Warning 185-26 remains a Suspicious Activity fire sighting 9 nautical miles north of Khasab at 0300 UTC, Third Party, unnamed vessel, crew then unknown. Friday morning\u2019s 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. 188-26 prints a vessel, 40 nautical miles south of Lavan Island, 1800 UTC, Attack, fire. A dhow wreck off Um Al Ghanam is not a projectile hit off Lavan. Do not merge the morning wreck onto the evening Attack because both sit on a 30 October clock.<\/p>\n

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\u2019s last 96-hour list ends at 185-26 as Unknown \/ Suspicious activity \/ 9 nautical miles north of Khasab. 186-26 at 1600 UTC, 187-26 at 2212 UTC and 188-26 at 1800 UTC 30 October all sit after that cut-off. They are not on that note. Wednesday afternoon\u2019s 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. 188-26 does not fill those slots. This is not Thursday\u2019s 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 Lavan Island Attack. 184-26 \/ 416\/26 remains the Gulf of Aden PAG keep-clear through 032359 UTC 3 November.<\/p>\n

Operational implications<\/h2>\n

For a master already in the Arabian Gulf, shaping a transit past Lavan, Kharg, the Saudi or Qatari coasts, or working the western approaches to the Strait of Hormuz this evening, Friday night is an unknown-projectile Attack on a new 40-nautical-mile south-of-Lavan-Island offset, on top of Friday morning\u2019s 25-nautical-mile northeast-of-Khasab attached-device Attack and Thursday afternoon\u2019s unused 186-26 outbound-Hormuz projectile Attack. Update 109 remains the last numbered JMIC note and still prints the Arabian Gulf SUBSTANTIAL. 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. 188-26 adds a verified Master report of a port-side projectile hit after dark in the northern Gulf. A passage plan that only carried Update 109\u2019s Hormuz SEVERE line, or that treated the Gulf as a mid-October Al Jubayl problem because the last dedicated Arabian Gulf Attack files on this desk were 174-26 and 175-26, has not budgeted an 1800 UTC Friday projectile 40 nautical miles south of Lavan Island.<\/p>\n

Unknown projectile on the port side is a standoff watchkeeping problem before it is a war-risk rewrite. 188-26 is not 187-26\u2019s alongside, slow-speed, above-waterline device problem. It is a lookout, CPA, AIS-on\/AIS-off, citadel and fire problem at the same time as it is an engine-room and possible-disablement problem. BMP MS projectile and citadel guidance remains the working industry pack; 188-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 northern Gulf as a confirmed Attack. Log the Warning number, the 1800 UTC clock, the 40-nautical-mile south-of-Lavan-Island offset, the Master source line, the unknown-projectile method, the port-side hit, the fire, the crew-safe line, and the no-environmental-impact-at-this-time line. Do not log RITI, Louise 1, a small-boat device, a mine in the water, a Hormuz TSS waypoint, or an IRGC attribution that the PDF does not print.<\/p>\n

Fire and an open onward-status line are the practical damage watch, not a completed all-clear. The public PDF says the crew are safe and there is no reported environmental impact at this time. It does not say the fire is out, whether propulsion or steering is available, whether a tug was offered, whether the hull is holed, or where the ship is heading. Those missing lines are omissions. They are not a completed \u201call well,\u201d and they are not a NUC. Next-port authorities will want a written account that 188-26 does not contain. Charterers and war-risk underwriters will now ask whether the ship was 40 nautical miles south of Lavan Island after 1800 UTC 30 October, whether it reported, and whether it was following Update 109 and 016-26. They will not be answered by Friday morning\u2019s 187-26 Khasab Attack, by Tuesday\u2019s 121-count, or by Monday\u2019s 183-26 Al-Faw fire.<\/p>\n

For a DPA and an operator with tankers, LPG, products or any merchant hull still using the Arabian Gulf or the western Hormuz approaches, the reporting split is the operational content. Sightings of projectiles, fire, smoke, a disabled hull or pollution go to UKMTO on the 188-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. 188-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 Arabian Gulf SUBSTANTIAL \/ Hormuz SEVERE and 016-26 visit-and-search in the master\u2019s pack. Watch a PDF revision that names a hull, prints a lat\/long, a NUC, a tow, an anchorage or a fire-extinguished line; a NAVAREA that plots this vessel rather than RITI; a flag or class note; a JMIC Update 110; or an IMO-board row \u2014 not a headline that Friday evening closed the Arabian Gulf.<\/p>\n

Keep the dedicated files on their own lines. 187-26 remains Friday morning\u2019s unnamed outbound-tanker Attack 25 nautical miles northeast of Khasab. 417\/26 remains Friday morning\u2019s dedicated MSV Quba wreck. 186-26 remains the unused 1600 UTC unknown-projectile Attack. 420\/26 remains the unused RITI fire-and-anchor NAVAREA until this desk\u2019s companion piece on that number. 185-26 remains Thursday\u2019s 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 188-26 hull. 181-26 \/ Leonora Kosan remains Limah. 179-26 \/ Al Dasma remains Bukha. 174-26 and 175-26 remain the mid-October Al Jubayl Arabian Gulf Attacks. 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\u2019s blockade document pack. Thursday\u2019s 768\/26 and 766\/26 remain the Kaliakra and Shabla Black Sea files. Do not recast 30 October evening as a named RITI, as a Louise 1 conversion, as Update 110, as an IMO 122-count, or as a Gulf closure.<\/p>\n

What Operators Should Note<\/h2>\n
    \n
  • Log 188-26 as an Arabian Gulf Attack with an unknown projectile, not as a Hormuz attached-device file and not as a RITI naming.<\/strong> UKMTO Warning 188-26, incident 30 October 2026, 1800 UTC, source Master, location footer Lavan Island, Iran. Filename 20261030-ukmto_warning_188.pdf<\/code>. Forty nautical miles south of Lavan Island. Vessel. Unknown projectile on the port side. Fire onboard. Crew reported safe. No reported environmental impact at this time. Transit with caution. Report suspicious activity to UKMTO, watchkeepers@ukmto.org \/ +44 (0)2392222060. Authorities are investigating. UKMTO printed neither hull, IMO, flag, ship type beyond vessel, cargo, attacker, lat\/long, anchorage, NUC, tow, nor a keep-clear radius. This is not 187-26, not 186-26, not 420\/26, not 417\/26, and not Update 109.<\/li>\n
  • Hold the method and the water.<\/strong> 188-26 is Attack, not Suspicious Activity. The working weapon print is an unknown projectile on the port side, not two explosive devices attached above the waterline. The working water is 40 nautical miles south of Lavan Island in the Arabian Gulf, not 25 nautical miles northeast of Khasab in the Strait of Hormuz. Do not brief Friday night as \u201canother Hormuz small-boat hit, continuing, all well.\u201d Do not brief Friday night as quiet because the crew are safe.<\/li>\n
  • Hold Reuters \/ Newsquawk colour separately.<\/strong> Those reprints restated the PDF without adding a hull, a flag or a cargo. None of those extras sit on the product. Do not promote a wire rewrite to an 188-26 naming or to a flag line.<\/li>\n
  • Do not collapse 420\/26 RITI, 187-26 or 186-26 onto this number.<\/strong> 420\/26 names oil tanker RITI, fire, anchored, 26-24.07N 056-24.72E, 1 nautical mile northwest of Ra\u2019s Tahir. 188-26 prints no name, no lat\/long and no anchorage, and prints Lavan Island, not Ra\u2019s Tahir. 187-26 remains the dedicated 2212 UTC attached-device Attack 25 nautical miles northeast of Khasab, continuing. 186-26 remains the unused 1600 UTC CSO unknown-projectile Attack on an outbound Hormuz tanker. Three Friday or Thursday products are three products. Do not make them one hull.<\/li>\n
  • Do not merge this watch onto the Quba wreck, Aden, Al-Faw, Limah, Bukha, Al Jubayl or Cape Dao.<\/strong> 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. 174-26 and 175-26 remain the mid-October Al Jubayl Attacks. Cape Dao remains the 23 September 15-nautical-mile northeast-of-Khasab IMO wreck. Forty nautical miles south of Lavan Island is a new offset. IMO still 121 \/ 24 as at 27 October. Update 109 ICOD remains 291300 UTC 29 October. 016-26 remains the blockade document pack.<\/li>\n
  • Treat fire and the missing onward-status line as open damage lines.<\/strong> The public tape says the crew are safe and there is no reported environmental impact at this time. It does not print a fire-extinguished line, a survey, a hole size, a NUC interval, a tug, a next-port name or a class note. Keep Update 109 Arabian Gulf SUBSTANTIAL \/ Hormuz SEVERE and 016-26 visit-and-search in the master\u2019s pack. Watch a PDF revision that names a hull or prints a lat\/long; a NAVAREA that plots this vessel; a flag or class note; a JMIC Update 110; or an IMO-board row \u2014 not a headline that Friday evening closed the Arabian Gulf or completed a salvage.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Warning 188-26 against Friday morning\u2019s dedicated 187-26 Khasab Attack and against Update 109\u2019s earlier 291300 UTC cut-off so operators can treat Friday evening\u2019s tape as a numbered unnamed vessel Attack 40 nautical miles south of Lavan Island, not as a Hormuz rewrite, a named RITI, or a completed class survey.<\/p>\n","protected":false},"excerpt":{"rendered":"

    The United Kingdom Maritime Trade Operations centre published Warning 188-26 as a numbered PDF on its product board, filename 20261030-ukmto_warning_188.pdf. The face of the product is titled 188-26 \u2014 ATTACK. The incident date is 30 October 2026. The incident time is 1800 UTC. The source line is Master. UKMTO states that it has received a […]<\/p>\n","protected":false},"author":1,"featured_media":1143,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wpai_generated_summary":"","wpai_meta_description":"","footnotes":""},"categories":[26,18,4],"tags":[],"class_list":["post-1145","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-highlights","category-maritime-industry","category-maritime-security"],"_links":{"self":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1145","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/comments?post=1145"}],"version-history":[{"count":0,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1145\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/1143"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=1145"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=1145"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=1145"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}