{"id":764,"date":"2026-09-21T16:51:04","date_gmt":"2026-09-21T16:51:04","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-reports-unnamed-inbound-tanker-hit-in-hormuz-as-two-crew-are-injured\/"},"modified":"2026-09-21T16:55:10","modified_gmt":"2026-09-21T16:55:10","slug":"ukmto-reports-unnamed-inbound-tanker-hit-in-hormuz-as-two-crew-are-injured","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-reports-unnamed-inbound-tanker-hit-in-hormuz-as-two-crew-are-injured\/","title":{"rendered":"UKMTO reports unnamed inbound tanker hit by projectile in Hormuz as two crew are injured"},"content":{"rendered":"

United Kingdom Maritime Trade Operations (UKMTO) said on Monday, 21 September, that military authorities had reported an inbound tanker struck by an unknown projectile while transiting the Strait of Hormuz. Two crew members sustained minor injuries. The vessel remained under its own power and was continuing to its next port of call. No environmental impact had been reported when the warning was issued. UKMTO posted the case as Warning 140-26 and advised ships in the area to transit with caution and report suspicious activity while authorities investigate.<\/p>\n

UKMTO did not name the tanker, flag, cargo, owner, manager or the precise position. Secondaries repeating the warning, including Arab News, Anadolu Agency, MarineLink and Reuters, likewise had no hull identity. That pattern matches several recent Hormuz files in which the first public product is an unnamed projectile report, with attribution and coordinates arriving later or not at all.<\/p>\n

Incident context<\/h2>\n

Monday\u2019s inbound hit lands on a waterway that is still only a trickle of its pre-war traffic. IMO Secretary-General Arsenio Dominguez told CCC 12 on 16 September that the Secretariat had verified 80 attacks on merchant ships in the Hormuz theatre since 28 February, with 22 seafarer deaths. Pre-war the strait typically handled about 125 large commercial vessels a day. Reuters, citing Kpler, reported on Monday that 17 commodity ships transited over the weekend, down from 37 a week earlier. Five vessels exited on Sunday, including the VLCC Pinios, plus two products tankers and two empty bulk\/gas carriers; two small oil tankers entered. Visible AIS is an incomplete picture: Gulf producers continue to move crude on hulls with transponders off, and CENTCOM has separately said it has assisted more than 2,000 commercial transits and moved more than a billion barrels of partner crude through the strait in recent months.<\/p>\n

Warning 140-26 is distinct from last week\u2019s unnamed files. UKMTO Warning 137-26 covered a 16 nautical mile north-east-of-Khasab incident on Thursday, 17 September. A separate Friday, 18 September product (Warning 139-26 in several secondaries) described an unnamed tanker hit by an unknown projectile, a fire that was extinguished, and all crew safe, with environmental impact unconfirmed. IRGC Navy commander Rear Adm. Ali Ozmaei named the Togo-flagged products tanker Trend (IMO 9477177) on Friday as having been hit and stopped; that claim was not independently confirmed as the UKMTO hull. Monday\u2019s product is an inbound transit with two injured seafarers and the ship still making way \u2014 a different operational picture from a fire-and-abandonment or a named IRGC interdiction.<\/p>\n

The inbound direction matters. Ships entering the Gulf are typically heading for load ports in Saudi Arabia, Iraq, Kuwait, the UAE or Qatar, or for STS and bunker calls. A projectile strike that leaves the hull under command still puts injured crew, a damaged compartment and an incomplete investigation between the master and a load berth. Engine-room hits have been a recurring feature of the 2026 Hormuz series: UKMTO previously noted that a large share of projectile strikes since early July have been on the southern Omani side of the strait, with engine rooms frequently the point of impact.<\/p>\n

Operational implications<\/h2>\n

For owners still using the waterway, Monday\u2019s warning is a reminder that \u201ccontinuing under own power\u201d is not the same as a clear passage. Two injured crew trigger medical, ISM and flag reporting even when the injuries are described as minor. Charterers and terminals will want to know whether the hull can berth, whether class and P&I have been notified, and whether the cargo system or a bunker tank was involved. With the name withheld, counterparties cannot yet screen the ship against the Persian Gulf Steering Authority non-compliance list (77 vessels as of 14 September), OFAC exposure, or recent STS history.<\/p>\n

The weekend AIS counts also show why inbound risk is not only a transit problem. Reuters reported that the Pinios was on Monday transferring about two million barrels of Iraqi Basrah crude off Fujairah to the VLCC New Constant, expected to head to China. Shuttle and STS patterns off Fujairah and Sohar remain the workaround while Hormuz stays thin and while Saudi East\u2013West \/ Petroline recoveries and Yanbu loadings remain constrained. An inbound tanker that is hit and still bound for a Gulf load port can delay a stem, force a substitute hull, or leave cargo sitting in a shuttle chain that is already short of willing owners.<\/p>\n

War-risk, crew-change and ISPS posture do not reset because one hull limps on. Liberia\u2019s ISPS Level 3 for the Red Sea and Gulf of Aden remains a separate theatre. Hormuz itself continues to mix CENTCOM-facilitated passages, AIS-off commercial movements, Iranian-route transits and occasional projectile or mine claims. Masters still have to treat UKMTO, JMIC and NAVAREA IX products as live, even when the last named casualty is days old.<\/p>\n

What Operators Should Note<\/h2>\n