The United Kingdom Maritime Trade Operations centre issued Warning 170-26 on Tuesday, 13 October. It is an Attack product, source verified, incident date 13 October, time to be confirmed. UKMTO said it had received a report of an incident within the Strait of Hormuz. A verified source reported that a container ship was struck by an unknown projectile. 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, inbound or outbound heading, fire location, crew status, damage, environmental impact, position nor a responsible party.
That is the working primary. 170-26 is a same-day Hormuz Attack file, not a time-late reprint of Monday’s dedicated Warning 167-26 and not a rewrite of Sunday’s Joint Maritime Information Center Update 104. 167-26 was issued 12 October as a time-late inbound container vessel struck on 11 October. Tuesday’s product prints a new incident date of 13 October, does not use the time-late formula, and does not print inbound or outbound. Anadolu Agency, writing later on Tuesday, and Iran International, writing the same evening, both confirmed the two 13 October notices named neither vessel and gave no casualty, damage or responsibility line. The times of both incidents remained unconfirmed. Do not invent a liner, a feeder, a flag or a casualty tally to fill the PDF gap.
What UKMTO published on Tuesday, and what it left open
170-26 is an Attack warning, not a suspicious-activity note and not an Advisory. The verified-source line is short: container ship, unknown projectile, Strait of Hormuz, investigating. That is a type change on a new numbered file, not a tanker increment. UKMTO did not say the ship was on fire. It did not say the ship was underway, adrift, at anchor or under tow after the hit. It did not report how many people were on board. It did not print a damage line or an environmental snapshot. Those omissions are the operational fact. Monday’s dedicated 167-26 inbound container also had no crew, damage or environment line. Tuesday’s product is thinner still: it does not even print a heading.
Hold the source tag and the clock. 170-26 is source verified, incident date 13 October, time TBC. Incident-tracking colour first logged the warning at about 1904 UTC on 13 October, with Warning 171-26 a couple of minutes later. That clustering is a tape-timing observation, not a UKMTO finding that the two hulls were hit together. TradeWinds published a joint read of the tanker and the container ship at 1955 UTC the same evening; Anadolu followed at 2239 UTC. Those newspapers wrapped two official products. They did not merge the files. Stay with “unknown projectile.” UKMTO did not name a UAV, a missile, a mine or the Islamic Revolutionary Guard Corps.
The geography is the Strait of Hormuz. UKMTO did not print a traffic-separation-scheme lane, a Musandam range, an eastern-entrance mark, or a territorial-sea call. Maritime Executive’s “eastern entrance” colour on Monday’s 167-26 inbound container is not on Tuesday’s PDF and should not be back-fitted onto 170-26. Do not invent a latitude and longitude. Do not brief a coastal-state finding that UKMTO did not make.
A second container Attack, not a 167-26 reprint
This autumn’s dedicated Hormuz tape on this desk has been tankers, LNG and LPG, plus one Gulf of Oman bulk-carrier blockade disablement, until Monday’s 167-26 inbound container. 170-26 is the second official container-ship Attack product on that tape. The clocks differ. 167-26 is an 11 October inbound, issued time-late on 12 October. 170-26 is a 13 October incident date, issued the same day, with no inbound or outbound line. Do not collapse Tuesday into Monday. Do not brief one unnamed box-ship event spanning 11–13 October.
Seatrade, writing on Monday’s four time-late alerts, called a box-ship hit in the Strait relatively rare, with major liner services still staying away and some smaller feeder traffic still operating. That industry colour remains the only liner-market read available. It is not a UKMTO ship-type expansion beyond “container ship,” and it is not a Tuesday finding that a main-line operator has returned. Feeder operators still offering a Gulf call should not brief a tanker-only threat inside the strait. Main-line operators who have stayed out should not treat a second unnamed hit as a liner-reopening signal. UKMTO still has not printed a service, a flag or a casualty line on either container file.
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 169-26. Tuesday’s 170-26 sits outside that cut-off, as do Monday’s four time-late warnings and Sunday’s Sohar UAV. Do not treat Update 104 as a Tuesday all-clear for a box-ship transit. 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
170-26 is not a rewrite of Monday’s dedicated 167-26. The incident dates, the time-late tag and the heading line differ. It is not Warning 171-26, which is Tuesday’s unnamed tanker on a separate PDF two minutes later on the tracker. It is not a naming of 166-26, 168-26 or 169-26. It is not Sunday’s dedicated 164-26 CSO outbound 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 170-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 Tuesday’s 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. Tuesday’s file is an unnamed container ship, unknown projectile, in the Strait of Hormuz, with no crew, damage or environment line.
Anadolu’s standing context — Iran’s designated transit routes and the 30 May requirement for prior IRGC Navy authorisation — is the political backdrop, not a UKMTO finding that this container ship was on an unauthorised lane. Iran International’s Tuesday evening read, that the Revolutionary Guards have continued to warn ships against routes Tehran considers unauthorised, is the same backdrop. Neither outlet named the 170-26 hull. Do not recast Tuesday as a confirmed IRGC naming of a liner.
Operational implications
A second container Attack with no heading, no crew snapshot and no damage line is a reporting problem before it is a stowage problem. Passage plans written against Update 104 plus Monday’s 167-26 inbound still need a live 13 October box-ship file in the master’s folder. CSOs who treated 167-26 as a one-off inbound feeder event now have a second unnamed container on a new clock. UKMTO did not say the two ships are related. UKMTO also did not say the threat has gone back to tankers only.
Masters already committed to a Hormuz transit, including any residual feeder or tramp box-ship, 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 disabled hull in the TSS remain the standing orders even though UKMTO did not print a fire. The absence of a crew-safe line is not a casualty finding. It is an incomplete welfare picture. Managers who later recognise the 170-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 hit, whether a fire was fought, the casualty list, and whether emergency power and steering were restored.
Charterers still stemming Gulf boxes, or still offering a feeder into Fujairah, Khor Fakkan, Jebel Ali or Sohar, should treat Tuesday as another kinetic day on a strait that Update 104 left at SEVERE. Do not brief the lack of a published casualty as 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. Tuesday’s container file does not name those corridors. It also does not clear them.
Do not merge Tuesday with the dedicated 12 October 11:30 IMO-board count of 104, with Monday’s four time-late warnings, or with Warning 171-26’s unnamed tanker. 170-26 is an unnamed container-ship Attack product issued the same day as the incident. It is not Update 105, not a Hormuz reopen, and not a liner-service restoration.
What Operators Should Note
- Log a new Tuesday Attack product, not a Monday reprint. Warning 170-26, 13 October, time to be confirmed, source verified, container ship in the Strait of Hormuz, unknown projectile, authorities investigating. Transit with caution and report to UKMTO. The official PDF named neither hull, flag, service, heading, crew, damage nor attacker. Do not invent those fields.
- Keep 167-26 on its own clock. Monday’s dedicated inbound container is an 11 October time-late file issued 12 October. Tuesday is a 13 October incident date with no inbound or outbound line. Seatrade’s feeder-versus-main-line colour remains industry read, not a UKMTO finding that a liner has returned. Do not brief one unnamed box-ship event spanning three days.
- Do not merge 170-26 into 171-26. The tanker warning is a separate PDF, same evening, same waterway, different type. Anadolu and Iran International wrapped both notices as unnamed, with times still unconfirmed. Tracker colour first logged 170-26 at about 1904 UTC and 171-26 about two minutes later. That is tape timing, not a combined casualty.
- Treat the missing crew and damage lines as incomplete, not as all-clear. UKMTO printed neither a crew-safe snapshot nor an environmental snapshot. Plan for a possible disabled hull in the TSS and for a welfare check that has not yet reached the warning board. The omission is not a completed MARPOL finding and not a completed casualty list.
- Do not rewrite Update 104. ICOD remains 111500 UTC 11 October. Hormuz SEVERE. 170-26 sits outside that cut-off, as do 165-26 through 169-26. Replace nothing in the master’s JMIC pack until Update 105, a UKMTO naming of 170-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 Tuesday as a UKMTO-named liner, a confirmed IRGC targeting of a box ship, a 167-26 rewrite, a Hormuz reopen, or a completed weekly tape. Anadolu’s IRGC-authorisation backdrop and Iran International’s unauthorised-route warning are political context, not a naming of this hull.
Regulas Shipping will keep lining Warning 170-26 against Monday’s dedicated 167-26 inbound container and Update 104 so operators can treat Tuesday’s unnamed box-ship hit as a second live container Attack on the Hormuz tape, not as a liner reopening or a reprint of Sunday’s time-late cluster.
