The sensor shifted the image. Then the patch slipped off-screen and never returned.
A patch that looked different from the rest of the image crossed the screen as a military sensor moved, exited on the left, and never reappeared.
Declassified 43-second 1080p H.264 video (DVIDS ID 1006063) released by the U.S. Department of War as DOW-UAP-PR26, the public-release counterpart to mission report DoW-UAP-D23 (a USCENTCOM UAP report from the United Arab Emirates, October 2023). Despite the DVIDS description characterizing PR26 as 'a still image' with an operator-added red circle (the description appears to have been mis-pasted from the PR for DoW-UAP-D12), the released artifact is full-motion airborne FLIR/IR sensor footage at 30 fps showing a uniform low-contrast sky and a small bright/dim point of contrast drifting in the lower-left quadrant outside the central reticle. The frame is heavily masked with opaque black rectangles covering every position where HUD telemetry (classification banner, time, lat/lon, altitude/FL, heading, sensor mode, polarity, slant range, target box) would normally appear; only the cyan center crosshair, four corner field-of-view brackets, and a 'N' compass indicator near bottom-center remain visible. The matching mission report describes two UAP at FL243 — the first at 0241Z (320 MPH, cold thermal signature) and the second at 0322Z (440 MPH).
Airborne IR sensor recording in which a small point-source contrast is visible in the lower-left of the field of view, drifting leftward across the frame while the centered cyan crosshair remains fixed on empty sky. The bright point appears at roughly the 8-9 o'clock position from the reticle in early frames (~7s, ~22s), continues to translate left/down through ~29s, then is no longer resolvable in the final keyframe (~36s) as the surrounding sky brightens. Polarity and sensor mode are not visible (HUD is masked).
United Arab Emirates
Airborne forward-looking infrared (FLIR/IR) targeting/surveillance sensor
sensor
Top-of-frame classification / status banner area (one wide rectangle and three smaller rectangles spanning the upper edge across roughly 40–85% horizontal extent)
Likely reason: Classification banner and sensor-system identifiers — typical USCENTCOM MISREP redaction style
Top-left and top-right corner blocks
Likely reason: Sensor model / aircraft tail identifiers or time-code
Mid-left tall vertical block and mid-right small block
Likely reason: HUD telemetry: likely target range / azimuth / elevation / heading
Small black rectangle directly below the central cyan crosshair (target-data callout position)
Likely reason: Targeting-pod target data block (range / track / designation)
Bottom-right large block and bottom-left small block
Likely reason: Lat/lon, FL/altitude, ground speed, sensor mode/polarity, time — the standard MISREP HUD strip
PR-26 / slug 083 is the FIRST of two videos paired with the duplicate PDFs at slugs 041 and 042 (the same DoW-UAP-D23 MISREP, byte-identical). The second video is PR-27 / slug 084. Together this is a 2-video / 2-PDF (duplicate) cluster covering one UAE October 2023 mission report describing two UAP at FL243. The DVIDS description for slug 083 is mis-attributed (it describes DoW-UAP-D12, a still image) — do not let downstream summaries quote it verbatim as if it described this video.
A patch that looks different from the rest of the image. The record does not identify it.
It’s impossible to tell. The video description says the sensor’s movement made the patch cross the screen.
A video from a military sensor shows a patch that looks different from the surrounding image. At first, it appears in the upper-left corner of the screen, and the sensor tracks it.
The video doesn’t clearly show what the patch is or what it looks like up close. It shows only an area of the image that looks different from its surroundings. The curious thing is that we can follow it on-screen until the sensor loses track of it and can’t find it again.
The 43-second video was recorded by a heat-detecting sensor aboard a U.S. military aircraft. For much of the clip, the patch stays in roughly the same part of the screen: toward the upper left.
Then the sensor shifts the image. It turns from one side to the other, making the patch appear to cross the center of the screen. When the sensor changes direction again, the patch returns to roughly where it appeared before. In other words, its movement across the screen is caused by the sensor’s motion; the video doesn’t show the patch moving on its own.
At around the 29-second mark, the sensor stops tracking the patch. It leaves the sensor’s field of view through the left side of the screen.
The sensor continues moving relative to the background, but the patch doesn’t reappear. The video captures the moment the track is lost, but doesn’t show what happened to the patch afterward. The accompanying mission report says an unidentified phenomenon was observed during the mission.
It’s not known what the patch was or what made it look that way. The record offers no conventional explanation and doesn’t identify the phenomenon.
The patch exited on the left. The sensor kept moving, but the screen offered no answer.