{"id":1209,"date":"2026-11-03T23:38:09","date_gmt":"2026-11-03T23:38:09","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-195-26-records-a-tanker-engine-room-hit-14-nm-northeast-of-lima\/"},"modified":"2026-11-03T23:39:09","modified_gmt":"2026-11-03T23:39:09","slug":"ukmto-195-26-records-a-tanker-engine-room-hit-14-nm-northeast-of-lima","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-195-26-records-a-tanker-engine-room-hit-14-nm-northeast-of-lima\/","title":{"rendered":"UKMTO 195-26 records a tanker engine-room hit 14 NM northeast of Lima"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre published Warning 195-26 as a numbered PDF on its product board, filename 20261103-ukmto_warning_195_26.pdf<\/code>. The face of the product is titled 195-26 \u2014 ATTACK. The incident date is 3 November 2026. The incident time is 1900 UTC. The source line is Company Security Officer. UKMTO states that it has received a report of an incident 14 nautical miles northeast of Lima, Oman. The Company Security Officer for a Tanker reports being struck by two unknown projectiles into the engine room. There are no casualties or environmental impact reported as 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 Lima, 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. Tuesday night\u2019s product is a same-day Attack on a 1900 UTC CSO tanker clock, not a rewrite of tonight\u2019s dedicated Warning 194-26, not a rewrite of last night\u2019s dedicated Warning 193-26, and not a conversion of last night\u2019s dedicated NAVAREA IX 425\/26 Selat Storm wreck onto a 14-nautical-mile Lima tanker. It names a Tanker, two unknown projectiles, an engine-room strike, a 14-nautical-mile northeast-of-Lima offset, and a no-casualties \/ no-environmental-impact 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 14-nautical-mile northeast-of-Lima offset, or a keep-clear radius. Monitor the Situation first tracked the public product at 20:43 UTC on 3 November. Masters who brief Tuesday night as 194-26\u2019s dhow now recast as a tanker, as last night\u2019s 9-nautical-mile hole filed again, as LARGO ATOM leaving Khafji, or as Selat Storm leaving Um Al Ghanam will have merged four other series into a CSO Attack that still withholds the struck hull.<\/p>\n

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

The confirmed tape is the body of 195-26. UKMTO has received a report of an incident 14 nautical miles northeast of Lima, Oman. The Company Security Officer for a Tanker reports being struck by two unknown projectiles into the engine room. There are no casualties or environmental impact reported as 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 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. 195-26 does not print one. Do not invent a keep-clear radius around Lima, Limah, Khasab, Bukha or Fujairah. 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 195-26. The crew line on this PDF is \u201cno casualties \u2026 reported as this time,\u201d not \u201cvessel and crew safe\u201d and not \u201call crew are accounted for.\u201d Hold that wording, including the PDF\u2019s \u201cas this time.\u201d The damage line is two unknown projectiles into the engine room. Hold that too.<\/p>\n

The product type is the first briefing fact. 195-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, dedicated 191-26, dedicated 192-26, last night\u2019s dedicated 193-26 and tonight\u2019s dedicated 194-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\u2019s engine room 14 nautical miles northeast of Lima. 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 Tuesday night 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 14-nautical-mile northeast-of-Lima engine-room offset that is the whole of this PDF. A DPA who briefs Tuesday night as a completed salvage because the PDF prints no casualties and no environmental impact has under-read a numbered Attack that still withholds hull, fire, damage volume beyond the engine room, and onward status.<\/p>\n

Company Security Officer, two projectiles and engine room is the second briefing fact. The report sits on the Company Security Officer, not on a Master, not on a Verified source, and not on a third-party Channel 16 relay. That is a different reporting path from last night\u2019s dedicated 193-26, whose source line was Master, and from tonight\u2019s dedicated 194-26, whose source line is Verified. Two unknown projectiles is also a different count from 193-26\u2019s single unknown projectile and a different aiming point from 192-26\u2019s two unknown projectiles on the port side. Do not treat \u201cCompany Security Officer\u201d as a hull naming. Do not treat \u201cunknown projectiles\u201d as a confirmed UAV, a confirmed mine, or a confirmed small-boat pairing. Do not treat \u201cinto the engine room\u201d as a confirmed lost-propulsion line, a confirmed fire, a confirmed flooding rate, 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 1900 UTC.<\/p>\n

The geography is the third briefing fact. 195-26 prints 14 nautical miles northeast of Lima, Oman. The location footer is Lima, Oman. That is Musandam\u2019s Gulf of Oman face, on the eastern approach, not the Strait of Hormuz traffic-separation scheme, not Monday morning\u2019s 72-nautical-mile east-of-Khafji offset, and not 0.6 nautical miles west of Jazirat Um Al Ghanam. Last night\u2019s dedicated 193-26 remains a Master Attack 9 nautical miles northeast of Lima with a hole on the starboard side. Tonight\u2019s dedicated 194-26 remains a Verified Attack on an Indian crewed Dhow outbound through Hormuz with a Lima footer and no nautical-mile offset. 195-26 is neither of those two products. Five nautical miles separate 193-26\u2019s 9-nautical-mile offset from 195-26\u2019s 14-nautical-mile offset, on different dates, with different types and different damage lines. A passage plan that only carried last night\u2019s 9-nautical-mile hole, or that treated Tuesday as closed because 194-26 was the last Indian-dhow number, has not budgeted a 1900 UTC engine-room hit 14 nautical miles northeast of Lima.<\/p>\n

The numbering is the fourth briefing fact. 195-26 is numbered after 194-26 on the product board. The incident clock is the later of the two Tuesday-night files. 1900 UTC on 3 November sits about 32 hours after 194-26\u2019s 1105 UTC dhow clock and about 47 hours after 193-26\u2019s 2020 UTC 1 November hole. Monitor the Situation first tracked the public 195-26 product at 20:43 UTC on 3 November. Do not brief Tuesday night as \u201c195 after 194 on the same hull.\u201d Brief Tuesday night as a later-issued Attack on a later Lima tanker clock. Do not invent a 196-26 because 195 sits after 194 on the board.<\/p>\n

Industry colour of the same clock, held separately: Monitor the Situation first tracked the public product at 20:43 UTC on 3 November, restated the two-projectile engine-room line and the 14-nautical-mile northeast-of-Lima offset, tagged a southern corridor of the Strait of Hormuz, and added a colour line on U.S. Air Force tankers nearby. Iran International restated the CSO report, the engine-room strike, the 14-nautical-mile offset and the no-casualties \/ no-environmental-impact line at 20:53 UTC. Xinhua restated the same UKMTO sentences from London later on 3 November and separately restated 194-26 as Monday\u2019s Indian-government dhow. Those reprints are not a naming. Treat them as industry colour of the public PDF. Do not collapse them onto 195-26 as a completed identification, a TSS plot, a fire line, a USAF-operations finding, or a conversion onto 194-26, 193-26, LARGO ATOM or Selat Storm. Monitor\u2019s southern-corridor tag and USAF colour are not on the PDF. Do not promote them.<\/p>\n

What this is not<\/h2>\n

This is not Warning 194-26, and it is not Monday\u2019s Indian-crewed dhow. Tonight\u2019s dedicated Warning 194-26 remains an Attack, incident 2 November 2026, 1105 UTC, source Verified, filename 20261103-ukmto_warning-194-26.pdf<\/code>: 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. 195-26 is 3 November, 1900 UTC, source Company Security Officer, Tanker, two unknown projectiles into the engine room, 14 nautical miles northeast of Lima, no casualties. Thirty-two hours and a ship type separate the two clocks. A Verified dhow with a Royal Navy rescue and unknown vessel status is not a CSO tanker with an engine-room strike and no casualties. Do not convert tonight\u2019s tanker onto Monday\u2019s dhow. Do not convert Monday\u2019s dhow onto tonight\u2019s unnamed tanker casualty. This afternoon\u2019s dedicated MSV Al Jusufi statements remain wrap on 194-26, not on this PDF. Do not promote Al Jusufi onto 195-26.<\/p>\n

This is not Warning 193-26, and it is not last night\u2019s unnamed Lima hole. Last night\u2019s dedicated Warning 193-26 remains an Attack, incident 1 November 2026, 2020 UTC, source Master, filename 20261102-ukmto_warning_193.pdf<\/code>: vessel struck by an unknown projectile causing a hole on the starboard side, 9 nautical miles northeast of Lima, Oman; vessel and crew safe; no environmental impact reported. 195-26 is 3 November, 1900 UTC, source CSO, Tanker, two unknown projectiles into the engine room, 14 nautical miles northeast of Lima, no casualties. Forty-seven hours, five nautical miles, a type change and a damage-line change separate the two clocks. A Master Attack that prints a starboard hole and vessel and crew safe is not a CSO Attack that prints an engine-room strike and no casualties. Do not collapse 195-26 onto 193-26 because both sit northeast of Lima. Official MSCIO Alert 166\/26 remains wrap on dedicated 193-26. Do not promote MSCIO\u2019s Strait of Hormuz tag onto 195-26.<\/p>\n

This is not Warning 192-26, and it is not IMO\u2019s new 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, now 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. 195-26 is 3 November, 1900 UTC, 14 nautical miles northeast of Lima, engine room, not port side, not Khafji. Two unknown 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 NAVAREA IX 425\/26, and it is not a Selat Storm naming. Last night\u2019s dedicated 425\/26 remains a named hydrographic wreck: tug boat Selat Storm reported involved in a security incident and sunk in 26-22.55N 056-20.47E, approximately 0.6 nautical miles west of Jazirat Um Al Ghanam. IMO, as at 3 November, now prints SELAT STORM (IMO 9266657), 1 November, Strait of Hormuz, Damaged, pollution unknown \u2014 wrap on dedicated 425\/26, not a 195-26 hull. 195-26 prints Tanker, engine room, 14 nautical miles northeast of Lima, no casualties. It does not print tug, Selat Storm, sunk, or Um Al Ghanam. A CSO Attack that withholds the hull and prints no casualties is not a NAVAREA that names a tug and prints sunk. Do not collapse 425\/26 onto 195-26 as a UKMTO naming.<\/p>\n

This is not Warning 191-26, not Leonora Kosan, and not tonight\u2019s 194-26 Al Jusufi wrap. Sunday night\u2019s dedicated 191-26 remains a Strait of Hormuz Mayday-relay Attack at 1509 UTC 1 November. Dedicated 181-26 \/ IMO\u2019s Leonora Kosan row remains 9390953, 23 October, 6 nautical miles northeast of Limah. This afternoon\u2019s dedicated Al Jusufi file remains a named MSV fatality on a 2 November Limah clock; tonight\u2019s 194-26 is the UKMTO wrap that still withholds that hull. 195-26 is a 3 November tanker on a 14-nautical-mile Lima offset. Do not convert those earlier files onto this number because they share Musandam reporting.<\/p>\n

This is not Update 110, not Update 111, not a 129th IMO row, and not NAVAREA IX 427\/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 now prints 128 confirmed incidents and 24 confirmed seafarer fatalities as at 3 November, with new top rows LARGO ATOM, SELAT STORM and ARZANAH (IMO 9928023, 28 October, Strait of Hormuz, Damaged, no pollution). That increment is wrap, not tonight\u2019s dedicated file. IMO has not named 195-26, 194-26, 193-26, 191-26, Al Jusufi, Quba or AZINI. The fatality line is still 24. NAVAREA IX 427\/26 and 428\/26, both 031500 UTC 3 November, remain Red Sea seaplane-landing boxes off Shura Island and Amaala Triple Bay \u2014 wrap, unused as dedicated. 416\/26 self-cancelled at 032359 UTC 3 November. No numbered MSCIO wrap against the 1900 UTC tanker clock was retrieved this run.<\/p>\n

Operational implications<\/h2>\n

For a master already shaping a Gulf of Oman or southern Hormuz transit, or holding at Fujairah, Khor Fakkan, Sohar, Lima, Limah, Khasab or the Musandam TSS tonight, Tuesday night is a same-day Attack on a 1900 UTC CSO tanker clock, on top of tonight\u2019s dedicated 194-26 dhow, on top of last night\u2019s dedicated 193-26 hole, on top of this afternoon\u2019s dedicated named Al Jusufi fatality, and on top of last night\u2019s dedicated Selat Storm wreck. Update 110 remains the last numbered JMIC note and still prints Hormuz SEVERE. 016-26 remains the working blockade document pack for hulls that still need the Strait. 195-26 adds a tanker that was already struck in the engine room 14 nautical miles northeast of Lima at 1900 UTC. A passage plan that only carried 194-26\u2019s 1105 UTC dhow, or that treated Tuesday as closed because 193-26 was the last UKMTO number at 11:30 UTC, has not budgeted a 1900 UTC engine-room hit on Musandam\u2019s Gulf of Oman face.<\/p>\n

Two unknown projectiles into the engine room, learned from that tanker\u2019s Company Security Officer, is a standoff watchkeeping problem and a propulsion-and-power problem before it is a war-risk rewrite. 195-26 is not 187-26\u2019s alongside, slow-speed, above-waterline device problem, and it is not 193-26\u2019s single-projectile starboard-hole problem. It is a lookout, CPA, AIS-on\/AIS-off, citadel, possible-disablement and possible-blackout problem at the same time as it is a missing-fire-line problem. An engine-room strike is not automatically a confirmed lost-propulsion line, but it is the compartment where propulsion, steering hydraulics and electrical generation sit. BMP MS projectile and citadel guidance remains the working industry pack; 195-26 does not reprint it and does not order an armed team. It also does not authorise a master to treat every radar contact northeast of Lima as a confirmed Attack, or to treat every AIS-on tanker as LARGO ATOM, Louise 1 or Selat Storm after the fact. Log the Warning number, the 3 November date, the 1900 UTC clock, the Company Security Officer source line, the Tanker type, the two-unknown-projectile method, the engine-room aiming point, the 14-nautical-mile northeast-of-Lima offset, the no-casualties line, and the no-environmental-impact line. Do not log a hull, LARGO ATOM, Selat Storm, Al Jusufi, a small-boat device, a mine in the water, a Khafji offset, a fire, a NUC, a sunk line, a southern-corridor tag, or a USAF-operations finding that the PDF does not print.<\/p>\n

The missing hull, fire, propulsion and onward-status lines are the practical damage watch, not a completed all-clear. The public PDF says there are no casualties or environmental impact reported as this time. It does not say whether the tanker is making way, whether propulsion or steering is available, whether the engine room is still habitable, whether a fire started and was put out, whether a tug was offered, or where the ship went after 1900 UTC. Those missing lines are omissions. They are not a completed \u201call well,\u201d and they are not a NUC. \u201cNo casualties\u201d is a status sentence. It is not a class survey. Next-port authorities will want a written account that 195-26 does not contain. Charterers and war-risk underwriters will now ask whether the ship was 14 nautical miles northeast of Lima after 1900 UTC on 3 November, whether it reported, and whether it was following Update 110 and 016-26. They will not be answered by last night\u2019s 193-26 hole, by tonight\u2019s 194-26 dhow, by IMO\u2019s new 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 Fujairah, Khor Fakkan, Sohar or the southern Hormuz corridor, 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 195-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 1900 UTC tanker clock was retrieved this run. Registering with one mailbox is not a substitute for the others. 195-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 or a next-port line; a NAVAREA that plots this tanker rather than Selat Storm, RITI or Quba; a flag or class note; a JMIC Update 111; or an IMO-board row \u2014 not a headline that IMO\u2019s 128-count closed Tuesday\u2019s Gulf of Oman Attack or completed a salvage.<\/p>\n

Keep the dedicated files on their own lines. 194-26 remains tonight\u2019s dedicated Verified Attack on an Indian crewed Dhow outbound through Hormuz, 1105 UTC 2 November, vessel status unknown; this afternoon\u2019s dedicated Al Jusufi file remains wrap, not a 194-26 hull. 193-26 remains last night\u2019s dedicated unnamed Lima hole, 2020 UTC 1 November, 9 nautical miles northeast, vessel and crew safe; MSCIO 166\/26 is wrap. 192-26 remains Monday morning\u2019s dedicated Arabian Gulf tanker Attack; IMO\u2019s new LARGO ATOM row is wrap. 191-26 remains Sunday night\u2019s dedicated Channel 16 Mayday-relay Attack. 425\/26 remains last night\u2019s dedicated named tug wreck; IMO\u2019s new SELAT STORM row is wrap. 189-26 remains Saturday morning\u2019s unnamed time-late Hormuz Attack; Arzanah on Update 110 and now on IMO\u2019s 128-count is wrap. 188-26 \/ Al Mayeda, 187-26 \/ Louise 1 and 186-26 \/ RITI remain earlier dedicated or unused files. 417\/26 remains Quba. 420\/26 remains RITI\u2019s fire-and-anchor. Update 110 remains ICOD 011300 UTC, 167 incidents. 016-26 remains the blockade document pack. 424\/26 remains the dedicated 3\u20134 November Pakistan firing box through 040700 UTC 4 November. 427\/26 and 428\/26 remain wrap. Do not recast 3 November night as a named Lima tanker, as 194-26 recast, as 193-26 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 195-26 as a 3 November Lima tanker Attack on a CSO clock, not as a 194-26 rewrite and not as a 193-26 rewrite.<\/strong> UKMTO Warning 195-26, 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. Transit with caution. Report suspicious activity to UKMTO, watchkeepers@ukmto.org \/ +44 (0) 2392 222060. Authorities are investigating. Location footer Lima, Oman. UKMTO printed neither hull, IMO, flag, cargo, attacker, fire, lat\/long beyond the 14-nautical-mile offset, anchorage, NUC, tow, next port, nor a keep-clear radius. This is not 194-26, not 193-26, not 192-26 \/ LARGO ATOM, not 425\/26, and not Al Jusufi.<\/li>\n
  • Hold the clock, the water and the damage line.<\/strong> 195-26 is Attack, not Suspicious Activity. The working date is 3 November. The working time is 1900 UTC. The working source is Company Security Officer, not Master, not Verified, and not Merchant Vessel. The working type is Tanker. The working water is 14 nautical miles northeast of Lima, Oman. The working method is two unknown projectiles. The working damage line is into the engine room. The crew line is no casualties reported as this time, not \u201cvessel and crew safe.\u201d The product number is 195. The incident clock sits after 194-26\u2019s 1105 UTC 2 November dhow and after 193-26\u2019s 2020 UTC 1 November hole. Do not brief Tuesday night as \u201c193-26\u2019s Lima hole, now a tanker.\u201d Do not brief Tuesday night as quiet because the PDF withholds hull and fire.<\/li>\n
  • Hold Monitor the Situation \/ Iran International \/ Xinhua colour separately.<\/strong> Monitor the Situation first tracked the product at 20:43 UTC on 3 November and added a southern-corridor tag and USAF-tanker colour that the PDF does not print. Iran International restated the CSO report at 20:53 UTC. Xinhua restated the UKMTO sentences from London later on 3 November. None of those products named a hull. Do not promote a wire rewrite, a southern-corridor tag, or a USAF-operations finding to a 195-26 naming, a TSS plot, a fire line, or a conversion onto 194-26, 193-26, LARGO ATOM or Selat Storm. No numbered MSCIO wrap against the 1900 UTC clock was retrieved this run.<\/li>\n
  • Do not collapse 194-26, 193-26, 192-26 \/ LARGO ATOM or 425\/26 onto this number.<\/strong> 194-26 remains tonight\u2019s dedicated Verified Attack on an Indian crewed Dhow, 1105 UTC 2 November, vessel status unknown; this afternoon\u2019s dedicated Al Jusufi file remains wrap on that number, not on 195-26. 193-26 remains last night\u2019s dedicated unnamed Lima hole, 9 nautical miles northeast, vessel and crew safe; MSCIO 166\/26 is wrap. 192-26 remains Monday morning\u2019s dedicated Khafji tanker Attack; IMO\u2019s new LARGO ATOM row is wrap. 425\/26 remains last night\u2019s dedicated Selat Storm wreck; IMO\u2019s new SELAT STORM row is wrap. Two unknown projectiles on 192-26\u2019s port side east of Khafji are not two unknown projectiles into an engine room 14 nautical miles northeast of Lima. Five products are five products. A Lima tanker is a sixth overnight file. Do not make them one hull.<\/li>\n
  • Do not merge this watch onto Leonora Kosan, Quba, AZINI, Aden or IMO\u2019s 128-count as a completed 195-26 naming.<\/strong> 181-26 \/ Leonora Kosan remains the 23 October 6-nautical-mile northeast-of-Limah row. 417\/26 remains the dedicated MSV Quba sunk file. 190-26 \/ 161\/26 remains the dedicated fishing-vessel hijack, AZINI; MSCIO Update 02 on that page now prints the vessel liberated and the incident closed \u2014 wrap, unused as dedicated. 184-26 \/ 416\/26 remains the Gulf of Aden PAG keep-clear and is now self-cancelled at 032359 UTC 3 November. IMO now prints 128 confirmed \/ 24 dead as at 3 November, with LARGO ATOM, SELAT STORM and ARZANAH as the new named rows \u2014 wrap, not tonight\u2019s dedicated file. IMO has not named 195-26. Fatality still 24. 424\/26 remains the dedicated 3\u20134 November Pakistan firing box through 040700 UTC 4 November. 427\/26 and 428\/26 remain Red Sea seaplane-landing wrap. 016-26 remains the blockade document pack. Update 110 remains the last numbered public periodic note. No Update 111 this run.<\/li>\n
  • Treat the missing hull, fire and propulsion lines as open damage lines.<\/strong> The public tape prints Tanker, two unknown projectiles, engine room, 14 nautical miles northeast of Lima, no casualties, and no environmental impact reported as this time. 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. An engine-room strike is a power-and-propulsion watch until a later product prints otherwise. 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 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 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 Tuesday\u2019s Gulf of Oman Attack or completed a salvage.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Warning 195-26 against tonight\u2019s dedicated 194-26 and against last night\u2019s dedicated 193-26 so operators can treat Tuesday night\u2019s tape as a numbered CSO Attack on a tanker 14 nautical miles northeast of Lima, not as a dhow rewrite, a 9-nautical-mile hole filed again, or a completed class survey.<\/p>\n","protected":false},"excerpt":{"rendered":"

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