FBI-UAP-D001, FD-302, Unresolved UAP Report, Colorado Springs, 2022
This document is a Federal Bureau of Investigation (FBI) FD-302, a form the FBI uses to record interviews. This FD-302 contains a summary of an interview with a U.S. military service member in March 2025 regarding a February 2022 incident potentially involving unidentified anomalous phenomena (UAP). The individual described the phenomenon as being “bean shaped,” “matte white” or “off-white” in color, with a surface covered in “intersecting lines or ridges which formed an abstract polygon pattern.” The individual described the phenomenon as “motionless” and that “no sound could be heard coming from it.” FBI Note: AARO has since been in contact with the interviewee to conduct subsequent interviews to inform its analysis of this incident.
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 FBI's 87 files in the Trump PURSUE disclosure. Within the FBI agency block it ranks #78 of 87 by Anomalousness Index. Across the entire 334-file archive it ranks #268 of 334.
That places it in the lower-scoring band of the archive (268 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 FBI Modern UAP Files - the FBI's modern UAP files: the 2022 Colorado Springs interview and the FBI-authenticated northeastern orb videos. The cluster page walks through all 30 member files with regional grouping, sensor breakdown, and standout analysis.
Anomalousness Index: 55/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 FBI, 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 FBI 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 FBI - 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 FBI 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 55/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 FBI
Other PURSUE files in the same category, ranked by Anomalousness Index.
FBI-UAP-PR001, “Triangle Orbs,” Northeastern United States, 2021
FBI-UAP-PR002, “Red Orb Rotation,” Northeastern United States, 2022
FBI-UAP-PR003, “Orbs Over the Pond,” 2024
FBI-UAP-PR004, “Northeastern Orb Sighting,” 2025
FBI-UAP-PR005, Digital Recreation, Narrative Statement 3-1, Western United States Event, 2…
FBI-UAP-PR006, Digital Recreation, Narrative Statement 3-2, Western United States Event, 2…
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 →