UFO files: Senior intelligence officer departs JOC for UAP investigation
The second May 2026 Department of War UFO/UAP declassification release contains a firsthand account of a senior U.S. intelligence officer who left base to chase reports of unidentified aerial phenomena. The episode offers a rare, time-stamped look at how military intelligence responded to anomalous activity on a restricted test range. Details remain limited, yet the narrative is specific enough to raise questions about what the team encountered and what records still sit behind classification barriers.
Departure from the joint center
The account opens on a late-2025 evening still lit by daylight. A senior U.S. intelligence officer, one colleague, and two pilots lifted off from the Joint Operations Center in a single helicopter. Their stated purpose was to locate the source of repeated loud thuds reported in nearby mountains and to check UAP sightings logged over several prior nights.
Timing mattered. The flight launched after multiple ground observers had already logged visual and sensor contacts. The crew carried night-vision goggles, forward-looking infrared, and standard optics, indicating they expected both daylight and low-light conditions.
Logistics stayed minimal. No larger formation accompanied them, and the mission profile suggests the team wanted speed and a small footprint rather than a show of force. The departure itself became the first concrete data point in the newly released file.
Range conditions and prior sightings
The test range sits inside controlled airspace used for classified development programs. Access is restricted, which makes civilian overflights unlikely and raises the stakes for any unexplained object that appears on sensors.
Ground reports described sharp acoustic events followed by visual contacts. Observers noted objects low to the terrain that moved faster than conventional drones or aircraft in the same altitude band. Those descriptions prompted the helicopter launch.
Command chose to investigate rather than stand down, a decision now preserved in the declassified narrative. The choice signals that leadership treated the contacts as credible enough to commit aviation assets and senior personnel.
Sensor contact during flight
Once airborne, the crew acquired a thermal signature on FLIR. The object registered as super-hot, hugging the ground before accelerating east and then south. Its speed and thermal profile stood out against the surrounding terrain and known traffic.
Seconds later the signature split. Two distinct returns appeared where one had been, each changing direction independently. The split occurred within the sensor’s field of view, ruling out simple radar artifact in the released description.
The crew maintained visual and electronic track while closing distance. NVG and naked-eye confirmation followed, establishing a multi-sensor chain of custody for the event that later appeared in the document.
Ground team radio traffic
A separate ground element positioned on the range called the helicopter directly. Their message stated that an object had risen from the surface, closed to roughly ten feet of the aircraft, then dropped below the rotor wash before accelerating away. The proximity claim is now part of the official record.
Pilots aboard the helicopter corroborated the report through NVGs. They described the same rapid vertical movement and subsequent lateral acceleration. The dual confirmation from air and ground assets forms the core of the newly released account.
Radio discipline stayed intact. No panic language appears in the transcript excerpt, suggesting the crew treated the encounter as an operational event rather than an emergency requiring immediate abort.
Object behavior after split
After the initial separation, one element continued on a southern heading while the second veered sharply. The smaller return then appeared to emerge from the larger signature before both accelerated beyond visual range.
Thermal intensity dropped once the objects gained altitude and speed. The cooling profile matched the earlier climb and directional change, consistent with a propulsion system that modulates output during maneuvers.
The sequence lasted under two minutes from first FLIR lock to loss of contact. That brevity limited additional data collection but preserved a clear timeline now available in the declassified file.
Command response and documentation
Upon return, the senior U.S. intelligence officer filed a narrative that included sensor logs, radio transcripts, and personal observations. The document remained classified until the May 2026 release.
Review channels included standard intelligence reporting chains rather than public affairs pathways. This routing kept the incident inside operational channels until broader declassification policy shifted.
No public statement accompanied the original event. The absence of contemporaneous leaks suggests tight information control at the time, a posture that the new release now partially relaxes.
Technical implications for sensors
The FLIR track demonstrated that existing thermal systems can register and classify objects with unusual heat signatures at low altitude. The split signature, however, exposed limits in current tracking algorithms when returns divide rapidly.
NVG performance proved adequate for confirmation once the object closed distance. Yet the crew still relied on ground radio calls for the final proximity data, underscoring the value of multi-domain observation.
Range instrumentation captured acoustic data from the reported thuds. Correlation between sound events and aerial tracks remains an open analytical thread within the released material.
Classification and future access
The document sits within the second May 2026 Department of War UFO/UAP declassification release. Additional files from the same tranche may contain supporting sensor data or after-action assessments still under review.
Researchers now have a baseline account against which future releases can be measured. Discrepancies or corroborations will shape how analysts weigh single-observer narratives versus multi-sensor packages.
Continued releases could clarify whether similar incidents occurred on other ranges or whether this episode remained isolated. The current file provides the first public timestamp and participant list for such an investigation.
Next steps for investigators
The released narrative stops at loss of contact and return to base. Follow-on collection priorities, if any, are not addressed in the excerpt.
Analysts will likely compare the thermal and acoustic signatures against known propulsion test profiles. Any matches or gaps will determine whether the objects align with domestic programs or remain genuinely unexplained.
Public attention will focus on whether additional helicopter or ground-team statements surface in later tranches. Until then, the late-2025 flight stands as the clearest operational snapshot yet from the declassification effort.
Record now public
The account supplies a concrete sequence: departure, sensor lock, split track, close approach, and departure. It places a senior U.S. intelligence officer at the center of an on-site UAP response and preserves that record for further study. Future releases will decide whether this episode represents an outlier or part of a larger pattern still emerging from the May 2026 document drop.
