The Gulf of Oman Gunship Encounter

The Gulf of Oman gunship encounter is a September 2021 incident in which the crew of a US Special Operations AC-130J tracked around 25 unidentified objects during live-fire training. The objects appeared on infrared as cold orbs roughly four feet across, flew between 250 and 1,300 mph with no visible propulsion, and appeared to respond when the aircraft fired its main cannon. The intelligence report was declassified on 7 August 2026 in the Pentagon's fifth UAP release, and the case is officially unresolved.

Of everything in that fifth release, this is the case with the best paperwork. The videos are poor, and the Department of War is unusually honest about why. But behind them sits a formal Intelligence Information Report written by Air Force Special Operations Command, distributed to most of the American intelligence community, and describing a sequence of events that its own authors could not account for.

What Is an AC-130J Gunship, and What Was It Doing There?

The AC-130J Ghostrider is a converted transport aircraft loaded with sensors and guns. It carries a 105mm howitzer and a 30mm cannon in its left side, along with an electro-optical and infrared sensor turret that lets the crew find and track targets in complete darkness. It exists to circle a point on the ground for hours and hit things precisely. The people who fly it are among the most experienced sensor operators in any air force.

On 8 September 2021 one of these aircraft was over the Gulf of Oman running a night live-fire exercise. The standard method is simple: drop a flare on the water, let it burn, orbit it, and use it as a target. The crew member watching the sensor screen is the Combat Systems Officer, and his job that night was to keep the flare in frame and put rounds on it.

Two Cold Orbs Over the Flare

The report describes what happened in plain operational language. The aircraft dropped a water-activated flare as a mock target and entered an orbit around it. The Combat Systems Officer ran collateral scans with the infrared sensor around the flare's position. When he slewed the sensor back to the flare in infrared mode, two objects were there.

Two details matter here. The first is the word cold. A burning flare is the hottest thing for miles. Anything with an engine, a motor or an exhaust would show hot on that sensor. These objects showed cold, sitting directly above an open flame, and the crew viewed them in both white-is-hot and black-is-hot modes to check.

The second is that they were stationary. Not drifting with the wind, not falling, not passing through. They held position over a burning flare on open water for about 15 seconds while a gunship circled them.

What Happened When the Cannon Fired

After roughly 15 seconds the Combat Systems Officer fired. The report's description of the next moment is the single most striking line in the entire fifth release.

A 105mm howitzer does not fire instantly. There is a short delay between the trigger being pulled and the round leaving the barrel, and the crew feels it as the gap before the recoil. The report places the objects' departure inside that gap. They did not climb or dive. They went sideways, fast, and left the sensor's field of view.

The report offers no explanation for the timing, and neither will we. It could be coincidence: objects that had been sitting there for 15 seconds happened to move at that moment. It could be a reaction to something the aircraft did that a person on board would not notice. The document records the sequence and stops there, which is the correct way to write an intelligence report and the reason this one is worth taking seriously.

Dolphins in a Pod: The Other 23 Sightings

The two orbs over the flare were the beginning. Across the rest of the sortie the crew logged around 25 instances of these objects, and the behaviour they describe becomes stranger as the report goes on.

The dolphin comparison is doing real work in that document. The crew were not describing debris, or birds startled by a flare, or drifting lanterns. They were describing objects that appeared to be flying together on purpose, and an intelligence officer thought that impression was worth writing down and attributing to the source rather than burying it.

The Video Recorder That Inexplicably Failed

Here is the part almost no coverage of this release has mentioned. The crew did try to save the good footage. The aircraft records its sensor feed to an onboard Digital Video Recorder, and that is what any investigator would want.

That word inexplicably is the report's own. It is why the only footage the public will ever see of this encounter is a handful of phone clips filmed off a screen in a dark aircraft cabin. Every clip on DVIDS carries a note explaining that this is a secondary capture, that it does not represent native primary sensor data, and that any blurring or flickering comes from filming a display rather than from the objects.

We would encourage reading that caveat carefully in both directions. It means the video is weak evidence and should not be presented as anything else. It also means the strongest evidence in this case was destroyed by an equipment failure, and the surviving clips are a poor proxy for what the crew actually watched.

Who Received the Report

The report was raised by Air Force Special Operations Command at Hurlburt Field, Florida, and transmitted in late April 2022, around seven months after the encounter. The distribution list runs to dozens of addressees, and it is worth knowing who was on it.

This is not a report that sat in a drawer at one command. It went across the American national security apparatus in 2022 and, as far as the public record shows, produced no explanation in the four years before it was declassified.

What Could Explain the Gulf of Oman Orbs?

Several ordinary explanations deserve a hearing, and the honest answer is that none of them fits every detail in the file.

Timeline

Why This Case Stands Out

Most declassified UAP footage is a smudge on a screen with a story attached. This case is the other way round. The footage is the weakest part of it, and the document is the strong part: a formal intelligence report, written by professionals seven months after the event, describing measured speeds, an absent propulsion signature, coordinated group behaviour and a departure timed to a trigger pull.

It also sits inside a pattern this site has followed all year. The Pentagon's own annual reporting has hundreds of cases it cannot close, and a striking share involve military aircraft and sensitive airspace. We covered that count in the Pentagon's 2026 UAP report, the wider release programme in our breakdown of the fifth file release, and the same "unresolved" label applied to earlier footage in what the DoD's UAP videos actually show.

Nothing in the Gulf of Oman file establishes that these objects were not made on Earth, and the report does not claim it. What it establishes is that a heavily instrumented American gunship spent a night surrounded by objects it could not identify, that the best recording of it was lost to a hardware failure, and that four years of review by the offices whose job this is produced the word unresolved.

Read the File Yourself

The full seven-page intelligence report is public. It is catalogued as DOW-UAP-D101 in Release 05 of the PURSUE archive at war.gov/ufo, and the six video clips are on DVIDS as DOW-UAP-PR117 through PR122, all public domain. Our own searchable index of the primary sources is in the UAP document archive.

Related Cases