Sixty-nine of the 294 cases in the declassified archive carry the CENTCOM/Middle East tag. That is more than any region except the United States itself. Iraq, Syria, the Arabian Gulf, the Gulf of Aden, the Gulf of Oman, the Arabian Sea, Iran. The dates run 2016-2024, with a heavy cluster in 2020-2022. Sorting through the stack, the files come in three flavors: Mission Reports (MISREPs) from Air Force squadrons, Range Fouler forms from Navy crews, and a long run of sensor videos with operator-written titles like "Syrian UAP instant acceleration" and "4 UAP Formation Iran 26 Aug 2022 over water." What follows is what the paper records actually say, case by case, and at the end, the boring structural reason the count is probably this high.
The earliest file: a P-8A off Latakia, November 2016
The oldest CENTCOM-tagged record in the archive is DOW-UAP-D055, a one-page mission briefing slide dated November 18, 2016. A Navy P-8A monitoring activity in the Eastern Mediterranean picked up an unidentified low-flying object 55 nautical miles northwest of Latakia, Syria, on its EO/IR sensor. The slide describes it as a possible missile launch from an unknown origin, appearing to be in "sea skim mode," traveling at approximately 500 knots on a southeasterly heading. The crew held it for about two minutes, watched it pass between a Russian vessel identified as INGUL ARS and one unidentified vessel, and lost visual roughly 40 nautical miles northwest of Latakia.
Then the assessment section drains all the drama out. The mission commander characterized the interaction as safe. The task group comment notes this was the first observed occurrence of possible missile activity by P-8 aircraft in the Eastern Mediterranean and assesses it as standard activity consistent with the assessed activity of the group it was tracking, identified in the slide only as KCTG. Filed, briefed, moved on. It still ended up in the UAP release nine years later, which says something about how wide the net was cast.
What a MISREP looks like when a UAP shows up
The workhorse document in the CENTCOM stack is the MISREP, a standardized form that logs takeoff time, time on station, fuel, taskings, and, in a free-text GENTEXT field, anything the crew thought worth writing down. DOW-UAP-D010 is a clean example: an Air Force ISR mission over Iraq on May 6, 2022, flying in support of Operation Inherent Resolve, twenty-plus hours of surveillance work compressed into six pages of form fields.
The UAP content is two sentences in the observation GENTEXT. Between 1514Z and 1934Z the crew "OBSERVED 5X UAP FLY ACROSS THE SCREEN." The first had the visual recognition profile of a possible missile. The remaining four, in the report's own words, "FIT CLOSER TO THE PROFILE OF POSSIBLE BIRDS." The weather line notes that dust hindered most of the full motion video collection that day. So the archive's formal count of five UAP on this mission may resolve, per the reporting crew itself, to one missile and four birds seen through dust. The form logs it as UAP anyway, because at the moment of observation nobody had identified anything, and that is what the U in UAP does.
The declassification trail on these pages is worth a glance. Each one is stamped "Declassified by MG Richard A. Harrison, USCENTCOM Chief of Staff," with a Mandatory Declassification Review number and the line "Approved for Release to AARO." The CENTCOM files did not leak. They were pulled through a review pipeline, one MDR case number at a time, in 2025 and 2026.
The Navy's version: a checkbox form for things in the range
DOW-UAP-D038 is a Range Fouler Debrief, the form a Navy crew fills out when something intrudes into controlled airspace during operations. It reads like a DMV form for anomalies. Date: May 14, 2020. Time of detection: 20:40Z, at night, over the Arabian Gulf during an ISR tasking. Was the contact moving: yes. Stable trackfile: intermittent. Number of contacts in group: one. Then a shape checklist, Round, Square, Balloon-shaped, Wings/Airframe, Apparent Propulsion, Metallic, Translucent, Reflective. The only box checked is Round.
The narrative field is where the file earns its place in the archive. The crew describes a solid white object that flew through the sensor's field of view, was briefly lost, then reacquired. They followed it as it made what the report calls erratic movements above the water, got 4x zoom on it, and finally lost it due to poor track placement, with the sensor operator continuously slewing to keep eyes on. The form also states, in its boilerplate, that SPEAR sanitizes all reports of identifying information before analysis, so no aircrew names survive into the record. No shape estimate beyond the checkbox, no size, no conclusion. One round white thing, low over the gulf, at night.
Strike Eagles over Shaddadi, with jamming in the same log
DOW-UAP-D019 is a MISREP from a two-ship of F-15Es out of Muwaffaq Salti Air Base, flying defensive counter-air over Syria in the early hours of February 21, 2023. The mission narrative is a timeline, and reading it in order is instructive. At 0021Z-0024Z the flight received radar jamming in the vicinity of Shaddadi at FL270. At 0025Z, same vicinity, "OBS 3X POSS UAP" at FL240, weapon system video produced, nothing further to report. At 0135Z, again near Shaddadi, one possible balloon at FL210. Video produced. Nothing further.
The archive categorizes this case under Balloon, one of the few CENTCOM cases with any shape tag at all, and that tag comes straight from the aircrew's own "POSS BALLOON" call. The three possible UAP an hour earlier never get another word. Somewhere there is weapon system video of both, and the form says so, but the paper record ends at NFTR.
Twenty hours over the Strait of Hormuz, two UAP, five minutes apart
DOW-UAP-D064 is the file that best explains the CENTCOM numbers without meaning to. An Air Force attack squadron aircraft took off at 0608Z on November 2, 2020, and landed at 0250Z the next day, 20.42 mission hours, supporting Naval Forces Central Command over the Arabian Gulf, the Strait of Hormuz, and the Gulf of Oman. In all that time the narrative logs exactly two anomalies: a UAP observed at 2143Z and another at 2148Z, the second noted as proceeding northwest. Two lines in a twenty-hour log, cross-referenced to observation entries, the full motion video exploited afterward per the report.
Why CENTCOM, probably
The files never answer this directly, but they carry the answer in their formatting. Every one of these documents exists because a reporting channel already existed. The MISREP has a GENTEXT field waiting for anything unusual. The Navy has a preprinted form specifically for uninvited contacts in a range, checkboxes included. Crews flying 20-hour ISR orbits stare at sensor feeds for a living, over an airspace full of missiles, drones, balloons, and birds, several of which appear in these reports as the crews' own first guesses. Point that much glass at that much contested sky, wire it to standardized paperwork, and a UAP archive accretes on its own. The stamps on every page show where the paper went next: CENTCOM reviewed the files case by case and approved them for release to AARO in batches through 2025 and 2026.
None of that explains any individual file. It does not explain a round white object maneuvering over the water, or why a Strike Eagle flight logged radar jamming and three possible UAP over Shaddadi within minutes of each other. The videos that go with several of these reports sit in the Pentagon and military UAP videos collection, and the newest additions to the archive land in the latest release page as they arrive. The CENTCOM count stands at 69. Given how the last few releases have gone, that number reads less like a total than a pause.