NASA-UAP-D025, “Apollo 16 Scientific Debriefing”
At 32:41, the speaker makes an off-handed comment, “Could be an alien starbase or something, I don’t know” when discussing correlations between experimental data sets.
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 NASA's 33 files in the Trump PURSUE disclosure. Within the NASA agency block it ranks #4 of 33 by Anomalousness Index. Across the entire 294-file archive it ranks #4 of 294.
That score is the highest in the PURSUE archive - the only file at this tier.
Anomalousness Index: 72/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.
Captured by a single U.S. military sensor platform (typically infrared, occasionally short-wave infrared or dual EO+IR), aboard a mission aircraft or operational platform. Instrumented, time-stamped, and recoverable. Lower than a multi-sensor capture only because cross-modality confirmation is the rubric's higher bar.
Astronaut witness on the official federal record. The highest tier in the rubric and essentially unique in the PURSUE archive - only the Borman/Lovell Gemini 7 file fits this tier, which is the structural reason it is the sole 72 in the archive.
Single-witness or single-instrument capture. Every file in the PURSUE archive scores at this corroboration tier on the released metadata - the rubric records the honest limit of the underlying record rather than inferring multi-witness corroboration that the released summaries do not establish.
No kinematic measurements - speed, acceleration, vector - are published in the released file with sufficient precision to score on the kinematic axis. The rubric does not infer kinematic anomaly from narrative observer estimates. Every file in the archive carries this value, which is itself an observation about the disclosure: kinematic-grade telemetry was not part of what was released.
A conventional candidate explanation has been considered but is not dispositive. Every file in the archive scores this way - reflecting that the underlying release metadata systematically caveats strong determinations in either direction. The released summaries warn against reading them as conclusive analytical judgments, and the rubric respects that.
Released as open after formal review by the originating agency. The file passed through a review process and was published in that posture - a stronger disposition signal than 'unresolved with no review,' because review has occurred and the open status is the agency's published conclusion.
Bottom line on the score: the Anomalousness Index of 72/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 NASA
Other PURSUE files in the same category, ranked by Anomalousness Index.
NASA-UAP-D024, “Apollo 16 Scientific Debriefing”
NASA-UAP-VM001, Apollo 12, 1969
NASA-UAP-VM002, Apollo 12, 1969
NASA-UAP-VM003, Apollo 12, 1969
NASA-UAP-VM004, Apollo 12, 1969
NASA-UAP-VM005, Apollo 12, 1969
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 →
Source (DVIDS): https://www.dvidshub.net/video/1010336/nasa-uap-d025-apollo-16-scientific-debriefing
Direct video file: https://d34w7g4gy10iej.cloudfront.net/video/2606/DOD_111764902/DOD_111764902-1920x1080-9000k.mp4