{"id":1110,"date":"2026-10-27T03:33:57","date_gmt":"2026-10-27T03:33:57","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-183-26-records-a-vessel-fire-63-nm-southeast-of-al-faw\/"},"modified":"2026-10-27T03:33:57","modified_gmt":"2026-10-27T03:33:57","slug":"ukmto-183-26-records-a-vessel-fire-63-nm-southeast-of-al-faw","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-183-26-records-a-vessel-fire-63-nm-southeast-of-al-faw\/","title":{"rendered":"UKMTO 183-26 records a vessel fire 63 NM southeast of Al-Faw"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations published Warning 183-26 as a SUSPICIOUS ACTIVITY product. The working primary is the numbered PDF dated 26 October 2026, 20261026-uktmo_warning-183-26.pdf<\/code>. The incident date is 26 October 2026. The incident time is printed as TBC. The source line is Third Party. UKMTO says it has received multiple third-party reports of a vessel on fire, 63 nautical miles southeast of Al-Faw, Iraq. Crew status, damage assessment and environmental impact are unknown at the time of the report. 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 vessel type, a cargo grade, a heading, a projectile, a fire origin, an attacker, nor a coordinate pair beyond the Al-Faw offset.<\/p>\n

This is a northern-Gulf fire file typed as Suspicious Activity. It is not Warning 180-26, the dedicated Attack 30 nautical miles southeast of Al Faw on 20 October at 1830 UTC, later named Soyia on Thursday\u2019s dedicated IMO 120-count. It is not Warning 182-26, Monday\u2019s dedicated outbound Hormuz Attack with a disablement line. It is not Warning 181-26, Friday\u2019s dedicated unnamed tanker Attack 7 nautical miles northeast of Limah. It is not Warning 179-26, the dedicated Bukha fire. JMIC Update 108, ICOD 251300 UTC on 25 October, cuts off before Monday\u2019s fire clock and does not list 183-26. The IMO highlighted-incidents board, as at 22 October, remains 120 confirmed incidents and 24 confirmed seafarer fatalities. Do not brief Tuesday\u2019s product as an Attack upgrade, as a Soyia rewrite, as Update 109, as an IMO-board move past 120, or as a Hormuz closure.<\/p>\n

What UKMTO actually printed<\/h2>\n

The confirmed tape is short. SUSPICIOUS ACTIVITY. 183-26. 26 October 2026. Time TBC. Source: Third Party. Multiple third-party reports. Vessel on fire. 63 nautical miles southeast of Al-Faw, Iraq. Crew status unknown. Damage assessment unknown. Environmental impact unknown. Transit with caution. Report suspicious activity to UKMTO. Authorities investigating. That is the product. Stay with the PDF\u2019s 26 October incident date, the TBC time, and the Third Party source line. Do not invent a hull because Anadolu Agency reprinted the same numbered warning on Monday without a name. That wire does not print a cargo. It does not print a projectile. It does not print an attacker. gCaptain\u2019s 26 October read is industry colour that correctly restates the type line: UKMTO classified the report as suspicious activity rather than a confirmed attack, and the cause of the fire remains unclear. Seatrade\u2019s same-day piece carried Orbital Risk Intelligence colour of a vessel attacked off Basra on 26 October and on fire, plus a NASA-satellite heat signature at 0926 hours. That is industry colour. UKMTO did not print \u201cattacked,\u201d did not print a tanker type, and did not print 0926. Do not collapse Orbital Risk or the satellite heat onto 183-26 as a naming, a type line, or an Attack conversion.<\/p>\n

The product type is the first briefing fact. 183-26 is Suspicious Activity, 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 178-26 and 163-26. UKMTO says it has received multiple third-party reports of a 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, or proceeding. A DPA who briefs Tuesday as \u201cconfirmed tanker Attack, projectile, crew safe, no pollution\u201d has borrowed Monday\u2019s 182-26 disablement language and Thursday\u2019s Soyia damage line and has filled every gap the PDF left open. A DPA who briefs Tuesday as nothing because the type is not Attack has under-read a numbered warning that already puts a fire 63 nautical miles off Al-Faw on the recent-incidents board.<\/p>\n

Third-party and time TBC 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 published the next day. 183-26 is a same-day Third Party product with no incident time. The centre has a fire report and has not yet printed a master, a CSO, or a verified 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 northern Arabian Gulf. Do not treat \u201cTBC\u201d as evidence that the event was minor. Do not treat \u201cThird Party\u201d as a hull naming.<\/p>\n

Geography and the files this is not<\/h2>\n

183-26 prints 63 nautical miles southeast of Al-Faw, Iraq. It does not print Basra as a substitute offset, though industry colour used that city. It does not print a latitude and longitude. Do not move the dedicated 180-26 \/ Soyia 30-nautical-mile southeast-of-Al-Faw offset onto this number because both files sit off Iraq. Thirty nautical miles and 63 nautical miles are different circles. Do not move New Andros (dedicated 9 September, 28 nautical miles southeast of Al-Faw) onto 183-26. Do not move the Ambrey Basrah STS four-projectile water-impact colour onto 183-26; that colour remains unused as a dedicated file unless UKMTO numbers it or collapses it onto 180-26, and Monday\u2019s PDF does neither. Do not move 182-26 onto this number because both PDFs carry a 26 October product date. 182-26 is a Friday-morning Hormuz Attack. 183-26 is a Monday northern-Gulf fire.<\/p>\n

Sunday\u2019s 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\u2019s information cut-off is 251300 UTC on 25 October. Monday\u2019s 183-26 fire clock sits after that cut-off. The 156-incident tally on Update 108 does not absorb a 26 October Al-Faw fire. The IMO board as at 22 October still does not carry 181-26, 182-26 or 183-26. Those are different counters. Hold them separately. Do not invent Update 109 because a later numbered warning appeared.<\/p>\n

The northern-Gulf context on Update 108 stays wrap, not a conversion. That note already told operators that five attacks inside the Gulf since 7 October show attacks remain a strong possibility throughout the Arabian Gulf, including at anchorages and ship-to-ship areas off Iraq, and it kept the Arabian Gulf at SUBSTANTIAL. 180-26 \/ Soyia was the first reported northern-AG attack off Iraq in the period on dedicated Update 107. 183-26 does not become the sixth Gulf Attack on that arithmetic. It is a Suspicious Activity fire 33 nautical miles farther southeast than the Soyia offset, with crew, damage and pollution still unknown. Brief the geography. Do not upgrade the type.<\/p>\n

Operational implications<\/h2>\n

For a CSO with tonnage still working the northern Arabian Gulf, the Iraq approaches, or STS and anchorage boxes off Al-Faw and Basra, Monday is a fire-and-unknown-status problem, not a Hormuz disablement problem and not a Soyia no-damage Attack. Update 108 remains the last numbered JMIC note. It does not list 183-26. The IMO 120-count as at 22 October does not list 183-26. Plan the next northern-Gulf run on Update 108 plus Warning 180-26 plus Warning 183-26 plus the dedicated 120-count piece, not on a headline that JMIC has already absorbed Monday\u2019s fire or that UKMTO has already typed it as Attack.<\/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 63 nautical miles off Al-Faw 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. The missing lines are omissions. They are not a completed \u201call well.\u201d Watch a PDF revision that upgrades the type, prints a time, names a hull, or closes the crew and pollution lines; a flag or class note; a NAVAREA; a JMIC Update 109; or an IMO-board row before briefing the vessel as a tanker Attack, as Soyia, as proceeding, or as mistaken identity.<\/p>\n

Third-party remains the other watch. A same-day fire that lands as Third Party \/ time TBC leaves the next hull in the same northern-Gulf box without a verified master or CSO line. That is a thinner tape than Monday\u2019s verified 182-26 disablement. Masters still have to answer UKMTO and the DPA while smoke is in sight. Do not treat \u201cwe will file when we have confirmation\u201d as a risk-reducing phrase on this coast, and do not treat a Suspicious Activity stamp as proof that Monday was quiet off Al-Faw.<\/p>\n

Keep the dedicated files on their own lines. 182-26 remains Monday\u2019s dedicated outbound Hormuz Attack with a disablement line. 181-26 remains Friday\u2019s dedicated Limah Attack; Update 108\u2019s LPG \/ Khor Fakkan status remains wrap on Sunday\u2019s dedicated note. 180-26 \/ Soyia remains the dedicated 30-nautical-mile Al Faw Attack. 179-26 \/ Al Dasma remains the dedicated Bukha fire. 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\u2019s 403\/26 and 404\/26 remain the Cape Dao and Ghana Prosperity hydrographic files. Sunday\u2019s ARN 155\/2026 remains the Khoryv wreck-move file. Do not collapse Monday\u2019s 63-nautical-mile Al-Faw fire onto any of them.<\/p>\n

Do not recast 26 October as a 180-26 rewrite, as a Soyia naming, as an Attack upgrade, as a rewrite of 174-26 through 182-26, as Update 108, as Update 109, as an IMO-board move, as a verified mine, or as a Hormuz closure. The confirmed facts are Warning 183-26, Suspicious Activity, 26 October, time TBC, Third Party, vessel on fire, 63 nautical miles southeast of Al-Faw, Iraq, crew status unknown, damage unknown, environmental impact unknown, no hull name, JMIC still Update 108 with an earlier cut-off, IMO board still 120 as at 22 October without this file.<\/p>\n

What Operators Should Note<\/h2>\n
    \n
  • Log a numbered UKMTO Suspicious Activity fire, not an Attack and not a Soyia file.<\/strong> Warning 183-26. 26 October 2026. Time TBC. Source: Third Party. Multiple third-party reports of a vessel on fire, 63 nautical miles southeast of Al-Faw, Iraq. Crew status, damage assessment and environmental impact unknown at the time of the report. UKMTO printed neither hull, IMO, flag, vessel type, cargo, projectile, attacker nor a latitude\/longitude. Anadolu Agency reprinted the same numbered product without a name.<\/li>\n
  • Hold the type line.<\/strong> 183-26 is Suspicious Activity. It is not the Attack family that ran 182-26, 181-26 and 180-26. gCaptain\u2019s restatement that UKMTO did not confirm an attack is colour on that type line, not a finding that nothing happened. Orbital Risk \u201cattacked off Basra\u201d and a NASA heat signature at 0926 hours remain industry colour. Do not write those words onto the PDF.<\/li>\n
  • Do not merge 183-26 onto 180-26 \/ Soyia or onto 182-26.<\/strong> 180-26 remains the dedicated 20 October 1830 UTC Attack, tanker, unknown projectile, 30 nautical miles southeast of Al Faw, crew safe, no reported damage; IMO later named Soyia on Thursday\u2019s 120-count. 182-26 remains Monday\u2019s dedicated outbound Hormuz disablement. 63 nautical miles off Al-Faw is a new circle on a new clock. Thirty nautical miles is not 63.<\/li>\n
  • Treat unknown crew, unknown damage and unknown pollution as open lines, not a completed all-well.<\/strong> The public tape does not say the fire is out. It does not print a NUC, tow, refuge or wreck line. It does not print a cargo or a bunker figure. Watch a PDF revision, a flag or class note, a NAVAREA, or a JMIC Update 109 before briefing the vessel as proceeding, under tow, or mistaken identity.<\/li>\n
  • Keep Update 108 and the 120-count in the master\u2019s pack, and do not stretch them to this product.<\/strong> Update 108\u2019s information cut-off is 251300 UTC on 25 October. Hormuz remains SEVERE and the Arabian Gulf SUBSTANTIAL on that note, including the STS-and-anchorage watch off Iraq. The 156-incident tally absorbs 181-26, not 183-26. The IMO board as at 22 October is 120 confirmed \/ 24 dead and does not print a 26 October Al-Faw row. Transit with caution. Report to UKMTO.<\/li>\n
  • Put the northern Arabian Gulf back on the night orders as a fire-and-unknown-status envelope.<\/strong> A Third Party \/ time TBC product means the next ship in the same box may only have smoke and a numbered warning, not a verified master line. Answer UKMTO and the DPA while the event is happening. Leave 174-26 through 182-26 on their dedicated pieces. Watch the next numbered warning, a type upgrade, or a named-hull primary \u2014 not a Soyia or Hormuz rewrite.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Warning 183-26 against Update 108\u2019s earlier 251300 UTC cut-off and against the dedicated 180-26 \/ Soyia Attack so operators can treat Monday\u2019s tape as a numbered unnamed fire 63 nautical miles southeast of Al-Faw, not as an Attack upgrade or a completed class survey.<\/p>\n","protected":false},"excerpt":{"rendered":"

    The United Kingdom Maritime Trade Operations published Warning 183-26 as a SUSPICIOUS ACTIVITY product. The working primary is the numbered PDF dated 26 October 2026, 20261026-uktmo_warning-183-26.pdf. The incident date is 26 October 2026. The incident time is printed as TBC. The source line is Third Party. UKMTO says it has received multiple third-party reports of […]<\/p>\n","protected":false},"author":1,"featured_media":1108,"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-1110","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\/1110","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=1110"}],"version-history":[{"count":0,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1110\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/1108"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=1110"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=1110"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=1110"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}