FBI-UAP-D010, FD-302-71, “Northeastern Orb Sighting,” 2026
This document is an FBI FD-302, a form the Federal Bureau of Investigation uses to record interviews. This FD-302 records an interview with a U.S. person regarding their first-hand account of an incident potentially involving unidentified anomalous phenomena. The subject matter described in files FBI-UAP-D009 and FBI-UAP-D010 and depicted in the video footage FBI-UAP-PR004 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 401 words from pages 1, 2 of 2.
PAGE 1
FEDERAL BUREAll OF' INVESTIGATION Date ofentry was interviewed along with After being advised of the ide, natti ty• o•f •the• i n-terviewing agents and the nature of the interview, provided the following - On ___, ■■■■ arrived home in the evening around 9:15pm. Once parking in the driveway, ■■■■ noticed a ball of ligh: -:hrough - winds~ield which was yellow and about the size of a basketball. Upon exiting the vehicle, ■••■ saw a second ball of ligjt which was larger and about the size of a beach ball. rhe ocjects were be~ind a row of trees, which have since been taken down but in front of a section of trees between - prope=ty and - neighbor's property behind the home. ■••■ was able to look at the lights without stre.1in or discomfort on - eyes. stated that - h~s not h~d ~ny health issues or concerns since seeing these [Agent Note; Based on where was standing, the objects were approximately 30 yards away and 20-30 feet above the ground]. ■: Upon seeir.g the lights, - came outside to views the objects as well. Both ■••■ and - observed tte objects move laterally to their left, passing behind a tree approximately 36 yards away, at the same height, continuing behind a neighbor's house and beyond a tree that was approximately 75 away. It was at this point where ■--■ stated that - ■ stated that a few weeks after this event, ■ saw several ~hite orbs travel over house from the west to the east. These whi-:e orbs were traveling much higher in ~ltit~dc than the prior red orbs. ■ In 1987, - stated that ■ had witnessed something strange off of in ■■■■■■• near power lines. - saw a red light circling around itself at night described lt like the front end or Kit frurn Cniced Scaces (In Person) This document contains neither ii-commendations nor i:onclusions ofthe fBI. It is thc properly ofth.: FBI and 1s looncd 10 your agency: it and its rnntcnts arc not to be distributed outside your agency.
PAGE 2
~ erview of t he TV show nightrider. - saw t he ob ject hover and then land neai:- the power station. Since then - stated t hat • has always been i nterested in the topi c of OAP. ■ Attached to this i nterview were phot os taken by Agents at the per mission of -
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 #95 of 104 by Anomalousness Index. Across the entire 450-file archive it ranks #326 of 450.
That places it in the lower-scoring band of the archive (326 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.
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 one of the rubric's higher credibility tiers - trained federal investigative staff, weighted level with a trained aviator and below only an astronaut witness - though 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 →