DISCLOSURE / FILE
A U.S. Navy Range Fouler Debrief form documenting a 2019 sighting over the Eastern United States of a small object that a 28-year military aviator and others could not identify, filed alongside the video DOW-UAP-PR112.
DOW-UAP-D090, Range Fouler Debrief, Eastern United States, 2019
A U.S. Navy Range Fouler Debrief form documenting a 2019 sighting over the Eastern United States of a small object that a 28-year military aviator and others could not identify, filed alongside the video DOW-UAP-PR112.
This is a standardized U.S. Navy Range Fouler Reporting Form used to log unauthorized intrusions into controlled airspace, released by the Department of War on July 10, 2026 for a 2019 incident over the Eastern United States. Between mission sorties, the reporting aviator observed a small object below the aircraft traveling in a straight line opposite the platform's direction at high speed, tracking it for roughly 10 to 15 seconds before recording the attached video DOW-UAP-PR112. The reporter, citing 28 years of service with the USAF and Navy, wrote that the object's speed carried it out of the field of view before it could be reacquired, and that on later analysis it appeared rectangular. All identifying information for aircrew and squadron was stripped from the form, and the report states others with equal or more experience were also unsure what the object was.
In between mission sorties, I noticed an object with flight characteristics unlike anything I had seen in my 28 years of performing for the USAF and Navy.p.2
I tracked it for ~10-15 seconds before we turned on the recorder to provide the attached video.p.2
Upon analysis after the flight, the object appeared to be rectangular.p.2
Others with equal or more experience were also unsure as to what this object might be.p.2
Absolutely no identifying information for aircrew or squadron will be recorded for analysis.p.1
Extracted text · Page 1
Page 1 · born-digital extraction
Please do not use the purple Ill Ii ■• Ai. Ti ii 1, Fi 151 I "submit" button above. Save and email the complete file manually Range Fouler Reporting Form (see below). Please complete this form to the best of your abil ity. If you do not have the requested information, please leave the field blank. If there was more than one "group," please report each on a separate form for data collection purposes. You should receive a response within 5 business days. Last Name, First Name Rank SIPR Email Address Crew Position This information is for contact only. - sanitizes all reports of identifying information. Absolutely no identifying information for aircrew or squadron will be recorded for analysis. Day Date (mmldd/yy) Time of detection Day I Night Side No. Buno Mission Description (CAS, BFM, etc) (hh:mm:ss Z) - Contact Working Area Contact Latitute NIS Contact Longitude E/W Contact Altitude Altitude Wind Dir at Wind (Ex: W-72 1A) (DD:MM:SS) (DD:MM:SS) (Ex: 22000) Constant? Contact Alt Speed (From) Please attempt to determine a Lat I Long for the contact at initial detection. We recommend using - to reference the sensor-derived bearing and range relative to the bullseye you had Was the contact moving? Yes in use. If that method is not available, any reasonable derivation of location will work, but please be as specific as possible and make a note in the comments section. These locations may be Direction/Speed used to cue other means of tracking. (Ex. 090/1 5) Please check all that apply: Round: D Moving Parts.- D Square: D Metallic: D Balloon-shaped: D Markings: D Wings/Airframe .- D Translucent.- D Other Shape .-O Opaque: O Apparent Propulsion .-□ Reflective .- D Please use the field below to describe the contact and any interaction in your own words with as much detail as possible. Please be sure to include any detail not included in questions above. uri le "submit" button! Save this form with filename "Date_Squadron_RF.pdf'' and email itto (Also in the global). For troubleshooting, call Thank you for your time. Please ensure all dis es are ripped for the entire time of interaction and saved as a . wmv (Example: . Squadron intel personnel shall upload those files to the re osito located at SSSRSTTF TS 1191; Fi IF'.
Page 2 · born-digital extraction
H IHiiVHb ii I ii r; Fi iiii I, 2 other In between mission sorties, I noticed an object with flight characteristics unlike anything I had seen in my 28 years of performing for the USAF and Navy. A small object was below us and appeared to be traveling in a straight line opposite our direction at high speed . I tracked it for ~10-15 seconds before we turned on the recorder to provide the attached video. When I zoomed in to try and achieve more resolution, the object's speed took out of my FOV and I was unable to reacquire, even at a lower zoom . Upon analysis after the flight, the object appeared to be rectangular. Others with equal or more experience were also unsure as to what this object might be.
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.
Please do not use the purple Ill Ii ■• Ai. Ti ii 1, Fi 151 I "submit" button above. Save and email the complete file manually Range Fouler Reporting Form (see below). Please complete this form to the best of your abil ity. If you do not have the requested information, please leave the field blank. If there was more than one "group," please report each on a separate form for data collection purposes. You should receive a response within 5 business days. Last Name, First Name Rank SIPR Email Address Crew Position This information is for contact only. - sanitizes all reports of identifying information. Absolutely no identifying information for aircrew or squadron will be recorded for analysis. Day Date (mmldd/yy) Time of detection Day I Night Side No. Buno Mission Description (CAS, BFM, etc) (hh:mm:ss Z) - Contact Working Area Contact Latitute NIS Contact Longitude E/W Contact Altitude Altitude Wind Dir at Wind (Ex: W-72 1A) (DD:MM:SS) (DD:MM:SS) (Ex: 22000) Constant? Contact Alt Speed (From) Please attempt to determine a Lat I Long for the contact at initial detection. We recommend using - to reference the sensor-derived bearing and range relative to the bullseye you had Was the contact moving? Yes in use. If that method is not available, any reasonable derivation of location will work, but please be as specific as possible and make a note in the comments section. These locations may be Direction/Speed used to cue other means of tracking. (Ex. 090/1 5) Please check all that apply: Round: D Moving Parts.- D Square: D Metallic: D Balloon-shaped: D Markings: D Wings/Airframe .- D Translucent.- D Other Shape .-O Opaque: O Apparent Propulsion .-□ Reflective .- D Please use the field below to describe the contact and any interaction in your own words with as much detail as possible. Please be sure to include any detail not included in questions above. uri le "submit" button! Save this form with filename "Date_Squadron_RF.pdf'' and email itto (Also in the global). For troubleshooting, call Thank you for your time. Please ensure all dis es are ripped for the entire time of interaction and saved as a . wmv (Example: . Squadron intel personnel shall upload those files to the re osito located at SSSRSTTF TS 1191; Fi IF'.
H IHiiVHb ii I ii r; Fi iiii I, 2 other In between mission sorties, I noticed an object with flight characteristics unlike anything I had seen in my 28 years of performing for the USAF and Navy. A small object was below us and appeared to be traveling in a straight line opposite our direction at high speed . I tracked it for ~10-15 seconds before we turned on the recorder to provide the attached video. When I zoomed in to try and achieve more resolution, the object's speed took out of my FOV and I was unable to reacquire, even at a lower zoom . Upon analysis after the flight, the object appeared to be rectangular. Others with equal or more experience were also unsure as to what this object might be.