USPER Statement about UAP Sighting
This is an FBI 302 interview conducted with a senior US intelligence official regarding his first-hand account of a UAP encounter at a US military facility. USPER relayed to FBI agents that he and other federal and state personnel conducted searches to where orbs had been previously seen. After searching the area with a helicopter, they found a “super-hot” orb hovering over the ground. The orb is reported to have travelled for 20 miles at a speed too fast for the helicopter in pursuit. An additional “swarm” of lights were seen moving in all directions. A total of four or five additional orbs were seen shortly thereafter for a short time, flaring up and then down. This pattern of four or five orbs flaring up, then down continued over the next thirty minutes across the area. The photos linked in the "Related Media" section are connected to a set of UAP encounters on a sensitive government testing installation in the Western US in 2025. These orb-like UAP were observed at various ranges by multiple, and in some cases simultaneous, government personnel and sensors. The linked narrative is an FBI-collected account from a senior U.S. intelligence community official who witnessed the UAP with the naked eye, while accompanied by two pilots under NVGs. Other pilots in separate aircraft, and ground-based observers with night vision, also witnessed UAP during the exercise. The photos of UAP underneath the helicopter are from this same set of observations, taken through night vision devices by ground-based personnel.
The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.
Text of the document
Machine-extracted from the PDF war.gov published (its text layer or OCR), so expect errors, especially in names, numbers and handwriting; the PDF is the authoritative copy. Lines that did not extract as readable text are left out. Showing about 1000 words from pages 1, 2, 3 of 3.
PAGE 1
On 2025, at approximately 1700 hoursllll [WITNESS 1 (a senior US accompanied by [WITNESS 2 (a senior US intelligence official ilots from [STATE PARTNER ORGANIZATION], departed th [OPERATIONS CENTER] ([COORDINATES]), main area via a [STATE PARTNE e Icop er (call sign [CALL SIGN 11) to conduct a daytime ariel search of the [MOUNTAIN RANGE NAME] west of [SITE CODE NAME] on [FACIU~yewitness reports from personnel who observed orbs/lights IV~[COORDINATES]) cited hearing thuds as if someth~ fallen and hit the ground. (Note: Earlier that day the ffice-completed a successful test of the at [SITE CODE NAME] ([COORDINATES]) on [FACILITY]. At 1751 hours [CALL SIGN 1] spotteed cav-elrna erntrance ([COORDINATES]) and conducted a short orbit of the location mountains and dropped off [WITNESS 2) with [FEDERAL PARTNER 3] personnel. At 2052 hours [CALL SIGN 1] headed toward [SITE CODE NAME] to refuel. A second helicopter ([STATE PARTNER ORGANIZATION] - [CALL SIGN 21) brieflY. landed at [SITE CODE NAME] to await refueling but then lifted off and returned to the At 2141 hours-[CALL SIGN 1) lifted off from [SITE CODE NAME] and headed toward debris spotted by the Listening Post/Observation Post (LP/OP - [FEDERAL PARTNER 4] personnel using Forward Looking Infrared (FUR) and Night Vision Goggles (NVG)- position ([COORDINATES]) located approximately four miles east of [SITE CODE NAME] in the mountains -location ([COORDINATES])). [CALL SIGN 1) orbited the location while searching with NVGs (pilots) and the naked eye ([WITNESS 11) with the aid of the helicopter's spotlight in near full darkness for several minutes with negative results. At approximately 2149 hours, [CALL SIGN 1) departed the search location to return to base and received notification from LP/OP that -had-hits bearing - 4 miles out from their location. The JOC then provided coord ([COORDINATES]). [CALL SIGN 1] moved to intercept. At 2202 hours-[CALL SIGN 1] arrived at the aforementioned coordinates and spotted a possible aircraft on the horizon moving away to the west. LP/OP confirmed the sighting then relayed they spotted an orb under FUR and described as "super-hot" hovering at ground level before heading bearing-from LP/OP. LP/OP reported the orb was heading east and then south at a high rate of speed and then broke into two objects. LP/OP directed [CALL SIGN 1] to head south to [COORDINATES] to intercept.
PAGE 2
At 2207 hoursilllll JOC reported five [MILITARY AIRCRAFT] from were in the air space conducting a training mission. Once on station, [CALL SIGN 1] searched the location with FUR, NVG, and the naked eye but did not locate the orb. LP/OP reported the orb ained elevation, came within ten feet of (CALL SIGN 1] and then headed east to (CALL SIGN 1] moved to intercept but LP/OP reported the orb continued southeast and estimated it to be past [ROAD NAME], some 20 miles from the current position at- [CALL SIGN 1], unable to match speed, broke off pursuit, however the co-pilot reported seeing under NVG something emerge from the two objects and then travel in a different direction and a high rate of speed. At 2218 hours . (CALL SIGN 1] remained at (COORDINATES] awaiting instructions when the pilots (NVG) and (WITNESS 1] (naked eye) spotting a swarm of Ii hts too many to count) moving in all directions but generally located west of and headed south. JOC relayed they contacted the [MILITARY AIRCRAFT] who were enroute to assist, eta two minutes. At 2227 hours. , (CALL SIGN 1] lost visual of the At approximately 2227 hours- (possible out of order), in proximity of [SITE CODE NAME] headed south, [WITNESS 1] (naked eye) and the pilots (NVG) spotted two large orbs appear in close proximity to (CALL SIGN 1] to the west and above the rotor disk. From the naked eye perspective, the two orbs appeared to flare up and remain stationary side by side. They appeared to be oval shaped, orange in color with a white or yellow center and emitting light in all directions. After a few seconds, a third orb flared up below the two, and then another one below that one until there were four or five in total below the original two. After a few seconds the orbs began to flare down in reverse order while appearing to be stationary until visual was lost. At approximately 2228 hours- (CALL SIGN 1] - [WITNESS 1] (naked eye) and the pilots (NVG) spotted four or five orbs (similar to the orbs that were in close proximity to the helicopter) appear to the west over the mountains above the (MILITARY AIRCRAFT]. The orbs flared up one at a time in a horizontal formation and after approximately ten - fifteen seconds, flared down in the opposite order. At approximately 2233 hours - (CALL SIGN 1] - (WITNESS 1] (naked eye) and the pilots (NVG) spotted a similar orb formation to the east in the direction of [NEARBY TOWN NAME]. The orbs flared up one at a time in a horizontal formation and after approximately ten - fifteen seconds, flared down in the opposite order and lost visual. At approximately 2241 hours- (CALL SIGN 1] - (WITNESS 1] (naked eye) and the pilots (NVG) spotted a similar orb flare up west of [SITE CODE NAME] over the mountain. After several seconds the orb flared down and lost visual.
PAGE 3
At 2249 hours- while positioned IVO [SITE CODE NAME], [CALL SIGN 1] - [WITNESS 1] (na~ilots (NVG) spotted a swarm of lights moving in all directions west of- with three distinct orbs in a triangle formation. After several seconds the orbs flared down and lost visual. At 2252 hours - while positioned approximately ten miles north of [SITE CODE NAME], [CALL SIGN 1] - [WITNESS 1] (naked eye) and the pilots (NVG) spotted five to six orbs flare up IVO [LOCAL TOWN] (east of [SITE CODE NAME]). The orbs flared up one at a time in a horizontal formation and after approximately ten seconds, flared down in the opposite order and lost visual. At 2257 hours- while positioned approximately ten miles north of [SITE CODE
Where this file fits in the PURSUE archive
This file is one of FBI's 105 files in the Trump PURSUE disclosure. Within the FBI agency block it ranks #105 of 105 by Anomalousness Index. Across the entire 478-file archive it ranks #351 of 478.
That places it in the lower-scoring band of the archive (351 of 478 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.
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.
Reported by a witness with no instrumented record. The lowest tier in the rubric's sensor axis. Eyewitness perception in field conditions, even when the witness is highly credentialed, scores below capture by any instrumented modality. This report reached the federal record through the FBI.
Federal agency personnel (FBI investigators or equivalent) recording the report into the federal investigative system. Investigative credentials, but typically operating in a reactive rather than mission-active posture.
Single-witness or single-instrument capture. This is the corroboration tier for the overwhelming majority of the PURSUE archive 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. A small number of files with an independent second witness or instrument score on the multi-witness/multi-instrument tier above this one.
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.
Catalogued as unresolved with no formal review process having concluded. This is the disposition for a large share of the archive's military infrared captures - the reports are logged into the system as unresolved, but no formal review has finalized. The rubric distinguishes this from 'open after review' because the absence of review is itself a status signal.
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 →
Source: https://www.war.gov/medialink/ufo/release_1/usper-statement-redacted.pdf