Database Anomaly Record The Account Physics Nuclear Map Key Docs Videos Archive The System Timeline Investigation

A four-act investigation into institutional behavior

How does an institution manage something it cannot explain?

The US national security apparatus has been in contact with unexplained aerial phenomena since at least 1947. What it did with that contact—how it classified, routed, contained, and occasionally disclosed it—is now partially visible in 224 declassified primary-source documents. This is what those documents reveal about the machine, not just the phenomena.

The Architecture — how the system is built

The Playbook — the documented precedent

III

The Lens Applied — three contemporary cases

The Analysts — who mapped the system from outside

The Architecture

Before you can understand what the apparatus has done, you need to understand what the apparatus is. Five open questions. Five lines of evidence. One system.

The Structure

How UAP information moves through the government

The PURSUE corpus is not just a collection of anomalous incidents. It is an X-ray of an institutional information management system — one built for something it never fully explains.

When a military sensor records an object it cannot identify, what happens next is determined not by the object's nature, but by the institutional architecture it encounters. That architecture — the agencies, classification hierarchies, routing protocols, and oversight structures that determine what gets seen, by whom, and when — is now partially visible in the 224 documents of the PURSUE corpus. This is what it looks like.

Layer 1 — Detection

Sensor encounter reported at unit level

Pilot, crew, or automated system logs an anomalous observation. Report is filed within chain of command. At this stage: incident exists in institutional record.

↓

Layer 2 — Classification

Document enters classification architecture

Report is assigned a classification level (Confidential → Secret → Top Secret → SCI/SAP). Classification determines which oversight bodies can see it — and which cannot. Many UAP files carry unusual secondary routing codes not found in standard classification registries.

↓

Layer 3 — Interagency Routing

File distributed across agencies by design

The most significant finding from the PURSUE corpus's routing metadata: the same incident often appears in FBI, DoD, CIA, and ODNI file chains simultaneously — but no single agency holds the complete record. This is the compartmentalization David Grusch described in congressional testimony. The PURSUE corpus confirms the structure.

↓

Layer 4 — Classification Review

Long retention schedules protect program-level secrets

Kirtland-adjacent and nuclear-corridor files in the corpus carry classification review dates 40–50 years past their creation. Standard military records review at 25 years. Extended retention is reserved for program-level secrets — not individual incidents.

↓

Layer 5 — PURSUE Release

First formal institutional reversal — 2025/2026

The executive declassification order directed public release of UAP records. For the first time, the primary source moved from controlled to public domain before it could be managed. The 224 documents now in this corpus are the first the institutional apparatus allowed to escape the system as designed.

The Verdict Map

Five open questions — where the evidence stands

The analytical capstone of this investigation: five questions the corpus can partially answer, scored against 224 records.

Question 1

Is the phenomenon physically real?

Multi-sensor government records — FLIR, radar, electro-optical simultaneously — document objects that leave physical signatures across independent systems.

▉▉▉▉▉ Well-evidenced by the corpus

Question 2

Do the flight characteristics exceed known technology?

Instantaneous acceleration, zero inertial signature, transmedium operation — all documented in primary sensor data, all outside every known performance envelope.

▉▉▉▉░ Strong, with data limitations

Question 3

Is the nuclear clustering statistically significant?

The Sandia TOP SECRET file confirms what civilian researchers suspected: UAP reports cluster around nuclear infrastructure in the government's own classified record.

▉▉▉░░ Supported, not proven

Question 4

Has the institutional apparatus actively managed information?

Parallel routing, extended classification, civilian witness protocols, documented disinformation operations — the management architecture is confirmed by primary sources.

▉▉▉▉▉ Directly confirmed

Question 5

What is the origin of the phenomenon?

This question the corpus cannot answer. The machine is well-evidenced. The cargo is still undetermined. No document in the PURSUE corpus — classified or otherwise — provides a verified explanation. That gap is the honest answer.

▉░░░░ Open — not yet addressable from primary sources

The Playbook

Once you understand the architecture, you can read what it does. One documented case established the method. It has never been formally repudiated.

Albuquerque, New Mexico · 1979–1988

The Bennewitz Blueprint

Paul Bennewitz was a physicist who picked up real signals near Kirtland Air Force Base and reported them to the Air Force. What the Air Force did next is the most thoroughly documented example of institutional UAP information management on the public record.

Paul Bennewitz was not a crank. He held a doctorate in physics, ran a successful electronics company, and lived adjacent to Kirtland Air Force Base in Albuquerque — one of the most sensitive nuclear installations in the American complex, home to Sandia National Laboratories. He was methodical, technically literate, and serious about documentation. He was exactly the kind of person who notices things.

Beginning around 1979, Bennewitz recorded unusual electromagnetic signals from the direction of Kirtland. The signals followed patterns he couldn't match to any known military protocol. Separately, he and his family observed unusual aerial phenomena near the Manzano Mountains and the weapons storage areas of the base. He documented what he saw. He attempted to decode what he heard. And in 1980, he did something that sealed his fate: he wrote to the Air Force and told them what he had found.

"I have been doing a lot of research in these areas and I have some data that I think will be of interest to you."

Paul Bennewitz — letter to Kirtland AFB, 1980

The Air Force's interest was not what he expected. An internal investigation from late 1980 acknowledged that Bennewitz had recorded genuine signal activity near the installation and that his observations were consistent with reports from base personnel during the same period. Several Kirtland security officers filed corroborating reports.

Whatever Bennewitz had picked up, it was real enough to warrant attention from the Air Force Office of Special Investigations. What AFOSI concluded — and what they chose to do about it — would determine the rest of his life.

The assigned agent

Special Agent Richard Doty, AFOSI — Kirtland AFB

Doty has acknowledged in multiple interviews and in congressional testimony that he was assigned to feed Bennewitz fabricated information about extraterrestrial activity as a means of discrediting his legitimate signal intercepts and redirecting his research away from classified programs. He has stated that he acted under orders. The chain of command above him has never been formally identified.

The Operation

The campaign — five years, five phases

The disinformation fed to Bennewitz was detailed, internally consistent, and designed to be unverifiable. That was the point.

1980 — Early Engagement

Legitimization and access

Doty and other AFOSI personnel met with Bennewitz and initially appeared to validate his findings. They reviewed his recordings, expressed interest in his research, and created the impression his work was being taken seriously at the highest levels. This established trust and encouraged him to share everything he found.

1981 — Fabricated Documents

The disinformation payload

Doty began providing Bennewitz with fabricated documents describing an extraterrestrial presence, underground alien bases in New Mexico, and ongoing cooperation between the US government and alien entities. The documents were constructed to exploit what Bennewitz already believed and to push his interpretation of his real observations into increasingly unfalsifiable territory.

1981–82 — Network Seeding

Contamination of the research community

The fabricated materials were not contained to Bennewitz. Multiple UFO researchers and journalists received versions of the same documents through intermediaries connected to Doty and AFOSI. The mythology of the "Dulce underground base" and the "MJ-12" documents — which would shape UAP discourse for decades — trace their origin, in whole or substantial part, to this operation.

1982–83 — Escalation

Psychological pressure

As Bennewitz became more consumed by the fabricated narrative, the operation escalated. He was encouraged to decode messages he was told were extraterrestrial communications. His real intercepts were reframed within the alien mythology, making it impossible to evaluate them accurately. His sleep deteriorated. His behavior became erratic.

1988 — Outcome

Hospitalization and end of research

Paul Bennewitz suffered a complete mental breakdown and was hospitalized. He never returned to his research. The signals he had recorded — whatever they were — were never formally explained. The classified programs near Kirtland that appear to have generated them were never publicly acknowledged.

"We were trying to deflect him, to send him off in the wrong direction. The idea was to make him look so crazy that nobody would believe him."

Richard Doty — interview with journalist Greg Bishop, cited in "Project Beta" (2005)

Part Four

The Apparatus

The Bennewitz operation was not a rogue action by one agent. The PURSUE corpus is now a partial X-ray of the institutional infrastructure that ran it.

AFOSI Routing Patterns — Kirtland-Area Files (1975–1985)

A subset of AFOSI documents in the PURSUE corpus from the late 1970s and early 1980s carry dual routing: a standard AFOSI chain of custody alongside a secondary routing to an unspecified program office. The secondary routing codes do not match the standard AFOSI classification registry. This pattern — parallel routing that excludes normal oversight chains — is structurally identical to the compartmented management Doty described when discussing his authorization to run the Bennewitz operation.

Source: PURSUE Tranche 1 · AFOSI declassified 2025

Structural match

Civilian Witness Management Protocols — FBI/USAF Joint Files (1970s)

Several joint FBI-USAF documents in the corpus relate to the handling of civilian witnesses who reported aerial phenomena near sensitive installations. The documents describe a standardized approach that includes initial validation (to establish trust), assessment of the witness's access to classified information, and a determination of whether redirection or containment is warranted. The language is bureaucratic and procedural — suggesting this was established practice, not improvised response.

Source: PURSUE Tranche 1 · FBI declassified 2025

Procedural pattern

Classification Longevity — Kirtland-Adjacent Programs (1980s filings)

Documents in the corpus related to Kirtland and the surrounding New Mexico test corridor show unusually long classification retention periods relative to comparable files from other installations. Several files have classification review dates extending 40–50 years past their original creation date. This is consistent with the protection of program-level secrets that have never been formally acknowledged — the same programs that the Bennewitz operation appears to have been protecting.

Source: PURSUE Tranche 1 · USAF declassified 2025

Long retention

None of this proves the Bennewitz operation was formally authorized at the highest institutional level. What it establishes is that the operation was not anomalous within its environment. The apparatus that ran it — parallel routing, civilian witness management protocols, extended classification of sensitive installation programs — is visible in the public record. The Bennewitz operation was not a bug in this system. It was a feature.

III

The Lens Applied

The Bennewitz case documented a specific institutional methodology. Three contemporary figures each have a documented relationship with that same apparatus. Here is what the framework asks — not answers — about each of them.

A note on methodology

The primary methodology of this investigation is document-first: every conclusion is grounded in primary source material. This section is a deliberate exception. It applies a documented historical framework — the Bennewitz case — to three contemporary figures whose relationship with the institutional apparatus is a matter of public record, but whose inner experience is not.

We take all three individuals at their word about what they believe they have experienced. Nothing in this analysis requires any of them to be dishonest. The Bennewitz case established that the apparatus can shape the interpretation of genuine experience without the subject knowing it is happening. That is the only claim this framework makes. The questions it raises are institutional. The answers are not yet in the primary record.

Case 01

Bob Lazar

Physicist and electronics technician. Claimed employment at a classified facility designated S-4 near Papoose Lake, Nevada, adjacent to the Area 51 complex. Went public in 1989 describing nine extraterrestrial craft and a propulsion system using a then-unknown element he called Element 115. His account has been consistent across 35 years.

What can be established: Lazar's name appeared in a Los Alamos National Laboratory phone directory, partially corroborating his claim of prior work there. He passed a polygraph examination. George Knapp, an experienced investigative reporter, has maintained for decades that he found Lazar credible after extensive investigation. And in 2003, Element 115 — Moscovium — was synthesized for the first time, confirming the existence of an element Lazar had named 14 years earlier.

What the PURSUE corpus can offer

The flight characteristics Lazar described — instant acceleration from stationary, no visible propulsion signature, silent operation, apparent indifference to inertia — appear repeatedly in the PURSUE corpus as independently documented sensor observations across multiple decades. He was not the only person saying this. He was one of the first to say it publicly.

The institutional secrecy architecture Lazar described — compartmentalized programs, need-to-know restrictions so narrow that individual components are invisible to each other, classification structures that prevent oversight — is visible in the routing anomalies documented in the PURSUE corpus. The apparatus he described exists, at least in structural form.

What the Bennewitz framework asks

The core of the Bennewitz operation was this: take a person with genuine access to a real installation, give them a briefing that explains what they are observing in a specific and internally consistent way, and let the briefing do the work. Bennewitz had real signals. He was given a narrative about what those signals meant. He reported that narrative as evidence because he believed it was.

Lazar's account is structured the same way. He describes not just what he observed, but a ready-made interpretive framework he was given through official briefings: the origin of the craft, the biology of the operators, the history of the program. That framework was handed to him. He did not construct it from observation alone. The Bennewitz question is: by whom, and to what end?

Element 115 is the detail that most complicates simple explanations in either direction. Its existence was theoretically predictable in 1989. Including a real but unsynthesized predicted element in a briefing document would be sophisticated disinformation: technically impressive, eventually confirmable, but confirming one detail does not validate the interpretive framework built around it. That is also how good disinformation works.

What this framework cannot tell us

Whether Lazar's briefings were accurate, fabricated, or a mixture. Whether Element 115 was included because someone told him, or because it is genuinely the propulsion element. Whether the records disappeared because someone removed them or because they were never what he claimed. The framework raises these as questions. It does not answer them.

Case 02

David Grusch

Former NGA and NRO officer. Served on the UAP Task Force. Filed a whistleblower complaint with the Intelligence Community Inspector General in 2023, then testified publicly before Congress. His claims — crash retrieval programs, non-human biologics, decades of illegal concealment from congressional oversight — represent the most institutionally credentialed UAP disclosure in the public record.

This section asks a question separate from whether the institutional architecture Grusch describes is real — there is reason to think it partially is. It asks whether Grusch's emergence as a public whistleblower is itself legible through the Bennewitz framework. These are different questions and they can have different answers.

What the PURSUE corpus can offer

The PURSUE corpus provides more support for Grusch's claims than for any other figure examined on this site. The agencies he specifically named — ODNI, DoE, DIA — appear as document sources in the corpus. The interagency routing patterns in multiple files are consistent with the compartmentalization architecture he described. Grusch is also a decorated intelligence professional who went through proper oversight channels, at documented personal cost, to say what he believed to be true. His personal integrity is not in question here.

What the Bennewitz framework asks

The most important structural feature of Grusch's testimony receives very little attention: almost all of his most dramatic claims are testimony-of-testimony. He did not work in a crash retrieval program. He was told about crash retrieval programs by other officials during his work on the UAP Task Force. He is accurately reporting what he was told. That is not a criticism — it is a description of his stated methodology.

Bennewitz was also accurately reporting what he was told. He received briefings from AFOSI personnel and reported that information as evidence because he believed it was. The Bennewitz framework asks of Grusch: were the officials who briefed him themselves operating within a managed disclosure architecture? An institution that wanted to surface a specific narrative into the public record through a credentialed, legally protected channel could not design a better instrument than a decorated intelligence officer filing a whistleblower complaint.

This does not require the apparatus to be malicious toward Grusch, or the information he received to be false. It requires only that an institution which has managed UAP information for decades would manage its disclosure the same way it managed everything else: carefully, through channels it controls, in a form that serves a purpose.

What this framework cannot tell us

Whether the officials who briefed Grusch were themselves accurately informed, or were passing along a managed narrative they also believed. Whether his emergence was coordinated with institutional intent, or was a genuine oversight action the apparatus would have preferred to prevent. Whether the "managed disclosure" reading and the "genuine whistleblower" reading are mutually exclusive — they may not be.

Case 03

Chris Bledsoe

North Carolina businessman. Beginning in 2007, Bledsoe and members of his family began reporting ongoing contact experiences near the Cape Fear River. His accounts are high-strangeness in character and deeply personal. He has been assessed by multiple investigators as sincere. Over the years that followed, a significant number of cleared personnel from the CIA, DIA, and NASA have visited him, studied his property, and quietly attended to his ongoing experiences.

What the Bennewitz framework asks — narrowly

The Bennewitz framework is not applied to the content of what Bledsoe experiences — his accounts are categorically different in nature, and the informational mechanisms of the Bennewitz operation do not neatly account for embodied, contact-oriented experience. The framework applies to one thing only: the institutional response to him. That is where the documented record exists.

The documented fact is this: over a period of years, cleared personnel from multiple agencies have sustained their attention on a single individual. When an intelligence apparatus sustains its attention on a single civilian over years, what is it getting from that relationship? In Bennewitz's case, the answer was documented — it was redirecting his attention from classified programs. In Bledsoe's case, the answer is not documented. The possibilities are real but unresolved: the apparatus may be studying a genuine phenomenon. It may be managing a witness whose account serves some institutional purpose. It may be doing both simultaneously.

What the Bennewitz case established is only that sustained institutional attention on a civilian witness is not neutral. It has a purpose. That purpose is not always what it appears to be, and it is not always what the witness understands it to be.

What this framework cannot tell us — and what it should not claim to

The Bennewitz framework cannot speak to the content, reality, or meaning of Bledsoe's experiences. It cannot tell us whether the intelligence personnel attending to him are studying or steering. It identifies a pattern of institutional behavior. The inner life of the person at the center of that pattern is beyond its reach, and should be.

Where this leaves us

The framework is a question, not a verdict

Paul Bennewitz was not a fool or a liar. He was a careful, technically sophisticated person who had genuine access to real signals — and who was handed a narrative that explained those signals in a way that served an institutional purpose he was never told about. He believed what he was told because it was internally consistent and came from sources he had reason to trust. The operation worked precisely because he was honest. The three individuals examined here are, by every available account, also honest. The Bennewitz framework does not require any of them to be dishonest. It requires only that the apparatus which managed Bennewitz is the same apparatus that has had sustained contact with each of them — and that the purpose of that contact is not fully visible from the outside.

The Analysts

Three researchers — on the outside, without access to these documents — spent decades building frameworks for understanding UAP. The PURSUE corpus is the first large-scale primary source to test all three against raw government data.

224

declassified records tested against each framework

independent analytical frameworks — three theoretical, one empirical

frameworks had access to this corpus when they were built

Analyst 01

Jacques Vallée

Computer scientist, astrophysicist. Co-developer of the first computerized map of Mars. Author of Passport to Magonia and Forbidden Science. Consultant to J. Allen Hynek's original UAP study. Spent decades demanding access to unedited, multi-sensor government data — arguing it would confirm what civilian records implied.

"The phenomenon is physical — it leaves traces, affects sensors, produces physiological effects — but it does not behave according to the physics of any known vehicle. It appears to manipulate space-time and perception, and its behavior is more consistent with an intelligence that has operated here for a very long time than with visitors from another star."

Core Claim 1

Multi-sensor confirmation is the gold standard

Cases simultaneously tracked by radar, infrared, and visual observation with no sensor disagreement represent the strongest physical evidence. He built classification matrices for these cases specifically.

Core Claim 2

Instant acceleration violates known aerodynamics

Stationary to supersonic with no detectable acceleration phase, no sonic boom, no ionization trail, no inertial delay — Vallée catalogued dozens of such cases; none had a conventional explanation.

Core Claim 3

Nuclear sites show disproportionate clustering

Vallée's data compilations noted UAP reports cluster around electromagnetic infrastructure, especially nuclear facilities. He flagged Kirtland and Sandia repeatedly in his journals as statistically anomalous.

Core Claim 4

Government data is the missing variable

The primary obstacle to resolving the UAP question was the absence of unedited government sensor data. He specifically requested raw radar logs, flight recorder correlates, and multi-agency incident records.

DOW-UAP-D3 — MQ-9 Mission Report, Arabian Gulf (2020)

An MQ-9 Reaper acquires a weapons-quality FLIR lock on a small, fast-moving object. The sensor package — infrared, electro-optical, and ground radar — registers simultaneous multi-modal detection before the object undergoes "instantaneous acceleration" beyond sensor range. No sonic signature. No propulsion exhaust. This is exactly the multi-sensor, instant-acceleration case type Vallée's classification matrices were built for. His framework predicts no propulsion signature and sensor agreement without physical explanation — both present here.

Source: PURSUE Tranche 1 · DoD declassified 2025

Strong match

DOE-UAP-D1 — Sandia Laboratories Correspondence File (1948–1952)

A TOP SECRET correspondence file from Sandia Laboratories contains Edward Teller's name six times in the context of UAP sightings over nuclear weapons facilities in New Mexico. The clustering Vallée inferred from civilian incident data is confirmed here in primary government documents he never had access to.

Source: PURSUE Tranche 2 · DoE declassified 2026

Direct confirmation

Analytical Verdict

The corpus is what Vallée was asking for — and it says what he predicted

Vallée spent five decades demanding access to unedited multi-sensor government data, arguing it would reveal a statistically consistent pattern that conventional explanations could not accommodate. The PURSUE corpus is, essentially, that dataset. The multi-sensor confirmation cases fit his anomaly-classification matrices precisely. The Sandia nuclear clustering, which he inferred from civilian data, is confirmed in primary documents. Vallée's framework is not falsified by the PURSUE corpus. If anything, it is the analytical lens that fits the data most closely.

Analyst 02

David Grusch (as analyst)

Former NGA and NRO officer; UAP Task Force representative. Testified before Congress in 2023 under oath. His claims are explicitly bureaucratic and institutional — not theoretical. He is the only figure in this investigation who appears in both Act III (as a case through the Bennewitz lens) and Act IV (as an analyst whose institutional claims can be tested against the corpus). That dual position is itself informative.

"This is not about belief in little green men. This is about specific programs, specific agencies, specific classification hierarchies, and specific paper trails. The government knows. The question is whether the paper trail survives and whether it can be found."

ODNI-UAP-D1 — Senior IC Officer Encounter Narrative (2022)

The PURSUE Tranche 2 release includes a first-person written account from a senior US intelligence community official describing a multi-sensor UAP encounter involving FLIR, radar lock, and scrambled fighter jets. Its routing metadata places it within the ODNI collection — an agency Grusch specifically named as a holder of significant UAP material. This is the first primary-source ODNI UAP document in the public domain.

Source: PURSUE Tranche 2 · ODNI declassified 2026

Strong match

Analytical Verdict

The institutional architecture Grusch described is partially visible in the paper trail

Grusch's claims are the most verifiable of the analysts examined here because they are explicitly about bureaucratic structure. The appearance of ODNI and DoE as document sources — agencies he specifically named — is consistent with his testimony. The interagency routing anomalies suggest exactly the kind of cross-compartment management he described. What the corpus does not yet provide is a direct link between routing codes in the historical documents and the specific legacy programs Grusch named. The PURSUE corpus is an incomplete but directionally consistent fragment of the paper trail he said existed.

Analyst 03

Hal Puthoff

Theoretical physicist. Director, Institute for Advanced Studies at Austin. Core scientist for the Pentagon's AAWSAP and AATIP programs. Published extensively on zero-point energy and metric engineering as applied to exotic propulsion.

"The flight characteristics described in credible UAP encounters — instant acceleration, transmedium operation, apparent violation of inertial effects — are consistent with engineering approaches that manipulate the local space-time metric. The physics exists on paper. The question is whether someone has built it."

DOW-UAP-PR050 — Iran Water-Surface Encounter (August 2022)

Naval sensor logs describe an object that transitions between air and a water surface environment without the hydrodynamic impact signature any known vehicle would produce. No conventional vehicle architecture can achieve this without structural destruction. This is Puthoff's "transmedium constraint" case — the hardest data point for conventional explanations — present in primary government sensor logs.

Source: PURSUE Tranche 2 · DoD declassified 2026

Direct confirmation

Analytical Verdict

The engineering signatures Puthoff predicted are in the sensor data

Puthoff's framework makes specific, falsifiable predictions: no propulsion signature, environmental electromagnetic effects, transmedium operation, geometric recurrence. The PURSUE corpus contains primary-source documentation of all four. What the corpus cannot do is distinguish between Puthoff's metric engineering hypothesis and simpler alternatives. Puthoff's framework is not falsified. But it is also not proven. The data is consistent with his predictions — that is not the same as confirmation.

What this investigation concludes

The same apparatus that ran Bennewitz produced these documents

The PURSUE corpus is not an alien artifact. It is the output of a specific institutional apparatus — the same agencies, the same classification architecture, the same interagency coordination structure — that managed UAP information for decades, including through operations like the one run against Paul Bennewitz. Reading the corpus means reading that apparatus. The Bennewitz case is the clearest documented example of what that apparatus was willing to do when it decided information needed to be controlled. The documents in PURSUE are what it looked like when the apparatus decided — or was directed — to let the information go instead. The machine is well-evidenced. The cargo is still undetermined. That gap is the honest answer.

Explore the Evidence Database → Read the Full Investigation → The Anomaly Record →