{"id":664,"date":"2026-09-12T11:49:03","date_gmt":"2026-09-12T11:49:03","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/irgc-claims-strike-on-us-saildrone-5838-as-centcom-diverts-96-ships-from-hormuz\/"},"modified":"2026-09-12T11:49:03","modified_gmt":"2026-09-12T11:49:03","slug":"irgc-claims-strike-on-us-saildrone-5838-as-centcom-diverts-96-ships-from-hormuz","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/irgc-claims-strike-on-us-saildrone-5838-as-centcom-diverts-96-ships-from-hormuz\/","title":{"rendered":"IRGC Claims Strike on US Saildrone 5838 as CENTCOM Diverts 96 Ships From Hormuz"},"content":{"rendered":"

Iran\u2019s Islamic Revolutionary Guard Corps Navy said on Thursday, 10 September 2026, that it had struck a U.S. Saildrone Explorer unmanned surface vessel at the entrance to the Strait of Hormuz. Iranian outlets identified the hull as number 5838, said the craft was on an \u201caggressive mission,\u201d and released video they described as the moment of the hit. IRGC Navy commander Alireza Tangsiri was quoted naming the same hull. Tasnim published a still that it said showed the sail-drone on fire. The U.S. military had not confirmed the strike, the capture, or the status of hull 5838 as of Saturday, 12 September.<\/p>\n

A Saildrone Explorer is about seven metres long. It is wind-driven, solar-powered, and fitted with cameras, communications gear and sensors used for maritime domain awareness. Fifth Fleet and Task Force 59 have previously operated the type from Bahrain. The IRGC said those units had been used in the region and that, after strikes on the U.S. naval presence in Bahrain, the craft were now being run from a unit near Khasab on Oman\u2019s Musandam Peninsula \u2014 the same gateway where UKMTO Warning 133-26 logged four unknown projectiles on two unidentified merchant ships the same evening. Iranian claims about the Khasab basing have not been independently confirmed. What is confirmed is the warning that followed the claimed hit: the IRGC repeated that the strait is closed and under its control, and that \u201cany hostile presence in the strategic waterway will be targeted.\u201d<\/p>\n

Thursday\u2019s claim sits on top of an earlier unmanned-systems incident. On 8 September the IRGC said it had captured a U.S. Dive-LD unmanned underwater vehicle at the entrance to the strait. U.S. officials said the underwater drone had malfunctioned while surveying regional waters and described it as an older system without sensitive or classified equipment. They did not say whether Iranian forces had taken it. Two unmanned-system confrontations in three days, one of them still unconfirmed by Washington, is now part of the merchant-ship risk file even though neither platform is a tanker. The IRGC is treating unmanned surveillance craft as hostile presence. A master who sees a small sail-drone, a skiff, or an unidentified contact near the TSS cannot assume that only naval units are in the engagement envelope.<\/p>\n

The commercial overlay arrived the same day. U.S. Central Command said that, as of 10 September, U.S. forces had redirected 96 commercial vessels as part of the naval blockade of Iran that resumed on 14 July, and had allowed more than 50 vessels supporting humanitarian aid to pass. Preliminary ship-tracking put Hormuz transits at seven on Thursday \u2014 two exits and five entries \u2014 against a 10-day average of 15, and down from 11 the day before. Those figures exclude dark AIS. UKMTO kept the strait at \u201csevere\u201d and said the likelihood of attacks on vessels remains high. Brent settled at $107.63 and West Texas Intermediate at $102.48 on Thursday, the highest closes since 19 May. The IRGC had already said, on 9 September, that a restricted maritime zone would stretch from Chabahar into parts of the Gulf of Oman and the Arabian Sea, with coordinates to follow, and that a vessel entering without coordination would face sanctions and future access limits. A Hormuz transit decision now starts well before the TSS: it starts at the Gulf of Oman approaches, against a U.S. redirection count that has moved from the low nineties into 96 and an Iranian zone whose lines are still unpublished.<\/p>\n

Operational implications are about classification, not about who owns the sail-drone. A company security officer who writes the voyage order as \u201cavoid military unmanned systems\u201d has not written a usable order. The IRGC\u2019s language is \u201chostile presence.\u201d That can be a Saildrone, a survey launch, a coalition aircraft overhead, or a merchant ship that Iranian forces decide is non-compliant. CENTCOM\u2019s 96 redirected hulls are the other side of the same lane: a ship that does not fit the U.S. blockade rule can be turned around before it reaches the strait, and a ship that does fit it can still be in an IRGC engagement area. Shuttle and STS programmes in the Gulf of Oman \u2014 the workaround that has kept some barrels moving \u2014 sit closer to Khasab and to any Chabahar-origin restricted zone than a Ras Tanura\u2013Fujairah narrative admits. War-risk and P&I will ask whether the master was briefed that unmanned contacts are now a reported firing event, not only a curiosity on the radar, and whether the owner had a written rule for a U.S. redirection order versus an Iranian coordination demand.<\/p>\n

Iran and Oman are due to put a temporary traffic-separation and corridor script in front of Gulf foreign ministers in Salalah on Monday, 14 September. That meeting does not cancel Thursday\u2019s claimed strike, the Dive-LD episode, or CENTCOM\u2019s 96-ship count. A corridor announcement next week is a routing product only if UKMTO and JMIC downgrade the threat and the unpublished Chabahar zone is issued as coordinates a master can plot. Until then, the live file is a claimed hit on hull 5838, an unconfirmed U.S. position, a severe threat rating, single-digit transits, and a warning that any hostile presence will be targeted.<\/p>\n

What Operators Should Note<\/h2>\n