Iraq.The hot object that crossed the crosshairs between release and impact

The aircraft entered the restricted operating zone designated 'RAINDROP', over Ayn al-Asad Airbase in Iraq's Anbar province, at approximately 19:30Z on September 20, 2024, tasked with conducting a weapons calibration. At roughly 20:25Z it received a call for fire to employ an AGM-176 —the Griffin, a lightweight laser-guided missile. The crew executed the release and, per procedure, held laser energy on the target until the munition impacted.

It is in that interval, short by definition, that what turns a routine exercise into a UAP file occurs. At 20:27:59Z, between weapons release and impact, an object crossed the sensor's field of view. The report records it tersely but precisely: the object generated an infrared lens flare on the MX-20 and MX-25 optical turrets, which the operator read as indicating a significant heat source, and moved at a high rate of speed through the field of view. The maneuverability-observations box carries the literal phrasing: 'UAP flew through sensor in between munition release and munition impact.'

The structured form adds the elements that let the case be weighed. The object's signatures are recorded as 'IR signature detectable by MX-20 & MX-25.' Physical state is solid. Advanced capabilities or materials are recorded as 'none observed.' The object's response to observer actions reads 'none observed,' and in the reaction-to-observation-or-engagement box the operator wrote a phrase carrying more judgment than it appears to: 'none observed; path of movement appeared predetermined.' There were no effects on persons or equipment, no material was recovered, and the observing aircraft was flying at 170 knots indicated.

Two data points in the report bound the interpretation. First: under 'third-party observers and/or reporters' it is recorded that no parties reported an additional aircraft in that airspace —that is, nobody had declared traffic there. Second: the person who signed the observation was a Captain, and their assessment of the object was 'benign.' The event was assigned serial number 202027ZSEP2024-CENTCOM.

An archival note is necessary and forms part of the file. The document was distributed in the first PURSUE drop under a filename placing it in the East China Sea. Its content does not support that: it mentions neither China, nor the Pacific, nor INDOPACOM anywhere in its six pages, while citing CENTCOM fourteen times, naming Ayn al-Asad and placing the observer's coordinates in grid 38SKC, which corresponds to Iraq. The case is cataloged here by its content, not by its filename.

The case matters for its temporal coincidence, which is unusually precise for this corpus. The object did not cross the field of view at just any moment of a twenty-hour mission: it did so in the seconds-long window separating the release of a guided munition from its impact, while the crew deliberately held sensor and laser fixed on the target. That means the record has a hard timestamp, documented operational context, and a sensor pointed exactly where the event happened —conditions that almost never coincide.

It is also the second case in the corpus, alongside the Gulf of Oman in 2021, where an unidentified object appears at the instant of a live weapons employment. The resemblance ends there: in the Gulf of Oman the orbs fled at the moment of firing, an apparent reaction; here the report says the opposite —'none observed'— and goes further by calling the trajectory 'predetermined.' That two different crews, in different theaters and years, log UAP presence during live fire is a pattern worth tracking, but it is not evidence of reaction in this case.

The posterior's calibration is dominated by where it happened. Ayn al-Asad has for years been a recurring target of drone and rocket attacks by Iran-aligned militias, besides being a base with intense U.S. air activity. In that context, a hot, fast object on an apparently predetermined path with no declared traffic describes with uncomfortable precision a one-way drone, a rocket, or a fragment of the munition itself or its thermal signature. Hence the mass splits nearly in thirds among the prosaic, classified human technology and an adversary platform: in Anbar in 2024 all three hypotheses are ordinary, not exotic.

What prevents closing it entirely is that the report resolves nothing. The operator saw a heat source cross the crosshairs at the worst possible moment, noted that nobody had declared traffic there, assessed the object as benign and moved on. That residue —an unattributed object in the airspace of a base under threat, during live fire— is what sustains the indeterminate share, and it is also, in operational-security terms rather than phenomenological ones, the file's most serious aspect.