Military Observer Saw Mysterious Object During Flight in Iraq
He tried to track it, but couldn't identify what he saw.
He tried to track it, but couldn't identify what he saw.
During a military flight in Iraq, an observer spotted an object moving north and northeast. He attempted to track it but couldn't identify it.
USCENTCOM Mission Report (MISREP undefined-7528881) classified SECRET//REL TO USA, FVEY, declassified 8 October 2025 by MG Richard A. Harrison. Documents an 18-hour 54-minute reconnaissance sortie on 20-21 May 2022 by a single redacted ISR aircraft (callsign and tail number redacted under 1.4a) operating from OKAS under Operation INHERENT RESOLVE, tasked by the 196 ATKS / 609 CAOC. The aircraft collected SIGINT via AIRHANDLER VERSION 2 and supported OP PHANTOM FLEX (with redacted unit MAG) conducting FMV and SIGINT, exploited by DGS 1. At 2043Z on 20 May 2022 the crew observed one UAP flying north to north-east; the screener could not get a positive ID and the aircraft followed it as long as possible.
While conducting FMV and SIGINT in support of OP PHANTOM FLEX / MAG, the redacted ISR aircraft observed a single UAP fly north to north-east. The aircraft followed the UAP as long as possible. The screener could not get a positive ID on the UAP. UAP altitude, depth, velocity, and trajectory listed as UNK.
"(S//REL) AT 0542Z, [redacted 1.4a] TOOK OFF LATE FROM OKAS. AT 0551Z, [redacted 1.4a] HANDED OVER FROM THE LRE. FROM 0614Z TO 2346Z, [redacted 1.4a] COLLECTED SIGINT VIA AIRHANDLER VERSION 2. FROM 0927Z TO 2121Z, [redacted 1.4a] SUPPORTED OP PHANTOM FLEX IVO 38SMC361.4a201.4a ISO MAG (SEE ISR 1). AT 2121Z, [redacted 1.4a] WAS CLEARED TO RTB. AT 0005Z, [redacted 1.4a] HANDED BACK TO THE LRE. AT 0036Z, [redacted 1.4a] LANDED AT OKAS. FMV WAS EXPLOITED BY DGS 1."
Why it matters: Full mission narrative establishing sortie timeline, sensor packages, supported operation, and post-mission exploitation chain.
Page 1
"(S//REL) [redacted 1.4a] OBSERVED A UAP AT 2043Z FLY NORTH TO NORTH EAST AND FOLLOWED AS LONG AS POSSIBLE. [redacted 1.4a] SCREENER COULD NOT GET A POSITIVE ID ON THE UAP."
Why it matters: Verbatim UAP observation entry including direction of travel and lack of positive identification by the screener.
Page 6
"Initial Contact DTG: 202043:00ZMAY22"
Why it matters: Precise timestamp of UAP initial contact.
Page 6
"Friendly Aircraft Altitude/Depth: 18,000FT"
Why it matters: Only quantitative kinematic value recorded (own-ship altitude); UAP altitude/velocity/trajectory recorded as UNK.
Page 6
MG Richard A. Harrison
USCENTCOM Chief of Staff (declassification authority) · USCENTCOM · Page 1
OKAS (takeoff and landing ICAO), Kuwait
Page 4
Iraq (operating area)
Page 1
Killbox 89AS
Page 4
Tasked Start Point 38S MC 361.4a 201.4a (MGRS, partially redacted)
Page 5
Friendly Aircraft Location 38S MC 851.4a 771.4a (MGRS, partially redacted)
Page 6
UAP First Seen Location 38SMC791.4a701.4a (MGRS, partially redacted)
Page 6
196 ATKS
Air Force · Page 1
609 CAOC / 609 AOC
Air Force · Page 2
163 AW
Air Force (Air National Guard) · Page 2
12 AF PAROC
Air Force · Page 2
DGS 1 (Distributed Ground Station 1)
Air Force · Page 1
MAG (supported unit; redacted)
Page 5
LRE (Launch and Recovery Element)
Page 1
Aircraft callsign / asset identity throughout the narrative
Likely reason: 1.4a (intelligence sources, methods, activities)
ATO Mission Number
Likely reason: 1.4a
POC, QC, and Approver names, phone numbers, and emails
Likely reason: FOIA Exemption (b)(3) 10 U.S.C. 130b and (b)(6) personal privacy
Aircraft Callsign in ACEQUIP block
Likely reason: 1.4a
Asset Type (Aircraft) and Aircraft Tail Number(s)
Likely reason: 1.4a, 1.4g (intelligence sources/methods; weapons of mass destruction guidance does not apply — likely platform identity)
MGRS easting/northing digits in Tasked Start Point (38S MC 36X.Xa 20X.Xa) and BE Number
Likely reason: 1.4a
Supported operation name (OP [redacted]) and precoord callsign
Likely reason: 1.4a
MGRS digits in Friendly Aircraft Location (38S MC 851.4a 771.4a) and UAP First Seen Location (38SMC791.4a701.4a)
Likely reason: 1.4a
Observer/screener identity in UAP description block
Standard USCENTCOM MISREP form (MISREP undefined-7528881) on a 196 ATKS reconnaissance sortie. Sortie timeline (all 2022): takeoff OKAS 200542Z; LRE handover 200551Z; SIGINT via AHv2 0614Z-2346Z; on-station ISO MAG 0927Z-2121Z; UAP initial contact 202043Z; off station 210005Z; land OKAS 210036Z; engine shutdown 210046Z. Total time on station 18h14m; total mission time 18h54m. Mode 3 IFF: 2232. Killbox: 89AS. Declassification by MG Richard A. Harrison, USCENTCOM Chief of Staff, 8 October 2025; bates MDR 25-0094 thru MDR 25-0099 / JS-250710-TM8S; Approved for Release to AARO 10/17/25. Aircraft type, tail number and callsign all redacted under 1.4a/1.4g — platform identity not recoverable from this document alone. Document also contains a 'GENTEXT' caveat (per manifest description) that descriptive/estimative language reflects the reporter's subjective interpretation; this caveat text is not present verbatim in the OCR'd MISREP body.
The report does not describe its shape, color, or size.
The report states that the object moved north and northeast but does not specify its speed or altitude.
AIRHANDLER VERSION 2 (AHv2)
sensor · Page 1
ANDAS4 (targeting pod)
sensor · Page 3
ISR aircraft (type and tail redacted under 1.4a, 1.4g)
aircraft · Page 4
Likely reason: 1.4a
During a military flight in Iraq, an observer spotted an object in the sky. He saw it moving north, then slightly east, and attempted to track it.
The surprising detail is that tracking didn't solve the mystery. The observer couldn't identify the object, and the report offers almost no description of its appearance. Nevertheless, it's possible to learn from it what transpired—and also what's missing.
The flight was a reconnaissance mission: a flight designed to gather information and observe the area. During the mission, the observer noticed a single object. The sighting was recorded in a US Army report, alongside details about the flight's activity.
According to the report, the object moved north and northeast. That is, it advanced northward, with a slight eastward movement. The observer tried to track it as best he could but couldn't identify it with certainty.
The report describes an attempt to track the object but doesn't explain what the observer saw during the tracking. There is no description of its shape, color, or size. It also doesn't state whether the object was near or far, or how long the tracking lasted.
We can learn that there was a sighting of a single object and that its direction was recorded. But there aren't enough details to understand what the object was or to estimate its size. Other parts of the record were redacted, but the description of the sighting itself is brief and clear: the object was seen, and the observer tried to track it.
The report does not describe the object's shape, size, or altitude, nor does it explain what it was. It also doesn't offer a possible mundane explanation, such as a known aircraft or a natural phenomenon.
One direction was recorded in the sky, and one simple question remains: What exactly did the observer see?