PR117
Reserved for the official AARO/DVIDS secondary capture. The exact individual item URL is being resolved; no thumbnail or sequence claim has been invented.
8 September 2021. A USSOF AC-130 mission. EO/IR observations. Roughly twenty-five reported UAP instances. Six released secondary captures. And a reported DVR save failure that left the native video data corrupted.
The page separates the official intelligence narrative, the six public secondary captures, the reported corruption of the native EO/IR video data and the performance estimates attributed to the crew.
On 8 September 2021, a U.S. Special Operations Forces AC-130J was conducting a live-fire exercise over the Gulf of Oman in darkness. A water-activated flare was being used as a mock target. The crew were operating an aircraft designed to find, track and engage targets through sophisticated sensors.
Then the EO/IR scan reportedly found something else.
The intelligence report that followed describes two approximately four-foot 'cold orbs' near the water. The pair were reportedly between zero and twenty feet above the surface. According to the report, they departed after the crew pulled the trigger for the aircraft's 105 mm cannon.
That was not the end of it. The report describes roughly twenty-five UAP observations during the wider episode, including formations, erratic manoeuvring and estimated speeds ranging from 250 to 1,300 mph.
Those are extraordinary claims. What makes the case important is that they were written into a contemporaneous military intelligence report rather than appearing only years later in a witness interview.

The central problem is that the public record preserves two very different things.
First, it preserves the crew's reported observations and the intelligence narrative produced from them. That narrative contains the most dramatic details: the cold thermal appearance, the near-water behaviour, the reported formations and the TACTOOL speed estimates.
Second, it preserves six secondary video captures released publicly. These are not the same thing as the aircraft's native EO/IR recording.
AARO has made clear that the released material is secondary capture material rather than the original primary sensor file. That matters because a native sensor recording could contain metadata and image information that are critical for reconstructing range, field of view, angular movement and apparent speed.
The distinction does not make the report unimportant. It tells us exactly where the strongest claims live.
Reserved for the official AARO/DVIDS secondary capture. The exact individual item URL is being resolved; no thumbnail or sequence claim has been invented.
Reserved for the official AARO/DVIDS secondary capture. The exact individual item URL is being resolved; no thumbnail or sequence claim has been invented.
Reserved for the official AARO/DVIDS secondary capture. The exact individual item URL is being resolved; no thumbnail or sequence claim has been invented.
Reserved for the official AARO/DVIDS secondary capture. The exact individual item URL is being resolved; no thumbnail or sequence claim has been invented.
Reserved for the official AARO/DVIDS secondary capture. The exact individual item URL is being resolved; no thumbnail or sequence claim has been invented.
Reserved for the official AARO/DVIDS secondary capture. The exact individual item URL is being resolved; no thumbnail or sequence claim has been invented.
These six positions are deliberately conservative. The authoritative case record identifies PR117 through PR122 as the released secondary captures, but this prototype does not invent individual thumbnails, durations or chronology while their exact official item pages are still being resolved.
According to the intelligence report, the aircraft's DVR save attempt failed and the native EO/IR data became corrupted. That removed the record most capable of testing the strongest kinematic claims independently.
The most consequential sentence in the case may be the one describing what happened to the recording.
According to the intelligence report, an attempt was made to save the EO/IR footage from the aircraft's digital video recorder. The save failed, and the native data became corrupted.
That loss changes what can be demonstrated today.
If the native recording survived, independent analysts might be able to examine the original image sequence, sensor metadata, zoom changes, timing information and perhaps the assumptions underlying the speed estimates. Without it, the public is left with secondary captures and the report produced by the people who had access to the event closer to the time.
This is not a reason to discard the case. It is the reason the evidential hierarchy has to stay visible.
The report gives estimated speeds ranging from 250 to 1,300 mph using TACTOOL.
Those numbers are among the most dramatic claims in the entire Gulf of Oman record. They are also among the claims most dependent on assumptions that the released material does not allow the public to reconstruct fully.
Speed derived from imagery depends heavily on range. A small error in assumed distance can produce a large error in calculated velocity. Without the native telemetry and full geometry, the published figures should therefore be described as reported estimates, not as independently verified performance.
That does not make them meaningless. The crew were operating in an environment where range, targeting and motion matter professionally. But professional estimation and recoverable raw telemetry are still different categories of evidence.
Several conventional possibilities remain serious.
Birds have been proposed for some infrared UAP videos, although the report's description of these objects as thermally cold and the reported performance would need to be reconciled with that explanation. Drones, balloons, classified systems, sensor artefacts, geometry errors and incorrect range assumptions also remain candidates.
The released secondary clips alone are not rich enough to eliminate all of those possibilities. Nor does the existence of a possible mundane explanation for one clip automatically explain approximately twenty-five reported observations.
The whole-case question is therefore not 'can something in an infrared video look strange?' It plainly can. The harder question is whether one conventional explanation can account for the reported thermal appearance, repeated observations, formations, near-water behaviour, speed estimates and operational response together.
At present, the public record does not allow that question to be settled cleanly.
Potentially relevant to some infrared imagery, but must be reconciled with the reported thermal description, behaviour and speed estimates.
Possible candidates for some observations. The question is whether they fit the reported formations, near-water behaviour and performance.
Cannot be excluded publicly, but invoking an unknown system is not itself an explanation of the released record.
Especially important because speed calculations depend strongly on distance. The missing native telemetry limits independent testing.
We would like to hear from people who can improve the public understanding of the sensor record, geometry, released clips or conventional alternatives.
Useful contributions can include imagery analysis, AC-130J/EO-IR expertise, range and motion analysis, identification of ordinary objects, source corrections, or public documents we have missed.
Gulf of Oman is powerful because the extraordinary parts of the story were not invented by later popular retelling. They appear in a contemporaneous official intelligence narrative generated inside the military reporting chain.
But the case also contains a major evidential fracture.
The report preserves the dramatic performance claims. Six public secondary captures preserve pieces of the visual record. The native EO/IR video data that might have allowed those claims to be tested most rigorously was reportedly corrupted after the failed save attempt.
That leaves an unusual modern UAP case: stronger than a story told from memory, weaker than a complete raw sensor package, and important precisely because the gap between those two things is so clear.
Six secondary captures survive. The native video data was reportedly corrupted.
This case concerns the 8 September 2021 Gulf of Oman event described in DOW-UAP-D101: a USSOF AC-130 gunship conducting live-fire training during darkness. The report says the crew observed approximately twenty-five instances of UAP while using the aircraft's EO/IR sensor. It is an official information report, not a final determination of object identity or performance.
The public record is narrower. PR117 through PR122 are contemporaneous secondary cellular captures of an infrared sensor display aboard a USSOF AC-130J. They are not native primary sensor data. The releases therefore preserve pieces of what was visible on a display, but not the full sensor file, its original fidelity or the metadata needed to independently reconstruct range and speed.
Read the official DOW-UAP-D101 report and a representative AARO/DVIDS secondary capture. The six public releases are PR117–PR122; their descriptions do not constitute an analytical finding about the event's nature or significance.