{"id":1000,"date":"2026-10-14T11:33:28","date_gmt":"2026-10-14T11:33:28","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-logs-an-inbound-hormuz-container-ship-hit-after-warning-172-26\/"},"modified":"2026-10-14T11:34:28","modified_gmt":"2026-10-14T11:34:28","slug":"ukmto-logs-an-inbound-hormuz-container-ship-hit-after-warning-172-26","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-logs-an-inbound-hormuz-container-ship-hit-after-warning-172-26\/","title":{"rendered":"UKMTO logs an inbound Hormuz container-ship hit after Warning 172-26"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre issued Warning 172-26 on Wednesday, 14 October. It is an Attack product, source verified, labelled time-late. The incident date is 13 October. The incident time is 1640 UTC. UKMTO said it had received a time-late report of an incident within the Strait of Hormuz. A 50,000 tonne container ship was struck by an unknown projectile whilst conducting an inbound Strait of Hormuz transit. The vessel reports minor damage, no casualties and was able to continue on its passage. Authorities are investigating. Vessels are advised to transit with caution and report any suspicious activity to UKMTO. The official PDF named neither hull, flag, service, TEU count, cargo, projectile type, fire location, environmental impact, position nor a responsible party.<\/p>\n

That is the working primary. 172-26 is a Wednesday time-late Attack file with a printed clock, a printed size, an inbound heading, a minor-damage line, a no-casualty line and a continued-passage line. It is not a rewrite of Tuesday\u2019s dedicated Warning 170-26 and not a reprint of Monday\u2019s dedicated Warning 167-26. 170-26 was issued on 13 October as a same-day Attack product, time to be confirmed, unnamed container ship, unknown projectile, Strait of Hormuz, with no size, heading, crew, damage or environment line. 167-26 was issued 12 October as a time-late inbound container vessel struck on 11 October, with no crew, damage or environment line. Wednesday\u2019s product prints a new number, a new clock and a 50,000 tonne inbound that continued. Arab Times, writing from London on 14 October, restated the official 50,000-tonne inbound, 1640 UTC, minor-damage, no-casualty, continued-passage snapshot. Do not invent a liner, a feeder, a flag or a casualty tally to fill the remaining PDF gap.<\/p>\n

What UKMTO published on Wednesday, and what it left open<\/h2>\n

172-26 is an Attack warning, not a suspicious-activity note and not an Advisory. The verified-source line is longer than Tuesday\u2019s unnamed container file: 50,000 tonne container ship, inbound Strait of Hormuz transit, unknown projectile, minor damage, no casualties, continued on passage, investigating. Stay with the official wording \u201c50,000 tonne.\u201d UKMTO did not print deadweight, gross tonnage or a TEU count. It did not say the ship was on fire. It did not say the ship was adrift, at anchor or under tow after the hit. It did not report how many people were on board. It did not print an environmental snapshot. Those omissions remain operational facts. The new facts are the ones on the PDF: inbound, 1640 UTC, minor damage, no casualties, able to continue.<\/p>\n

Hold the source tag and the clock. 172-26 is source verified, incident date 13 October, incident time 1640 UTC, issued as a time-late report on 14 October. Incident-tracking colour first logged the warning at about 1018 UTC on 14 October, with Warning 173-26 a few minutes later. That clustering is a tape-timing observation, not a UKMTO finding that the two hulls were hit together. Arab Times treated 172-26 as a standalone inbound 50,000-tonne file. Stay with \u201cunknown projectile.\u201d UKMTO did not name a UAV, a missile, a mine or the Islamic Revolutionary Guard Corps. Do not back-fit Maritime Executive\u2019s Tuesday \u201cnorth of the Musandam Peninsula\u201d colour from the dedicated 170-26 \/ 171-26 wrap onto Wednesday\u2019s time-late PDF. UKMTO printed Strait of Hormuz. It did not print a traffic-separation-scheme lane, a Musandam range, an eastern-entrance mark or a territorial-sea call. Do not invent a latitude and longitude.<\/p>\n

The size and heading are the operational change against Tuesday\u2019s unnamed container. 170-26 printed neither. 172-26 prints 50,000 tonne and inbound. That is still not a naming. A 50,000 tonne container ship is a mid-size box ship on this desk\u2019s language, not a UKMTO finding that a main-line operator has returned to the strait. Seatrade\u2019s feeder-versus-main-line colour, first used against Monday\u2019s dedicated 167-26 inbound, remains industry read. It is not a Wednesday liner-reopening signal and not a UKMTO ship-type expansion beyond \u201ccontainer ship.\u201d<\/p>\n

A third container Attack, not a 170-26 or 167-26 reprint<\/h2>\n

This autumn\u2019s dedicated Hormuz tape on this desk was tankers, LNG and LPG, plus one Gulf of Oman bulk-carrier blockade disablement, until Monday\u2019s 167-26 inbound container. Tuesday\u2019s 170-26 was the second official container-ship Attack product on that tape, unnamed, time to be confirmed, no heading. 172-26 is the third numbered container Attack, and the first on this desk with a printed 50,000 tonne size, a 1640 UTC clock, a minor-damage line and a continued-passage line. The clocks differ. 167-26 is an 11 October inbound, issued time-late on 12 October, with no crew or damage line. 170-26 is a 13 October incident date issued the same day, time TBC, no inbound or outbound line, no size, no crew, no damage. 172-26 is a 13 October 1640 UTC inbound, issued time-late on 14 October. Do not collapse Wednesday into Tuesday. Do not brief one unnamed box-ship event spanning 11\u201314 October.<\/p>\n

Do not treat 172-26 as an Update 001 to 170-26. UKMTO issued a new number. If the 1640 UTC inbound were a fleshing-out of Tuesday\u2019s unnamed container, the usual product would be an update on 170-26, not Warning 172-26. Hold both files until UKMTO, the Joint Maritime Information Center or a flag prints one hull against both numbers. Anadolu Agency and Iran International, writing on Tuesday evening against 170-26 and 171-26, both confirmed those two 13 October notices named neither vessel and gave no casualty, damage or responsibility line. Wednesday\u2019s 172-26 is the first of the 13 October container files to print minor damage, no casualties and continued passage. That is new reporting, not a completed identification of Tuesday\u2019s unnamed hull.<\/p>\n

Update 104, information cut-off 111500 UTC on 11 October, remains the last numbered JMIC regional note on the bridge. It held the Strait of Hormuz at SEVERE, printed confirmed files through 164-26, and did not print 165-26 through 173-26. Wednesday\u2019s 172-26 sits outside that cut-off, as do Monday\u2019s four time-late warnings, Sunday\u2019s Sohar UAV, Tuesday\u2019s 170-26 \/ 171-26 and Wednesday\u2019s companion 173-26. Do not treat Update 104 as a Wednesday all-clear for a 50,000 tonne inbound. Do not rewrite Update 104 on the strength of one later container warning. NAVAREA IX 363\/26, which Update 104 assessed as likely fishermen warning shots, remains in force to 142359 UTC on 14 October. That expiry is tonight. It is not a container-ship routing order.<\/p>\n

What this is not<\/h2>\n

172-26 is not a rewrite of Tuesday\u2019s dedicated 170-26. The time-late tag, the 1640 UTC clock, the 50,000 tonne size, the inbound heading, the minor-damage line, the no-casualty line and the continued-passage line are all new. It is not Monday\u2019s dedicated 167-26 inbound container, which remains an 11 October time-late file with no crew or damage line. It is not Warning 173-26, which is Wednesday\u2019s companion time-late 19,000 tonne outbound container on a separate PDF at 1700 UTC. It is not Warning 171-26, Tuesday\u2019s unnamed tanker. It is not a naming of 166-26, 168-26 or 169-26. It is not Sunday\u2019s dedicated 164-26 CSO outbound or 165-26 Sohar UAV. It is not Advisory 163-26\u2019s Gulf of Oman military file. It is not a JMIC Update 105.<\/p>\n

Do not collapse 172-26 into Al Maqam, Valthera, Petro Dolphin, GEM NO.2, Ocean Molica, NV Sunshine or the unused Fujairah-roadstead fire colour. Those hulls sit on other dedicated or unused desks. Do not fold Wednesday\u2019s inbound container into Yanbu loadings, the UAE MPCI container-filing mandate, Japan\u2019s vessel-level permit, the 9 October OFAC\/State 22-tanker package, Oman\u2019s Article 10 AIS-on territorial-water rule, or Iran\u2019s Persian Gulf Strait Authority declaration channel. Those are crude-export, documentation, sanctions and coastal-state products. Wednesday\u2019s file is a 50,000 tonne inbound container ship, unknown projectile, in the Strait of Hormuz, minor damage, no casualties, continued on passage.<\/p>\n

Maritime Executive\u2019s Tuesday wrap of a tanker and a container ship north of Musandam, with no times, names, damage, crew status or salvage details, is colour on the dedicated 170-26 \/ 171-26 files. It is not a position for 172-26. Two Iranian officials telling Reuters that the method and pace of attacks on merchant shipping had changed, with the stated aim of impeding U.S.-sponsored oil exports, is political backdrop, not a UKMTO finding that this inbound box ship was a shuttle tanker or that IRGC named it. Anadolu\u2019s standing context \u2014 Iran\u2019s designated transit routes and the 30 May requirement for prior IRGC Navy authorisation \u2014 remains the same backdrop. Do not recast Wednesday as a confirmed IRGC naming of a liner.<\/p>\n

Operational implications<\/h2>\n

A time-late inbound container Attack with a printed 1640 UTC clock, a 50,000 tonne size, a minor-damage line and a continued-passage line is a reporting problem before it is a stowage problem. Passage plans written against Update 104 plus Monday\u2019s 167-26 inbound plus Tuesday\u2019s unnamed 170-26 still need a live 13 October 1640 UTC 50,000 tonne inbound in the master\u2019s folder. CSOs who treated 167-26 as a one-off inbound feeder event, then treated 170-26 as a second unnamed box ship with no heading, now have a third numbered container Attack with an inbound heading and a size. UKMTO did not say the three ships are related. UKMTO also did not say the threat has gone back to tankers only.<\/p>\n

Masters already committed to a Hormuz inbound, including any residual feeder or tramp box-ship of about this size, still need a written projectile watch on both sides and the after end. Citadel, fire-main isolation, boundary cooling and a lookout for a possible damaged hull in the TSS remain the standing orders even though UKMTO printed minor damage and continued passage rather than a fire. The no-casualty line is a welfare snapshot, not a completed investigation. Managers who later recognise the 172-26 hull as theirs should assume flag, class and P&I will ask for the master\u2019s report, the CSO log, the VDR, the last position before the 1640 UTC hit, whether a fire was fought, the casualty list, the damage survey, and whether the ship continued under its own power or with assistance that UKMTO did not print.<\/p>\n

Charterers still stemming Gulf boxes, or still offering a feeder into Fujairah, Khor Fakkan, Jebel Ali or Sohar, should treat Wednesday as another kinetic day on a strait that Update 104 left at SEVERE. A 50,000 tonne inbound that continued is not a reason to drop BMP, war-risk clauses or a lookout for a container ship that may be AIS-dark after a projectile hit. Hold the published hygiene from Update 104 for the strait itself: prompt answers to military queries, AIS-off is not a detection shield, and further projectile or drone risk remains on the southern Omani corridor and at UAE anchorages. Wednesday\u2019s inbound container file does not name those corridors. It also does not clear them. Do not brief the continued-passage line as a Hormuz reopen.<\/p>\n

Do not merge Wednesday with the dedicated 12 October 11:30 IMO-board count of 104, with Monday\u2019s four time-late warnings, with Tuesday\u2019s 170-26 \/ 171-26, or with Warning 173-26\u2019s 19,000 tonne outbound. 172-26 is a time-late 50,000 tonne inbound container-ship Attack product. It is not Update 105, not a Hormuz reopen, and not a liner-service restoration.<\/p>\n

What Operators Should Note<\/h2>\n