Iran Fired Its Most Dangerous Missile at a U.S Aircraft Carrier — Then THIS Happened...

Added: 2026-06-01

[00:00:00]At 6:31, the USS Thomas Hudner's SPY1D radar picks up a contact 25 km to the north, flying at 47 m above the surface of the Persian Gulf. Not from the Iranian coastline, not descending from a ballistic arc, from the water itself. A contact that appears on the radar display fully formed, already at terminal approach speed, already inside the outer engagement envelope with no approach track preceding it. Because there was no approach, the missile did not come from above. It came from below, launched from an underground tunnel carved into the seafloor of the Persian Gulf. its launch signature, a 4-se secondond pressure transient that the Thomas Hudner's automated classification system had logged at 627 as a seismic event and filed without flagging. 4 minutes and 11 seconds from radar detection to impact. Lieutenant Commander James Hassan had flagged the seismic event at 627, not because the automated system had told him to, because in 9 years of electronic warfare work, he had never seen a seismic transient on a bearing that had been producing zero geological activity for the 6 days that Thomas Hudner had been operating in this grid. The Arabian Gulf seafloor on bearing 031 was featureless sand over limestone. No fault lines, no volcanic activity, no geological mechanism that produced a 4-se secondond pressure transient at 6:27 on a Tuesday morning. Hassan had logged it at 628 and transmitted the bearing to the combat information center with one line appended. Possible launch signature bearing 031. Request classification review. It came back at 6:30. Seismic activity consistent with tectonic microracture. No further action required. Hassan looked at the response for 3 seconds. Then he started watching bearing 031 with every passive sensor his station could bring to bear because a tectonic micro fracture on featureless sand over limestone was not something that happened either. And if whatever had produced the pressure transient at 627 on bearing 031 was not geological, there was only one thing it could be. At 631, the contact appeared on radar, and Hassan already knew what it was. The Sumar cruise missile is Iran's longestrange strike weapon, a direct descendant of the Soviet CP 55, the same cruise missile design that carried nuclear warheads for the USSR throughout the Cold War. Iran acquired several KH55 airframes from Ukraine in 2001. The Sumar is named after a village in western Iran where chemical weapons were used against Iranian civilians during the war with Iraq in the 1980s. Iran did not name their most advanced cruise missile after a geographic feature or a military achievement. They named it after a massacre that is not an accident. The Sumar flies at below 50 m altitude using a terrain following guidance system that reads the surface beneath it continuously. a downwardpointing radar altimeter measuring the distance between the missile's airframe and the ground or water below it, adjusting its flight path in real time to maintain the specific altitude that keeps it below the radar horizon of any ship in its path. At 47 meters above the Persian Gulf, the Earth's curvature means the Thomas Hudner's SPY1D radar cannot detect it until it is approximately 25 km away at Mach 0.8.

[00:03:44]That is 4 minutes and 11 seconds of warning. Not 14 minutes like a ballistic missile climbing through the upper atmosphere. Not 9 minutes like the DF21D arcing over the South China Sea. 4 minutes and 11 seconds. From the moment the contact appears on radar to the moment a 200 kg warhead reaches the hull, the tactical action officer calls weapons free at 0631.

[00:04:10]And the Aegis system begins building its intercept solution against a contact flying 47 m above the water at Mach 0.8.

[00:04:19]The first SM2 interceptor launches from the forward vertical launch cells at 0632.

[00:04:26]The fire control solution is clean. A terrain following cruise missile at Mach 0.8 is a manageable threat geometry. The M2 designed for exactly this engagement profile. The intercept point calculated and the missile climbing toward it. The Sumar executed a terrain following correction at 632 and 41 seconds. Not a guidance maneuver, not a programmed evasive action, a response to the water surface beneath it. a wave, a natural swell running northeast across the Persian Gulf that the altimeter detected at 140 m range. And the guidance system responded to by dropping the missile's altitude from 47 m to 31 m in 0.4 seconds to maintain its 47 m clearance above the wave crest. The SM2 fire control solution had been built for a contact at 47 m. The Sumar was at 31 m when the interceptor reached the intercept point. The SM2 detonated 22 m above the missile's actual position.

[00:05:31]Miss 3 minutes and 29 seconds remaining.

[00:05:34]The second SM2 launched on an updated solution incorporating the observed altitude correction. The fire control computer adjusting for a contact that was capable of 16 m altitude changes in 0.4 seconds. The solution built around the corrected profile, a more conservative intercept geometry, less precise, higher probability of finding the missile regardless of its exact altitude at the moment of intercept. The Sumar's radar absorbing coating degraded the fire control solution as the range closed below 18 km. the coating, reducing the Spy 1D's return from the airframe, progressively as the contact moved into the coating's optimal absorption angle. The solution confidence dropping from 81% at 18 km to 67% at 14 km to 54% at 11 km as the return weakened. The second SM2 detonating at 54% confidence close 14 m from the airframes's projected position outside the lethal fragmentation radius as the coding degraded solution placed the intercept point 14 m from where the Sumar actually was. Two SM2 expended 2 minutes and 44 seconds remaining. Hassan was not watching the SM2 engagements. He had been watching something else since 6:27. a signal so faint it had been appearing in his passive collection feed as background noise for the four minutes since the seismic transient. A specific narrow band emission in the low gigahertz range appearing on bearing 031 at intervals of exactly 0.3 seconds not random exactly 0.3 seconds the specific pulse interval of a radar altimeter cycling through its measurement sequence. the downward pointing altimeter on the Sumar's airframe pointing toward the water and measuring continuously but producing a small upward scatter component as the return bounced off the water surface and propagated upward through the airframes's vententral section leaking through the hull and radiating faintly upward. A signal so small the automated systems had classified it as receiver noise. Hassan had been watching it cycle at 0.3 second intervals since 628. At 631, when the contact appeared on radar, he had cross referenced the altimeter scatter bearing with the radar contact bearing and confirmed they were identical to within 0.2°.

[00:08:11]He had been tracking the Sumar's exact position from its own altimeter scatter for 3 minutes and 11 seconds before the radar found it. passive data from a signal the missile was producing involuntarily. Data that gave him the contacts altitude and position to within four meters rather than the 14 m uncertainty the coding degraded radar solution was producing. He had submitted the position update to the combat information center at 0631 and 44 seconds 13 seconds after the contact appeared on radar. It came back at 0632.

[00:08:48]position data from non-standard collection source. Unable to integrate with fire control solution at this time, Hassan kept watching bearing 031. Kept logging, kept building. The ESSM launched at 6:33 as the Sumar crossed 14 km. The evolved sea sparrow. Smaller, faster, designed for the knife fight geometry that developed when a sea skimming missile got inside the SM2's optimal engagement range. The ESSM climbing hard into the terminal engagement envelope. Its active radar seeker activating at 8 km from the contact. The seeker finding the coding degraded return and building its own guidance solution independent of the SPY1D's fire control data. The Sumar flew through another wave correction at 633 and 17 seconds. A larger swell this time, a 3 m wave crest that the altimeter detected at 80 m and responded to by dropping the missile's flight path 11 m in 0.2 seconds. The ESSM seeker had been tracking a contact at a specific altitude. The contact dropped 11 meters in 0.2 seconds. The seeker lost the return for 0.6 seconds as it searched the new altitude band. The ESSM flew through the space where the Sumar had been 0.6 seconds earlier and detonated on timer 31 m past the contact's actual position. Three intercept attempts, three misses. 1 minute and 47 seconds remaining. The failank activated as the Sumar crossed four kilometers. The close-in weapon systems fire control radar, acquiring a coding degraded return at 4 km and beginning its tracking sequence. The failank fire control radar operated on a different frequency than the spy1D and the coding's absorption profile was optimized for the spy1D's band producing a stronger return on the failanc's frequency than the main radar had been getting. The track was better. The solution was building. Hassan transmitted at 635 and 14 seconds. Not a report, not a request for classification review. a direct data injection into the Failank fire control system, his passive altimeter scatter solution, 4 meters of position accuracy, the Sumar's exact altitude and exact bearing for the previous 3 minutes and 47 seconds of continuous collection formatted as a fire control track update and transmitted directly to the Failank console without routing through the combat information center authorization chain, an action he had no authority to take an action that gave the failank fire control system the Sumar's exact position 2.4 km earlier than its own radar solution would have produced it.

[00:11:48]The failank found the contact at 635 and 19 seconds, 2.4 4 km outside its standard engagement envelope, a geometry the system had never used operationally because its own radar could not build a solution at that range against a coded C skimming contact. Hassan's altimeter scatter data gave it the solution the radar could not. The burst fired at 0635 and 19 seconds on a contact 2.4 km out, flying at 44 m. The rounds reaching the intercept point in 0.4 4 seconds.

[00:12:23]Finding the Sumar's forward section, not the warhead, the guidance section, the terrain following radar altimeter and the navigation electronics housed in the forward airframe. The fragmentation pattern shredding the altimeter housing and severing the navigation bus connection between the guidance section and the flight control surfaces. The Sumar lost terrain following guidance at 44 m above the Persian Gulf with 1.8 8 km remaining to the Thomas Hudner's hull without terrain following the flight control system held the last commanded altitude 44 m for 0.7 seconds as the guidance section attempted to reacquire its altimeter signal and found nothing.

[00:13:07]Then the aerodynamic forces acting on a missile traveling at Mach 0.8 without active altitude correction began pulling the nose down. Not immediately, not catastrophically. Gradually, the way a missile descends when the system holding it level stops working and physics takes over. The Sumar descended from 44 m to 31 m to 19 m to 8 m in the 1.4 seconds it took to cover the remaining 1.8 km.

[00:13:38]At 8 m above the Persian Gulf, it hit the crest of a 2 m wave. The warhead initiated on surface impact 340 m off the Thomas Hudner's port bow at 0635 and 31 seconds. Full initiation. The 200 kg warhead detonating against the water surface and directing its full energy upward and outward in the hemispherical blast pattern of a surface contact detonation. The blast wave traveling 340 m of open water and reaching the Thomas Hudner's port hull. attenuated by distance. Still enough, the hull absorbing a pressure event from the port side that threw four crew members off their feet in compartments along the port passageway, shattered two bridge windows from the over pressure and produced a hull flex that the structural monitors registered and the damage control teams confirmed as within tolerance in 6 minutes. The water column from the detonation rose 40 m above the surface, visible from the Thomas Hudner's bridgewing as a white column climbing above the horizon 340 m to port and then falling back into the gulf in a spreading ring of white water. Four crew members in medical, no hull breach, no flooding. The Thomas Hudner operational.

[00:14:58]Hassan wrote his unauthorized data injection into the failank fire control system into his engagement log at 637 with full technical detail and submitted it to the combat information center before anyone had asked him about it.

[00:15:13]The tactical action officer read it and called his position on the circuit. You had no authorization to inject data directly into the failank fire control system. Hassan looked at his display at the altimeter scatter signal that had been cycling at 0.3 second intervals since 628 at the 3 minutes and 47 seconds of continuous passive collection that had given him 4 m position accuracy on a contact the radar had been seeing at 14 m uncertainty. He said nothing for 2 seconds. Then no sir, I did not. The underground tunnel launch position fixed from the seismic transient bearing at 627. The altimeter scatter collection from 628 to 635 and the radar contact track from 631 triangulated to within 22 m received two tomahawks at 638. The tunnel entrance and the fire control post above it ceased to exist at 649.

[00:16:14]Iran spent years carving launch tunnels into the Persian Gulf seafloor so that Sumar missiles could appear from the water rather than the coastline. No approach track, no warning from coastal radar, a contact that materializes fully formed inside the outer engagement envelope. With 4 minutes and 11 seconds between existence and impact, the Sumar flew at 47 m above the surface and defeated every conventional engagement.

[00:16:43]The Thomas Hudner attempted three intercept solutions built on a radar degraded return. Three misses. It hit a wave 340 m from the hull because a lieutenant commander spent four minutes watching a signal that the automated systems had classified as receiver noise. A 0.3 second pulse from a radar altimeter leaking upward through a missile's airframe and spent 3 minutes and 47 seconds building a fire control solution from it that gave the felank 2.4 km of additional engagement geometry. Iran hid the launcher underground. The Sumar hid itself in wave clutter and radar coating. Hassan found it in the signal it could not hide. the signal it had been producing since the moment it launched and could not stop producing because it needed that signal to