Iran strikes Muwaffaq al-Salti Air Base in Jordan, claiming hits on U.S. F-35, F-15 and F-16 hangars
Iran's Islamic Revolutionary Guard Corps said at 03:15 UTC on 11 June 2026 that it had launched twelve ballistic missiles at Muwaffaq al-Salti Air Base and an associated command facility in Jordan, claiming to have hit structures housing U.S. F-35, F-15 and F-16 combat aircraft. The claim, carried by the Liveuamap wire on Telegram, is the most direct Iranian strike yet against a base identified by the IRGC itself as hosting American stealth and fourth-generation fighters, and the first time Tehran has publicly described its target inventory in that level of platform-specific detail.
The wider picture matters more than the missile count. A strike on a host country's air base — even one used by U.S. Central Command — is a different kind of escalation than the shadow exchanges of the past eighteen months. It pulls Amman, formally a non-belligerent, into the line of fire. It tests the U.S. force-protection posture on Jordanian soil. And it gives Tehran a claim of proportionality it can sell domestically: an attack on a military target, not on a city, conducted through state media, broadcast as a measured response.
What the open-source record shows
Within minutes of the IRGC statement, two independent OSINT channels posted corroborating visual material. OSINTdefender reported at 03:09 UTC that air-defence activity and what appeared to be interception plumes were visible over Muwaffaq Salti Air Base, following "a wave of ballistic missiles launched by Iran," and pointed to on-the-ground video circulating on X. The Middle East Spectator account posted at 02:37 UTC footage of smoke rising from the airbase itself, tagged with the Iran–Jordan pairing. Read together, the two feeds establish three things: a launch happened; it was aimed at a specific named base; and the base was hit, or at least engaged by interceptors, hard enough to produce visible smoke columns.
None of the three source items confirm casualties, aircraft losses, or damage to the F-35 / F-15 / F-16 inventory the IRGC named. That silence is itself a data point: a hit on a hardened hangar complex of that kind would normally be visible in commercial-satellite overflights within hours, and the absence of those images, several hours after the strike, suggests either that damage was lighter than Iran's claim, that the base's dispersal posture worked, or that the imagery has not yet been released. The source items do not specify which of those readings is correct.
The Iranian framing, and what it leaves out
The IRGC's claim is carefully constructed. The target list — F-35s, F-15s, F-16s — names the platforms most associated in the regional press with the air strikes Iran has been complaining about for months. The number of missiles, twelve, is large enough to suggest a salvo designed to saturate point-defence, but small enough to be defensible as a calibrated response rather than an all-out barrage. And the choice of Muwaffaq al-Salti specifically, rather than a base inside Israel or a U.S. carrier group in the Gulf, signals that Tehran wants the crisis to live in the Jordanian–American bilateral relationship, not to trigger a NATO article 5-style cascade.
What the framing leaves out is the Iraqi and Syrian infrastructure Iran has been hitting in the same window. Reporting on those strikes is not in the current source set, but the pattern across the past year has been that Iranian operations against U.S. and partner forces in the region have been carried out through Iraqi militias and Syrian proxy formations, with plausible deniability attached. A direct IRGC ballistic-missile launch, claimed in the IRGC's own name, against a base in a third country, breaks that pattern. Either Tehran has decided that deniability is no longer worth the cost, or the strike was carried out by a unit the IRGC is now choosing to own publicly for reasons of its own.
The structural read
The U.S. military footprint in Jordan has grown steadily since 2023, partly as a hedge against Iranian air and missile programmes and partly as a logistics node for operations further east. Muwaffaq al-Salti, near Azraq in eastern Jordan, has hosted U.S. fighter rotations on and off for years; the F-35 question — whether the aircraft have been forward-deployed there or only rotated through — has been a recurrent item in regional reporting that the current source items do not resolve. What the IRGC has now done is make the host-base question a public Iranian talking point, which means that future Iranian statements about U.S. force posture in Jordan will have a concrete location attached, and that Jordanian diplomats will have to answer a sharper set of questions in Washington, Amman, and at the United Nations.
The escalation logic is familiar but worth restating in plain terms. When a regional power strikes a host nation's air base and names the aircraft it is trying to destroy, it is signalling that the host nation's territory is no longer a sanctuary for the power it is contesting. The signal is aimed as much at Amman — keep hosting, or don't — as it is at Washington. Whether Amman reads that signal as a deterrent or as a casus belli is the question the next 48 hours will answer, and the source items available at the time of writing do not yet contain a Jordanian government response.
What we still do not know
Three things remain genuinely uncertain. First, the damage assessment: the OSINT material shows smoke and air-defence activity, not destroyed aircraft, and the satellite overflights that would settle the question have not surfaced in the public channels the pipeline is reading from. Second, the casualty count on the base, which neither Iranian nor Jordanian nor U.S. sources have yet published. Third, the U.S. response posture — whether Washington treats the strike as a one-off to be deterred, a pattern to be punished, or a negotiation opener to be answered in kind at the diplomatic table. Until those three questions are answered, the strike is best read as a move in a game whose next few turns are still being written.
A separate question, outside the source set but worth flagging for the reader, is whether Tehran coordinated any private signal to Amman in advance. The history of Iranian strikes on U.S. positions in the region suggests that some form of back-channel communication is the norm; the public claim, in that reading, is the visible part of an arrangement whose invisible part is not in the open record.
Stakes over the next weeks
If the strike is treated by Washington as a single event to be deterred through posture statements, the regional equilibrium that has held since late 2024 survives. If it is treated as a pattern — a third, fourth, fifth strike in a sequence — the political space around the Jordanian-American defence relationship narrows fast, and the question of which air bases the U.S. can credibly operate from becomes a planning problem rather than a press problem. Amman, which has spent two decades constructing a defence identity that is American-anchored but regionally careful, is the actor with the least margin for error in that scenario.
The structural lesson is older than the strike itself. Forward-deployed air power is only as safe as the host country is willing to keep it, and host-country tolerance is a function of political cost. Iran has now put a price tag on hosting U.S. fighters in the Jordanian desert. Whether that price is paid in damaged aircraft, in a quieter basing arrangement, or in a diplomatic settlement is the question the rest of June will answer.
Desk note: Monexus is leading with the IRGC's own claim and the two independent OSINT visual confirmations, and is explicitly flagging that the source set does not yet contain a damage assessment, a Jordanian government response, or a U.S. military readout. Where wire reporting on the same event will, over the next 24 hours, race to declare winners and losers, this publication is holding to the verifiable record and naming the three questions the record does not yet answer.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/liveuamap/
- https://t.me/osintlive/
- https://t.me/Middle_East_Spectator/