Short Note / May 31, 2026
The Yemen orb clip is turning into a 3D problem
The Yemen orb clip is no longer only a missile-hit mystery. The useful fight is now in 3D: line of sight, FOV, Reaper motion, Bullseye references, and missile angle.
The Yemen orb clip is no longer just a “missile hits UFO” clip.
It has become a geometry problem.
The newer Metabunk thread is useful because it moves the argument off one frozen frame.
The fight is now in the machinery behind the video: line of sight, slant range, horizontal range, camera heading, field of view, Reaper motion, Bullseye references, and the angle of the missile as it enters the frame.
Less clickable than “Hellfire bounces off orb.” Much more useful.
The new angle
The Metabunk thread started as a focused 3D spin-off from the broader Yemen orb discussion. The basic question is narrow: can the on-screen numbers and geometry recreate what the public video shows?
Several users pulled data from the display. The important pieces are not glamorous. A north indicator. Azimuth. Slant range. Horizontal range. Possible altitude. Camera direction. Bullseye references that may locate the drone and target relative to a fixed point on the map.
Once those numbers are plotted, the clip gets harder to treat as a simple magic-object story.
A static-object setup appears to fit parts of the tracked sequence surprisingly well.
Later work adds caveats. The source video is filmed off a screen. The field of view may be cropped. Some HUD values are hard to read. And the missile path after impact may be affected by tracking behavior rather than by the missile making a wild turn.
Not a clean ending.
A better problem.
Why it clicks
The viral version of the Yemen case depends on a very strong read: a Hellfire hits an object, the object survives, the missile bends away, and the whole scene behaves like something exotic.
The 3D work pulls that apart without making the case boring.
If the object is near-static, the Reaper is moving, the camera is tracking, and the missile is coming in close to the line of sight, the screen can make geometry feel physical.
A slow-looking missile can still be fast. A curved-looking path can be camera motion or tracking behavior. A strange post-impact motion can be a lock trying to recover.
None of that proves what the object was.
It changes the questions.
The piece we still do not have
Chris Lehto also enters the thread with a tactical point: Bullseye references may matter, and the drone filming the object may not be the drone lasing or firing.
If there are multiple platforms involved, the geometry of the shot changes.
Other posts push on missile size, heat signature, glare, motion blur, FOV, and whether the source video speed could have been altered before it reached the public.
That is the shape of the case now: no clean ending, no victory lap.
A short, degraded, filmed-off-screen military video has turned into a reconstruction problem. The next evidence would be plain: original file, full sensor metadata, platform track, range data, laser data, missile type, and post-engagement tracking.
Without that, every model stays provisional.
With it, the Yemen orb story could change quickly.
Related UAP Logbook notes
- The Hellfire UAP clip is missing the boring data
- UAP video analysis
- How to read a UAP video release
- war.gov UFO files: PURSUE portal, UAP videos, and old cases