Release one, what is actually inside the Department of War's first UAP document drop

Mikey · 21 May 2026

THE RELEASE

PURSUE Release 01, the first tranche of the Presidential Unsealing and Reporting System for UAP Encounters. Published by the U.S. Department of War at war.gov/ufo on 8 May 2026. Records sourced from multiple federal agencies, 1940s to 2020s.

What this briefing is

This is the first in a series. The plan is simple. The government has begun publishing its backlog of unidentified anomalous phenomena records, and most of it has never been read carefully in public. Each briefing on this site takes one document, or one coherent group of documents, and does the same four things: says what is in it, says what it reliably establishes, says what it does not, and assigns an evidence tier.

Before any of that is useful you need to understand the release itself. That is what this briefing covers. What it is, who published it, how the documents are structured, and how to read one without being either fooled or bored.

TL;DR

On 8 May 2026 the Department of War published the first tranche of unresolved UAP records held across the federal government, under a program it calls PURSUE. This first release, PURSUE Release 01, gathers roughly 160 videos, photographs and documents, with dates running from the 1940s to the 2020s, and more tranches are promised on a rolling basis. The largest and most coherent block is a set of U.S. Central Command files, mostly aircrew mission reports and Range Fouler debriefs from the Middle East theatre between 2016 and 2025, internally declassified on 8 October 2025 and approved for release to the All-domain Anomaly Resolution Office ahead of publication.

The honest first impression is mixed. The release is real, it is official, and it is primary-source material of a kind the public has rarely seen. It is also heavily redacted, procedurally dry, and in many individual cases entirely mundane. Both of those things are true at once. The value is not in any single dramatic document. It is in the fact that, for the first time, the actual paperwork of how the U.S. military logs these encounters is open to anyone willing to read it.

This whole series is evidence tier 2: primary documents. That is a strong tier. It is not the same as proof of anything anomalous, and this briefing explains why.

Who published it, and under what authority

The release sits under a program the Department of War calls the Presidential Unsealing and Reporting System for UAP Encounters, PURSUE for short. The framing is a directive from the President to find, review, declassify and publicly release the government’s unresolved UAP records on an accelerated timeline. It is an interagency effort: the Department of War coordinates, with records drawn in from the White House, the Office of the Director of National Intelligence, the Department of Energy, AARO, NASA and the FBI. The documents are hosted on the official war.gov domain. PURSUE is described as a rolling program, with Release 01 the first tranche and further releases expected every few weeks.

That provenance matters for one specific reason. It means the documents are authentic government records, not leaks and not reconstructions. When this site cites one, you can follow the link to a .gov address and read the same page. That is the floor of what makes a source trustworthy, and this release clears it.

What the provenance does not do is vouch for the contents. A genuine government document can still record a witness who was mistaken, a sensor that glitched, or a balloon. Authentic is not the same as anomalous. Keep those two ideas in separate pockets.

The shape of the collection

The roughly 160 items are not one archive. They are a stack of unrelated material pulled from different agencies and eras, and not all of it is paper. Alongside the documents, the release includes photographs and 28 short infrared video clips, sensor footage of the objects themselves. It helps to see the main blocks.

The centre of gravity is the U.S. Central Command set. These are aircrew documents from the Middle East theatre: the Arabian Gulf, the Persian Gulf, the Strait of Hormuz, Syria, Iraq, Djibouti, the Gulf of Aden, the Mediterranean, with a few from further afield. They run from 2016 to 2025. Most are mission reports or Range Fouler debriefs. This is the block this site will work through first, because it is recent, specific, and consistently formatted.

Around it sit smaller, older groups. A handful of State Department cables in which UAP events were reported back to Washington through diplomatic rather than military channels. A set of NASA spaceflight transcripts from the Apollo, Gemini and Skylab era. FBI files, including a large historical case file and a recent witness case. And a deep layer of 1940s and 1950s records from the National Archives, the early flying-disc era. Future briefings will reach all of them.

How to read a Central Command mission report

Most of the CENTCOM block is built on one template, the MISREP, short for mission report. It is the routine after-action paperwork an aircrew or operations centre files. The vast majority of MISREPs in military life have nothing to do with UAP. The ones in this release are the ones that happen to contain a UAP observation, logged in a dedicated block.

A reader opening one for the first time should look for four things.

The declassification stamp at the top. On the CENTCOM set this reads as declassified by the USCENTCOM Chief of Staff, with a date of 8 October 2025, and a line approving release to AARO. That is your authenticity anchor.

The GENTEXT/UAP block. This is the part that matters. It is a short, terse, often single-paragraph description of what was observed. The language is clipped military shorthand. A typical entry reads like a description of a round white object, or a triangular metallic object, observed at a stated time, altitude and speed, in the vicinity of a grid coordinate. The aircrew label these “POSS UAP”, possible UAP. The word “possible” is doing real work and should not be sanded off.

The redaction codes. You will see “1.4(a)” repeatedly. That is a reference to Executive Order 13526, section 1.4(a), the category covering military plans, operations and capabilities. You will also see “(b)(6)” and “(b)(3)”, which are Freedom of Information Act exemptions, the first protecting personal privacy and the second covering information withheld by statute, here mostly the names of service members. What this tells you is concrete: the redactions in these files are overwhelmingly about hiding operational detail and personnel identities, not about hiding the UAP observation itself. The UAP description is usually the part left visible.

The discipline of the aircrew. This is the quiet, important detail. In at least one Syria mission report the crew log a possible UAP and, a few lines later in the same flight, a separate possible balloon. They are not collapsing everything strange into one category. They are recording a balloon as a balloon and an unknown as an unknown. That internal distinction is worth more than any single dramatic sighting, because it tells you the observers were calibrated.

The Range Fouler form

The second common document type is the Range Fouler debrief. “Range fouler” is the military term for something intruding into airspace where it should not be, a training range or operating area. The Navy uses a standardised form to log these. Several appear in the release.

The form is structured: date, time, location, altitude, the observer’s crew position, a description block. It also carries an explicit note that the reports are sanitised of identifying information before analysis, handled through a program the documents refer to as SPEAR. A briefing later in this series will take the Range Fouler system on its own, because the existence of a routine, structured intake form for these intrusions is itself a meaningful fact. It means the military treats airspace incursions by unidentified objects as a recurring operational problem with its own paperwork, not as a novelty.

What this release reliably establishes

It establishes that the U.S. military has a standing, bureaucratic process for recording encounters with objects its own aircrew cannot identify, and that this process generated a steady stream of reports across at least a decade in one theatre alone. It establishes that these reports were classified, were held, and have now been reviewed and released through an official, traceable channel. It establishes the raw descriptive language the observers used, round and white, triangular and metallic, moving at stated speeds and altitudes, before any analyst, journalist or believer reshaped it. For anyone studying how the UAP problem is actually documented inside the government, that primary language is the single most valuable thing in the release.

What it does not establish

It does not establish that any object in these files is extraterrestrial, or even that it is genuinely unexplained once fully analysed. “POSS UAP” is a field observation, not a verdict. Many of these contacts, given complete data, would likely resolve into drones, balloons, aircraft, sensor artefacts or atmospheric effects. The release does not include that complete data, and in many cases it has been redacted out.

It does not establish a cover-up by its redactions. The redaction codes point at operational and personnel secrecy, which is normal for any military document, not at the suppression of the UAP content. Reading every black bar as a hidden truth is the fastest way to lose a reader’s trust.

And it does not, on its own, deliver a dramatic story. Press coverage of the release was notably underwhelmed, and that reaction is fair on the merits. There is no single smoking-gun document here. The honest framing is that this is infrastructure, the paperwork layer of the phenomenon, and infrastructure is rarely thrilling. Its worth is cumulative, and only visible to someone willing to read across many files.

How this site will use it

The plan for the briefings ahead is to go through the release at a sustainable pace, roughly one document or document group per week, applying the same template every time. Striking cases and dull cases both get the same treatment, because a site that only briefs the exciting documents is not a record, it is a highlight reel.

Some briefings will be genuinely strange. Some will end with the conclusion that the most likely explanation is mundane. Publishing both is the entire point. The evidence tier system, which gets its own page, exists so that a reader always knows whether they are looking at a firsthand account, a primary document, a secondhand relay or a rumour. This release is tier 2 throughout. Strong, official, and still not the same as proof.

Read the documents yourself. Every one cited in this series links to its government source. The next briefing takes the first individual case.

Related wiki entries

The wiki entries below give background on the people, programmes and document types behind this briefing.

PURSUE · Department of War · USCENTCOM · Range Fouler · MISREP · Executive Order 13526 · AARO

References and further reading

• 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
• AARO Declassification Information Paper, 2025, aaro.mil
• Example primary document: DOW-UAP-D38, Range Fouler Debrief, Middle East, May 2020, hosted at war.gov
• Press coverage of the release, CBS News and ABC News, May 2026