The International Maritime Organization\u2019s highlighted-incidents board, as at 6 November, still prints 129 confirmed incidents in the Strait of Hormuz and the wider Middle East, and it now prints 25 confirmed seafarer fatalities. Thursday night\u2019s dedicated board piece on this desk sat at 129 as at 5 November, with 24 dead, and with Velos Sapphire\u2019s 4 November row 50 nautical miles north of Madinat ash Shamal carrying \u201cone seafarer missing.\u201d The confirmed-incident count has not moved. What moved is the as-at date by one day, the fatality line by one, and the wording on that top row. IMO now prints VELOS SAPPHIRE, IMO 9321201, dated 4 November, 50 nautical miles north of Madinat ash Shamal, Qatar, damaged, no pollution, one seafarer fatality. Friday afternoon is the first official IMO conversion of that missing line into a confirmed death.<\/p>\n
The count is an IMO product. It is not a UKMTO warning, not a rewrite of Thursday morning\u2019s dedicated Warning 196-26, not a rewrite of Thursday night\u2019s dedicated 129-count naming, and not a rewrite of Wednesday night\u2019s dedicated Update 111. Update 111, ICOD 051300 UTC 5 November, still withholds 196-26 as Name withheld UFN and does not print a fatality against that row. UKMTO\u2019s 196-26 PDF still prints crew, damage and environmental impact unconfirmed. Those are different instruments from IMO\u2019s 25. Masters who brief Friday afternoon as Update 111 finally printing a death, as UKMTO finally closing the unconfirmed crew line, as a 130th confirmed incident, or as a Hormuz reopen will have misread the table. Thursday night\u2019s dedicated file on this desk correctly held \u201cmissing\u201d off the fatality total. Friday afternoon\u2019s board has moved that line. Log the move. Do not invent a second new hull to explain it.<\/p>\n
Thursday night\u2019s English page was 129 confirmed incidents, 24 dead, as at 5 November, with VELOS SAPPHIRE as the operational naming of that snapshot \u2014 damaged, no pollution, one seafarer missing \u2014 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. Friday afternoon\u2019s English page is 129 as at 6 November, 25 dead. The increment is one confirmed fatality. Zero new named rows sit at the top of the table. That arithmetic is a wording move on an existing hull, not a 130-count. Do not invent a second new name. Do not treat the +1 fatality as a silent conversion of Tuesday night\u2019s dedicated 194-26, Tuesday night\u2019s dedicated 195-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 Friday rows. Do not treat the +1 fatality 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 confirmed-incident count is still 129.<\/p>\n
The changed row is VELOS SAPPHIRE, IMO 9321201, 4 November, 50NM north of Madinat ash Shamal, Qatar, damaged, no pollution, one seafarer fatality. Thursday night\u2019s dedicated 129-count printed the same hull, the same IMO number, the same date, the same offset, damaged, no pollution, and one seafarer missing. Thursday morning\u2019s dedicated Warning 196-26 remains an unnamed tanker Attack, 2320 UTC 4 November, source Verified, location footer Madinat ash Shamal, Qatar: UKMTO has received a report of an incident 50 nautical miles north of Madinat ash Shamal; a tanker has been struck by two unidentified projectiles; the status of the crew, a damage assessment and the environmental impact are unconfirmed at present. Official MSCIO alerts index still showed 0 recent incidents this run and no numbered wrap against that 2320 UTC Qatar clock. Thursday night\u2019s companion Update 111 reprints 196-26 as Name withheld UFN, tanker, Attack, Arabian Gulf, crew \/ damage \/ environment unconfirmed as of ICOD 051300 UTC. IMO does not print 196-26, 2320 UTC, \u201ctwo unidentified projectiles,\u201d a Verified line or an unconfirmed crew line. It now prints Velos Sapphire, 9321201, damaged, no pollution, one seafarer fatality, 50 nautical miles north of Madinat ash Shamal, Qatar, on a 4 November date. That is a tighter casualty finding than Thursday night\u2019s missing line, and it is a different crew line from the PDF. The fatality total is now 25. Fatality is a confirmed death on this sheet. It is not a completed class survey. It is not a UKMTO PDF revision. It is not an Update 111 naming.<\/p>\n
Hold the nearby Qatar plot. ACERS remains 7 October, IMO 9301902, 51NM north of Madinat ash Shamal, Qatar, damaged, no pollution, on this same table. One nautical mile and 28 days separate those two offsets. Do not promote ACERS onto the Velos Sapphire fatality. Do not promote a 7 October clock, a Damaged\/no-pollution line from ACERS, or IMO 9301902 onto Thursday morning\u2019s dedicated 196-26. Thursday night\u2019s dedicated file already held that split. Friday afternoon\u2019s fatality conversion does not collapse it.<\/p>\n
Hold the clocks. UKMTO dates 196-26 to 4 November 2320 UTC. IMO dates the Velos Sapphire row to 4 November without a time. Update 111, ICOD 051300 UTC 5 November, reprints 196-26 as unnamed and unconfirmed. The IMO as-at date is now 6 November. Those are separate official instruments, not one collapsed Attack. Do not invent which UKMTO number is the 4 November Velos Sapphire row. The 196-26 PDF has not been revised this afternoon. Do not collapse Largo Atom, Selat Storm, Arzanah, Al Mayeda, RITI, Louise 1 and Velos Sapphire into one late-October-to-early-November Attack because all seven now sit near the top of the sheet. Velos Sapphire remains Thursday night\u2019s dedicated 129-count print, now with a fatality line instead of a missing line. Largo Atom, Selat Storm and Arzanah remain Wednesday morning\u2019s dedicated 128-count prints. Al Mayeda and RITI remain Tuesday morning\u2019s dedicated 125-count prints. Louise 1 remains Monday afternoon\u2019s dedicated 123-count print.<\/p>\n
The rest of Thursday night\u2019s sheet is still there. 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. LEONORA KOSAN remains 23 October, IMO 9390953, 6 NM northeast of Limah, damaged, no pollution. SOYIA remains 20 October, IMO 9263916, 30 NM southeast of Al Faw, damaged, no pollution. CHLOE (MIVERVA V) remains 19 October, IMO 9315367, 121 NM from the coast of Oman, damaged, no pollution. AL DASMA remains 20 October, IMO 9653446, Strait of Hormuz, second attack, damaged, no pollution, with the 7 September first-attack row still on the board. JIF BARRACUDA remains 18 October, IMO 9345506, northeast of Khor Fakkan, damaged, no pollution, one seafarer injured. GFS PRIDE remains sunk, no pollution. PETRO DOLPHIN remains two seafarers missing at Sohar Anchorage. GEM NO. 2 remains 9 October, IMO 9735373, 13 NM west of Al Jazeera, damaged. Cameroon Prosperity is still printed with the eight-digit IMO typo 93151598; the working seven-digit number on earlier dedicated files is 9315159. CAPE DAO remains 23 September, IMO 9219020, 15 NM northeast of Khasab, sunk, no pollution, one seafarer fatality. None of those rows is the 6 November move. The move is the as-at date shift to 6 November, the fatality total from 24 to 25, and the Velos Sapphire wording from missing to fatality. The confirmed-incident count is unchanged at 129.<\/p>\n
Warning 196-26 remains an unnamed PDF. The working primary on that dedicated Thursday-morning file is still: ATTACK, 4 November 2026, 2320 UTC, source Verified, tanker struck by two unidentified projectiles, 50 nautical miles north of Madinat ash Shamal, Qatar, status of the crew, damage assessment and environmental impact unconfirmed at present, location footer Madinat ash Shamal, Qatar, filename 20261105-ukmto_warning-196-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 missing-seafarer line, a fatality line nor a latitude\/longitude beyond the 50-nautical-mile north-of-Madinat-ash-Shamal offset. Friday afternoon\u2019s IMO row does not revise that PDF. A DPA who briefs Friday afternoon as \u201cUKMTO has now named 196-26\u201d or as \u201cUKMTO has now confirmed a death\u201d has over-read a highlighted-incidents table that does not print a warning number.<\/p>\n
Thursday night\u2019s companion Update 111, retrieved from jmic_advisory_update_111_05-nov.pdf, ICOD 051300 UTC 5 November, remains wrap on dedicated 196-26: Name withheld UFN, tanker, Attack, Arabian Gulf, two unidentified projectiles approx. 50 NM north of Madinat ash Shamal, Qatar, crew, damage assessment and environmental impact unconfirmed as of ICOD. Update 111 does not print Velos Sapphire. Update 112 was not retrieved this run. IMO\u2019s sheet is tighter on the hull, the IMO number and the fatality line and thinner on the method. It prints \u201c50NM north of Madinat ash Shamal, Qatar,\u201d \u201cdamaged,\u201d \u201cno pollution\u201d and \u201cone seafarer fatality,\u201d not \u201ctwo unidentified projectiles,\u201d not \u201cVerified,\u201d and not \u201cunconfirmed.\u201d Hold the official lines separately. A DPA who briefs IMO\u2019s \u201cdamaged, no pollution, one seafarer fatality\u201d as a UKMTO revision of 196-26 will over-read the PDF. The PDF has not been revised this afternoon. A DPA who briefs Update 111 as having named Velos Sapphire or as having moved a death will over-read a table that still reads Name withheld UFN and unconfirmed as of ICOD.<\/p>\n
Industry colour of the same 4 November clock, held separately: open-register particulars only, Marshall Islands, oil products tanker, about 228 m, 40,953 gt \/ 74,998 dwt, MMSI 538008858. Those extras are not an IMO flag, cargo or owner print. IMO prints Velos Sapphire, 9321201, damaged, no pollution, one seafarer fatality. 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. Distinct from dedicated ACERS on this same table, 7 October, IMO 9301902, 51NM north of Madinat ash Shamal. Distinct from dedicated LARGO ATOM, 1 November, 72NM east of Ras Al Khafji. Distinct from dedicated 195-26, Tuesday night\u2019s unnamed tanker engine-room Attack, 1900 UTC 3 November, 14 nautical miles northeast of Lima. Do not fold Velos Sapphire onto that Lima clock.<\/p>\n
The missing-to-fatality conversion is the briefing fact. 196-26 printed unconfirmed. Update 111 printed unconfirmed as of ICOD. Thursday night\u2019s dedicated 129-count printed one seafarer missing and held the fatality total at 24. Friday afternoon\u2019s board prints one seafarer fatality and holds the fatality total at 25. 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 when they first printed, and they have not moved it this afternoon. Velos Sapphire\u2019s line has. A war-risk file that still treats IMO\u2019s Velos Sapphire row as a missing-seafarer watch has under-read the 6 November sheet. A master\u2019s pack that treats 196-26\u2019s unconfirmed crew line as now closed because IMO said fatality has collapsed two instruments. Thursday night\u2019s dedicated file was right to refuse a 25th fatality from a missing line. Friday afternoon\u2019s dedicated file is the conversion, not a restatement of that refusal.<\/p>\n
This is not Warning 196-26. Thursday morning\u2019s dedicated UKMTO Attack remains an unnamed Verified report, 2320 UTC 4 November, tanker, two unidentified projectiles, 50 nautical miles north of Madinat ash Shamal, crew, damage and environment unconfirmed. IMO has taken the offset, the date, the hull, the IMO number, the damaged\/no-pollution lines and, this afternoon, the fatality. It has not revised the PDF. Thursday night\u2019s companion Update 111 still withholds the hull and still prints unconfirmed.<\/p>\n
This is not a 130-count, and it is not a new named hull. The confirmed-incident line is still 129. No 195-26 tanker, no 194-26 dhow, no Al Jusufi, no 193-26 vessel, no 191-26 Mayday hull, no Quba and no AZINI has been added as a new Friday row. A DPA who briefs Friday afternoon as \u201cIMO has now named the Lima engine-room tanker\u201d or as \u201cIMO has now named Al Jusufi\u201d has invented a row the sheet does not print. The only wording move on an existing top row is Velos Sapphire\u2019s missing-to-fatality conversion.<\/p>\n
This is not Update 111, and it is not Update 112. Thursday night\u2019s dedicated JMIC note remains Update 111 to the advisory, 1 March\u20135 November 2026, ICOD 051300 UTC, JMIC# 001 26, regional threat SEVERE, 172 incidents since 1 March, printed correction that Update 110 should have read 166 not 167, six counted since last report including 196-26 as Name withheld UFN. That note named SELAT STORM, LARGO ATOM and MSV AL JUSUFI against other clocks and still withheld Velos Sapphire. No Update 112 was retrieved this run. Do not promote IMO\u2019s 25th fatality onto Update 111. Do not invent an ICOD move that the JMIC PDF has not printed.<\/p>\n
This is not a rewrite of Thursday night\u2019s dedicated 129-count naming except for the two lines the board actually moved. Thursday night remains the first official IMO print of Velos Sapphire, IMO 9321201, 4 November, 50NM north of Madinat ash Shamal, damaged, no pollution. Friday afternoon does not unsay that naming. It amends the casualty line and the fatality total and the as-at date. Keep Thursday night\u2019s file as the naming. Keep this afternoon\u2019s file as the fatality conversion. Do not delete the 5 November snapshot. Do not brief Friday afternoon as a second first-print of the hull.<\/p>\n
This is not 195-26, 194-26, 193-26, 192-26, 191-26, 425\/26 or Al Jusufi. Tuesday night\u2019s 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\u2019s dedicated 194-26 remains an Indian-crewed dhow Attack outbound through Hormuz, surviving crew rescued, vessel status unknown on the PDF; Tuesday afternoon\u2019s dedicated Indian statements remain the Al Jusufi \/ Gandhar Nahim Ajij national-statement primary. Monday night\u2019s dedicated 193-26 remains an unnamed vessel, hole starboard, 9 NM northeast of Lima, vessel and crew safe. Monday morning\u2019s dedicated 192-26 remains wrap under Wednesday morning\u2019s Largo Atom IMO print. Sunday night\u2019s dedicated 191-26 remains an unnamed Mayday-relay Attack in the Strait of Hormuz. Sunday night\u2019s dedicated 425\/26 remains tug Selat Storm sunk 0.6 NM west of Jazirat Um Al Ghanam. IMO\u2019s 25th fatality is printed against Velos Sapphire, 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 this afternoon, and it is not the 25th line on this sheet.<\/p>\n
This is not ACERS, and it is not a 7 October Qatar rewrite. Dedicated ACERS remains 7 October, IMO 9301902, 51NM north of Madinat ash Shamal, damaged, no pollution. Velos Sapphire remains 4 November, IMO 9321201, 50NM north of Madinat ash Shamal, damaged, no pollution, one seafarer fatality. One nautical mile and 28 days still separate those offsets. Do not brief Friday afternoon as ACERS killed a seafarer.<\/p>\n
This is not this morning\u2019s dedicated NAVAREA IX 431\/26, and it is not this afternoon\u2019s companion ARN 167\/26. 431\/26 remains the Fujairah jack-up on SKATE 3D. 167\/26 is a 9 November 20 km Romanian training circle at 44-02.80 N 030-35.20 E. Neither product belongs on this Middle East highlighted-incidents table. Official HNHS 1338\/26 and 1339\/26 remain unused as dedicated Thracian Sea unlit lights. Official NAVAREA II 386\/2026 remains unused as dedicated Pointe Noire containers. UKMTO still ends at 196-26. NAVAREA IX still ends at dedicated 431\/26. NAVAREA III still ends at dedicated 0169\/26 beside dedicated 0168\/26. No 197-26, no Update 112, no IMO 130, no 432\/26, no 0170\/26, no NAVWARN 798 this run.<\/p>\n
For a master still holding a Qatar \/ central-Gulf passage, a Madinat ash Shamal north offset, or a war-risk file opened against Thursday morning\u2019s unnamed 196-26 PDF, Friday afternoon is a casualty-line problem before it is a new-attack problem. IMO has not added a 130th confirmed incident. It has converted Thursday night\u2019s missing seafarer on Velos Sapphire into a confirmed fatality and moved the running total from 24 to 25, with an as-at date of 6 November. Charterers and underwriters who copied Thursday night\u2019s \u201c24 dead, one missing on Velos Sapphire, do not convert\u201d language into Friday\u2019s pack now have an official conversion on the same hull. That is not a licence to treat 196-26 as closed. The PDF still prints unconfirmed. Update 111 still prints unconfirmed as of ICOD. IMO now prints fatality. Carry all three lines. Do not brief a single \u201ccrew status: dead.\u201d Do not brief a single \u201ccrew status: unconfirmed.\u201d Write the instrument next to the finding.<\/p>\n
The next-of-kin and ISM split is the operational content a DPA has to get right. Thursday night\u2019s dedicated file told operators not to convert missing into a 25th confirmed fatality because the table had not done so. Friday afternoon\u2019s table has done so. A safety-management report that still says \u201cIMO: one missing, fatality line 24\u201d is stale against the 6 November sheet. A safety-management report that says \u201cUKMTO 196-26: one dead\u201d is over-read against a PDF that still withholds the hull and still prints unconfirmed. Notify the CSO, the P&I correspondent and the war-risk underwriter that IMO\u2019s public highlighted-incidents board as at 6 November now reads 129 confirmed \/ 25 dead and that the Velos Sapphire row, IMO 9321201, 4 November, 50NM north of Madinat ash Shamal, Qatar, now reads damaged, no pollution, one seafarer fatality. Keep 196-26 on the unnamed-PDF sheet. Keep Update 111 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.<\/p>\n
The unnamed remainder is unchanged and still matters. 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 Friday afternoon as \u201cthe board is now complete through 4 November\u201d has ignored those gaps. A DPA who treats the 25th fatality as India\u2019s Al Jusufi death moved onto the IMO sheet has borrowed a 2 November Limah clock and dropped Velos Sapphire.<\/p>\n
Keep the dedicated files on their own lines. Thursday night\u2019s dedicated 129-count remains the first IMO print of Velos Sapphire, as at 5 November, 24 dead, one seafarer missing. Thursday night\u2019s dedicated Update 111 remains the JMIC 172-count \/ SEVERE note with 196-26 withheld. Thursday morning\u2019s dedicated 196-26 remains the unnamed Qatar tanker Attack. Wednesday morning\u2019s dedicated 128-count remains Largo Atom, Selat Storm and Arzanah. Tuesday morning\u2019s dedicated 125-count remains Al Mayeda and RITI. Monday afternoon\u2019s dedicated 123-count remains Louise 1. Tuesday night\u2019s dedicated 194-26 and 195-26 remain unnamed PDFs. Tuesday afternoon\u2019s dedicated Al Jusufi statements remain the Indian national-statement primary. This morning\u2019s dedicated 431\/26 remains the Fujairah jack-up. This afternoon\u2019s companion 167\/26 remains the Romanian 20 km training circle. Do not recast 6 November afternoon as a 196-26 PDF naming, as an Update 111 death, as a 130-count, or as a completed 4 November tape.<\/p>\n
Regulas Shipping will keep lining Friday afternoon\u2019s IMO board as at 6 November \u2014 129 confirmed, 25 dead, Velos Sapphire now a seafarer fatality \u2014 against Thursday night\u2019s dedicated 129-count missing line and against Thursday morning\u2019s unnamed 196-26 PDF so operators can treat the 25th death as an IMO conversion on an existing hull, not as a 130th incident, a UKMTO naming, or a completed Qatar Attack file.<\/p>\n","protected":false},"excerpt":{"rendered":"
The International Maritime Organization\u2019s highlighted-incidents board, as at 6 November, still prints 129 confirmed incidents in the Strait of Hormuz and the wider Middle East, and it now prints 25 confirmed seafarer fatalities. Thursday night\u2019s dedicated board piece on this desk sat at 129 as at 5 November, with 24 dead, and with Velos Sapphire\u2019s […]<\/p>\n","protected":false},"author":1,"featured_media":1244,"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-1247","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\/1247","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=1247"}],"version-history":[{"count":1,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1247\/revisions"}],"predecessor-version":[{"id":1248,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1247\/revisions\/1248"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/1244"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=1247"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=1247"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=1247"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}