The hearing video exists
The House Oversight Committee publicly hosted the hearing in which Burlison played the clip.
OFF YEMEN · 30 OCTOBER 2024 · PUBLICLY SHOWN 9 SEPTEMBER 2025
The Yemen Orb and the Hellfire MissileMQ-9 FOOTAGE · CONGRESSIONAL DISCLOSURE · NO PUBLIC OFFICIAL IDENTIFICATION
At a House Oversight hearing, Rep. Eric Burlison played whistleblower-provided footage said to show an MQ-9 tracking a small object off Yemen while another MQ-9 fired a Hellfire missile. The public video clearly shows a tracked contrast, a fast incoming contrast and post-interaction debris or motion. The exact date, location, weapon type and second-drone narrative remain attributed metadata from the anonymous-source chain rather than a released DoD case file.
AUTHENTIC DISCLOSURE CONTEXT · Hero uses the official House Oversight hearing video thumbnail. The underlying sensor clip was presented to Congress by Rep. Eric Burlison and attributed to an anonymous whistleblower; it was not released with a public DoD chain-of-custody package.
MQ-9Platform described at the hearing.
HELLFIREWeapon described by Rep. Burlison.
ANONYMOUS SOURCEPublic provenance begins with a whistleblower handoff.
PENTAGONPublicly declined to comment to CBS.
30 OCT 2024Date presented with the footage.
OFF YEMENLocation given to Congress.
9 SEP 2025First major public disclosure.
IDENTITYNo official public determination.
THE FAST ANSWER
The video is real congressional evidence. The viral description is not the same thing as a verified weapons-effects report.
MQ-9 + Hellfire + orb
He described an MQ-9 tracking an orb off Yemen while another MQ-9 fired a Hellfire missile.
Apparent interaction
A fast-moving contrast reaches the tracked object and the scene changes sharply around the point of contact.
No public DoD case file
No publicly released weapon telemetry, full sensor file, engagement log or official identification accompanies the viral clip.
WATCH THE CONGRESSIONAL RECORD
The clip entered the public record at the 2025 UAP hearing.
The committee hearing is the strongest public provenance point currently available. It establishes that a member of Congress presented the video and described what he had been told about it. It does not, by itself, authenticate every element of the anonymous source narrative.
PIXELS VS SOURCE NARRATIVE
The case becomes clearer when the visible evidence and the anonymous-source metadata are separated.
What the pixels actually establish
A tracked contrast remains near the centre of the sensor view. A second fast-moving contrast reaches it. After the interaction, multiple bright/dark elements and continued apparent motion remain visible.
What is not independently verified in the public file
The date of 30 October 2024, location off Yemen, MQ-9 platform description, existence of a second MQ-9 and the claim that the incoming object was a Hellfire missile all enter the public story through the whistleblower chain.
That distinction does not make the source narrative false. It simply prevents attributed metadata from being presented as if a full DoD mission record had been publicly released.
WHAT BURLISON ACTUALLY CLAIMED
“A Hellfire missile smacking into that UFO.”
Rep. Burlison told the hearing the footage was taken on 30 October 2024, showed an MQ-9 tracking an orb off the coast of Yemen, and that another MQ-9 — not visible in the shot — launched a Hellfire missile.
He then characterised the interaction as the missile hitting the object and “bouncing” away while the object kept going and apparent debris moved with it. Online discussion has also surfaced uncertainty around the metadata chain itself, so the 30 October 2024 date should remain phrased as the date presented with the footage, not as independently verified EXIF-like metadata from an original file.
Those are important first-order claims because they were made in Congress. They are still claims attached to whistleblower-provided footage, not a published DoD weapons-effects conclusion.
THE MOMENT EVERYONE ARGUES ABOUT
Did the missile bounce off — or did the camera geometry make a damaged target look intact?
The target appears to survive a direct weapon strike
The object remains visible after the apparent collision. To experienced weapons personnel such as Luis Elizondo, the lack of a conventional destructive result looks deeply unusual for a Hellfire engagement.
Glancing hit, failed fuze or ballistic debris
A small target can be clipped rather than cleanly struck; a warhead may fail to detonate; and after impact a damaged object or debris can continue along a similar apparent screen path because both target and sensor platform are moving.
The phrase “bounced off” is visually intuitive but not a measured result. The crucial unresolved question is whether the post-impact material is the original object remaining intact, a damaged target continuing ballistically, or a cluster of debris sharing similar apparent screen motion. Without full-rate footage, missile telemetry and engagement geometry, the clip alone cannot decide between them.
THE TELEMETRY / 3D GEOMETRY PASS
This is where the strongest technical counter-analysis lives.
Independent analysts on Metabunk extracted values from the on-screen display — including sensor azimuth, elevation, aircraft heading, slant range and horizontal range — and began reconstructing the scene in three dimensions. The point is not that one forum model settles the case. The point is that the HUD contains enough geometric information to test claims about speed, altitude and apparent motion rather than relying on intuition alone.
Sensor look direction
Helps reconstruct where the camera was pointed relative to the aircraft heading.
Look angle
Combined with range, this constrains the target's approximate altitude below the MQ-9.
Geometry instead of guesswork
Provides a basis for estimating the distance to the tracked point and how that changes over time.
Why parallax matters
The Reaper's own movement can produce substantial apparent target motion on screen, especially when circling or changing look angle.
One reconstruction is consistent with a relatively small, slow or near-static target while the observing aircraft moves around it. That is a materially stronger conventional explanation than simply saying “parallax might be involved.”
WHY PARALLAX MATTERS
Continued screen motion is not the same thing as continued powered flight.
Analysts on Metabunk argued that the tracking MQ-9 and target were moving in broadly similar directions before the collision. After impact, a lightweight damaged target and nearby debris could lose power, begin falling and still appear to continue along the display because the observing platform itself is moving.
This is one of the most important counterarguments because the viral reading assumes that anything still moving across the screen after impact is still flying under control.
The public clip does not provide enough range, altitude, velocity or platform-position data to convert the apparent motion into a reliable three-dimensional trajectory.
HOW BIG WAS THE OBJECT?
Some reconstructions put it in the small-object range — but the result depends on assumptions.
Roughly 2–4 feet across in one recreation
A Metabunk contributor using the apparent Hellfire width as a reference produced approximate right-angle dimensions of about 2.13 feet vertically and 2.5 feet across the longest image axis, with perspective-adjusted estimates in roughly the 2.6–3.9 foot range.
The reference itself is uncertain
The estimate assumes the incoming object really is a Hellfire, assumes a usable apparent missile width, and is sensitive to sensor perspective, glare and crop. It is best treated as a reconstruction scale, not a confirmed physical dimension.
This is still useful because it demonstrates how far the public evidence is from supporting a “large craft” claim. The object could plausibly be physically small if the reconstruction assumptions are approximately right.
THE HOUTHI-DRONE HYPOTHESIS
A combat theatre already full of drones.
The incident was said to occur off Yemen during a period when U.S. forces were regularly operating against Houthi threats to shipping. Astrophysicist Avi Loeb and other commentators have suggested the target could have been a Houthi attack drone such as a Samad-type vehicle.
That contextual fit is strong: drones were real, numerous and militarily relevant in exactly that region.
But the public clip is too degraded to make a clean airframe identification. A small featureless blob in infrared does not automatically become a sphere in three-dimensional space — and neither does it become a specific Samad model without better imagery.
THE EVIDENCE LANES
Separate the video, the congressional claims and the later interpretations.
| Evidence lane | What it establishes | What it does not establish |
|---|---|---|
| Public sensor clip | A tracked object and an apparent high-speed interaction followed by continued visible material/motion. | Exact object type, range, speed, altitude, weapon fuze behaviour or powered flight after impact. |
| Congressional presentation | Burlison publicly attributed the clip to 30 Oct 2024, off Yemen, involving MQ-9s and a Hellfire. | Independent DoD verification of every metadata point or a formal technical finding. |
| Weapons-effects interpretation | The apparent survival looks unusual to some experienced observers. | That the target possessed extraordinary materials or technology. |
| Conventional analysis | Glancing strike, failed fuze, small drone and parallax/ballistic motion are plausible mechanisms. | A positive identification of the object from the public clip alone. |
WHAT WOULD ACTUALLY SETTLE THIS?
The missing evidence is more valuable than another round of screenshot enhancement.
Full-rate imagery
Needed to assess edits, frame cadence, image processing and the exact interaction sequence.
Position, heading, altitude
Would turn the 3D reconstruction from an informed model into a much tighter geometry solution.
Launch and fuze data
Would establish whether the incoming object was in fact a Hellfire and whether detonation was commanded or detected.
Operational conclusion
Would show what the operators believed they engaged and what the post-strike assessment concluded.
WHY THIS CASE MATTERS
It is not just another dot in the sky.
The Yemen case matters because it appears to move the UAP question from passive observation into an alleged real-world weapons engagement. That raises very different questions: why was the target selected, what rules of engagement applied, what did the operators believe it was, and what did the battle-damage assessment show?
The most interesting missing evidence may therefore be bureaucratic rather than visual. If a U.S. weapon was fired at an unidentified object in a combat theatre, there should ordinarily be a much larger operational paper trail than the few seconds now public.
The clip is compelling precisely because it is incomplete. The page should resist turning missing records into proof of exotic technology while making clear how important those missing records would be.
FIRST COMPETITOR POSITION
UAP Globe is already strong. The opening is provenance discipline.
UAP Globe has built a substantial version of this case around the dramatic weapons interaction, the congressional disclosure, the Houthi-drone hypothesis and the Metabunk parallax analysis. It is probably the direct page to beat.
Our advantage should be sharper evidential separation and deeper technical treatment: what is visible, what Burlison was told, what the Pentagon has or has not confirmed, and what telemetry-based reconstruction suggests. V2 now adds the HUD/3D geometry work, a cautious small-object size reconstruction, a stronger source-provenance split and a concrete list of the records that would actually settle the case.
SOURCE ROOM