The International Maritime Organization’s highlighted-incidents board, as at 10 November, now prints 133 confirmed incidents in the Strait of Hormuz and the wider Middle East, with 25 confirmed seafarer fatalities. Tuesday morning’s dedicated conversion on this desk sat at 131 as at 9 November, with 25 dead, and with Huda’s 7 November row 17 nautical miles from the coast of Oman as the named top line. The as-at date has moved. The confirmed-incident count has moved by two. The fatality line has not moved. What arrived on the public English page overnight is a later as-at stamp and one new named row at the top of the table. IMO now prints NAVIG8 MACALLISTER, IMO 9482873, dated 7 November, 8NM northwest of Khasab, Oman, damaged, no pollution. Wednesday morning is the first official IMO print of that hull.
The count is an IMO product. It is not a UKMTO warning, not a rewrite of Sunday morning’s dedicated Warning 199-26, not a rewrite of Sunday night’s dedicated Update 112, not a rewrite of Tuesday morning’s dedicated 131-count naming, and not a rewrite of this morning’s companion Warning 201-26. Dedicated 199-26 remains an unnamed tanker fire 8 nautical miles northwest of Khasab, crew evacuated; Update 001 later reclassified that product to Attack and printed 1920 UTC on 7 November, wrap, unused as a second dedicated Khasab fire piece. Update 112, ICOD 081300 UTC 8 November, still withholds 199-26, 197-26 and 200-26. UKMTO’s 199-26 PDF still prints an unnamed tanker, fire, evacuation, 8 nautical miles northwest of Khasab. Those are different instruments from IMO’s 133. Masters who brief Wednesday morning as Update 112 finally becoming an IMO table, as UKMTO finally printing that hull on the original PDF, as a 26th fatality, as a 10 November Lima conversion, or as a Hormuz reopen will have misread the sheet. Tuesday morning’s dedicated file on this desk correctly held the count at 131 as at 9 November. Wednesday morning’s board has added a named 133rd-count snapshot, has moved the as-at date to 10 November, and has printed one new named hull at the top. Log the move. Do not invent a second new hull to explain the +2.
What the 10 November board actually adds
Tuesday morning’s English page was 131 confirmed incidents, 25 dead, as at 9 November, with HUDA as the operational top row of that snapshot — damaged, no pollution — and with VIEILA, VELOS SAPPHIRE, GRIT, LARGO ATOM, SELAT STORM, AL MAYEDA, RITI, LOUISE 1, ARZANAH, GHANA PROSPERITY, LEONORA KOSAN, SOYIA, CHLOE (MIVERVA V), AL DASMA, JIF BARRACUDA, LOYALTY, ST3, GFS PRIDE, GFS GISELLE, AL SAADIYAT, DP WORLD KAVERI, KITION M, EVER VICT, AL MAQAM, ANGOLA PROSPERITY and PETRO DOLPHIN already on the sheet. Wednesday morning’s English page is 133 as at 10 November, 25 dead. The increment is two confirmed incidents. The as-at date has moved one day, from 9 November to 10 November. One new named row sits at the top of the table, above Tuesday’s Huda line. That arithmetic is a two-count move on a later as-at date with one new public name. Do not invent a second new name. Do not treat the extra increment as a silent conversion of this morning’s companion 201-26, Sunday morning’s dedicated 200-26, Friday night’s dedicated 197-26, Tuesday night’s dedicated 195-26, Tuesday night’s dedicated 194-26, Monday night’s dedicated 193-26, Sunday night’s dedicated 191-26, Tuesday afternoon’s dedicated Al Jusufi statements, AZINI or Quba. Those products remain unnamed on this board as new Wednesday rows. 201-26 is a 10 November Master Attack 19 nautical miles northeast of Lima; this table still has no 10 November row. Do not treat the +2 as a Contship Jet conversion. That hull does not belong on this Middle East table. One increment from the earlier 114-to-119 jump is still unnamed on this public sheet. The fatality line is still 25, on Velos Sapphire, not on this new row.
The new row is NAVIG8 MACALLISTER, IMO 9482873, 7 November, 8NM northwest of Khasab, Oman, damaged, no pollution. Sunday morning’s dedicated Warning 199-26 remains an unnamed tanker fire, first posted as Suspicious Activity, source Military authorities, location footer Khasab, Oman: UKMTO has received a time-late report of an incident 8 nautical miles northwest of Khasab; military authorities reported the tanker is on fire which has resulted in the evacuation of the crew. Update 001, filename 20261108-ukmto_warning-_199-26_update_001.pdf, later reclassified that incident to ATTACK and printed 1920 UTC on 7 November. IMO does not print 199-26, Suspicious Activity, Attack, “tanker,” “fire,” “evacuation,” “Military authorities,” “1920 UTC,” or a keep-clear radius. It prints Navig8 Macallister, 9482873, damaged, no pollution, 8 nautical miles northwest of Khasab, Oman, on a 7 November date. That is a tighter hull finding than the PDF, and it is the same offset wording as the PDF. It is also a different damage and pollution line from the original PDF, which printed fire and evacuation and did not print “damaged” or “no pollution.” The fatality total is still 25. This new row does not carry a casualty line. It is not a completed class survey. It is not a UKMTO PDF revision. It is not an Update 112 rewrite. Official wording keeps NAVIG8 MACALLISTER.
Hold the nearby Oman-coast plots. HUDA remains 7 November, IMO 9197088, 17NM from the coast of Oman, damaged, no pollution, on this same table — Tuesday morning’s dedicated 131st row, now the second row. Eight nautical miles northwest of Khasab is not 17 nautical miles from the coast of Oman. Do not promote Huda onto the new Navig8 Macallister row. Do not promote a 17-nautical-mile Oman-coast offset, a Damaged/no-pollution line from Huda, or IMO 9197088 onto Sunday morning’s dedicated 199-26. Tuesday morning’s dedicated file already held Huda on 198-26’s Oman-coast clock. Wednesday morning’s IMO print does not collapse that split. VIEILA remains 5 November, IMO 9234654, 16NM east of Khasab, Oman, damaged, no pollution. LOUISE 1 remains 29 October, IMO 9290323, 25NM Northeast of Khasab, Oman, damaged, no pollution. GRIT remains 3 November, IMO 9243150, 14NM northeast of Lima, Oman, damaged, no pollution. Those earlier Oman-coast and Lima rows are still on the sheet. They are not this 7 November northwest-of-Khasab hull.
Hold the clocks. UKMTO dates 199-26’s original product to a time-late 8 November posting against a 7 November fire; Update 001 prints 1920 UTC on 7 November. IMO dates the Navig8 Macallister row to 7 November without a time. Update 112, ICOD 081300 UTC 8 November, still withheld 199-26. The IMO as-at date is now 10 November. Those are separate official instruments, not one collapsed Attack. Do not invent which UKMTO number is the 7 November Navig8 Macallister row as a PDF fact. The 199-26 PDF has not been revised this morning to print the hull. Do not collapse Navig8 Macallister, Huda, Vieila, Velos Sapphire, Grit, Largo Atom and Selat Storm into one early-November Attack because all seven now sit near the top of the sheet. Navig8 Macallister is Wednesday morning’s first official IMO print. Huda remains Tuesday morning’s dedicated 131-count print. Vieila remains Monday midday’s dedicated 130-count print. Velos Sapphire remains Thursday night’s dedicated 129-count print, converted Friday afternoon to a fatality. Grit remains the dedicated 195-26 wrap on this table. Largo Atom, Selat Storm and Arzanah remain Wednesday morning’s dedicated 128-count prints.
Industry and open-register reprints of the same 7 November Khasab clock often restated a Singapore-flagged oil-products tanker, IMO 9482873, MMSI 563257100, call sign 9VCX4, and Clearwater later named NAVIG8 MACALLISTER against CW Alert 010-(Nov 26). Hold that colour separately. IMO prints NAVIG8 MACALLISTER and IMO 9482873. It does not print a flag. It does not print “oil products tanker.” It does not print an MMSI, a call sign, a fire, or an evacuation. Do not tidy the board into a Clearwater or open-register press line. Do not promote a sinking line, a spill line, an IRGC attribution, a cargo grade or a flag onto this row. IMO printed damaged and no pollution. It did not print sunk, abandoned, NUC, tow, a pollution volume, a seafarer casualty or an attacker.
The rest of Tuesday morning’s sheet is still there. HUDA remains 7 November, IMO 9197088, 17NM from the coast of Oman, damaged, no pollution. VIEILA remains 5 November, IMO 9234654, 16NM east of Khasab, Oman, damaged, no pollution. VELOS SAPPHIRE remains 4 November, IMO 9321201, 50NM north of Madinat ash Shamal, Qatar, damaged, no pollution, one seafarer fatality. GRIT remains 3 November, IMO 9243150, 14NM northeast of Lima, Oman, damaged, no pollution. LARGO ATOM remains 1 November, IMO 1034747, 72NM East of Ras Al Khafji, Saudi Arabia, damaged, no pollution. SELAT STORM remains 1 November, IMO 9266657, Strait of Hormuz, damaged, pollution unknown. ARZANAH remains 28 October, IMO 9928023, Strait of Hormuz, damaged, no pollution. LOUISE 1 remains 29 October, IMO 9290323, 25NM Northeast of Khasab, Oman, damaged, no pollution. PETRO DOLPHIN remains two seafarers missing at Sohar Anchorage. EL GAIA remains two seafarers missing. MINOAN PIONEER remains one seafarer missing. None of those rows is the Wednesday morning move. The move is the confirmed-incident count from 131 to 133, the as-at date from 9 November to 10 November, and the new Navig8 Macallister top row. The fatality line is unchanged at 25.
The naming is an IMO print, not a 199-26 PDF naming
Warning 199-26 remains an unnamed PDF. The working primary on that dedicated Sunday-morning file is still: first posted as SUSPICIOUS ACTIVITY, time-late, source Military authorities, tanker on fire 8 nautical miles northwest of Khasab, Oman, crew evacuated, location footer Khasab, Oman. Update 001 later reclassified the incident to ATTACK and printed 1920 UTC on 7 November, filename 20261108-ukmto_warning-_199-26_update_001.pdf. UKMTO printed neither a ship name, an IMO number, a flag, a cargo, an attacker, a projectile, a mine, a small-boat device, a NUC or tow line, an anchorage, a damaged line, a no-pollution line nor a latitude/longitude beyond the 8-nautical-mile northwest-of-Khasab offset. Wednesday morning’s IMO row does not revise that PDF. A DPA who briefs Wednesday morning as “UKMTO has now named 199-26” has over-read a highlighted-incidents table that does not print a warning number.
Sunday night’s companion Update 112, retrieved from jmic_advisory_update_112_08-nov.pdf, ICOD 081300 UTC 8 November, remains wrap on dedicated 199-26 as a withheld line: 199-26 remains Name withheld UFN, tanker, Incident (not Attack on that JMIC table), 8 NM NW Khasab, fire, crew evacuated. Update 112 does not print Navig8 Macallister. It does not print IMO 9482873. It does not print “damaged, no pollution.” Update 113 was not retrieved this run. IMO’s sheet is tighter on the IMO number, the hull and the damaged/no-pollution lines, and thinner on the method. It prints neither fire nor evacuation. Hold the official lines separately. A DPA who briefs IMO’s “damaged, no pollution” as a UKMTO revision of 199-26 will over-read the PDF. The PDF has not been revised this morning to print the hull. A DPA who briefs Update 112 as having printed IMO 9482873, or as having printed Navig8 Macallister, will over-read a JMIC table that still withheld that tanker.
Clearwater’s later confirmation that the vessel involved was the Singapore-flagged oil-products tanker NAVIG8 MACALLISTER (IMO 9482873) remains colour on dedicated 199-26, unused as a completed PDF naming and unused as an IMO flag print. That colour sits behind the same 8-nautical-mile northwest-of-Khasab 7 November clock. It is not an IMO flag print. It is not an IMO method print. IMO printed Navig8 Macallister, 9482873, 8 NM northwest of Khasab, damaged, no pollution. It did not print Singapore, oil products tanker, fire, evacuation or 1920 UTC. Do not promote those Clearwater extras onto this row. Distinct from dedicated Huda on this same table, 7 November, IMO 9197088, 17NM from the coast of Oman. Distinct from dedicated 200-26, Sunday morning’s unnamed outbound Hormuz projectile, 2020 UTC 7 November. Distinct from this morning’s companion 201-26, a Master Attack, unnamed tanker, unknown projectile, 19 nautical miles northeast of Lima, 1338 UTC 10 November. Do not fold Navig8 Macallister onto those later tanker clocks because the IMO date is also 7 November, and do not fold it onto a 10 November Lima clock the table does not print.
The 131-to-133 conversion is the briefing fact. Tuesday morning’s dedicated 131-count file printed 131 confirmed / 25 dead as at 9 November, with Huda as the named top row. Wednesday morning’s board prints 133 confirmed / 25 dead as at 10 November, with Navig8 Macallister as the named top row and Huda as the second row. The as-at date moved. The fatality line did not move. The public table added one named hull. The confirmed-incident count added two. A war-risk file that still treats IMO’s public sheet as 131 with Huda on top, as at 9 November, has under-read the current table. A master’s pack that treats 199-26’s unnamed tanker as now closed because IMO said Navig8 Macallister has collapsed two instruments. Tuesday morning’s dedicated file was right to refuse a 132nd incident from a board that had not added one. Wednesday morning’s dedicated file is the conversion, not a restatement of that refusal, and not a licence to invent a second named Wednesday hull.
What this is not
This is not Warning 199-26. Sunday morning’s dedicated UKMTO warning remains an unnamed military-authorities report, tanker on fire, 8 nautical miles northwest of Khasab, crew evacuated, later reclassified to Attack on Update 001 with a 1920 UTC stamp. IMO has taken a 7 November date, the hull, the IMO number, the same 8-nautical-mile northwest-of-Khasab offset and the damaged/no-pollution lines. It has not revised the PDF. Sunday night’s companion Update 112 remains a withheld 199-26 line, wrap, not a PDF naming.
This is not a 26th fatality, and it is not a Velos Sapphire rewrite. The fatality line is still 25, on Velos Sapphire, 4 November, 50NM north of Madinat ash Shamal, Qatar, damaged, no pollution, one seafarer fatality. Navig8 Macallister’s row prints no casualty. Do not convert Damaged. No pollution. into a death. Do not convert 199-26’s evacuation into a fatality. Do not brief Wednesday morning as “IMO has now moved the fatality off Velos Sapphire.” PETRO DOLPHIN remains two seafarers missing at Sohar Anchorage. EL GAIA remains two seafarers missing. MINOAN PIONEER remains one seafarer missing. Those earlier missing lines did not move the fatality count this morning.
This is not Update 112, and it is not Update 113. Sunday night’s dedicated JMIC note remains Update 112 to the advisory, 1 March–8 November 2026, ICOD 081300 UTC, JMIC# 001 26, regional threat SEVERE, 177 incidents since 1 March, five counted since last report including 199-26 as Name withheld UFN, tanker, fire, 8 NM NW Khasab, crew evacuated. That note still withheld 199-26’s hull. It did not print IMO 9482873. It did not print Navig8 Macallister. It did not print damaged, no pollution. No Update 113 was retrieved this run. Do not promote IMO’s 133rd-count snapshot onto Update 112 as a completed JMIC reprint. Do not invent an ICOD move that the JMIC PDF has not printed.
This is not 201-26, 200-26 or 197-26. This morning’s companion 201-26 remains an unnamed tanker Attack, unknown projectile, 19 NM northeast of Lima, 1338 UTC 10 November, crew safe, no environmental impact, first-light damage assessment. Sunday morning’s dedicated 200-26 remains an unnamed tanker Attack, unknown projectile, outbound Hormuz, 2020 UTC 7 November, crew safe, no environmental impact on the PDF. Friday night’s dedicated 197-26 remains an unnamed tanker Attack, waterline explosion port side, 16 NM east of Khasab, 2200 UTC 5 November, crew safe, own power; Monday midday’s dedicated 130-count remains the first IMO print of Vieila against that 5 November Khasab offset. IMO has not named 201-26, 200-26 or 197-26 as new Wednesday rows. A DPA who briefs Wednesday morning as “IMO has now named the outbound Hormuz projectile” or as “IMO has now named the 10 November Lima tanker” has invented a row the sheet does not print. A 7 November date on Navig8 Macallister is not a 200-26 conversion and not a 201-26 conversion. The extra +1 on the confirmed-incident count is not a licence to invent those namings.
This is not Huda, and it is not a 7 November Oman-coast rewrite. Dedicated Huda remains 7 November, IMO 9197088, 17NM from the coast of Oman, damaged, no pollution — Tuesday morning’s 131st row, still the second row this morning. Navig8 Macallister remains 7 November, IMO 9482873, 8NM northwest of Khasab, damaged, no pollution. The same calendar date and a different offset wording still separate those lines. Do not brief Wednesday morning as Huda reprinted. Official wording still keeps HUDA on that earlier row. Do not tidy NAVIG8 MACALLISTER into a house-style contraction on the official line.
This is not 195-26 / Grit, 194-26, 193-26, 192-26, 191-26, 425/26 or Al Jusufi. Tuesday night’s dedicated 195-26 remains an unnamed tanker, two unknown projectiles into the engine room, 14 NM northeast of Lima, no casualties printed on that PDF; IMO Grit remains wrap on that 3 November Lima row. Tuesday night’s dedicated 194-26 remains an Indian-crewed dhow Attack outbound through Hormuz; Tuesday afternoon’s dedicated Indian statements remain the Al Jusufi national-statement primary. Monday night’s dedicated 193-26 remains an unnamed vessel, hole starboard, 9 NM northeast of Lima. Wednesday morning’s dedicated 128-count remains the first IMO print of Largo Atom and Selat Storm. Sunday night’s dedicated 191-26 remains an unnamed Mayday-relay Attack. Sunday night’s dedicated 425/26 remains tug Selat Storm sunk 0.6 NM west of Jazirat Um Al Ghanam. IMO’s new Wednesday row is printed against Navig8 Macallister, not against those files. India’s dedicated Al Jusufi fatality remains a national-statement death on a different clock and a different hull; it is still not a new IMO row this morning, and it is not the 25th line on this sheet.
This is not last night’s dedicated NAVAREA IX 435/26, not last night’s dedicated Irakleio 1441/26, and not this morning’s companion Warning 201-26. 435/26 remains the second Fujairah SKATE 3D geotechnical box through 20 November. 1441/26 remains the unauthorised FA76-1127-26 void on the Abeille Marengo cable-research file. 201-26 is this morning’s other dedicated file: a Master Attack on a tanker 19 nautical miles northeast of Lima. None of those products belongs on this Middle East highlighted-incidents table. Official English 829/26, 828/26 and 820/26 remain unused as dedicated. Official Cyprus 345/26, NAVAREA III 0172/26 and NAVAREA IX 433/26 remain unused as dedicated. UKMTO now ends at this morning’s dedicated 201-26 on the Attack line, dedicated 199-26 on the original Suspicious Activity line, and dedicated 198-26 on the Advisory line. NAVAREA IX now lists dedicated 435/26 as the first row atop dedicated 434/26. No UKMTO 202-26, no Update 113, no IMO 134, no ARN 169, no 436/26 and no official NAVWARN 830 this run.
Operational implications
For a master still holding a Khasab northwest offset, a Musandam coastal passage, or a war-risk file opened against Sunday morning’s unnamed 199-26 PDF, Wednesday morning is a hull-naming problem before it is a new-attack problem. IMO has moved the confirmed-incident count to 133. It has named Navig8 Macallister, IMO 9482873, 7 November, 8 nautical miles northwest of Khasab, Oman, damaged, no pollution, with an as-at date now of 10 November. Charterers and underwriters who copied Tuesday morning’s “131 confirmed, Huda on top, as at 9 November, do not invent a 132nd row” language into Wednesday’s pack now have an official naming on a new hull and a later as-at stamp. That is not a licence to treat 199-26 as closed. The PDF still withholds the name. Update 112 still withheld 199-26. IMO now prints Navig8 Macallister, 9482873, 8 NM northwest of Khasab, damaged, no pollution. Carry all three lines. Do not brief a single “hull: Navig8 Macallister on 199-26.” Do not brief a single “hull: unnamed.” Write the instrument next to the finding.
The ISM and war-risk split is the operational content a DPA has to get right. Tuesday morning’s dedicated file told operators not to convert the 131-count into a 132nd incident because the table had not done so, and not to treat 199-26’s unnamed fire as an IMO row. Wednesday morning’s table has done the IMO conversion on that Khasab offset. A safety-management report that still says “IMO: 131 confirmed, top row Huda, as at 9 November” is stale against the current sheet. A safety-management report that says “UKMTO 199-26: Navig8 Macallister, IMO 9482873, damaged, no pollution” is over-read against a PDF that still withholds the hull, still prints fire and evacuation, and still prints neither damaged nor no pollution. Notify the CSO, the P&I correspondent and the war-risk underwriter that IMO’s public highlighted-incidents board as at 10 November now reads 133 confirmed / 25 dead and that the new top row is NAVIG8 MACALLISTER, IMO 9482873, 7 November, 8NM northwest of Khasab, Oman, damaged, no pollution. Keep 199-26 on the unnamed-PDF sheet. Keep Update 112 on the withheld-199-26 sheet. Keep Update 001 on the Attack / 1920 UTC reclassification sheet. Do not merge the four into one closed casualty file without a PDF revision, a later JMIC update, or a flag-state statement this desk has not retrieved. Do not write a Singapore flag, an oil-products class or a Clearwater confirmation onto the IMO row because industry colour named that hull against the same offset. IMO printed NAVIG8 MACALLISTER, 9482873, damaged, no pollution.
The unnamed remainder is unchanged and still matters. 201-26, 200-26, 197-26, 195-26, 194-26, 193-26 and 191-26 are still unnamed on this board as new rows. Al Jusufi is still a national-statement hull, not a new IMO row. AZINI and Quba are still unnamed here. A 114-to-119 increment is still unnamed. The extra +1 on this morning’s 131-to-133 move is still unnamed as a second public hull. PETRO DOLPHIN, EL GAIA and MINOAN PIONEER still carry missing lines that have not moved the 25. A DPA who treats Wednesday morning as “the board is now complete through 10 November” has ignored those gaps. A DPA who treats the 133rd-count snapshot as Sunday morning’s 200-26 projectile or as this morning’s 201-26 Lima tanker has borrowed a 7 November Khasab offset and dropped Navig8 Macallister’s 8-nautical-mile northwest-of-Khasab line. A DPA who treats the as-at move from 9 November to 10 November as two new confirmed named attacks has over-read a table that added one named row.
Keep the dedicated files on their own lines. Tuesday morning’s dedicated 131-count remains Huda, as at 9 November, 131 confirmed / 25 dead. Monday midday’s dedicated 130-count remains Vieila, as at 6 November, 130 confirmed / 25 dead. Friday afternoon’s dedicated 25-fatality conversion remains Velos Sapphire, as at 6 November, 129 confirmed / 25 dead. Sunday night’s dedicated Update 112 remains the JMIC 177-count / SEVERE note with 199-26 withheld. Sunday morning’s dedicated 199-26 remains the unnamed Khasab tanker fire; Update 001 remains wrap. Sunday morning’s dedicated 200-26 remains the unnamed outbound Hormuz projectile. This morning’s companion 201-26 remains the unnamed Lima tanker Attack. Last night’s dedicated 435/26 remains the second Fujairah SKATE 3D box. Last night’s dedicated 1441/26 remains the unauthorised Abeille Marengo NAVTEX void. Do not recast 11 November morning as a 199-26 PDF naming, as an Update 112 reprint, as a 26th fatality, as a 10 November Lima conversion, or as a completed 7 November tanker tape.
What Operators Should Note
- Log the current board as a 133rd-count snapshot and a first IMO print of Navig8 Macallister, not as a 199-26 PDF naming and not as a 26th fatality. Official IMO highlighted-incidents board as at 10 November 2026: 133 confirmed incidents, 25 confirmed seafarer fatalities. Tuesday morning’s dedicated snapshot was 131 / 25 as at 9 November, HUDA (IMO 9197088) on top. Wednesday morning’s new top row is NAVIG8 MACALLISTER (IMO 9482873), 7 November, 8NM northwest of Khasab, Oman, damaged, no pollution. Official wording keeps NAVIG8 MACALLISTER. The as-at date moved 9 November to 10 November. The confirmed-incident count moved by two. The public table added one named hull. The fatality line did not move. IMO still prints neither 199-26, fire, evacuation, 1920 UTC, Military authorities, a flag, a cargo nor an attacker.
- Keep 199-26, Update 001 and Update 112 on their own hull lines. Dedicated 199-26 remains a time-late tanker fire 8 NM northwest of Khasab, crew evacuated, source Military authorities, first posted as Suspicious Activity. Update 001 remains wrap: reclassified to ATTACK, 1920 UTC 7 November, filename
20261108-ukmto_warning-_199-26_update_001.pdf. Dedicated Update 112 remains ICOD 081300 UTC 8 November, 199-26 Name withheld UFN, tanker, fire, 8 NM NW Khasab, crew evacuated. No Update 113 this run. Do not brief UKMTO as having named the hull. Do not brief JMIC as having printed IMO 9482873 or Navig8 Macallister. Write IMO: NAVIG8 MACALLISTER, 9482873, damaged, no pollution, 8 NM northwest of Khasab. Write UKMTO: unnamed tanker, fire, crew evacuated, 8 NM northwest of Khasab. Write JMIC: Name withheld UFN on that fire line. - Do not invent a second Wednesday hull to explain the 133, and do not collapse Navig8 Macallister onto 200-26 or 201-26. 201-26, 200-26, 197-26, 195-26, 194-26, 193-26, 191-26, Al Jusufi, Quba and AZINI remain unnamed as new rows on this sheet. Do not promote a sinking, a spill, IRGC, a flag or a cargo onto the IMO row. IMO printed damaged and no pollution. PETRO DOLPHIN remains two missing at Sohar. EL GAIA remains two missing. MINOAN PIONEER remains one missing. Those missing lines did not move the 25 this morning. One 114-to-119 increment is still unnamed. The as-at move to 10 November added one named row, not two 7–10 November tanker conversions, and not this morning’s 19-nautical-mile northeast-of-Lima Attack.
- Hold Huda, Vieila, Velos Sapphire, Grit and the rest of the top of the sheet on their own dedicated files. Huda remains 7 November, IMO 9197088, 17NM from the coast of Oman, damaged, no pollution — Tuesday morning’s 131st row, still the second row, not this 8-nautical-mile northwest-of-Khasab line. Vieila remains 5 November, IMO 9234654, 16NM east of Khasab, damaged, no pollution — Monday midday’s 130th row. Velos Sapphire remains 4 November, IMO 9321201, 50NM north of Madinat ash Shamal, damaged, no pollution, one seafarer fatality — still the 25th death, not displaced by this naming. Grit remains 3 November, IMO 9243150, 14NM northeast of Lima, damaged, no pollution — wrap on dedicated 195-26, not this Khasab fire. Largo Atom, Selat Storm and Arzanah remain last week’s dedicated 128-count prints. Louise 1 remains 29 October, IMO 9290323, 25NM Northeast of Khasab, damaged, no pollution. Do not fold those namings into one 7 November Attack because the count moved.
- Update the war-risk and ISM pack against Tuesday morning’s “do not invent a 132nd row” instruction. Tuesday morning’s dedicated 131-count file correctly held the count at 131 as at 9 November. Wednesday morning’s board is the conversion. A file that still says 131 confirmed / Huda on top / as at 9 November is stale. A file that says 199-26 named Navig8 Macallister, IMO 9482873, damaged, no pollution is over-read. Notify the CSO, P&I and war-risk underwriter of the 10 November as-at date, the 133, the unchanged 25, the one new named hull, and the Navig8 Macallister wording. Keep the unnamed PDF, the Update 001 Attack reclassification, and the JMIC withheld row open until those products move.
- Keep the rest of Wednesday’s tape off this table. This morning’s companion 201-26 remains the unnamed Lima tanker Attack, 19 NM northeast of Lima, 1338 UTC 10 November, first-light damage assessment. Last night’s dedicated 435/26 remains the second Fujairah SKATE 3D box through 20 November. Last night’s dedicated 1441/26 remains the unauthorised Abeille Marengo NAVTEX void. Dedicated 200-26 remains the outbound Hormuz projectile. Dedicated 199-26 remains the Khasab tanker fire. Dedicated 198-26 remains the Khor Fakkan bulk carrier. Dedicated 197-26 remains the Khasab waterline explosion. JMIC remains dedicated Update 112. UKMTO now ends at 201-26. Official English 829/26, 828/26 and 820/26 remain unused as dedicated. Official Cyprus 345/26, NAVAREA III 0172/26 and NAVAREA IX 433/26 remain unused as dedicated. No 202-26, no Update 113, no IMO 134, no ARN 169, no 436/26 and no official NAVWARN 830 this run. Watch a later IMO sheet that moves the 133, moves the 25, names 201-26 / 200-26 / 197-26 / 195-26 / 194-26 / Al Jusufi, or prints a second new named hull — not a 199-26 PDF revision and not an Update 112 reprint.
Regulas Shipping will keep lining Wednesday morning’s IMO board as at 10 November — 133 confirmed, 25 dead, Navig8 Macallister now the named top row — against Sunday morning’s unnamed 199-26 PDF and against Sunday night’s Update 112 withheld fire line so operators can treat the 133rd-count snapshot as an IMO naming on a new hull, not as a UKMTO naming, a JMIC reprint, a 10 November Lima conversion, or a 26th fatality.
