{"id":905,"date":"2026-10-05T03:32:44","date_gmt":"2026-10-05T03:32:44","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-logs-a-hormuz-engine-room-hit-after-warning-150-26\/"},"modified":"2026-10-05T03:33:45","modified_gmt":"2026-10-05T03:33:45","slug":"ukmto-logs-a-hormuz-engine-room-hit-after-warning-150-26","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-logs-a-hormuz-engine-room-hit-after-warning-150-26\/","title":{"rendered":"UKMTO logs a Hormuz engine-room hit after Warning 150-26"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre issued Warning 150-26 on Sunday, 4 October. Sourced to a master, it said a tanker transiting the Strait of Hormuz had been struck by an unknown projectile, causing damage to the engine room. The crew were reported safe. No environmental impact had been reported at the time of the warning. Authorities were investigating. Vessels were advised to transit with caution and report suspicious activity to UKMTO. The official product named neither hull, flag, cargo, projectile nor a responsible party, and it left the report date and time as to be confirmed.<\/p>\n

Arab Times, Mehr News, Middle East Eye and Reuters carried the same unnamed master report on Sunday. That is the working primary. Sunday is a new engine-room attack product, not a reprint of Friday\u2019s Warnings 148-26 and 149-26, not a rewrite of Thursday\u2019s 147-26 \/ Kazimah III file, and not a closed weekly tape. The useful facts for a DPA and a Gulf master are the engine-room damage, the unnamed hull, the SEVERE kinetic picture still sitting under the last public JMIC note, and a later NAVAREA that does name a drifting tanker. Do not invent an attacker from market colour, and do not treat an industry match as a UKMTO naming.<\/p>\n

What UKMTO published, and what NAVAREA later named<\/h2>\n

150-26 is an Attack warning, not a suspicious-activity note. The master\u2019s line is short: unknown projectile, engine-room damage, crew safe, no pollution reported. That combination is an engineering and fire-main problem before it is a naming exercise. A chief engineer has to brief loss of propulsion, emergency power, steering-gear redundancy and a disabled-hull lookout. UKMTO did not say the ship was underway after the hit, and it did not say the ship was drifting. That gap matters. Friday\u2019s 148-26 outbound tanker stayed underway after a small fire and a blackout. Sunday\u2019s product does not give operators that comfort.<\/p>\n

NAVAREA IX 352\/26, issued at 1500 UTC on 4 October, is the first official product that names a hull. It cautioned mariners that oil tanker Lipsi had been involved in a security incident and was drifting at 26\u00b023.0\u2032N 056\u00b026.3\u2032E, about 3.9 nautical miles northeast of Jazirat Um Al Fayarin, on British Admiralty charts 2851, 2888 and 3172 and Oman charts OM509 and OM1219. Treat that as a named drifting object in the Musandam approaches, not as UKMTO filling in 150-26. The two products sit on the same Sunday file. They are not the same sentence.<\/p>\n

Industry matching, not a UKMTO naming, then put a register on that NAVAREA hull. Vanguard Tech, Riviera and The Maritime Executive identified the latest Hormuz tanker as the Liberia-flag LR2 Lipsi, IMO 1025033, MMSI 636025815, call sign 5LZH2. TradeWinds said the 115,100-dwt ship had been delivered to Dynacom Tankers on 24 August, about six weeks before Sunday\u2019s report, and that a Chinese lease financier sits on the ownership line. Open particulars match a 2026 Shanhaiguan \/ DSIC Dalian newbuilding of about 249.9 by 44 metres, around 63,250 gt and 114,800 dwt, classed by DNV, registered owner Lipsi Ships Ltd, ISM and commercial manager Dynacom Tankers Management Ltd of Glyfada, P&I NorthStandard, beneficial owner linked to CMB Financial Leasing. Riviera\u2019s Equasis read put delivery and commissioning on 24 August 2026. Those particulars are register matching. They do not convert 150-26 into a UKMTO-named ship.<\/p>\n

Dynacom\u2019s recent Hormuz file is context, not Sunday\u2019s cause. Riviera recorded that the company had already confirmed two earlier 2026 hits: Kavomaleas, struck by two unknown projectiles off Oman on 20 July, and the 2026-built VLCC Acheloos. A third Dynacom hull in six weeks does not prove a named targeting list. It does tell a DPA that a newbuilding SMS, a first-voyage fire-and-blackout drill and a Chinese-lessor notice of claim are now live on the same desk.<\/p>\n

Four attacks in 72 hours, and exports still moving<\/h2>\n

The U.S.-led Joint Maritime Information Center listed up to four attacks in the Strait of Hormuz in the 72 hours from 2 to 4 October and still did not name the ships. Riviera\u2019s JMIC read of Sunday\u2019s cluster is useful colour on the unnamed tape: one inbound tanker whose master said a drone entered the funnel and dropped into the engine room, leaving a small fire and a short loss of power; one outbound tanker struck on the port quarter, smoke from the engine room, loss of power, emergency generator, a brief drift, then a tug-assisted transit toward Fujairah; and a U.S. Navy report of an outbound tanker struck on the port quarter and losing propulsion. Those lines describe a pattern of after-end and engine-room hits. They do not assign any of those four hulls to 150-26, and they do not replace the official warning. The last public numbered JMIC regional note operators still have on the bridge is Update 101, information cut-off 011500 UTC on Thursday, 1 October, which held the strait at SEVERE. No later numbered update covering 147-26 through 150-26 was on the public board at the time of writing.<\/p>\n

The Hindu, filing Reuters\u2019s Singapore copy on Monday, 5 October, said West Asian crude exports had risen above the pre-war average on four of the seven days in the final week of September, with Kpler putting those peak days between 19.5 and 22.5 million barrels a day against an 18 million bpd pre-war average. The seven-day moving average sat at 18.5 million bpd on 1 October, including Hormuz, Red Sea, terminal and Gulf of Oman ship-to-ship barrels. LNG cargoes leaving Hormuz in September were the highest monthly count since February. Those figures exclude AIS-off ships. The same copy said UKMTO had reported at least one attack a day in the Strait of Hormuz or the Gulf of Aden since 2 October, and that Marisks, writing on Saturday, had counted at least seven tanker incidents and warned of a heightened, increasingly unpredictable kinetic threat. Marisks\u2019s working theory is a predetermined engagement area, or \u201ckill box,\u201d in which weapons lock onto available radar signatures rather than a pre-selected hull. That is intelligence colour. It is not a UKMTO attribution, and it is not a reason to treat AIS-on as a shield.<\/p>\n

The Maritime Executive, writing Sunday afternoon, said Iranian forces had hit another tanker and that the recent hit rate had approached one tanker a day after weeks of relative quiet. Stay with UKMTO\u2019s unknown projectile. Do not brief Sunday as a confirmed IRGC naming. Fars and Iran International colour that named Ore Vinst, or that counted \u201cseven tankers in five days,\u201d remains increment on already-dedicated Hormuz files. Hamerintel flashes stay unused. Kazimah III remains Thursday\u2019s 147-26 matching file, not Sunday\u2019s hull. Al Funtas remains the earlier KOTC VLCC. 148-26 and 149-26 remain Friday\u2019s two unnamed master reports.<\/p>\n

Operational implications<\/h2>\n

An engine-room hit that leaves a tanker drifting 3.9 nautical miles off Jazirat Um Al Fayarin is a disabled-hull and traffic-separation problem before it is a class survey. Masters already in the southern Omani corridor, the Musandam approaches and the first miles toward Fujairah or Khor Fakkan need a written projectile watch, a fire-and-blackout drill that assumes the after end is the target, and a lookout for a named drifting LR2 that may not be easy to see if she is AIS-dark. NAVAREA IX 352\/26 is a caution to mariners, not a towage order. Riviera\u2019s JMIC colour of a tug-assisted move toward Fujairah is one possible next step for one unnamed outbound ship in the 72-hour cluster. It is not a statement that Lipsi is already in Fujairah, and it is not a pollution all-clear beyond the \u201cno environmental impact reported\u201d line in 150-26.<\/p>\n

Managers who recognise IMO 1025033 as theirs should assume flag, class, P&I and the lessor will ask for the master\u2019s 150-26 report, the VDR, the last position before the hit, the engine-room damage assessment, and whether emergency power and steering were restored. A six-week-old newbuilding does not get a first-voyage holiday. Charterers still stemming Gulf crude or products through the shuttle and Gulf of Oman STS should treat Sunday as another unnamed kinetic event on a route that is moving more barrels than the pre-war average on some days and still producing at least one UKMTO attack product a day. Do not brief that combination as a Hormuz reopen.<\/p>\n

Hold the published hygiene from Update 101: neutral transit, a 30-nautical-mile standoff from U.S. units, prompt answers to military queries, and NAVCENT NCAGS for any Iran-port humanitarian exception. AIS-on still carries elevated projectile risk in that note. Oman\u2019s Article 10 AIS-on rule inside territorial waters was not withdrawn. The two instructions do not cancel. Do not fold 150-26 into Yanbu loadings, the UAE MPCI container-filing mandate, the Premier Alliance FE1 Suez return, or Iran\u2019s Persian Gulf Strait Authority declaration channel. Those are crude-export, documentation, liner and coastal-state products. Sunday\u2019s file is an unnamed engine-room strike plus a named drifting tanker in a NAVAREA.<\/p>\n

What Operators Should Note<\/h2>\n