THE SOURCE
Roughly eighteen infrared video clips from the U.S. Department of War’s PURSUE Release 02, published at war.gov/ufo on 22 May 2026, all assessed by AARO to U.S. military sensors operating in the U.S. Central Command area during 2020. Their uploader-defined dates run from February to November 2020 and cluster in August to November. They include DOW-UAP-PR055, PR059 and PR077 to PR095.
What this briefing is
This briefing does not take a single clip. It takes a wave. Across PURSUE Release 02, around eighteen of the video clips share three properties: the same theatre, the Central Command area; the same year, 2020; and uploader dates that bunch together heavily in the autumn of that year.
That is a pattern, and patterns have to be read differently from clips. Release 01 Briefing 20 did this for the Central Command mission reports, reading a batch rather than a document. This briefing does the same for the 2020 video wave, and the question is the one that always governs a cluster: what does the repetition prove, and where does it stop proving anything. The general grounding for the footage itself is in Release 01 Briefing 3.
TL;DR
The 2020 Central Command clips are not one event. They are a run of separate encounters, dated by their uploaders across the year and concentrated in roughly August to November 2020. Each is an infrared clip of a U.S. military sensor tracking an “area of contrast” it could not identify. Several run four to five minutes. The titles are individual: a date, a callsign, an observation.
Read as a wave, the set shows something a single clip does not: through one year, in one theatre, U.S. aircrew repeatedly encountered and recorded unidentified objects, often enough to fill eighteen clips. That is a sustained operational pattern rather than a handful of isolated incidents.
The wave also has the limit every cluster has. A run of similar reports is consistent with a real recurring phenomenon; it is equally consistent with one ordinary, recurring cause encountered many times by aircrew who, once primed, recorded it each time. The clips individually carry no telemetry and resolve no identities. This briefing is labelled source tier 2: the set establishes recurrence and does not establish what recurred.
What a wave establishes that a clip cannot
A single clip is always vulnerable to the lonely-data-point problem. It could be an artefact, a one-off, a fluke of one sensor on one day.
A wave closes that down. Eighteen separate clips, separate dates, spread across a year and tracked by military sensors, are not a fluke of one recording. The set establishes, firmly, that encounters with unidentified objects were a recurring feature of Central Command operations in 2020, frequent enough and consistent enough to generate a steady stream of footage. The military was not seeing one strange thing. Its aircrew were seeing something they could not identify, again and again, and pointing sensors at it each time.
That is a real and substantial finding. The phenomenon, whatever its nature, had operational regularity in that theatre that year. A reader is entitled to take the recurrence seriously, because the recurrence is the best-supported thing in the whole set.
Where the pattern stops
Here is the discipline a wave demands. Recurrence is not identity, and a cluster is not automatically a mystery.
Consider how a wave of lookalike reports forms. A single recurring ordinary cause, the Central Command theatre in 2020 had no shortage of candidates, drones of many nations, balloons, surveillance and reconnaissance traffic, can be encountered dozens of times. Each encounter is logged separately. Add a second effect: once aircrew in a theatre know that unidentified objects are being seen and reported, they notice and record more of them. The reporting rate climbs partly because the watching has intensified. The result is a wave that looks impressive in aggregate and may, object for object, be ordinary.
This is not a claim that the 2020 objects were ordinary. It is a plain statement of what the wave cannot do. Eighteen clips of unmeasured objects is eighteen times the footage and zero times the measurement. The cluster shows the encounters kept happening. By its size alone it does not show the encounters were extraordinary.
A note on the upload dates
One detail separates parts of this wave from much of Release 02, and it cuts in the footage’s favour. Several of the 2020 clips were uploaded to a classified network in 2020 itself, the same year and in some cases the same month as the encounter, rather than years later. Contemporaneous upload is a modestly better provenance signal than a long gap: it means the clip entered the system close to the event, with less time and fewer hands between the sensor and the archive. It does not lift the chain-of-custody caveat from Release 02 Briefing 1, which still applies to the release as a whole. But within this wave, the clips uploaded in 2020 sit on slightly firmer ground than those uploaded in 2024.
What the file says
It establishes that across 2020, in the Central Command theatre, U.S. military sensors repeatedly captured and tracked unidentified objects, generating roughly eighteen separate clips, with the encounters clustering in the autumn. It establishes that this was a sustained operational pattern, not isolated incidents, and that the recurrence is documented through an official, traceable channel. It establishes that several of the clips were uploaded contemporaneously, in 2020, which gives that subset a firmer provenance. As a wave, the set is a substantial tier 2 record of a recurring operational reality.
What the file does not say
It does not establish what the objects were. Eighteen clips with no telemetry resolve no identities, and a cluster of similar infrared captures is consistent with a recurring ordinary cause as much as with anything unusual.
It does not establish that the size of the wave makes it a mystery. Reporting waves form partly because a recurring cause is encountered many times and partly because heightened attention lifts the recording rate. The number is a fact about frequency, not about nature.
It does not establish a single coherent event. These are separate encounters on separate dates; the only things they share are the theatre and the year.
It is labelled source tier 2. The 2020 Central Command wave is genuine, official, and substantial; it shows something unidentified kept being encountered, and leaves entirely open what that something was.
What to watch
Two things are open: whether later tranches thicken the run with more clips from the same theatre and year, and whether anything ever names the recurring cause. The contemporaneously uploaded subset entered the system closest to its events; those clips sit on the firmest provenance in the wave.
Read the file. Decide for yourself.
References and further reading
- DOW-UAP-PR055, PR059 and PR077 to PR095, PURSUE Release 02, U.S. Department of War, hosted at war.gov/ufo
- Presidential Unsealing and Reporting System for UAP Encounters, U.S. Department of War, war.gov/ufo
- AARO UAP Records, All-domain Anomaly Resolution Office, aaro.mil/UAP-Records
- Signals from the Periphery, Release 01 Briefing 20, on reading the Central Command mission reports as a batch
- Signals from the Periphery, Release 01 Briefing 3, on reading infrared footage, and Release 02 Briefing 1, on the chain-of-custody caveat