{"id":1137,"date":"2026-10-29T11:35:10","date_gmt":"2026-10-29T11:35:10","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-185-26-records-a-vessel-fire-9-nm-north-of-khasab\/"},"modified":"2026-10-29T11:35:10","modified_gmt":"2026-10-29T11:35:10","slug":"ukmto-185-26-records-a-vessel-fire-9-nm-north-of-khasab","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-185-26-records-a-vessel-fire-9-nm-north-of-khasab\/","title":{"rendered":"UKMTO 185-26 records a vessel fire 9 NM north of Khasab"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre published Warning 185-26 as a numbered PDF on its product board, filename 20261029-ukmto_warning-185-26.pdf<\/code>. The face of the product is titled 185-26 \u2014 SUSPICIOUS ACTIVITY. The incident date is 29 October 2026. The incident time is 0300 UTC. The source line is Third Party. UKMTO states that it has received a report of an incident occurring in the Strait of Hormuz, 9 nautical miles north of Khasab, Oman. The master of a third-party vessel has reported sighting another vessel on fire. Status of crew is unknown. 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, whilst authorities investigate. The location footer on the PDF is Khasab, Oman. Emergency contacts printed on the product remain watchkeepers@ukmto.org and +44 (0)2392222060.<\/p>\n

That is the working primary. Thursday\u2019s product is a Warning typed as Suspicious Activity, not an Attack and not an Advisory. It does not name a merchant hull, an IMO number, a flag, a vessel type, a cargo, a projectile, an attacker, a fire origin, a NUC or tow line, or a latitude\/longitude beyond the Khasab offset. Thursday morning\u2019s dedicated NAVWARN 759\/26 and 766\/26 pieces on this desk, published about 03:38 UTC, still told operators that UKMTO ended at Advisory 184-26. 185-26 was not on that board when those notes were written. Masters who brief Thursday as an Attack PDF, as a Cape Dao rewrite, as a named IRGC mine strike, or as Update 109 will have merged a third-party fire sighting into four other series.<\/p>\n

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

The confirmed tape is the body of 185-26. UKMTO has received a report of an incident occurring in the Strait of Hormuz, 9NM north of Khasab, Oman. The Master of a third-party vessel has reported sighting another vessel on fire. Status of crew is unknown. 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, whilst authorities investigate. That is the product. Stay with that wording. Do not invent a hull, a tanker type, a projectile, a mine, a submergence line, or a SAR complete. Do not invent a lat\/long on the UKMTO PDF. 185-26 does not print one. Do not invent a keep-clear radius around Khasab. The PDF does not print one.<\/p>\n

The product type is the first briefing fact. 185-26 is Suspicious Activity, the same family as Monday\u2019s dedicated 183-26 Al-Faw fire, not the Attack family that ran 174-26 through 177-26, 179-26, 180-26, 181-26 and 182-26, and not the Advisory family that ran 184-26 and 178-26. UKMTO says a third-party master sighted another vessel on fire. It does not say a master reported a hit. It does not say a company security officer confirmed a projectile. It does not say the fire is extinguished. It does not say the ship is at anchor, NUC, under tow, mostly submerged, or proceeding. A DPA who briefs Thursday as \u201cconfirmed tanker Attack, projectile, crew safe, no pollution\u201d has borrowed Friday\u2019s 182-26 disablement language and has filled every gap the PDF left open. A DPA who briefs Thursday as nothing because the type is not Attack has under-read a numbered warning that already puts a fire 9 nautical miles north of Khasab on the board.<\/p>\n

Third-party and 0300 UTC is the second briefing fact. 182-26 was a verified time-late Attack published three days after a Friday 0839 UTC clock. 181-26 was a time-late Company Security Officer Attack. 185-26 is a same-day Third Party product with a printed incident time. The centre has a fire sighting from a passing master and has not yet printed a named hull, a CSO, or a verified Attack line. Channel 16, the UKMTO emergency line and the company duty officer still have to be on the night orders for any hull working the Musandam approaches or the southern Hormuz corridor. Do not treat \u201cThird Party\u201d as a hull naming. Do not treat 0300 UTC as evidence that the event was minor.<\/p>\n

Agency and industry colour of the same clock, held separately: Anadolu Agency, Iran International and Deutsche Welle Thursday reprints restated the UKMTO fire-sighting sentence without adding a hull. Seatrade Maritime and Maritime Executive carried Vanguard Tech colour that a tanker had been struck by an unknown projectile 9 nautical miles north of Khasab in the southern corridor at 03:00 UTC, that the master of a Panama-flagged tanker reported passing a vessel on fire and mostly submerged, and that another vessel was observed nearby, potentially providing assistance. Those extras are not on the UKMTO PDF. UKMTO printed \u201cvessel,\u201d not \u201ctanker.\u201d It printed \u201csighting another vessel on fire,\u201d not \u201cstruck by an unknown projectile.\u201d It printed no submergence line and no assisting hull. Treat Vanguard\u2019s tanker \/ projectile \/ mostly-submerged \/ Panama-flagged reporter \/ assisting-vessel lines as industry colour. Do not collapse them onto 185-26 as a naming, a type line, a wreck finding, or an Attack conversion.<\/p>\n

Same-day attribution colour, also held separately: Iranian state and IRGC-affiliated outlets described three oil tankers exploding and catching fire after hitting mines on an \u201cunauthorized southern route\u201d of the Strait of Hormuz, with radar and navigation systems switched off. Reuters and AFP carried that claim. US Central Command stated that Iranian-controlled media reports of commercial vessels hitting sea mines in the strait are false, and that internationally recognized primary transit routes have been cleared of sea mines by US forces. None of that attribution sits on 185-26. The PDF describes one burning vessel, 9 nautical miles north of Khasab, sourced to a third-party master. It does not print a mine, a three-tanker tally, a southern-route finding, or a CENTCOM line. Do not brief Thursday\u2019s warning as an IRGC mine confirmation or as a CENTCOM all-clear.<\/p>\n

What this is not<\/h2>\n

This is not a rewrite of 184-26, and it is not a Gulf of Aden product. Wednesday night\u2019s dedicated Advisory 184-26 remains a Pirate Action Group watch in the Gulf of Aden, with NAVAREA IX 416\/26 as the 12-42N 047-35E keep-clear until 032359 UTC 3 November. 185-26 prints Khasab, Oman. It prints none of that Aden small-craft language. Pakistan\u2019s in-force NAVAREA IX table on Thursday still ends at 416\/26. There is no 417\/26 wrap on this fire at the time of writing. Do not invent a Hormuz NAVAREA because 183-26 also had none on publication.<\/p>\n

This is not a rewrite of 183-26, 182-26, 181-26 or 179-26. 183-26 remains Monday\u2019s dedicated Suspicious Activity fire 63 nautical miles southeast of Al-Faw, time TBC, Third Party. 182-26 remains Monday\u2019s dedicated outbound-Hormuz Attack with a disablement line and crew reported safe. 181-26 remains Friday\u2019s dedicated unnamed tanker Attack 7 nautical miles northeast of Limah, later typed as an LPG tanker on Update 108 and named Leonora Kosan on Tuesday\u2019s dedicated IMO 121-count. 179-26 remains the dedicated Bukha fire, 11 nautical miles west of Bukha, later wrapped as Al Dasma at anchor. 185-26 prints none of those hulls and none of those offsets. Nine nautical miles north of Khasab is a new circle on a new 0300 UTC 29 October clock. Bukha is not Khasab. Limah is not Khasab. Al-Faw is not the Strait of Hormuz.<\/p>\n

This is not a rewrite of Cape Dao. Saturday\u2019s dedicated NAVAREA IX 403\/26 remains the Cape Dao sunk file, later cancelled by 410\/26. The IMO highlighted-incidents board still carries Cape Dao, IMO 9219020, 23 September, 15 nautical miles northeast of Khasab, Oman, damaged, no pollution, one seafarer fatality, sunk. Fifteen nautical miles northeast of Khasab is not 9 nautical miles north of Khasab, and 23 September is not 29 October. Do not move a named wreck from September onto this morning\u2019s unnamed fire sighting because both files sit off Musandam. Ghana Prosperity, 404\/26 and the 4.5-nautical-mile south-of-Musandam plot remain their dedicated files. Petro Dolphin \/ NAVAREA IX 389\/26 remains the 12 October Gulf of Oman security-incident line, still in force on Thursday\u2019s Pakistan table.<\/p>\n

This is not Update 109. Update 108, JMIC# 001 26, ICOD 251300 UTC 25 October, remains the last numbered public periodic note, with Hormuz SEVERE, the Arabian Gulf SUBSTANTIAL, the Gulf of Oman MODERATE and 156 incidents since 1 March. 185-26, 184-26, 183-26 and 182-26 all sit after that cut-off. Wednesday afternoon\u2019s dedicated JMIC Advisory Note 016-26 remains the blockade visit-and-search document pack for the Gulf, the Strait of Hormuz, the Gulf of Oman and the Arabian Sea. It is not this fire. Do not recast 016-26 as having predicted 185-26, and do not recast 185-26 as a Hormuz reopen or as a completed Update 109.<\/p>\n

This is not an International Maritime Organization 122-count. The highlighted-incidents board is still 121 confirmed \/ 24 seafarer fatalities as at 27 October, with Leonora Kosan still the newest named row. 176-26, 182-26, 183-26 and 185-26 remain unnamed on that board. 185-26 does not fill those slots. This is not Thursday morning\u2019s dedicated Contship Jet or Khoryv Black Sea files. NAVWARN 759\/26 and 766\/26 are Kaliakra and Shabla products. They do not belong on a Khasab warning.<\/p>\n

Operational implications<\/h2>\n

For a master already in the Strait of Hormuz, shaping an outbound transit past Musandam, or working Khasab, Bukha, Limah, Fujairah or Khor Fakkan this morning, Thursday is a fire-and-unknown-status problem on a new 9-nautical-mile north-of-Khasab offset. Update 108 remains the last numbered JMIC note and still prints Hormuz SEVERE. 016-26 remains the working blockade document pack: 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. 185-26 adds a third-party fire sighting on that same water. A passage plan that only carried Update 108\u2019s SEVERE line, or that treated Musandam as quiet because the last dedicated Hormuz Attack on this desk was 182-26 on Friday\u2019s 0839 UTC clock, has not budgeted a 0300 UTC Thursday fire 9 nautical miles north of Khasab with crew, damage and pollution still unknown.<\/p>\n

Unknown crew, unknown damage and unknown pollution are the practical watch, not a completed all-clear and not a wreck finding. A vessel reported on fire in the strait is a reporting, SAR, damage-survey, tow, refuge and pollution-watch problem before anyone has a public class note. P&I, class and the nearest coastal State will want a written account that the public PDF does not contain: whether anyone is still aboard, 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. Vanguard\u2019s mostly-submerged colour, if it later becomes a flag, class, NAVAREA or UKMTO revision, would convert this file from a fire sighting into a wreck-and-keep-clear problem. It has not done so on the PDF. The missing lines are omissions. They are not a completed \u201call well,\u201d and they are not a completed sinking.<\/p>\n

For a DPA and an operator with tankers, LPG, products or any merchant hull still using the southern Hormuz corridor, the reporting split is the operational content. Sightings of fire, smoke, a disabled hull, persons in the water or pollution go to UKMTO on the 185-26 action line and to the company security officer. NAVCENT NCAGS remains the 016-26 blockade mailbox. MSCIO remains the EU ATALANTA registration and alert desk. Registering with one mailbox is not a substitute for the others. 185-26 does not order an armed team, a daylight-only transit, a deviation around a published circle, or a halt to visit-and-search compliance. It also does not authorise a master to treat a fire sighting as a confirmed Attack, a mine strike, or a named hull after the fact. Log the Warning number, the 0300 UTC clock, the 9-nautical-mile north-of-Khasab offset, the Third Party source line, and the open crew \/ damage \/ pollution lines. Do not log a projectile, a tanker type, a submergence, or an IRGC attribution that the PDF does not print.<\/p>\n

For charterers and P&I, Thursday is a Hormuz delay-and-reporting file with an open SAR and pollution watch, not a war-risk conversion that the PDF has already completed and not a Cape Dao rewrite. Off-hire, deviation and general-average conversations will now ask whether the ship was 9 nautical miles north of Khasab after 0300 UTC 29 October, whether it reported, and whether it was following Update 108 and 016-26. They will not be answered by Wednesday night\u2019s 184-26 Aden Advisory, by Tuesday\u2019s 121-count, or by Monday\u2019s 183-26 Al-Faw fire. Seatrade and Maritime Executive colour of a mostly-submerged tanker is industry analysis of a security-company line. It is not a 185-26 naming and not a dedicated wreck notice. Do not collapse that colour onto this morning\u2019s Warning.<\/p>\n

Keep the dedicated files on their own lines. 184-26 remains Wednesday night\u2019s Gulf of Aden Advisory. 183-26 remains the 26 October Al-Faw fire. 182-26 remains the 23 October outbound-Hormuz disablement. 181-26 \/ Leonora Kosan remains the Limah LPG file. 179-26 \/ Al Dasma remains the Bukha fire. Cape Dao remains 403\/26 \/ the 23 September IMO row. Update 108 remains the last periodic threat note, Hormuz still SEVERE. 016-26 remains Wednesday afternoon\u2019s blockade document pack. Thursday morning\u2019s 759\/26 and 766\/26 remain the Kaliakra and Shabla Black Sea files. Do not recast 29 October late morning as an Attack upgrade, as a named hull, as Update 109, as an IMO 122-count, as a mine confirmation, or as a Hormuz closure.<\/p>\n

What Operators Should Note<\/h2>\n
    \n
  • Log 185-26 as a Suspicious Activity fire sighting, not as an Attack.<\/strong> UKMTO Warning 185-26, incident 29 October 2026, 0300 UTC, source Third Party, location footer Khasab, Oman. Filename 20261029-ukmto_warning-185-26.pdf<\/code>. Strait of Hormuz, 9 nautical miles north of Khasab. Master of a third-party vessel sighted another vessel on fire. Crew status unknown. No damage assessment or environmental impact report. Transit with caution. Report suspicious activity to UKMTO, watchkeepers@ukmto.org \/ +44 (0)2392222060. Authorities are investigating. UKMTO printed neither hull, IMO, flag, tanker type, projectile, mine, attacker, submergence, assisting vessel nor a lat\/long. This is not 184-26, not 183-26, not 182-26, not Cape Dao, and not Update 109.<\/li>\n
  • Hold the type line and the Third Party source.<\/strong> 185-26 is Suspicious Activity, the same family as 183-26, not the Attack family that ran 182-26, 181-26 and 180-26. A passing master reported a fire. That is thinner tape than a verified CSO Attack. Do not brief Thursday as \u201cconfirmed tanker Attack, projectile, crew safe.\u201d Do not brief Thursday as quiet because the stamp is not Attack.<\/li>\n
  • Hold Vanguard \/ Seatrade colour separately.<\/strong> Vanguard Tech colour, as carried by Seatrade and Maritime Executive, adds tanker, unknown projectile, mostly submerged, a Panama-flagged reporting tanker, and a nearby vessel potentially assisting. Anadolu, Iran International and Deutsche Welle reprints add no hull. None of those extras sit on the PDF. Do not promote any of them to a naming, a wreck buoy, or an Attack conversion.<\/li>\n
  • Do not collapse the IRGC three-tanker mine claim or the CENTCOM denial onto this number.<\/strong> 185-26 describes one burning vessel 9 nautical miles north of Khasab. It does not print a mine, a three-hull tally, or a southern-route finding. CENTCOM\u2019s same-day statement that commercial vessels hitting sea mines in the strait is false is not a 185-26 all-clear. Hold both as colour. Stay with the PDF.<\/li>\n
  • Do not merge this watch onto Aden, Al-Faw, Limah, Bukha or Cape Dao.<\/strong> 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. 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. Nine nautical miles north of Khasab is a new offset. Pakistan\u2019s table still ends at 416\/26. IMO still 121 \/ 24 as at 27 October. Update 108 remains last periodic note. 016-26 remains the blockade document pack.<\/li>\n
  • Treat unknown crew, unknown damage and unknown pollution as open lines.<\/strong> The public tape does not say the fire is out. It does not print a NUC, tow, refuge, wreck buoy, least depth or pollution volume. Keep Update 108 Hormuz SEVERE and 016-26 visit-and-search in the master\u2019s pack. Watch a PDF revision that upgrades the type, names a hull, or closes the crew and pollution lines; a NAVAREA; a flag or class note; a JMIC Update 109; or an IMO-board row \u2014 not a headline that Thursday morning closed the strait or completed a salvage.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Warning 185-26 against Update 108\u2019s earlier 251300 UTC cut-off and against the dedicated 182-26 outbound Attack so operators can treat Thursday\u2019s tape as a numbered unnamed fire 9 nautical miles north of Khasab, not as an Attack upgrade, a mine confirmation, or a completed class survey.<\/p>\n","protected":false},"excerpt":{"rendered":"

    The United Kingdom Maritime Trade Operations centre published Warning 185-26 as a numbered PDF on its product board, filename 20261029-ukmto_warning-185-26.pdf. The face of the product is titled 185-26 \u2014 SUSPICIOUS ACTIVITY. The incident date is 29 October 2026. The incident time is 0300 UTC. The source line is Third Party. UKMTO states that it has […]<\/p>\n","protected":false},"author":1,"featured_media":1135,"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-1137","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\/1137","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=1137"}],"version-history":[{"count":0,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1137\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/1135"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=1137"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=1137"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=1137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}