The United Kingdom Maritime Trade Operations centre published Warning 193-26 as a numbered PDF on its product board, filename 20261102-ukmto_warning_193.pdf. The face of the product is titled 193-26 — ATTACK. The incident date is 1 November 2026. The incident time is 2020 UTC. The source line is Master. UKMTO states that it has received a report of an incident 9 nautical miles northeast of Lima, Oman. The Master reports the vessel has been struck by an unknown projectile which has caused a hole on the starboard side. Vessel and crew are safe, and no environmental impact is reported. 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 [email protected], +44 (0) 2392 222060, +44 (0) 7779 966976 and +44 (0) 7585 795608.
That is the working primary. Monday night’s product is a later-numbered Attack on an earlier 1 November clock, not a rewrite of this morning’s dedicated Warning 192-26, not a late naming of Sunday night’s dedicated Warning 191-26, and not a conversion of tonight’s dedicated NAVAREA IX 425/26 tug wreck onto a Lima hole. It names a vessel, a single unknown projectile and a starboard-side hole. It does not name a merchant hull, an IMO number, a flag, a ship type beyond vessel, a cargo, an attacker, a fire, a NUC or tow line, a latitude/longitude beyond the 9-nautical-mile northeast-of-Lima offset, or a keep-clear radius. This morning’s dedicated Warning 192-26 piece on this desk, retrieved as 20261102-ukmto_warning-192-26.pdf, still told operators that a tanker travelling southeast through the Arabian Gulf had been struck by two unknown projectiles on the port side at 2347 UTC, 72 nautical miles east of Ras Al Khafji. 193-26 is not that tanker. The 2020 UTC Master report sits about three hours and twenty-seven minutes earlier than 192-26’s 2347 UTC clock and about a gulf and a strait away. Masters who brief Monday night as 192-26 filed again, as 191-26’s Mayday named at last, as Selat Storm leaving Um Al Ghanam, or as Leonora Kosan hit a second time will have merged four other series into a Master Attack that withholds the struck hull.
What the warning actually printed
The confirmed tape is the body of 193-26. UKMTO has received a report of an incident 9 nautical miles northeast of Lima, Oman. The Master reports the vessel has been struck by an unknown projectile which has caused a hole on the starboard side. Vessel and crew are safe, and no environmental impact is reported. 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 tanker, tug, products, LPG or LNG type beyond the word vessel. The PDF prints vessel, not tanker and not tug boat. Do not invent a UAV, a mine, a small-boat device or a boarding. Do not invent a lat/long on the UKMTO PDF. 193-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 193-26. The crew line on this PDF is “vessel and crew safe,” not “all crew are accounted for” and not “crew reported safe.” Hold that wording. The damage line is a hole on the starboard side. Hold that too.
The product type is the first briefing fact. 193-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, Sunday night’s dedicated 191-26 and this morning’s dedicated 192-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 an unknown projectile struck a vessel on the starboard side 9 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 Monday night as “another Hormuz attached-device hit, crew safe” has borrowed 187-26’s method and Update 110’s Louise 1 all-clear and has dropped the 9-nautical-mile northeast-of-Lima offset that is the whole of this PDF. A DPA who briefs Monday night as a completed salvage because the PDF prints vessel and crew safe and no environmental impact has under-read a numbered Attack that still withholds hull, fire, damage volume beyond the hole, and onward status.
Master, one projectile and starboard hole 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’s dedicated 191-26, whose source line was Merchant Vessel relaying someone else’s Mayday. One unknown projectile is also a different count from 192-26’s two unknown projectiles on the port side and from 188-26’s single unknown projectile on the port side. Do not treat “Master” as a hull naming. Do not treat “unknown projectile” as a confirmed UAV, a confirmed mine, or a confirmed small-boat pairing. Do not treat “hole on the starboard side” as a confirmed tank group, a confirmed engine-room fire, a confirmed flooding rate, or a confirmed class survey. The public PDF does not say whether the vessel is still making way, whether propulsion is available, whether a tug was offered, or where the ship went after 2020 UTC.
The geography is the third briefing fact. 193-26 prints 9 nautical miles northeast of Lima, Oman. The location footer is Lima, Oman. That is Musandam’s Gulf of Oman face, on the eastern approach, not the Strait of Hormuz traffic-separation scheme, not this morning’s 72-nautical-mile east-of-Khafji offset, and not 0.6 nautical miles west of Jazirat Um Al Ghanam. Sunday night’s dedicated 191-26 remains a Strait of Hormuz Attack with a Channel 16 Mayday-relay clock. This morning’s dedicated 192-26 remains a northern Arabian Gulf tanker Attack. Tonight’s dedicated 425/26 remains a named tug wreck on the western Musandam face. 193-26 is none of those three plots. A passage plan that only carried this morning’s Khafji tanker, or that treated Monday afternoon as empty because 191-26 was a Hormuz Mayday, has not budgeted a 2020 UTC hole 9 nautical miles northeast of Lima.
The numbering is the fourth briefing fact. 193-26 is numbered after 192-26 on the product board. The incident clock is not. 2020 UTC on 1 November sits about three hours and twenty-seven minutes before 192-26’s 2347 UTC tanker hit east of Khafji, and about five hours and eleven minutes after 191-26’s 1509 UTC Mayday inside the Strait. Monitor the Situation first tracked the public 193-26 product at 18:55 UTC on 2 November, after this afternoon’s dedicated 123-count and 424/26 files. Do not brief Monday night as “193 after 192 on the water.” Brief Monday night as a later-issued Attack on an earlier Lima clock. Do not invent a 194-26 because 193 sits after 192 on the board.
Industry colour of the same clock, held separately: Arab Times restated the UKMTO 9-nautical-mile northeast-of-Lima offset, the starboard-side hole, the vessel-and-crew-safe line and the no-environmental-impact line from Muscat on 2 November, and said the warning did not identify the vessel or the origin of the projectile. Monitor the Situation first tracked the public product at 18:55 UTC on 2 November and tagged Lima as near the approach to the Strait of Hormuz. Clearwater Dynamics issued CW Alert 004-(Nov 26) against the 2020 UTC clock, restating the UKMTO sentences and tagging the region Indian Ocean and the aggressors Military. Those reprints are not a naming. Treat them as industry colour of the public PDF. Do not collapse them onto 193-26 as a completed identification, a TSS plot, a tug conversion, a fire line, or a conversion onto Selat Storm, Leonora Kosan, Louise 1, RITI or Sunday night’s unnamed Hormuz casualty. Monitor’s IRGC-attribution colour is not on the PDF. Do not promote it.
Official MSCIO wrap of the same clock, held separately: Alert 166/26, retrieved from mscio.eu/alerts/202, Attack, 2 November 8:49 p.m. page. MSCIO has received information regarding an incident at approximately 20:20 UTC on 1 November 2026, 9 nautical miles northeast of Lima, Oman, in the Strait of Hormuz. A vessel was reportedly struck by an unknown projectile, causing a hole on its starboard side. The vessel and crew are reported safe, and no environmental impact has been reported. Heightened vigilance, BMP-MS, report immediately to MSCIO. Contacts remain [email protected] / +33 (0)298 220 220 and +33 (0)298 220 170. 166/26 is wrap on tonight’s 193-26, not a dedicated file and not a hull naming. MSCIO prints “in the Strait of Hormuz.” UKMTO prints Lima, Oman and 9 nautical miles northeast of Lima. Do not promote MSCIO’s Strait tag onto the UKMTO PDF. Lima sits on Musandam’s Gulf of Oman face. Hold the two geographies separately.
What this is not
This is not Warning 192-26, and it is not a Khafji tanker. This morning’s dedicated Warning 192-26 remains an Attack, incident 1 November 2026, 2347 UTC, source Master, filename 20261102-ukmto_warning-192-26.pdf: 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. 193-26 is 2020 UTC, source Master, vessel, one unknown projectile, hole on the starboard side, 9 nautical miles northeast of Lima, Oman. Three hours and a gulf separate the two clocks. A tanker with two port-side projectiles east of Khafji is not a vessel with a starboard hole off Lima. Do not convert this morning’s Khafji tanker onto Monday night’s Lima hole. Do not convert Monday night’s vessel onto this morning’s unnamed Khafji casualty. Official MSCIO Alert 165/26, mscio.eu/alerts/201, 2 November 11:45 a.m. page, remains wrap on dedicated 192-26 — unused as a second Khafji piece.
This is not Warning 191-26, and it is not a Strait of Hormuz Mayday. Sunday night’s dedicated Warning 191-26 remains an Attack, incident 1 November 2026, 1509 UTC, source Merchant Vessel, filename 20261101-ukmto_warning_191_26.pdf: 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, no hole. 193-26 is 2020 UTC, source Master, this vessel reporting its own starboard hole, 9 nautical miles northeast of Lima. Five hours and a coast separate the two clocks. A Channel 16 relay of “another vessel” inside the Strait is not a Master report of a hole 9 nautical miles northeast of Lima. Do not convert Sunday night’s Mayday onto Monday night’s Lima Attack. Do not convert Monday night’s vessel onto Sunday night’s unnamed Hormuz casualty. Official MSCIO Alert 164/26 remains wrap on dedicated 191-26 — unused as dedicated.
This is not NAVAREA IX 425/26, and it is not a Selat Storm naming. Tonight’s dedicated 425/26, 021500 UTC 2 November, is 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, mariners cautioned. 193-26 prints vessel, hole, safe, Lima. It does not print tug, Selat Storm, sunk, or Um Al Ghanam. 9 nautical miles northeast of Lima is the Gulf of Oman face. 0.6 nautical miles west of Um Al Ghanam is the Strait face, on the order of 15 nautical miles west of Lima. A Master Attack that withholds the hull and prints safe is not a NAVAREA that names a tug and prints sunk. Do not collapse 425/26 onto 193-26 as a UKMTO naming. Do not collapse 193-26 onto 425/26 as a continuing-voyage rewrite of a wreck. Vanguard / Seatrade / Clearwater colour that puts Selat Storm against Sunday’s 1509 UTC Mayday is held on the 425/26 file, not on this PDF.
This is not a rewrite of 181-26, and it is not Leonora Kosan. Tuesday afternoon’s dedicated IMO 121-count named Leonora Kosan, IMO 9390953, 23 October, 6 nautical miles northeast of Limah, Oman, damaged, no pollution. UKMTO 181-26 remains an unnamed Limah Attack on that earlier clock. 193-26 prints Lima, not Limah, 9 nautical miles, not 6, 1 November, not 23 October, and vessel, not LPG. Do not convert Leonora Kosan onto 193-26 because both files sit northeast of the same Omani town under two spellings. Hold Lima as UKMTO printed it. Hold Limah as IMO printed it. They are not a completed identity.
This is not Update 110, and it is not a 168th row on that note. Sunday afternoon’s 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. 191-26 at 1509 UTC, 192-26 at 2347 UTC and 193-26 at 2020 UTC all sit after that cut-off. None of them is a completed Update 111. Do not back-fit a 2020 UTC Lima Attack onto a 1300 UTC table. Do not treat Update 110’s Louise 1 or Arzanah rows as the Monday night casualty.
This is not a rewrite of unused 186-26, dedicated 187-26, dedicated 188-26 or dedicated 189-26, and it is not NAVAREA IX 420/26 or 417/26. Thursday afternoon’s 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’s 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 and this afternoon’s dedicated IMO 123-count now print LOUISE 1 against that file. Saturday morning’s 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. Friday night’s dedicated 188-26 remains an unnamed vessel Attack 40 nautical miles south of Lavan Island; Update 110 now prints AL MAYEDA against that file. Friday morning’s dedicated 417/26 remains dhow MSV Quba sunk at 26-19.95N 056-16.82E. Those products are Hormuz, Musandam-west, Khasab or Lavan water. 193-26 is Lima water. Do not convert RITI, Louise 1, Arzanah, Al Mayeda or Quba onto 193-26 as a UKMTO naming.
This is not 190-26, and it is not Sunday morning’s dedicated AZINI hijack. Saturday night’s dedicated Warning 190-26 remains a Suspicious Activity boarding of a large fishing vessel at 1419 UTC 30 October. Sunday morning’s 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. 193-26 prints an Attack and a starboard hole on a vessel off Lima. A Somali-Basin fishing-vessel hijack is not a Lima projectile hit. Do not merge the mothership watch onto this Attack because both sat on a late-October board.
This is not an International Maritime Organization 124-count, and it is not Advisory 184-26. This afternoon’s dedicated IMO highlighted-incidents board remains 123 confirmed / 24 seafarer fatalities as at 2 November, with Louise 1 still the newest named row. IMO has not named 191-26, 192-26, 193-26, Selat Storm, RITI, Al Mayeda, Arzanah, AZINI or Quba. Wednesday afternoon’s 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. This afternoon’s dedicated NAVAREA IX 424/26 remains the 3–4 November Pakistan firing box. Same-board 426/26, 021720 UTC 2 November, live weapon firing 0300–0700 UTC on 3 November only, remains wrap — unused as a second Pakistan firing piece. Thursday’s dedicated Contship Jet and Khoryv Black Sea files, Saturday’s dedicated NAVWARN 775/26, 776/26 and 777/26, and this morning’s dedicated NAVWARN 779/26 remain Kaliakra, Shabla, Burgas and Galata products. They do not belong on a Lima Attack.
Operational implications
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, Monday night is a later-issued Attack on a 2020 UTC Master clock, on top of this morning’s Khafji tanker, on top of Sunday night’s Hormuz Mayday, and on top of Sunday afternoon’s Update 110 named table. 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. 193-26 adds a vessel that was already holed 9 nautical miles northeast of Lima, about five hours after Sunday’s Hormuz Mayday and about three hours before this morning’s Khafji tanker. A passage plan that only carried Update 110’s 011300 UTC cut-off, or that treated Monday as closed because 192-26 was the last UKMTO number at 11:30 UTC, has not budgeted a 2020 UTC hole on Musandam’s Gulf of Oman face.
One unknown projectile and a starboard hole, learned from that vessel’s Master, is a standoff watchkeeping problem and a flooding-and-stability problem before it is a war-risk rewrite. 193-26 is not 187-26’s alongside, slow-speed, above-waterline device problem. It is a lookout, CPA, AIS-on/AIS-off, citadel, possible-disablement and possible-ingress problem at the same time as it is a missing-fire-line problem. BMP MS projectile and citadel guidance remains the working industry pack; 193-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 hull as Leonora Kosan, Louise 1 or Selat Storm after the fact. Log the Warning number, the 1 November date, the 2020 UTC clock, the Master source line, the vessel type, the unknown-projectile method, the starboard-side hole, the 9-nautical-mile northeast-of-Lima offset, the vessel-and-crew-safe line, and the no-environmental-impact line. Do not log Selat Storm, Leonora Kosan, Louise 1, RITI, Arzanah, a small-boat device, a mine in the water, a Khafji offset, a fire, a NUC, a sunk line, or an IRGC attribution that the PDF does not print.
The missing hull, fire, flooding and onward-status lines are the practical damage watch, not a completed all-clear. The public PDF says the vessel and crew are safe and that no environmental impact is reported. It does not say whether the vessel is making way, whether propulsion or steering is available, whether the hole is above or below the waterline beyond “starboard side,” whether a tug was offered, whether a fire started and was put out, or where the ship went after 2020 UTC. Those missing lines are omissions. They are not a completed “all well,” and they are not a NUC. “Vessel and crew safe” is a status sentence. It is not a class survey. Next-port authorities will want a written account that 193-26 does not contain. Charterers and war-risk underwriters will now ask whether the ship was 9 nautical miles northeast of Lima after 2020 UTC on 1 November, whether it reported, and whether it was following Update 110 and 016-26. They will not be answered by this morning’s Khafji tanker, by Sunday night’s Hormuz Mayday, by this afternoon’s 123-count, or by a NAVAREA that names a different hull on a different plot.
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 holed hull, a Mayday on Channel 16 or pollution go to UKMTO on the 193-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; 166/26 is the numbered wrap against this clock, not a substitute for the UKMTO PDF. Registering with one mailbox is not a substitute for the others. 193-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’s pack. Watch a PDF revision that names a hull, prints a type beyond vessel, a lat/long, a NUC, a tow, a fire, a flooding line or a next-port line; a NAVAREA that plots this vessel rather than Selat Storm, RITI or Quba; a flag or class note; a JMIC Update 111; or an IMO-board row — not a headline that this afternoon’s 123-count closed Monday’s Gulf of Oman Attack.
Keep the dedicated files on their own lines. 192-26 remains this morning’s dedicated Arabian Gulf tanker Attack, 2347 UTC, 72 nautical miles east of Ras Al Khafji; MSCIO 165/26 is wrap. 191-26 remains Sunday night’s dedicated Channel 16 Mayday-relay Attack inside the Strait of Hormuz; MSCIO 164/26 is wrap. Update 110 remains Sunday afternoon’s numbered regional note, ICOD 011300 UTC, 167 incidents, Hormuz still SEVERE, Arabian Gulf still SUBSTANTIAL. This afternoon’s dedicated IMO board remains 123 / 24 as at 2 November, Louise 1 still the newest named row. 189-26 remains Saturday morning’s unnamed time-late Hormuz Attack; Arzanah on Update 110 is wrap, not a 193-26 hull. 188-26 remains Friday night’s unnamed vessel Attack 40 nautical miles south of Lavan Island; Al Mayeda on Sunday’s Nakilat statement and on Update 110 is wrap. 187-26 remains Friday morning’s unnamed outbound-tanker Attack 25 nautical miles northeast of Khasab; Louise 1 on Update 110 and on this afternoon’s 123-count is wrap. 186-26 remains the unused 1600 UTC unknown-projectile Attack; RITI on 420/26 and on Update 110 is wrap. 185-26 remains Thursday’s 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 123-count as wrap. 181-26 / Leonora Kosan remains the 23 October Limah row. 016-26 remains Wednesday afternoon’s blockade document pack. 424/26 remains this afternoon’s dedicated 3–4 November Pakistan firing box. 426/26 remains wrap. Do not recast 2 November night as a named Lima casualty, as Selat Storm continuing, as 191-26 or 192-26 filed twice, as Update 111, as an IMO 124-count, or as a Hormuz reopen.
What Operators Should Note
- Log 193-26 as a 1 November Lima Attack on a Master clock, not as a 192-26 rewrite and not as a Selat Storm naming. UKMTO Warning 193-26, incident 1 November 2026, 2020 UTC, source Master. Filename
20261102-ukmto_warning_193.pdf. 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. Transit with caution. Report suspicious activity to UKMTO, [email protected] / +44 (0) 2392 222060. Authorities are investigating. UKMTO printed neither hull, IMO, flag, type beyond vessel, cargo, attacker, fire, lat/long beyond the 9-nautical-mile offset, anchorage, NUC, tow, next port, nor a keep-clear radius. This is not 192-26, not 191-26, not 425/26, not Update 110, and not Leonora Kosan. - Hold the clock, the water and the numbering. 193-26 is Attack, not Suspicious Activity. The working date is 1 November. The working time is 2020 UTC. The working source is Master, not Merchant Vessel, not Verified, and not CSO. The working water is 9 nautical miles northeast of Lima, Oman. The working method is one unknown projectile. The working damage line is a hole on the starboard side. The crew line is vessel and crew safe, not “all crew are accounted for.” The product number is 193. The incident clock sits before 192-26’s 2347 UTC Khafji tanker and after 191-26’s 1509 UTC Mayday. Do not brief Monday night as “192-26’s Khafji tanker, filed on the Omani coast.” Do not brief Monday night as quiet because the PDF withholds hull and fire.
- Hold Arab Times / Monitor the Situation / Clearwater colour, and MSCIO 166/26, separately. Arab Times restated the public PDF from Muscat and said the warning did not identify the vessel. Monitor the Situation first tracked the product at 18:55 UTC on 2 November. Clearwater 004-(Nov 26) restated the UKMTO sentences. MSCIO Alert 166/26, mscio.eu/alerts/202, is wrap on tonight’s 193-26 and adds a Strait of Hormuz tag that the UKMTO PDF does not print. None of those products named a hull. Do not promote a wire rewrite, a Military tag, an IRGC attribution, or MSCIO’s Strait line to a 193-26 naming, a TSS plot, a tug conversion, or a conversion onto Selat Storm or Leonora Kosan.
- Do not collapse 192-26, 191-26, 425/26 or Update 110’s named rows onto this number. 192-26 remains this morning’s dedicated tanker Attack, 2347 UTC, 72 nautical miles east of Ras Al Khafji; MSCIO 165/26 is wrap. 191-26 remains Sunday night’s dedicated Strait of Hormuz Mayday-relay Attack; MSCIO 164/26 is wrap. 425/26 remains tonight’s dedicated named tug wreck, Selat Storm, 26-22.55N 056-20.47E. Update 110 remains Sunday afternoon’s dedicated note, ICOD 011300 UTC, 167 incidents. 189-26 / Arzanah, 188-26 / Al Mayeda, 187-26 / Louise 1 and 186-26 / RITI remain earlier dedicated or unused files. Five earlier products are five products. A Lima vessel is a sixth overnight file. Do not make them one hull.
- Do not merge this watch onto Leonora Kosan, Quba, AZINI, Aden or the IMO 123-count. 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, east-southeast of Socotra. 184-26 / 416/26 remains the Gulf of Aden PAG keep-clear through 3 November. 185-26 remains the 0300 UTC 9-nautical-mile north-of-Khasab fire. This afternoon’s dedicated IMO board remains 123 / 24 as at 2 November, Louise 1 still the newest named row. 016-26 remains the blockade document pack. 424/26 remains this afternoon’s dedicated 3–4 November Pakistan firing box. 426/26 remains wrap.
- Treat the missing hull, fire and onward-status lines as open damage lines. The public tape prints vessel, unknown projectile, hole on the starboard side, 9 nautical miles northeast of Lima, vessel and crew safe, and no environmental impact reported. It does not print a hull, a type beyond vessel, a fire, a survey, a hole size, a waterline 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’s pack. Watch a PDF revision that names a hull or prints a lat/long; a NAVAREA that plots this vessel rather than Selat Storm; a flag or class note; a JMIC Update 111; or an IMO-board row — not a headline that this afternoon’s 123-count closed Monday’s Gulf of Oman Attack or completed a salvage.
Regulas Shipping will keep lining Warning 193-26 against this morning’s dedicated 192-26 and against Sunday night’s dedicated 191-26 so operators can treat Monday night’s tape as a numbered Master Attack on a vessel 9 nautical miles northeast of Lima, not as a Khafji tanker rewrite, a Selat Storm naming, or a completed class survey.
