top of page

The Strongest UAP Case In PURSUE Release 1 Is The One Nobody Has Named Yet. Thirty-Three Documents. Senior Intelligence Official On The Record. Western US, Late 2025.

  • Writer: Patrick Duggan
    Patrick Duggan
  • 2 hours ago
  • 6 min read

The Department of War's PURSUE Release 1 dropped on May 8, 2026, with 158 declassified UAP records. The mainstream coverage focused on the headline items the press release teased: 1947-era FBI Vault material on Oak Ridge, the 1970s Sandia Base file, the recycled documents from the 62-HQ-83894 case. Release 2 dropped May 22 with 64 more, and the cycle repeated — coverage centered on the "4 UAP Formation Iran 26 Aug 2022" video that DoW highlighted. Each cycle, the journalists who covered the release pulled out the items the press release pointed them at.


Tonight, while cross-correlating the full 222-record corpus against itself for clustering patterns, our pipeline surfaced something that none of the coverage has named yet. Thirty-three documents in Release 1, all dated only as "Late 2025," all in the Western United States, all with intentionally-withheld dates and locations. The set is anchored by an FBI 302 — the formal FBI interview transcript — with a senior U.S. Intelligence Community official describing a multi-witness, multi-sensor UAP encounter at "a sensitive government testing installation." Structurally, this is one of the strongest UAP receipts on the official record. It has been sitting in PURSUE for seventeen days. Nobody has surfaced it.



What the 302 says


The encounter begins with prior orb sightings in the area. Federal and state personnel conducted searches by helicopter to where the orbs had previously been seen. They found a "super-hot" orb hovering over the ground. The orb then traveled twenty miles at a speed too fast for the helicopter in pursuit. A swarm of lights appeared, moving in all directions. Four or five additional orbs flared up and down over the next thirty minutes across the area.


The senior intelligence community official witnessed the UAP with the naked eye. Two pilots in the same aircraft witnessed it through night vision goggles. Other pilots in separate aircraft also witnessed it. Ground-based observers with night vision also witnessed it. Multiple sensor systems captured imagery simultaneously. The thirty-two photographs in the cluster — eight in series A, twenty-four in series B — are reticle-centered monochrome images consistent with night-vision-device capture through ground-based optics. Most show a dark, circular object centered in a crosshair. One image, in the swarm phase, shows two elongated objects.


The witness stack is the structural argument. Naked-eye observation by a senior USIC official is one modality. Aircraft NVG observation by multiple pilots in multiple aircraft is a second modality. Ground-based NVG observation is a third modality. Sensor capture is a fourth. Four independent observation modalities corroborating the same event is the gold standard for UAP case strength. The 2004 Nimitz incident had radar plus IR plus four-witness aircrew. The 1989 Belgian Wave had ground witnesses plus radar plus F-16 intercept. The Late 2025 Western US encounter has senior USIC plus multiple pilots plus multiple aircraft plus ground NVG plus sensor imagery plus federal-state coordination plus helicopter pursuit plus thirty-minute duration plus multi-object swarm. The structural strength of this case is, by reasonable measure, at the top of the publicly disclosed corpus.



Why no coverage


The case is buried inside a thirty-three-document evidence package with the labels "FBI Photo A001" through "FBI Photo A008" and "FBI Photo B001" through "FBI Photo B024." The incident's date and location are intentionally withheld in the PURSUE release. The narrative description on each individual photograph reads "the date and location of the event have not been provided. The original imagery was altered with redactions before being submitted to AARO. An accompanying mission report was not provided." Read in isolation, each of those photographs is a forgettable monochrome dot. Read together, with the FBI 302 interview that ties them together, the package describes a major UAP encounter.


The press cycle that covered PURSUE saw thirty-three FBI photos, assumed they were related to the historical 62-HQ-83894 Vault material that dominates the rest of the FBI submission, and moved on. The actual relationship — that these photos are sensor captures from a 2025 Western US military installation incident, not from the 1947-era historical FBI files — is buried in the description text of a single 302 interview document at the tail of the release. The signal is in the metadata that ties the cluster together, not in any individual document.


This is a recognizable pattern. Large declassification dumps almost always have one or two records buried where the headline-relevant material isn't. Releases get covered on first-day reading, and the cross-reference work that surfaces the actual narrative happens months later, if at all. We saw the same shape with Snowden documents, with the Pandora Papers, with the Epstein flight logs. The infrastructure that makes deeply-buried records discoverable in real time is not journalism's strength; it is database-archeology's.



What we can and cannot say


We cannot say which testing installation. The Western US has roughly seven plausible candidates — Nellis Air Force Base Range Complex / NTTR in Nevada, Tonopah Test Range in Nevada, Dugway Proving Ground in Utah, China Lake Naval Air Weapons Station in California, Edwards Air Force Base in California, White Sands Missile Range in New Mexico, and the DOE Nevada National Security Site. The PANTEX nuclear weapons assembly facility in Texas is a marginal eighth candidate given that DOE-UAP-D001 in Release 2 is enhanced PANTEX imagery and the nuclear-infrastructure-attracts-UAP pattern (Hastings, Salas) recurs across the entire PURSUE dataset. Without the redacted location data, all eight are live candidates. Of them, Nellis/NTTR is the highest-probability inference: restricted airspace, helicopter pursuit, federal-state jurisdictional overlap (Nevada civilian airspace borders the range), and a documented history of "orb"-class observations in the official record.


We cannot say which month in Late 2025. The reasonable bound is November to December 2025, narrower if anyone can correlate to NORAD scramble logs, FAA temporary flight restrictions, or local news pickups from the November-December 2025 window. The orb-swarm activity at this scale would have generated civilian witness reports if it occurred near populated airspace.


We can say this with confidence: a senior U.S. Intelligence Community official, on the formal record, with FBI 302 paperwork, with two pilots in his aircraft on NVG, with other aircraft witnesses, with ground witnesses, with sensor imagery, witnessed a four-or-five-object orb swarm at a sensitive government testing installation in late 2025 that displayed thermal signatures so distinct that the lead object was described as "super-hot," traveled twenty miles faster than a pursuit helicopter could match, and persisted in observable activity for thirty minutes. The receipt is timestamped May 8, 2026. The receipt has been public for seventeen days. The receipt does not appear in any major media coverage of PURSUE.



What this is and what it isn't


This is not a conclusion about what was observed. It is a document-archeology finding about what the U.S. government has placed in the official record and the public did not notice. The orbs may be classified U.S. test platforms — Lockheed Martin's "Cormorant Tail" or a similar tier-zero black project — and the senior intelligence official's witness statement may exist precisely because the test was significant enough that even cleared personnel did not know what they were watching. The orbs may be foreign adversary craft — the time frame post-dates the Chinese balloon incident by roughly thirty months and overlaps with the Russian Drone-of-Theseus campaigns documented in our own threat intel. The orbs may be something the government still considers genuinely unidentified and is releasing precisely because they cannot identify them. Each interpretation has different downstream consequences for what U.S. counter-air doctrine should look like.


What is certain is that the document is on the public record. The senior official's first-person account is in PURSUE. The thirty-two photographs are downloadable. The methodology that surfaced the cluster is repeatable. We pulled the 222-record corpus, ran a date-clustering aggregation, sorted by cluster size, looked at the largest cluster, parsed its descriptions, and found the 302. Total elapsed wall-clock time: approximately four minutes of database work after the corpus was loaded. The data was always there. The question is whether anyone was looking.



The methodological lesson


This is the same shape as our threat intelligence findings throughout this week. We had Megalodon's command-and-control endpoint indexed forty-nine days before the campaign fired. We had TeamPCP's blockchain canister months before the public naming. The pattern that ties those receipts to this UAP case is identical: the data was in the corpus, the detector was the missing piece, and once the detector ran, the receipt was instant. The defender-side asymmetric edge belongs to whoever runs the cross-correlation work that nobody else has the tooling or the discipline to run.


For UAP specifically, the lesson is that PURSUE is not a press-release-driven story. PURSUE is a data corpus. The interesting findings will, by structural rule, be the ones that require parsing the relationships between documents rather than reading any individual document. Release 3 is being prepared. The records housed at war.gov/ufo number 222 today and will grow. The clusters we have not yet surfaced will outnumber the ones we have.


The detector finds the case. The case is timestamped. The receipt is open.




How do AI models see YOUR brand?

AIPM has audited 250+ domains. 15 seconds. Free while still in beta.


bottom of page