{"id":1235,"date":"2026-11-05T23:35:24","date_gmt":"2026-11-05T23:35:24","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/jmic-update-111-names-selat-storm-largo-atom-and-al-jusufi\/"},"modified":"2026-11-05T23:36:25","modified_gmt":"2026-11-05T23:36:25","slug":"jmic-update-111-names-selat-storm-largo-atom-and-al-jusufi","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/jmic-update-111-names-selat-storm-largo-atom-and-al-jusufi\/","title":{"rendered":"JMIC Update 111 names Selat Storm, Largo Atom and Al Jusufi"},"content":{"rendered":"

The U.S. Navy-led Joint Maritime Information Center published Update 111 to its regional advisory note with an information cut-off of 051300 UTC on 5 November. The working primary retrieved this run is the numbered PDF posted on the UKMTO product board as jmic_advisory_update_111_05-nov.pdf<\/code>. The face of the note is titled Update 111 to JMIC Advisory Note, 01 March \u2013 05 November 2026. The information cut-off is printed as ICOD 051300 UTC. The note is printed as JMIC# 001 26. The regional threat level remains SEVERE. The Strait of Hormuz remains SEVERE. The Arabian Gulf remains SUBSTANTIAL. The Gulf of Oman stays MODERATE. The Arabian Sea stays MODERATE. The Gulf of Aden stays SUBSTANTIAL. Bab el-Mandeb \/ the southern Red Sea stay SUBSTANTIAL. The Somali Coast \/ Somali Basin stay MODERATE. The Northern Red Sea \/ Suez Canal stay MODERATE. The Eastern Mediterranean stays LOW. Confirmed vessel incidents since 1 March are now printed as 172. A correction line states that the total in Update 110 should have read 166, not 167; the error was a double count. Six incidents are counted since the last report: UKMTO 191-26, 192-26, 193-26, 194-26, 195-26 and 196-26.<\/p>\n

That is the working primary. Thursday night\u2019s product is a numbered regional instrument, not a Hormuz reopen, not Update 112, and not a rewrite of Sunday night\u2019s dedicated Update 110, Monday morning\u2019s dedicated Warning 192-26, Sunday night\u2019s dedicated 425\/26, Sunday night\u2019s dedicated Warning 191-26, Monday night\u2019s dedicated Warning 193-26, Tuesday afternoon\u2019s dedicated Al Jusufi statements, Tuesday night\u2019s dedicated Warning 194-26 or 195-26, or Thursday morning\u2019s dedicated Warning 196-26. The useful facts for a DPA and a bridge team are the first JMIC conversions of dedicated 191-26 and dedicated 425\/26 onto SELAT STORM, dedicated 192-26 onto LARGO ATOM, and dedicated 194-26 onto MSV AL JUSUFI; the still-withheld 193-26, 195-26 and 196-26 rows; the 172-incident tally after the Update 110 double-count correction; the 5 November congestion print of about 179 hulls at Fujairah \/ Khor Fakkan; the 1\u20134 November U.S.-facilitated Hormuz count of 126; and the outlook that still treats further Hormuz attacks as highly likely, particularly off Musandam. Do not treat Wednesday morning\u2019s dedicated IMO 128-count as a substitute for this numbered note, and do not treat Update 110 as still the current public instrument. Tonight\u2019s companion IMO 129-count is a different instrument. Update 111 still withholds 196-26.<\/p>\n

What Update 111 actually added<\/h2>\n

The confirmed tape is the body of Update 111. ICOD 051300 UTC 5 November. JMIC# 001 26. Regional threat SEVERE. Six incidents since Update 110, counted as 191-26 through 196-26. Total 172 since 1 March, after a printed correction that Update 110 should have read 166, not 167. That is the product. Stay with that wording. Do not invent a seventh counted row for MSCIO 168\/26. That file sits on the table as Suspicious activity and is not in the six-incident tally. Do not invent a Hormuz downgrade. Do not invent a completed Update 112. Do not invent a UKMTO PDF revision of 191-26, 192-26, 193-26, 194-26, 195-26 or 196-26.<\/p>\n

On 191-26 and 425\/26, Update 111 names the hull and joins the two instruments. The table prints the date line as 01 Nov 2026 UKMTO 191-26 and 02 Nov 2026 NAVAREA IX 425\/26. Vessel: SELAT STORM. Vessel type: Tug. Event type: Attack. Location: Strait of Hormuz. The narrative says UKMTO received a report that on 01 Nov the Master of a merchant vessel relayed a Mayday call stating that a vessel had been struck by an unknown projectile within the Strait of Hormuz. NAVAREA IX 425\/26 reported the tug, identified by NAVAREA IX as the SELAT STORM, involved in a security incident and sunk approx. 0.6 NM west of Jazirat Um Al Ghanam. Casualty reports are conflicting. That is the first numbered JMIC print of Selat Storm against dedicated 191-26. Dedicated Warning 191-26 remains an unnamed Merchant Vessel Attack, 1509 UTC 1 November, Channel 16 Mayday relay, another vessel, unknown projectile, location footer Strait of Hormuz. Dedicated 425\/26 remains tug boat Selat Storm sunk in 26-22.55N 056-20.47E, approximately 0.6 nautical miles west of Jazirat Um Al Ghanam. Wednesday morning\u2019s dedicated IMO 128-count already printed SELAT STORM, IMO 9266657, 1 November, Strait of Hormuz, damaged, pollution unknown. Update 111 is the regional-note naming that now joins 191-26 and 425\/26 and adds \u201ccasualty reports are conflicting.\u201d Hold those instruments. Do not invent a flag on this row. Do not invent an IMO number on this note. Do not convert JMIC\u2019s Attack onto 425\/26 as a refloat. Do not convert 425\/26\u2019s Sunk onto 191-26 as a completed PDF naming. Do not collapse Largo Atom or Al Jusufi onto this Mayday.<\/p>\n

On 192-26, Update 111 names the hull. Vessel: LARGO ATOM. Vessel type: Tanker. Event type: Attack. Location: Arabian Gulf. The narrative says UKMTO received a report that on 01 Nov a tanker, identified by UKMTO as the LARGO ATOM, travelling southeast through the Arabian Gulf was struck by two unknown projectiles on the port side approx. 72 NM east of Ras Al Khafji, Saudi Arabia. All crew were accounted for and no environmental impact was reported. Dedicated Warning 192-26 remains an unnamed Master Attack, 2347 UTC 1 November, tanker, two unknown projectiles on the port side, 72 nautical miles east of Ras Al Khafji, all crew accounted for, no reported environmental impact at this time. Official MSCIO Alert 165\/26 remains wrap on that dedicated file. Wednesday morning\u2019s dedicated IMO 128-count already printed LARGO ATOM, IMO 1034747, 1 November, 72NM East of Ras Al Khafji, Saudi Arabia, damaged, no pollution. Update 111 is the first numbered JMIC print of Largo Atom against 192-26. The \u201cidentified by UKMTO\u201d clause is a JMIC sourcing line. It is not a revision of the public 192-26 PDF, which still withholds the name. Do not invent a flag. Do not invent an IMO number on this note. Do not invent a fire, a NUC or a next port.<\/p>\n

On 193-26, Update 111 withholds the name. Vessel: Name withheld UFN. Vessel type: Unknown. Event type: Attack. Location: Strait of Hormuz. The narrative says UKMTO received a report that on 01 Nov a vessel was struck by an unknown projectile approx. 9 NM northeast of Lima, Oman, causing a hole on the starboard side. The vessel and crew were reported safe, with no environmental impact. Also reported by MSCIO in 166\/26. Dedicated Warning 193-26 remains an unnamed Master Attack, 2020 UTC 1 November, 9 nautical miles northeast of Lima, hole on the starboard side, vessel and crew safe. Official MSCIO Alert 166\/26 remains wrap. Update 111 reprints that clock and still withholds the hull. Do not invent a name. Do not collapse Selat Storm or Al Jusufi onto this Lima hole.<\/p>\n

On 194-26, Update 111 names the hull. Vessel: MSV AL JUSUFI. Vessel type: Dhow. Event type: Attack. Location: Strait of Hormuz. The narrative says UKMTO received a report by the Indian Government that on 02 Nov an Indian-crewed dhow, identified by India’s Ministry of External Affairs as the MSV AL JUSUFI, was attacked while sailing outbound through the Strait of Hormuz. The Royal Navy of Oman rescued the surviving crew; Indian officials reported one crew member fatality and 13 rescued. UKMTO is unaware of the status of the vessel. Dedicated Warning 194-26 remains an unnamed Verified Attack, 1105 UTC 2 November, Indian-crewed dhow outbound through the Strait of Hormuz, surviving crew rescued, vessel status unknown, location footer Lima, Oman. Tuesday afternoon\u2019s dedicated Indian minister \/ MEA \/ DMA Al Jusufi file remains the national-statement primary. Update 111 is the first numbered JMIC print of MSV Al Jusufi against 194-26. It is not a UKMTO PDF revision. Do not invent a lat\/long. Do not invent an IMO number. Do not invent an attacker. Do not convert \u201cunaware of the status of the vessel\u201d into a sinking, a NUC or a wreck buoy.<\/p>\n

On 195-26, Update 111 withholds the name. Vessel: Name withheld UFN. Vessel type: Tanker. Event type: Attack. Location: Strait of Hormuz. The narrative says UKMTO received a report from the Company Security Officer of a tanker that on 03 Nov the vessel was struck by two unknown projectiles in the engine room approx. 14 NM northeast of Lima, Oman. No casualties or environmental impact were reported. Dedicated Warning 195-26 remains an unnamed CSO Attack, 1900 UTC 3 November, tanker, two unknown projectiles into the engine room, 14 nautical miles northeast of Lima, no casualties or environmental impact reported at this time. Update 111 reprints that clock and still withholds the hull. Do not invent a name. Do not collapse Largo Atom or Thursday morning\u2019s dedicated 196-26 onto this Lima engine-room hit.<\/p>\n

On MSCIO 168\/26, Update 111 withholds the name. Vessel: Unknown. Vessel type: Unknown. Event type: Suspicious activity. Location: Bab el-Mandeb. The narrative says MSCIO received a report that on 03 Nov a merchant vessel observed a large floating object, possibly a boat, surrounded by smoke in the Bab el-Mandeb. No distress calls were received and the circumstances are unknown. That file is unused as a dedicated piece this run. It is wrap on Update 111. It is not in the six-incident Attack tally. Do not convert Suspicious activity into Attack. Do not invent a hull, a lat\/long or a Houthi claim against this smoke.<\/p>\n

On 190-26 and 161\/26, Update 111 reprints AZINI as liberated. The table prints the date line as 31 Oct 2026 UKMTO 190-26 and 02 Nov 2026 MSCIO 161\/26 UPDATE 02. Vessel: AZINI. Vessel type: Fishing vessel. Event type: Suspicious activity. Location: Somali Basin. The narrative says UKMTO received a report on 31 Oct that a large fishing vessel had been boarded and taken by armed persons east southeast of Socotra. The vessel identified by MSCIO as the AZINI was hijacked by armed pirates off northeast Somalia on 29 Oct. MSCIO UPDATE 02 (02 Nov) reported the AZINI liberated and the incident closed. Sunday morning\u2019s dedicated MSCIO Alert 161\/26 remains the working hijack instrument. Saturday night\u2019s dedicated Warning 190-26 remains an unnamed large-fishing-vessel boarding. Sunday night\u2019s dedicated Update 110 already collapsed those two files onto AZINI as wrap. Update 02 liberation was already wrap on dedicated 161\/26. Update 111 reprints the closed incident. It does not convert Suspicious activity into Attack. It does not print a merchant target. Do not rewrite 161\/26 as a second dedicated hijack.<\/p>\n

On 196-26, Update 111 withholds the name. Vessel: Name withheld UFN. Vessel type: Tanker. Event type: Attack. Location: Arabian Gulf. The narrative says UKMTO received a report that on 04 Nov a tanker was struck by two unidentified projectiles approx. 50 NM north of Madinat ash Shamal, Qatar. The status of the crew, damage assessment and environmental impact is unconfirmed as of ICOD. Thursday morning\u2019s dedicated Warning 196-26 remains an unnamed Verified Attack, 2320 UTC 4 November, tanker, two unidentified projectiles, 50 nautical miles north of Madinat ash Shamal, Qatar, crew, damage and environmental impact unconfirmed. Update 111 reprints that clock and still withholds the hull. Tonight\u2019s companion IMO 129-count is a different instrument. Do not promote a later IMO naming onto this 051300 UTC table. Do not collapse ACERS, Largo Atom or 195-26 onto this Qatar tanker.<\/p>\n

The Arabian Gulf operational summary is the paragraph that should replace Update 110\u2019s version in the master\u2019s pack. Two attacks were reported in this period (UKMTO 192-26 and 196-26). No further disruptions were reported. The attacks were the seventh and eighth inside the Arabian Gulf since 07 Oct. UKMTO 196-26 occurred in the central Gulf, north of Qatar. Traffic flows continued, with anchorage congestion high across the region. The 24\u201348-hour outlook is unchanged in kind: eight attacks inside the Gulf since 07 Oct, including the 01 November attack on a tanker approx. 72 NM east of Ras Al Khafji (UKMTO 192-26) and the 04 November attack on a tanker approx. 50 NM north of Madinat ash Shamal, Qatar (UKMTO 196-26), show that attacks remain a strong possibility throughout the Arabian Gulf, including the northern and central Gulf, anchorages and STS areas. Electronic interference was stable but remained a credible concern in the central and southern Arabian Gulf. Vessels stationary for extended periods, or maintaining AIS-on while static, may face elevated targeting risk.<\/p>\n

The Strait of Hormuz summary carries four Attacks in the period (191-26, 193-26, 194-26 and 195-26), against three in the previous period. All four occurred within about 52 hours, from 01 Nov 1509 UTC to 03 Nov 1900 UTC, off the Musandam coast of Oman. IRGC attacks, attempted attacks and\/or harassment activity persisted, including UAV overflight, targeted surveillance of merchant shipping, and occasional VHF hailing. Commercial traffic through the Strait remained at reduced levels compared to the 2025 baseline. Independent tracking data indicated single to low double digit transits per day, while U.S. NCAGS data indicated an average of approximately 31 U.S. assisted transits during this period against an average of 34 per day over 24\u201330 October. U.S.-facilitated Strait of Hormuz transits for 01\u201304 November, the past 96 hours, are printed as 126. Do not add the 126, the 31-per-day series and the independent single-to-low-double-digit series into one throughput figure. Further attacks on transiting vessels, including tugs and dhows, are highly likely, particularly off Musandam. AIS-on vessels can expect elevated targeting risk and directed hails instructing them to divert toward the northern Iranian-controlled route. A 30-nautical-mile standoff from U.S. units remains advised. JMIC Advisory Note 016-26 remains the clearance-request tool.<\/p>\n

What sits off the list, and the traffic that moved<\/h2>\n

Thursday\u2019s cut-off is 051300 UTC on 5 November. Update 111 does print Thursday morning\u2019s dedicated Warning 196-26, as an unnamed tanker Attack 50 nautical miles north of Madinat ash Shamal. It does not print a hull against that clock. Tonight\u2019s companion IMO 129-count is a later highlighted-incidents instrument, not a seventh named row on this table. Do not back-fit an IMO hull onto a 1300 UTC JMIC sheet that still reads Name withheld UFN.<\/p>\n

The Gulf of Oman summary is marked no change. No confirmed attacks or disruptions were reported in this period. Naval presence remained elevated because of blockade enforcement. The latest official CENTCOM figures cited in Update 111 remain dated 01 Nov: 144 commercial vessels redirected; four vessels disabled as a result of blockade enforcement; two boarded for blockade compliance. No further CENTCOM blockade-enforcement action was announced in this period. Neutral vessels between non-Iranian ports may be questioned, visited and searched under the blockade and should be prepared to provide the documentation noted in JMIC Advisory Note 016-26. A 30-nautical-mile standoff from U.S. units remains advised, as well as continuous monitoring of VHF Channel 16.<\/p>\n

The Arabian Sea paragraph is marked no change. The Gulf of Aden paragraph says no confirmed attacks or disruptions were reported in this period. NAVAREA IX 416\/26, suspected Pirate Action Group activity following UKMTO 184-26, was stated to remain in force until 03 November; no replacement warning has been identified. Further approaches are likely in the western Gulf of Aden and the IRTC. MSCIO continues to advise strict adherence to BMP-MS. The southwest monsoon withdrew on 15 Oct. Sea state across the Gulf of Aden is forecast to remain slight, with significant wave heights of approx. 0.7\u20131.4 m and winds of 12\u201318 kt through the reporting period.<\/p>\n

Southern Red Sea and Bab el-Mandeb carry MSCIO 168\/26 as the one Suspicious activity in the period. No attack on a merchant vessel was reported. Traffic remains below the 20 July Houthi selective embargo. Commercial traffic in the Bab el Mandeb rose on S&P tracking, to an average of approx. 34 transits per day on 01\u201304 November (38, 37, 35 and 26) against approx. 28 per day in the previous week. Bab el-Mandeb remains open to commercial traffic but is considered as volatile. The last confirmed Houthi attack on a merchant vessel on this note remains 24 August. MT ASANA, the Tanzanian-flagged product\/chemical tanker hijacked on 17 July approximately 65 NM southwest of Mukalla, is still the one merchant vessel remaining hijacked.<\/p>\n

The Somali Coast and Somali Basin paragraph reprints the AZINI liberation and still treats Pirate Action Group range as likely to extend across the northern Somali Basin towards the shipping routes east and south of Socotra. Sea state in the Somali Basin is forecast to remain slight, with significant wave heights of approx. 1.0\u20131.2 m and winds of 9\u201313 kt, with no storm warning until next report. Following the withdrawal of the southwest monsoon, those conditions remain favorable for skiff and mother-ship operations further offshore.<\/p>\n

Infrastructure colour is unchanged in kind. No attack on ports, terminals, offshore platforms, oil and gas loading facilities or subsea infrastructure was reported in this period. The overall infrastructure risk remains MODERATE.<\/p>\n

Port and anchorage congestion is printed as of 05 Nov. About 179 vessels were at anchor in the vicinity of Fujairah \/ Khor Fakkan. About 141 were off Dubai \/ Jebel Ali to Ras Al Khaimah, mainly off Sharjah \/ Ajman \/ Umm Al Quwain. About 50 were in the vicinity of Musandam \/ Sohar. About 17 were off Bandar Abbas \/ Qeshm, low confidence because Iranian AIS coverage is thin. There was no mass departure, new cluster or gap near an attack area, including off Musandam where four attacks were reported. JMIC internal tracking counted approximately 229 commercial vessels stationary at the main anchorages east of the Strait of Hormuz (Fujairah, Khor Fakkan, Sohar and Musandam), against single-digit to low double-digit AIS-visible transits per day; the backlog is expected to persist. Data limits: internal AIS estimates; AIS-dark vessels excluded. Stationary AIS-on hulls may face elevated targeting risk. Do not restore Update 110\u2019s 490-vessel wait as a figure on this note. That sentence sat on Update 110. It is not reprinted here.<\/p>\n

GNSS \/ AIS interference in the Arabian Gulf was stable, concentrated along the UAE coast near Dubai \/ Sharjah. Windward recorded 362 jammed vessels of 5,921 transmitting in the Gulf and Gulf of Oman on 3 November, about 3 percent below its seven-day average. UKMTO\u2019s weekly VRA report for the week ending 30 October recorded four vessel GNSS reports. In the Strait of Hormuz, indications remained low; the Gulf of Oman rose slightly from a quiet base. In the Red Sea and Bab el-Mandeb, no significant GNSS interference was observed at sea. No new specific UKMTO, MARAD, NAVCENT or NAVAREA IX GNSS\/EMI notices were issued 01\u201305 November. Baseline advisories remain in force. Cross-check with radar and visual navigation.<\/p>\n

The annex is the independent traffic colour Update 110 did not yet have for 01\u201304 November. Independent cargo-vessel transits through the Strait, S&P Maritime \/ SeaVision, excluding Iranian-port callers, are printed as 3, 4, 4, 0, 0, 1 and 4 for 29 October through 4 November. Independent tanker transits for the same week are 2, 0, 4, 1, 2, 2 and 1. Bab el-Mandeb cargo totals for those seven days are 16, 24, 33, 19, 25, 22 and 17. Bab el-Mandeb tanker totals are 10, 8, 15, 19, 12, 13 and 9. Do not add those independent figures to the 126 U.S.-facilitated count. UKMTO\u2019s own transit, latest-incidents and AIS-anomaly boards are printed as annex headings.<\/p>\n

What this is not<\/h2>\n

This is not Update 112, and it is not a rewrite of dedicated Update 110. Update 110, ICOD 011300 UTC 1 November, remains the previous numbered public periodic note. Update 111 replaces it. The 167-incident print on Update 110 is now corrected to 166. Masters who still brief the region as Update 110 will have the wrong instrument in the folder. Masters who brief Thursday night as Update 112 will have invented a later cut-off this desk has not retrieved.<\/p>\n

This is not a rewrite of 191-26, and it is not a UKMTO PDF naming of Selat Storm. Dedicated Warning 191-26 remains an unnamed Channel 16 Mayday-relay Attack, 1509 UTC 1 November, Strait of Hormuz. Dedicated 425\/26 remains the named hydrographic wreck at 26-22.55N 056-20.47E. Wednesday morning\u2019s dedicated IMO 128-count remains the first IMO print of SELAT STORM, IMO 9266657, damaged, pollution unknown. Update 111 is the first numbered JMIC print that joins 191-26 and 425\/26 on Selat Storm and adds conflicting casualty reports. Four instruments. Do not collapse them into one \u201cUKMTO named Selat Storm on 191-26\u201d sentence. Do not convert IMO\u2019s Damaged onto 425\/26 as a refloat.<\/p>\n

This is not a rewrite of 192-26, and it is not a UKMTO PDF naming of Largo Atom. Dedicated Warning 192-26 remains an unnamed Master Attack, 2347 UTC 1 November, 72 nautical miles east of Ras Al Khafji. Official MSCIO 165\/26 remains wrap. Wednesday morning\u2019s dedicated IMO 128-count remains the first IMO print of LARGO ATOM, IMO 1034747. Update 111 is wrap that now prints Largo Atom against 192-26 and attributes the identification to UKMTO. That attribution is not a public PDF revision.<\/p>\n

This is not a rewrite of 194-26, and it is not a UKMTO PDF naming of Al Jusufi. Dedicated Warning 194-26 remains an unnamed Verified Attack, 1105 UTC 2 November, Indian-crewed dhow, surviving crew rescued, vessel status unknown. Tuesday afternoon\u2019s dedicated Indian minister \/ MEA \/ DMA file remains the national-statement primary. Update 111 is the first numbered JMIC print of MSV Al Jusufi against 194-26. Do not promote an IMO number, a lat\/long or an attacker onto the PDF.<\/p>\n

This is not a rewrite of 193-26, 195-26 or 196-26. Those three Attacks remain Name withheld UFN on this note. Dedicated 193-26 remains Monday night\u2019s unnamed Lima hole. Dedicated 195-26 remains Tuesday night\u2019s unnamed Lima engine-room tanker. Dedicated 196-26 remains Thursday morning\u2019s unnamed Qatar tanker. Tonight\u2019s companion IMO 129-count is a different instrument and is not a 196-26 PDF naming.<\/p>\n

This is not an International Maritime Organization 129-count. Wednesday morning\u2019s dedicated IMO highlighted-incidents board remains 128 confirmed \/ 24 seafarer fatalities as at 3 November, until tonight\u2019s companion 129-count file. JMIC\u2019s 172 and IMO\u2019s board are different datasets. Wednesday afternoon\u2019s dedicated JMIC Advisory Note 016-26 remains the blockade visit-and-search document pack; Update 111 reprints the pack, it does not replace it. This is not Thursday morning\u2019s dedicated HNHS NAVWARN 1336\/26, and it is not Thursday morning\u2019s dedicated 797\/26 MENTOR or 790\/26 Maslen Nos files. Official MSCIO 168\/26 remains wrap, unused as dedicated. NAVAREA IX 429\/26 and 430\/26, both 051500 UTC 5 November self-cancelling notices, are unused as dedicated. ARN 165\/2026, published 5 November, is unused as dedicated.<\/p>\n

Operational implications<\/h2>\n

A numbered JMIC update is a routing and manning problem before it is a count of who was hit. Hormuz is still SEVERE, with deliberate attacks called highly likely, AIS-on targeting risk, directed hails toward the northern Iranian-controlled route, and a specific watch for attempted mining within and adjacent to the traffic-separation scheme. That guidance did not move because six more files cleared the table. The Arabian Gulf column did not move either. It stays SUBSTANTIAL. What moved is the three Attack namings \u2014 Selat Storm against dedicated 191-26 and dedicated 425\/26, Largo Atom against dedicated 192-26, MSV Al Jusufi against dedicated 194-26 \u2014 the still-withheld 193-26, 195-26 and 196-26 rows, the incident tally from a corrected 166 to 172, the congestion print from Update 110\u2019s 1 November figure of about 175 hulls at Fujairah \/ Khor Fakkan up to about 179 on 5 November, the facilitated count from 119 over 29\u201331 October to 126 over 1\u20134 November, and the GNSS colour from Windward\u2019s 29 October 174 jammed print to a 3 November 362 jammed \/ 5,921 transmitting print. Masters who still brief the region as Update 110 will have the wrong instrument in the folder. Masters who brief Thursday night as a Hormuz downgrade will have the wrong scale on the chart.<\/p>\n

The three Attack paragraphs are a briefing-discipline problem, not three new casualties. Sunday night\u2019s dedicated 191-26 left a Channel 16 Mayday unnamed. Sunday night\u2019s dedicated 425\/26 already named Selat Storm as a sunk tug. Wednesday morning\u2019s dedicated IMO 128-count printed Selat Storm as damaged, pollution unknown. Update 111 is the first numbered JMIC note that prints Selat Storm against 191-26, joins 425\/26, and adds conflicting casualty reports. Monday morning\u2019s dedicated 192-26 left the Ras Al Khafji tanker unnamed; Wednesday\u2019s IMO 128-count named Largo Atom; Update 111 now prints Largo Atom against 192-26 and attributes that identification to UKMTO. Tuesday night\u2019s dedicated 194-26 left the Indian-crewed dhow unnamed; Tuesday afternoon\u2019s dedicated Indian statements named MSV Al Jusufi; Update 111 is the first JMIC print of that dhow against 194-26. A master\u2019s pack that briefs \u201cUKMTO named Selat Storm, Largo Atom and Al Jusufi\u201d has over-read three JMIC rows. A pack that briefs Thursday morning\u2019s dedicated 196-26 as a named Qatar tanker because a later IMO sheet moved will have promoted a companion instrument onto this cut-off. Hold the PDFs, the NAVAREA, the Indian statements, the IMO 128-count, this note, and tonight\u2019s companion 129-count as separate sheets.<\/p>\n

The Fujairah density and the 229-vessel east-of-strait wait are the other operator facts. Update 111 parks that density against a Strait that printed independent cargo transits of 0, 0, 1 and 4 on 1\u20134 November and independent tanker transits of 1, 2, 2 and 1. Four Musandam Attacks in about 52 hours sit on this note, with no mass departure from the east-of-strait anchorages. Vessels stationary for extended periods, or maintaining AIS-on while static, may face elevated targeting risk. Harbour assists, wreck response and disabled-hull tows operating in that density are in the same watch as shuttle tankers. AIS-off is not a detection shield and is not an order on this note. Do not merge Selat Storm\u2019s Um Al Ghanam wreck onto the Fujairah line, and do not merge 196-26\u2019s 50-nautical-mile north-of-Madinat-ash-Shamal offset onto it.<\/p>\n

CSOs should replace the 1 November Update 110 pack with Update 111 in the master\u2019s folder and in the charterer\u2019s security clause file. The new named lines are 191-26 \/ 425\/26 SELAT STORM, tug, Attack, Mayday-relay unknown projectile, sunk approx. 0.6 NM west of Jazirat Um Al Ghanam, casualty reports conflicting; 192-26 LARGO ATOM, tanker, two unknown projectiles port side, 72 NM east of Ras Al Khafji, crew accounted for, no environmental impact; 194-26 MSV AL JUSUFI, dhow, outbound Hormuz, Royal Navy of Oman rescued surviving crew, one fatality and 13 rescued on Indian officials\u2019 line, UKMTO unaware of vessel status. The still-withheld lines are 193-26, 195-26 and 196-26. The new tally is 172 since 1 March, after the Update 110 double-count correction. The new congestion line is about 179 hulls in the vicinity of Fujairah \/ Khor Fakkan as of 5 November and about 229 stationary at the main east-of-strait anchorages. The new facilitated count is 126 U.S.-assisted Hormuz transits over 1\u20134 November. The new GNSS colour is Windward\u2019s 3 November print of 362 jammed vessels of 5,921 transmitting. None of those edits is a flag circular, a class condition, or a completed MARPOL finding. Do not replace Sunday\u2019s dedicated 191-26 PDF, Monday\u2019s dedicated 192-26, Sunday\u2019s dedicated 425\/26, Tuesday\u2019s dedicated 194-26, Thursday morning\u2019s dedicated 196-26, Wednesday\u2019s dedicated 016-26 pack, or Wednesday morning\u2019s dedicated IMO 128-count. They are different instruments. Update 111 is the numbered regional threat note that now sits on top of Update 110.<\/p>\n

For a master already shaping Musandam, holding off Fujairah or Khor Fakkan, or still needing a blockade clearance, Thursday night is a document-pack and lookout problem before it is a policy problem. 016-26 remains the working visit-and-search list. Update 111 reprints it; it does not shorten it. Channel 16, the UKMTO emergency line, the MSCIO emergency line and the company duty officer still have to be on the night orders. Registering with one mailbox is not a substitute for the other. Update 111 does not order a daylight-only transit, a deviation around a replacement for cancelled 416\/26, or a halt to visit-and-search compliance. It also does not authorise a master to treat every AIS-on tanker in the Strait as Largo Atom, or every dhow as Al Jusufi, after the fact. Thursday morning\u2019s dedicated 196-26 remains a separate unnamed Qatar Attack on this table.<\/p>\n

Charterers, P&I and war-risk underwriters will now ask whether the ship was in the Voluntary Reporting Area after 051300 UTC 5 November, whether it was off Musandam after the four-Attack cluster, whether it was 72 nautical miles east of Ras Al Khafji after the Largo Atom row, whether it held the 016-26 pack, and whether it was following BMP-MS. They will not be answered by Thursday morning\u2019s 196-26 unnamed Qatar tanker, by Wednesday\u2019s 128-count, or by a headline that three JMIC namings closed those files. Off-hire and deviation conversations that treat Update 111 as a completed Hormuz reopen, or as a UKMTO PDF naming of Selat Storm, Largo Atom and Al Jusufi, have misread the cut-off.<\/p>\n

Keep the dedicated files on their own lines. 191-26 remains the dedicated 1509 UTC unnamed Mayday-relay Attack; Selat Storm on this note, on dedicated 425\/26 and on Wednesday\u2019s IMO 128-count is wrap on that PDF, not a UKMTO naming. 192-26 remains Monday morning\u2019s unnamed Ras Al Khafji Attack; Largo Atom on this note and on Wednesday\u2019s IMO 128-count is wrap. 193-26 remains Monday night\u2019s unnamed Lima hole; MSCIO 166\/26 is wrap. 194-26 remains Tuesday night\u2019s unnamed Indian-crewed dhow Attack; Al Jusufi on this note and on Tuesday afternoon\u2019s dedicated Indian statements is wrap. 195-26 remains Tuesday night\u2019s unnamed Lima engine-room tanker. 196-26 remains Thursday morning\u2019s unnamed Qatar tanker; tonight\u2019s companion IMO 129-count is a different instrument. 190-26 remains Saturday night\u2019s unnamed fishing-vessel boarding; AZINI on this note and on Sunday morning\u2019s dedicated 161\/26 is wrap, now printed as liberated. 184-26 \/ 416\/26 remains past 032359 UTC 3 November, with no replacement warning identified. 016-26 remains Wednesday afternoon\u2019s blockade document pack. Thursday morning\u2019s dedicated 1336\/26 remains the South Aegean NG SURVEYOR line. Thursday morning\u2019s dedicated 797\/26 remains MENTOR. Do not recast 5 November night as a Hormuz reopen, as three UKMTO PDF namings, as Update 112, as an IMO 129-count on this note, or as a corridor closure.<\/p>\n

What Operators Should Note<\/h2>\n
    \n
  • Log Update 111, ICOD 051300 UTC 5 November, not a Hormuz downgrade.<\/strong> JMIC# 001 26. Filename jmic_advisory_update_111_05-nov.pdf<\/code>. Regional threat SEVERE. Hormuz SEVERE. Arabian Gulf SUBSTANTIAL. Gulf of Oman MODERATE. Arabian Sea MODERATE. Gulf of Aden SUBSTANTIAL. Bab el-Mandeb \/ southern Red Sea SUBSTANTIAL. Somali Coast \/ Somali Basin MODERATE. Northern Red Sea \/ Suez MODERATE. Eastern Mediterranean LOW. 172 incidents since 1 March after a printed correction that Update 110 should have read 166, not 167. Six counted files since Update 110 (191-26, 192-26, 193-26, 194-26, 195-26 and 196-26). Replace Update 110 in the master\u2019s pack. Do not confuse this numbered note with Wednesday morning\u2019s dedicated IMO 128-count, and do not stretch it to tonight\u2019s companion IMO 129-count.<\/li>\n
  • Type the three named Attack rows as JMIC typed them, and hold the dedicated PDFs beside them.<\/strong> SELAT STORM, tug, Mayday-relay unknown projectile, sunk approx. 0.6 NM west of Jazirat Um Al Ghanam, casualty reports conflicting; NAVAREA IX identification; dedicated 191-26 remains unnamed, dedicated 425\/26 remains the plot, Wednesday\u2019s IMO 128-count remains Damaged \/ pollution unknown. LARGO ATOM, tanker, two unknown projectiles port side, 72 NM east of Ras Al Khafji, crew accounted for, no environmental impact; \u201cidentified by UKMTO\u201d is a JMIC sourcing line, not a 192-26 PDF revision; dedicated 192-26 remains unnamed; Wednesday\u2019s IMO 128-count remains IMO 1034747. MSV AL JUSUFI, dhow, outbound Hormuz, Royal Navy of Oman rescued surviving crew, one fatality and 13 rescued on Indian officials\u2019 line, UKMTO unaware of vessel status; India\u2019s MEA identification; dedicated 194-26 remains unnamed; Tuesday afternoon\u2019s dedicated Indian statements remain the national-statement primary. Do not invent flags or IMO numbers on this note. Do not brief those three names as UKMTO PDF namings.<\/li>\n
  • Leave 193-26, 195-26 and 196-26 as Name withheld UFN on this table.<\/strong> Dedicated 193-26 remains the 9 NM northeast-of-Lima hole, vessel and crew safe; MSCIO 166\/26 is wrap. Dedicated 195-26 remains the 14 NM northeast-of-Lima engine-room tanker, no casualties. Dedicated 196-26 remains the 50 NM north-of-Madinat-ash-Shamal tanker, crew \/ damage \/ environment unconfirmed as of ICOD. Tonight\u2019s companion IMO 129-count is a different instrument. Do not promote a later IMO hull onto this 051300 UTC sheet.<\/li>\n
  • Treat the Fujairah density and the 229-vessel east-of-strait wait as live routing, not as a published closure.<\/strong> About 179 vessels were at anchor IVO Fujairah \/ Khor Fakkan as of 5 November; about 141 Dubai \/ Jebel Ali to Ras Al Khaimah; about 50 Musandam \/ Sohar; about 17 Bandar Abbas \/ Qeshm. About 229 stationary at Fujairah, Khor Fakkan, Sohar and Musandam against single-digit to low-double-digit AIS-visible transits. U.S.-facilitated Hormuz transits 1\u20134 November: 126. Independent Strait cargo series 29 October\u20134 November: 3, 4, 4, 0, 0, 1, 4. Independent tanker series: 2, 0, 4, 1, 2, 2, 1. CENTCOM as at 1 November, unchanged this period: 144 redirected, four disabled, two boarded. Do not add those series into one throughput figure. Do not restore Update 110\u2019s 490-vessel wait. Stationary AIS-on hulls may face elevated targeting risk.<\/li>\n
  • Keep the 016-26 pack, the mining watch and the reduced-but-live GNSS baseline.<\/strong> Update 111 reprints Advisory Note 016-26: last-port clearance, bill of lading, registry, agent letter, receipts or contracts, berth booking, VHF 16, 30-nautical-mile standoff from U.S. units, NAVCENT NCAGS mailbox. AIS-on targeting risk and directed hails toward the northern Iranian-controlled route remain. Attempted mining within and adjacent to the TSS remains on the outlook. Windward\u2019s 3 November print is 362 jammed vessels of 5,921 transmitting in the Gulf and Gulf of Oman, about 3 percent below its seven-day average. UKMTO\u2019s week-ending 30 October VRA report recorded four GNSS reports. No new UKMTO, MARAD, NAVCENT or NAVAREA IX GNSS\/EMI notice was issued 1\u20135 November. Cross-check with radar and visual navigation.<\/li>\n
  • Hold AZINI, Aden, 168\/26 and the eight Arabian Gulf attacks on their own lines.<\/strong> 161\/26 remains Sunday morning\u2019s dedicated AZINI hijack; 190-26 remains Saturday night\u2019s unnamed boarding; Update 110 joined them as wrap; Update 111 reprints the 2 November liberation and closed incident. 168\/26 remains wrap, unused as dedicated: large floating object, possibly a boat, surrounded by smoke in the Bab el-Mandeb on 3 November, no distress calls. 184-26 \/ 416\/26 remains past 3 November, with no replacement warning identified. Asana is still hijacked. The last confirmed Houthi merchant attack on this note remains 24 August. Eight Arabian Gulf attacks since 7 October, including 192-26 and 196-26. Four Hormuz Attacks in about 52 hours off Musandam. Do not promote a merchant target onto AZINI, and do not convert 168\/26 into a Houthi Attack.<\/li>\n
  • Do not recast Thursday night as Update 112 or as a completed early-November tape.<\/strong> 191-26 through 196-26 now sit on this table. Three of those six remain unnamed on the note. Watch a later JMIC cut-off, a UKMTO PDF that prints any of the three named hulls, a 425\/26 move of 26-22.55N, or tonight\u2019s companion IMO 129-count as a separate sheet \u2014 not a headline that Thursday night reopened Hormuz or completed three UKMTO namings.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Update 111\u2019s 051300 UTC cut-off against dedicated Warnings 191-26 through 196-26, dedicated 425\/26, Tuesday afternoon\u2019s Al Jusufi statements, and Wednesday morning\u2019s IMO 128-count so operators can treat Thursday night\u2019s Selat Storm, Largo Atom and Al Jusufi namings, the 172-incident tally and the 229-vessel east-of-strait wait as a live routing pack, not as a Hormuz reopen or a completed Update 112.<\/p>\n","protected":false},"excerpt":{"rendered":"

    The U.S. Navy-led Joint Maritime Information Center published Update 111 to its regional advisory note with an information cut-off of 051300 UTC on 5 November. The working primary retrieved this run is the numbered PDF posted on the UKMTO product board as jmic_advisory_update_111_05-nov.pdf. The face of the note is titled Update 111 to JMIC Advisory […]<\/p>\n","protected":false},"author":1,"featured_media":1233,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wpai_generated_summary":"","wpai_meta_description":"","footnotes":""},"categories":[26,20,4,6],"tags":[],"class_list":["post-1235","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-highlights","category-maritime-regulations","category-maritime-security","category-regulatory-updates"],"_links":{"self":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1235","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=1235"}],"version-history":[{"count":1,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1235\/revisions"}],"predecessor-version":[{"id":1237,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1235\/revisions\/1237"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/1233"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=1235"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=1235"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=1235"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}