{"id":885,"date":"2026-10-03T03:46:46","date_gmt":"2026-10-03T03:46:46","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-logs-two-friday-tanker-attacks-after-warnings-148-26-and-149-26\/"},"modified":"2026-10-03T03:47:46","modified_gmt":"2026-10-03T03:47:46","slug":"ukmto-logs-two-friday-tanker-attacks-after-warnings-148-26-and-149-26","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-logs-two-friday-tanker-attacks-after-warnings-148-26-and-149-26\/","title":{"rendered":"UKMTO logs two Friday tanker attacks after Warnings 148-26 and 149-26"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre issued two separate attack warnings on Friday, 2 October. Warning 148-26, sourced to a master at 1122 UTC, said a tanker on an outbound Strait of Hormuz transit had been struck by an unknown projectile, leaving a small fire and a blackout on board. The fire was extinguished and the ship remained underway. UKMTO reported no casualties and no environmental impact. Warning 149-26, again sourced to a master, followed at 2142 UTC: a crude-oil tanker about four nautical miles east of Oman reported an unknown projectile on the port side. All crew were reported safe, and no environmental impact had been reported at the time of the warning. In both products, authorities were investigating. Vessels were advised to transit with caution and report suspicious activity to UKMTO. The official PDFs name neither hull, flag, cargo, projectile nor a responsible party.<\/p>\n

Anadolu Agency, Arab Times and gCaptain carried 148-26 the same day. AFP, through Gulf News into Saturday morning, put both Friday products on one tape. Clearwater Dynamics logged 149-26 as CW Alert 004 (Oct 26), classifying it as an attack and locating it near the strait without a precise position. gCaptain\u2019s Mike Schuler, writing after 148-26 but before the 2142 UTC product, said Friday\u2019s outbound hit brought the number of vessels reported struck in the waterway since Sunday, 28 September, to at least six. 149-26 sits after that six-count. Neither warning is a rewrite of Thursday\u2019s Warning 147-26, of Wednesday\u2019s time-late 144-26 \/ 145-26 \/ 146-26 pack, or of Tuesday\u2019s 143-26 \/ Al Funtas file.<\/p>\n

The public record is still thin because the reporting channel is voluntary and names are withheld. That is enough for a bridge and a DPA. It is not a basis for treating Friday as a completed weekly tape, and it is not a basis for reconstructing an attacker from secondary market colour.<\/p>\n

Two master reports, ten hours apart<\/h2>\n

148-26 is the first Friday product. The master reported the strike during an outbound transit inside the strait. The useful operational facts are the combination of a small fire and a blackout, then a ship that stayed underway after the fire was put out. A chief engineer has to brief that as an electrical and fire-main problem, not as a naming exercise. 149-26 is a second master report, about ten hours later, and it is geographically different: four nautical miles east of Oman, a crude-oil tanker, port-side strike, crew safe, no fire stated in the UKMTO text, no pollution reported \u201cat present time.\u201d Clearwater repeated the same gaps. Do not collapse the two warnings into one hull. Do not move 149-26 back inside the TSS just because the first Friday ship was outbound in the strait.<\/p>\n

Industry matching is not a UKMTO naming. The Maritime Executive, writing Friday afternoon, said security consultancy Ambrey had associated the outbound fire-and-blackout ship with a Panama-flagged crude-oil tanker about 5.3 nautical miles off Oman and with smoke from the after end. Treat that as matching colour on 148-26, not as a flag or a position UKMTO published. Hamerintel and other flashes that add an Iranian cruise-missile claim, a named attacker or a second unverified pair of hulls are not this file. Stay with the two official warnings.<\/p>\n

Thursday\u2019s Warning 147-26 remains a separate product. UKMTO still has not named that tanker. Marisks, Riviera, World Ports and the Indian embassy in Muscat have since matched it to the Kuwait-flag VLCC Kazimah III, IMO 9329693, about 317,250 dwt, owned, managed and operated by Kuwait Oil Tanker Company \u2014 the second reported KOTC VLCC after Al Funtas. The embassy said on Friday that it had coordinated the safe landing in Oman of five Indian crew from that ship. Moneycontrol timed the strike to 1 October and to UKMTO\u2019s third-party fire report. That is an increment on the already-published 147-26 piece. It does not identify Friday\u2019s two master reports, and it does not convert 148-26 or 149-26 into a KOTC naming.<\/p>\n

SEVERE still sits under Friday\u2019s tape<\/h2>\n

The last official regional picture is still the Joint Maritime Information Center\u2019s Update 101, information cut-off 011500 UTC on Thursday. That note counted four confirmed attacks or disruptions in the previous 96 hours \u2014 143-26, 144-26, 145-26 and 146-26 \u2014 and held the Strait of Hormuz at SEVERE, with deliberate attacks highly likely. IRGC UAV overflight, targeted surveillance and occasional VHF hailing were still in the text. AIS-on ships were told to expect elevated projectile risk and directed hails toward the northern Iranian-controlled route. A mining watch in and next to the traffic-separation scheme was unchanged. Independent commodity counts were still in single digits; U.S. NCAGS averaged about 30 vessel transits a day against a 2025 baseline of about 138. No later JMIC update covering 147-26, 148-26 or 149-26 was on the public board at the time of writing. A master who planned a weekend transit on Update 101\u2019s four-incident count is now three UKMTO attack products behind that cut-off.<\/p>\n

The operational implication is not a new listed area and not a Hormuz reopen. It is that Thursday\u2019s fire did not close the week. Friday produced two further master-reported projectile strikes, one inside the outbound lane with a fire and a blackout, and one on a crude tanker just east of Oman after dark. The southern Omani corridor and the first miles of the Gulf of Oman exit are both in the picture. A ship making for Khor Fakkan, Fujairah, Sohar or a Gulf of Oman STS still needs a projectile watch, a fire-and-blackout drill, and a pollution and disabled-hull lookout for unnamed tankers that may not be on AIS.<\/p>\n

Hold the published hygiene. 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 remain the last official stack in Update 101. CENTCOM\u2019s figure in that note, dated 30 September, was 125 commercial vessels redirected under the Iran-port blockade, three disabled and two boarded. The Maritime Executive repeated the 125 figure on Friday; it is still the blockade file, not Friday\u2019s projectile file. Do not fold 148-26 or 149-26 into Yanbu loadings, the UAE MPCI container-filing mandate, Oman\u2019s Article 10 AIS-on reminder, or Iran\u2019s Persian Gulf Strait Authority declaration channel. Those are crude-export, documentation and coastal-state products. Friday\u2019s warnings are two unnamed kinetic events.<\/p>\n

What Operators Should Note<\/h2>\n