{"id":1320,"date":"2026-11-11T11:36:16","date_gmt":"2026-11-11T11:36:16","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-202-26-records-a-tanker-incident-in-the-strait-of-hormuz\/"},"modified":"2026-11-11T11:37:16","modified_gmt":"2026-11-11T11:37:16","slug":"ukmto-202-26-records-a-tanker-incident-in-the-strait-of-hormuz","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-202-26-records-a-tanker-incident-in-the-strait-of-hormuz\/","title":{"rendered":"UKMTO 202-26 records a tanker incident in the Strait of Hormuz"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre published Warning 202-26 as a numbered PDF on its product board, filename 20261111-ukmto_warning_202_26.pdf<\/code>. The face of the product is titled 202-26 \u2014 SUSPICIOUS ACTIVITY. The incident date is TBC. The incident time is TBC. The source line is Military authorities. UKMTO states that it has received a report of an incident involving a tanker in the Strait of Hormuz. The status of crew, damage assessment, and environmental impact are unknown at the time of this report. 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 Strait of Hormuz. Emergency contacts printed on UKMTO warnings remain watchkeepers@ukmto.org, +44 (0) 2392 222060, +44 (0) 7779 966976 and +44 (0) 7585 795608.<\/p>\n

That is the working primary. Wednesday afternoon\u2019s product is a military-authorities Suspicious Activity on a tanker in the Strait of Hormuz, posted on the 11 November board, with date, time, crew, damage and environmental lines still open. It is not a rewrite of this morning\u2019s dedicated Warning 201-26, not a rewrite of Sunday morning\u2019s dedicated Warning 200-26, not a conversion of Sunday morning\u2019s dedicated Warning 199-26 onto a later Hormuz fire, and not a conversion of this morning\u2019s companion IMO 133-count onto an 11 November hull. It names a tanker, a Strait of Hormuz footer, a Suspicious Activity stamp and an unknown status line. It does not name a merchant hull, an IMO number, a flag, a cargo grade, an attacker, a projectile, a mine, a fire, a NUC or tow line, a nautical-mile offset, a latitude\/longitude, a next port or a keep-clear radius. UKMTO posted the numbered PDF on the 11 November product board against TBC clocks. Masters who brief Wednesday afternoon as 201-26\u2019s unnamed Lima projectile now recast as a Hormuz fire, as 200-26\u2019s outbound projectile, as 199-26\u2019s northwest-of-Khasab evacuation, or as an Iranian mine claim will have merged four other series into a Suspicious Activity product that still withholds the struck hull, still withholds a method, and still withholds whether anyone is on board.<\/p>\n

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

The confirmed tape is the body of 202-26. UKMTO has received a report of an incident involving a tanker in the Strait of Hormuz. The status of crew, damage assessment, and environmental impact are unknown at the time of this report. 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. 202-26 prints incident, not explosion, not fire, not unknown projectile, and not two projectiles. Do not invent a lat\/long on the UKMTO PDF. 202-26 does not print one. Do not invent a keep-clear radius around Hormuz, Musandam, Khasab, Lima, Fujairah or the TSS. The PDF does not print one. Do not invent a fire-extinguished line, a lost-propulsion line, a sunk line, an evacuation line, a crew-safe line or a next-port name. The product already prints that crew, damage and environmental impact are unknown. Hold that wording. Do not convert unknown into this morning\u2019s \u201cthe crew are safe.\u201d Do not convert unknown into Sunday\u2019s \u201call crew are safe and accounted for.\u201d Do not convert unknown into 199-26\u2019s evacuation.<\/p>\n

The product type is the first briefing fact. 202-26 is Suspicious Activity, the same family that first ran dedicated 199-26 before Update 001 reclassified that Khasab fire to Attack as wrap, not the Attack family that ran dedicated 191-26 through 197-26, dedicated 200-26 and this morning\u2019s dedicated 201-26, and not the Advisory family that ran dedicated 198-26. 202-26 is a new numbered Suspicious Activity on a later board. UKMTO says a tanker in the Strait of Hormuz is involved in an incident. 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 on fire. It does not say the ship was struck by an unknown projectile. It does not say the ship is at anchor, NUC, under tow, or sunk. A DPA who briefs Wednesday afternoon as \u201canother Hormuz Attack, projectile, crew safe\u201d has borrowed 201-26\u2019s method and 201-26\u2019s crew line and has dropped the Suspicious Activity stamp, the TBC clocks, the military-authorities source and the unknown-status sentence that are the whole of this PDF. A DPA who briefs Wednesday afternoon as a completed salvage because Iran later printed a mine has under-read a numbered Suspicious Activity that still withholds hull, method, damage volume and whether the ship is making way.<\/p>\n

Military-authorities source and TBC clocks is the second briefing fact. The report sits on a Military authorities source, not on Master, not on Company Security Officer, and not on Verified. That is a different reporting path from this morning\u2019s dedicated 201-26, whose source line is Master, from Sunday morning\u2019s dedicated 200-26, whose source line is Company Security Officer, and from Thursday morning\u2019s dedicated 196-26, whose source line was Verified. It is the same source family as Sunday morning\u2019s dedicated 199-26, whose first public product sat on Military authorities. Time-late is not printed on the face of this product. The incident date is TBC. The incident time is TBC. The numbered PDF appeared on the 11 November board. Do not treat the 11 November filename as a closed 11 November strike. Do not treat TBC as 1338 UTC. Do not treat TBC as 2020 UTC. Do not treat \u201cincident involving a tanker\u201d as a confirmed UAV, a confirmed mine, a confirmed small-boat pairing, or a confirmed projectile strike. Do not treat \u201cunknown at the time of this report\u201d as a class survey, and do not convert it into 201-26\u2019s crew-safe line, 201-26\u2019s first-light survey, or 199-26\u2019s evacuation line. The public PDF says crew, damage and environmental impact are unknown. It does not say whether a fire started, whether a hole was found, whether a tug was offered, or where the ship went after the report.<\/p>\n

The geography is the third briefing fact. 202-26 prints the Strait of Hormuz. The location footer is Strait of Hormuz. That is the named water, not this morning\u2019s dedicated 201-26 19-nautical-mile northeast-of-Lima offset with a Lima Oman footer, not Sunday morning\u2019s dedicated 199-26 8-nautical-mile northwest-of-Khasab offset, not Friday night\u2019s 16-nautical-mile east-of-Khasab offset, and not Saturday night\u2019s 18-nautical-mile east-of-Khor-Fakkan Gulf of Oman offset. Sunday morning\u2019s dedicated 200-26 remains a Strait of Hormuz footer with no nautical-mile offset, but that product is Attack, CSO, 2020 UTC 7 November, unknown projectile, crew safe, no environmental impact. A shared footer is not a shared product. A passage plan that only carried 201-26\u2019s 19-nautical-mile northeast-of-Lima watch, or that treated Wednesday afternoon as closed because 201-26 was the last UKMTO number at this morning\u2019s desk, has not budgeted a later Suspicious Activity on a tanker in the Strait of Hormuz with TBC clocks and an unknown-status line.<\/p>\n

The numbering is the fourth briefing fact. 202-26 is numbered after 201-26 on the product board. It is a Warning, Suspicious Activity. UKMTO\u2019s Suspicious Activity series on this Wednesday board now ends at 202-26. Dedicated 201-26 remains the last Attack. Dedicated 199-26 remains the last previous Suspicious Activity product, later reclassified to Attack on Update 001 as wrap, unused as a second dedicated Khasab fire piece. Dedicated 198-26 remains the last Advisory. Do not brief Wednesday afternoon as \u201c202 after 201 on the same hull.\u201d Brief Wednesday afternoon as a later-issued Suspicious Activity on a later 11 November board, incident date TBC, incident time TBC. There is no 203-26 this run.<\/p>\n

Industry colour of the same clock, held separately: Reuters \/ Arab News restated the public sentences \u2014 UKMTO received a report of an incident involving a tanker in the Strait of Hormuz, crew, damage and environmental impact unknown. Those reprints are colour of the PDF, not a naming. Rudaw restated the same public lines and noted the product followed this morning\u2019s dedicated 201-26. Iran\u2019s army, via the same Arab News \/ Reuters wrap, reported that an oil tanker struck a mine and caught fire in a prohibited area. Iran\u2019s Islamic Revolutionary Guard Corps Navy, via IRNA \/ Rudaw wrap, said a third oil tanker had exploded after striking a naval mine on an unauthorised route. Hold mine, fire, prohibited area, unauthorised route and \u201cthird tanker\u201d as colour, not PDF facts. 202-26 prints incident involving a tanker and does not print a mine, a fire, a route restriction or an attacker. ADNOC Logistics & Services via WAM remains unused as dedicated: unpublished hull damaged in UAE territorial waters on the afternoon of 10 November. Do not collapse that WAM statement onto a Suspicious Activity product that prints the Strait of Hormuz and does not print a hull. No numbered MSCIO wrap against the TBC Hormuz clock was retrieved this run.<\/p>\n

What this is not<\/h2>\n

This is not Warning 201-26, and it is not this morning\u2019s unnamed Lima projectile. This morning\u2019s dedicated Warning 201-26 remains an Attack, incident 10 November 2026, 1338 UTC, source Master, filename 20261110-ukmto_warning_201_26.pdf<\/code>: tanker struck by an unknown projectile 19 nautical miles northeast of Lima, Oman; crew safe; no environmental impact reported; Master will conduct damage assessment at first light; location footer Lima Oman. 202-26 is Suspicious Activity, incident date TBC, incident time TBC, source Military authorities, tanker involved in an incident in the Strait of Hormuz, crew\/damage\/environmental status unknown, footer Strait of Hormuz. A family change from Attack to Suspicious Activity, a source change from Master to Military authorities, a geography change from a 19-nautical-mile northeast-of-Lima offset to a Strait of Hormuz footer with no offset, and an unknown-status line that 201-26 does not print separate the two clocks. A Master Attack with a first-light survey is not a military-authorities Suspicious Activity with TBC clocks. Do not convert Wednesday afternoon\u2019s tanker onto this morning\u2019s Lima tanker. Do not convert this morning\u2019s \u201cthe crew are safe\u201d onto Wednesday afternoon\u2019s unknown crew line. Do not drop Wednesday afternoon\u2019s unknown damage line because this morning\u2019s PDF already printed no environmental impact.<\/p>\n

This is not Warning 200-26, and it is not Sunday morning\u2019s unnamed outbound Hormuz projectile. Sunday morning\u2019s dedicated Warning 200-26 remains an Attack, incident 7 November 2026, 2020 UTC, source Company Security Officer, time-late, filename 20261108-ukmto_warning-200-26.pdf<\/code>: tanker struck by an unknown projectile while transiting outbound through the Strait of Hormuz; all crew safe and accounted for; no reported environmental impact at this time; location footer Strait of Hormuz. 202-26 is Suspicious Activity, TBC, Military authorities, incident involving a tanker, unknown status, same Strait of Hormuz footer. Four days, a family change from Attack to Suspicious Activity, a source change from CSO to Military authorities, and a method change from unknown projectile to an unnamed incident separate the two clocks. A shared Hormuz footer is not a shared hull. Do not convert Wednesday afternoon\u2019s tanker onto Sunday\u2019s outbound tanker. Do not convert Sunday\u2019s \u201call crew are safe and accounted for\u201d onto Wednesday afternoon\u2019s unknown crew line. Do not invent an outbound stamp on 202-26; the PDF does not print outbound, inbound, or TSS.<\/p>\n

This is not Warning 199-26, and it is not Sunday morning\u2019s unnamed northwest-of-Khasab fire. Sunday morning\u2019s dedicated Warning 199-26 remains a time-late tanker fire 8 nautical miles northwest of Khasab, Oman, crew evacuated, source Military authorities, first posted as Suspicious Activity. UKMTO Warning 199-26 Update 001 later reclassified that incident to ATTACK and printed 1920 UTC on 7 November. That Update 001 remains wrap on dedicated 199-26, unused as a second dedicated Khasab fire piece. This morning\u2019s companion IMO 133-count is the first official IMO print of NAVIG8 MACALLISTER, IMO 9482873, against that 8-nautical-mile northwest-of-Khasab 7 November clock \u2014 wrap on the IMO file, unused as a 202-26 naming. 202-26 is Suspicious Activity, TBC, tanker, Strait of Hormuz, unknown status, no fire line, no evacuation line, no nautical-mile offset. A Khasab fire with an evacuation is not a Hormuz incident with an unknown-status line. Do not convert Wednesday afternoon\u2019s incident onto Sunday\u2019s fire. Do not convert Wednesday afternoon\u2019s unknown crew line onto Sunday\u2019s evacuation. Do not promote NAVIG8 MACALLISTER, IMO 9482873, or an 8-nautical-mile northwest-of-Khasab offset onto a PDF that prints the Strait of Hormuz and does not print a hull. Do not treat 202-26 as 199-26 filed twice because both opened as Suspicious Activity on a military-authorities source.<\/p>\n

This is not Warning 197-26, not Advisory 198-26, not Warning 196-26 \/ Velos Sapphire, not 195-26 \/ Grit, and not 191-26. Friday night\u2019s dedicated Warning 197-26 remains an Attack, incident 5 November 2026, 2200 UTC, source Master: tanker, explosion at the waterline, port side, 16 nautical miles east of Khasab; crew safe; own power. Saturday night\u2019s dedicated Advisory 198-26 remains an Advisory, bulk carrier and military forces, 18 nautical miles east of Khor Fakkan, incident time TBC; Tuesday morning\u2019s dedicated IMO 131-count named HUDA, IMO 9197088, against that 7 November Oman-coast clock. Thursday morning\u2019s dedicated Warning 196-26 remains an Attack, tanker struck by two unidentified projectiles, 50 nautical miles north of Madinat ash Shamal, Qatar; Friday afternoon\u2019s dedicated IMO fatality conversion remains Velos Sapphire, IMO 9321201, one seafarer fatality, wrap on that Qatar sheet. Tuesday night\u2019s dedicated 195-26 remains a CSO Attack, two unknown projectiles into the engine room, 14 nautical miles northeast of Lima; IMO Grit remains wrap. 202-26 prints tanker, incident, Strait of Hormuz, TBC, Military authorities, unknown status. It does not print bulk carrier, Huda, Qatar, two projectiles, engine room, waterline explosion, dhow, or 1 November. Do not collapse those files onto this number because they share Hormuz, tanker, TBC or military wording.<\/p>\n

This is not an Iranian mine naming, not an ADNOC Logistics & Services naming, not Update 113, and not an 11 November IMO row. Iran\u2019s army \/ IRGC Navy statements that a tanker struck a mine and caught fire in a prohibited area remain colour, unused as a completed 202-26 method. 202-26 prints incident involving a tanker. It does not print mine, fire, prohibited area or IRGC. ADNOC Logistics & Services, via WAM, remains unused as dedicated: unpublished hull, UAE territorial water, afternoon of 10 November, response operations ongoing. Last week\u2019s dedicated Update 112, ICOD 081300 UTC 8 November, remains the last numbered public periodic note. Its confirmed-incidents table closed before this 11 November board. This morning\u2019s companion IMO board, as at 10 November, prints 133 confirmed \/ 25 dead with NAVIG8 MACALLISTER as the named top row and does not print an 11 November hull. IMO has not named 202-26. No 203-26, no Update 113 and no IMO 134 this run.<\/p>\n

Operational implications<\/h2>\n

For a master already shaping a Hormuz outbound or inbound, Musandam, Khasab, Lima, Fujairah, Khor Fakkan, Sohar or Gulf of Oman coastal transit, or holding in the Southern Gulf this afternoon, Wednesday is a later Suspicious Activity on a TBC tanker clock, on top of this morning\u2019s dedicated 201-26 19-nautical-mile northeast-of-Lima projectile, on top of Sunday morning\u2019s dedicated 200-26 outbound Hormuz projectile, and on top of Sunday morning\u2019s dedicated 199-26 northwest-of-Khasab fire. Update 112 remains the last numbered JMIC note and still prints Hormuz SEVERE and Arabian Gulf SUBSTANTIAL, with an ICOD that closed before this board. 016-26 remains the working blockade document pack for hulls that still need the Strait. 202-26 adds a tanker that military authorities reported as involved in an incident in the Strait of Hormuz, with crew, damage and environmental impact unknown, and with date and time still TBC. A passage plan that only carried 201-26\u2019s Lima Attack, or that treated Wednesday afternoon as closed because 201-26 was the last UKMTO number at this morning\u2019s desk, has not budgeted a later Suspicious Activity on Hormuz water and has not budgeted an unknown-status line that is still open this afternoon.<\/p>\n

An unnamed incident, learned from military authorities on TBC clocks, with crew, damage and environmental impact unknown, is a standoff watchkeeping problem and an open-status problem before it is a war-risk rewrite. 202-26 is not 201-26\u2019s unknown-projectile, crew-safe, first-light problem. It is not 200-26\u2019s outbound-projectile, crew-safe problem. It is not 199-26\u2019s fire-and-evacuation problem. It is not 197-26\u2019s waterline-explosion, own-power problem. It is a lookout, CPA, AIS-on\/AIS-off, citadel and damage-watch problem at the same time as it is an unknown-crew problem. BMP MS projectile, mine and citadel guidance remains the working industry pack; 202-26 does not reprint it, does not print a mine, and does not order an armed team. It also does not authorise a master to treat every radar contact in the Strait as a confirmed Attack, or to treat every AIS-on tanker as 201-26, 200-26, 199-26, Grit, Vieila or Navig8 Macallister after the fact. Log the Warning number, the 11 November board date, the TBC clocks, the Military authorities source line, the tanker type, the Strait of Hormuz footer, the incident wording, and the unknown crew\/damage\/environmental line. Do not log a hull, 201-26\u2019s projectile, 201-26\u2019s Lima offset, 199-26\u2019s fire, 199-26\u2019s evacuation, an Iranian mine, an ADNOC operator, a NUC, a sunk line, or an Omani-port finding that the PDF does not print.<\/p>\n

The missing hull, method and status lines are the practical damage watch, not a completed all-clear. The public PDF says crew, damage assessment and environmental impact are unknown at the time of this report. Those are status sentences. They are not a class survey, and they are not a finding that the hull is undamaged. 202-26 prints the opposite of a closed survey: unknown. Next-port authorities will want a written account that 202-26 does not contain. Charterers and war-risk underwriters will now ask whether the ship was in the Strait of Hormuz against this TBC clock, whether military authorities reported on time, whether a later PDF named a hull or a method, and whether the ship was following Update 112 and 016-26. They will not be answered by this morning\u2019s 201-26 projectile, by Sunday\u2019s 200-26 projectile, by Sunday\u2019s 199-26 fire, by IMO\u2019s Navig8 Macallister row, by an Iranian mine claim, or by a WAM statement that names a different unpublished hull on UAE territorial water.<\/p>\n

For a DPA and an operator with any merchant hull still using Hormuz, Musandam, Khasab, Lima, 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 202-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 TBC Hormuz clock was retrieved this run. Registering with one mailbox is not a substitute for the others. 202-26 does not order a daylight-only transit, a deviation around a published circle, or a halt to visit-and-search compliance. Keep Update 112 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 UTC clock, a method, a NUC, a tow, a fire, a flooding line, a casualty line, a completed survey or a next-port line; a NAVAREA that plots this tanker rather than Grit, Navig8 Macallister, Selat Storm, RITI, Quba or Louise 1; a flag or class note; a JMIC Update 113; or an IMO-board row on an 11 November hull \u2014 not a headline that 201-26 closed Wednesday\u2019s board, that an Iranian mine completed a method, or that an ADNOC WAM statement completed a naming.<\/p>\n

Keep the dedicated files on their own lines. 201-26 remains this morning\u2019s dedicated Master Attack on a tanker 19 nautical miles northeast of Lima, unknown projectile, 1338 UTC 10 November, crew safe, no environmental impact, first-light damage assessment, footer Lima Oman. 200-26 remains Sunday morning\u2019s dedicated CSO Attack on an outbound Hormuz tanker, unknown projectile, 2020 UTC 7 November, crew safe, no environmental impact, footer Strait of Hormuz. 199-26 remains Sunday morning\u2019s dedicated tanker fire 8 nautical miles northwest of Khasab, crew evacuated, military authorities, later reclassified to Attack on Update 001 as wrap; this morning\u2019s companion IMO 133-count remains the first official print of Navig8 Macallister against that Khasab clock, unused as a 202-26 naming. 198-26 remains Saturday night\u2019s dedicated Advisory on a bulk carrier and military forces 18 nautical miles east of Khor Fakkan; Tuesday morning\u2019s dedicated IMO 131-count remains the Huda conversion on that Oman-coast sheet. 197-26 remains Friday night\u2019s dedicated Master Attack on a tanker 16 nautical miles east of Khasab, explosion at the waterline port side, crew safe, under own power. 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; Friday afternoon\u2019s dedicated IMO 25-fatality conversion remains Velos Sapphire 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; IMO Grit remains wrap on that number. Update 112 remains ICOD 081300 UTC, 177 incidents. 016-26 remains the blockade document pack. Last night\u2019s dedicated NAVAREA IX 435\/26 remains the second Fujairah SKATE 3D box through 20 November. Last night\u2019s dedicated Irakleio 1441\/26 remains the unauthorised FA76-1127-26 void on the Abeille Marengo file. This morning\u2019s companion IMO board remains 133 confirmed \/ 25 dead as at 10 November, NAVIG8 MACALLISTER top row. Do not recast 11 November afternoon as a named Hormuz tanker, as 201-26 recast, as 199-26 filed twice, as an Iranian mine naming, as an ADNOC naming, as Update 113, or as IMO moving an 11 November hull onto the 133-count.<\/p>\n

What Operators Should Note<\/h2>\n
    \n
  • Log 202-26 as an 11 November Hormuz tanker Suspicious Activity on a military-authorities clock, not as a 201-26 rewrite and not as a 200-26 rewrite.<\/strong> UKMTO Warning 202-26, incident date TBC, incident time TBC, source Military authorities. Filename 20261111-ukmto_warning_202_26.pdf<\/code>. Incident involving a tanker in the Strait of Hormuz. Status of crew, damage assessment and environmental impact unknown at the time of this report. Transit with caution. Report suspicious activity to UKMTO, watchkeepers@ukmto.org \/ +44 (0) 2392 222060. Authorities are investigating. Location footer Strait of Hormuz. UKMTO printed neither hull, IMO, flag, cargo, attacker, projectile, mine, fire, lat\/long, nautical-mile offset, anchorage, NUC, tow, next port, nor a keep-clear radius. This is not 201-26, not 200-26, not 199-26 \/ Navig8 Macallister, not 195-26 \/ Grit, not 197-26 \/ Vieila, and not 198-26 \/ Huda.<\/li>\n
  • Hold the family, the water and the unknown-status stamp.<\/strong> 202-26 is Suspicious Activity, not Attack and not Advisory. The working board date is 11 November. The working incident date is TBC. The working incident time is TBC. The working source is Military authorities, not Master and not Company Security Officer. The working type is tanker. The working water is the Strait of Hormuz, footer Strait of Hormuz, with no nautical-mile offset. The working method is an incident \u2014 not a fire, not an unknown projectile, and not a mine. The crew line is unknown, not safe and not evacuated. The environmental line is unknown. The damage line is unknown, not a closed survey and not a first-light assessment. The product number is 202. The board sits after 201-26\u2019s 1338 UTC 10 November Lima tanker and after 200-26\u2019s 2020 UTC 7 November outbound Hormuz tanker. Do not brief Wednesday afternoon as \u201c201-26\u2019s Lima projectile, now in the Strait.\u201d Do not treat TBC as already closed because the PDF posted on 11 November.<\/li>\n
  • Hold 201-26 and 200-26 on their own lines.<\/strong> Dedicated 201-26 remains Attack, incident 10 November 2026, 1338 UTC, source Master: tanker struck by an unknown projectile 19 nautical miles northeast of Lima, Oman; crew safe; no environmental impact reported; damage assessment at first light; footer Lima Oman. Dedicated 200-26 remains Attack, incident 7 November 2026, 2020 UTC, source Company Security Officer, time-late: tanker struck by an unknown projectile while transiting outbound through the Strait of Hormuz; crew safe and accounted for; no reported environmental impact; footer Strait of Hormuz. One Wednesday morning Attack, one Sunday Attack and one Wednesday afternoon Suspicious Activity are three warnings. Do not merge Wednesday afternoon\u2019s incident into this morning\u2019s Lima projectile. Do not merge Wednesday afternoon\u2019s unknown crew line into this morning\u2019s crew-safe line. Do not treat 19 nautical miles northeast of Lima as 202-26\u2019s plot. Do not treat a shared Hormuz footer as proof that 202-26 is 200-26 filed twice.<\/li>\n
  • Do not collapse 199-26 \/ Navig8 Macallister, 195-26 \/ Grit, 197-26 \/ Vieila, 198-26 \/ Huda or 196-26 \/ Velos Sapphire onto this number.<\/strong> 199-26 remains Sunday morning\u2019s dedicated tanker fire 8 nautical miles northwest of Khasab, crew evacuated, military authorities, later reclassified to Attack on Update 001 as wrap; this morning\u2019s companion IMO 133-count names NAVIG8 MACALLISTER against that Khasab clock, unused as a 202-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; IMO Grit, IMO 9243150, remains wrap on that 3 November row. 197-26 remains Friday night\u2019s dedicated Master Attack on a tanker 16 nautical miles east of Khasab, explosion at the waterline port side, crew safe, under own power. 198-26 remains Saturday night\u2019s dedicated Advisory on a bulk carrier and military forces 18 nautical miles east of Khor Fakkan; Tuesday morning\u2019s dedicated IMO 131-count remains the Huda conversion. 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; Friday afternoon\u2019s dedicated IMO 25-fatality conversion remains Velos Sapphire on that Qatar sheet. A Strait of Hormuz Suspicious Activity with unknown status is not an 8-nautical-mile northwest-of-Khasab fire, and it is not a 19-nautical-mile northeast-of-Lima projectile. Five products are five products. An 11 November Hormuz tanker is a sixth overnight file. Do not make them one hull.<\/li>\n
  • Do not promote an Iranian mine claim, an ADNOC WAM statement, or an 11 November IMO row onto this PDF.<\/strong> Iran\u2019s army \/ IRGC Navy mine-and-fire statements remain colour, unused as a 202-26 method. 202-26 prints incident involving a tanker and does not print mine, fire, prohibited area or IRGC. ADNOC Logistics & Services, via WAM, remains unused as dedicated: unpublished hull, UAE territorial water, afternoon of 10 November, response operations ongoing. Do not collapse it onto this Strait of Hormuz footer. This morning\u2019s companion IMO board, as at 10 November, prints 133 confirmed \/ 25 dead with NAVIG8 MACALLISTER as the named top row and does not print an 11 November hull. IMO has not named 202-26. Update 112 remains ICOD 081300 UTC; this 11 November board sits after that cut-off. 016-26 remains the blockade document pack. No Update 113, no 203-26, no IMO 134 this run.<\/li>\n
  • Treat the missing hull, method and unknown-status line as open damage lines.<\/strong> The public tape prints tanker, Strait of Hormuz, incident, TBC, Military authorities, crew\/damage\/environmental status unknown. It does not print a hull, a cargo grade, a fire, a projectile, a mine, a survey result, a hole size, a NUC interval, a tug, own power, a next-port name or a class note. Keep Update 112 Hormuz SEVERE \/ Arabian Gulf SUBSTANTIAL and 016-26 visit-and-search in the master\u2019s pack. Sightings go to UKMTO, MSCIO, coastal authorities and the CSO. Watch a PDF revision that names a hull or prints a UTC clock, a method or a completed survey; a NAVAREA that plots this tanker rather than Grit or Navig8 Macallister; a flag or class note; a JMIC Update 113; or an IMO-board row on an 11 November hull \u2014 not a headline that 201-26 closed Wednesday\u2019s board or that an Iranian statement completed a naming.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Warning 202-26 against this morning\u2019s dedicated Warning 201-26 and against Sunday morning\u2019s dedicated Warning 200-26 so operators can treat Wednesday afternoon\u2019s tape as a numbered Suspicious Activity on a tanker in the Strait of Hormuz, not as a Lima-projectile rewrite, a 7 November outbound reprint, an Iranian mine naming, or a completed class survey.<\/p>\n","protected":false},"excerpt":{"rendered":"

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