Four Objects In Sequence, Arabian Gulf ISR 2020

Brief

Four UAP were observed at approximately 1736Z during an ISR mission over the Arabian Gulf in 2020, reported by a U.S. Air Force crew operating under AFCENT. The objects appeared sequentially — one at 17:36:22, two side by side at 17:36:30, and one more at 17:36:49 — a pattern the war.gov description characterizes as 'a line of dots followed by a trailing dot.' Cloud coverage prevented a clear visual track, and ISR imagery cross-referenced as 'ISR 1' was collected. The standardized UAP fields formally record no advanced capabilities or recovered materials.

Metadata

Agency

Department of War

Release

5/8/26

Type

PDF • .pdf

Length

7 pages

Classification

SECRET//REL TO USA, FVEY

Tags

4 objects, sequential formation, 1+2+1 pattern, Arabian Gulf, 2020, ISR asset, AFCENT, CENTCOM AOR, cloud-obstructed visual

Key points

• Four UAP were observed beneath a redacted sensor platform in the Arabian Gulf at approximately 1736Z, with sub-minute timestamps for each appearance.p.7
• Two of the four UAP appeared side by side simultaneously at 17:36:30, flanked by solo objects 8 seconds before and 19 seconds after, producing a 1+2+1 sequential formation.p.7
• Cloud coverage directly obstructed the observing platform from maintaining visual continuity on the objects.p.7
• ISR imagery was collected and cross-referenced as 'ISR 1,' indicating a companion sensor file exists outside this MISREP.p.7
• The structured 'UAP Advanced Capabilities And/Or Materials' field is answered 'NO,' a formal negative finding on the standardized checklist.p.6
• The report is classified SECRET//REL TO USA, FVEY and carries a declassification date of June 3, 2048 — 28 years after the event.p.1
• All personnel identifiers (rank, name, unit, wing, phone, email) are redacted under both (b)(6) personal privacy and (b)(3) 10 U.S.C. §130b.p.2
• The mission was tasked to the U.S. Air Force under AFCENT, placing it within the CENTCOM area of responsibility.p.1

Verbatim

• 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).

  p.7

• 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.

  p.7

• UAP Advanced Capabilities And/Or Materials (yes/no; if yes, describe): NO

  p.6

• (SECRET//REL TO USA, FVEY) WEATHER WAS (NOT) A FACTOR (EXPLAIN WHY IF IT WAS)

  p.4

• Declassification Date (YYYYMMDD): 20480603

  p.1

• Country Tasked: US - UNITED STATES • Service Tasked: A - AIR FORCE

  p.2

Most interesting

• The declassification date of June 3, 2048 means this report stays protected for 28 years after the 2020 event, suggesting the operational context — platform type, mission, location specifics — remains sensitive far beyond a typical tactical report.
• The 27-second observation window (17:36:22 to 17:36:49) with distinct sub-second timestamps implies active sensor tracking rather than a passive visual scan, yet the platform identity and sensor type are entirely redacted.
• The war.gov description characterizes the formation as 'a line of dots followed by a trailing dot,' consistent with the 1+2+1 sequential appearance documented in the GENTEXT.
• The entire ACEQUIP section — radar, radar warning receiver, missile warning system, ECM, chaff, flares, missiles, gun, targeting pod — is redacted under (b)(1)1.4a, making it impossible to determine the observing aircraft type or its sensor configuration.
• Page 5 of 7 produced no extractable text, leaving a gap in the structured data fields between the mission timeline (page 4) and the off-station/UAP event section (page 6).
• The MISREP form itself includes a dedicated 'UAP Objects/Material Recovered' field, confirming that physical recovery was a standard question on all UAP MISREPs routed through this reporting pipeline.