A U.S. military infrared sensor tracked a small contrast object near the sea surface. The crew reported multiple sharp 90-degree turns and an estimated 80 mph — but the public release withholds the geometry needed to turn that description into measured extraordinary performance.
DOW-UAP-PR34 is the October 2023 Greece UAP case in which a U.S. military infrared sensor tracked a small object near the Aegean Sea surface. Mission report D33 records multiple sharp 90-degree turns and an estimated speed of about 80 mph. The official video is real; the harder question is what the public release actually lets us prove about the object's speed, size, range and manoeuvres.
The encounter sits inside MISREP 9329374, a seven-page operational mission report from the 33rd Special Operations Squadron. The report identifies the mission as Air Force ISR under AFSOC and USCENTCOM. The aircraft type and callsign remain redacted in the public copy.
The sortie took off from LGLR at 23:39Z on 26 October 2023, with the possible UAP first logged at 00:35:12Z on 27 October while the aircraft was still en route. The report records landing at OJMS at 13:09Z after 13 hours 30 minutes of mission time, including 6 hours 29 minutes of full-motion-video activity.
That context matters. The UAP entry was not written as a standalone UFO story after the fact. It appears as one operational observation inside a much longer military mission record.
The public mission report lists an AN/DAS-4 targeting pod, full-motion video as the primary sensor, and Link 16 among the aircraft's datalinks. Those details tell us this was a modern military ISR platform with a sophisticated electro-optical/infrared sensor suite.
The 33rd Special Operations Squadron is associated with MQ-9 operations, and the sensor/endurance profile is consistent with that family of platform. But the released PR34 mission report redacts the asset type. The UAP Map therefore treats “MQ-9” as a plausible platform inference — not an established fact for this sortie.
The report immediately adds that the object was too small to make out details. “Circular” is therefore an appearance description, not a measured physical planform.
The form records “Sharp 90 degree turns.” The narrative says multiple 90-degree turns while flying just above the ocean surface.
The mission form explicitly marks kinetic velocity accuracy as “Estimated.” No public range solution or raw telemetry accompanies the figure.
The same UAP form that contains the 90-degree-turn language records the observer assessment as Benign. It lists physical state as Solid, propulsion means as UNK, intelligent control as NO, signatures as NONE, effects on persons as NO, effects on equipment as NONE, and recovered material as NO.
Those entries do not explain the object. They do demonstrate that the original report was not written as a breathless claim of advanced craft performance.
An area of contrast enters the lower-left portion of the infrared sensor field of view.
The contrast area moves horizontally while the sensor itself pans to track it. Screen motion therefore mixes object motion with sensor pointing.
The sensor designates the contrast area and synchronizes the reticle with its relative position.
The operator changes the image processing to improve separation from background.
The contrast becomes indistinguishable against the background and the reticle loses lock.
The audit and release material place the event off the Northern Sporades, Greece. The mission paperwork also contains a partially redacted military grid reference beginning 35S KD, which supports a broad regional placement rather than a precise coordinate.
That distinction is important. A grid prefix can help place the event in a broad area, but the public file does not supply enough unredacted digits to reconstruct the crew's exact position or the object's exact track.
So this Case File deliberately stops at the level the evidence supports: north-central Aegean, off the Northern Sporades. Any more precise marker would be presentation, not recovered fact.
The DVIDS video page carries a generic 1 October 2023 “date taken” field. The paired mission report is much more specific: it timestamps the observation at 00:35:12Z on 27 October 2023. The release manifest also associates the companion document with 27 October and the Aegean Sea.
For this Case File, 27 October is therefore the controlling incident date. The 1 October field is preserved as part of the archive history, but it should not be mistaken for the event timestamp.
Once a date is copied into search results, videos and summaries, it can take on the appearance of certainty. Here the operational record gives us a stronger anchor than the generic media-page field.
To calculate true speed, turn radius or acceleration from an imaging sensor, an analyst needs geometry: range to target, line-of-sight rate, platform motion, sensor pointing, altitude/depth and timing data. Much of that information is redacted or absent from the public release.
The report’s 80 mph figure is explicitly estimated. Likewise, “just above the surface” is a crew description rather than a public instrumented altitude solution.
That means the 90-degree turns are meaningful as what the military operator perceived/reported, but the public video alone does not let an outside analyst prove an impossible or exotic maneuver.
The official title calls PR34 an Unresolved UAP Report. That is important: the government has not published an identification for the event.
But AARO/DVIDS also attaches an explicit warning that its video description is informational only and should not be interpreted as an analytical judgment, investigative conclusion or factual determination about the event’s validity, nature or significance.
The strongest reading is therefore narrow: an operational military crew recorded and reported an unidentified contrast object; the public material does not currently establish what it was.
A small UAS can be hard to resolve in infrared, can fly low over water, and can make abrupt heading changes. That fits several features of the report. What is missing is a positive identification: no public transponder, radar association, launch point, operator, or matching platform has been tied to PR34.
If the target was closer and smaller than the operator assumed, apparent speed and turn sharpness could be exaggerated. A seabird or other near-field object therefore has to remain in play. The public video, however, does not provide enough range, size or biological detail to confirm that explanation.
The aircraft is moving while the sensor pans, tracks and changes field of view. Background-relative motion can therefore look more dramatic than the target's true path through space. This is precisely why range, line-of-sight rate and platform motion matter.
The same mission record that notes sharp turns also records the observer assessment as Benign, physical state as Solid, propulsion as UNK, intelligent control as NO, signatures as NONE, and no effects on people or equipment. Those fields do not solve the case — but they are a powerful warning against reading more into the footage than the crew itself recorded.
After giving those explanations their strongest case, a residue remains: the crew still logged a small low-over-water object, tracked it in infrared, described repeated sharp turns, and did not identify it before the contact was lost. That is the part worth keeping open.
Three separately released Greece records now sit close enough in time and geography to be worth comparing. They should not be merged into one case, but the archive pattern is interesting in its own right.
Small, seemingly circular object near the ocean surface; reported sharp 90-degree turns; estimated 80 mph; approximately three minutes of tracked infrared footage.
A separate military report describes another small circular object near the ocean surface moving toward land. The estimated velocity in D35 is lower, and the released clip lasts only 24 seconds.
AARO's transparency release also includes a separate unresolved Greece report from January 2024. The public listing establishes another Greece event in the archive, not a demonstrated continuation of PR34 or PR35.
The three records may share nothing more than operating area, military sensors and the fact that each remained unresolved at release. Or they may eventually prove useful for comparison. The evidence does not yet justify claiming the same object, source or cause.
No public turn radius or acceleration calculation accompanies the release. The turns are recorded as the operator’s manoeuvrability observation.
The mission report explicitly marks the velocity as estimated. Public range and full telemetry are not available.
No radar corroboration has been published with PR34. That does not prove radar data never existed; it means none accompanies the public case file.
Both are plausible categories worth testing because the target was small, low over water and poorly resolved. Neither has been demonstrated from the released evidence.
No. PR35 is a separate Greece report dated 29 October 2023. Similar setting and timing make comparison worthwhile, but the records do not establish a shared object or cause.
No. It means the released record does not contain a definitive identification. The remaining possibilities include conventional objects, sensor/geometry effects and an object that has not yet been matched to a known explanation.
Compare PR34 with military sensor cases, close encounters and historic investigations across the full Case File archive.
Explore Case Files →Return to the map to explore where other UAP reports sit geographically and how the Aegean case fits the wider record.
Open The UAP Map →The Source Room below links the official PR34 video and the companion mission-report trail so readers can inspect the underlying record themselves.
There is enough here to take the case seriously: an operational report, nearly three minutes of infrared footage, a precise contact time and a crew description that includes both unusual movement and surprisingly restrained assessments.
There is also enough missing to resist an easy answer. Range, measured altitude, complete sensor geometry and raw telemetry are not public. A drone, bird or sensor-relative effect remains possible; none has been tied conclusively to this event in the released material.
That leaves PR34 where the government left it: unresolved. Whether that residue feels mundane, unusual or genuinely provocative is for the reader to decide.