CIA-UAP-002, Scientific Advisory Panel on Unidentified Flying Objects, Report, 1952-1953
This file contains correspondence and reports dated 1952–1953 from the Scientific Advisory Panel on Unidentified Flying Objects, convened by the CIA’s Office of Scientific Intelligence. The panel’s primary conclusion was that “flying saucers” did not pose a direct physical threat to the national security of the United States. The panel found no evidence that these phenomena were attributable to hostile foreign artifacts or indicated a need to revise existing scientific concepts. However, the panel identified a significant indirect threat stemming from the public’s fascination with the subject. The panel concluded that the high volume of reports, encouraged by a "sensationalist press," could overwhelm and clog vital intelligence and communication channels, potentially distracting from genuine threats. Furthermore, they warned that a “morbid national psychology” could be exploited by adversaries to incite “hysterical behavior and harmful distrust of duly constituted authority.” To mitigate these risks, the panel recommended an official policy of “debunking” to “strip the UFO subject of its mystery,” alongside a training initiative for military personnel to better recognize and filter out misidentified objects, thereby reducing communication “noise” and allowing the national security apparatus to focus on more "legitimate defense concerns."
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 CIA's 21 files in the Trump PURSUE disclosure. Within the CIA agency block it ranks #1 of 21 by Anomalousness Index. Across the entire 334-file archive it ranks #181 of 334.
That places it in the lower-scoring band of the archive (181 of 334 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.
For the broader cluster context, this file is part of The Robertson Panel - the 1952-53 CIA Scientific Advisory Panel (the Robertson Panel) that recommended an official policy of debunking UFOs. The cluster page walks through all 1 member files with regional grouping, sensor breakdown, and standout analysis.
Anomalousness Index: 58/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 CIA, 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.
The witness here is CIA personnel, entering the report into the federal investigative system through standard channels. That's a real credibility tier - trained federal investigative staff - though the rubric ranks it below mission-active military or astronaut testimony because the posture is reactive (responding to a report) rather than an active operational context.
On corroboration, this file from the CIA - 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 was released as open by the CIA after a formal review process concluded - not simply logged and left pending. That's a stronger disposition signal than 'unresolved, no review': a review actually happened, and remaining open is the CIA's own published conclusion from it, not an absence of one.
Bottom line on the score: the Anomalousness Index of 58/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 CIA
Other PURSUE files in the same category, ranked by Anomalousness Index.
ODNI-UAP-D001, USPER Narrative, Senior USIC Official
CIA-UAP-003, The Central Intelligence Agency and Overhead Reconnaissance; The U-2 and OXCA…
CIA-UAP-004, CASE 17708 (CLOSED) and DR. Leon Davidson
CIA-UAP-005, German Scientist's Article on 'Flying Discs'
CIA-UAP-006, Sighting Of Unconventional Aircraft
CIA-UAP-007, Current Status Of Unidentified Flying Objects (UFO) Project.
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 →