The Helicopter’s Orange Orbs: What the PURSUE Papers Say Before Anyone Takes Them to Congress
Burlison wants the intelligence witnesses to the 2025 orbs to testify, and the New York Post illustrated it with drawings from a different case. We have read the FBI log and the witness's account, hour by hour: the approach to within three meters came over the radio, and the “mothership” is in no paper.
In late 2025, on a test range in the western U.S. whose name is redacted, a senior intelligence official aboard a helicopter, its two pilots and ground personnel described orange orbs, a swarm of lights and a “super-hot” object on infrared. In May 2026 the Department of War released an FBI log, the witness's account for the ODNI and 32 photos. On October 10, Congressman Burlison said he is considering bringing the witnesses before Congress.
Executive summary of the case file. Everything essential before you dig deeper.
Fact sheet
OSINT - Traceability
What made me close the newspaper over the weekend wasn’t the headline. It was a photo caption. On October 10, the New York Post reported that Congressman Eric Burlison (Republican, Missouri) is considering bringing before Congress the intelligence witnesses to a 2025 encounter with orange orbs around a helicopter. Below it, a drawing: two silhouettes next to a car and five red lights in an arc over some mountains.
The caption says it is “a digital rendering of the orb incident at a west coast military base that had several witnesses from the intelligence community,” credited to the Department of War. The drawing is from the Department of War, yes. But it is not of that incident.
It is FBI-UAP-D023, a rendering the FBI prepared for the third batch of the PURSUE program, released on June 12. It illustrates another case: two days in October 2023 next to a “sensitive national security site” in the West, as told by a federal special agent. The article’s second illustration, the road with the orange ball, is FBI-UAP-D014, from the same 2023 case. The file name on the Post’s server begins with “2023-image-based-upon-first.” It doesn’t even hide it.
I searched all 450 entries in the PURSUE database and the helicopter case has no rendering. It has something better: two written documents and 32 photos, public since May. Before anyone sits those witnesses in front of a microphone, let’s read what they already put in writing. That is my territory: papers, hours and who signs.
What is verifiable, first: two papers and one witness
The first document was posted by the Department of War on May 8, in the first PURSUE batch, and its entry describes it as “an FBI 302 interview” with a senior intelligence official. What is published does not look like an FD-302 form: no FBI header, no transcription date, no file number. It is a typed, hour-by-hour chronology with everything identifiable replaced by bracketed placeholders: [WITNESS 1], [CALL SIGN 1], [SITE CODE NAME].
The alt text the portal itself gives its thumbnail calls it “Heavily redacted event log.” I side with them against themselves: it is a record of events with a closing paragraph of comments from the witness. The SECRET//NOFORN stamp at the top and bottom of each page is struck through with a line, which is how a declassified paper is marked.
The second arrived on May 22 with the second batch and is something else: a first-person account, two pages, written by “a currently serving (May 2026) senior U.S. intelligence official” and filed under the Office of the Director of National Intelligence (ODNI).
The portal pairs the two documents with each other and with the 32 photos. That the [WITNESS 1] of the first and the author of the second are the same person is my reading, but everything fits: both are observing with the naked eye while the pilots wear night vision goggles.
An archivist’s detail that made my afternoon. On May 26 the Department posted a correction to the second document: where it said “map-of-the-earth” it should have said “nap-of-the-earth,” flight hugging the terrain. They corrected one letter. And they left, two paragraphs further down, fighter jets “at about 23,00 feet AGL,” a figure that does not exist: it is either 2,300 feet or 23,000, and that is not the same thing.
The night, hour by hour
The first document has a virtue the second lacks: times. I have cleaned them up. It does not say which time zone they are in or what day it is, so these are times without a date, but the order matters, and order is what has been most damaged in summaries.
The chronology of the log
Daylight takeoff
Two intelligence officials and two pilots from a state agency go out to search a mountain range for the source of dull thuds heard by personnel who had seen orbs. Earlier that same day, the log notes, a redacted office had completed “a successful test.”
Source ↗The mouth of a cave
They orbit the entrance of a large cavern and continue. The debris they find along the way is from rockets and projectiles from years of testing.
The second official gets off
The helicopter lands and drops [WITNESS 2] with personnel from a federal partner. From here on, only [WITNESS 1] and the two pilots are aboard.
Night search with no result
A ground observation post with FLIR and night vision points out debris on the mountain. They search with the spotlight and find nothing.
The “super-hot” object
The ground post sees on infrared a “super-hot” orb at ground level that heads east and south and splits in two. The helicopter goes to intercept.
Five military aircraft in the air
The operations center warns of five military aircraft on a training mission in the area.
“Within ten feet”
The ground post reports that the orb gained altitude, passed about three meters from the helicopter and went off about 20 miles. From the helicopter they did not locate it; the copilot saw on night vision something coming out of the two objects.
A swarm of lights
Pilots and witness see lights “too many to count” moving in all directions. They lose them at 22:27.
Two orbs beside the rotor
Two oval orbs, orange with a white or yellow center, above the rotor disc; below, four or five more light up and go out in reverse order. The log notes “possible out of order.”
Formations over the aircraft
Several times, groups of four to six orbs light up one by one in a horizontal line over the aircraft, over the mountain range or toward a redacted town, and go out in reverse order after ten or fifteen seconds. At 22:49, three in a triangle.
Return for fuel
The helicopter returns to the operations center and crosses paths with an aircraft from a federal partner heading north.
Look at the line with no time, because it is the headline of all this. The “ten feet” of the orb that approached the helicopter, that near miss Fox News put in a headline in May, was seen by no one in the helicopter. The ground post reported it by radio. The log says, literally, that the crew searched “with FLIR, NVG, and the naked eye” and “did not locate the orb.” What the copilot does say is that he saw something come out of the two objects and leave fast in another direction.
Something else that gets lost: the second intelligence official got off at 20:50, an hour before the strange part began. The log does not say what he saw from the ground, if he saw anything. The other observers are personnel of “federal partners” with the agency redacted, an operations center with detections that the account calls radar, and pilots from a state agency.
One intelligence official aboard. One. The rest is radios, goggles and redactions.
Two versions from the same witness
Putting the log next to the account, which is another text written for another recipient, is the most useful thing you can do with this case file. Almost everything matches. Even the sides: the log puts the two large orbs “to the west” with the helicopter heading south, and the account puts them “to our right.” Heading south, west is on the right. It checks out.
But there are two differences, and they point the same way. The account adds that the orbs appearing over the aircraft were “matching the jets’ speed and flight path.” In the log they light up in a line over the aircraft and go out, and the witness remarks at the end that they seemed to separate from the helicopter to “pursue” the aircraft; the matched speed is not there. And the account omits the one sentence in the log that points to something terrestrial: the “successful” test that same day.
I am not accusing anyone of embellishing. It always happens when someone tells the same thing twice: the first-person account is a better story and a worse record. That is why the document that matters is the one with the hours. And that is why it bothers me that the Post attributes to “an FBI report” objects that are “countless”: that word comes from the account for the ODNI. The FBI log says “too many to count.”
“We were virtually speechless after these observations.”
ODNI-UAP-D001, page 2
What is being told: the Post, Burlison and Loeb
Now, the Post article, signed by Shane Galvin. I set it next to the two documents sentence by sentence, because it is the version running this weekend across social media and aggregators:
- “Intelligence officials who witnessed,” in the plural. The documents attribute observations to only one intelligence official. The other got off earlier.
- The “mothership.” It appears in neither paper. The closest thing is “something emerge from the two objects” in the log and “a smaller object emerged” in the account.
- “West coast military base.” The portal says “Western United States” and the rest is redacted. Mountains, a test range with years of rockets on the ground, five military aircraft. Nothing more.
- The oval orb that approaches and splits. It mixes two moments. The oval orange orbs with a white or yellow center are the ones that light up beside the rotor. The one that approaches and splits is the “super-hot” object the ground post sees on infrared.
- The drawings. They are from another case, from 2023.
What Burlison and Loeb say
What is Burlison’s, in quotation marks in the Post: “There’s some people that are working for the agency that having them come forward publicly may expose other things.” He says he will look into it, that one of the witnesses is a career ODNI official unknown to the public, and that some have already met behind closed doors with members of Congress without showing them all the video. That there is video fits the log: the pilots said they were recording.
And then there is Avi Loeb, the Harvard astrophysicist of Project Galileo, who chairs the UAP Science Advisory Council. According to the council’s website, the ODNI commissioned it and it will review only unclassified information. That explains what he told the Post: that he has not seen a single frame of the video and has not spoken with any witness. He wants to go to the site and take measurements. Fine. First they have to tell him where it is.
What I do not share is his statement that any information on technologies of non-human origin is “fully protected” by the presidential directive and by the confidentiality waiver from the ODNI and the Pentagon. I read that waiver when it came out, and I covered it here: it lifts the civil and administrative restrictions, and only for speaking with PURSUE. That is not a safe-conduct to testify at a public hearing. It is my reading of the law; Loeb’s is different.
There is one last version circulating since July. According to Liberation Times, Jordan Flowers, whom it presented as executive director of the Disclosure Foundation, said on CBS that the ODNI was running an operation to lure UAP and that it was “wildly successful.” The documents say nothing about luring anything. The only thing that resembles it is that successful test of the same day, with the object redacted. And a redaction proves nothing. Neither for nor against.
The photos: below in the frame is not below in the sky
Of the 32 photos, the most eloquent is B007. Monochrome, with a reticle, a helicopter at upper right and a dark dot below. Its entry speaks of “a U.S. military system”; the one for the FBI document specifies that the photos of UAP under the helicopter were taken from the ground with night vision devices.
The printed date is 12/31/99 at 18:10:02, and the entry itself warns that the system did not have the date set. With a clock like that, the time is no use to me either.
Two things can be said without inventing anything. The first, geometry: a photo flattens. That the dot appears below the helicopter in the frame does not say whether it is ten meters from it or ten kilometers behind. The second, about the sensor, and I flag it as a reading: the helicopter, which is the hottest thing in the sky, appears black. If this is a thermal image in “black hot” polarity, the dot is also hotter than the background. The entry does not clarify the polarity.
And a third, about the archive. The eight photos of series A say in their entry that neither date, nor place, nor mission report was provided. Their relation to the helicopter night is asserted by the Department in the entry for another document. I believe it, but let the record show who says so.
The test sentence
Document · PURSUE R01
No need for little green men
I start with what asks the least. Lights that switch on one by one in a horizontal line, over a mountain range, near five training aircraft, on a range where weapons are tested, and that go out in order after ten or fifteen seconds. That looks a lot like a description of flares, illumination or countermeasure. We covered it with the ones at the Bardenas Reales.
The U.S. Air Force attributed to flares dropped by A-10 aircraft over an Arizona bombing range the Phoenix lights of March 1997; there are witnesses who still dispute it. And in 1944 bomber crews swore that balls of light followed their aircraft: these are the foo fighters, and this site’s case file concludes that most are explained by things of the war itself.
What lights up near an aircraft and goes out a few seconds later, seen from afar, looks like it is traveling with it.
Second hypothesis, the log’s own: something of ours. A sensitive range, a successful test that same day whose object is redacted, and a swarm of lights too many to count moving in all directions. A swarm of test drones fits, and it fits that the observers were not informed. I cannot prove it, because the data point that would settle it is exactly the one they redacted.
Third, optics. With the naked eye and at night, a light with no references gives no distance: “close proximity” is an impression, not a measurement. And night vision goggles turn any bright point into a round halo. I know this sounds like textbook skepticism. It happens that the textbook exists because it is right many times. The Coyne crew in 1973 also saw a light coming down on them.
What is not so easily explained, and I say it just as plainly: an object that the ground post sees “super-hot” on infrared at ground level, that leaves at great speed, that according to them splits in two, and some detections that the account attributes to the operations center’s radar. Several sensors and several observers at once. If that is recorded, that is what needs to be seen. And not one second has been released.
What is missing, and what I would ask
If Burlison manages to seat them, this is my list. None of the questions asks for secrets, only papers:
- The pilots’ video. They said they were recording; Burlison says it has not been shown in full.
- The FLIR images from the ground post at the moment of the “super-hot” object, which is the only thing that dates and measures.
- The radar data from the operations center.
- What was successfully tested that day, even in closed session, and whether the five aircraft dropped flares.
- What the second official saw from the ground after 20:50.
- Which figure “23,00 feet” is, and why the PDF of the first document was modified on May 13, five days after publication, with no correction note on the portal.
For anyone who wants to follow me: the log of the hours is on the PURSUE portal, no account and no payment, just like the National Archives entries or the NRC drone reports we read these past weeks. Before the next hearing, three pages. You can read them over a coffee.
Put in Astro’s language: less microphone and more PDF.
And one request to whoever does the layout: if the case is from 2025, the drawing should not be from 2023.
OSINT – Source traceability
V3 for the event, not for the documents: the papers have verifiable official provenance, but what they recount rests on a naked-eye witness, on radio reports and on photos with no date or location, and the sensor data have not been released. Incident date left empty on purpose: the documents only say “late 2025.” The identity between the log's [WITNESS 1] and the author of the account, the thermal polarity of photo B007 and the flare and own-test hypotheses are flagged in the body as the author's own reading.