FBI-UAP-D005, FD-1057-04, Northeastern United States, 2024
This document is an FBI FD-1057, a form the Federal Bureau of Investigation (FBI) uses to record investigative activity. This FD-1057 documents an October 2024 interview with a US person regarding several incidents potentially involving unidentified anomalous phenomena in the northeastern United States over the previous three years. The subject matter described in files FBI-UAP-D004 through FBI-UAP-D008 and depicted in the video footage FBI-UAP-PR001 through FBI-UAP-PR003 corresponds to reports originating from the same general area in the northeastern United States.
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 532 words from pages 1, 2, 3 of 3.
PAGE 1
FEDERAL BUREAU OF INVESTIGATION Approved By: Drafted By: Case ID#: - Unidentified Aerial Phenomenon - Unidentified Anomalous Phenomenon (UAP) • - is currently empl oyed by and works primarily in the ■ facility. - spoke to a presentation and videos that were previously provided to the FBI. - has spoken with fellow and former employees, about the sightings observed from - property in was exercising in - house around 5am when ■ noticed some lights
PAGE 2
outside of back window. Initially, - believed someone was in - yard with a f ashlight bobbing around. When - went outside, . observed a singular light that eventuall y split into two or three lights. This formed a triangular pattern with a light in the center and remained for approximatel y ten minutes. - got •••• to see what ■ was seeing as well. - while filming on . smartphone, accidently took a flash photo and the lights immediately disappeared. was previously provided to the FBI and explained that the location of this sighting was not in the same location. - stated that the UAP sightings that - observes are typically at dusk or at night and the light observed appears to morph and move laterally. ■ first reached out to - , formerly of • - through Linkedin to speak about what • had observed from - ■ home. In conversations with - - was told that what ■ was observing was legitimate and that "people have been hurt by these things" and to be careful. - asked - if - had a UFO experience before in - life. At this point, - explained an incident that officer from Fort Bliss, TX to Fort Carson, CO . While in New Mexico, - clai med that the vehicl e ■ was driving shut down and a large light shined on - and - passenger. After about two minutes the light went away and the vehicle ' s electronics turned back on. - • - has lived at current property, in - ■ s ince 2021 but - previ ously l i ved about five miles from current home from - stated that - has seen hundreds of these l ights from - property and has numerous videos and photos that - was wil ling to share. - also stated that - has seen these lights as well and others who have visited his property as well . • - stated that ■ has seen more activity since September. The sightings have not always been as long as - initial sighting in 2021 . There have been shorter bursts and it is common to have corrupted video when trying to record these sightings.
PAGE 3
- - explained how ■ used ADSB data to try a disprove what - was seeing as aircraft flying overhead. - e xpl ained that ■ cross referenced date and time stamps with ADSB records to determine what sightings may be aircraft. - would then determine the azimuth of the lights and check the ADSB data. ■ acknowl edged throughout the interview that ■ never had an interest in UAPs and that a lot of what - said may seem weird or crazy.
Where this file fits in the PURSUE archive
This file is one of FBI's 104 files in the Trump PURSUE disclosure. Within the FBI agency block it ranks #90 of 104 by Anomalousness Index. Across the entire 450-file archive it ranks #321 of 450.
That places it in the lower-scoring band of the archive (321 of 450 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 47 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.
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 →