Iranian Strikes on U.S bases in the Middle East and Gulf Arab Countries

CBS News reported on 15 September that service members deployed at U.S. bases in the Middle East had anonymously leaked photographs said to show extensive, previously undisclosed damage at Prince Sultan Air Base in Saudi Arabia, Camp Buehring in Kuwait and Camp Arifjan in Kuwait. One service member quoted by CBS said, “There is extensive damage to our bases that hasn’t been communicated to the American public.” The leaked material reportedly includes a Boeing E-3 Sentry at Prince Sultan described as having sustained a direct strike to its aft section, along with destroyed barracks and leveled utility structures; CBS did not publish a comparable damage inventory for the Kuwait facilities. The Pentagon declined to comment on the photographs. Snopes published a fact-check on 16 September, titled “‘Leaked’ photos allegedly show Iranian damage to US bases in Middle East. Here’s what we know,” which said the images’ authenticity had not been independently verified and that no metadata, capture-location data or chain of custody had been published to confirm them. Snopes noted that the claimed damage is broadly consistent with the pattern already documented elsewhere on this page, including the Pentagon inspector general’s estimate of $3.7 billion in equipment damage and nearly 60 aircraft destroyed or damaged fleet-wide — but consistency with that broader pattern is not independent verification of these specific photographs, their locations or their dates. The CBS story was subsequently repeated by RT, IranWire and Crooks and Liars; those re-reports add no independent verification and are not treated here as primary sources. This item is recorded as an anonymously sourced leak under review, not as confirmed new damage, pending release of the underlying images with verifiable provenance. CBS News — leaked-photo report, 15 September ↗ Snopes — fact-check, 16 September ↗

The War Zone combined the inspector-general figures, the Congressional Budget Office's accounting through 1 August and later open-source reporting to produce the most current public aircraft-loss synthesis reviewed for this page, with a cutoff of 18 September. It assessed 47 MQ-9 Reapers lost across the wider Middle East conflict, including aircraft shot down over Iran, lost to the Houthis or destroyed on the ground; that is an analyst total built partly from unnamed-official and open-source reporting, not a Pentagon-published final inventory and not a count of base-strike losses alone. For crewed aircraft, it assessed two KC-135 tankers destroyed and as many as seven damaged; four F-15Es lost — three to friendly fire and one over Iran — plus roughly eight damaged in the later Muwaffaq al-Salti base attack; two MC-130Js and four MH-6 helicopters deliberately destroyed by U.S. forces during the April rescue operation; two A-10s damaged or lost; and the Prince Sultan E-3 as a combat loss despite the inspector general describing it as damaged. It also noted later reports of four additional H-60-family helicopters damaged after 10 September. These categories mix hostile base strikes, aerial combat, friendly fire, accidents and U.S. denial actions, so they cannot be summed as aircraft destroyed by Iranian attacks on bases. The CBO valued equipment requiring replacement at about $1.9 billion through 1 August and estimated roughly $3.3 billion to replace all lost capability with currently available platforms; TWZ assessed that subsequent losses and repairs could push the broader figure above $4 billion. Separately, the Congressional Research Service reported 18 U.S. military deaths and 824 wounded as of 15 September, while the later AP and Washington Post figures discussed below supersede that wounded cutoff and raise unresolved questions about additional fatalities. The War Zone — aircraft-by-aircraft synthesis, 22 September ↗ Congressional Research Service — conflict update, 18 September ↗

This site obtained and reviewed the underlying Lead Inspector General report directly. Its body text says that from 28 February to 30 June, seven U.S. service members were killed in action and seven died in non-hostile incidents during OEF combat operations, with 417 wounded in action over the same period, and that four additional service members were killed in action in July. Table 4 of the report (p.17) gives the full incident-level breakdown, sourced to the Defense Casualty Analysis System as of 26 August 2026: Port Shuaiba, Kuwait (1 March) — 6 killed in action; Saudi Arabia (1 March) — 1 killed in action; KC-135 crash, Iraq (12 March) — 6 non-hostile deaths; MH-60S helicopter crash, Arabian Sea (1 July) — 1 non-hostile death; Muwaffaq al-Salti Air Base, Jordan (17 July) — 3 killed in action; Erbil Air Base, Iraq (19 July) — 1 killed in action; for a total of 11 killed in action and 7 non-hostile deaths, 18 overall. Independent reporting (Task & Purpose, CNN, Time, Air Force Times) identified all 18 by name and unit, corroborating the table. Critically, the table carries its own footnote: the Defense Casualty Analysis System lists all casualties before 7 July as part of OEF, while casualties after that date are instead classified under a separate "Overseas Operations" category — the same administrative reclassification the Washington Post's 18 September report (below) says was applied to at least four Jordan-strike deaths, now confirmed directly from the inspector general's own report rather than only via anonymous sourcing. Separately, coverage of this same report by Army Times reported that a wounded count disclosed later, covering a period extending into August, had risen to 774 from the 417 given in the report itself — a near-doubling within about two months that neither the report nor that coverage explained. Read together with the Al Jazeera/DCAS snapshot above and the Post's reporting below, this is now a third, and the most authoritative, data point showing officially disclosed U.S. casualty figures for this war have consistently moved upward only after the fact, and that the government's own accounting system routes some deaths out of the OEF category entirely depending on when they occurred. None of this proves any specific higher total is the true one; it is why this page treats every casualty figure on it as provisional rather than final. Pentagon inspector-general report, Table 4, p.17 ↗ Army Times — wounded-count discrepancy ↗ Tampa Free Press — wire summary ↗

Al Jazeera, citing the Pentagon casualty database, reported 820 U.S. troops wounded and 18 killed across the war as of Tuesday, 8 September, with 30 additional wounded recorded. These are attributed official totals, subject to reporting delays and revisions, not an independently complete accounting. The date an injury enters the database does not establish when or where it occurred. The increase must not be assigned to the latest Jordan barrage without incident-specific evidence. The late-July figures below are retained as historical accounting context. Al Jazeera — Pentagon database report ↗

The Washington Post reported on 18 September that the true U.S. military death toll from the Iran war exceeds what the Pentagon has disclosed in its public Defense Casualty Analysis System (DCAS) database. Citing six U.S. officials speaking on condition of anonymity, the Post said five of them put the total at least 22 fatalities — four more than the 18 then listed in DCAS — while a sixth official said 23 service members had died since the war began on 28 February, cautioning that not all of the undisclosed deaths are directly tied to combat but did involve personnel in the Middle East amid the hostilities. That same official said three U.S. contractors based in the region have also died since the war started. The identities, dates, locations and causes of the undisclosed deaths remain unclear, and the Pentagon declined to address the Post's questions about the discrepancy before publication. Separately, the Pentagon has acknowledged two other Middle East deaths during the same period at bases that have been attacked by Iran — Sgt. Devin Seibel, who died in a training accident in Irbil, Iraq, on 31 May under Operation Inherent Resolve, and Maj. Sorffly Davius, who died of an unspecified medical emergency in Kuwait on 6 March under Operation Spartan Shield — neither of whom is named in the DCAS tally, though it is unclear whether either death is tied to an Iranian attack. The Post cited a CENTCOM document estimating the war's cost at about $43.6 billion through early September, including $28 billion in expended munitions but excluding damage to U.S. bases. Associated Press reporting published later that day corroborated the $43.6 billion total, dated the estimate to 3 September, and put the precise munitions line at $28.1 billion; it also reported that the public Pentagon tally had reached more than 830 wounded while still listing 18 deaths. Those newer figures supersede the lower historical cost and wounded totals elsewhere on this page, which remain labelled by their earlier cutoff dates. The report also noted that the administration reclassified four Jordan-strike deaths from Operation Epic Fury into a separate “Overseas Operations” category over the summer, an accounting change already documented above. This is an anonymously sourced account, not a Pentagon-confirmed casualty figure, and none of the additional deaths described have been independently verified by name; it is recorded here as a serious, multiply-sourced allegation of undercounting rather than a revision to the war-wide totals reported elsewhere on this page. The Washington Post — undisclosed-casualties report, 18 September ↗ Associated Press — CENTCOM cost estimate, 18 September ↗

Jordan's armed forces said its air defenses engaged 20 ballistic missiles fired from Iran toward Jordan, intercepting 18. It said the remaining two fell in unpopulated areas and reported no casualties. This supersedes the initial live count of at least eight interceptions and confirms that the salvo exceeded 10 missiles. Iran said it had targeted U.S. forces at Muwaffaq Salti Air Base, also known as Al Azraq, and claimed to have destroyed fighter-aircraft hangars. Subsequent imagery and reporting support the conclusion that weapons reached the airfield and damaged aircraft and infrastructure, although they do not substantiate every effect claimed by Iran. The apparent conflict between Jordan's initial account and the later evidence remains publicly unresolved: the accounts may describe different projectiles or attack waves, or use different definitions of a successful interception. Petra — Jordan Armed Forces statement ↗ Al Jazeera and AFP — attack and response report ↗At 01:31 GMT on 9 September, Al Jazeera correspondents reported hearing a fresh series of interceptions in eastern Jordan. That initial update supplied no missile count, intended target or impact assessment, so it is recorded as a continuation of the episode rather than proof of a separate successful strike. Al Jazeera — 9 September live updates ↗Open-source accounts also described some missiles as carrying cluster warheads and circulated footage said to show heavy interceptions and multiple impacts. Jordan's official statement did not identify cluster warheads or report an impact at a U.S. facility. The reviewed clips alone cannot reliably distinguish successful warhead impacts from interceptor bursts, falling debris or dispersed submunitions. Later satellite imagery independently supports probable impacts at Muwaffaq Salti, but the cluster-warhead description and the precise effects of each impact remain unverified. Separately, CENTCOM said a U.S. warship evaded two missile attacks in the preceding two days without American casualties; that statement does not resolve the later Jordan incident. Iranian reporting described crews evacuated from tankers near Kharg and Jask, with no casualties reported so far. The IRGC also threatened U.S. bases and warned tanker crews near Kuwaiti and Bahraini ports to leave their vessels; that warning is not confirmation of an attack or completed evacuation at those ports. Al Jazeera — initial reports and chronology ↗

Iranian ballistic missiles struck U.S. troop housing at Muwaffaq Salti Air Base, killing three American soldiers and wounding four. U.S. officials later told The Wall Street Journal that Iran had acquired high-resolution images of the base from unnamed Chinese entities before and after the attack. The officials did not identify the suppliers, publish the underlying intelligence or allege that China's government directly participated; Beijing rejected the allegation and asked for evidence. Their further concern that Chinese assistance may help Iran locate U.S. warships remains an attributed intelligence assessment, not proof that such imagery guided any particular naval attack. This July strike is separate from the 8 September barrage described above. Report summarising the Wall Street Journal findings ↗

Air & Space Forces Magazine, citing people familiar with the matter and an earlier CBS report, said one A-10 suffered severe wing damage and about eight F-15E fighters were lightly damaged in the 8 September attack on Muwaffaq Salti Air Base. The F-15Es were assessed as serviceable, and U.S. officials said no American personnel were killed. CENTCOM had not commented when the report was published. This supports material damage at the base but not the circulating claim that five F-15s were destroyed. Air & Space Forces Magazine — aircraft damage report ↗

An OSINT613 post attributed to analyst BeamTracker compares Sentinel-2 imagery from 8 September with a newly released post-strike view and marks at least four apparent changes: one on a taxiway and three at aircraft shelters. The temporal comparison materially strengthens the conclusion that weapons reached the airfield. Sentinel-2's roughly 10-metre optical resolution does not independently establish whether every marked feature is a direct-hit crater, what was inside the shelters, or the number and condition of damaged aircraft. The imagery therefore corroborates probable impact locations, while the A-10 and F-15E damage count remains sourced to reporting from people familiar with the assessment. OSINT613 — Sentinel-2 comparison ↗

A separate report said Australian mapping platform Soar compared commercial images from 8 and 10 September and identified at least six suspected damage marks at Muwaffaq Salti. Its assessment described a fighter-aircraft hangar that appeared to have been struck, possible impact marks beside a runway and visible changes at two UAV hangars. This is retained alongside, rather than merged with, the OSINT613 assessment because the analyses use different imagery and counting methods. The reported marks support damage at the airfield but do not by themselves establish what equipment was present, the severity of every change or a six-hit total. VnExpress — report on the Soar comparison ↗

The Wall Street Journal, citing U.S. officials, reported that Iran launched a previously undisclosed second attack against U.S. Navy ships on Monday, 7 September, after the weekend attack on an aircraft carrier and destroyer. The officials said no American ship was hit. CENTCOM later said one unidentified warship had been targeted with ballistic missiles twice over the preceding two days, evaded both attempts and continued patrolling; it cited those attempts when announcing strikes on five Iranian crude carriers on 8 September. The Journal reported concern that Iran may be using more sophisticated anti-ship missiles with electro-optical seekers and noted the Qassem Bassir and Khalij Fars as systems associated with that technology, but no reviewed evidence identifies the weapon used. U.S. officials also raised the possibility of Chinese or Russian assistance in locating American ships without publishing evidence establishing it. A Navy official said 19 U.S. warships were supporting Middle East operations. This naval count describes regional force posture, not forces stationed at any single base. Wall Street Journal — second naval attack report ↗ CENTCOM statement reproduced by Times of Israel ↗The IRGC later named USS Delbert D. Black and USS John Paul Jones and claimed both destroyers were struck and significantly damaged. No reviewed U.S. statement, imagery or independent assessment confirms those outcomes, which directly conflict with CENTCOM's evasion account. Al Jazeera — attributed IRGC claim ↗ CENTCOM — evasion account ↗

Anthropic says it identified and disrupted an Iran-linked account that used Claude to collect and analyse publicly available information and develop targeting recommendations concerning U.S. naval forces in the region. According to the company, Claude helped build a Python pipeline and compile targeting handbooks using public military-photo captions, ship and aircraft transponder identifiers, commercial satellite-imagery query scripts and websites exposing naval movements. The actor also requested research into known vulnerabilities in shipboard communications and industrial-control products. Anthropic says it banned the account and shared intelligence with government authorities. This is a company attribution based on activity it observed on its service: the public report does not identify the operator, establish direct Iranian-government control, or show that Claude guided a weapon or enabled any particular strike. Anthropic — primary threat-intelligence report ↗ Military Times — report and context ↗

Iran launched a renewed series of missiles and one-way attack drones toward U.S.-linked facilities in Jordan, Kuwait, Bahrain, the United Arab Emirates and Erbil after U.S. strikes on Iranian military targets near the Strait of Hormuz. Host-country reporting confirms repeated air-defense engagements and interceptions, including a second consecutive night of attacks over Kuwait early on 3 September. Those confirmed launches and interceptions do not substantiate Iran's stronger claims that U.S. command buildings, drone facilities, aircraft or personnel were hit. No reviewed U.S. or host-government statement confirms American deaths or major new base damage from this round. The sections below keep each country's claims, denials and confirmed effects separate. Associated Press — regional chronology ↗ Kuwait interception report ↗

A U.S. official told CBS that overnight Iranian attacks affected no American-used regional military facilities. CBS News ↗ This attributed assessment should be read alongside, not confused with, the Iranian claims below. It does not independently verify every interception or establish that no civilian property was damaged.

A three-frame satellite sequence shows a clean runway on 25 August, a new dark mark on Runway 13/31 at Prince Hassan Air Base on 2 September and a repaired but still visible patch on 3 September. The temporal change is the strongest public overhead evidence that at least one projectile reached the airfield. Available browse imagery is not sufficiently detailed to distinguish a crater from scorching or to verify Iran's separate claims of hangar damage, destroyed RQ-4 or MQ-9 aircraft, casualties or lasting operational disruption. Overhead imagery digest and source sequence ↗

Bahrain's Defence Force said its air-defence systems intercepted and destroyed multiple Iranian aerial attacks on 2 September. Iranian state media claimed that U.S. bases and radar facilities in Bahrain, including Sheikh Isa Air Base, were targeted, but the reviewed official and independent reporting did not identify a projectile impact at Sheikh Isa or Naval Support Activity Bahrain, confirm new damage to the Fifth Fleet headquarters or report casualties there. The confirmed fact is the national air-defence engagement; the claimed base strikes and any operational effects remain unresolved. Bahrain Defence Force ↗ Associated Press ↗

An open-source comparison reportedly shows a mark on a Naval Support Activity Bahrain warehouse in 2 September imagery that was absent on 31 August. The image's provenance and resolution do not establish that the change resulted from an Iranian weapon, and circulating strike video has not been independently geolocated to the installation. The feature is therefore recorded as a possible post-attack change—not verified new damage—and does not establish casualties or operational effect. Imagery report and limitations ↗

Kurdish authorities said 10 explosive-laden drones were intercepted around Erbil between 01:13 and 03:31 local time. A Sentinel-2 comparison from 28 August and 2 September shows new dark features mainly west of the runway, within the coalition-base area, with additional changes east and southeast of the airport. NASA FIRMS data from the NOAA-20 VIIRS sensor recorded two adjacent thermal anomalies inside the base at 23:58 UTC on 1 September—02:58 local time on 2 September—during the reported attack window. Together, the satellite and thermal observations support a localized fire or heat event inside the compound more strongly than the earlier single-image report. They still cannot establish whether a drone struck the ground, interceptor debris caused the fire, or which asset was affected. At Sentinel-2's 10-metre resolution, Iran's claims that a repair facility, technical-equipment warehouses and a surveillance-balloon control system were destroyed remain unverified; no casualties were reported. Sentinel-2 comparison, thermal detections and chronology ↗ Associated Press ↗ ABC News ↗

Low-resolution imagery attributed to MizarVision marks three possible changes in the aircraft-parking area at Ahmad Al-Jaber and three dark roof features on a billeting-area building at Ali Al Salem. The published graphic is useful enough to retain as an open-source lead, but its resolution and presentation do not establish impact craters, penetrating damage, damaged aircraft or an Iranian weapon as the cause. The Ahmad Al-Jaber features therefore remain possible post-attack changes rather than confirmed impacts; the Ali Al Salem marks supplement, but are weaker than, the separate structural comparison below. Published imagery and report ↗

In the days after the 8 September barrage, higher-resolution commercial imagery and further analyst assessments were reported to be emerging, with Muwaffaq Salti identified at the time as the principal site to watch. No persuasive new public post-strike image set with inspectable original pixels, capture metadata and a usable pre-strike baseline had emerged by the 19 September review cutoff beyond the 10 September comparisons. Images republished in reporting through 17 September add useful context but do not establish another strike or a larger aircraft-loss count. The existing Sentinel-2 comparison supports at least four probable impact points at Muwaffaq Salti, while the separate Soar assessment describes at least six suspected marks; neither is detailed enough to count damaged aircraft independently. A higher-resolution frame could resolve whether the shelter and UAV-hangar changes are roof penetrations, scorching, debris or unrelated activity, but resolution alone would not establish which aircraft were present or whether they remained serviceable. No commercial imagery reviewed by the cutoff establishes new damage from the latest wave at Al Minhad or Al Dhafra in the UAE, Sheikh Isa in Bahrain, or Camp Titin in Jordan. Ahmad Al-Jaber remains a provisional imagery lead, while Ali Al Salem is excluded from this unresolved group because a commercial comparison shows substantial structural change there. Wide-area imagery remains too coarse to exclude small impacts, and absence of visible smoke at that resolution is not proof that every weapon was intercepted. This assessment would still be tightened if the original higher-resolution captures or a reproducible before-and-after comparison became publicly inspectable, but none had emerged by 19 September. Muwaffaq Salti Sentinel-2 comparison ↗ Separate Soar assessment ↗ 11 September Bahrain and Jordan synthesis ↗ Overhead-imagery review ↗