{"id":1251,"date":"2026-11-06T23:33:48","date_gmt":"2026-11-06T23:33:48","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-197-26-records-a-tanker-waterline-explosion-16-nm-east-of-khasab\/"},"modified":"2026-11-06T23:34:48","modified_gmt":"2026-11-06T23:34:48","slug":"ukmto-197-26-records-a-tanker-waterline-explosion-16-nm-east-of-khasab","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-197-26-records-a-tanker-waterline-explosion-16-nm-east-of-khasab\/","title":{"rendered":"UKMTO 197-26 records a tanker waterline explosion 16 NM east of Khasab"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre published Warning 197-26 as a numbered PDF on its product board, filename 20261106-ukmto_warning-197-26.pdf<\/code>. The face of the product is titled 197-26 \u2014 ATTACK. The incident date is 5 November 2026. The incident time is 2200 UTC. The source line is Master. UKMTO states that it has received a time-late report of an incident 16 nautical miles east of Khasab, Oman. The Master of a tanker transiting the Strait of Hormuz outbound has reported an explosion at the waterline, port side. The crew are safe and are accounted for. The tanker is still under its own power and is continuing on its voyage. 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 Khasab, Oman. 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. Friday night\u2019s product is a Master Attack on a 2200 UTC 5 November tanker clock, posted time-late on 6 November, 16 nautical miles east of Khasab on an outbound Hormuz transit. It is not a rewrite of Thursday morning\u2019s dedicated Warning 196-26, not a rewrite of Tuesday night\u2019s dedicated Warning 195-26, and not a conversion of IMO\u2019s Louise 1 row onto a later east-of-Khasab offset. It names a tanker, an explosion at the waterline on the port side, a 16-nautical-mile east-of-Khasab offset, a crew-safe line, and a continuing-under-own-power line. It does not name a merchant hull, an IMO number, a flag, a cargo grade, an attacker, a projectile, a fire, a NUC or tow line, a latitude\/longitude beyond the 16-nautical-mile offset, or a keep-clear radius. UKMTO posted the numbered PDF on the 6 November product board against a 2200 UTC 5 November clock. Masters who brief Friday night as 196-26\u2019s unnamed Qatar tanker now recast as a Khasab hull, as Louise 1 leaving Musandam, as 195-26\u2019s Lima engine-room tanker, or as Selat Storm leaving Um Al Ghanam will have merged four other series into a Master Attack that still withholds the struck hull.<\/p>\n

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

The confirmed tape is the body of 197-26. UKMTO has received a time-late report of an incident 16 nautical miles east of Khasab, Oman. The Master of a tanker transiting the Strait of Hormuz outbound has reported an explosion at the waterline, port side. The crew are safe and are accounted for. The tanker is still under its own power and is continuing on its voyage. 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 products, crude, LPG or LNG grade beyond the word tanker. Do not invent a UAV, a mine, a small-boat device, a boarding or a projectile. 197-26 prints explosion, not projectile. Do not invent a lat\/long on the UKMTO PDF. 197-26 does not print one. Do not invent a keep-clear radius around Khasab, Lima, Musandam, Fujairah or the TSS. The PDF does not print one. Do not invent a fire-extinguished line, a lost-propulsion line, a sunk line, or a next-port name. The product already prints own power and continuing on its voyage. It does not print a destination. The crew line on this PDF is \u201csafe and are accounted for,\u201d not \u201cunconfirmed at present,\u201d not \u201cone seafarer missing,\u201d and not \u201cone seafarer fatality.\u201d Hold that wording. The damage line is an explosion at the waterline, port side. Hold that too.<\/p>\n

The product type is the first briefing fact. 197-26 is Attack, the same family that ran dedicated 191-26 through 196-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 a tanker outbound through the Strait of Hormuz reported an explosion at the waterline on the port side, 16 nautical miles east of Khasab. 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 two unidentified projectiles. It does not say the ship is at anchor, NUC, under tow, or sunk. A DPA who briefs Friday night as \u201canother Hormuz two-projectile hit, crew unconfirmed\u201d has borrowed 196-26\u2019s method and Thursday morning\u2019s unconfirmed crew line and has dropped the time-late stamp, the 16-nautical-mile east-of-Khasab offset, the port-side waterline explosion, and the continuing-under-own-power sentence that are the whole of this PDF. A DPA who briefs Friday night as a completed salvage because the tanker is making way has under-read a numbered Attack that still withholds hull, damage volume and attacker.<\/p>\n

Time-late Master source, a waterline explosion and a crew-safe line is the second briefing fact. The report sits on a Master source, not on Verified, not on a Company Security Officer, and not on a third-party Channel 16 relay. That is a different reporting path from Thursday morning\u2019s dedicated 196-26, whose source line was Verified, and from Tuesday night\u2019s dedicated 195-26, whose source line was Company Security Officer. Time-late is printed on the face of the product. The incident clock is 2200 UTC on 5 November. The numbered PDF appeared on the 6 November board. Do not treat the 6 November filename as a 6 November strike. Do not treat \u201ctime-late\u201d as a completed investigation. Do not treat \u201cexplosion\u201d as a confirmed UAV, a confirmed mine, a confirmed small-boat pairing, or a confirmed two-projectile strike. Do not treat \u201ccrew are safe and are accounted for\u201d as a class survey, and do not convert it into Thursday morning\u2019s unconfirmed crew line. The public PDF says the tanker is still under its own power and is continuing on its voyage. It does not say whether a fire started, whether a hole was found, whether a tug was offered, or where the ship went after 2200 UTC beyond \u201ccontinuing on its voyage.\u201d<\/p>\n

The geography is the third briefing fact. 197-26 prints 16 nautical miles east of Khasab, Oman. The location footer is Khasab, Oman. The transit line is Strait of Hormuz outbound. That is the Musandam \/ eastern-Hormuz exit into the Gulf of Oman, not Thursday morning\u2019s 50-nautical-mile north-of-Madinat-ash-Shamal offset, 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 6 November, already prints LOUISE 1 (IMO 9290323), 29 October, 25 nautical miles northeast of Khasab, Oman, Damaged, no pollution \u2014 a dedicated earlier row, not this PDF. Nine nautical miles of offset wording and eight days separate Louise 1\u2019s 25-nautical-mile northeast-of-Khasab print from 197-26\u2019s 16-nautical-mile east-of-Khasab print, on different dates, with different confirmation states. A passage plan that only carried 196-26\u2019s Qatar tanker, or that treated Friday as closed because 196-26 was the last UKMTO number at 11:30 UTC, has not budgeted a 2200 UTC waterline explosion 16 nautical miles east of Khasab on an outbound Hormuz transit.<\/p>\n

The numbering is the fourth briefing fact. 197-26 is numbered after 196-26 on the product board. The incident clock is later than Thursday morning\u2019s Qatar tanker. 2200 UTC on 5 November sits about 23 hours after 196-26\u2019s 2320 UTC 4 November Madinat ash Shamal clock and about 27 hours after 195-26\u2019s 1900 UTC Lima tanker clock. Do not brief Friday night as \u201c197 after 196 on the same hull.\u201d Brief Friday night as a later-issued Attack on a later Khasab tanker clock, posted time-late. UKMTO now ends at 197-26. There is no 198-26 this run.<\/p>\n

Industry colour of the same clock, held separately: Arab News restated the public sentences from a Reuters copy on 6 November at 15:24, repeating the port-side waterline explosion, the 16-nautical-mile east-of-Khasab offset, the crew-safe line and the continuing-under-own-power line. Clearwater Dynamics issued CW Alert 008-(Nov 26) against the same UKMTO tape. Those reprints are not a naming. Treat them as industry colour of the public PDF. Do not collapse them onto 197-26 as a completed identification, a TSS plot, a fire line, an Omani-port finding, a \u201cMilitary\u201d attacker, or a conversion onto 196-26, 195-26, Louise 1, Velos Sapphire or Selat Storm. No numbered MSCIO wrap against the 2200 UTC Khasab clock was retrieved this run.<\/p>\n

What this is not<\/h2>\n

This is not Warning 196-26, and it is not Thursday morning\u2019s unnamed Qatar tanker. Thursday morning\u2019s dedicated Warning 196-26 remains an Attack, 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; location footer Madinat ash Shamal, Qatar. This afternoon\u2019s dedicated IMO 129-count, as at 6 November, converted Velos Sapphire\u2019s missing line to one seafarer fatality on that Qatar sheet \u2014 wrap on dedicated 196-26, unused as a 197-26 naming. 197-26 is 5 November, 2200 UTC, source Master, time-late, tanker, explosion at the waterline port side, 16 nautical miles east of Khasab, Oman, crew safe and accounted for, under own power and continuing. Twenty-three hours, a sea change and a confirmation-state change separate the two clocks. A Verified Attack that prints two unidentified projectiles and an unconfirmed crew line is not a Master Attack that prints a waterline explosion, a crew-safe line and a continuing voyage. Do not convert Friday\u2019s tanker onto Thursday\u2019s Qatar tanker. Do not convert Thursday\u2019s two unidentified projectiles onto Friday\u2019s unnamed Khasab casualty. Do not promote Velos Sapphire, IMO 9321201, or the 25th fatality onto a PDF that withholds the hull.<\/p>\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. 197-26 is 5 November, 2200 UTC, source Master, time-late, explosion at the waterline port side, 16 nautical miles east of Khasab, crew safe, under own power. Two days, a sea change and an aiming-point change separate the two clocks. An engine-room strike 14 nautical miles northeast of Lima is not a waterline explosion 16 nautical miles east of Khasab. Do not convert Friday\u2019s tanker onto Tuesday\u2019s Lima tanker.<\/p>\n

This is not IMO\u2019s Louise 1 row, and it is not a 29 October rewrite. IMO, as at 6 November, still prints LOUISE 1 (IMO 9290323), 29 October, 25 nautical miles northeast of Khasab, Oman, Damaged, no pollution. That row remains an earlier dedicated print. 197-26 is 5 November, 2200 UTC, 16 nautical miles east of Khasab, tanker, explosion at the waterline port side, crew safe. Nine nautical miles of offset wording and eight days do not collapse a later Master Attack onto a 29 October IMO sheet. Do not brief Friday night as \u201cLouise 1 hit again.\u201d Do not promote IMO 9290323 onto a UKMTO PDF that withholds the hull.<\/p>\n

This is not Warning 194-26, not 193-26, not 191-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. Sunday night\u2019s dedicated Warning 191-26 remains a Channel 16 Mayday-relay Attack in the Strait of Hormuz. 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. 197-26 prints tanker, Khasab, 16 nautical miles east, outbound, explosion at the waterline port side, crew safe, under own power. It does not print dhow, Lima, starboard hole, Mayday, tug, Selat Storm, or Um Al Ghanam. Do not collapse those files onto this number because they share an outbound, Hormuz or Attack family.<\/p>\n

This is not Update 111, not a 130th IMO row, and not NAVAREA IX 432\/26. Last night\u2019s dedicated Update 111, ICOD 051300 UTC 5 November, remains the last numbered public periodic note. Its confirmed-incidents table closed at 191-26 through 196-26. 197-26\u2019s 2200 UTC 5 November clock sits about nine hours after that cut-off. IMO\u2019s highlighted-incidents board still prints 129 confirmed incidents and 25 confirmed seafarer fatalities as at 6 November, with VELOS SAPPHIRE as the named top row. IMO has not named 197-26, 195-26, 194-26, 193-26, 191-26, Al Jusufi, Quba or AZINI. The fatality line is still 25, on Velos Sapphire, not on this PDF. NAVAREA IX now ends at 432\/26 on a Southern Gulf drifting-container product \u2014 a companion dedicated file this run, not a 197-26 wreck plot. No 198-26, no Update 112, no IMO 130, no 433\/26 and no 0170\/26 this run. Official MSCIO alerts index showed no numbered wrap against the 2200 UTC Khasab clock.<\/p>\n

Operational implications<\/h2>\n

For a master already shaping a Hormuz outbound, Musandam, Khasab, Lima, Fujairah, Khor Fakkan, Sohar or Gulf of Oman coastal transit, or holding in the Southern Gulf this evening, Friday night is a same-week Attack on a 2200 UTC Master tanker clock, posted time-late, on top of Thursday morning\u2019s dedicated 196-26 Qatar tanker, on top of Tuesday night\u2019s dedicated 195-26 Lima engine-room tanker, on top of Tuesday night\u2019s dedicated 194-26 dhow, and on top of last week\u2019s dedicated 193-26 hole. Update 111 remains the last numbered JMIC note and still prints Hormuz SEVERE and Arabian Gulf SUBSTANTIAL, with an ICOD that closed before this clock. 016-26 remains the working blockade document pack for hulls that still need the Strait. 197-26 adds a tanker that had already reported an explosion at the waterline, port side, 16 nautical miles east of Khasab at 2200 UTC on 5 November, with crew safe and the ship still making way when the time-late PDF was posted. A passage plan that only carried 196-26\u2019s 2320 UTC Qatar tanker, or that treated Friday as closed because 196-26 was the last UKMTO number at 11:30 UTC, has not budgeted a 2200 UTC waterline explosion on the Musandam \/ eastern-Hormuz exit.<\/p>\n

A waterline explosion, learned time-late from the Master, with crew accounted for and the ship still under own power, is a standoff watchkeeping problem and a delayed-reporting problem before it is a war-risk rewrite. 197-26 is not 187-26\u2019s alongside, slow-speed, above-waterline device problem, and it is not 196-26\u2019s two-unidentified-projectile, unconfirmed-crew problem. It is a lookout, CPA, AIS-on\/AIS-off, citadel and flooding-watch problem at the same time as it is a late-report problem. BMP MS projectile and citadel guidance remains the working industry pack; 197-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 Khasab as a confirmed Attack, or to treat every AIS-on tanker as Louise 1, Velos Sapphire or Selat Storm after the fact. Log the Warning number, the 5 November date, the 2200 UTC clock, the time-late stamp, the Master source line, the tanker type, the outbound Hormuz transit, the waterline \/ port-side explosion method, the 16-nautical-mile east-of-Khasab offset, the crew-safe line, and the continuing-under-own-power line. Do not log a hull, Louise 1, Velos Sapphire, Selat Storm, Al Jusufi, a projectile count, a small-boat device, a mine in the water, a Lima offset, a fire, a NUC, a sunk line, or an Omani-port finding that the PDF does not print.<\/p>\n

The missing hull, fire and damage-volume lines are the practical damage watch, not a completed all-clear. The public PDF says the crew are safe and accounted for and the tanker is still under its own power. Those are status sentences. They are not a class survey, and they are not a finding that the hull is undamaged. Next-port authorities will want a written account that 197-26 does not contain. Charterers and war-risk underwriters will now ask whether the ship was 16 nautical miles east of Khasab after 2200 UTC on 5 November, whether it reported on time or time-late, and whether it was following Update 111 and 016-26. They will not be answered by Thursday morning\u2019s 196-26 Qatar strike, by IMO\u2019s Louise 1 row, by IMO\u2019s Velos Sapphire 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 Hormuz, Musandam, Khasab, Fujairah, Khor Fakkan or the Gulf of Oman, the reporting split is the operational content. Sightings of explosions, fire, smoke, a disabled tanker, a Mayday on Channel 16 or pollution go to UKMTO on the 197-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 2200 UTC Khasab clock was retrieved this run. Registering with one mailbox is not a substitute for the others. 197-26 does not order a daylight-only transit, a deviation around a published circle, or a halt to visit-and-search compliance. Keep Update 111 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 Louise 1; a flag or class note; a JMIC Update 112; or an IMO-board row \u2014 not a headline that IMO\u2019s 129-count closed Friday\u2019s Hormuz Attack or completed a salvage.<\/p>\n

Keep the dedicated files on their own lines. 196-26 remains Thursday morning\u2019s dedicated Verified Attack on a tanker 50 nautical miles north of Madinat ash Shamal, two unidentified projectiles, crew unconfirmed; this afternoon\u2019s dedicated IMO 129-count remains the Velos Sapphire fatality conversion on that Qatar sheet, wrap, not a 197-26 hull. 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. Louise 1 remains IMO\u2019s 29 October 25-nautical-mile northeast-of-Khasab row, not a 197-26 hull. Update 111 remains ICOD 051300 UTC, 172 incidents, six counted since the last report through 196-26. 016-26 remains the blockade document pack. This morning\u2019s dedicated 431\/26 remains the Fujairah SKATE 3D harbour survey through 132359 UTC 13 November. This morning\u2019s dedicated 167\/26 remains the 9 November 20 km training circle at 44-02.80 N. Do not recast 6 November night as a named Khasab tanker, as 196-26 recast, as Louise 1 filed twice, as Velos Sapphire leaving Qatar, as Update 112, or as IMO moving the fatality line off Velos Sapphire.<\/p>\n

What Operators Should Note<\/h2>\n
    \n
  • Log 197-26 as a 5 November Khasab tanker Attack on a time-late Master clock, not as a 196-26 rewrite and not as a Louise 1 rewrite.<\/strong> UKMTO Warning 197-26, incident 5 November 2026, 2200 UTC, source Master, time-late. Filename 20261106-ukmto_warning-197-26.pdf<\/code>. Tanker transiting the Strait of Hormuz outbound. Explosion at the waterline, port side, 16 nautical miles east of Khasab, Oman. Crew safe and accounted for. Tanker still under its own power and continuing on its voyage. Transit with caution. Report suspicious activity to UKMTO, watchkeepers@ukmto.org \/ +44 (0) 2392 222060. Authorities are investigating. Location footer Khasab, Oman. UKMTO printed neither hull, IMO, flag, cargo, attacker, projectile, fire, lat\/long beyond the 16-nautical-mile offset, anchorage, NUC, tow, next port, nor a keep-clear radius. This is not 196-26 \/ Velos Sapphire, not 195-26, not Louise 1, not 425\/26, and not Al Jusufi.<\/li>\n
  • Hold the clock, the water and the time-late stamp.<\/strong> 197-26 is Attack, not Suspicious Activity. The working date is 5 November. The working time is 2200 UTC. The working source is Master, not Verified and not Company Security Officer. The working type is tanker. The working transit is Strait of Hormuz outbound. The working water is 16 nautical miles east of Khasab, Oman. The working method is an explosion at the waterline, port side \u2014 not two unidentified projectiles. The crew line is safe and accounted for, not \u201cunconfirmed at present.\u201d The ship is under own power and continuing. The product number is 197. The incident clock sits after 196-26\u2019s 2320 UTC 4 November Qatar tanker and after 195-26\u2019s 1900 UTC 3 November Lima tanker. Do not brief Friday night as \u201c196-26\u2019s Qatar tanker, now off Khasab.\u201d Do not treat the 6 November filename as a 6 November strike.<\/li>\n
  • Hold Arab News \/ Clearwater colour separately.<\/strong> Arab News restated the public sentences from a Reuters copy at 15:24 on 6 November. Clearwater Dynamics issued CW Alert 008-(Nov 26) against the same UKMTO tape. Neither product named a hull. Do not promote a wire rewrite to a 197-26 naming, a TSS plot, a fire line, a \u201cMilitary\u201d attacker, or a conversion onto 196-26, 195-26, Louise 1, Velos Sapphire or Selat Storm. No numbered MSCIO wrap against the 2200 UTC clock was retrieved this run.<\/li>\n
  • Do not collapse 196-26 \/ Velos Sapphire, 195-26, Louise 1 or 425\/26 onto this number.<\/strong> 196-26 remains Thursday morning\u2019s dedicated Verified Attack on a tanker 50 nautical miles north of Madinat ash Shamal, two unidentified projectiles, crew unconfirmed; this afternoon\u2019s dedicated IMO 129-count remains the Velos Sapphire fatality conversion on that Qatar sheet. 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. Louise 1 remains IMO\u2019s 29 October 25-nautical-mile northeast-of-Khasab 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. A waterline explosion 16 nautical miles east of Khasab is not two unidentified projectiles 50 nautical miles north of Madinat ash Shamal, and it is not a 29 October IMO sheet. Five products are five products. A Khasab 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 129-count as a completed 197-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 197-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 129 confirmed \/ 25 dead as at 6 November, with VELOS SAPPHIRE as the named top row \u2014 wrap on dedicated 196-26, not this evening\u2019s dedicated file. IMO has not named 197-26. Fatality still 25, on Velos Sapphire. Update 111 remains ICOD 051300 UTC; this 2200 UTC clock sits after that cut-off. 016-26 remains the blockade document pack. No Update 112, no 198-26, no IMO 130 this run.<\/li>\n
  • Treat the missing hull, fire and damage-volume lines as open damage lines.<\/strong> The public tape prints tanker, outbound Hormuz, explosion at the waterline port side, 16 nautical miles east of Khasab, crew safe, under own power and continuing. 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 111 Hormuz SEVERE \/ Arabian Gulf SUBSTANTIAL and 016-26 visit-and-search in the master\u2019s pack. Sightings go to UKMTO, MSCIO, the Omani 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 Louise 1 or Selat Storm; a flag or class note; a JMIC Update 112; or an IMO-board row \u2014 not a headline that IMO\u2019s 129-count closed Friday\u2019s Hormuz Attack or completed a salvage.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Warning 197-26 against Thursday morning\u2019s dedicated 196-26 and against Tuesday night\u2019s dedicated 195-26 so operators can treat Friday night\u2019s tape as a numbered time-late Master Attack on a tanker 16 nautical miles east of Khasab, not as a Qatar projectile rewrite, a Louise 1 reprint, or a completed class survey.<\/p>\n","protected":false},"excerpt":{"rendered":"

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