Directive
PURSUE Release 01 originated in President Donald J. Trump's February 19, 2026 public directive calling for federal agencies to identify and release government files related to UAP, UFOs, alien life, extraterrestrial life, and adjacent records. The Department of War page presents PURSUE as the resulting publication system, run with support from the Office of the Director of National Intelligence to locate, review, declassify, and release unresolved UAP-related records from across federal holdings.1
Release 01
The first tranche was cleared for release on May 8, 2026. Its CSV lists 162 records: 120 PDF rows, 28 video rows, and 14 image rows. The named agencies are the Department of War, FBI, NASA, and Department of State, with four rows carrying no agency value in the CSV.12
The Department of War describes the tranche as unresolved material. In the page's own framing, these are cases where the government could not make a definitive determination about the reported phenomena, whether because of limited data, incomplete reporting, or other evidentiary limits. The page also publishes a statement attributed to Secretary of War Pete Hegseth, who framed the release as part of a broader transparency effort and said the files had previously been held behind classification.1
Source Corpus
The corpus is not one story. It is a cross-agency release that combines older historical holdings with newer military reporting. FBI rows include sections from the 62-HQ-83894 UFO case file and several image records. Department of War rows include mission reports, range-fouler reports, email correspondence, unresolved-video records, DVIDS-hosted MP4 assets, and related still imagery. NASA rows include Apollo, Gemini, and Skylab transcripts or media. Department of State rows include diplomatic cables from Papua New Guinea, Kazakhstan, Georgia, Turkmenistan, and Mexico.2
Publication Structure
The public site renders the release table from uap-csv.csv. Each row maps to a remote PDF, image, DVIDS page, or direct MP4 source rather than to a locally hosted copy. That row-level structure matters because several release records share related files, pair a mission report with a video, or use DVIDS metadata to carry the playable media source.2