The U.S. Navy-led Joint Maritime Information Center published Update 105 to its regional advisory note with an information cut-off of 151300 UTC on 15 October. The note, JMIC# 001 26, is the first numbered public update since Update 104 of 11 October. Hormuz remains at SEVERE. The Arabian Gulf stays MODERATE, the Gulf of Oman MODERATE, and Bab el-Mandeb / the southern Red Sea SUBSTANTIAL. Confirmed vessel incidents since 1 March are now printed as 149, up from 140 on Update 104. The confirmed-incidents table adds nine files since the last report: UKMTO 165-26 through 173-26. Seven of those hulls are named. 165-26 is PETRO DOLPHIN. 166-26 is AL MAQAM. 167-26 is DP WORLD KAVERI. 168-26 is KITION M. 169-26 is EVER VICT. 170-26 is GFS PRIDE. 172-26 is GFS GISELLE. 173-26 is AL SAADIYAT. 171-26 remains “Name withheld UFN.”
That is the working primary. Thursday’s note is a numbered regional instrument, not a Hormuz reopen and not a rewrite of the dedicated UKMTO, MPA, IMO-board or Update 104 pieces. It is also not the International Maritime Organization’s highlighted-incidents board, which on Wednesday printed a confirmed count of 113. Those are different counters. The useful facts for a DPA and a bridge team are the unchanged SEVERE/MODERATE split, the first JMIC namings of Petro Dolphin, Al Maqam, DP World Kaveri, Kition M, Ever Vict, GFS Pride, GFS Giselle and Al Saadiyat against numbered UKMTO products, the first JMIC assignment of Pride to 170-26 and of Giselle to 172-26, the Cape Dao “disputed, but she is not sunk” line, the wreck caution at 26-16.8N 056-08.6E, and the expanded UAE-anchorage and southern-Omani-corridor watch. Do not treat industry matching, MPA flag-state notes or the IMO 113-count as a substitute for this numbered note, and do not treat UKMTO’s original unnamed PDFs as if they had printed these hulls.
What Update 105 actually added
Update 104’s information cut-off was 111500 UTC on 11 October. It already carried 159-26 through 164-26, named GEM NO.2 and Ocean Molica, and left 159-26, 162-26 and 164-26 unnamed. Update 105 does not reprint that table and does not downgrade Hormuz. It adds the next nine products that had cleared confirmation by 151300 UTC on 15 October.
On 165-26, Update 105 names PETRO DOLPHIN. That is the first JMIC naming of the hull that sat as the dedicated 12 October Sohar UAV Attack file. The numbered note places a products tanker at or in the vicinity of the Sohar anchorage. UKMTO received a report that on 11 October the ship was struck by a UAV, leading to the evacuation of the crew. India’s Ministry of External Affairs reported two crew members missing. NAVAREA IX 372/26 reported that as of 14 October the vessel was drifting about 50 nautical miles northeast of Sohar. The dedicated 165-26 piece remains the original Sunday product and the later Indian 11/9/2 count. Update 105 does not print the missing seafarers’ names, an IMO number, a pollution volume or a wreck position. Open-register colour only, already used on this desk: do not treat the naming as a completed SAR, a UKMTO PDF naming, or a rewrite of the dedicated Sohar file.
On 166-26, Update 105 names AL MAQAM. That is the first JMIC naming of the hull that the IMO highlighted-incidents board printed on Wednesday against an 11 October Strait geometry, and it is not a rewrite of the dedicated 13 October 03:30 Warning 166-26 piece, which remained an unnamed outbound tanker Attack. The numbered note says the tanker was struck by an unknown projectile while transiting the Strait of Hormuz outbound on 11 October. No crew injuries reported. Vessel damage and environmental impact unknown. Tasnim / IRGC video colour and the ADNOC L&S no-comment line stay colour on the dedicated 166–169 file. They are not a JMIC attribution. Open-register colour only, already used on this desk: IMO 9732577. That is particulars colour, not a JMIC IMO print.
On 167-26, Update 105 names DP WORLD KAVERI. First JMIC naming of the India-flag container that the IMO board printed on Wednesday. Inbound Strait of Hormuz, unknown projectile on 11 October, one minor crew injury, vessel continued its voyage, no environmental damage reported. The dedicated 13 October 03:30 Warning 167-26 piece remains the original time-late unnamed inbound-container product. Update 105 does not print an IMO number, a TEU figure or a projectile type.
On 168-26, Update 105 names KITION M. First JMIC naming of the Panama products tanker that the IMO board printed on Wednesday. The table dates the row 12 October; the narrative dates the strike 11 October, outbound, unknown projectile, vessel continued, reports of environmental damage unconfirmed. Hold both clocks on the same named file. The dedicated 13 October 03:30 Warning 168-26 piece remains the original unnamed product. Riviera’s 168-26 match stays colour. It is not a UKMTO PDF naming.
On 169-26, Update 105 names EVER VICT. First JMIC naming of the Bahamas crude tanker that the IMO board printed on Wednesday. Outbound Strait of Hormuz on 11 October, unknown projectile, reports of crew injuries unconfirmed, vessel self-reported as not under command. The dedicated 13 October 03:30 Warning 169-26 piece remains the original unnamed product. Update 105 does not convert the unconfirmed injury line into a casualty tally and does not print a pollution volume.
On 170-26, Update 105 names GFS PRIDE. That is the first JMIC assignment of a hull to the dedicated 14 October 03:30 unnamed-container Warning 170-26 piece, and it is not a rewrite of Wednesday’s dedicated MPA flag-state note. The numbered note says a container ship, identified by the IMO as GFS PRIDE, was struck by an unknown projectile on 13 October while transiting the Strait of Hormuz outbound. NAVAREA IX 373/26 reported the vessel sank, resulting in floating container debris about 4 nautical miles northwest of Ras Shaykh Masud. All crew evacuated with no injuries. Status of vessel debris, cargo and environmental pollution unconfirmed. The original UKMTO PDF named neither hull, flag, heading, fire, crew, damage nor a responsible party. The MPA note used Singapore time for a 13 October Pride strike, a fire, a sink, 21 crew evacuated and no injuries, and did not print an IMO number or a wreck position. Keep all three instruments. Do not collapse them. Open-register colour only, already used on this desk: Singapore-flag GFS Pride, IMO 9349045, about 28,340 gt / 39,446 dwt. That is particulars colour, not a JMIC IMO print.
On 171-26, Update 105 still withholds the name. An outbound tanker in the Strait of Hormuz was struck by an unknown projectile on 13 October. The vessel was able to continue its voyage. No crew injuries reported. The dedicated 14 October 03:30 Warning 171-26 piece remains the original unnamed tanker Attack product. Update 105 adds a heading, a continued-voyage line and a no-injury line. It does not print a size, a flag or a damage assessment.
On 172-26, Update 105 names GFS GISELLE. First JMIC assignment of a hull to the dedicated 14 October 11:30 Warning 172-26 piece, which remained a time-late unnamed 50,000-tonne inbound container, minor damage, no casualties, continued on passage. The numbered note says a container ship, identified by the IMO as GFS GISELLE, was struck by an unknown projectile on 13 October while transiting inbound. Minor damage reported but the vessel continued its voyage. No crew injuries or environmental impact reported. The MPA flag-state note placed Giselle on 14 October Singapore time, hull damage, own propulsion to a safe anchorage, 22 crew safe. Hold both clocks. Open-register colour only, already used on this desk: Singapore-flag GFS Giselle, IMO 9704661, about 44,887 gt / 54,117 dwt. The 50,000-tonne line on the original PDF is in the same size band. That is particulars colour, not a reason to treat the UKMTO PDF as a named product.
On 173-26, Update 105 names AL SAADIYAT. First JMIC assignment of a hull to the dedicated 14 October 11:30 Warning 173-26 piece, which remained a time-late unnamed 19,000-tonne outbound container, minor damage, no casualties, continued on passage. The table dates the UKMTO product 14 October; the narrative dates the strike 13 October, outbound, unknown projectile, minor damage, continued, no crew injuries or environmental impact. Hold both clocks. The IMO board printed Al Saadiyat on Wednesday against a 13 October geometry about 1 nautical mile off Oman. Open-register colour only: Marshall Islands-flag Al Saadiyat, IMO 9760598, MMSI 538012603, about 18,870 gt / 23,504 dwt, about 170 × 28 metres, 2016. The 18,870 gt figure sits next to the original PDF’s 19,000-tonne line. That is particulars colour, not a JMIC IMO print. GFS Ship Management FZE as commercial and ISM manager is industry colour on the same open registers. It is not a JMIC company naming and not a reason to merge 173-26 into the dedicated Pride / Giselle MPA file.
What sits off the list, and the traffic that moved
Thursday’s cut-off is 151300 UTC on 15 October. UKMTO still has no 174-26 or later product on the public warnings board used for this desk. Update 105 does not print Angola Prosperity, Valthera, Gem No. 2’s IMO number, or a new Bab el-Mandeb Attack. Angola Prosperity remains the dedicated 15 October 03:30 IMO-board naming against an 11 October geometry 8 nautical miles off Oman. It is still not a JMIC or UKMTO naming of 164-26. 159-26, 162-26 and 164-26 remain unnamed on Update 104’s table; Update 105 does not reopen them.
The Strait of Hormuz operational summary is the other operator paragraph. Eight unknown-projectile attacks occurred on two days, UKMTO 166-26 to 173-26: four strikes on 11 October, three tankers and one container ship, and four strikes on 13 October, three container ships and one tanker. GFS Pride, cited against 170-26, NAVAREA IX 373/26 and HYDROPAC 2978/26, caught fire, drifted and sank on 14 October. The threat to merchant shipping remains SEVERE. IRGC attacks, attempted attacks and harassment persisted, including UAV overflight, targeted surveillance and occasional VHF hailing. On 14 October the IRGC claimed that a container ship struck a naval mine on an unauthorised route; Update 105 prints “there is no substantiation to this claim.” Stay with that. CENTCOM’s separate public line, as carried by gCaptain on 15 October, that M/V GFS Pride was hit by an IRGC projectile and sank while being towed is a military statement on the same hull. It is not the JMIC table’s wording. The numbered note still says unknown projectile. Do not convert either line into a completed flag-state finding.
Cape Dao is the increment that cuts against Wednesday’s IMO-board piece rather than repeating it. The Gulf of Oman summary says NAVAREA IX 370/26 and HYDROPAC 2970/26 reported that the bulk carrier CAPE DAO (UKMTO 142-26) sank; “her status remains disputed, but she is not sunk.” The dedicated 15 October 03:30 IMO 113-count piece recorded a status change to Sunk on the 23 September row, one fatality, no pollution, with NAVAREA IX 370/26 at 131520 UTC on 13 October printing a sinking at 24-44.2N 056-47.7E. Hold both instruments. Do not brief a completed wreck survey. Do not merge Cape Dao with GFS Pride. They are different hulls, different dates and different products.
Blockade hygiene is unchanged in the published CENTCOM tally and tighter in the last-96-hours line. The latest official CENTCOM figures cited in Update 105, dated 10–11 October, remain 135 commercial vessels redirected and four disabled during blockade enforcement. No further CENTCOM blockade-enforcement action was announced in this period. On 14 October CENTCOM reported that U.S. forces had destroyed an Iranian-affiliated dhow conducting surveillance of U.S. Navy ships in the Gulf of Oman on 6 October; the crew was removed before the strike. That is a surveillance-dhow line, not a fifth commercial disablement. Neutral transit remains permitted. Visit-and-search, a 30-nautical-mile standoff from U.S. units, AIS-on unless constrained by security threats, continuous monitoring of VHF Channel 16, and a humanitarian-cargo exemption via NAVCENT NCAGS are still the published tools. Approved humanitarian vessels may transit to Iranian ports but remain subject to inspection and may not load cargo in Iran beyond fuel and stores.
Strait of Hormuz traffic is still a split series. Independent tracking still shows single-digit numbers each way against a 2025 baseline of about 138 vessels a day. U.S. NCAGS data indicated U.S.-assisted flows averaging about 30 vessel transits a day for the last 96 hours. U.S.-facilitated Strait of Hormuz transits for 11–14 October are printed as 121. Do not add the 121 and the independent single-digit series. CENTCOM’s separate 15 October public line of more than 40 commercial ships in the past 24 hours, as carried by gCaptain, covers a different clock and is not a replacement for the 121. The annex cargo-vessel table, drawn from S&P Maritime / SeaVision for non-facilitated traffic above 1,000 dwt excluding Iranian-port calls adjacent to the strait, shows Strait of Hormuz daily totals of 5, 3, 2, 2, 2, 4 and 1 from 8 to 14 October. Tanker-only Hormuz rows stay thinner: 2, 1, 1, 2, 0, 1 and 1 across the same week. Bab el-Mandeb cargo transits for 11–14 October are 117 against a 2023 baseline of about 61 a day.
Port and anchorage congestion is printed as of 15 October: about 180 vessels at anchor in the vicinity of Fujairah / Khor Fakkan, 178 off Dubai / Jebel Ali to Ras Al Khaimah, and 74 in the vicinity of Musandam / Sohar. GNSS interference remains elevated across the Arabian Gulf and the Strait of Hormuz. No new specific UKMTO, MARAD, NAVCENT or NAVAREA IX GNSS/EMI notices were issued 11–15 October. Baseline advisories remain in force. Live-weapon firing is scheduled off Karachi on 16–17 October under NAVAREA IX 374/26; that is a routine notice, not a dedicated Attack file. MT ASANA, the Tanzanian-flag product/chemical tanker hijacked on 17 July about 65 nautical miles southwest of Mukalla, is still the one merchant vessel remaining hijacked. Yanbu loadings as of the morning of 6 October remain 5.8 million barrels, confirmed by Saudi Arabia’s energy minister. Suez remains functional both ways. On 13 October the Saudi-led Coalition struck Houthi fuel facilities in Hudaydah, reported to include fuel-unloading berths or piers. Bab el-Mandeb / southern Red Sea stays SUBSTANTIAL.
Operational implications
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 Pride was named. What moved is the geography of the last 96 hours on JMIC’s own account: eight confirmed Hormuz projectile Attacks on two days, a named UAV Attack at Sohar, a named wreck with floating containers inside the southern corridor, and an outlook that now names tankers and container ships, inbound as well as outbound.
The outlook paragraph is the line that should replace Update 104’s version in the master’s pack. If the present pattern persists, additional projectile or drone incidents could affect tankers and container ships at UAE anchorages — Ras Al Khaimah, Umm al Quwain, Sharjah, and possibly Fujairah — and both outbound and inbound vessels in the southern Omani corridor. Update 104’s watch was tankers at those anchorages and outbound ships in the southern corridor. Thursday adds containers and inbound transits. Vessels transiting with AIS-on can expect elevated targeting risk and directed hails instructing them to divert toward the northern Iranian-controlled route. Mariners are cautioned of the wreck of GFS Pride and floating containers in the vicinity of 26-16.8N 056-08.6E, NAVAREA IX 373/26 and HYDROPAC 2982/26. Night transits, restricted-visibility transits, and any AIS-off routing through that box now carry a named debris field on the current JMIC note, not only on the NAVAREA.
The IRGC mine claim is a briefing-discipline problem. Update 105 prints no substantiation. The same note still tells mariners to remain vigilant for mining activity within and adjacent to the TSS. Those two sentences can sit together. A master’s pack that briefs “JMIC ruled out mines” has over-read the unsubstantiated-claim line. A pack that briefs a confirmed mine on Pride has over-read the IRGC statement. Stay with unknown projectile on the named Pride row, no substantiation on the 14 October IRGC claim, and a standing mining watch.
CSOs should replace the 11 October Update 104 pack with Update 105 in the master’s folder and in the charterer’s security clause file. The new named lines are Petro Dolphin on 165-26, Al Maqam on 166-26, DP World Kaveri on 167-26, Kition M on 168-26, Ever Vict on 169-26, GFS Pride on 170-26, GFS Giselle on 172-26 and Al Saadiyat on 173-26. The still-unnamed line is 171-26, outbound tanker, continued, no injuries. None of those edits is a flag circular, a class condition, or a completed MARPOL finding. Do not replace the dedicated MPA Pride / Giselle note, the dedicated IMO 113-count, or the original UKMTO PDFs. They are different instruments. Update 105 is the numbered regional threat note that now sits on top of them.
Do not recast Thursday as a UKMTO naming in the original PDFs, as a Hormuz reopen, as a completed Cape Dao wreck survey, as a rewrite of Warning 165-26 through 173-26, as a rewrite of the MPA flag-state note, or as a substitute for Wednesday’s IMO 113-count. IMO’s 113 and JMIC’s 149 are different datasets. gCaptain said as much on 15 October. Masters who brief Thursday as Update 104 still in force, or as UKMTO finally printing Pride on the 170-26 PDF, will have misread the instrument.
What Operators Should Note
- Log Update 105, ICOD 151300 UTC 15 October, not a Hormuz downgrade. JMIC# 001 26. Hormuz SEVERE. Arabian Gulf MODERATE. Gulf of Oman MODERATE. Bab el-Mandeb / southern Red Sea SUBSTANTIAL. 149 incidents since 1 March, nine since Update 104. Replace Update 104 in the master’s pack. Do not confuse this numbered note with the IMO highlighted-incidents board’s Wednesday count of 113.
- Name only the hulls JMIC named, against the products it named. 165-26 PETRO DOLPHIN, Sohar UAV, crew evacuated, two missing per India MEA, drifting about 50 nautical miles northeast of Sohar as of 14 October. 166-26 AL MAQAM, outbound Hormuz, unknown projectile, no injuries, damage and environment unknown. 167-26 DP WORLD KAVERI, inbound container, one minor injury, continued. 168-26 KITION M, outbound products, continued, environmental damage unconfirmed; hold the 11 October strike / 12 October table clocks. 169-26 EVER VICT, outbound crude, injuries unconfirmed, not under command. 170-26 GFS PRIDE, outbound container, sank, floating containers about 4 nautical miles northwest of Ras Shaykh Masud, all crew evacuated. 172-26 GFS GISELLE, inbound container, minor damage, continued. 173-26 AL SAADIYAT, outbound container, minor damage, continued; hold the 13 October strike / 14 October UKMTO-date clocks. 171-26 remains unnamed: outbound tanker, continued, no injuries.
- Keep the original UKMTO PDFs unnamed. 170-26 through 173-26 did not print hulls. The MPA flag-state note is still the dedicated Pride / Giselle primary for crew counts, fire and own-propulsion to anchorage. JMIC’s assignment of Pride to 170-26 and Giselle to 172-26 is a numbered-note matching, not a retroactive edit of those PDFs. Al Saadiyat’s 18,870 gt sitting next to 173-26’s 19,000-tonne line is particulars colour. Angola Prosperity is still off this table.
- Treat Cape Dao as disputed on this note, sunk on the IMO board and on NAVAREA IX 370/26. Update 105: status remains disputed, but she is not sunk. Wednesday’s IMO 113-count: Sunk, one fatality, no pollution. Do not merge Cape Dao with GFS Pride. Do not brief a completed wreck survey. Put both lines in the master’s pack until a flag, class or a later numbered note closes the disagreement.
- Do not add Thursday’s traffic and blockade numbers into one throughput figure. NCAGS about 30 transits a day over 96 hours. U.S.-facilitated Hormuz transits 11–14 October: 121. Independent series still single-digit each way. BAM cargo transits 11–14 October: 117. CENTCOM 10–11 October blockade line remains 135 redirected, four disabled. The 14 October dhow strike is a surveillance-craft line, not a fifth commercial disablement. Congestion as of 15 October: about 180 Fujairah / Khor Fakkan, 178 Dubai / Jebel Ali to Ras Al Khaimah, 74 Musandam / Sohar. NAVAREA IX 374/26 is Karachi live-weapon firing 16–17 October, not an Attack product. Asana is still hijacked. Yanbu 5.8 million barrels as of 6 October morning is still a pipeline-recovery line.
- Treat the UAE-anchorage, inbound-corridor and Pride-wreck watches as live routing, not as a published closure. Update 105 now says further projectile or drone incidents could affect tankers and container ships at Ras Al Khaimah, Umm al Quwain, Sharjah and possibly Fujairah, and both outbound and inbound ships in the southern Omani corridor. AIS-off is not a detection shield. The wreck and floating containers at 26-16.8N 056-08.6E sit inside that corridor. The 30-nautical-mile standoff from U.S. units and the NCAGS humanitarian exemption are still blockade procedure. The IRGC mine claim is unsubstantiated; the mining watch is still in force.
Regulas Shipping will keep lining Update 105’s 151300 UTC cut-off against UKMTO 165-26 through 173-26 so operators can treat Thursday’s named hulls, the Pride wreck caution and the expanded UAE-anchorage watch as a live routing pack, not as a Hormuz reopen or a retroactive naming of the original UKMTO PDFs.
