Iran's overnight barrage leaves two U.S. airbases burning in Jordan and Kuwait

Two Iranian ballistic missiles slipped past U.S. Patriot interceptors and slammed into Muwaffaq al-Salti Airbase in the early hours of 18 July 2026, with new Sentinel-2 satellite imagery reviewed by conflict-mapping analysts showing a U.S. aircraft hangar completely destroyed and NASA fire-detection data pointing to a large blaze at troop barracks on the same installation. The overnight barrage extended to Kuwait, where Iran's Army announced coordinated Arash-2 drone strikes on U.S. military infrastructure at Ali Al Salem Airbase, carried out in coordination with the Islamic Revolutionary Guard Corps.

The combined salvo, claimed by Tehran in a single operational window, marks the most direct Iranian strike on U.S. air infrastructure in Jordan and Kuwait since the escalation cycle that followed 7 October 2023. It also exposes, in plain imagery rather than in communiqués, the limits of a Patriot air-defence architecture that has anchored U.S. force protection across the Levant for three decades.

What the satellites and fire data show

The first hard confirmation came not from any government but from a NASA fire-monitoring product. According to a 05:18 UTC analysis posted by AMK Mapping, Sentinel-2 satellite imagery shows that an Iranian ballistic missile completely destroyed a U.S. aircraft hangar at Muwaffaq al-Salti Airbase in Jordan. A separate post at 05:52 UTC documented footage of two Iranian ballistic missiles bypassing Patriot interceptors before impacting the base, while NASA FIRMS data reviewed at 05:53 UTC indicated a large fire breaking out at U.S. troop barracks there following the overnight strikes. The two fire signatures, on the hangar and on the barracks, are geographically distinct within the same installation, which is consistent with the Iranian claim of a multi-missile package rather than a single round.

Middle East Spectator posted a confirmation thread at 02:07 UTC pointing to NASA's firemap showing a "huge fire" at Muwaffaq Salti Airbase, alongside footage the channel described as showing Iranian missiles striking the base. The triangulation is unusually clean for an active strike package: independent satellite, an open fire-data product, and ground-circulated video all converging on the same grid square within hours.

The Kuwaiti axis

The scope widened at 05:46 UTC, when AMK Mapping relayed an Iranian Army announcement that it had targeted U.S. military infrastructure in Kuwait and Jordan, naming Ali Al Salem Airbase and Muwaffaq al-Salti Airbase, and attributing the Kuwait strikes to Arash-2 drones used in coordination with the IRGC. Ali Al Salem, some 70 kilometres from the Iraqi border, is the principal U.S. Air Force hub in Kuwait and has hosted coalition logistics, tanker aircraft, and transient fighter rotations for two decades. Striking it from Iranian territory with loitering munitions rather than ballistic missiles is, on the face of it, a different problem set: shorter flight time, lower radar cross-section, a different interception calculus.

The two-target geography matters. Muwaffaq al-Salti sits in Jordan's eastern desert and has been a hub for U.S. and partner-nation air operations as well as a long-standing intelligence and drone footprint. Ali Al Salem sits on the Gulf side of the same arc. Hitting both within hours forces a defender to think about magazine depth, radar coverage, and base damage-control across two separate air-defence sectors simultaneously, a problem the U.S. Central Command posture in the region has rarely had to solve in real time.

The Patriot question, in plain terms

Patriot is the public face of U.S. theatre missile defence. It is a phased-array system, optimised against a specific class of ballistic-missile threats, with a documented record of successful interceptions and a documented record of misses. The footage AMK Mapping circulated of two Iranian rounds apparently bypassing the system and impacting Muwaffaq al-Salti is not, on its own, proof of a Patriot failure. Iranian media have an obvious incentive to release clips that flatter their own munitions; defenders will argue radar mode, saturation, debris discrimination, or even the angle of camera all confound a clean read. What the imagery does establish is that something reached the target set, and that the fire data independently confirms an energetic event on the ground.

The honest read is that no single piece of open-source material here proves a systemic Patriot failure. The honest further read is that two impacts, on a defended base, with thermal signatures large enough to register on NASA FIRMS, are not a story air defence can simply absorb without explanation. The Pentagon, on past form, will release a denial or a partial confirmation within days; the U.S. and partner-nation silence in the immediate aftermath is itself data.

What this is, structurally

For three years the regional rule of thumb has been that Iran and its partners strike Israel, U.S. forward bases absorb a trickle, and the escalation ladder is managed in private channels. The overnight package breaks that pattern in two ways. First, the targets are U.S. infrastructure on the territory of two Arab host states, not Israel. The political weight of an Iranian missile landing on Jordanian soil, even at a U.S. base, is different from the political weight of an Iranian missile landing in the Negev. Second, the strike was announced in the open, by Iran's Army, with named weapon systems and named bases, in the same operational window. That is closer to the messaging register Tehran has used for direct strikes on Israel than the more deniable posture it has historically adopted for actions against U.S. assets in the Gulf.

The two plausible framings sit in tension. The first, favoured by Western analysts, is that this is a calibrated message: Iran wants to demonstrate reach and willingness without producing a body count that forces a U.S. reply, and the choice of two bases, two weapon classes, and an open announcement is the signal. The second, favoured by Tehran-aligned commentators, is that this is a genuine escalation across a wider arc, with Jordan and Kuwait folded in because the existing Israel-only framework was no longer sufficient. The evidence in the open sources does not yet adjudicate between them. What it does establish is that the operational envelope, in geography, in weapon mix, and in messaging, has widened.

What remains uncertain

The sources do not yet specify casualties. They do not name the unit or service component assigned to the destroyed hangar, nor confirm whether aircraft were inside it. The Iranian Army announcement, relayed by AMK Mapping, is a single-channel claim; confirmation from the Pentagon, from the Jordanian Armed Forces, or from Kuwait's Ministry of Defence would materially strengthen or weaken the picture. The Patriot footage is unverified, and the standard caveats, attribution uncertainty, possible fabrication, possible old footage re-circulated, all apply. NASA's FIRMS product is reliable for thermal anomalies but cannot, on its own, distinguish a fuel blaze from a structural fire from a decoy flare. The 48 hours after a strike of this scale are, by long experience, the period in which the gap between social-media reality and the official ledger is widest.

What the open record does establish, with reasonable confidence, is the geographical and material envelope of the strike: a hangar destroyed and barracks burning at Muwaffaq al-Salti, an Iranian claim of Arash-2 strikes on Ali Al Salem, and a Pentagon response still to come. The story's second chapter will be written in Washington, Amman, and Kuwait City. The first chapter, with its Sentinel-2 pixels and its FIRMS heat signatures, belongs to the open-source analysts who had it on the map before any government press officer had a line ready.

This article draws on Telegram-channel analysis from AMK Mapping and Middle East Spectator. Monexus treats Iranian state-aligned claims of strike outcomes as the opening word in a sequence, not the final one; the satellite and fire-data records above are independent of those claims and stand on their own.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/Middle_East_Spectator
• https://t.me/AMK_Mapping
• https://t.me/AMK_Mapping
• https://t.me/AMK_Mapping
• https://t.me/AMK_Mapping