The United Kingdom Maritime Trade Operations centre issued Warning 173-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 1700 UTC. UKMTO said it had received a time-late report of an incident within the Strait of Hormuz. A 19,000 tonne container ship was struck by an unknown projectile whilst conducting an outbound 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.
That is the working primary. 173-26 is a Wednesday time-late Attack file with a printed clock, a printed size, an outbound heading, a minor-damage line, a no-casualty line and a continued-passage line. It is not a rewrite of Tuesday’s dedicated Warning 170-26, not a reprint of Monday’s dedicated Warning 167-26, and not a second page of Wednesday’s companion Warning 172-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. 172-26 is Wednesday’s other time-late product: a 50,000 tonne inbound at 1640 UTC. Iran International, writing at 1133 GMT+1 on 14 October, restated the official 19,000-tonne ship struck while leaving the strait, delayed report, minor damage, no casualties, continued passage. Do not invent a liner, a feeder, a flag or a casualty tally to fill the remaining PDF gap.
What UKMTO published on Wednesday, and what it left open
173-26 is an Attack warning, not a suspicious-activity note and not an Advisory. The verified-source line is specific: 19,000 tonne container ship, outbound Strait of Hormuz transit, unknown projectile, minor damage, no casualties, continued on passage, investigating. Stay with the official wording “19,000 tonne.” UKMTO did not print deadweight, gross tonnage or a TEU count. A 19,000 tonne container ship is a small box ship on this desk’s language — feeder-scale, not a main-line hull — but that is an operator read of the printed size, not a UKMTO service finding. UKMTO 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: outbound, 1700 UTC, 19,000 tonne, minor damage, no casualties, able to continue.
Hold the source tag and the clock. 173-26 is source verified, incident date 13 October, incident time 1700 UTC, issued as a time-late report on 14 October. That is twenty minutes after 172-26’s 1640 UTC inbound. Incident-tracking colour first logged 173-26 at about 1024 UTC on 14 October, a few minutes after 172-26. That clustering is a tape-timing observation, not a UKMTO finding that the two hulls were hit together or that one projectile produced two warnings. Iran International treated 173-26 as a standalone delayed report of a 19,000-tonne ship leaving the strait. Stay with “unknown projectile.” UKMTO did not name a UAV, a missile, a mine or the Islamic Revolutionary Guard Corps. Do not back-fit Maritime Executive’s Tuesday “north of the Musandam Peninsula” colour from the dedicated 170-26 / 171-26 wrap onto Wednesday’s 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.
The outbound heading is the operational change against this autumn’s container tape. Monday’s dedicated 167-26 was inbound. Tuesday’s dedicated 170-26 printed no heading. Wednesday’s 172-26 is inbound. 173-26 is the first official container-ship Attack product on this desk’s Hormuz tape that prints outbound. Seatrade’s feeder-versus-main-line colour, first used against Monday’s inbound, fits a 19,000 tonne size more closely than it fits a 50,000 tonne inbound, but it remains industry read. It is not a UKMTO finding that a named feeder operator was hit, and it is not a Wednesday liner-reopening signal.
A fourth container Attack, and the first official outbound box ship
This autumn’s dedicated Hormuz tape on this desk was tankers, LNG and LPG, plus one Gulf of Oman bulk-carrier blockade disablement, until Monday’s 167-26 inbound container. Tuesday’s 170-26 was the second official container-ship Attack product, unnamed, time to be confirmed, no heading. 172-26 is the third, a 50,000 tonne inbound. 173-26 is the fourth numbered container Attack, and the first with an outbound heading. 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. 172-26 is a 13 October 1640 UTC inbound, issued time-late on 14 October. 173-26 is a 13 October 1700 UTC outbound on the same Wednesday tape. Do not collapse the outbound 19,000 tonne file into the inbound 50,000 tonne file. Do not brief one unnamed box-ship event spanning 11–14 October.
Do not treat 173-26 as an Update 001 to 170-26. Tuesday’s unnamed container had no heading and no size. Wednesday’s 173-26 prints outbound and 19,000 tonne. UKMTO issued a new number. Hold 170-26, 172-26 and 173-26 as three distinct products until UKMTO, the Joint Maritime Information Center or a flag prints one hull against more than one number. 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’s 173-26 is the outbound container file that does print minor damage, no casualties and continued passage. That is new reporting, not a completed identification of Tuesday’s unnamed hull.
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’s 173-26 sits outside that cut-off. Update 104 had already warned that further projectile or drone incidents could affect outbound vessels in the southern Omani corridor. 173-26 does not name that corridor. It also does not clear it. Do not treat Update 104 as a Wednesday all-clear for a 19,000 tonne outbound. 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.
What this is not
173-26 is not a rewrite of Tuesday’s dedicated 170-26. The time-late tag, the 1700 UTC clock, the 19,000 tonne size, the outbound heading, the minor-damage line, the no-casualty line and the continued-passage line are all new. It is not Monday’s dedicated 167-26 inbound container. It is not Warning 172-26, which is Wednesday’s companion time-late 50,000 tonne inbound on a separate PDF at 1640 UTC. It is not Warning 171-26, Tuesday’s unnamed tanker. It is not a naming of 166-26, 168-26 or 169-26, the Monday time-late outbound tankers. It is not Sunday’s dedicated 164-26 CSO outbound tanker or 165-26 Sohar UAV. It is not Advisory 163-26’s Gulf of Oman military file. It is not a JMIC Update 105.
Do not collapse 173-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’s outbound container into Yanbu loadings, the UAE MPCI container-filing mandate, Japan’s vessel-level permit, the 9 October OFAC/State 22-tanker package, Oman’s Article 10 AIS-on territorial-water rule, or Iran’s Persian Gulf Strait Authority declaration channel. Those are crude-export, documentation, sanctions and coastal-state products. Wednesday’s file is a 19,000 tonne outbound container ship, unknown projectile, in the Strait of Hormuz, minor damage, no casualties, continued on passage.
Maritime Executive’s 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 173-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 outbound box ship was a shuttle tanker or that IRGC named it. Iran International’s Tuesday evening read against 170-26, that the Revolutionary Guards have continued to warn ships against routes Tehran considers unauthorised, is the same backdrop. Wednesday’s Iran International piece on 173-26 restated the official delayed outbound report. Neither outlet named the hull. Do not recast Wednesday as a confirmed IRGC naming of a feeder.
Operational implications
A time-late outbound container Attack with a printed 1700 UTC clock, a 19,000 tonne size, a minor-damage line and a continued-passage line is a reporting and routing problem before it is a stowage problem. Passage plans written against Update 104 plus Monday’s inbound 167-26 plus Tuesday’s unnamed 170-26 plus Wednesday’s inbound 172-26 still need a live 13 October 1700 UTC 19,000 tonne outbound in the master’s folder. CSOs who treated the container tape as inbound-only now have an official outbound box-ship hit twenty minutes after a 50,000 tonne inbound. UKMTO did not say the two Wednesday hulls are related. UKMTO also did not say the threat has gone back to tankers only.
Masters already committed to a Hormuz outbound, 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 173-26 hull as theirs should assume flag, class and P&I will ask for the master’s report, the CSO log, the VDR, the last position before the 1700 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.
The outbound heading sits on the same watch already open for Monday’s three time-late outbound tankers and for Update 104’s southern-Omani-corridor warning. 173-26 does not convert that tanker watch into a container-only watch. It adds a small outbound box ship to it. Charterers still stemming Gulf boxes, or still offering a feeder out of Fujairah, Khor Fakkan, Jebel Ali or Sohar, should treat Wednesday as another kinetic day on a strait that Update 104 left at SEVERE. A 19,000 tonne outbound 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’s outbound container file does not name those corridors. It also does not clear them. Do not brief the continued-passage line as a Hormuz reopen.
Do not merge Wednesday with the dedicated 12 October 11:30 IMO-board count of 104, with Monday’s four time-late warnings, with Tuesday’s 170-26 / 171-26, or with Warning 172-26’s 50,000 tonne inbound. 173-26 is a time-late 19,000 tonne outbound container-ship Attack product. It is not Update 105, not a Hormuz reopen, and not a liner-service restoration.
What Operators Should Note
- Log a new Wednesday time-late Attack product, not a Tuesday reprint. Warning 173-26, 13 October, 1700 UTC, source verified, 19,000 tonne container ship, outbound Strait of Hormuz, unknown projectile, minor damage, no casualties, continued on passage, authorities investigating. Transit with caution and report to UKMTO. The official PDF named neither hull, flag, service, TEU count, cargo, projectile type nor attacker. Stay with “19,000 tonne.” Do not invent those fields.
- Keep 172-26, 170-26 and 167-26 on their own clocks. Wednesday’s companion inbound is a 50,000 tonne file at 1640 UTC. Tuesday’s dedicated unnamed container is a 13 October same-day file, time to be confirmed, no size, no heading, no crew, no damage. Monday’s dedicated inbound container is an 11 October time-late file issued 12 October. Wednesday’s 173-26 is a 13 October 1700 UTC outbound with a printed size and a continued-passage line. Do not brief one unnamed box-ship event spanning three days. Do not treat 173-26 as an Update 001 to 170-26 unless UKMTO, JMIC or a flag prints one hull against both numbers.
- Do not merge 173-26 into 172-26. The inbound 50,000 tonne container warning is a separate PDF, same Wednesday tape, 1640 UTC, different size and heading. Tracker colour first logged 172-26 at about 1018 UTC on 14 October and 173-26 at about 1024 UTC. That is tape timing, not a combined casualty. Iran International restated 173-26 as the 19,000-tonne ship leaving the strait. Arab Times restated 172-26 as the inbound 50,000-tonne file.
- Treat the outbound heading as a type change on the container tape, not as a shuttle finding. This is the first official container Attack on this desk’s Hormuz file that prints outbound. Seatrade’s feeder-versus-main-line colour remains industry read from Monday’s 167-26. A 19,000 tonne size is feeder-scale on an operator read; it is not a UKMTO naming of a service. Do not recast the outbound box ship as a tanker shuttle, an IRGC mine contact, or a southern-corridor routing order.
- Treat minor damage and continued passage as a snapshot, not as all-clear. UKMTO printed no fire line, no environmental snapshot, no crew count and no position. Plan for a possible damaged hull still making way in the TSS and for a survey that has not yet reached the warning board. The omission is not a completed MARPOL finding and not a completed class condition.
- Do not rewrite Update 104. ICOD remains 111500 UTC 11 October. Hormuz SEVERE. 173-26 sits outside that cut-off, as do 165-26 through 172-26. Replace nothing in the master’s JMIC pack until Update 105, a UKMTO naming of 173-26, or a threat-level change appears. NAVAREA IX 363/26 remains in force to 142359 UTC 14 October; Update 104 assessed it as likely fishermen warning shots, not a container routing order. Stay with unknown projectile and no claim. Do not recast Wednesday as a UKMTO-named feeder, a confirmed IRGC targeting of a box ship, a 170-26 rewrite, a Hormuz reopen, or a completed weekly tape.
Regulas Shipping will keep lining Warning 173-26 against Wednesday’s dedicated 172-26 inbound, Tuesday’s dedicated 170-26 unnamed container, Monday’s dedicated 167-26 inbound and Update 104 so operators can treat Wednesday’s 19,000 tonne outbound hit as the first live outbound container Attack on the Hormuz tape, not as a liner reopening or a reprint of Tuesday’s unnamed file.
