The Greece footage, sixty-six seconds of a bright object against a cloud bank

Mikey · 21 May 2026

THE SOURCE

DOW-UAP-PR28, “Unresolved UAP Report Greece January 2024”. A 66-second infrared sensor clip, 1920 by 1080, released in PURSUE Release 01 by the U.S. Department of War, hosted at war.gov. Catalogued in the project inventory as a reported fast-moving diamond-shaped object tracked against a cloud bank.

What this briefing is

This is the fifth briefing in the series and the second to take a single piece of footage rather than a document. Briefing 3 did the groundwork for all the video briefings: it explained how a targeting-pod feed actually works, the tracking reticle, the telemetry fields, the redaction blocks, why infrared inverts hot and cold, and why a single frame proves very little. This briefing assumes that and stays focused on the Greece clip itself. If you have not read Briefing 3, read it first, because the method there is the method here.

The clip is short, 66 seconds, and it is described in the release and in the project inventory as showing a fast-moving, diamond-shaped UAP. The job of this briefing is to say what the footage genuinely shows when you watch it frame by frame, which is both more and less than that description implies.

TL;DR

PR28 is a 66-second infrared clip from a military sensor, tagged Greece, January 2024. It shows a small, bright, compact object held near the centre of a tracking reticle while the sensor pans across a sky that is partly clear and partly filled with a large cloud bank. The sensor cycles through display modes during the clip: a split black-hot and white-hot view at the start, then a white-hot infrared view in which the object reads as a bright point, then a blue-tinted mode near the end. The object stays small and bright throughout and the cloud bank drifts behind it.

The footage is real sensor data. It is genuinely an object the sensor operator could not identify, tracked long enough to be logged as an unresolved UAP. What it is not is a clear view of a diamond-shaped craft. At the object’s size on the sensor, its shape is at or below the resolution of the image. The “diamond” is a description from the written report, not something the clip itself resolves. This briefing is evidence tier 2, primary footage. Strong and official, and very easy to over-read.

What the footage shows, second by second

Watching the full clip, the sequence is as follows.

It opens in a split-screen sensor mode. The frame is divided into two panels showing the same scene in different infrared polarities. A cloud bank fills the lower part of both panels and clear sky sits above. A small bright marker and the tracking reticle sit over the clear sky near the cloud tops. The object at this stage is a tiny bright speck. Heavy black redaction blocks cover the telemetry fields in every corner, as expected and as explained in Briefing 3.

The clip then settles into a single white-hot infrared view. Here the object is clearest: a small, round, bright white point of light, held just to the side of the reticle by the tracking system. The background through this section is mostly a smooth, hazy grey, the look of infrared sky, with a large soft bright region that is the cloud bank seen in infrared. The object stays compact and bright. It does not visibly change shape. It does not trail a contrail or streak. It does not pulse or flare. It simply sits there as a bright dot while the sensor and the cloud move around it.

As the clip continues the cloud bank passes behind the object. At several points the bright point is silhouetted against, or set just in front of, the brighter mass of cloud. This is the most useful part of the footage, because it shows the object is being tracked against a real, textured background and is not simply a fixed blemish on the sensor.

Near the end the sensor switches to a blue-tinted display mode. The sky becomes an even blue field, the object is a faint pale point near the reticle, and the clip ends shortly after.

What you do not see anywhere in 66 seconds is a clearly resolved shape. The object is always small relative to the sensor’s resolution. It reads as a bright dot. Calling it a diamond requires either a frame the public clip does not contain, or a judgement made from the written report rather than the image.

Reading the Greece clip

A few specific points, building on the method from Briefing 3.

The object’s apparent motion is mostly the sensor’s motion. A targeting pod locks onto a contact and keeps it near the reticle by slewing the camera. On screen this makes the object look nearly stationary while the background sweeps past. That is the normal behaviour of a tracked feed and it is why “the object held still while the clouds moved” is not, by itself, evidence of anything unusual. Equally, when the background appears to rush, that can be the camera slewing rather than the object accelerating. Without the telemetry, which is redacted, the clip cannot tell you the object’s true speed. The “fast-moving” in the report is the sensor operator’s assessment from data we cannot see.

The object’s brightness in white-hot mode means it was warmer than the sky around it, or more reflective, or both. That is genuine information. It is also true of a great many ordinary things: an aircraft, a drone, the sun glinting off a balloon or a light aircraft, a hot engine or exhaust. Infrared brightness narrows nothing down on its own.

The cloud bank is the most valuable element in the clip, and it cuts both ways. It confirms the object is a real thing in the real sky, tracked against real weather, not a sensor artefact. It also gives a parallax cue that, with telemetry, an analyst could use to bound the object’s distance. Without the telemetry, the viewer cannot. A bright point in front of a cloud could be close and small or distant and large, and the unaided eye, or the unaided viewer, cannot tell the difference.

The shape question is where this clip is most likely to be over-read. The release describes a diamond. The clip shows a dot. Both can be honestly true: an analyst with the full-resolution sensor feed, zoom control and telemetry may well have resolved a diamond outline that the compressed, redacted public clip does not preserve. But the briefing has to be plain about what the public can verify. From the footage as released, the object is a bright compact point, and its shape is not resolved.

What it reliably establishes

It establishes that in January 2024 a military sensor in the Greece area acquired and tracked an airborne object for at least 66 seconds, that the object was bright in infrared, that it was held against a real and changing cloud background, and that the sensor operator could not identify it, which is why it was logged and released as an unresolved UAP. It establishes that the footage is authentic government sensor data, traceable to a war.gov source. And it establishes, by the cloud parallax, that the object was a genuine physical thing in the sky and not an internal sensor artefact.

What it does not establish

It does not establish the object’s shape. The clip shows a bright point. The diamond comes from the written report, not from the footage as released.

It does not establish the object’s speed, size, altitude or distance. All of those depend on the telemetry, which is redacted out of the public clip. “Fast-moving” is the operator’s reading of data the viewer does not have.

It does not establish that the object was anomalous. A bright, compact, infrared-bright object tracked for about a minute against cloud is fully consistent with a range of ordinary explanations, an aircraft, a drone, a balloon, a glint, before any of them can be ruled out. The clip does not contain the information needed to rule them out. “Unresolved” means the military’s analysts did not reach a conclusion. It does not mean the object was extraordinary.

And it does not, as a single short clip, prove anything on its own. Sixty-six seconds of footage with the data fields blacked out is genuine evidence that something was there and was tracked. It is not evidence of what that something was. As set out in Briefing 3, a clip like this is a starting point for analysis, not a verdict.

Where this sits

This briefing is evidence tier 2, primary footage. PR28 is real, official, sensor-derived material of a kind the public rarely sees, and it is genuinely a case the US military logged as unresolved. It is also a short clip of a bright dot with its telemetry redacted, which means almost every interesting question about the object, shape, speed, size, distance, cannot be answered from the footage itself. The honest framing, the same one this site applies to every item, is that PR28 shows something real that was not identified, and that “not identified” is a long way short of “anomalous”.

Related wiki entries

The wiki entries below give background on the people, programmes and document types behind this briefing.

PURSUE · Department of War · AARO

References and further reading

• Presidential Unsealing and Reporting System for UAP Encounters, U.S. Department of War, war.gov/ufo
• Source clip: DOW-UAP-PR28, Unresolved UAP Report Greece January 2024, PURSUE Release 01, hosted at war.gov
• Briefing 3, How to read infrared sensor footage, and the eight-pointed star
• Briefing 1, Release one, what is actually inside the Department of War’s first UAP document drop
• AARO UAP Records, All-domain Anomaly Resolution Office, aaro.mil/UAP-Records