{"id":1179,"date":"2026-11-02T03:35:41","date_gmt":"2026-11-02T03:35:41","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-192-26-records-a-tanker-projectile-hit-72-nm-east-of-ras-al-khafji\/"},"modified":"2026-11-02T03:36:41","modified_gmt":"2026-11-02T03:36:41","slug":"ukmto-192-26-records-a-tanker-projectile-hit-72-nm-east-of-ras-al-khafji","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-192-26-records-a-tanker-projectile-hit-72-nm-east-of-ras-al-khafji\/","title":{"rendered":"UKMTO 192-26 records a tanker projectile hit 72 NM east of Ras Al Khafji"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre published Warning 192-26 as a numbered PDF on its product board, filename 20261102-ukmto_warning-192-26.pdf<\/code>. The face of the product is titled 192-26 \u2014 ATTACK. The incident date is 1 November 2026. The incident time is 2347 UTC. The source line is Master. UKMTO states that it has received a report of an incident 72 nautical miles east of Ras Al Khafji, Saudi Arabia. A tanker travelling southeast through the Arabian Gulf has been struck by two unknown projectiles on the port side. All crew are accounted for 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 printed on the product is RAS AL KHAFJI, SAUDI ARABIA. Emergency contacts printed on the product remain watchkeepers@ukmto.org, +44 (0)2392 222060, +44 (0)7779 966976 and +44 (0)7585 795608.<\/p>\n

That is the working primary. Monday morning\u2019s product is a same-night Arabian Gulf Attack on a Master clock, not a rewrite of Sunday night\u2019s dedicated Warning 191-26, not a late naming of Friday night\u2019s dedicated 188-26, and not a conversion of unused 186-26, dedicated 187-26 or dedicated 189-26 onto a northern-Gulf hull. It names a tanker type and a two-projectile port-side method. It does not name a merchant hull, an IMO number, a flag, a cargo grade, an attacker, a fire, a NUC or tow line, a latitude\/longitude beyond the 72-nautical-mile east-of-Khafji offset, or a keep-clear radius. Sunday night\u2019s dedicated Warning 191-26 piece on this desk, retrieved as 20261101-ukmto_warning_191_26.pdf<\/code>, still told operators that a Merchant Vessel had relayed a Channel 16 Mayday of another vessel struck by an unknown projectile inside the Strait of Hormuz at 1509 UTC. 192-26 is not that Mayday. The 2347 UTC Master report sits about eight and a half hours later and about a gulf away. Masters who brief Monday morning as 191-26 filed again, as Al Mayeda hit a second time, as RITI leaving Ra\u2019s Tahir, as unused 186-26 finally reprinted, or as a named northern-Gulf casualty will have merged five other series into a Master Attack that withholds the struck hull.<\/p>\n

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

The confirmed tape is the body of 192-26. UKMTO has received a report of an incident 72 nautical miles east of Ras Al Khafji, Saudi Arabia. A tanker travelling southeast through the Arabian Gulf has been struck by two unknown projectiles on the port side. All crew are accounted for 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 VLCC, products, LPG or LNG type beyond the word tanker. The PDF prints tanker, not crude oil tanker and not LNG carrier. Do not invent a UAV, a mine, a small-boat device or a boarding. Do not invent a lat\/long on the UKMTO PDF. 192-26 does not print one. Do not invent a keep-clear radius around Khafji, Al Jubail, Ras Tanura, Al-Faw or Lavan. The PDF does not print one. Do not invent a fire-extinguished line, a lost-propulsion line, or a continuing-to-next-port line. Those sentences sit on Update 110\u2019s named rows. They do not sit on 192-26. The crew line on this PDF is \u201call crew are accounted for,\u201d not \u201ccrew reported safe.\u201d Hold that wording.<\/p>\n

The product type is the first briefing fact. 192-26 is Attack, the same family that ran dedicated 179-26 through 182-26, unused 186-26, dedicated 187-26, dedicated 188-26, dedicated 189-26 and Sunday night\u2019s dedicated 191-26, not the Suspicious Activity family that ran 183-26, 185-26 and 190-26, and not the Advisory family that ran 184-26. UKMTO says two unknown projectiles struck a tanker on the port side inside the Arabian Gulf. 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 Monday morning as \u201canother Hormuz attached-device hit, crew safe\u201d has borrowed 187-26\u2019s method and Update 110\u2019s Louise 1 all-clear and has dropped the 72-nautical-mile Khafji offset that is the whole of this PDF. A DPA who briefs Monday morning as a completed salvage because the PDF prints accounted-for crew and no environmental impact has under-read a numbered Attack that still withholds hull, fire, damage volume and onward status.<\/p>\n

Master, two projectiles and port side is the second briefing fact. The report sits on the Master, not on a Verified source, not on a CSO, and not on a third-party Channel 16 relay. That is a different reporting path from Sunday night\u2019s dedicated 191-26, whose source line was Merchant Vessel relaying someone else\u2019s Mayday. Two unknown projectiles is also a different count from 191-26\u2019s single unknown projectile and from 188-26\u2019s single unknown projectile on the port side. Do not treat \u201cMaster\u201d as a hull naming. Do not treat \u201ctwo unknown projectiles\u201d as a confirmed UAV salvo, a confirmed mine pair, or a confirmed small-boat pairing. Do not treat \u201cport side\u201d as a confirmed hole size, a confirmed tank group, or a confirmed engine-room fire. The public PDF does not say whether the tanker is still making way, whether propulsion is available, whether a tug was offered, or where the ship went after 2347 UTC.<\/p>\n

The geography is the third briefing fact. 192-26 prints 72 nautical miles east of Ras Al Khafji, Saudi Arabia, and a tanker travelling southeast through the Arabian Gulf. The location footer is RAS AL KHAFJI, SAUDI ARABIA. That is northern Arabian Gulf water, on the Saudi\u2013Kuwait coast, not the Strait of Hormuz traffic-separation scheme and not Friday night\u2019s 40-nautical-mile south-of-Lavan offset. Sunday night\u2019s dedicated 191-26 remains a Strait of Hormuz Attack with a Channel 16 Mayday-relay clock. Sunday afternoon\u2019s dedicated Update 110 remains a 011300 UTC periodic note whose newest Arabian Gulf Attack sits on 188-26 \/ Al Mayeda. 192-26 at 2347 UTC sits after that cut-off. Update 110 still prints the Arabian Gulf SUBSTANTIAL and the Strait of Hormuz SEVERE, and still counts six attacks inside the Gulf since 7 October. Monday morning\u2019s tape is a seventh Gulf Attack after that cut-off, not a seventh row on that table. A passage plan that only carried Sunday afternoon\u2019s named table, or that treated Sunday night as empty because 191-26 was a Hormuz Mayday, has not budgeted a 2347 UTC tanker hit 72 nautical miles east of Khafji.<\/p>\n

Industry colour of the same clock, held separately: Middle East Eye restated the UKMTO two-projectile sentence, the 72-nautical-mile east-of-Khafji offset and the accounted-for crew line at 02:41 GMT on 2 November. Iran International restated the same PDF as a tanker struck near a Saudi port, citing the vessel\u2019s master, at 01:47 GMT. Newsquawk restated the same facts at 02:09 UTC. Monitor the Situation first tracked the public product at 01:46 UTC. CGTN recirculated the accounted-for crew and no-environmental-impact sentences. Those reprints are not a naming. Treat them as industry colour of the public PDF. Do not collapse them onto 192-26 as a completed identification, a TSS plot, a fire line, or a conversion onto Al Mayeda, RITI, Louise 1, Arzanah or Sunday night\u2019s unnamed Hormuz casualty.<\/p>\n

What this is not<\/h2>\n

This is not Warning 191-26, and it is not a Strait of Hormuz Mayday. Sunday night\u2019s dedicated Warning 191-26 remains an Attack, incident 1 November 2026, 1509 UTC, source Merchant Vessel, filename 20261101-ukmto_warning_191_26.pdf<\/code>: Master of a merchant vessel relayed a VHF Channel 16 Mayday stating that another vessel had been struck by an unknown projectile; location footer Strait of Hormuz; no hull, no type beyond another vessel, no crew line, no environmental line. 192-26 is 2347 UTC, source Master, tanker, two unknown projectiles, port side, 72 nautical miles east of Ras Al Khafji. Eight and a half hours and a gulf separate the two clocks. A Channel 16 relay of \u201canother vessel\u201d inside the Strait is not a Master report of a tanker 72 nautical miles east of Khafji. Do not convert Sunday night\u2019s Mayday onto Monday morning\u2019s tanker. Do not convert Monday morning\u2019s tanker onto Sunday night\u2019s unnamed Hormuz casualty.<\/p>\n

This is not Update 110, and it is not a seventh row on that note. Sunday afternoon\u2019s dedicated Update 110, ICOD 011300 UTC 1 November, JMIC# 001 26, remains the last numbered public periodic note, with Hormuz SEVERE, the Arabian Gulf SUBSTANTIAL, 167 incidents since 1 March, and six files since Update 109. Its confirmed-incidents table ends at 186-26 \/ RITI, 187-26 \/ Louise 1, 188-26 \/ Al Mayeda, 189-26 \/ Arzanah, MSCIO 160\/26 and 161\/26 \/ 190-26 \/ AZINI. Its Arabian Gulf outlook still counts six attacks inside the Gulf since 7 October, including 188-26 south of Lavan Island. 191-26 at 1509 UTC and 192-26 at 2347 UTC both sit after that cut-off. Neither is a completed Update 111. Do not back-fit a 2347 UTC Khafji Attack onto a 1300 UTC table. Do not treat Update 110\u2019s Al Mayeda row as the Monday casualty.<\/p>\n

This is not a rewrite of 188-26, and it is not this afternoon\u2019s leftover Nakilat Al Mayeda file. Friday night\u2019s 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. Sunday afternoon\u2019s dedicated Nakilat \/ Qatar Stock Exchange disclosure remains the company statement that Al Mayeda was hit by unidentified objects in the Arabian Gulf on Friday evening, crew uninjured, no environmental impact, vessel safe and operational. Update 110 now prints AL MAYEDA against 188-26 as an LNG carrier, identified by India\u2019s Minister of Ports, Shipping and Waterways. Forty nautical miles south of Lavan is central-to-southern Arabian Gulf water. Seventy-two nautical miles east of Ras Al Khafji is northern Arabian Gulf water. A Friday 1800 UTC Master report of fire is not a Sunday 2347 UTC Master report that withholds fire. Do not merge Friday\u2019s Lavan Attack onto Monday\u2019s Khafji Attack because both print unknown projectile and port side.<\/p>\n

This is not a rewrite of 183-26, and it is not an Al-Faw fire file. Thursday\u2019s dedicated Warning 183-26 remains Suspicious Activity, not Attack: a vessel fire about 63 nautical miles southeast of Al-Faw, name withheld, crew unknown. Al-Faw sits at the Iraqi head of the Gulf. Khafji sits on the Saudi\u2013Kuwait coast. Sixty-three nautical miles southeast of Al-Faw is not 72 nautical miles east of Ras Al Khafji. A Thursday fire sighting is not a Sunday 2347 UTC two-projectile Attack. IMO\u2019s 16 October Loyalty row, 78 nautical miles northeast of Al Jubail, and the ST3 row, 68 nautical miles from Al Jubail, remain earlier named northern-Gulf casualties on Saturday\u2019s dedicated 122-count. They are not this tanker. Do not convert Loyalty, ST3 or 183-26 onto 192-26 as a UKMTO naming.<\/p>\n

This is not a rewrite of unused 186-26, dedicated 187-26 or dedicated 189-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 29 October whilst completing an outbound Hormuz transit, location footer Khasab, Oman; Update 110 now prints RITI against that file and against dedicated 420\/26. Friday morning\u2019s dedicated Warning 187-26 remains an unnamed outbound tanker Attack, 2212 UTC 29 October, 25 nautical miles northeast of Khasab, two attached devices, engine-room fire; Update 110 now prints LOUISE 1 against that file. Saturday morning\u2019s dedicated Warning 189-26 remains a time-late unnamed crude-oil-tanker Attack, 28 October, outbound Hormuz; Update 110 now prints ARZANAH against that file. Those four products are Hormuz or Musandam water. 192-26 is Khafji water. Do not convert RITI, Louise 1 or Arzanah onto 192-26 as a UKMTO naming.<\/p>\n

This is not 190-26, and it is not Sunday morning\u2019s dedicated AZINI hijack. Saturday night\u2019s dedicated Warning 190-26 remains a Suspicious Activity boarding of a large fishing vessel at 1419 UTC 30 October. Sunday morning\u2019s dedicated MSCIO Alert 161\/26 remains the Iranian fishing vessel AZINI, hijacked 29 October off northeastern Somalia. Update 110 now prints AZINI against 161\/26 and 190-26 as wrap. 192-26 prints an Arabian Gulf Attack and two unknown projectiles on a tanker. A Somali-Basin fishing-vessel hijack is not a Khafji tanker hit. Do not merge the mothership watch onto this Attack because both sat on a late-October board.<\/p>\n

This is not an International Maritime Organization 123-count, and it is not Advisory 184-26. Saturday afternoon\u2019s dedicated IMO highlighted-incidents board remains 122 confirmed \/ 24 seafarer fatalities as at 30 October. Wednesday afternoon\u2019s dedicated JMIC Advisory Note 016-26 remains the blockade visit-and-search document pack. 184-26 \/ 416\/26 remains the Gulf of Aden PAG keep-clear through 032359 UTC 3 November. NAVAREA IX 424\/26, the 011500 UTC 1 November Pakistan live-weapon-firing box for 0300\u20130600 UTC on 3 and 4 November, remains unused as a dedicated file this run. Thursday\u2019s dedicated Contship Jet and Khoryv Black Sea files, Saturday\u2019s dedicated NAVWARN 775\/26, 776\/26 and 777\/26, and Sunday morning\u2019s dedicated ARN 162\/2026 remain Kaliakra, Shabla, Burgas, Galata and Romanian products. They do not belong on a Khafji Attack.<\/p>\n

Operational implications<\/h2>\n

For a master already shaping a northern Arabian Gulf transit, or holding at Ras Tanura, Ju\u2019aymah, Al Jubail, Mina Al Ahmadi, Shuaiba, or the Khafji approaches tonight, Monday morning is a same-night Attack on a Master clock, on top of Sunday night\u2019s Hormuz Mayday and on top of Sunday afternoon\u2019s Update 110 named table. Update 110 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. 192-26 adds a tanker that was already hit 72 nautical miles east of Khafji, travelling southeast, about eight and a half hours after Sunday\u2019s Hormuz Mayday. A passage plan that only carried Update 110\u2019s 011300 UTC cut-off, or that treated the northern Gulf as quiet because 191-26 was a Hormuz file, has not budgeted a 2347 UTC two-projectile hit on the Saudi\u2013Kuwait coast.<\/p>\n

Two unknown projectiles on the port side of a tanker, learned from that tanker\u2019s Master, is a standoff watchkeeping problem before it is a war-risk rewrite. 192-26 is not 187-26\u2019s 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-fire-line problem. BMP MS projectile and citadel guidance remains the working industry pack; 192-26 does not reprint it and does not order an armed team. It also does not authorise a master to treat every radar contact east of Khafji as a confirmed Attack, or to treat every AIS-on tanker as Al Mayeda, Loyalty or ST3 after the fact. Log the Warning number, the 1 November date, the 2347 UTC clock, the Master source line, the tanker type, the two-unknown-projectile method, the port-side hit, the southeast heading, the 72-nautical-mile east-of-Khafji offset, the accounted-for crew line, and the no-environmental-impact line. Do not log Al Mayeda, RITI, Louise 1, Arzanah, Ghana Prosperity, a small-boat device, a mine in the water, a Lavan offset, a fire, a NUC, or an IRGC attribution that the PDF does not print.<\/p>\n

The missing hull, fire, damage and onward-status lines are the practical damage watch, not a completed all-clear. The public PDF says the crew are accounted for and that there is no reported environmental impact at this time. It does not say whether the tanker is making way, whether propulsion or steering is available, whether a tug was offered, whether the hull is holed, whether a fire started and was put out, or where the ship went after 2347 UTC. Those missing lines are omissions. They are not a completed \u201call well,\u201d and they are not a NUC. \u201cAccounted for\u201d is a head-count sentence. It is not a class survey. Next-port authorities will want a written account that 192-26 does not contain. Charterers and war-risk underwriters will now ask whether the ship was in the northern Arabian Gulf after 2347 UTC on 1 November, whether it was travelling southeast, whether it reported, and whether it was following Update 110 and 016-26. They will not be answered by Sunday afternoon\u2019s named Al Mayeda row, by Sunday night\u2019s Hormuz Mayday, by Saturday\u2019s 122-count, or by Sunday morning\u2019s AZINI hijack.<\/p>\n

For a DPA and an operator with crude, products, LPG, LNG or any tanker still using the northern Gulf, the reporting split is the operational content. Sightings of projectiles, fire, smoke, a disabled hull, a Mayday on Channel 16 or pollution go to UKMTO on the 192-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. This desk has not retrieved a numbered MSCIO alert against the 2347 UTC Khafji clock. Registering with one mailbox is not a substitute for the others. 192-26 does not order a daylight-only transit, a deviation around a published circle, or a halt to visit-and-search compliance. Keep Update 110 Hormuz SEVERE \/ Arabian Gulf SUBSTANTIAL and 016-26 visit-and-search in the master\u2019s pack. Watch a PDF revision that names a hull, prints a cargo grade, a lat\/long, a NUC, a tow, a fire or a next-port line; a NAVAREA that plots this tanker rather than RITI or Quba; a flag or class note; a JMIC Update 111; or an IMO-board row \u2014 not a headline that Sunday afternoon\u2019s named table closed Sunday night\u2019s Gulf Attack.<\/p>\n

Keep the dedicated files on their own lines. 191-26 remains Sunday night\u2019s dedicated Channel 16 Mayday-relay Attack inside the Strait of Hormuz. Update 110 remains Sunday afternoon\u2019s numbered regional note, ICOD 011300 UTC, 167 incidents, Hormuz still SEVERE, Arabian Gulf still SUBSTANTIAL, six Gulf attacks since 7 October on that cut-off. 189-26 remains Saturday morning\u2019s unnamed time-late Hormuz Attack; Arzanah on Update 110 is wrap, not a 192-26 hull. 188-26 remains Friday night\u2019s unnamed vessel Attack 40 nautical miles south of Lavan Island; Al Mayeda on Sunday\u2019s Nakilat statement and on Update 110 is wrap, not a Khafji tanker. 187-26 remains Friday morning\u2019s unnamed outbound-tanker Attack 25 nautical miles northeast of Khasab; Louise 1 on Update 110 is wrap. 186-26 remains the unused 1600 UTC unknown-projectile Attack; RITI on 420\/26 and on Update 110 is wrap. 183-26 remains the 63-nautical-mile Al-Faw fire. 190-26 remains Saturday night\u2019s unnamed fishing-vessel boarding; AZINI on 161\/26 and on Update 110 is wrap. 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. 182-26 remains the 23 October outbound disablement, Ghana Prosperity on Update 109 and the IMO 122-count as wrap. 016-26 remains Wednesday afternoon\u2019s blockade document pack. NAVAREA IX 424\/26 remains the unused 3\u20134 November Pakistan firing box. Do not recast 2 November morning as a named Khafji casualty, as Al Mayeda hit again, as 191-26 filed twice, as Update 111, as an IMO 123-count, or as a northern-Gulf closure.<\/p>\n

What Operators Should Note<\/h2>\n
    \n
  • Log 192-26 as a Sunday-night Arabian Gulf tanker Attack, not as a 191-26 rewrite and not as an Al Mayeda second hit.<\/strong> UKMTO Warning 192-26, incident 1 November 2026, 2347 UTC, source Master. Filename 20261102-ukmto_warning-192-26.pdf<\/code>. Tanker travelling southeast through the Arabian Gulf struck by two unknown projectiles on the port side, 72 nautical miles east of Ras Al Khafji, Saudi Arabia. All crew accounted for. No reported environmental impact at this time. Transit with caution. Report suspicious activity to UKMTO, watchkeepers@ukmto.org \/ +44 (0)2392 222060. Authorities are investigating. UKMTO printed neither hull, IMO, flag, cargo, attacker, fire, lat\/long beyond the 72-nautical-mile offset, anchorage, NUC, tow, next port, nor a keep-clear radius. This is not 191-26, not Update 110, not 188-26, not 183-26, and not 420\/26.<\/li>\n
  • Hold the clock and the water.<\/strong> 192-26 is Attack, not Suspicious Activity. The working date is 1 November. The working time is 2347 UTC. The working source is Master, not Merchant Vessel, not Verified, and not CSO. The working water is the Arabian Gulf, 72 nautical miles east of Ras Al Khafji. The working method is two unknown projectiles on the port side. The working heading is southeast. The crew line is accounted for, not \u201ccrew reported safe.\u201d Do not brief Monday morning as \u201c191-26\u2019s Hormuz Mayday, filed late.\u201d Do not brief Monday morning as quiet because the PDF withholds hull and fire.<\/li>\n
  • Hold Middle East Eye \/ Iran International \/ Newsquawk \/ Monitor the Situation colour separately.<\/strong> All four restated the public PDF. None of those reprints named a hull, a flag or a cargo grade. Do not promote a wire rewrite to a 192-26 naming, a TSS plot, a fire line, or a conversion onto Al Mayeda, Loyalty or ST3.<\/li>\n
  • Do not collapse Update 110\u2019s named rows, or Sunday night\u2019s Mayday, onto this number.<\/strong> Update 110 remains Sunday afternoon\u2019s dedicated note, ICOD 011300 UTC, 167 incidents, six Gulf attacks since 7 October on that cut-off. 191-26 remains Sunday night\u2019s dedicated Strait of Hormuz Mayday-relay Attack. 188-26 \/ Al Mayeda remains the dedicated 1800 UTC LNG-carrier Attack 40 nautical miles south of Lavan Island. 189-26 \/ Arzanah remains the dedicated time-late 28 October VLCC Attack. 187-26 \/ Louise 1 remains the dedicated 2212 UTC attached-device Attack. 186-26 \/ RITI remains the unused 1600 UTC 29 October CSO Attack, with 420\/26 as the Ra\u2019s Tahir fire-and-anchor. Five earlier products are five products. A Khafji tanker is a sixth overnight file. Do not make them one hull.<\/li>\n
  • Do not merge this watch onto Al-Faw, AZINI, Aden, Ghana Prosperity or Quba.<\/strong> 183-26 remains the 63-nautical-mile Al-Faw fire. Loyalty \/ ST3 remain earlier named northern-Gulf rows on Saturday\u2019s dedicated IMO 122-count; they are not this tanker. 190-26 \/ 161\/26 remains the dedicated fishing-vessel hijack, AZINI, east-southeast of Socotra. 184-26 \/ 416\/26 remains the Gulf of Aden PAG keep-clear through 3 November. 182-26 remains the outbound disablement, Ghana Prosperity on Update 109 as wrap only. 185-26 remains the 0300 UTC 9-nautical-mile north-of-Khasab fire. 417\/26 remains the dedicated MSV Quba sunk file. IMO still 122 \/ 24 as at 30 October. 016-26 remains the blockade document pack. 424\/26 remains the unused 3\u20134 November Pakistan firing box.<\/li>\n
  • Treat the missing hull, fire and onward-status lines as open damage lines.<\/strong> The public tape prints tanker, two projectiles, port side, southeast, 72 nautical miles east of Khafji, crew accounted for, and no environmental impact at this time. It does not print a hull, a cargo grade, a fire, a survey, a hole size, a NUC interval, a tug, a next-port name or a class note. Keep Update 110 Hormuz SEVERE \/ Arabian Gulf SUBSTANTIAL 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 tanker; a flag or class note; a JMIC Update 111; or an IMO-board row \u2014 not a headline that Sunday afternoon\u2019s named table closed Sunday night\u2019s Gulf Attack or completed a salvage.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Warning 192-26 against Sunday night\u2019s dedicated 191-26 and against Sunday afternoon\u2019s dedicated Update 110 so operators can treat Monday morning\u2019s tape as a numbered Master Attack on a tanker 72 nautical miles east of Ras Al Khafji, not as a Hormuz Mayday rewrite, an Al Mayeda second hit, or a completed class survey.<\/p>\n","protected":false},"excerpt":{"rendered":"

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