{"id":1231,"date":"2026-11-05T11:37:03","date_gmt":"2026-11-05T11:37:03","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-196-26-records-a-tanker-projectile-hit-50-nm-north-of-madinat-ash-shamal\/"},"modified":"2026-11-05T11:37:03","modified_gmt":"2026-11-05T11:37:03","slug":"ukmto-196-26-records-a-tanker-projectile-hit-50-nm-north-of-madinat-ash-shamal","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-196-26-records-a-tanker-projectile-hit-50-nm-north-of-madinat-ash-shamal\/","title":{"rendered":"UKMTO 196-26 records a tanker projectile hit 50 NM north of Madinat ash Shamal"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre published Warning 196-26 as a numbered PDF on its product board, filename 20261105-ukmto_warning-196-26.pdf<\/code>. The face of the product is titled 196-26 \u2014 ATTACK. The incident date is 4 November 2026. The incident time is 2320 UTC. The source line is Verified. UKMTO states that it has received a report of an incident 50 nautical miles north of Madinat ash Shamal, Qatar. A tanker has been struck by two unidentified projectiles. The status of the crew, a damage assessment and the environmental impact are unconfirmed at present. Vessels are advised to transit with caution and report any suspicious activity to UKMTO while authorities continue to investigate. The location footer printed on the product is Madinat ash Shamal, Qatar. 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. Thursday morning\u2019s product is a Verified Attack on a 2320 UTC 4 November tanker clock in the central Arabian Gulf, not a rewrite of Tuesday night\u2019s dedicated Warning 195-26, not a rewrite of Monday morning\u2019s dedicated Warning 192-26, and not a conversion of IMO\u2019s 7 October ACERS row onto a later 50-nautical-mile Qatar offset. It names a tanker, two unidentified projectiles, a 50-nautical-mile north-of-Madinat-ash-Shamal offset, and an unconfirmed crew \/ damage \/ environmental line. 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 50-nautical-mile offset, or a keep-clear radius. Monitor the Situation first tracked the public product at 08:20 UTC on 5 November. Masters who brief Thursday morning as 195-26\u2019s Lima engine-room tanker now recast as a Qatar hull, as LARGO ATOM leaving Khafji, as ACERS filed again, or as Selat Storm leaving Um Al Ghanam will have merged four other series into a Verified Attack that still withholds the struck hull.<\/p>\n

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

The confirmed tape is the body of 196-26. UKMTO has received a report of an incident 50 nautical miles north of Madinat ash Shamal, Qatar. A tanker has been struck by two unidentified projectiles. The status of the crew, damage assessment and environmental impact are unconfirmed at present. Vessels are advised to transit with caution and report any suspicious activity to UKMTO while authorities continue to investigate. That is the product. Stay with that wording. Do not invent a hull. Do not invent a flag. Do not invent a products, crude, LPG or LNG grade beyond the word 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. 196-26 does not print one. Do not invent a keep-clear radius around Madinat ash Shamal, Ras Laffan, Al Ruwais, Bushehr, Bahrain or Ras Al Khafji. The PDF does not print one. Do not invent a fire-extinguished line, a lost-propulsion line, a sunk line, or a continuing-to-next-port line. Those sentences sit on other products. They do not sit on 196-26. The crew line on this PDF is \u201cunconfirmed at present,\u201d not \u201cno casualties,\u201d not \u201cvessel and crew safe,\u201d and not \u201call crew are accounted for.\u201d Hold that wording. The damage line is two unidentified projectiles. Hold that too.<\/p>\n

The product type is the first briefing fact. 196-26 is Attack, the same family that ran dedicated 191-26 through 195-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 unidentified projectiles struck a tanker 50 nautical miles north of Madinat ash Shamal. 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 Thursday 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 50-nautical-mile Qatar offset that is the whole of this PDF. A DPA who briefs Thursday morning as a completed salvage because the PDF prints no named casualty has under-read a numbered Attack that still withholds hull, crew status, damage volume and onward status.<\/p>\n

Verified source, two projectiles and an unconfirmed crew line is the second briefing fact. The report sits on a Verified source, not on a Master, not on a Company Security Officer, and not on a third-party Channel 16 relay. That is a different reporting path from Tuesday night\u2019s dedicated 195-26, whose source line was Company Security Officer, and from Monday morning\u2019s dedicated 192-26, whose source line was Master. Two unidentified projectiles is the same count as 195-26 and 192-26 and a different aiming point from both: 195-26 printed \u201cinto the engine room\u201d; 192-26 printed \u201con the port side.\u201d 196-26 prints neither engine room nor port side. Do not treat \u201cVerified\u201d as a hull naming. Do not treat \u201cunidentified projectiles\u201d as a confirmed UAV, a confirmed mine, or a confirmed small-boat pairing. Do not treat \u201cunconfirmed at present\u201d as a confirmed all-clear, a confirmed fatality, a confirmed fire, or a confirmed class survey. 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 2320 UTC.<\/p>\n

The geography is the third briefing fact. 196-26 prints 50 nautical miles north of Madinat ash Shamal, Qatar. The location footer is Madinat ash Shamal, Qatar. That is the central Arabian Gulf, on the Qatari north coast\u2019s seaward face, not the Strait of Hormuz traffic-separation scheme, not Tuesday night\u2019s 14-nautical-mile northeast-of-Lima offset, and not Monday morning\u2019s 72-nautical-mile east-of-Khafji offset. IMO\u2019s highlighted-incidents board, as at 3 November, already prints ACERS (IMO 9301902), 7 October, 51 nautical miles north of Madinat ash Shamal, Qatar, Damaged, no pollution \u2014 a dedicated earlier row, not this PDF. One nautical mile and 28 days separate ACERS\u2019s 51-nautical-mile offset from 196-26\u2019s 50-nautical-mile offset, on different dates, with different confirmation states. A passage plan that only carried 195-26\u2019s Lima engine-room tanker, or that treated Thursday as closed because 195-26 was the last UKMTO number at 03:30 UTC, has not budgeted a 2320 UTC projectile hit 50 nautical miles north of Madinat ash Shamal.<\/p>\n

The numbering is the fourth briefing fact. 196-26 is numbered after 195-26 on the product board. The incident clock is later than Tuesday night\u2019s pair. 2320 UTC on 4 November sits about 28 hours after 195-26\u2019s 1900 UTC Lima tanker clock and about 32 hours after 194-26\u2019s 1105 UTC dhow clock. Monitor the Situation first tracked the public 196-26 product at 08:20 UTC on 5 November. Do not brief Thursday morning as \u201c196 after 195 on the same hull.\u201d Brief Thursday morning as a later-issued Attack on a later Qatar tanker clock. UKMTO now ends at 196-26. There is no 197-26 this run.<\/p>\n

Industry colour of the same clock, held separately: Monitor the Situation first tracked the public product at 08:20 UTC on 5 November and restated the two-projectile line and the 50-nautical-mile north-of-Madinat-ash-Shamal offset. Arab Times restated the same UKMTO sentences from Doha on 5 November. CGTN restated the public wording later on 5 November. JNS and Siasat restated the unidentified-projectile line, the unconfirmed crew and damage line, and the caution advice. Those reprints are not a naming. Treat them as industry colour of the public PDF. Do not collapse them onto 196-26 as a completed identification, a TSS plot, a fire line, a Qatari-port finding, or a conversion onto 195-26, 192-26, LARGO ATOM, ACERS or Selat Storm. No numbered MSCIO wrap against the 2320 UTC Qatar clock was retrieved this run.<\/p>\n

What this is not<\/h2>\n

This is not Warning 195-26, and it is not Tuesday night\u2019s unnamed Lima engine-room tanker. Tuesday night\u2019s dedicated Warning 195-26 remains an Attack, incident 3 November 2026, 1900 UTC, source Company Security Officer, filename 20261103-ukmto_warning_195_26.pdf<\/code>: Tanker struck by two unknown projectiles into the engine room, 14 nautical miles northeast of Lima, Oman; no casualties or environmental impact reported as this time; location footer Lima, Oman. 196-26 is 4 November, 2320 UTC, source Verified, tanker, two unidentified projectiles, 50 nautical miles north of Madinat ash Shamal, Qatar, crew and damage unconfirmed. Twenty-eight hours, a sea change and a confirmation-state change separate the two clocks. A CSO Attack that prints an engine-room aiming point and no casualties is not a Verified Attack that prints a Qatar offset and an unconfirmed crew line. Do not convert Thursday\u2019s tanker onto Tuesday\u2019s Lima tanker. Do not convert Tuesday\u2019s engine-room strike onto Thursday\u2019s unnamed Qatar casualty.<\/p>\n

This is not Warning 192-26, and it is not IMO\u2019s LARGO ATOM row. Monday morning\u2019s dedicated Warning 192-26 remains an Attack, incident 1 November 2026, 2347 UTC, source Master, filename 20261102-ukmto_warning-192-26.pdf<\/code>: a 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; location footer RAS AL KHAFJI, SAUDI ARABIA. IMO\u2019s highlighted-incidents board, as at 3 November, prints LARGO ATOM (IMO 1034747), 1 November, 72 NM east of Ras Al Khafji, Damaged, no pollution \u2014 wrap on dedicated 192-26, first official IMO print of that hull, unused as a second Khafji piece. 196-26 is 4 November, 2320 UTC, 50 nautical miles north of Madinat ash Shamal, unidentified projectiles, unconfirmed crew. Two unidentified projectiles do not make the two tankers one hull. Official MSCIO Alert 165\/26 remains wrap on dedicated 192-26.<\/p>\n

This is not IMO\u2019s ACERS row, and it is not a 7 October rewrite. IMO, as at 3 November, still prints ACERS (IMO 9301902), 7 October, 51 nautical miles north of Madinat ash Shamal, Qatar, Damaged, no pollution. That row remains an earlier dedicated print. 196-26 is 4 November, 2320 UTC, 50 nautical miles north of the same town, tanker, two unidentified projectiles, crew unconfirmed. One nautical mile and 28 days do not collapse a later Verified Attack onto a 7 October IMO sheet. Do not brief Thursday morning as \u201cACERS hit again.\u201d Do not promote IMO 9301902 onto a UKMTO PDF that withholds the hull.<\/p>\n

This is not Warning 194-26, not 193-26, and not a Selat Storm naming. Tuesday night\u2019s dedicated Warning 194-26 remains an Attack, incident 2 November 2026, 1105 UTC, source Verified: Indian Government report of an attack on an Indian crewed Dhow whilst sailing outbound through the Strait of Hormuz; Omani Royal Navy rescued the surviving crew; UKMTO unaware of the status of the vessel; location footer Lima, Oman. Last week\u2019s dedicated Warning 193-26 remains a Master Attack, 2020 UTC 1 November, vessel struck by an unknown projectile causing a hole on the starboard side, 9 nautical miles northeast of Lima, vessel and crew safe. Dedicated NAVAREA IX 425\/26 remains tug boat Selat Storm sunk in 26-22.55N 056-20.47E, 0.6 nautical miles west of Jazirat Um Al Ghanam. 196-26 prints tanker, Qatar, 50 nautical miles north of Madinat ash Shamal, unconfirmed crew. It does not print dhow, Lima, starboard hole, tug, Selat Storm, or Um Al Ghanam. Do not collapse those files onto this number because they share a two-projectile or Attack family.<\/p>\n

This is not Update 110, not Update 111, not a 129th IMO row, and not NAVAREA IX 429\/26. Sunday afternoon\u2019s dedicated Update 110, ICOD 011300 UTC 1 November, remains the last numbered public periodic note. There is no Update 111 this run. IMO\u2019s highlighted-incidents board still prints 128 confirmed incidents and 24 confirmed seafarer fatalities as at 3 November, with top rows LARGO ATOM, SELAT STORM and ARZANAH. IMO has not named 196-26, 195-26, 194-26, 193-26, 191-26, Al Jusufi, Quba or AZINI. The fatality line is still 24. NAVAREA IX still ends at 428\/26. No 197-26, no 429\/26, no 0170\/26 and no IMO 129 this run. Official MSCIO alerts index showed no numbered wrap against the 2320 UTC Qatar clock. Official English on hs-navy.mod.bg has now taken this morning\u2019s dedicated NAVWARN 797\/26 MENTOR \u2014 wrap on that Black Sea file, not a 196-26 hull.<\/p>\n

Operational implications<\/h2>\n

For a master already shaping a central Arabian Gulf, Ras Laffan, Ras Al Khafji, Bahrain, Bushehr, Doha or north-Qatar coastal transit, or holding at Fujairah, Khor Fakkan, Sohar or the Hormuz approaches this morning, Thursday is a same-week Attack on a 2320 UTC Verified tanker clock, on top of Tuesday night\u2019s dedicated 195-26 Lima engine-room tanker, on top of Tuesday night\u2019s dedicated 194-26 dhow, on top of last week\u2019s dedicated 193-26 hole, and on top of Monday morning\u2019s dedicated 192-26 Khafji tanker. Update 110 remains the last numbered JMIC note and still prints Hormuz SEVERE and Arabian Gulf SUBSTANTIAL. 016-26 remains the working blockade document pack for hulls that still need the Strait. 196-26 adds a tanker that was already struck by two unidentified projectiles 50 nautical miles north of Madinat ash Shamal at 2320 UTC on 4 November, with crew, damage and pollution still unconfirmed at the time of the PDF. A passage plan that only carried 195-26\u2019s 1900 UTC Lima tanker, or that treated Thursday as closed because 195-26 was the last UKMTO number at 03:30 UTC, has not budgeted a 2320 UTC projectile hit on the Qatari north coast\u2019s seaward face.<\/p>\n

Two unidentified projectiles, learned from a Verified source, with crew and damage unconfirmed, is a standoff watchkeeping problem and a missing-status problem before it is a war-risk rewrite. 196-26 is not 187-26\u2019s alongside, slow-speed, above-waterline device problem, and it is not 195-26\u2019s engine-room aiming-point problem. It is a lookout, CPA, AIS-on\/AIS-off, citadel and possible-disablement problem at the same time as it is a missing-crew-line problem. BMP MS projectile and citadel guidance remains the working industry pack; 196-26 does not reprint it and does not order an armed team. It also does not authorise a master to treat every radar contact north of Madinat ash Shamal as a confirmed Attack, or to treat every AIS-on tanker as ACERS, LARGO ATOM or Selat Storm after the fact. Log the Warning number, the 4 November date, the 2320 UTC clock, the Verified source line, the tanker type, the two-unidentified-projectile method, the 50-nautical-mile north-of-Madinat-ash-Shamal offset, and the unconfirmed crew \/ damage \/ environmental line. Do not log a hull, ACERS, LARGO ATOM, Selat Storm, Al Jusufi, a small-boat device, a mine in the water, a Lima offset, a fire, a NUC, a sunk line, or a Qatari-port finding that the PDF does not print.<\/p>\n

The missing hull, crew, fire and onward-status lines are the practical damage watch, not a completed all-clear. The public PDF says the status of the crew, a damage assessment and the environmental impact are unconfirmed at present. It does not say whether the tanker is making way, whether propulsion or steering is available, whether a fire started, whether a tug was offered, or where the ship went after 2320 UTC. Those missing lines are omissions. They are not a completed \u201call well,\u201d and they are not a NUC. \u201cUnconfirmed\u201d is a status sentence. It is not a class survey, and it is not a fatality finding. Next-port authorities will want a written account that 196-26 does not contain. Charterers and war-risk underwriters will now ask whether the ship was 50 nautical miles north of Madinat ash Shamal after 2320 UTC on 4 November, whether it reported, and whether it was following Update 110 and 016-26. They will not be answered by Tuesday night\u2019s 195-26 engine-room strike, by IMO\u2019s ACERS row, by IMO\u2019s LARGO ATOM row, or by a NAVAREA that names a different hull on a different plot.<\/p>\n

For a DPA and an operator with any merchant hull still using Ras Laffan, north-Qatar coastal waters, Bahrain, Ras Al Khafji or the central Gulf, the reporting split is the operational content. Sightings of projectiles, fire, smoke, a disabled tanker, a Mayday on Channel 16 or pollution go to UKMTO on the 196-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; no numbered MSCIO wrap against the 2320 UTC Qatar clock was retrieved this run. Registering with one mailbox is not a substitute for the others. 196-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 type beyond tanker, a lat\/long, a NUC, a tow, a fire, a flooding line, a casualty line or a next-port line; a NAVAREA that plots this tanker rather than Selat Storm, RITI, Quba or ACERS; a flag or class note; a JMIC Update 111; or an IMO-board row \u2014 not a headline that IMO\u2019s 128-count closed Thursday\u2019s Arabian Gulf Attack or completed a salvage.<\/p>\n

Keep the dedicated files on their own lines. 195-26 remains Tuesday night\u2019s dedicated CSO Attack on a tanker 14 nautical miles northeast of Lima, two unknown projectiles into the engine room, no casualties. 194-26 remains Tuesday night\u2019s dedicated Verified Attack on an Indian crewed Dhow outbound through Hormuz, 1105 UTC 2 November, vessel status unknown; Monday afternoon\u2019s dedicated Al Jusufi file remains wrap, not a 194-26 hull. 193-26 remains last week\u2019s dedicated unnamed Lima hole, 2020 UTC 1 November, 9 nautical miles northeast, vessel and crew safe. 192-26 remains Monday morning\u2019s dedicated Arabian Gulf tanker Attack; IMO\u2019s LARGO ATOM row is wrap. 191-26 remains Sunday night\u2019s dedicated Channel 16 Mayday-relay Attack. 425\/26 remains last week\u2019s dedicated named tug wreck; IMO\u2019s SELAT STORM row is wrap. ACERS remains IMO\u2019s 7 October 51-nautical-mile Madinat ash Shamal row, not a 196-26 hull. NAVAREA IX 411\/26 remains a live Qatar subsea-pipeline watch through 26 November with a 2-nautical-mile berth \u2014 wrap on this geography, not a 196-26 naming. Update 110 remains ICOD 011300 UTC, 167 incidents. 016-26 remains the blockade document pack. This morning\u2019s dedicated 797\/26 remains unmanned tanker Mentor east of Cape Kaliakra; official English has now taken that number \u2014 wrap on the Black Sea file, not on this PDF. This morning\u2019s dedicated 790\/26 remains two drifting containers east of Maslen Nos. Do not recast 5 November morning as a named Qatar tanker, as 195-26 recast, as ACERS filed twice, as LARGO ATOM leaving Khafji, as Update 111, or as IMO moving the fatality line.<\/p>\n

What Operators Should Note<\/h2>\n
    \n
  • Log 196-26 as a 4 November Qatar tanker Attack on a Verified clock, not as a 195-26 rewrite and not as an ACERS rewrite.<\/strong> UKMTO Warning 196-26, incident 4 November 2026, 2320 UTC, source Verified. Filename 20261105-ukmto_warning-196-26.pdf<\/code>. Tanker struck by two unidentified projectiles, 50 nautical miles north of Madinat ash Shamal, Qatar. Status of the crew, damage assessment and environmental impact unconfirmed at present. Transit with caution. Report suspicious activity to UKMTO, watchkeepers@ukmto.org \/ +44 (0) 2392 222060. Authorities are investigating. Location footer Madinat ash Shamal, Qatar. UKMTO printed neither hull, IMO, flag, cargo, attacker, fire, lat\/long beyond the 50-nautical-mile offset, anchorage, NUC, tow, next port, nor a keep-clear radius. This is not 195-26, not 192-26 \/ LARGO ATOM, not ACERS, not 425\/26, and not Al Jusufi.<\/li>\n
  • Hold the clock, the water and the unconfirmed line.<\/strong> 196-26 is Attack, not Suspicious Activity. The working date is 4 November. The working time is 2320 UTC. The working source is Verified, not Master, not Company Security Officer, and not Merchant Vessel. The working type is tanker. The working water is 50 nautical miles north of Madinat ash Shamal, Qatar. The working method is two unidentified projectiles. The crew, damage and environmental lines are unconfirmed at present, not \u201cno casualties,\u201d not \u201cvessel and crew safe,\u201d and not \u201call crew accounted for.\u201d The product number is 196. The incident clock sits after 195-26\u2019s 1900 UTC 3 November Lima tanker and after 194-26\u2019s 1105 UTC 2 November dhow. Do not brief Thursday morning as \u201c195-26\u2019s engine-room tanker, now off Qatar.\u201d Do not brief Thursday morning as quiet because the PDF withholds hull and crew.<\/li>\n
  • Hold Monitor the Situation \/ Arab Times \/ CGTN \/ JNS \/ Siasat colour separately.<\/strong> Monitor the Situation first tracked the product at 08:20 UTC on 5 November. Arab Times restated the public sentences from Doha. CGTN, JNS and Siasat restated the unidentified-projectile line and the unconfirmed crew and damage line. None of those products named a hull. Do not promote a wire rewrite to a 196-26 naming, a TSS plot, a fire line, or a conversion onto 195-26, 192-26, LARGO ATOM, ACERS or Selat Storm. No numbered MSCIO wrap against the 2320 UTC clock was retrieved this run.<\/li>\n
  • Do not collapse 195-26, 192-26 \/ LARGO ATOM, ACERS or 425\/26 onto this number.<\/strong> 195-26 remains Tuesday night\u2019s dedicated CSO Attack on a tanker 14 nautical miles northeast of Lima, two unknown projectiles into the engine room, no casualties. 192-26 remains Monday morning\u2019s dedicated Khafji tanker Attack; IMO\u2019s LARGO ATOM row is wrap. ACERS remains IMO\u2019s 7 October 51-nautical-mile Madinat ash Shamal row, Damaged, no pollution \u2014 an earlier dedicated print, not this PDF. 425\/26 remains last week\u2019s dedicated Selat Storm wreck; IMO\u2019s SELAT STORM row is wrap. Two unidentified projectiles 50 nautical miles north of Madinat ash Shamal are not two unknown projectiles into an engine room 14 nautical miles northeast of Lima, and they are not a 7 October IMO sheet. Five products are five products. A Qatar tanker is a sixth overnight file. Do not make them one hull.<\/li>\n
  • Do not merge this watch onto 194-26, Al Jusufi, 193-26, 191-26 or IMO\u2019s 128-count as a completed 196-26 naming.<\/strong> 194-26 remains Tuesday night\u2019s dedicated Verified Attack on an Indian crewed Dhow, 1105 UTC 2 November, vessel status unknown; Monday afternoon\u2019s dedicated Al Jusufi file remains wrap on that number, not on 196-26. 193-26 remains last week\u2019s dedicated unnamed Lima hole, 9 nautical miles northeast, vessel and crew safe. 191-26 remains Sunday night\u2019s dedicated Channel 16 Mayday-relay Attack. IMO still prints 128 confirmed \/ 24 dead as at 3 November, with LARGO ATOM, SELAT STORM and ARZANAH as the named top rows \u2014 wrap, not this morning\u2019s dedicated file. IMO has not named 196-26. Fatality still 24. NAVAREA IX still ends at 428\/26. NAVAREA IX 411\/26 remains a live Qatar pipeline watch through 26 November, unused as a 196-26 naming. 016-26 remains the blockade document pack. Update 110 remains the last numbered public periodic note. No Update 111, no 197-26, no 429\/26, no IMO 129 this run.<\/li>\n
  • Treat the missing hull, crew, fire and propulsion lines as open damage lines.<\/strong> The public tape prints tanker, two unidentified projectiles, 50 nautical miles north of Madinat ash Shamal, and crew \/ damage \/ environmental impact unconfirmed at present. It does not print a hull, a cargo grade, a fire, a survey, a lost-propulsion finding, 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. Sightings go to UKMTO, MSCIO, the Qatari authorities and the CSO. Watch a PDF revision that names a hull or prints a lat\/long; a NAVAREA that plots this tanker rather than ACERS or Selat Storm; a flag or class note; a JMIC Update 111; or an IMO-board row \u2014 not a headline that IMO\u2019s 128-count closed Thursday\u2019s Arabian Gulf Attack or completed a salvage.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Warning 196-26 against Tuesday night\u2019s dedicated 195-26 and against Monday morning\u2019s dedicated 192-26 so operators can treat Thursday morning\u2019s tape as a numbered Verified Attack on a tanker 50 nautical miles north of Madinat ash Shamal, not as a Lima engine-room rewrite, an ACERS reprint, or a completed class survey.<\/p>\n","protected":false},"excerpt":{"rendered":"

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