The International Maritime Organization\u2019s highlighted-incidents board, as at 11 November, now prints 134 confirmed incidents in the Strait of Hormuz and the wider Middle East, with 25 confirmed seafarer fatalities. Wednesday morning\u2019s dedicated conversion on this desk sat at 133 as at 10 November, with 25 dead, and with Navig8 Macallister\u2019s 7 November row 8 nautical miles northwest of Khasab, Oman, as the named top line. The as-at date has moved. The confirmed-incident count has moved by one. The fatality line has not moved. What arrived on the public English page this afternoon is a later as-at stamp and one new named row at the top of the table. IMO now prints TARIF, IMO 9828390, dated 7 November, Strait of Hormuz, damaged, no pollution. Wednesday night is the first official IMO print of that hull.<\/p>\n
The count is an IMO product. It is not a UKMTO warning, not a rewrite of Sunday morning\u2019s dedicated Warning 200-26, not a rewrite of Wednesday morning\u2019s dedicated 133-count naming, not a rewrite of this morning\u2019s dedicated Warning 202-26, and not a rewrite of this morning\u2019s companion Warning 201-26. Dedicated 200-26 remains an unnamed tanker Attack, unknown projectile, outbound Hormuz, 2020 UTC 7 November, crew safe, no environmental impact on the PDF. Update 112, ICOD 081300 UTC 8 November, still withholds 200-26, 197-26 and 199-26. UKMTO\u2019s 200-26 PDF still prints an unnamed tanker, outbound Strait of Hormuz, unknown projectile. Those are different instruments from IMO\u2019s 134. Masters who brief Wednesday night 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, as this morning\u2019s TBC Hormuz tanker converted, or as a Hormuz reopen will have misread the sheet. Wednesday morning\u2019s dedicated file on this desk correctly held the count at 133 as at 10 November. Wednesday night\u2019s board has added a named 134th-count snapshot, has moved the as-at date to 11 November, and has printed one new named hull at the top. Log the move. Do not invent a second new hull. The arithmetic tonight is cleaner than Wednesday morning\u2019s 131-to-133 jump: one new public name, one new confirmed-incident count.<\/p>\n
Wednesday morning\u2019s English page was 133 confirmed incidents, 25 dead, as at 10 November, with NAVIG8 MACALLISTER as the operational top row of that snapshot \u2014 damaged, no pollution \u2014 and with HUDA, 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 night\u2019s English page is 134 as at 11 November, 25 dead. The increment is one confirmed incident. The as-at date has moved one day, from 10 November to 11 November. One new named row sits at the top of the table, above Wednesday morning\u2019s Navig8 Macallister line. That arithmetic is a one-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\u2019s dedicated 202-26, this morning\u2019s dedicated 201-26, Sunday morning\u2019s dedicated 200-26, Friday night\u2019s dedicated 197-26, Tuesday night\u2019s dedicated 195-26, Tuesday night\u2019s dedicated 194-26, Monday night\u2019s dedicated 193-26, Sunday night\u2019s dedicated 191-26, Tuesday afternoon\u2019s dedicated Al Jusufi statements, AZINI or Quba. Those products remain unnamed on this board as new Wednesday-night rows. 202-26 is an 11 November military-authorities Suspicious Activity, unnamed tanker, Strait of Hormuz, incident date TBC, incident time TBC, crew, damage and environmental impact unknown; this table still has no 11 November row. 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 +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.<\/p>\n
The new row is TARIF, IMO 9828390, 7 November, Strait of Hormuz, damaged, no pollution. Sunday morning\u2019s dedicated Warning 200-26 remains an unnamed tanker Attack, source Company Security Officer, location footer Strait of Hormuz: UKMTO has received a time-late report of an incident in the Strait of Hormuz; the Company Security Officer of a tanker has reported that the vessel was struck by an unknown projectile while transiting outbound through the Strait of Hormuz; all crew are safe and accounted for and there is no reported environmental impact at this time. IMO does not print 200-26, Attack, \u201ctanker,\u201d \u201cunknown projectile,\u201d \u201coutbound,\u201d \u201cCompany Security Officer,\u201d \u201c2020 UTC,\u201d \u201ccrew safe,\u201d or a keep-clear radius. It prints Tarif, 9828390, damaged, no pollution, Strait of Hormuz, on a 7 November date. That is a tighter hull finding than the PDF, and it is the same waterway tag as the PDF footer. It is also a thinner method line than the PDF, which printed an unknown projectile on an outbound transit and did not print a hull. 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 TARIF.<\/p>\n
Hold the nearby 7 November plots. NAVIG8 MACALLISTER remains 7 November, IMO 9482873, 8NM northwest of Khasab, Oman, damaged, no pollution, on this same table \u2014 Wednesday morning\u2019s dedicated 133rd row, now the second row. Strait of Hormuz is not 8 nautical miles northwest of Khasab. Do not promote Navig8 Macallister onto the new Tarif row. Do not promote an 8-nautical-mile northwest-of-Khasab offset, a fire, an evacuation, or IMO 9482873 onto Sunday morning\u2019s dedicated 200-26. Wednesday morning\u2019s dedicated file already held Navig8 Macallister against 199-26\u2019s Khasab-fire clock. Wednesday night\u2019s IMO print does not collapse that split. 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. LOUISE 1 remains 29 October, IMO 9290323, 25NM Northeast of Khasab, Oman, damaged, no pollution. SELAT STORM remains 1 November, IMO 9266657, Strait of Hormuz, damaged, pollution unknown. RITI remains 29 October, IMO 9249075, Strait of Hormuz, damaged, no pollution. ARZANAH remains 28 October, IMO 9928023, Strait of Hormuz, damaged, no pollution. Those earlier Hormuz-tag and Oman-coast rows are still on the sheet. They are not this 7 November Tarif hull.<\/p>\n
Hold the clocks. UKMTO dates 200-26 to 2020 UTC on 7 November. IMO dates the Tarif row to 7 November without a time. Update 112, ICOD 081300 UTC 8 November, still withheld 200-26. The IMO as-at date is now 11 November. Those are separate official instruments, not one collapsed Attack. Do not invent which UKMTO number is the 7 November Tarif row as a PDF fact. The 200-26 PDF has not been revised tonight to print the hull. Do not collapse Tarif, Navig8 Macallister, Huda, Vieila, Velos Sapphire, Grit, Largo Atom and Selat Storm into one early-November Attack because all eight now sit near the top of the sheet. Tarif is Wednesday night\u2019s first official IMO print. Navig8 Macallister remains Wednesday morning\u2019s dedicated 133-count print. Huda remains Tuesday morning\u2019s dedicated 131-count print. Vieila remains Monday midday\u2019s dedicated 130-count print. Velos Sapphire remains Thursday night\u2019s 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 last week\u2019s dedicated 128-count prints.<\/p>\n
Industry and open-register reprints of a 7 November Hormuz clock, and a 10 November ADNOC Logistics & Services \/ WAM restatement of an unpublished hull damaged in UAE territorial waters, stay colour, not a board fact. IMO prints TARIF and IMO 9828390. It does not print a flag. It does not print \u201ccrude oil tanker.\u201d It does not print ADNOC, an MMSI, a call sign, a projectile, or an outbound tag. Do not tidy the board into an ADNOC 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. Do not collapse the unused ADNOC \/ WAM 10 November unpublished hull onto Tarif as a completed naming; that colour sits on a 10 November UAE-territorial-water clock, and IMO\u2019s new row is a 7 November Strait of Hormuz date with no territorial-water tag. IMO printed damaged and no pollution. It did not print sunk, abandoned, NUC, tow, a pollution volume, a seafarer casualty or an attacker.<\/p>\n
The rest of Wednesday morning\u2019s sheet is still there. NAVIG8 MACALLISTER remains 7 November, IMO 9482873, 8NM northwest of Khasab, Oman, damaged, no pollution. 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-night move. The move is the confirmed-incident count from 133 to 134, the as-at date from 10 November to 11 November, and the new Tarif top row. The fatality line is unchanged at 25.<\/p>\n
Warning 200-26 remains an unnamed PDF. The working primary on that dedicated Sunday-morning file is still: ATTACK, time-late, source Company Security Officer, tanker struck by an unknown projectile while transiting outbound through the Strait of Hormuz, 2020 UTC 7 November, all crew safe and accounted for, no reported environmental impact, location footer Strait of Hormuz. UKMTO printed neither a ship name, an IMO number, a flag, a cargo, an attacker, a fire, a NUC or tow line, an anchorage, a damaged line, a no-pollution line, a nautical-mile offset nor a latitude\/longitude. Wednesday night\u2019s IMO row does not revise that PDF. A DPA who briefs Wednesday night as \u201cUKMTO has now named 200-26\u201d has over-read a highlighted-incidents table that does not print a warning number.<\/p>\n
Sunday night\u2019s companion Update 112, retrieved from This morning\u2019s dedicated 202-26 remains an unnamed tanker Suspicious Activity, source Military authorities, Strait of Hormuz, incident date TBC, incident time TBC, crew, damage and environmental impact unknown. This morning\u2019s dedicated 201-26 remains an unnamed tanker Attack, unknown projectile, 19 nautical miles northeast of Lima, 1338 UTC 10 November, crew safe, no environmental impact, first-light damage assessment. Distinct from dedicated Navig8 Macallister on this same table, 7 November, IMO 9482873, 8NM northwest of Khasab. Distinct from dedicated Huda, 7 November, IMO 9197088, 17NM from the coast of Oman. Do not fold Tarif onto those later tanker clocks because the IMO date is also 7 November, and do not fold it onto an 11 November TBC Hormuz clock or a 10 November Lima clock the table does not print. Do not fold it onto the unused ADNOC \/ WAM 10 November unpublished UAE-territorial-water hull as a completed naming.<\/p>\n The 133-to-134 conversion is the briefing fact. Wednesday morning\u2019s dedicated 133-count file printed 133 confirmed \/ 25 dead as at 10 November, with Navig8 Macallister as the named top row. Wednesday night\u2019s board prints 134 confirmed \/ 25 dead as at 11 November, with Tarif as the named top row and Navig8 Macallister 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 one. A war-risk file that still treats IMO\u2019s public sheet as 133 with Navig8 Macallister on top, as at 10 November, has under-read the current table. A master\u2019s pack that treats 200-26\u2019s unnamed tanker as now closed because IMO said Tarif has collapsed two instruments. Wednesday morning\u2019s dedicated file was right to refuse a 134th incident from a board that had not added one. Wednesday night\u2019s dedicated file is the conversion, not a restatement of that refusal, and not a licence to invent a second named Wednesday-night hull.<\/p>\n This is not Warning 200-26. Sunday morning\u2019s dedicated UKMTO warning remains an unnamed Company Security Officer report, tanker struck by an unknown projectile on an outbound Hormuz transit, 2020 UTC 7 November, crew safe, no environmental impact. IMO has taken a 7 November date, the hull, the IMO number, the Strait of Hormuz tag and the damaged\/no-pollution lines. It has not revised the PDF. Sunday night\u2019s companion Update 112 remains a withheld 200-26 line, wrap, not a PDF naming.<\/p>\n 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. Tarif\u2019s row prints no casualty. Do not convert Damaged. No pollution. into a death. Do not convert 200-26\u2019s crew-safe line into a fatality. Do not brief Wednesday night as \u201cIMO has now moved the fatality off Velos Sapphire.\u201d 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 tonight.<\/p>\n This is not Update 112, and it is not Update 113. Sunday night\u2019s dedicated JMIC note remains Update 112 to the advisory, 1 March\u20138 November 2026, ICOD 081300 UTC, JMIC# 001 26, regional threat SEVERE, 177 incidents since 1 March, five counted since last report including 200-26 as Name withheld UFN, tanker, Attack, outbound Hormuz unknown projectile, crew safe. That note still withheld 200-26\u2019s hull. It did not print IMO 9828390. It did not print Tarif. It did not print damaged, no pollution against that withheld Attack. No Update 113 was retrieved this run. Do not promote IMO\u2019s 134th-count snapshot onto Update 112 as a completed JMIC reprint. Do not invent an ICOD move that the JMIC PDF has not printed.<\/p>\n This is not 202-26, 201-26 or 199-26. This morning\u2019s dedicated 202-26 remains an unnamed tanker Suspicious Activity, Strait of Hormuz, TBC, crew\/damage\/env unknown. This morning\u2019s dedicated 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\u2019s dedicated 199-26 remains an unnamed tanker fire, 8 NM northwest of Khasab, crew evacuated; Wednesday morning\u2019s dedicated 133-count remains the first IMO print of Navig8 Macallister against that 7 November Khasab offset. IMO has not named 202-26, 201-26 or 199-26 as new Wednesday-night rows beyond the already-dedicated Navig8 Macallister line. A DPA who briefs Wednesday night as \u201cIMO has now named the TBC Hormuz tanker\u201d or as \u201cIMO has now named the 10 November Lima tanker\u201d has invented a row the sheet does not print. A 7 November date on Tarif is not a 202-26 conversion and not a 201-26 conversion. The extra +1 on the confirmed-incident count is not a licence to invent those namings.<\/p>\n This is not Navig8 Macallister, and it is not a 7 November Khasab-fire rewrite. Dedicated Navig8 Macallister remains 7 November, IMO 9482873, 8NM northwest of Khasab, Oman, damaged, no pollution \u2014 Wednesday morning\u2019s 133rd row, still the second row tonight. Tarif remains 7 November, IMO 9828390, Strait of Hormuz, damaged, no pollution. The same calendar date and a different location wording still separate those lines. Do not brief Wednesday night as Navig8 Macallister reprinted. Official wording still keeps NAVIG8 MACALLISTER on that earlier row. Do not tidy TARIF into a house-style contraction on the official line.<\/p>\n This is not Huda, 197-26 \/ Vieila, 195-26 \/ Grit, 194-26, 193-26, 192-26, 191-26, 425\/26 or Al Jusufi. Dedicated Huda remains 7 November, IMO 9197088, 17NM from the coast of Oman, damaged, no pollution \u2014 Tuesday morning\u2019s 131st row, still the third row tonight. Friday night\u2019s dedicated 197-26 remains an unnamed tanker, waterline explosion port side, 16 NM east of Khasab, 2200 UTC 5 November, crew safe, own power; Monday midday\u2019s dedicated 130-count remains the first IMO print of Vieila against that 5 November Khasab offset. Tuesday night\u2019s dedicated 195-26 remains an unnamed tanker, two unknown projectiles into the engine room, 14 NM northeast of Lima; IMO Grit remains wrap on that 3 November Lima row. Tuesday night\u2019s dedicated 194-26 remains an Indian-crewed dhow Attack outbound through Hormuz; Tuesday afternoon\u2019s dedicated Indian statements remain the Al Jusufi national-statement primary. Monday night\u2019s dedicated 193-26 remains an unnamed vessel, hole starboard, 9 NM northeast of Lima. Last week\u2019s dedicated 128-count remains the first IMO print of Largo Atom and Selat Storm. Sunday night\u2019s dedicated 191-26 remains an unnamed Mayday-relay Attack. Sunday night\u2019s dedicated 425\/26 remains tug Selat Storm sunk 0.6 NM west of Jazirat Um Al Ghanam. IMO\u2019s new Wednesday-night row is printed against Tarif, not against those files. India\u2019s 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 tonight, and it is not the 25th line on this sheet.<\/p>\n This is not this morning\u2019s dedicated NAVAREA IX 436\/26, not this morning\u2019s dedicated Warning 202-26, and not tonight\u2019s companion NAVWARN 834\/26. 436\/26 remains the CS MARAM cable-repair line west of Karachi \/ Port Qasim from 11 November. 202-26 remains the unnamed TBC Hormuz tanker on the Suspicious Activity line. 834\/26 is tonight\u2019s other dedicated file: a drifting mine east of Cape Maslen Nos at 42-16.90N 028-13.48E. None of those products belongs on this Middle East highlighted-incidents table. Official English 835\/26, 829\/26, 828\/26 and 820\/26 remain unused as dedicated. Official Cyprus 345\/26, NAVAREA III 0172\/26, NAVAREA IX 433\/26, official HNHS 1378\/2026 and official HNHS 1376\/2026 remain unused as dedicated. UKMTO now ends at this morning\u2019s dedicated 202-26 on the Suspicious Activity line, dedicated 201-26 on the Attack line, and dedicated 198-26 on the Advisory line. NAVAREA IX still lists dedicated 436\/26 as the first row atop dedicated 435\/26. No UKMTO 203-26, no Update 113, no IMO 135, no ARN 169, no 437\/26 and no official NAVWARN 836 this run.<\/p>\n For a master still holding a Hormuz outbound offset, a Musandam coastal passage, or a war-risk file opened against Sunday morning\u2019s unnamed 200-26 PDF, Wednesday night is a hull-naming problem before it is a new-attack problem. IMO has moved the confirmed-incident count to 134. It has named Tarif, IMO 9828390, 7 November, Strait of Hormuz, damaged, no pollution, with an as-at date now of 11 November. Charterers and underwriters who copied Wednesday morning\u2019s \u201c133 confirmed, Navig8 Macallister on top, as at 10 November, do not invent a 134th row\u201d language into Wednesday night\u2019s pack now have an official naming on a new hull and a later as-at stamp. That is not a licence to treat 200-26 as closed. The PDF still withholds the name. Update 112 still withheld 200-26. IMO now prints Tarif, 9828390, Strait of Hormuz, damaged, no pollution. Carry all three lines. Do not brief a single \u201chull: Tarif on 200-26.\u201d Do not brief a single \u201chull: unnamed.\u201d Write the instrument next to the finding.<\/p>\n The ISM and war-risk split is the operational content a DPA has to get right. Wednesday morning\u2019s dedicated file told operators not to convert the 133-count into a 134th incident because the table had not done so, and not to treat 200-26\u2019s unnamed projectile as an IMO row. Wednesday night\u2019s table has done the IMO conversion on a 7 November Strait of Hormuz tag. A safety-management report that still says \u201cIMO: 133 confirmed, top row Navig8 Macallister, as at 10 November\u201d is stale against the current sheet. A safety-management report that says \u201cUKMTO 200-26: Tarif, IMO 9828390, damaged, no pollution\u201d is over-read against a PDF that still withholds the hull, still prints an unknown projectile on an outbound transit, and still prints neither damaged nor a hull name. Notify the CSO, the P&I correspondent and the war-risk underwriter that IMO\u2019s public highlighted-incidents board as at 11 November now reads 134 confirmed \/ 25 dead and that the new top row is TARIF, IMO 9828390, 7 November, Strait of Hormuz, damaged, no pollution. Keep 200-26 on the unnamed-PDF sheet. Keep Update 112 on the withheld-200-26 sheet. Keep 202-26 and 201-26 on the unnamed-PDF 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 an ADNOC flag, a crude-oil class or a 10 November UAE-territorial-water clock onto the IMO row because industry colour named other hulls against nearby clocks. IMO printed TARIF, 9828390, damaged, no pollution.<\/p>\n The unnamed remainder is unchanged and still matters. 202-26, 201-26, 200-26, 197-26, 195-26, 194-26, 193-26 and 191-26 are still unnamed on this board as new rows, other than the already-dedicated Navig8 Macallister conversion against the 199-26 Khasab offset. 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 Wednesday night as \u201cthe board is now complete through 11 November\u201d has ignored those gaps. A DPA who treats the 134th-count snapshot as this morning\u2019s 202-26 TBC tanker or as this morning\u2019s 201-26 Lima tanker has borrowed a 7 November Strait of Hormuz tag and dropped Tarif\u2019s hull line. A DPA who treats the as-at move from 10 November to 11 November as two new confirmed named attacks has over-read a table that added one named row.<\/p>\n Keep the dedicated files on their own lines. Wednesday morning\u2019s dedicated 133-count remains Navig8 Macallister, as at 10 November, 133 confirmed \/ 25 dead. Tuesday morning\u2019s dedicated 131-count remains Huda, as at 9 November, 131 confirmed \/ 25 dead. Monday midday\u2019s dedicated 130-count remains Vieila, as at 6 November, 130 confirmed \/ 25 dead. Friday afternoon\u2019s dedicated 25-fatality conversion remains Velos Sapphire, as at 6 November, 129 confirmed \/ 25 dead. Sunday night\u2019s dedicated Update 112 remains the JMIC 177-count \/ SEVERE note with 200-26 withheld. Sunday morning\u2019s dedicated 200-26 remains the unnamed outbound Hormuz projectile. This morning\u2019s dedicated 202-26 remains the unnamed TBC Hormuz tanker. This morning\u2019s dedicated 201-26 remains the unnamed Lima tanker Attack. This morning\u2019s dedicated 436\/26 remains the CS MARAM cable-repair line. Tonight\u2019s companion 834\/26 remains the Maslen Nos drifting mine. Do not recast 11 November night as a 200-26 PDF naming, as an Update 112 reprint, as a 26th fatality, as a 10 November Lima conversion, as an 11 November TBC Hormuz conversion, or as a completed 7 November tanker tape.<\/p>\n Regulas Shipping will keep lining Wednesday night\u2019s IMO board as at 11 November \u2014 134 confirmed, 25 dead, Tarif now the named top row \u2014 against Sunday morning\u2019s unnamed 200-26 PDF and against Sunday night\u2019s Update 112 withheld Attack line so operators can treat the 134th-count snapshot as an IMO naming on a new hull, not as a UKMTO naming, a JMIC reprint, a 10 November Lima conversion, an 11 November TBC Hormuz conversion, or a 26th fatality.<\/p>\n","protected":false},"excerpt":{"rendered":" The International Maritime Organization\u2019s highlighted-incidents board, as at 11 November, now prints 134 confirmed incidents in the Strait of Hormuz and the wider Middle East, with 25 confirmed seafarer fatalities. Wednesday morning\u2019s dedicated conversion on this desk sat at 133 as at 10 November, with 25 dead, and with Navig8 Macallister\u2019s 7 November row 8 […]<\/p>\n","protected":false},"author":1,"featured_media":1325,"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-1327","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\/1327","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=1327"}],"version-history":[{"count":0,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1327\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/1325"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=1327"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=1327"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=1327"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}jmic_advisory_update_112_08-nov.pdf<\/code>, ICOD 081300 UTC 8 November, remains wrap on dedicated 200-26 as a withheld line: 200-26 remains Name withheld UFN, tanker, Attack, outbound Hormuz unknown projectile, crew safe, no env impact. Update 112 does not print Tarif. It does not print IMO 9828390. It does not print \u201cdamaged, no pollution\u201d against that withheld Attack. Update 113 was not retrieved this run. IMO\u2019s sheet is tighter on the IMO number, the hull and the damaged\/no-pollution lines, and thinner on the method. It prints neither projectile nor outbound. Hold the official lines separately. A DPA who briefs IMO\u2019s \u201cdamaged, no pollution\u201d as a UKMTO revision of 200-26 will over-read the PDF. The PDF has not been revised tonight to print the hull. A DPA who briefs Update 112 as having printed IMO 9828390, or as having printed Tarif, will over-read a JMIC table that still withheld that tanker.<\/p>\nWhat this is not<\/h2>\n
Operational implications<\/h2>\n
What Operators Should Note<\/h2>\n
\n