DISCLOSURE / FILE

Three Speed-Variant Contacts Over Arabian Gulf

DOW-UAP-D42, Range Fouler Debrief, Japan, 2023

A U.S. Navy Range Fouler Debrief Form filed by an O-2 pilot from VFA-87 (482ATKS) recording three objects tracked on sensor during an ISR mission at dusk on August 31, 2020.

Brief

On August 31, 2020 at dusk, an O-2 pilot flying an ISR mission logged a Range Fouler Debrief reporting an initial object that flew through the sensor screen at 18,000 feet, was overtaken by a second object of the same size and shape at much higher speed, and at one point produced three contacts on the screen moving amongst each other. The reporter recorded contact altitude as 18,000 feet, wind 150 at 230, and noted apparent propulsion with no visible moving parts or markings. The form is stamped USCENTCOM MOR 26-0028, approved for release to MRO, FOUO/PA applies, dated 03/16/26.

Metadata

Agency: Department of War
Release: 5/8/26
Incident: 8/31/20
Location: Arabian Gulf
Type: PDF • .pdf
Length: 1 pages
Classification: FOUO
Programs: SPEAR, USCENTCOM MOR 26-0028
Tags: multiple objects, high-speed overtake, sensor track, ISR mission, dusk, 18000 ft, Arabian Gulf, 2020, Range Fouler, CENTCOM

Key points

Incident logged on 08/31/20 at dusk by an O-2 ranked pilot assigned to squadron 482ATKS in the Pilot crew position.p.1
Contact altitude recorded as 18,000 feet with altitude constant and wind 150/230 at the contact altitude.p.1
Reporter marked 'Other Shape' and 'Apparent Propulsion' on the shape and characteristics checklist; did not mark metallic, markings, translucent, opaque, or reflective.p.1
Narrative describes an initial object surpassed by a second object of the same size and shape at much higher speed, with three objects on screen at one point moving amongst each other.p.1
Mission described as ISR; no LFE; AIM-9x self-track, ATFL/R autotrack, and Tally Achieved fields were not checked as Yes.p.1
Document is tagged USCENTCOM MOR 26-0028, Approved for Release to MRO, FOUO/PA applies, dated 03/16/26.p.1

Verbatim

Saw the initial object fly through the screen and started tracking i .
p.1
Initial object was surpassed by another object of same size and shape but much higher speed.
p.1
At one p4int during tracking the objects, there were three on the screen at the same time moving amongst each other.
p.1
USCENTCOM MOR 26-0028 Approved for Release to MRO. FOUO / PA applies 03/16/26
p.1

Most interesting

The listing header places the incident in the Arabian Gulf on 08/31/20, while the form itself records a working area and an MGRS grid prefix '39R' (a UTM zone covering portions of the Middle East), consistent with a CENTCOM area of responsibility.
The form is processed under SPEAR, which the document notes 'sanitizes all reports of identifying information' so 'absolutely no identifying information for aircrew or squadron will be recorded for analysis.'
The reporter checked 'Apparent Propulsion' but left moving parts, metallic, markings, translucent, opaque, and reflective unchecked, indicating an object whose only visible performance cue was motion itself.
Three contacts appeared on the sensor screen simultaneously, with the second overtaking the first at much higher speed, a multi-object kinematic signature rather than a single anomalous track.

Cross-references

PDFTwo IR Contacts Vanish in 1/30 SecondDepartment of War
PDFRound Object's Erratic Moves Over Persian GulfDepartment of War
PDFThree Small Contacts Over North Arabian SeaDepartment of War
PDF73-Second Cold-IR Round Object, Gulf of AdenDepartment of War
PDFEight-Minute Cold IR Track, Gulf of AdenDepartment of War
VIDNine-Second IR Clip, Arabian Gulf 2020Department of War
VIDFive-Second IR Clip, Arabian Gulf (No Statement)Department of War
VIDFive-Minute IR Clip Loses Contact, 2020Department of War

Common questions

What is Three Speed-Variant Contacts Over Arabian Gulf?: A U.S. Navy Range Fouler Debrief Form filed by an O-2 pilot from VFA-87 (482ATKS) recording three objects tracked on sensor during an ISR mission at dusk on August 31, 2020.
What does Three Speed-Variant Contacts Over Arabian Gulf reveal?: Incident logged on 08/31/20 at dusk by an O-2 ranked pilot assigned to squadron 482ATKS in the Pilot crew position. Contact altitude recorded as 18,000 feet with altitude constant and wind 150/230 at the contact altitude. Reporter marked 'Other Shape' and 'Apparent Propulsion' on the shape and characteristics checklist; did not mark metallic, markings,…
Which agency produced Three Speed-Variant Contacts Over Arabian Gulf?: Three Speed-Variant Contacts Over Arabian Gulf is a primary-source record from Department of War. Its original classification was FOUO.
When is Three Speed-Variant Contacts Over Arabian Gulf dated?: Three Speed-Variant Contacts Over Arabian Gulf is dated 2020-08-31. It was declassified 2026-03-16.
What programs and topics appear in Three Speed-Variant Contacts Over Arabian Gulf?: Three Speed-Variant Contacts Over Arabian Gulf references SPEAR, USCENTCOM MOR 26-0028, multiple objects, high-speed overtake, sensor track and ISR mission.
What does Three Speed-Variant Contacts Over Arabian Gulf say, in its own words?: "Saw the initial object fly through the screen and started tracking i ." (source p. 1).

SharePost Reddit

loading viewer...

Extracted text · Page 1

Three Speed-Variant Contacts Over Arabian Gulf

Page 1

Page 1 · born-digital extraction

0 cl rM · 1tted � v Ml Ric { {..;,. d (\ IH rr '>Of' U easJN o not �se r . tle,,.J?,-irp e • ., su6hirf '&uf�� ��ov,e'":'� $aJJe and [1 r I �sili rH, J,1 ltl r'Wri,' G: b If Range Fouler Debrief Form f- 1uol1;<l!!'J"1eL_� o )�q��p1l 9 s manua y 1 \See ue ow. Please complete this form to the best of your ability. If you do not have the requested information, please leave the fi � ld blank. If there was more t� � n one "group!" � le � se rep � rt each on a separate form for data collection purposes. You should receive a response within 5 business days. Last Name, First Name Rank 0-2 Squadron j482ATKS SfPR Email Address Crew Position Pilot This information is for contact only. SPEAR sanitizes all r�ports of identifying information. Absolutely no identifying information for aircrew or squadr ! n will be recorded for analysis. 08/31/20 Dusk Date (mmldd,YY) Time of detection Day I Ni;:,ht {tlh:mm:ss Z) Contact Worl<ing Area (Ex: W-72 1A) {b)(1)Ua Contact Latitute (DD:MM:SS) Side No. Buno N/S Contact Longitude EMI (0D:MM:SS) Please attempt to determine a Lat I Long for the contact at initial detection. We recommend using JMPS to reference the sensor-derived bearing· and range relative to the bullseye you had in use. If that method is not available. any reasonafJ/e derivation of location will worl<, but please be as specific as possible and make a note in the comments section. These locations may be used to cue other means of tracking. Radar Equipped: Other Stable Trackfile?: # of Contacts in "Group": EA Indications (Check af/ that apply): □ ECM An: □ Letter tdenlifii,r □ □ False Other/ Trackfiles Ambiguous AIM-9x Self-Track: A TFL/R Autotrack: • Tally Achieved: □ □ □ ISR Mission Description (GAS, BFM, etc) No LFE? 118000 Contact Altitude ( x: 22000) Yes Altitude Constant? Wind Dir at Contact Alt (From) Was the contact moving? Direction/Speed (Ex. 090/15) Wind Speed Yes 150/230 Please check all that apply: Round: D Square: D Balloon-shaped: D Wings/Airframe: D Other Shape:[Z] Apparent Propulsion.@ Moving Parts: D Metallic: D Markings: D Translucent D Opaque: D Reflective: D Plesse use the field below to describe the contact and any inte. 1 action in your own words with as much detail as possible. Ple.ase be sure to include any detail not inc/ I ded in questions above. MGRS Grid of initial contact: 39RWL2fijij.1:Mlm]a Saw the initial object fly through the screen and started tracking i . Initial object was surpassed by another object of same size and shape but much higher speed. At one p4int during tracking the objects, there were three on the screen at the same time moving amongst each other. I Don't use the purple "submit" button! Save this form with fl/enaml "Date_Squadron_RF.pd f " and email it to I 3.5c, (bl{6l I (Also in the global)� For troubleshooting, call I 3.5c, <b)(6) I Thank you for your time. Please ensure all display tapes are ripJed for the entire time of interaction and saved as a . wmv (Example: 4 May VFA-106 HUD. wmv). Squa ron intel personnel shall upload those files to the repository located at this link. f 3.5c. {b)(6) I USCENTCOM MOR 26-0028 Approved for Release to MRO. FOUO / PA applies 03/16/26 000001

Full transcript1 pages · 556 words›

Concatenated page-by-page transcript. Born-digital pages came through pdf.js; scanned pages were transcribed by Claude vision OCR. Pages marked unreadable failed multiple OCR retries (heavy redaction, microfilm artifacts, or blank separators) and are kept in place for audit.

Page 1born-digital extraction

0 cl rM · 1tted � v Ml Ric { {..;,. d (\ IH rr '>Of' U easJN o not �se r . tle,,.J?,-irp e • ., su6hirf '&uf�� ��ov,e'":'� $aJJe and [1 r I �sili rH, J,1 ltl r'Wri,' G: b If Range Fouler Debrief Form f- 1uol1;<l!!'J"1eL_� o )�q��p1l 9 s manua y 1 \See ue ow. Please complete this form to the best of your ability. If you do not have the requested information, please leave the fi � ld blank. If there was more t� � n one "group!" � le � se rep � rt each on a separate form for data collection purposes. You should receive a response within 5 business days. Last Name, First Name Rank 0-2 Squadron j482ATKS SfPR Email Address Crew Position Pilot This information is for contact only. SPEAR sanitizes all r�ports of identifying information. Absolutely no identifying information for aircrew or squadr ! n will be recorded for analysis. 08/31/20 Dusk Date (mmldd,YY) Time of detection Day I Ni;:,ht {tlh:mm:ss Z) Contact Worl<ing Area (Ex: W-72 1A) {b)(1)Ua Contact Latitute (DD:MM:SS) Side No. Buno N/S Contact Longitude EMI (0D:MM:SS) Please attempt to determine a Lat I Long for the contact at initial detection. We recommend using JMPS to reference the sensor-derived bearing· and range relative to the bullseye you had in use. If that method is not available. any reasonafJ/e derivation of location will worl<, but please be as specific as possible and make a note in the comments section. These locations may be used to cue other means of tracking. Radar Equipped: Other Stable Trackfile?: # of Contacts in "Group": EA Indications (Check af/ that apply): □ ECM An: □ Letter tdenlifii,r □ □ False Other/ Trackfiles Ambiguous AIM-9x Self-Track: A TFL/R Autotrack: • Tally Achieved: □ □ □ ISR Mission Description (GAS, BFM, etc) No LFE? 118000 Contact Altitude ( x: 22000) Yes Altitude Constant? Wind Dir at Contact Alt (From) Was the contact moving? Direction/Speed (Ex. 090/15) Wind Speed Yes 150/230 Please check all that apply: Round: D Square: D Balloon-shaped: D Wings/Airframe: D Other Shape:[Z] Apparent Propulsion.@ Moving Parts: D Metallic: D Markings: D Translucent D Opaque: D Reflective: D Plesse use the field below to describe the contact and any inte. 1 action in your own words with as much detail as possible. Ple.ase be sure to include any detail not inc/ I ded in questions above. MGRS Grid of initial contact: 39RWL2fijij.1:Mlm]a Saw the initial object fly through the screen and started tracking i . Initial object was surpassed by another object of same size and shape but much higher speed. At one p4int during tracking the objects, there were three on the screen at the same time moving amongst each other. I Don't use the purple "submit" button! Save this form with fl/enaml "Date_Squadron_RF.pd f " and email it to I 3.5c, (bl{6l I (Also in the global)� For troubleshooting, call I 3.5c, <b)(6) I Thank you for your time. Please ensure all display tapes are ripJed for the entire time of interaction and saved as a . wmv (Example: 4 May VFA-106 HUD. wmv). Squa ron intel personnel shall upload those files to the repository located at this link. f 3.5c. {b)(6) I USCENTCOM MOR 26-0028 Approved for Release to MRO. FOUO / PA applies 03/16/26 000001

DISCLOSURE / FILE

Three Speed-Variant Contacts Over Arabian Gulf

A U.S. Navy Range Fouler Debrief Form filed by an O-2 pilot from VFA-87 (482ATKS) recording three objects tracked on sensor during an ISR mission at dusk on August 31, 2020.

Brief

Key points

Incident logged on 08/31/20 at dusk by an O-2 ranked pilot assigned to squadron 482ATKS in the Pilot crew position.p.1

Contact altitude recorded as 18,000 feet with altitude constant and wind 150/230 at the contact altitude.p.1

Reporter marked 'Other Shape' and 'Apparent Propulsion' on the shape and characteristics checklist; did not mark metallic, markings, translucent, opaque, or reflective.p.1

Narrative describes an initial object surpassed by a second object of the same size and shape at much higher speed, with three objects on screen at one point moving amongst each other.p.1

Mission described as ISR; no LFE; AIM-9x self-track, ATFL/R autotrack, and Tally Achieved fields were not checked as Yes.p.1

Document is tagged USCENTCOM MOR 26-0028, Approved for Release to MRO, FOUO/PA applies, dated 03/16/26.p.1

Verbatim

Saw the initial object fly through the screen and started tracking i .

p.1

Initial object was surpassed by another object of same size and shape but much higher speed.

p.1

At one p4int during tracking the objects, there were three on the screen at the same time moving amongst each other.

p.1

USCENTCOM MOR 26-0028 Approved for Release to MRO. FOUO / PA applies 03/16/26

p.1

Most interesting

The listing header places the incident in the Arabian Gulf on 08/31/20, while the form itself records a working area and an MGRS grid prefix '39R' (a UTM zone covering portions of the Middle East), consistent with a CENTCOM area of responsibility.

The form is processed under SPEAR, which the document notes 'sanitizes all reports of identifying information' so 'absolutely no identifying information for aircrew or squadron will be recorded for analysis.'

The reporter checked 'Apparent Propulsion' but left moving parts, metallic, markings, translucent, opaque, and reflective unchecked, indicating an object whose only visible performance cue was motion itself.

Three contacts appeared on the sensor screen simultaneously, with the second overtaking the first at much higher speed, a multi-object kinematic signature rather than a single anomalous track.

Common questions

What is Three Speed-Variant Contacts Over Arabian Gulf?

A U.S. Navy Range Fouler Debrief Form filed by an O-2 pilot from VFA-87 (482ATKS) recording three objects tracked on sensor during an ISR mission at dusk on August 31, 2020.

What does Three Speed-Variant Contacts Over Arabian Gulf reveal?

Incident logged on 08/31/20 at dusk by an O-2 ranked pilot assigned to squadron 482ATKS in the Pilot crew position. Contact altitude recorded as 18,000 feet with altitude constant and wind 150/230 at the contact altitude. Reporter marked 'Other Shape' and 'Apparent Propulsion' on the shape and characteristics checklist; did not mark metallic, markings,…

Which agency produced Three Speed-Variant Contacts Over Arabian Gulf?

Three Speed-Variant Contacts Over Arabian Gulf is a primary-source record from Department of War. Its original classification was FOUO.

When is Three Speed-Variant Contacts Over Arabian Gulf dated?

Three Speed-Variant Contacts Over Arabian Gulf is dated 2020-08-31. It was declassified 2026-03-16.

What programs and topics appear in Three Speed-Variant Contacts Over Arabian Gulf?

Three Speed-Variant Contacts Over Arabian Gulf references SPEAR, USCENTCOM MOR 26-0028, multiple objects, high-speed overtake, sensor track and ISR mission.

What does Three Speed-Variant Contacts Over Arabian Gulf say, in its own words?

"Saw the initial object fly through the screen and started tracking i ." (source p. 1).

0 cl rM · 1tted � v Ml Ric { {..;,. d (\ IH rr '>Of' U easJN o not �se r . tle,,.J?,-irp e • ., su6hirf '&uf�� ov,e'":'� $aJJe and [1 r I �sili rH, J,1 ltl r'Wri,' G: b If Range Fouler Debrief Form f- 1uol1;<l!!'J"1eL_� o )�q��p1l 9 s manua y 1 \See ue ow. Please complete this form to the best of your ability. If you do not have the requested information, please leave the fi � ld blank. If there was more t� � n one "group!" � le � se rep � rt each on a separate form for data collection purposes. You should receive a response within 5 business days. Last Name, First Name Rank 0-2 Squadron j482ATKS SfPR Email Address Crew Position Pilot This information is for contact only. SPEAR sanitizes all r�ports of identifying information. Absolutely no identifying information for aircrew or squadr ! n will be recorded for analysis. 08/31/20 Dusk Date (mmldd,YY) Time of detection Day I Ni;:,ht {tlh:mm:ss Z) Contact Worl<ing Area (Ex: W-72 1A) {b)(1)Ua Contact Latitute (DD:MM:SS) Side No. Buno N/S Contact Longitude EMI (0D:MM:SS) Please attempt to determine a Lat I Long for the contact at initial detection. We recommend using JMPS to reference the sensor-derived bearing· and range relative to the bullseye you had in use. If that method is not available. any reasonafJ/e derivation of location will worl<, but please be as specific as possible and make a note in the comments section. These locations may be used to cue other means of tracking. Radar Equipped: Other Stable Trackfile?: # of Contacts in "Group": EA Indications (Check af/ that apply): □ ECM An: □ Letter tdenlifii,r □ □ False Other/ Trackfiles Ambiguous AIM-9x Self-Track: A TFL/R Autotrack: • Tally Achieved: □ □ □ ISR Mission Description (GAS, BFM, etc) No LFE? 118000 Contact Altitude ( x: 22000) Yes Altitude Constant? Wind Dir at Contact Alt (From) Was the contact moving? Direction/Speed (Ex. 090/15) Wind Speed Yes 150/230 Please check all that apply: Round: D Square: D Balloon-shaped: D Wings/Airframe: D Other Shape:[Z] Apparent Propulsion.@ Moving Parts: D Metallic: D Markings: D Translucent D Opaque: D Reflective: D Plesse use the field below to describe the contact and any inte. 1 action in your own words with as much detail as possible. Ple.ase be sure to include any detail not inc/ I ded in questions above. MGRS Grid of initial contact: 39RWL2fijij.1:Mlm]a Saw the initial object fly through the screen and started tracking i . Initial object was surpassed by another object of same size and shape but much higher speed. At one p4int during tracking the objects, there were three on the screen at the same time moving amongst each other. I Don't use the purple "submit" button! Save this form with fl/enaml "Date_Squadron_RF.pd f " and email it to I 3.5c, (bl{6l I (Also in the global)� For troubleshooting, call I 3.5c, <b)(6) I Thank you for your time. Please ensure all display tapes are ripJed for the entire time of interaction and saved as a . wmv (Example: 4 May VFA-106 HUD. wmv). Squa ron intel personnel shall upload those files to the repository located at this link. f 3.5c. {b)(6) I USCENTCOM MOR 26-0028 Approved for Release to MRO. FOUO / PA applies 03/16/26 000001

Three Speed-Variant Contacts Over Arabian Gulf

Brief

Metadata

Key points

Verbatim

Most interesting

Cross-references

Related topics

Common questions

Three Speed-Variant Contacts Over Arabian Gulf

Three Speed-Variant Contacts Over Arabian Gulf

Three Speed-Variant Contacts Over Arabian Gulf

Brief

Metadata

Key points

Verbatim

Most interesting

Cross-references

Related topics

Common questions

Three Speed-Variant Contacts Over Arabian Gulf