It Came Within Ten Feet of Their Helicopter

A senior U.S. intelligence officer took a helicopter up to investigate loud thuds heard in the mountains of a weapons test range. What followed, in his own words, was "a series of close UAP encounters lasting over an hour."

An object rose off the ground, closed to within **ten feet** of the aircraft, dropped below them and accelerated away. They gave chase and broke off almost immediately — "unable to match its speed."

Later, hovering at 700 feet, he and both pilots watched two large orange orbs flare up beside the rotor disk. Then a third below them. Then a fourth. Four or five in a "T" formation, which dimmed in reverse order and vanished. When fighter jets arrived overhead, the same orbs appeared directly above them, flaring one at a time, matching their speed and course.

"We were virtually speechless."

He took no photographs, and he says why: "I was focused on assessing what it was and whether it posed a threat."

That account is ODNI-UAP-D001, and almost nobody has read it. It sits inside PURSUE — the 375 records the Department of War has published across five releases since 8 May 2026. We watched every video in all five: 134 files.

Most of it is distant infrared — a grey rectangle, a bright shape miles out, a crosshair. The best clip in the archive is DOW-UAP-PR054, a spherical object filed as showing "erratic movement," and it was not inside any of the download bundles. Nothing in five releases comes close to "GIMBAL" and "GO FAST", the two U.S. Navy recordings from 2015, declassified in 2020, which are not part of these releases at all.

A second document matters as much. DOW-UAP-D077, an anomaly-office memorandum dated 5 June 2026, covers October 2023 in the western United States: six federal law enforcement special agents, in three teams of two, reporting a "luminous orange mother orb" that releases clusters of smaller red orbs, repeatedly, over several hours. The office works through every ordinary explanation and attributes roughly 60% to military flares — while noting its own best explanation is "unsubstantiated by technical data or physical evidence." The remaining 40% lack a plausible explanation and remain unresolved.

Start with what anyone can check. Every case reference here is public and retrievable at war.gov/ufo. The 40% figure is the government's own arithmetic, published without flinching. And in May the Department reissued one of these documents solely to correct a typo in an aviation term — an office running a cover-up does not republish a UFO file to fix one word. That detail is inconvenient for the exciting reading, which is exactly why it belongs here.

Then the honest part. Almost nobody is talking about these releases, and having gone through all of it, the reason is not that something is hidden. It is that what has been released is genuinely poor to look at. Five tranches have not produced anything that competes with a Navy clip from 2015. Anyone telling you this archive is a bombshell has not watched it.

But the accounts are not poor. Six agents on duty over two nights. An officer and two pilots at the end of a long day, speechless in a cockpit. None of these people went looking for this — they were at work, and they filed reports because that is what you do. A camera has never once been pointed at the right piece of sky at the right moment. That is a problem with cameras, not with the men, and we are not willing to treat first-hand testimony as worthless because the pictures are bad.

Where we stop. We are not telling you what these objects are. Neither is the government, and it says so in writing. Believers differ on what, if anything, such phenomena mean, and Scripture does not settle the question of lights over a mountain — so we will not pretend it does. Testing a thing honestly sometimes means reporting that the evidence runs out, and then saying so plainly.

We will keep reading these files as they come. If the next release is thin, we will say it is thin.