THE RELEASE
(Unchanged: PURSUE Release 01, 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.)
Why this series exists
For eighty years, this subject has run on stories: testimony, leaks, recollections, secondhand accounts of documents nobody outside could read. On 8 May 2026, that changed in a way that is easy to undersell. The government began publishing the paperwork itself, the actual mission reports, cables, transcripts and case files in which the United States logs encounters its own people cannot identify, on a .gov address anyone can visit. After decades of being told what the files say, you can now read them.
Most of this material has never been read carefully in public, and that is the job this series takes on. Each briefing picks one document, or one coherent group of documents, and does the same things every time: says what the file is, summarises what it says and what it does not say, labels what kind of source it is, and links the original so you can check every word. No verdicts at the end; the judgment is yours. Before any of that is useful, though, you need to understand the release itself: what it is, who published it, how the documents are structured, and how to read one. That is this briefing.
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 programme it calls PURSUE. This first release 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.
Two things are true at once, and this series will hold both all the way through. The release is real, official, primary-source material of a kind the public has rarely seen, the genuine article. It is also heavily redacted, procedurally dry, and much of it is routine paperwork. 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, and this site is going to read all of it.
The whole series is evidence tier 2: primary documents. The tier is a label, not a verdict. It tells you what kind of source you are reading, and this briefing shows you how to read it. What the files add up to is, from the first briefing to the last, your call.
Who published it, and under what authority
The release sits under a programme 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 programme, 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.
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: the first is what the provenance settles, the second is the question it hands to you.
The shape of the collection
(Unchanged from the deployed v2, in full: the 160 items as a stack of unrelated material; photographs and the 28 infrared clips; the U.S. Central Command set as centre of gravity, 2016 to 2025; the State Department cables; the NASA spaceflight transcripts; the FBI files; the 1940s and 1950s National Archives layer with the analysts’ line “they cannot be disregarded”; every block gets its turn.)
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 qualifier is theirs, and it stays attached in every briefing here. Read enough of these blocks and something striking emerges: this is the rawest descriptive language the subject has, written by the people looking at the thing, before any analyst, journalist or believer got near it.
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 sit overwhelmingly on operational detail and personnel identities. The UAP description is usually the part left visible.
The same-sortie 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. A balloon recorded as a balloon, an unknown recorded as an unknown, in the same sortie, on the same form.
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 programme the documents refer to as SPEAR. A briefing later in this series takes the Range Fouler system on its own, because a routine, structured intake form for these intrusions is itself a fact worth sitting with: recurring problems get forms, and this one has had a form for years.
What the files say
The files show a standing, bureaucratic process for recording encounters with objects the military’s own aircrew cannot identify, and a steady stream of such reports across at least a decade in one theatre alone. They carry the full classification trail: reported, classified, held, then reviewed and released through an official, traceable channel. And they preserve the raw descriptive language the observers used, round and white, triangular and metallic, moving at stated speeds and altitudes, before anyone reshaped it. For anyone studying how the UAP problem is documented inside the government, that primary language is the heart of the release.
What the files do not say
They do not say what the objects were. “POSS UAP” is a field observation, not a conclusion, and the analysis that might resolve a given contact, the complete sensor data, the follow-up assessment, is either not included in the release or sits under the redactions. The redaction codes themselves point at operational and personnel secrecy; what is under the black bars is, by definition, not part of the released record, in either direction.
The files also do not carry a headline. Press coverage of the release was notably underwhelmed; the pages are procedural, and no single document announces itself. Whether the meaning lives in single pages or across the whole stack is exactly the kind of question you can only answer by reading across the stack.
How this series reads it
The plan for the briefings ahead is to go through the release at a sustainable pace, roughly one document or document group at a time, applying the same template every time. Striking files and routine files get the same treatment, because a record that only briefs the exciting documents is not a record, it is a highlight reel.
No briefing ends with a verdict. Each one tells you what the file is, what it says, what it does not say, and where to read it; the tier names the kind of source; the judgment travels home with you. The tier system has its own page, Evidence Standards, and this release is tier 2 throughout: primary documents, every one a link away.
Where this is going
Here is the honest excitement under all the procedure. For the first time, this subject has receipts, and the receipts keep coming: PURSUE is a rolling programme, with new tranches promised every few weeks, each one landing in this series as it arrives. Somewhere in this stack, or in the next one, or the one after that, there may be a file you read twice and then read again. The only way to know that file when you meet it is to know what the ordinary ones look like, and the only way to know the ordinary ones is to read them. That is what this series is for: the whole drawer, one file at a time.
The next briefing takes the first individual case, and it is a strange one in the telling: six federal agents, and orbs launching orbs.
Read it yourself
Every document cited in this series links to its government source; the release itself is at war.gov/ufo.
Read the files. Decide for yourself.
References and further reading
(Unchanged from deployed v2: PURSUE at war.gov/ufo; AARO UAP Records; AARO Declassification Information Paper 2025; example primary document DOW-UAP-D38; press coverage, CBS News and ABC News, May 2026.)