Two Crew Members Saw a Hot Flash After Missile Launch
In Iraq, something moved rapidly across the sensor image and vanished.
In Iraq, something moved rapidly across the sensor image and vanished.
After a missile launch in Iraq, two crew members saw a hot flash streak across the aircraft's sensors. They didn't see the object again, and the report doesn't explain what caused the flash.
A SECRET//REL TO USA, FVEY Mission Report (MISREP) covering an Armed Overwatch sortie under Operation INHERENT RESOLVE on 20-21 September 2024. The aircraft departed OKAS at 1740Z, arrived on station in ROZ RAINDROP over Ayn Al Asad Airbase (AAAB) at approximately 1930Z, performed a weapons calibration releasing 20x105mm, 101x30mm, and 1xAGM-176, and landed at OKAS at 0046Z. During the AGM-176 PGM shot at approximately 2027Z, the WSO and CSO observed an unidentified aerial phenomenon fly through the aircraft sensors at high speed, creating an IR lens flare on the MX-20 and MX-25 sensors indicating a significant heat source. The crew maintained laser energy until the munition impacted its target; the UAP was not reobserved. Slug references 'East China Sea' but the document body is set in Iraq (AAAB/ROZ RAINDROP); manifest title also corrects to 'Iraq, September 2024'.
During an Armed Overwatch mission and weapons calibration, the aircraft received a call for fire at approximately 2025Z to employ an AGM-176. After weapons release, the WSO and CSO observed an unidentified object 'fly' through the aircraft sensors at a high rate of speed between munition release and munition impact. The UAP created an IR lens flare on the MX-20 and MX-25 sensors, indicating a significant heat signature. The crew maintained laser energy until the munition impacted its desired target. The aircraft did not reobserve the UAP. UAP Event Serial Number: 202027ZSEP2024-CENTCOM. Observer assessment: Benign. UAP physical state: Solid. Reaction to observation: 'NONE OBSERVED; PATH OF MOVEMENT APPEARED PREDETERMINED AND NOT IN RESPONSE TO [aircraft]'s DETECTION.'
"DEPARTED OKAS AT 1740Z TO CONDUCT ARMED OVERWATCH IVO 38SKC63"
Why it matters: Establishes mission profile, takeoff, and area of operation.
Page 1
"PERFORMED A WEAPONS CALIBRATION, HAVING RELEASED 20x105mm, 101x30mm, 1xAGM-176."
Why it matters: Documents munitions expended during the sortie.
Page 1
"'s CREW OBSERVED AN UNIDENTIFIED AERIAL PHENOMENA DURING ITS PGM SHOT (SEE UAP 1)."
Speaker: Mission narrative
Why it matters: Primary in-line UAP observation reference.
Page 1
"UAP FLEW THROUGH [REDACTED] SENSOR IN BETWEEN MUNITION RELEASE AND MUNITION IMPACT"
Why it matters: Specifies precise temporal window of UAP transit.
Page 5
"IR SIGNATURE DETECTABLE BY MX-20 & MX-25"
Why it matters: Identifies the sensors that detected the UAP and indicates IR-band signature.
Page 5
"NONE OBSERVED; PATH OF MOVEMENT APPEARED PREDETERMINED AND NOT IN RESPONSE TO [REDACTED]'s DETECTION"
Why it matters: Reporter's characterization of UAP behavior as predetermined rather than reactive.
Page 6
"IT IS UNKNOWN AT THIS TIME WHETHER AN OBJECT DETACHED ITSELF FROM THE PRIMARY UAP IMMEDIATELY BEFORE LEAVING THE SENSOR FIELD OF VIEW."
Why it matters: Document explicitly flags this as unresolved/unknown — possible separation event.
Page 6
"UAP CREATED IR LENS FLARE ON MX-20 & MX-25 SENSORS, INDICATING A SIGNIFICANT HEAT SOURCE. THE UAP MOVED AT A HIGH RATE OF SPEED THROUGH THE SENSOR FIELD OF VIEW. THE CREW MAINTAINED LASER ENERGY UNTIL THE MUNITION IMPACTED ITS DESIRED TARGET."
MG Richard A. Harrison
Declassification Authority; USCENTCOM Chief of Staff · USCENTCOM · Page 1
[REDACTED]
POC, Captain · 16 SOS, 27 SOW, U.S. Air Force · Page 2
[REDACTED]
QC, Senior Airman (SrA) · 1 SOW, U.S. Air Force · Page 2
[REDACTED]
Approver, Staff Sergeant (SSgt) · ACF, 379 AEW, U.S. Air Force, 609 CAOC · Page 2
[REDACTED]
UAP Observer, Captain (Weapons Systems Officer / WSO) · U.S. Air Force · Page 5
[REDACTED]
Combat Systems Officer (CSO), UAP observer · U.S. Air Force · Page 6
OKAS (takeoff and landing ICAO)
Page 1
Ayn Al Asad Airbase (AAAB), Iraq
Page 6
Restricted Operating Zone (ROZ) RAINDROP, Iraq
Page 5
MGRS 38SKC63 (objective area)
Page 1
MGRS 38SKC55 (friendly aircraft location)
Page 5
MGRS 38SKC59 (UAP first/last coordinate)
Page 5
16 SOS (16th Special Operations Squadron)
U.S. Air Force · Page 2
27 SOW (27th Special Operations Wing)
JTAC/check-in unit identifier following 'CHECKED IN WITH'
Likely reason: (b)(1)1.4a — National security info / military plans
Aircraft callsign before 'CREW OBSERVED' and before 'WAS CLEARED OFF STATION AT 2323Z'
Likely reason: (b)(1)1.4a — Operational/identifying info
POC/QC/Approver names, phone, email
Likely reason: FOIA Exemption (b)(6) personal privacy; (b)(3), 130b
Aircraft Callsign in ACEQUIP block; Num Gun Rounds and A/G Wpn fields
Likely reason: (b)(1)1.4(a) — Military operations
Callsign, Asset Type, Tail Number(s), JTAR Number, Killbox, JTAC Callsign, Mode 3 IFF Codes
Likely reason: (b)(1)1.4a, (b)(1)1.4g — Operational/intel
Observer name, phone; UAP MDS/Tail Number; friendly aircraft references
Likely reason: (b)(1)1.4a, (b)(1)1.4g; FOIA (b)(3), 130b, (b)(6)
Aircraft callsign before 'DID NOT REOBSERVE THE UAP' and before 'ENTERED AYN AL ASAD'
Likely reason: (b)(1)1.4a — Operational identifier
The slug ('045-dow-uap-d28-mission-report-east-china-sea-2024') and the document URL filename refer to 'east-china-sea', but the document narrative is unambiguously set in Iraq at Ayn Al Asad Airbase (AAAB) inside ROZ RAINDROP, under USCENTCOM / Operation INHERENT RESOLVE. The corpus manifest title ('DOW-UAP-D28, Mission Report, Iraq, September 2024') and incident_location ('Iraq') are consistent with the document; the slug appears to be a war.gov filename mislabel. MGRS coordinates (38S KC zone) place this in western Iraq, consistent with AAAB. Aircraft callsign, MDS/asset type, and tail numbers are redacted under (b)(1)1.4a/g; munitions loadout (105mm, 30mm, AGM-176) plus AC-130-family sensor suite (MX-20/MX-25, 105mm/30mm guns, AGM-176) strongly suggests an AC-130J Ghostrider or similar AFSOC gunship, but the document does not state this and per the rules we omit it. Approved for Release to AARO; declassified 24 October 2025.
They saw an unidentified object rapidly crossing the sensor image. A lens flare appeared there, which the reporter estimated was related to a significant heat source.
The report describes a lens flare — a spot of light created in the imaging system — but does not offer a conventional explanation for what caused it in this case.
The U.S. Department of War report was released to the public in May 2026. It documents an event in Iraq from September 2024.
Why it matters: Core UAP description in GENTEXT/UAP.
Page 6
"(S//REL TO USA, FVEY) [REDACTED] ENTERED AYN AL ASAD AIRBASE's (AAAB) RESTRICTED OPERATING ZONE (ROZ) RAINDROP AT APPROXIMATELY 1930Z TO CONDUCT A WEAPONS CALIBRATION."
Why it matters: Sets geographic context — Iraq, AAAB ROZ RAINDROP, contradicting slug's 'east-china-sea'.
Page 6
"AFTER WEAPONS RELEASE, THE WEAPONS SYSTEMS OFFICER (WSO) AND COMBAT SYSTEMS OFFICER (CSO) OBSERVED AN UNIDENTIFIED OBJECT "FLY" THROUGH THE AIRCRAFT SENSORS AT A HIGH RATE OF SPEED."
Why it matters: Identifies the two-person crew witnesses by role.
Page 6
"(S//REL) UAP EVENT SERIAL NUMBER IS CORRECT WITH THE EXCEPTION OF THE "CCMD ASSIGNED NUMERICAL SEQUENCE," WHICH IS UNKNOWN AT THIS TIME."
Why it matters: Administrative caveat about the event serial number.
Page 6
U.S. Air Force · Page 2
1 SOW (1st Special Operations Wing)
U.S. Air Force · Page 2
379 AEW (379th Air Expeditionary Wing)
U.S. Air Force · Page 2
609 CAOC (609th Combined Air Operations Center)
U.S. Air Force · Page 2
SOTU 016 (originator)
U.S. Air Force · Page 1
AFSOC (Air Force Special Operations Command)
U.S. Air Force · Page 1
USCENTCOM
DoD · Page 1
AN/APN-241 (radar)
radar · Page 3
AN/ALR-56M / ALR-56M (Radar Warning Receiver)
sensor · Page 3
AAR-47 (Missile Warning System)
sensor · Page 3
AN/AAQ-24 / AAQ-24B (IRCM/ECM)
sensor · Page 3
ALE-47 (Countermeasures Dispenser)
sensor · Page 3
RR180 (Chaff)
sensor · Page 3
MJU-71, MJU-66, M206 (Flares)
sensor · Page 3
MX-25 (Targeting Pod)
sensor · Page 3
MX-20 (sensor)
sensor · Page 6
GPS/SADL (avionics)
sensor · Page 3
GATEWAY (data link)
sensor · Page 4
30MM gun
sensor · Page 3
105MM gun
sensor · Page 3
AGM-176 Griffin missile
sensor · Page 1
After a missile launch during a training exercise in Iraq, two crew members saw something rapidly cross the aircraft's sensor image. It left a flash that appeared to be linked to a significant heat source.
The crew continued to track the missile until it hit its target. When they looked again, the object was gone. What exactly created the flash — and what might have separated from it just before it disappeared — remains unclear.
The incident occurred during a training exercise to test a U.S. Army weapon system. After the missile launch, two crew members observed an unidentified object through the aircraft's sensors, which display heat in the image.
The object rapidly crossed the area of the image captured by the sensors. The system showed a spot of light, a phenomenon known as a lens flare. The crew member who wrote the report estimated that the flash was related to a significant heat source.
The report on the incident was released to the public in May 2026. It was written following a mission in Iraq in September 2024 and documents what the crew members observed during the exercise.
While the object moved across the image, the crew continued to operate a laser beam that helped guide the missile. They maintained the beam until the missile hit its chosen target.
The report does not state that the crew saw the object outside the sensor image. After it disappeared from view, the crew members were unable to see it again.
It is unknown what created the flash, if there was an identifiable object there, or if something separated from it just before it disappeared. A lens flare is a spot of light created in the imaging system, but the report does not offer a conventional explanation for what happened here.
The image showed a hot flash that crossed the field of view — and then vanished.