The United Kingdom Maritime Trade Operations centre issued Warning 156-26 on Monday, 5 October. Sourced to a master, it said a tanker transiting the Strait of Hormuz had been struck by an unknown projectile at 1637 UTC, causing a fire in the engine room which the crew were fighting. No casualties or 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.
gCaptain, The Maritime Executive, Iran International, dpa and Moneycontrol carried the same unnamed master report on Monday evening. That is the working primary. Monday’s 1637 UTC product is a new engine-room fire warning, not a reprint of Sunday’s Warning 150-26, not a rewrite of Friday’s 148-26 and 149-26, and not a closed weekly tape. The useful facts for a DPA and a Gulf master are the live fire in the engine room, the unnamed hull, and a JMIC picture that is still SEVERE on the Omani side of the strait. Do not invent an attacker from market colour, and do not treat an industry location as a UKMTO naming.
What UKMTO published on Monday, and what it did not
156-26 is an Attack warning, not a suspicious-activity note. The master’s line is short: unknown projectile, engine-room fire, crew still fighting it, no casualties, no pollution reported. That combination is a fire-main and blackout problem before it is a naming exercise. A chief engineer has to brief boundary cooling, CO2 or equivalent, emergency power, steering-gear redundancy and a disabled-hull lookout while the after end is still alight. UKMTO did not say the fire was out. It did not say the ship was underway. It did not say the ship was drifting. Sunday’s 150-26 product reported engine-room damage with the crew safe. Monday’s product reports an engine-room fire still being fought. Treat those as two warnings, not one hull with a delayed update.
The Maritime Executive, writing at 1556 UTC, placed the strike off the Musandam Peninsula. Stay with UKMTO’s geography: Strait of Hormuz. Musandam is industry colour on where Monday’s after-end hits have clustered. It is not a UKMTO position, and it is not a NAVAREA. No NAVAREA IX product naming Monday’s hull was on the public board at the time of writing. Do not borrow Sunday’s Lipsi / NAVAREA IX 352/26 drifting-object file for 156-26.
Stay with unknown projectile. The Maritime Executive’s opening line that Iran had added another strike, and Eurasia Group analyst Gregory Brew’s count of 11 ships hit since the previous Wednesday, are secondary assessments. They are not a UKMTO attribution. Fars and Iran International colour that named Ore Vinst, or that counted “seven tankers in five days,” remains increment on already-dedicated Hormuz files. Hamerintel flashes stay unused.
Three time-late attack products, then the live fire
156-26 did not arrive alone. Earlier on Monday UKMTO issued three time-late Attack warnings, all unnamed, all Strait of Hormuz, all verified-source rather than master-sourced:
- Warning 153-26: an inbound LPG tanker struck by an unknown projectile at 1716 UTC on 4 October.
- Warning 154-26: a crude oil tanker struck by unknown projectiles at 1907 UTC on 4 October. The official product uses the plural.
- Warning 155-26: a crude oil tanker struck above the waterline by an unknown projectile on 3 October, time to be confirmed.
gCaptain, filing Monday afternoon and again after 156-26, treated those three as delayed reports and flagged 155-26 in particular: because 3 October already had several recorded tanker attacks, it was not immediately clear whether the above-waterline crude was a previously unreported hull or an overlap with an incident already on the UKMTO and JMIC tapes. Hold that uncertainty. Do not add 155-26 as a confirmed extra ship in a running count, and do not collapse 153-26 and 154-26 into one Saturday evening event. They are less than two hours apart, one LPG inbound and one crude, and 154-26’s “projectiles” is not the same sentence as 153-26’s single projectile.
Taken together with Advisory 152-26, which is a separate IRGC hail-and-turn-back file, gCaptain counted four attack notices and one direct threat disclosed on Monday, three of the attacks having occurred on 3 and 4 October. That is a reporting-day count, not a finding that four new hulls were hit at 1637 UTC.
Update 102 is now the last numbered JMIC note, and it stops at 150-26
The last public numbered Joint Maritime Information Center regional note operators have on the bridge is Update 102, information cut-off 041500 UTC on Sunday, 4 October, which held the Strait of Hormuz at SEVERE. It listed four confirmed attacks or disruptions in the previous 72 hours: 147-26, 148-26, 149-26 and 150-26, names withheld until further notice, all unknown-projectile strikes on tankers, attacks along the Omani side of the strait continuing. JMIC’s own narratives in that note are useful pattern colour and should not be back-fitted onto Monday’s unnamed fire: 147-26 outbound, fire, crew evacuated, tugs on firefighting and salvage, Oman Maritime Security Centre confirming the projectile; 148-26 inbound, a drone entering the funnel and dropping into the engine room, small fire, short loss of power; 149-26 outbound, port-quarter hit, engine-room smoke, loss of power, emergency generator, brief drift, then tug-assisted toward Fujairah; 150-26 outbound, U.S. Navy NCAGS, port-quarter projectile, lost propulsion. No crew casualties and no environmental damage were reported in those four lines. 153-26, 154-26, 155-26 and 156-26 sit outside Update 102’s cut-off. Do not treat Update 102 as a Monday all-clear, and do not treat its 150-26 NCAGS line as a rewrite of Sunday’s dedicated 150-26 engine-room-damage article.
The same note is the working traffic picture until a later numbered update appears. Independent tracking showed single-digit transits in each direction. U.S. NCAGS data put traffic at about 32 vessel transits a day over the previous 72 hours, against a 2025 baseline of about 138 a day. U.S.-facilitated Strait of Hormuz transits for 1–3 October were given as 95. IRGC UAV overflight, targeted surveillance and occasional VHF hailing persisted. AIS-on still carried elevated targeting risk and directed hails toward the northern Iranian-controlled route. Mining watch in and adjacent to the TSS remained in the outlook. A 30-nautical-mile standoff from U.S. units remained the published hygiene. Neutral transit is permitted; unauthorized entry or departure from Iranian ports is not.
U.S. Central Command, in a Tampa release dated 5 October, said its forces had redirected the 130th commercial vessel the same day under the naval blockade of ships attempting to enter or depart Iranian ports, resumed on 14 July. Three ships that refused to comply had been disabled. Over the previous 12 weeks, CENTCOM said it had destroyed 13 commercial vessels that it described as violating the blockade or part of an IRGC shadow network. Adm. Brad Cooper said forces would “swiftly act against any vessels trying to run the blockade.” Mariners were told to monitor Notices to Mariners and to call U.S. naval forces on VHF Channel 16 in the Gulf of Oman and Strait of Hormuz approaches. Update 102 had still been carrying the 30 September figure of 125 redirected. Monday’s 130 is the new official count. It is a blockade-enforcement product, not a 156-26 naming, and it does not convert a Hormuz transit into a Iran-port call.
The Maritime Executive’s shuttle-convoy colour is operational context, not a cargo finding on Monday’s unnamed tanker. UAE, Saudi, Kuwaiti and more recently Iraqi interests have been using a smaller number of risk-tolerant tankers on round trips between Gulf loading piers and the Fujairah anchorage, where cargo is transferred onto long-haul ships. The same copy said satellite counts had largely restored net Gulf exports to pre-war volumes by the end of September, and asked whether the latest strikes would disable that tonnage or deter crews. Do not brief that as a Hormuz reopen, and do not assign Monday’s fire to a named shuttle hull.
Operational implications
An engine-room fire that is still being fought at the time of the warning is a different night order from engine-room damage already contained. 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 disabled tanker that may not be easy to see if she is AIS-dark. Citadel, fire-main isolation, emergency generator and steering-gear redundancy are the standing orders. A live fire also means a possible request for tugs and a possible pollution watch even though 156-26 reported no environmental impact at warning time. That line is a snapshot, not a completed MARPOL finding.
LPG charters should read 153-26 as a separate inbound gas-tanker product on Sunday afternoon, not as colour on Monday’s crude-or-products fire. Crude operators should read 154-26’s plural projectiles and 155-26’s above-waterline hit as two more unnamed attack products, one of them still possibly overlapping an earlier 3 October file. None of those three time-late warnings reported casualties, pollution, or a named hull. Do not wait for a UKMTO name before putting the after-end hit pattern into the passage plan.
Managers who later recognise the 156-26 hull as theirs should assume flag, class and P&I will ask for the master’s report, the VDR, the last position before the hit, the fire-extinguishing log, and whether emergency power and steering were restored. Charterers still stemming Gulf crude, products or LPG through the shuttle and Gulf of Oman STS should treat Monday as another unnamed kinetic day on a route that Update 102 still rates SEVERE. Do not brief the combination of restored export volumes and continuing attack products as a reason to drop BMP, war-risk clauses or the 30-nautical-mile U.S.-unit standoff.
Hold the published hygiene from Update 102: neutral transit, prompt answers to military queries, NAVCENT NCAGS for any Iran-port humanitarian exception, and no cargo loaded in Iran beyond fuel and stores on an approved exemption. Oman’s Article 10 AIS-on rule inside territorial waters was not withdrawn. The two instructions do not cancel. Dark mitigation against projectile risk becomes a compliance problem inside 12 nautical miles. Do not fold 156-26 into Yanbu loadings, the UAE MPCI container-filing mandate, the Premier Alliance FE1 Suez return, Japan’s 35-ship vessel-level permit, or Iran’s Persian Gulf Strait Authority declaration channel. Those are crude-export, documentation, liner, sanctions and coastal-state products. Monday’s file is an unnamed engine-room fire plus three time-late unnamed attack warnings.
What Operators Should Note
- Log a new Monday attack product, not a reprint of Sunday. Warning 156-26, 5 October, 1637 UTC, master, tanker in the Strait of Hormuz, unknown projectile, engine-room fire the crew were fighting, no casualties, no pollution reported at the time. Transit with caution and report to UKMTO. Do not invent a name, flag or attacker to fill the UKMTO gap, and do not treat it as an update to 150-26.
- Keep the three time-late warnings on their own lines. 153-26: inbound LPG, 1716 UTC 4 October, unknown projectile. 154-26: crude, 1907 UTC 4 October, unknown projectiles. 155-26: crude, 3 October, time TBC, struck above the waterline; gCaptain correctly flags a possible overlap with an earlier 3 October file. Do not add 155-26 to a ship count until UKMTO or JMIC separates it.
- Update 102 is now the last numbered JMIC note, ICOD 041500 UTC 4 October, still SEVERE. It covers 147-26 through 150-26 only. Funnel-to-engine-room and port-quarter / after-end hits are the working pattern in that note. 153-26 to 156-26 sit outside the cut-off. Independent transits remain single-digit; NCAGS about 32 a day versus a 2025 baseline of about 138.
- Brief fire, blackout, loss of propulsion and a disabled-hull lookout off Musandam. Citadel, fire-main isolation, emergency generator and steering-gear redundancy are the night orders. UKMTO did not say the fire was out and did not say the ship was underway. ME’s Musandam colour is not a position fix.
- CENTCOM’s 130th redirected vessel on 5 October is blockade hygiene, not a 156-26 naming. Blockade resumed 14 July against ships entering or leaving Iranian ports; three disabled for non-compliance; 13 destroyed over 12 weeks on CENTCOM’s account. Monitor NTMs, answer on VHF 16, hold the 30 nm U.S.-unit standoff. Neutral Hormuz transit is still permitted.
- Do not recast Monday as a Hormuz reopen, a UKMTO-named hull, or a rewrite of 150-26 / Lipsi / 148-26 / 149-26. Stay with unknown projectile. Keep this off the Yanbu, MPCI, FE1, Japan-permit and PGSA desks. CSO, master, flag, class and P&I own the file until UKMTO names the hull, a pollution volume appears, or a later JMIC update takes 156-26 onto the numbered list.
Regulas Shipping will keep lining Warning 156-26 against the three Monday time-late attack products and Update 102 so operators can treat the 1637 UTC engine-room fire as a new attack warning on a strait that is still SEVERE, not as a completed weekly tape or a reason to assume the southern Omani corridor has gone quiet.
