FBI-UAP-D028, FD-302, “Dark Triangle with Lights,” 2011
This document is an FBI FD-302, a form the Federal Bureau of Investigation (FBI) uses to record interviews. This FD-302 records an April 2025 interview with two former U.S. military service members, in which the interviewees describe an incident potentially involving unidentified anomalous phenomena (UAP) in June or July of 2011. An FBI digital rendering based upon the observers’ descriptions accompanies this document, under the title FBI-UAP-D029.
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 535 words from pages 1, 2 of 3.
PAGE 1
FEDERAL BUREAU OF INVESTIGATION On April ■, and were interviewed - Special Agent (SSA) , Special - - - After being advised of the identity of the interviewing agents and the nature of the interview, - and - provided the following information: On an evening in June or Jul y 2011, it was dark outside when was leaving his driveway l ocated at about 8 or 9 PM. - was with who was driving the vehicle, and , , who was in the front passenger seat. The vehicl e was about fifty feet from the driveway and preparing to make a l eft turn onto When they reached the intersection, - was looking out window and saw three l ights in the sky. - got out of the vehicl e, and when he l ooked up, he saw a massive bl ack isosceles This document contains neither recommendations nor conclusions ofthe FBI. It is the property ofthe FBI and is loaned to your agency; it and its contents are not to be distributed outside your agency.
PAGE 2
triangle shaped object flying North. The object had a car- sized white l ight in each of its three corners that emitted a diffuse gl ow and were recessed back a bit from the corners . The object was l ow to the ground, and creating a l ow humming noise that made a pul sing sound. told him to take a video, but by the time - got his phone out, the object had flown over the tree line behind the houses to the north, and out of s i ght. He had seen the object for approximatel y 10- 15 seconds . There were no contrail s left behind the object. - fel t dumbfounded and awestruck during the When observed the object, he was overwhelmed by the size of it and how low it was to the ground. thought the object may have been 800 feet above the ground, and based on the dimensions of their environment, he estimated the object was 200 feet long and 100 feet wide. believed the object had more of an equilateral triangle shape, but based on the cal cul ated dimensions, it could have been more of an isosceles triangle. The object was moving slowly and steadily, and he also heard the pulsing sound. saw the three lights in t he corners, but also remembered seeing something in the middle of the triangle that was grayi sh or graphite Neither nor - had a clear memory of the thickness or any other description of the vertical profile of the triangle. They opined that they were ini tially underneath the triangle and didn't really have a view of its side or vertical profile. They were then temporarily distracted by their unsuccessful attempt to get a phone out to video record the UAP, at the moment when they likely would have had a better view of the back profile. believed a couple of people in the neighborhood also saw would also would try to see if as well as their neighbors who witnessed the UAP, would be willing to write a statement about their observation, or speak to the FBI about it.
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 #98 of 104 by Anomalousness Index. Across the entire 450-file archive it ranks #329 of 450.
That places it in the lower-scoring band of the archive (329 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 →