The International Maritime Organization’s highlighted-incidents board, as at 6 November, now prints 130 confirmed incidents in the Strait of Hormuz and the wider Middle East, with 25 confirmed seafarer fatalities. Friday afternoon’s dedicated fatality conversion on this desk sat at 129 as at 6 November, with 25 dead, and with Velos Sapphire’s 4 November row 50 nautical miles north of Madinat ash Shamal carrying “one seafarer fatality.” The as-at date has not moved. The fatality line has not moved. What moved is the confirmed-incident count by one, and one new named row at the top of the table. IMO now prints VIEILA, IMO 9234654, dated 5 November, 16 nautical miles east of Khasab, Oman, damaged, no pollution. Monday midday 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 Friday night’s dedicated Warning 197-26, not a rewrite of Friday afternoon’s dedicated 25-fatality conversion, not a rewrite of Thursday night’s dedicated 129-count naming, and not a rewrite of Sunday night’s dedicated Update 112. Update 112, ICOD 081300 UTC 8 November, still withholds 197-26 as Name withheld UFN and does not print Vieila. UKMTO’s 197-26 PDF still prints an unnamed tanker, a waterline explosion on the port side, crew safe, and own power. Those are different instruments from IMO’s 130. Masters who brief Monday midday as Update 112 finally printing Vieila, as UKMTO finally printing that hull on the original PDF, as a 26th fatality, or as a Hormuz reopen will have misread the table. Friday afternoon’s dedicated file on this desk correctly held the count at 129. Monday midday’s board has added a 130th named row. Log the move. Do not invent a second new hull to explain it.
What the 6 November board actually adds
Friday afternoon’s English page was 129 confirmed incidents, 25 dead, as at 6 November, with VELOS SAPPHIRE as the operational top row of that snapshot — damaged, no pollution, one seafarer fatality — and with LARGO ATOM, SELAT STORM, ARZANAH, AL MAYEDA, RITI, LOUISE 1, 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. Monday midday’s English page is 130 as at 6 November, 25 dead. The increment is one confirmed incident. One new named row sits at the top of the table, above Friday’s Velos Sapphire line. That arithmetic is a single-row move on the same as-at date. Do not invent a second new name. Do not treat the +1 as a silent conversion of Sunday morning’s dedicated 199-26, Sunday morning’s dedicated 200-26, Saturday night’s dedicated 198-26, Sunday night’s dedicated Update 112 Huda naming, 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 Monday rows. Do not treat the +1 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 VIEILA, IMO 9234654, 5 November, 16NM east of Khasab, Oman, damaged, no pollution. Friday night’s dedicated Warning 197-26 remains an unnamed tanker Attack, 2200 UTC 5 November, source Master, location footer Khasab, Oman: UKMTO has received a time-late report of an incident 16 nautical miles east of Khasab; the Master of a tanker transiting the Strait of Hormuz outbound has reported an explosion at the waterline, port side; the crew are safe and are accounted for; the tanker is still under its own power and is continuing on its voyage. Official MSCIO alerts index showed no numbered wrap against that 2200 UTC Khasab clock when 197-26 first printed. Sunday night’s companion Update 112 reprints 197-26 as Name withheld UFN, tanker, Attack, waterline explosion port side, 16 NM east of Khasab, crew safe, continued voyage. IMO does not print 197-26, 2200 UTC, “explosion at the waterline,” “port side,” a Master line, a crew-safe line or an own-power line. It prints Vieila, 9234654, damaged, no pollution, 16 nautical miles east of Khasab, Oman, on a 5 November date. That is a tighter hull finding than the PDF, and it matches the PDF’s 16-nautical-mile east-of-Khasab offset. It is also a different damage and pollution line from the PDF, which printed neither “damaged” nor “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 naming.
Hold the nearby Khasab plots. LOUISE 1 remains 29 October, IMO 9290323, 25NM Northeast of Khasab, Oman, damaged, no pollution, on this same table. Sixteen nautical miles east is not 25 nautical miles northeast. Do not promote Louise 1 onto the new Vieila row. Do not promote a 29 October clock, a Damaged/no-pollution line from Louise 1, or IMO 9290323 onto Friday night’s dedicated 197-26. Friday night’s dedicated file already held that split. Monday midday’s IMO print does not collapse it. CAPE DAO remains 23 September, IMO 9219020, 15 NM northeast of Khasab, damaged, no pollution, one seafarer fatality, sunk. SIDR remains 31 August, IMO 9854715, 17NM east of Khasab, damaged, no pollution, two seafarer fatalities. Those earlier east-of-Khasab rows are still on the sheet. They are not this 5 November hull.
Hold the clocks. UKMTO dates 197-26 to 5 November 2200 UTC. IMO dates the Vieila row to 5 November without a time. Update 112, ICOD 081300 UTC 8 November, reprints 197-26 as unnamed. The IMO as-at date is still 6 November. Those are separate official instruments, not one collapsed Attack. Do not invent which UKMTO number is the 5 November Vieila row as a PDF fact. The 197-26 PDF has not been revised this morning. Do not collapse Vieila, Velos Sapphire, Largo Atom, Selat Storm and Arzanah into one late-October-to-early-November Attack because all five now sit near the top of the sheet. Vieila is Monday midday’s first official IMO print. Velos Sapphire remains Thursday night’s dedicated 129-count print, converted Friday afternoon to a fatality. Largo Atom, Selat Storm and Arzanah remain Wednesday morning’s dedicated 128-count prints.
Official wording keeps VIEILA. Industry and open-register reprints often print VIEIRA against IMO 9234654. Hold that spelling split as colour, not as a board fact. IMO prints VIEILA. Do not tidy the board into Vieira. 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 Friday afternoon’s sheet is still there. VELOS SAPPHIRE remains 4 November, IMO 9321201, 50NM north of Madinat ash Shamal, Qatar, damaged, no pollution, one seafarer fatality. 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. AL MAYEDA remains 30 October, IMO 9397298, 40NM South of Lavan Island, Iran, damaged, no pollution. RITI remains 29 October, IMO 9249075, Strait of Hormuz, damaged, no pollution. LOUISE 1 remains 29 October, IMO 9290323, 25NM Northeast of Khasab, Oman, damaged, no pollution. GHANA PROSPERITY remains 23 October, IMO 9732541, Strait of Hormuz, damaged, no pollution, with the 3 October Strait row for the same IMO number still lower on the board. 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 Monday midday move. The move is the confirmed-incident count from 129 to 130 and the new Vieila top row. The as-at date is unchanged at 6 November. The fatality line is unchanged at 25.
The naming is an IMO print, not a 197-26 PDF naming
Warning 197-26 remains an unnamed PDF. The working primary on that dedicated Friday-night file is still: ATTACK, 5 November 2026, 2200 UTC, source Master, tanker, explosion at the waterline, port side, 16 nautical miles east of Khasab, Oman, crew safe and accounted for, tanker still under its own power and continuing on its voyage, location footer Khasab, Oman, filename 20261106-ukmto_warning-197-26.pdf. UKMTO printed neither a ship name, an IMO number, a flag, a cargo, an attacker, a NUC or tow line, an anchorage, a damaged line, a no-pollution line nor a latitude/longitude beyond the 16-nautical-mile east-of-Khasab offset. Monday midday’s IMO row does not revise that PDF. A DPA who briefs Monday midday as “UKMTO has now named 197-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 197-26: Name withheld UFN, tanker, Attack, waterline explosion port side, 16 NM east of Khasab, crew safe, continued voyage, also MSCIO 171/26 wrap. Update 112 does not print Vieila. Update 113 was not retrieved this run. IMO’s sheet is tighter on the hull, the IMO number and the damaged/no-pollution lines and thinner on the method. It prints “16NM east of Khasab, Oman,” “damaged” and “no pollution,” not “explosion at the waterline,” not “port side,” not “Master,” and not “crew safe.” Hold the official lines separately. A DPA who briefs IMO’s “damaged, no pollution” as a UKMTO revision of 197-26 will over-read the PDF. The PDF has not been revised this morning. A DPA who briefs Update 112 as having named Vieila will over-read a table that still reads Name withheld UFN.
Industry colour of the same 5 November clock, held separately: open-register reprints often print VIEIRA against IMO 9234654, crude oil tanker, about 333 m, on the order of 161,500 gt / 307,000 dwt. Flag lines on those reprints split and are not used here. Those extras are not an IMO flag, cargo or owner print. IMO prints Vieila, 9234654, damaged, no pollution. It does not print a flag, a cargo grade, a deadweight or an owner. Do not promote a company-fleet colour line onto this row. Do not promote a sinking colour line, a spill colour line or an IRGC colour line onto this row. IMO printed no pollution. Distinct from dedicated Louise 1 on this same table, 29 October, IMO 9290323, 25NM Northeast of Khasab. Distinct from dedicated 199-26, Sunday morning’s unnamed tanker fire, 8 NM northwest of Khasab. Distinct from dedicated 200-26, Sunday morning’s unnamed outbound Hormuz projectile, 2020 UTC 7 November. Do not fold Vieila onto those later 7 November clocks.
The 129-to-130 conversion is the briefing fact. Friday afternoon’s dedicated 25-fatality file printed 129 confirmed / 25 dead as at 6 November, with Velos Sapphire as the named top row. Monday midday’s board prints 130 confirmed / 25 dead as at 6 November, with Vieila as the named top row and Velos Sapphire as the second row. The as-at date did not move. The fatality line did not move. A war-risk file that still treats IMO’s public sheet as 129 with Velos Sapphire on top has under-read the current table. A master’s pack that treats 197-26’s unnamed tanker as now closed because IMO said Vieila has collapsed two instruments. Friday afternoon’s dedicated file was right to refuse a 130th incident from a board that had not added one. Monday midday’s dedicated file is the conversion, not a restatement of that refusal.
What this is not
This is not Warning 197-26. Friday night’s dedicated UKMTO Attack remains an unnamed Master report, 2200 UTC 5 November, tanker, explosion at the waterline, port side, 16 nautical miles east of Khasab, crew safe, own power, continuing voyage. IMO has taken the offset, the date, the hull, the IMO number and the damaged/no-pollution lines. It has not revised the PDF. Sunday night’s companion Update 112 still withholds the hull.
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. Vieila’s row prints no casualty. Do not convert Damaged. No pollution. into a death. Do not brief Monday midday 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, printed correction that Update 110 should have read 166 not 167, five counted since last report including 197-26 as Name withheld UFN. That note named HUDA against dedicated 198-26 and still withheld Vieila. No Update 113 was retrieved this run. Do not promote IMO’s 130th incident onto Update 112. Do not invent an ICOD move that the JMIC PDF has not printed.
This is not 199-26, 200-26, 198-26 or Huda. Sunday morning’s dedicated 199-26 remains an unnamed tanker fire, Suspicious Activity, 8 NM northwest of Khasab. 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. Saturday night’s dedicated 198-26 remains an unnamed bulk carrier Advisory, 18 NM east of Khor Fakkan, TBC. Sunday night’s Update 112 remains the first JMIC naming of HUDA against that 198-26 clock, wrap, not a 198-26 PDF naming. IMO has not named 200-26, 199-26, 198-26 or Huda as new Monday rows. A DPA who briefs Monday midday as “IMO has now named the northwest-of-Khasab fire” or as “IMO has now named Huda” has invented a row the sheet does not print.
This is not 195-26, 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. 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 130th incident is printed against Vieila, 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 Louise 1, and it is not a 29 October Khasab rewrite. Dedicated Louise 1 remains 29 October, IMO 9290323, 25NM Northeast of Khasab, damaged, no pollution. Vieila remains 5 November, IMO 9234654, 16NM east of Khasab, damaged, no pollution. Nine nautical miles and seven days still separate those offsets. Do not brief Monday midday as Louise 1 reprinted.
This is not this morning’s dedicated coastal warning 527/26, and it is not this afternoon’s companion coastal warning 537/26. 527/26 remains the 9 November Sierra 733 submarine-ops box in the southern Gulf of Taranto. 537/26 is a 9–12 November Tango 833A gunfiring product off the Taranto harbour face. Neither product belongs on this Middle East highlighted-incidents table. Official English 814/26 remains wrap on dedicated 813/26. Official Cyprus 345/26, NAVAREA III 0170/26 and NAVAREA IX 433/26 remain unused as dedicated. Official HNHS 1355/26, dated 9 November, Agiokampos south breakwater head green light unlit at 39 40 39N 022 53 29E, remains unused as dedicated. UKMTO still ends at dedicated 200-26 on the Attack line, dedicated 199-26 on the Suspicious Activity line, and dedicated 198-26 on the Advisory line. NAVAREA IX still lists 433/26 as the in-force list. Dedicated 432/26 is now past 082359 UTC 8 November. No UKMTO 201-26, no Update 113, no IMO 131, no ARN 169, no 434/26 and no official NAVWARN 815 this run.
Operational implications
For a master still holding a Musandam / Khasab east offset, an outbound Hormuz passage, or a war-risk file opened against Friday night’s unnamed 197-26 PDF, Monday midday is a hull-naming problem before it is a new-attack problem. IMO has added a 130th confirmed incident. It has named Vieila, IMO 9234654, 5 November, 16 nautical miles east of Khasab, Oman, damaged, no pollution, with an as-at date still of 6 November. Charterers and underwriters who copied Friday afternoon’s “129 confirmed, Velos Sapphire on top, do not invent a 130th row” language into Monday’s pack now have an official naming on a new hull. That is not a licence to treat 197-26 as closed. The PDF still withholds the name. Update 112 still withholds the name. IMO now prints Vieila. Carry all three lines. Do not brief a single “hull: Vieila on 197-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. Friday afternoon’s dedicated file told operators not to convert the 129-count into a 130th incident because the table had not done so. Monday midday’s table has done so. A safety-management report that still says “IMO: 129 confirmed, top row Velos Sapphire” is stale against the current sheet. A safety-management report that says “UKMTO 197-26: Vieila” is over-read against a PDF that still withholds the hull. Notify the CSO, the P&I correspondent and the war-risk underwriter that IMO’s public highlighted-incidents board as at 6 November now reads 130 confirmed / 25 dead and that the new top row is VIEILA, IMO 9234654, 5 November, 16NM east of Khasab, Oman, damaged, no pollution. Keep 197-26 on the unnamed-PDF sheet. Keep Update 112 on the withheld-UFN sheet. Do not merge the three into one closed casualty file without a PDF revision, a JMIC update, or a flag-state statement this desk has not retrieved. Do not write Vieira onto the IMO line because open-register pages prefer that spelling. IMO printed VIEILA.
The unnamed remainder is unchanged and still matters. 200-26, 199-26, 198-26, Huda, 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. PETRO DOLPHIN, EL GAIA and MINOAN PIONEER still carry missing lines that have not moved the 25. A DPA who treats Monday midday as “the board is now complete through 8 November” has ignored those gaps. A DPA who treats the 130th incident as Sunday morning’s 199-26 fire or as Sunday morning’s 200-26 projectile has borrowed a 7 November clock and dropped Vieila’s 5 November Khasab offset.
Keep the dedicated files on their own lines. Friday afternoon’s dedicated 25-fatality conversion remains Velos Sapphire, as at 6 November, 129 confirmed / 25 dead. Thursday night’s dedicated 129-count remains the first IMO print of Velos Sapphire. Sunday night’s dedicated Update 112 remains the JMIC 177-count / SEVERE note with 197-26 withheld and Huda named against 198-26. Friday night’s dedicated 197-26 remains the unnamed Khasab tanker Attack. Sunday morning’s dedicated 199-26 and 200-26 remain unnamed PDFs. Saturday night’s dedicated 198-26 remains the unnamed Khor Fakkan bulk carrier. This morning’s dedicated 527/26 remains the Sierra 733 submarine-ops box. This afternoon’s companion 537/26 remains the Tango 833A gunfiring product. Do not recast 9 November midday as a 197-26 PDF naming, as an Update 112 hull, as a 26th fatality, or as a completed 5 November tape.
What Operators Should Note
- Log the current board as a 130th incident and a first IMO print of Vieila, not as a 197-26 PDF naming and not as a 26th fatality. Official IMO highlighted-incidents board as at 6 November 2026: 130 confirmed incidents, 25 confirmed seafarer fatalities. Friday afternoon’s dedicated snapshot was 129 / 25 as at 6 November, VELOS SAPPHIRE (IMO 9321201) on top. Monday midday’s new top row is VIEILA (IMO 9234654), 5 November, 16NM east of Khasab, Oman, damaged, no pollution. Official wording keeps VIEILA. The as-at date did not move. The fatality line did not move. IMO still prints neither 197-26, 2200 UTC, waterline explosion, port side, a Master line, a crew-safe line, own power, a flag, a cargo nor an attacker.
- Keep 197-26 and Update 112 on their own hull lines. Dedicated 197-26 remains ATTACK, 5 November 2026, 2200 UTC, source Master, tanker, explosion at the waterline, port side, 16 NM east of Khasab, Oman, crew safe, own power, continuing voyage, filename 20261106-ukmto_warning-197-26.pdf. Dedicated Update 112 remains ICOD 081300 UTC 8 November, 197-26 Name withheld UFN, tanker, Attack, waterline explosion port side, 16 NM east of Khasab, crew safe. No Update 113 this run. Do not brief UKMTO as having named the hull. Do not brief JMIC as having named Vieila. Write IMO: VIEILA, 9234654, damaged, no pollution. Write UKMTO: unnamed tanker. Write JMIC: withheld UFN.
- Do not invent a new Monday hull to explain the 130, and do not tidy VIEILA into Vieira. 200-26, 199-26, 198-26, Huda, 195-26, 194-26, 193-26, 191-26, Al Jusufi, Quba and AZINI remain unnamed as new rows on this sheet. Open-register reprints that print VIEIRA against IMO 9234654 stay colour. Do not promote a sinking, a spill, IRGC, a VLCC class line or a flag 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. Cameroon Prosperity is still printed 93151598; working number 9315159.
- Hold Louise 1, Velos Sapphire and the rest of the top of the sheet on their own dedicated files. Louise 1 remains 29 October, IMO 9290323, 25NM Northeast of Khasab, damaged, no pollution — 9 NM and seven days from Vieila, not this 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. Largo Atom, Selat Storm and Arzanah remain Wednesday morning’s dedicated 128-count prints. Do not fold those namings into one 5 November Attack because the count moved.
- Update the war-risk and ISM pack against Friday afternoon’s “do not invent a 130th row” instruction. Friday afternoon’s dedicated 25-fatality file correctly held the count at 129. Monday midday’s board is the conversion. A file that still says 129 confirmed / Velos Sapphire on top is stale. A file that says 197-26 named Vieila is over-read. Notify the CSO, P&I and war-risk underwriter of the unchanged 6 November as-at date, the 130, the unchanged 25, and the Vieila wording. Keep the unnamed PDF and the withheld JMIC row open until those products move.
- Keep the rest of Monday’s tape off this table. This morning’s dedicated 527/26 remains the Sierra 733 submarine-ops box through 092359Z tonight. This afternoon’s companion 537/26 remains Tango 833A gunfiring, 9–12 November split local-time windows. Dedicated 1404/26 remains ‘KOBI RUEGG’ through 112200 UTC 11 November. Dedicated 201/26 remains Zakynthos through 130830 UTC 13 November. Dedicated 199-26 remains the Khasab tanker fire. Dedicated 200-26 remains the outbound Hormuz projectile. Dedicated 198-26 remains the Khor Fakkan bulk carrier. JMIC remains dedicated Update 112. UKMTO still ends at 200-26. Official HNHS 1355/26, official Cyprus 345/26, NAVAREA III 0170/26 and NAVAREA IX 433/26 remain unused as dedicated. No 201-26, no Update 113, no IMO 131, no ARN 169, no 434/26 and no official NAVWARN 815 this run. Watch a later IMO sheet that moves the 130, moves the 25, names 200-26 / 199-26 / 198-26 / Huda / 195-26 / 194-26 / Al Jusufi, or prints a 131st row — not a 197-26 PDF revision and not an Update 112 naming.
Regulas Shipping will keep lining Monday midday’s IMO board as at 6 November — 130 confirmed, 25 dead, Vieila now the named top row — against Friday night’s unnamed 197-26 PDF and against Sunday night’s withheld Update 112 row so operators can treat the 130th incident as an IMO naming on a new hull, not as a UKMTO naming, a JMIC naming, or a 26th fatality.
