USG-UAP-D001, Congressional, White House, UFO-related Constituent Correspondence, 1998
This collection of documents, primarily from 1998, contains draft and final correspondence from the White House and the offices of members of Congress responding to constituent inquiries about Unidentified Flying Objects, or “UFOs.” These inquiries cover a diverse range of topics, including alleged UFO sightings by NASA astronauts, questions regarding the authenticity of photos collected during U.S. missions to Mars, alleged improper withholding of information by the U.S. Government, questions regarding the appropriateness of “UFO-related” governmental spending, and calls for congressional hearings regarding the nature and existence of “UFOs.” The official responses consistently state that, circa 1998, the U.S. Government is not aware of evidence supporting the existence of extraterrestrial technology, and that NASA does not actively investigate “UFOs.” The collection includes references to materials of both confirmed and unconfirmed authenticity, as provided by constituents, as well as references to historical, scientific literature addressing specific “UFO” sighting claims.
The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.
Where this file fits in the PURSUE archive
This file is one of USG's 1 files in the Trump PURSUE disclosure. Within the USG agency block it ranks #1 of 1 by Anomalousness Index. Across the entire 334-file archive it ranks #334 of 334.
That places it in the lower-scoring band of the archive (334 of 334 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.
Anomalousness Index: 47/100
Evidentiary weight that this encounter remains unexplained after conventional analysis. Not a probability of extraterrestrial origin - that number is not honestly computable from the released files and this tracker refuses to publish it.
🤖 AI-ASSISTED SCORING · methodology
The six rubric components break down for this file as follows. Each component has a weighted contribution to the final score; the per-component explanation below describes what this file's particular value on that component means in the rubric's framework.
No sensor, camera, or instrument backs this observation - it is testimony, relayed through the federal government, and scored on the rubric's lowest sensor-quality tier for that reason. That doesn't bear on the witness's credibility (a separate axis); it reflects only that nothing beyond human perception recorded the event.
A civilian account, routed into the federal record via the federal government's investigative channels rather than an operational mission report. The rubric scores this tier below uniformed personnel specifically because of that remove - the witness wasn't reporting from within a federal mission context when the observation occurred.
On corroboration, this file from the federal government - like every single-tier file in the PURSUE archive - is a single-witness or single-instrument capture per the released metadata. The rubric doesn't infer multi-witness confirmation the summaries don't actually establish; this score reflects the honest limit of what was released, not a judgment about the underlying event.
The released file contains no speed, acceleration, or vector data precise enough to score on the kinematic axis - and that's true archive-wide, not specific to this file. The rubric declines to infer kinematic anomaly from a witness's narrative estimate of how fast something moved; that itself says something about what PURSUE actually released: descriptive accounts, not flight-path telemetry.
Every file in the archive, including this one, scores this tier: a conventional explanation was considered in the released record but isn't treated as dispositive. That's a pattern in how war.gov's own summaries are written - they consistently hedge against strong conclusions either way - and the rubric takes that hedging at face value rather than resolving it for them.
This file from the federal government is catalogued as unresolved, with no formal review process having concluded - logged into the system, but not yet finalized by any review. The rubric treats that differently from 'open after review,' because the absence of a completed review is itself part of the file's status, not a placeholder for one.
Bottom line on the score: the Anomalousness Index of 47/100 reflects evidentiary weight that this specific file's encounter remains structurally unexplained by the rubric's six axes - it is not a claim that the underlying event involved anything non-conventional, and it is not comparable across rubrics that use different weights. For the full per-axis weights and the rubric JSON, see /methodology.
Related files in USG
Other PURSUE files in the same category, ranked by Anomalousness Index.
DOW-UAP-PR024, Unresolved UAP Report, Middle East, 2023
DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…
DOW-UAP-PR106, Unresolved UAP Report, Eastern United States, 2020
DOW-UAP-PR108, Unresolved UAP Report, Western United States, 2020
DOW-UAP-PR109, Unresolved UAP Report, Eastern United States, 2015
DOW-UAP-PR110, Unresolved UAP Report, Eastern United States, 2020
Verification
SHA-256:
This hash is the SHA-256 of the file body war.gov served on the verification date above. War.gov has re-processed some file bodies since first release (re-compression + OCR, no content removed - see /changes); we re-verify and record the change rather than silently serve a stale hash. How to check this yourself →