US Central Command confirmed it targeted the following in Tuesday’s strike package, according to Foreign Policy:

▸  Iranian air defense systems

▸  Radar systems

▸  Maritime assets

▸  Mine-laying capabilities

▸  Communications sites

▸  IRGC aerospace division personnel in Kermanshah (four killed, confirmed by IRGC)

WHY THESE ARE LEGITIMATE MILITARY TARGETS  

Under the laws of armed conflict, the specific categories CENTCOM named are legitimate military objectives:

▸  Air defense systems: direct military capability that affects the US and Israeli ability to conduct operations and protect their forces

▸  Radar systems: military intelligence and targeting infrastructure

▸  Maritime assets and mine-laying capabilities: directly connected to the ceasefire’s Hormuz opening; the Larak Island strike on August 31 was specifically because IRGC was preparing sea mines for Hormuz

▸  Communications sites: military command-and-control infrastructure

▸  IRGC aerospace personnel: combatants

THE QUESTION CENTCOM’S LIST DOES NOT ANSWER  

CENTCOM’s list of intended military targets confirms what CENTCOM was trying to strike. It does not answer the specific question the Kuhestak wedding raises: was Kuhestak on the target list, and if so why? Or was Kuhestak not on the target list, and if not, what happened?

These are the only two possibilities:

▸  Kuhestak was targeted: there was a military objective at or near the location that CENTCOM assessed was worth striking; the wedding casualties were assessed as collateral damage proportionate to the military objective; CENTCOM has not publicly stated this

▸  Kuhestak was not targeted: the strike at Kuhestak was an error — either a targeting failure, a precision failure, or a faulty intelligence assessment of who or what was at the location; CENTCOM has not publicly stated this either

CENTCOM said it targeted air defenses, radar, ships, mine-layers, and communications sites. It did not say whether Kuhestak was on that list. Those are different questions. The answer to ‘what were you targeting?’ does not answer ‘why did a wedding get hit?’

THE IRGC KASHMIR CONFIRMATION’S SIGNIFICANCE  

Iran’s IRGC confirmation that four aerospace division members were killed in Kermanshah during the same barrage is analytically significant: it confirms that the Tuesday strike package included personnel strikes against IRGC military members, not only infrastructure. Personnel strikes require specific intelligence about the target’s identity and location. Whether the same intelligence quality that produced the confirmed IRGC aerospace kills applied to the Kuhestak targeting is the specific accountability question for the intelligence dimension of the strike.

WHAT HAPPENS NEXT  

▸  CENTCOM Kuhestak clarification — whether CENTCOM addresses what was being targeted at Kuhestak specifically

▸  Battle damage assessment — whether the military releases any BDA that addresses the Kuhestak site

▸  Investigation — whether any formal targeting review is initiated

CONFIDENCE: HIGH

CENTCOM confirmed military targets (air defenses, radar, maritime, mine-layers, communications), IRGC confirmed four aerospace members killed in Kermanshah are from Foreign Policy and IRGC confirmed reporting.

⚖️  BIAS CHECK — WHO IS SAYING WHAT
CENTCOM	Released the military target list; has not addressed Kuhestak specifically; the silence on Kuhestak in the official target list is itself a specific accountability gap
Iran IRGC	Confirmed its own military personnel killed in Kermanshah; this confirmation is consistent with the US target list including military personnel
Foreign Policy	Reporting both the US military target package and the Iran civilian casualty claims; their separate reporting on the preliminary Minab assessment connects the accountability dots

SOURCES

▸  Foreign Policy — CENTCOM Iran military targets Tuesday, September 4, 2026