{"id":1052,"date":"2026-10-20T03:33:38","date_gmt":"2026-10-20T03:33:38","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/imo-names-st3-as-the-confirmed-tape-hit-114\/"},"modified":"2026-10-20T03:33:38","modified_gmt":"2026-10-20T03:33:38","slug":"imo-names-st3-as-the-confirmed-tape-hit-114","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/imo-names-st3-as-the-confirmed-tape-hit-114\/","title":{"rendered":"IMO names ST3 as the confirmed tape hit 114"},"content":{"rendered":"

The International Maritime Organization\u2019s highlighted-incidents board, as at Sunday, 19 October, now prints 114 confirmed incidents in the Strait of Hormuz and the wider Middle East, with 24 confirmed seafarer fatalities. Wednesday\u2019s dedicated board piece on this desk sat at 113. The fatality line has not moved. What moved is a single named row. IMO now prints ST3, IMO 9220964, dated 16 October, 68 nautical miles from Al Jubail, damaged, no pollution. That line is the first official IMO print on the hull that India named on Friday as a Hormuz projectile hit and that JMIC Update 106 assigned on Saturday to UKMTO Warning 174-26 in the central Arabian Gulf. It does not convert ST3 into a UKMTO naming. The 174-26 PDF remains unnamed.<\/p>\n

The count is an IMO product. It is not a UKMTO warning, not a JMIC Update 107, and not a rewrite of Friday\u2019s dedicated India-ministry ST 3 file or of Saturday\u2019s dedicated Update 106. UKMTO\u2019s recent-incidents board still ends at 177-26. Update 106 remains the last numbered public JMIC note, JMIC# 001 26, ICOD 181300 UTC 18 October, Hormuz SEVERE, Arabian Gulf SUBSTANTIAL, 153 incidents since 1 March on the JMIC counter. That is a different 153 from IMO\u2019s 114. Masters who brief Tuesday as Update 107, as UKMTO finally printing ST3 on the 174-26 PDF, or as a completed 16\u201318 October tape will have misread the instrument.<\/p>\n

What the 19 October board actually adds<\/h2>\n

Wednesday\u2019s page was 113 confirmed incidents, 24 dead, with AL MAQAM and ANGOLA PROSPERITY as the operational namings of that snapshot and with GFS PRIDE, GFS GISELLE, AL SAADIYAT, DP WORLD KAVERI, KITION M, EVER VICT and PETRO DOLPHIN already on the sheet. Sunday\u2019s page is 114. One named row sits on 16 October. IMO prints ST3, IMO 9220964, 68 NM from Al Jubail, damaged, no pollution. It does not print a projectile type, a fire, a cargo, a heading, a crew count, an evacuation, a responsible party, or a UKMTO warning number. It does not print 174-26. It does not print the Friday ministry line \u201cStrait of Hormuz.\u201d Hold both geometries. Do not collapse them.<\/p>\n

The board still does not carry the rest of last week\u2019s numbered UKMTO files. Warning 175-26 remains an unnamed tanker Attack, 16 October 1922 UTC, RPG from a small boat, 78 NM northeast of Al Jubayl, damage to the aft port quarter, crew safe, complete damage and environmental impact unknown on the PDF. Warning 176-26 remains an unnamed LNG tanker Attack, 17 October 1030 UTC, 140 NM southwest of Al Mukalla on the PDF, skiff with seven persons, two shots, embarked armed security team, two warning shots, craft altered course. Warning 177-26 remains an unnamed southbound tug Attack, 18 October, time TBC, northeast of Khor Fakkan, two unknown projectiles, damage, continuing on route, one minor casualty. IMO has not converted those three files into named rows. Do not brief Sunday\u2019s 114-count as a catch-up of the Jubayl night RPG, the Mukalla LNG skiff, or the Khor Fakkan tug.<\/p>\n

CAPE DAO, IMO 9219020, already on the board from 23 September, remains printed as damaged, no pollution, one seafarer fatality, partially sunk, 15 nautical miles northeast of Khasab, Oman. That is the current board line. It is not a new 19 October Attack. Update 106 treated NAVAREA IX 380\/26 as a sinking-and-drifting caution about 33 NM northeast of Al Suwaiq and did not treat the hull as sunk. GFS PRIDE remains sunk, no pollution, Strait of Hormuz, dated 13 October. GFS GISELLE remains damaged, no pollution, 6 NM from the coast of Oman. PETRO DOLPHIN remains two seafarers missing at Sohar Anchorage. The fatality total is still 24. Cameroon Prosperity is still printed with the eight-digit IMO typo 93151598; the working seven-digit number on earlier dedicated files is 9315159. None of those rows is the 114-count move. The move is ST3.<\/p>\n

ST3 leaves the unused-list gap on the IMO sheet<\/h2>\n

ST3 is the first official IMO print on the hull. Union minister Sarbananda Sonowal\u2019s 16 October post named crude-oil tanker MT ST 3 as struck by a projectile in the Strait of Hormuz that day, with 15 Indian seafarers safe and no casualties or injuries, and with monitoring and contact with ship-management companies. The minister printed neither attacker, damage, fire, cargo, heading, IMO, flag, position nor environment. That remains the dedicated Friday India-ministry file. Do not rewrite it. IMO does not reprint the 15-safe count. IMO does not reprint \u201cStrait of Hormuz.\u201d IMO prints 68 NM from Al Jubail, damaged, no pollution.<\/p>\n

JMIC Update 106, ICOD 181300 UTC 18 October, was the first JMIC naming: M\/T ST3 on UKMTO 174-26, central Arabian Gulf, 16 October, unknown projectile approximately 68 NM northeast of Al Jubayl, all crew reported safe and evacuated, no environmental impact reported. That remains wrap on Saturday\u2019s dedicated Update 106 piece. It is not a UKMTO PDF naming. Warning 174-26, issued time-late, incident 16 October 0900 UTC, source Company Security Officer, still prints an unnamed tanker stuck or struck by an unknown projectile 68 NM northeast of Al Jubayl, all crew safe and evacuated, no reported environmental impact at the time of the report. UKMTO printed neither hull, IMO, flag, cargo, heading, fire nor attacker. Sunday\u2019s IMO row uses the same Jubayl distance and the same damaged \/ no-pollution finding. It still does not print 174-26. Put the IMO name on the company file. Do not brief a UKMTO PDF that prints the hull.<\/p>\n

Open-register colour only: ST3, IMO 9220964, MMSI 538012480, call sign V7B2912, Marshall Islands, built 2002, about 333 metres, about 159,990 gross tons and 302,977 deadweight, historical names MARJAN \/ OREN \/ Meridian Ace on earlier unused files. TradeWinds\u2019 16 October UAE-owned VLCC colour remains industry colour, not an IMO owner or dwt print. Iranian Army Navy unnamed tanker-fire messaging east of Hormuz is still messaging. It is not an IMO fire line. IMO did not print a fire. Stay with damaged, no pollution, 68 NM from Al Jubail.<\/p>\n

Hold Friday\u2019s Hormuz ministry geometry beside Sunday\u2019s Jubayl IMO row, exactly as Saturday\u2019s Update 106 piece held the ministry line beside JMIC\u2019s central-Arabian-Gulf assignment. They are two official prints on one hull, not two incidents, and not a finding that UKMTO has named the ship. Do not assign ST3 to Warning 175-26. That PDF is a different clock, a different range from Al Jubayl, an RPG from a small boat, and still unnamed. Reuters and Arab News on 17 October could not establish whether 174-26 and 175-26 were the same incident. Keep them as two numbered files. IMO has taken only ST3, and only against the 68 NM Al Jubail geometry.<\/p>\n

Operational implications<\/h2>\n

For CSOs, Sunday is the first IMO sheet that names the Jubayl tanker India identified on Friday and JMIC assigned on Saturday. Charterers, P&I and war-risk underwriters who have been holding ST3 as a ministry or JMIC match can now point to the IMO board. They still cannot point to a UKMTO PDF that prints the name. They still cannot point to Update 107. The board\u2019s pollution line on this hull is \u201cno pollution,\u201d which matches 174-26\u2019s \u201cno reported environmental impact at time of report\u201d and Update 106\u2019s \u201cno environmental impact reported.\u201d It does not close a survey. It does not print a return-aboard, a refuge port, a wreck, or a NAVAREA against ST3. NAVAREA IX 373\/26 remains the GFS Pride sink caution. NAVAREA IX 380\/26 remains the Cape Dao sinking-and-drifting caution. Neither is an ST3 product.<\/p>\n

The 114-count is also a reminder of what IMO has not yet taken. Three later UKMTO Attack products from 16\u201318 October are still unnamed on the highlighted board: the Jubayl night RPG, the Mukalla LNG skiff, and the Khor Fakkan tug with a minor casualty. Update 106 listed all four files, named only ST3, and withheld the other three names UFN. IMO has now named ST3 and has still withheld the other three. A master\u2019s pack that treats 114 as \u201cthe weekend tape is now official\u201d will over-read the board. A pack that leaves ST3 off the IMO sheet because Friday\u2019s ministry note said Hormuz will under-read it. Replace the 14 October 113-count snapshot. Do not replace Update 106. ICOD remains 181300 UTC 18 October. Hormuz remains SEVERE. The Arabian Gulf remains SUBSTANTIAL. IMO\u2019s 114 is not JMIC\u2019s 153.<\/p>\n

Do not recast 19 October as Update 107, a UKMTO 174-26 naming, a Hormuz reopen, a 175-26 \/ 176-26 \/ 177-26 conversion, a fatality-count move, a Cape Dao sink revision, or a rewrite of Friday\u2019s ST 3 ministry piece. The confirmed facts are the IMO highlighted-incidents board as at 19 October, 114 confirmed incidents, 24 confirmed seafarer fatalities, and one new named row: ST3, IMO 9220964, 16 October, 68 NM from Al Jubail, damaged, no pollution.<\/p>\n

What Operators Should Note<\/h2>\n