{
 "slug": "dow-uap-d090",
 "title": "DOW-UAP-D090 Range-Fouler-Debrief Eastern-US 2019",
 "agency": "DoW",
 "year": "2019",
 "page_count": 2,
 "source_page": "https://wearenotalone.space/document/dow-uap-d090/",
 "original_file": "https://wearenotalone.space/Season 04/release_04_documents/Documents/DOW-UAP-D090_Range-Fouler-Debrief_Eastern-US_2019.pdf",
 "license": "U.S. Government work — public domain. Text is machine OCR from the original scan; the page image is authoritative.",
 "pages": [
  {
   "n": 1,
   "image": "https://wearenotalone.space/transcripts/dow-uap-d090/p01.jpg",
   "text": "Please do not use the purple\nIll Ii ■• Ai. Ti ii 1, Fi 151 I\n\"submit\" button above. Save and\nemail the complete file manually\nRange Fouler Reporting Form\n(see below).\nPlease complete this form to the best of your ability. If you do not have the requested information,\nplease leave the field blank. If there was more than one \"group,\" please report each on a separate\nform for data collection purposes. You should receive a response within 5 business days.\nLast Name, First Name\nRank\nSIPR Email Address\nCrew Position\nThis information is for contact only. -\nsanitizes all reports of identifying information.\nAbsolutely no identifying information for aircrew or squadron will be recorded for analysis.\nDay\nDate (mmldd/yy)\nTime of detection\nDay I Night\nSide No.\nBuno\nMission Description (CAS, BFM, etc)\n(hh:mm:ss Z)\n-\nContact Working Area\nContact Latitute\nNIS\nContact Longitude\nE/W\nContact Altitude\nAltitude\nWind Dir at\nWind\n(Ex: W-72 1A)\n(DD:MM:SS)\n(DD:MM:SS)\n(Ex: 22000)\nConstant?\nContact Alt\nSpeed\n(From)\nPlease attempt to determine a Lat I Long for the contact at initial detection. We recommend\nusing -\nto reference the sensor-derived bearing and range relative to the bullseye you had\nWas the contact moving?\nYes\nin use. If that method is not available, any reasonable derivation of location will work, but please\nbe as specific as possible and make a note in the comments section. These locations may be\nDirection/Speed\nused to cue other means of tracking.\n(Ex. 090/1 5)\nPlease check all that apply:\nRound: D\nMoving Parts.-D\nSquare: D\nMetallic: D\nBalloon-shaped: D\nMarkings: D\nWings/Airframe .-D\nTranslucent.- D\nOther Shape.-O\nOpaque: O\nApparent Propulsion .-□\nReflective.- D\nPlease use the field below to describe the contact and any interaction in your own words with as much\ndetail as possible. Please be sure to include any detail not included in questions above.\nuri le \"submit\" button! Save this form with filename \"Date_Squadron_RF.pdf'' and email\nitto\n(Also in the global). For troubleshooting, call\nThank you for your time. Please ensure all dis\nes are ripped for the entire time of interaction and\nsaved as a .wmv (Example:\n. Squadron intel personnel shall upload those files\nto the re osito\nlocated at\nSSSRSTTF TS 1191; Fi IF'."
  },
  {
   "n": 2,
   "image": "https://wearenotalone.space/transcripts/dow-uap-d090/p02.jpg",
   "text": "H IHiiVHb ii I ii r; Fi iiii\nI, 2 other\nIn between mission sorties, I noticed an object with flight\ncharacteristics unlike anything I had seen in my 28 years of performing\nfor the USAF and\nNavy. A small object was below us and appeared to be traveling in a straight line opposite our direction\nat high speed. I tracked it for ~10-15 seconds before we turned on the recorder to provide the attached\nvideo. When I zoomed in to try and achieve more resolution, the object's speed took out of my FOV and\nI was unable to reacquire, even at a lower zoom. Upon analysis after the flight, the object appeared to\nbe rectangular. Others with equal or more experience were also unsure as to what this object might be."
  }
 ]
}