Skip to content
UAP LEDGER
Department of War

DOW-UAP-D003: Mission Report, Arabian Gulf, 2020

Released: May 8, 2026

Written by AI from official sources, checked against them before publishingHow we do this

This is a standardized U.S. Military Mission Report (MISREP) filed by the Air Force documenting an operation in the Arabian Gulf in 2020. The report includes a dedicated section recording observations of unidentified anomalous phenomena (UAP), though most operational details remain classified.

What is a MISREP?

A MISREP is a standardized form the U.S. Military uses to record the circumstances surrounding its operations. It captures details about aircraft, equipment, mission timeline, and any significant events that occur during a flight.

What UAP activity was reported?

The report documents the observation of four unidentified anomalous phenomena. According to the record, the UAP were observed flying in the field of view of the aircraft's sensors. Cloud coverage prevented the crew from following the objects and obtaining a clear visual. The observations occurred at three separate times within a span of about 13 seconds, with one UAP observed at 17:36:22, two UAP observed side by side at 17:36:30, and one UAP observed at 17:36:49.

Why is most of the report classified?

The document is classified as SECRET with a declassification date of June 3, 2048. Most specific operational details, including the operation name, unit identity, aircraft callsign, location coordinates, and sensor information, are redacted under classification authority (b)(1)1.4a, which protects information that would reveal military operations, plans, or capabilities.

What does the report say about UAP capabilities?

The report includes a field asking whether the UAP demonstrated advanced capabilities or materials. The answer recorded is "NO," indicating the observers did not assess the objects as possessing advanced capabilities or materials based on the available observations.

Full Document Text

Text extracted directly from the source PDF. Text extraction via abigailhaddad/ufo-releases; original file at war.gov.

Read the full text (6,838 characters)
--- PAGE 1 ---
(b)(1)1.4a



Misrep 8799515
Narrative
(b)(1)1.4a                      (b)(1)1.4a, (b)(1)1.4c




Admin


CLASSIFICATION
• Classification: SECRET
• Associated Caveats: (b)(1)1.4a
• Classification Source (MS or Classification Guide ID): (b)(1)1.4a
• Declassification Date (YYYYMMDD): 20480603


OPERATION
• Operation: (b)(1)1.4a
             (b)(1)1.4a
• Domain:
• Operations Center: (b)(1)1.4a
• Major Command (MAJCOM): AFCENT
• Combatant Command (COCOM): (b)(1)1.4a


MSGID
• Report Type: MISREP
• Originator (Unit or Squadron): (b)(1)1.4a
• Submit Date (Auto-generated):




                           (b)(1)1.4a

--- PAGE 2 ---
(b)(1)1.4a


MSNID
• Tasking Order (ATO): (b)(1)1.4a
• Mission Type: (b)(1)1.4a
• ATO Mission Number: (b)(1)1.4a
• Country Tasked: US - UNITED STATES
• Service Tasked: A - AIR FORCE

Poc


POC
            (b) (6), (b)
• Rank:
• Full Name: (b) (6), (b)(3) 10 U.S.C.§130b
          (b) (6), (b)(3) 10 U.S.C.
• Unit:
            (b) (6), (b)(3) 10 U.S.C.§1
• Wing:
                                          (b) (6), (b)(3) 10 U.S.C.§130b
• Phone Number:
            (b) (6), (b)(3) 10 U.S.C.§130b
• Email:                                    @mail.smil.mil
• Service: Air Force
                                                  (b) (6), (b)(3) 10 U.S.C.§
• Operations Center:


QC
            (b) (6), (b)
• Rank:
• Full Name: (b) (6), (b)(3) 10 U.S.C.§130b
          (b) (6), (b)(3) 10 U.S.C.
• Unit:
           (b) (6), (b)(3) 10 U.S.C.§13
• Wing:
                                          (b) (6), (b)(3) 10 U.S.C.§130b
• Phone Number:
            (b) (6), (b)(3) 10 U.S.C.§130b
• Email:                                    @mail.smil.mil
• Service: Air Force
                                                  (b) (6), (b)(3) 10 U.S.C.§
• Operations Center:


APPROVER
            (b) (6), (b)(3)
• Rank:
                           (b) (6), (b)(3) 10 U.S.C.§130b
• Full Name:
          (b) (6), (b)(3) 10 U.S.C.§130b
• Unit:
            (b) (6), (b)(3) 1
• Wing:
• Phone Number: (b) (6), (b)(3) 10 U.S.C.§130b
• Email: (b) (6), (b)(3) 10 U.S.C.§130b                                                .smil.mil
• Service: Air Force
                                                  (b) (6), (b)(3) 10 U.S.C.§
• Operations Center:



                                                                  (b)(1)1.4a

--- PAGE 3 ---
(b)(1)1.4a


INGEST
• Rank:
• Full Name:
• Unit:
• Wing:
• Phone Number:
• Email:
• Service:
• Operations Center:

ACEQUIP


ACEQUIP
• Aircraft Callsign: (b)(1)1.4a
• 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:
• (b)(1)1.4a



• Type of Radar-Guided AAM:
• Num Radar-Guided AAM:
• 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: (b)(1)1.4a
                                     (b)(1)1.4a
• TGT Pod Name or Designator:
                       (b)(1)
• Additional Avionics: (b)(1)1.4a


                                (b)(1)1.4a

--- PAGE 4 ---
(b)(1)1.4a


• Data Link:
• Gentext:

Timeline


Takeoff
• Callsign: (b)(1)1.4a
                       (b)(
• Number of Aircraft:
                          (b)(1)1.4a
• Asset Type (Aircraft):
• Aircraft Tail Number(s): (b)(1)1.4a
                                             (b)(1)1.4a
• Takeoff Location (ICAO Code):
• Takeoff Time DTG: (b)(1)1.4a
• Mode 3 (IFF Codes):
• Gentext/Additional Details: (SECRET//REL TO USA, FVEY) WEATHER WAS (NOT) A FACTOR
(EXPLAIN WHY IF IT WAS)
• Mission Canceled:


Landing
• Last Land Location (ICAO Code): (b)(1)1.4a
• Last Land Time: (b)(1)1.4a
• Last Engine Shutdown Time: (b)(1)1.4a
• Total Mission Time: (b)(1)1.4a
• Gentext/Additional Details:


ISR
• Time-on Station DTG: (b)(1)1.4a
• Time-off Station DTG: (b)(1)1.4a
• Aircraft Callsign: (b)(1)1.4a
• Msn Type: (b)(1)1.4a
• Primary Sensor: (b)(1)1.4a
• Sensors Available: (b)(1)1.4a
• Tasking Type: (b)(1)1.4a
• Tasking or Request Number (JTAR#, AEM#, PRI#, or TIC#): -
• BE Number (if NTISR): -
• Tasked Start Point: (b)(1)1.4a
• Activity Description: ISR
• FMV or Image File Name (if NTISR): -
• EEIs Observed:
• Number of EEIs:


                                       (b)(1)1.4a

--- PAGE 5 ---


--- PAGE 6 ---
(b)(1)1.4a


• Killbox (Location):
• Mission Type: (b)(1)1.4a
• JTAC Callsign:
• Gentext/Additional Details:
• Did not Arrive On Station:


Off Station
• Time Off Station DTG: (b)(1)1.4a
• Total Time On Station: (b)(1)1.4a
• Gentext/Additional Details:


UAP
                      (b)(1)1.4a
• Initial Contact DTG:
• UAP Event Type: (b)(1)1.4a
• UAP Maneuverability Observations:
• UAP Response to Observer Actions:
                              (b)(1)1.4a
• MDS Type / Asset Type:
• Tail Number: (b)(1)1.4a
                                           (b)(1)1.4a
• Friendly Aircraft Location:
• Friendly Aircraft Altitude/Depth: (b)(1)1.4a
• Friendly Aircraft Trajectory:
• Observer Assessment of UAP:
• Friendly Aircraft Speed: (b)(1)1.4a
• 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 First Seen Location: (b)(1)1.4a
                                   (b)(1)1.4a
• UAP Last Seen Location:
• UAP Altitude, Depth, Velocity, and Trajectory (indicate estimated or measured):
• UAP Physical State: (b)(1)1.4a
                                    (b)(
• Number of UAP Sighted:
• UAP Propulsion Means:
• UAP Payload:
• UAP Under Intelligent Control (yes/no; if yes, describe):
• UAP Signatures:
• UAP Advanced Capabilities And/Or Materials (yes/no; if yes, describe): NO
• UAP RF Frequency:
• UAP RF Duration:
• UAP Event Serial Number: -


                                    (b)(1)1.4a

--- PAGE 7 ---
(b)(1)1.4a


• UAP Effects on Persons:
• UAP Objects/Material Recovered (yes/no; if yes, describe):
• UAP Effects on Equipment:
• Full Name:
• Rank/Grade:
• Email:
• Phone Number (VOSIP/STE):


GENTEXT/UAP
• UAP Description (e.g., size, shape, color, markings, recognizable features): 4X UAP OBSERVED
FLYING IN (b)(1)1.4a FOV. CLOUD COVERAGE OBSTRUCTED (b)(1)1.4a FROM FOLLOWING AND
GETTING A CLEAR VISUAL. (SEE ISR 1).
• Gentext (UAP Event Description): AT APPROX 1736Z 4 UAP WERE OBSERVED BENEATH
(b)(1)1.4a
           1X UAP OBSERVED AT 17:36:22, 2X UAP OBSERVED SIDE BY SIDE AT 17:36:30, AND 1X
UAP OBSERVED AT 17:36:49.




                           (b)(1)1.4a
View the official file

Frequently Asked Questions

How many UAP were observed and when?

Four unidentified anomalous phenomena were observed. One was observed at 17:36:22, two were observed side by side at 17:36:30, and one was observed at 17:36:49.

From the source, word for word
1X UAP OBSERVED AT 17:36:22, 2X UAP OBSERVED SIDE BY SIDE AT 17:36:30, AND 1X UAP OBSERVED AT 17:36:49.

Check it against the official file

What prevented the crew from getting a better look at the UAP?

Cloud coverage obstructed the field of view and prevented the crew from following the objects and obtaining a clear visual.

From the source, word for word
CLOUD COVERAGE OBSTRUCTED (b)(1)1.4a FROM FOLLOWING AND GETTING A CLEAR VISUAL.

Check it against the official file

What classification level is this report?

The report is classified as SECRET with associated caveats. It is scheduled for declassification on June 3, 2048.

Did the observers assess the UAP as having advanced capabilities?

No. The report includes a field asking whether the UAP demonstrated advanced capabilities or materials, and the recorded answer is "NO."

From the source, word for word
UAP Advanced Capabilities And/Or Materials (yes/no; if yes, describe): NO

Check it against the official file

Congressional Context

No confirmed links between this file and the congressional record yet. Connections are added only when the source text supports them, never inferred.