DOW-UAP-D033, Mission Report, Greece, October 2023
This document is a Mission Report (MISREP), a standardized reporting form the U.S. Military uses to record the circumstances surrounding its operations. U.S. military services often use MISREPs to report Unidentified Anomalous Phenomena (UAP) to AARO. The GENTEXT, or “general text” section of these reports often contains important qualitative, contextual information, distinguishing it from the more quantitative, or numerical, data found elsewhere in the report. A U.S. military operator reported observing a UAP “flying just above the surface of the ocean.” The report describes the UAP as taking “multiple 90-degree turns at an estimated 80 mph.” All descriptive and estimative language contained in this report reflects the reporter’s subjective interpretation at the time of the event. Such characterizations should not be interpreted as a conclusive indication of the presence or absence of any intrinsic object features or performance characteristics.
The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.
Text of the document
Machine-extracted from the PDF war.gov published (its text layer or OCR), so expect errors, especially in names, numbers and handwriting; the PDF is the authoritative copy. Lines that did not extract as readable text are left out. Showing about 939 words from pages 1, 2, 3, 4, 5, 6, 7 of 7.
PAGE 1
Dedasslfied by MG Richard A. Harrison USCENTCOM Chief of Staff THE LRE.~PROCEEDED TO FRAGGED TASKING TO SUPPORT DATA MASKED. AT 0013Z,~WAS 7•LINED TO SUPPORT DATA MASKED 1.4a ED ON•STATION AT 03422, CHECKED IN WITH DATA MASKED, AND PERFO D FMV/SIGINT COLLECTION AT AT 0035Z,[u;JOBSERVED lX POSS UAP (SEE UAP 1). AT 101 lZ[uia]RETURNED TO BASE. AT 1213Z,~HANpED BACK TO THE LRE. AT 1309Z, ~LANDED AT OJMS. FULL MOTION VIDEO WAS EXPLbITED BY GET. 13:30 MISSION Mission Narrative • Associated Caveats: • Classification Source (MS or Classification Guide ID): MS • Declassification Date (YYYYMMDD): 20481026 • Domain: AIR • Major Command (MAJCOM): AFSOC • Combatant Command (COCOM): USCENTCOM USCENTCOM MDR 26-0019 Approved for Release to AARO 01/26/26 001
PAGE 2
USCE'NTCOM Cl> ef of Sta'f • Report Type: MISREP • Originator (Unit or Squadron): 33 SOS • Submit Date: • Mission Type: ISR • Country Tasked: US -UNJTED STATES • Rank: AIC • Unit: Unavailable • Service: Air Force • Operations Center: 609 CAOC • Rank: SrA • Service: Air Force • Operations Center: 609 CAOC • Unit: Unavailable USCENTCOM MDR 26-0019 Approved for Release to AARO 01/26/26 002
PAGE 3
USCE-NTCOM Ct11ef of Staff • Wing: Other • Service: Air Force • Operations Center: 603 AOC • Full Name: • Phone Number: • Operations Center: • Radar Name or Destination: • Radar Software Load or Mission Data: • Radar Warning Receiver (RWR) Name or Designator: • RWR Software Load or Mission Data: • MWS Name or Designator: • MWS Software Load or Mission Data: • IRCM Name or Designator: • IRCM Software Load or Mission Data: • ECM Name or Designator: • ECM Software Load or Mission Data: • CMD Name or Designator: • Chaff Designator: • Num Chaff or Cartridges: • Flare Designator: • Num Flares: • Towed Decoy Name or Designator: • Towed Decoy Software Load or Mission Data: , • Num Towed Decoys: • Type of Radar-Guided AAM: • Num Radar-Guided AAM: USCENTCOM MDR 26-0019 Approved for Release to AARO 01/26/26 003
PAGE 4
• Type of IR-Guided AAM: • Num IR-Guided AAM: • Gun Name or Designator: • Num Gun Rounds: • Air-to-Ground Wpn to Include Num of Each: 1.4(a) • Additional Avionics: AWGMESH • Data Link: LINK 16 • Number of Aircraft: l • Takeoff Location (ICAO Code): LGLR • G entexUA dditionaI Details: ~TRANSITED AND LANDING AT OJMS TO REPLACE THE LIGHTNING LINE THAT LANDED AT LGLR YESTERDAY. • Mission Canceled: • Last Land Location (ICAO Code): OJMS • Last Land Time: 271309:00ZOCT23 • Last Engine Shutdown Time: 271319:00ZOCT23 • Total Mission Time: 13 hours 30 minutes USCENTCOM MDR 26-0019 Approved for Release to AARO 01/26/26 004
PAGE 5
USCE=NTCOM Chief of Staff Declassified on 22 JarJary 2026 • Sensors Available: G-MESH • Tasking Type: Planned • BE Number (if NTISR): - • Activity Description: TARGET DEVELOPMENT • FMV or Image File Name (if NTISR): - • EEis Observed: No • Number of EEis: • Global Campaign Plan: GCP -VEO (violent extremist group) UPON ARRIVAL TO THE SP AT 04132,wi) OBSERVED N EEIIRELATED ACTIVITY. BETWEEN 04132 AND 10112,~SHIFTED EYES TO MU TIPLE COI CONDUCTING POL, IDENTIFYING OBSTRUCTIONS TO HL2S, ROUTE ANALYS , AND CHARACTERIZING HUMAN OR VEHICLE TRAFFIC.~CONDUCTED POLO MULTIPLE COIS UNTIL RTB AT JSR ASSET UTILIZATION • Supported Unit: DATA MASK.ED • Weather: (UNCLASSIFIED) • Intel Gap Filled?: No • Gentext: (UNCLASSIFIED) USCENTCOM MDR 26-0019 Approved for Release to AARO 01/26/26 005
PAGE 6
On Station • Mission Type: • Gent ext/A dditional Details: • Did not Arrive On Station: OffS tation • Total Time On Station: 6 hours 29 minutes • UAP Event Type: UAP Incident • UAP Maneuverability Observations: Sharp 90 degree turns • UAP Response to Observer Actions: NONE • Friendly Aircraft Location: 35SKD5~31iia] • Friendly Aircrall Trajectory: SW • Observer Assessment of UAP: Benign • Friendly Aircraft Speed: • Observation Interrogation of UAP (yes/no; if yes list sensor(s) and returns):: • Third-party Observers and/or Reporters: • Friendly Aircraft State: • Training Range (If applicable): • Operational Range: • UAP Physical State: Solid • Number of UAP Sighted: • UAP Propulsion Means: UNK • UAP Payload: • UAP Under Intelligent Control (yes/no; if yes, describe): NO • UAP Signatures: NONE • UAP Advanced Capabilities And/Or Materials (yes/no; if yes, describe): UNK • UAP RF Frequency: UNK USCENTCOM MDR 26-0019 Approved for Release to AARO 01/26/26 006
PAGE 7
USCENTCOM Chief of Staff Declassified on 22 January 2026 • UAP RF Duration: UNK • UAP Event Serial Number: - • UAP Effects on Persons: NO • UAP Objects/Material Recovered (yes/no; if yes, describe): NO • UAP Effects on Equipment: NONE • Observer Engagement of UAP (yes/no; if yes, describe): NO • First Seen Radius: 5 • Last Accuracy: Estimated • Last Seen Radius: 5 • Kinetic Altitude Accuracy: Estimated • Kinetic Altitude: • Kinetic Depth Accuracy: Estimated • Kinetic Depth: • Kinetic Velocity Accuracy: Estimated • Kinetic Trajectory Accuracy: Estimated • Kinetic Trajectory: • UAP Date ofDoD Acquisition: 270035:00ZOCT23 • UAP Reaction to Observation, Interrogation, Engagement (y s/no; if yes, describe): UNK • UAP Anomalous Characteristics/ Behaviors: • First Accuracy: Estimated • UAP First Seen Location: • UAP Last Seen Location: • UAP Altitude, Depth, Velocity, and Trajectory (indicate esti ated or measured): • UAP Description (e.g., size, shape, color, markings, recogniza le features): SEEMINGLY CIRCULAR, TOO SMALL TO MAKE OUT DETAILS • Gentext (UAP Event Description): AT 0035ZJ 1.4a !WAS EN ROUTE TO THEIR TAR I ET WHEN THEY SPOTTED A UAP FLYING JUST ABOVE THE SURFACE OF THE OCEAN WATER. THE UAP TOOK MULTIPLE 90 DEGREE TURNS AT AN ESTIMATED 80 MPH. AT 00382, 1.4a LOST THE UAP FROM THEIR USCENTCOM MDR 26-0019 Approved for Release to AARO 01/26/26 007
Where this file fits in the PURSUE archive
This file is one of DoD's 257 files in the Trump PURSUE disclosure. Within the DoD agency block it ranks #181 of 257 by Anomalousness Index. Across the entire 450-file archive it ranks #355 of 450.
That places it in the lower-scoring band of the archive (355 of 450 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.
Anomalousness Index: 53/100
Evidentiary weight that this encounter remains unexplained after conventional analysis. Not a probability of extraterrestrial origin - that number is not honestly computable from the released files and this tracker refuses to publish it.
🤖 AI-ASSISTED SCORING · methodology
The six rubric components break down for this file as follows. Each component has a weighted contribution to the final score; the per-component explanation below describes what this file's particular value on that component means in the rubric's framework.
No sensor, camera, or instrument backs this observation - it is testimony, relayed through the Department of War, and scored on the rubric's lowest sensor-quality tier for that reason. That doesn't bear on the witness's credibility (a separate axis); it reflects only that nothing beyond human perception recorded the event.
Reported by trained U.S. military personnel during an operational mission (10/27/23) - a high witness-credibility tier, ranked in the rubric below astronaut, trained-aviator, and federal-agent testimony. This profile is shared across the AARO-submitted infrared-capture cluster that anchors the archive's densest scoring band, at 66.
On corroboration, this file from the Department of War - like every single-tier file in the PURSUE archive - is a single-witness or single-instrument capture per the released metadata. The rubric doesn't infer multi-witness confirmation the summaries don't actually establish; this score reflects the honest limit of what was released, not a judgment about the underlying event.
The released file contains no speed, acceleration, or vector data precise enough to score on the kinematic axis - and that's true archive-wide, not specific to this file. The rubric declines to infer kinematic anomaly from a witness's narrative estimate of how fast something moved; that itself says something about what PURSUE actually released: descriptive accounts, not flight-path telemetry.
Every file in the archive, including this one, scores this tier: a conventional explanation was considered in the released record but isn't treated as dispositive. That's a pattern in how war.gov's own summaries are written - they consistently hedge against strong conclusions either way - and the rubric takes that hedging at face value rather than resolving it for them.
This file from the Department of War is catalogued as unresolved, with no formal review process having concluded - logged into the system, but not yet finalized by any review. The rubric treats that differently from 'open after review,' because the absence of a completed review is itself part of the file's status, not a placeholder for one.
Bottom line on the score: the Anomalousness Index of 53/100 reflects evidentiary weight that this specific file's encounter remains structurally unexplained by the rubric's six axes - it is not a claim that the underlying event involved anything non-conventional, and it is not comparable across rubrics that use different weights. For the full per-axis weights and the rubric JSON, see /methodology.
Related files in DoD
Other PURSUE files in the same category, ranked by Anomalousness Index.
DOW-UAP-PR024, Unresolved UAP Report, Middle East, 2023
DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…
DOW-UAP-PR106, Unresolved UAP Report, Eastern United States, 2020
DOW-UAP-PR108, Unresolved UAP Report, Western United States, 2020
DOW-UAP-PR109, Unresolved UAP Report, Eastern United States, 2015
DOW-UAP-PR110, Unresolved UAP Report, Eastern United States, 2020
Verification
SHA-256:
This hash is the SHA-256 of the file body war.gov served on the verification date above. War.gov has re-processed some file bodies since first release (re-compression + OCR, no content removed - see /changes); we re-verify and record the change rather than silently serve a stale hash. How to check this yourself →
Source: https://www.war.gov/medialink/ufo/release_1/dow-uap-d33-mission-report-greece-october-2023.pdf