25 Cold Orbs, One Gunship, No Answers: Inside the Gulf of Oman UAP File

Twenty-five. That is the number that turns a strange infrared contact over open water into something a combat crew could not ignore. Not one light, not two, but roughly 25 instances described as “cold orbs” crowding the air around a U.S. Special Operations gunship during live-fire training over the Gulf of Oman. ³⁵ For a crew trained to track, target, and kill from the air, the scale alone made the encounter different: a swarm, in formation, close enough to watch, close enough to shoot at, and still unexplained years later. ²⁵

What is now on the public record centers on September 8, 2021, when an AC-130J gunship crew reported the encounter during a live-fire training sortie. ³⁵⁷ The account is preserved in DOW-UAP-D101, an Air Force Special Operations Command Intelligence Information Report labeled an “Unresolved UAP Report.” ²³⁴ The label matters because it is not journalism, memory, or rumor. It is the military’s own paperwork conceding that its sensors and crew saw something it could not resolve. ⁴⁶

The sequence, as summarized across the reporting file, begins with something routine. The crew dropped a flare into the water as a target. ²⁹ A sensor operator watching through infrared then saw two roughly four-foot orbs hovering motionless above the flare. ⁹⁵ They were not the hot white glare a viewer might expect from an engine, exhaust, or burning flare. They displayed cold signatures rather than hot, dark against the infrared picture where heat should have been. ⁹² That inversion — cold where hot belonged — is the detail that gave the file its name and its mystery. ³

What happened next is the reason the file continues to circulate. The crew fired on them and the objects appeared to react to cannon fire, reportedly moving between trigger pull and recoil. ⁹¹⁰ In plain terms, the sources describe a reaction so fast it seemed to fall inside the weapon cycle itself, not a slow drift away after the rounds landed. ⁹¹⁰ The crew then observed the larger swarm of about 25 cold orbs in coordinated formation. ²⁵ The file summaries describe formation flight rather than scattered, independent movement, a coordinated presence around the aircraft over open water. ²⁵

An AC-130J is built to record. Its sensors exist so crews can find targets, document strikes, and review what happened. In this encounter, the aircraft’s digital video recorder “inexplicably failed” during the event. ³⁵ That two-word fragment, reproduced in multiple summaries of the report, carries outsized weight because it explains why one of the most instrumented aircraft in the U.S. inventory left behind so little primary imagery of more than two dozen objects. ³⁵

Crew members used cell phones to record the infrared sensor display, a workaround that preserved something but not everything. ⁶⁸ The surviving imagery is described as a 26-second secondary cell-phone recording, released as DOW-UAP-PR122. ⁶⁸ It is not the original sensor tape. It is a phone pointed at a screen, with all the loss of resolution and context that implies. The wider Pentagon release is anchored by six videos documenting the encounter. ⁸ Six clips sounds substantial until it is set against the claim at the center: a crewed gunship, on a live-fire sortie, surrounded by a coordinated swarm it had just engaged. ²⁵

The disclosure arrived on August 7, 2026, as PURSUE Release 05, containing 41 files made up of 22 documents, 16 videos, and 3 images from the Department of War, Pentagon, FBI, CIA, State Department, and Executive Office of the President. ⁷⁴⁸ One tracking summary attributes the release to U.S. Department of War / AARO, while another describes it as the Pentagon’s fifth declassified UAP batch spanning more than seven decades. ⁷⁸ Before that, the file had been classified under a 50X1-HUM exemption from April 2022 until release, meaning the September 2021 encounter stayed out of public view for nearly four years after it was formally restricted. ³

Equally important is what the available sources do not provide. No crew member is named in any source. ²⁵ The sources do not reproduce verbatim official text from DOW-UAP-D101 itself beyond short quoted fragments like “cold orbs” and “inexplicably failed.” ³⁵ The report is classified as “Unresolved,” no explanation of the objects is given, and no independent verification of the objects’ identity, speeds, or thermal data is provided in the sources. ⁴⁶²⁵ The file documents an observation and a failure to explain it, not a conclusion. ⁴⁶

That boundary needs to be stated plainly because other details have traveled with this story that the reporting file cannot support. The sources record crew speed estimates generally, but a specific 250 to 300 mph figure appears nowhere in the provided material. ⁵ Likewise, commentary attributed to an astrophysicist about a drone-swarm interpretation, a Mach-scale speed figure, and a thermal contradiction argument is not corroborated by any of the ten provided sources, and that analyst’s affiliation is never even mentioned in them. ⁵ Exact quoted phrases about trigger pull and recoil timing and pod-like maneuvering also cannot be confirmed verbatim, even though the sources independently corroborate the underlying firing reaction and formation observations. ⁹¹⁰⁵ In short, the core is documented, the color around it is not. ²⁵

The practical question does not require believing any theory about what the orbs were. A crewed aircraft conducting live fire met objects that hovered over its target flare, appeared to react to cannon fire, and then appeared in larger numbers in formation over open water. ⁹¹⁰²⁵ The crew lost its primary recording, salvaged a phone video of a screen, and filed a report that remains unresolved. ³⁵⁴⁶ Until identity, speed, and thermal behavior are independently verified, the Gulf of Oman file will sit where the Pentagon left it: detailed enough to alarm, incomplete enough to prevent answers. ²⁵