DOW-UAP-D173, BAASS Monthly Report, November 2009
This document is an administrative, programmatic, or contractor-produced record related to the Advanced Aerospace Weapon System Applications Program (AAWSAP), a Defense Intelligence Agency (DIA)-administered program active from 2008 to 2012. AAWSAP’s official scope of work identified 12 technical research areas relating to potential aerospace threats over a time horizon of more than 40 years. As part of the broader program record, the file documents how AAWSAP was scoped, organized, tasked, funded, executed, or described at a particular point in time. This November 2009 Bigelow Aerospace Advanced Space Studies (BAASS) progress report summarizes contractor activities for the period November 1–30, 2009. The report focuses on AAWSAP investigative activity based on information received via the Mutual UFO Network (MUFON), progress on investigations centering on a ranch in Utah, and a preliminary report on a “blue orb” incident. It also records BAASS’s continued emphasis on field investigation, case database expansion, and focused inquiry into events at the Utah ranch and surrounding area, including creation of a separate database for those incidents.
The summary above is sourced from the released file metadata as published to war.gov. The analysis sections below are original to this tracker.
Text of the document
Machine-extracted from the PDF war.gov published (its text layer or OCR), so expect errors, especially in names, numbers and handwriting; the PDF is the authoritative copy. Lines that did not extract as readable text are left out. Showing about 982 words from pages 2, 3, 4, 5, 6, 7, 8 of 155.
PAGE 2
Bigelow Aerospace Advanced Space Studies This lnfom,at1011 Is proprietary and co11fide11tial and ca1111ot be disse111i11ated QC used wfithout prior writteA consent frem the Operating Manager or SAA"SS".
PAGE 3
This Progress report summarizes BAAS$ activities and progress for the TABLE OF CONTENTS Topics covered in this report are the following: Summary of MUF ON Investigative Activity for November 2009 .....................Page 3 Progress on Utah Ranch lnvestigations ............................................................... Page 59 Preliminary Report on a Blue Orb lncident....................................................... Page 126
PAGE 4
Summary of Cases That MUFON Investigated During November 2009 In February 2009, BAASS executed a Purchase order with MUFON that entitles BAASS to: (a) receive notification of significant reports on UAP sightings from anywhere in the United States within hours, (b) receive timely reports from MUFON investigators regarding investigations of these incidents (c) receive physical evidence (including photographs, digital recordings, samples of soil, insects, plants, and animals) for scientific analysis. BAASS has multiple laboratories that are ready to conduct forensic, photographic, metallurgic, chemical, isotope, biological, chemical analysis of any specimens that BAASS receives from MUFON. It should be noted that during the month of October 2009, BAASS conducted an appraisal of MUFON's performance to date. BAASS was dissatisfied with MUFON's tendency to warehouse significant sums of money every month, especially during the early stages of the contract. Hence, for the remainder of the contract, BAASS will be reducing the monthly stipend to MUFON by $10,000. This will still enable MUFON to operate at normal efficiencies as they spend down the remaining surplus money. The following are selected investigative reports from MUFON deployments during the months of October 2009.
PAGE 5
Case Report MUFON SIP Deployment COORDINATES ACCURACY: Location of witness vehicle on higlnway where sighting occurred. Object was seen 30-50 feet to the East at approx. 25' altitude. LOCATION: Railroad crossing ot843(a)(3) ~odesto, CA DATE OF EVENT: 10-07-09
PAGE 6
On 10-13-09 a CAT 3 Star team Deployment in Modesto, CA was authorized and !'°AP Person 116 ras assigned as lead investigator. MUFON (Mutual UFO Network) STAR Team Manager SIP Project Coordinator Two witnesses (father and 6 yr. old daughter) in a rural area first observed and photographed two blue elevated lights in flight approximately a mile away towards town. Witness drove towards objects for better view. Upon arriving at general site, objects converged in flight upon witnesses from left and right to a hovering position viewed from front auto window. Frightened bythe event and belief that objects began following them, witness drove rapidly one half mile into town and a mile beyond where objects were no longer observed. Daughter developed a chest rash the nest day. Drove to Modesto, CA and arrived 19:07 at california Highway Patrol at 4030 Kiernan Ave., only to find the office closed. Drove the route that reporting witness took on the night of his sighting to familiarize myself with surroundings, abstractions, lighting, traffic, and details included in his report.
PAGE 7
Drove to the church and waited until 20:00 when witness came out of the church. As soon as we met and made Introductions, witness offered to show me his route and stops for different events. We drove south on Tully Road and stopped midway between Kiernan Ave and Bangs Ave where witness took his 3 photos ofthe 2 blue lights with his cell phone looking southeast. (We later discovered the location of the 2 blue lights were very close to the vicinity of the Modesto Hobby and Crafts Store on Bangs Avenue east of Tully Road approximately 3000 feet away from witness's camera We then drove east on Bangs Avenue and stopped on the east side of the railroad tracks where witness stated, " ... my vehicle was converged on from the fields from the north and south just before the auto dealership on my right. I could see them from my front window a roximatel thlrt to flft feet awa ) with one being above the other'' 1843 (a)( 3 ) We soon discovered the Modesto Hobby and Crafts Store was on Bangs Avenue approximately 800 feet from the railroad crossing between the tracks and the auto dealership. Hobby store was closed. We continued to travel east on Bangs Avenue past the Modesto Hobby and Crafts Store and auto dealership to the stoplight on McHenry Avenue where we turned right and drove two blocks through Pelandale Avenue where witness's daughter had stated, "Daddy, it is following us". From this location, an illuminated aerial object above the railroad crossing could still be in view at approximately 4400 feet away. We drove one block farther south on McHenry to approach the next stoplight at E. Union Avenue where, on the night of this event, a police car was parked and many workers had been repaving the road. When witness's daughter was asked if she still saw it, she said, "Yes". It is questionable if these other people had also
PAGE 8
seen these blue lights although approximately 6000 feet from the railroad By the time we drove another block ("' 1200 feet ) south on McHenry Avenue to Standiford Avenue, witness's daughter had said, "It went away". (Total distance from railroad crossing "'7200 feet) I didn't see any rash on witness's daughter's chest.******* will send me a picture of It. The origin of the rash is unknown, perhaps stress. I did not find any knowledgeable person at the Boyett Gas Service Station in the vicinity to interview. Witness was leaning towards the hobby shop model remote controlled airplane hoax scenario through discussion with friends. Because of this inclination, witness does not want to talk to BAASS or any other third party. I have good working communications now through witness for networking in the Modesto area and I expect to hear from him as he explores his suspicions further with his personal friends and hobby store. IAAP Person 116 MUFON Star Team Investigator With new info from******* below, I listed identity of objects in CMS Report as: IFO-Man-Made Objects.
Where this file fits in the PURSUE archive
This file is one of DoD's 282 files in the Trump PURSUE disclosure. Within the DoD agency block it ranks #276 of 282 by Anomalousness Index. Across the entire 478-file archive it ranks #451 of 478.
That places it in the lower-scoring band of the archive (451 of 478 by score), typical of investigative-record style files where the report is paper-based rather than instrumented.
Anomalousness Index: 53/100
Evidentiary weight that this encounter remains unexplained after conventional analysis. Not a probability of extraterrestrial origin - that number is not honestly computable from the released files and this tracker refuses to publish it.
🤖 AI-ASSISTED SCORING · methodology
The six rubric components break down for this file as follows. Each component has a weighted contribution to the final score; the per-component explanation below describes what this file's particular value on that component means in the rubric's framework.
Reported by a witness with no instrumented record. The lowest tier in the rubric's sensor axis. Eyewitness perception in field conditions, even when the witness is highly credentialed, scores below capture by any instrumented modality. This report reached the federal record through the Department of War.
Trained U.S. military personnel reporting from an operational mission context. A high witness-credibility tier, ranked in the rubric below astronaut, trained-aviator, and federal-agent testimony. This is the witness profile shared by the entire AARO-submitted infrared-capture cluster that anchors the 66-point score band.
Single-witness or single-instrument capture. This is the corroboration tier for the overwhelming majority of the PURSUE archive on the released metadata - the rubric records the honest limit of the underlying record rather than inferring multi-witness corroboration that the released summaries do not establish. A small number of files with an independent second witness or instrument score on the multi-witness/multi-instrument tier above this one.
No kinematic measurements - speed, acceleration, vector - are published in the released file with sufficient precision to score on the kinematic axis. The rubric does not infer kinematic anomaly from narrative observer estimates. Every file in the archive carries this value, which is itself an observation about the disclosure: kinematic-grade telemetry was not part of what was released.
A conventional candidate explanation has been considered but is not dispositive. Every file in the archive scores this way - reflecting that the underlying release metadata systematically caveats strong determinations in either direction. The released summaries warn against reading them as conclusive analytical judgments, and the rubric respects that.
Catalogued as unresolved with no formal review process having concluded. This is the disposition for a large share of the archive's military infrared captures - the reports are logged into the system as unresolved, but no formal review has finalized. The rubric distinguishes this from 'open after review' because the absence of review is itself a status signal.
Bottom line on the score: the Anomalousness Index of 53/100 reflects evidentiary weight that this specific file's encounter remains structurally unexplained by the rubric's six axes - it is not a claim that the underlying event involved anything non-conventional, and it is not comparable across rubrics that use different weights. For the full per-axis weights and the rubric JSON, see /methodology.
Related files in DoD
Other PURSUE files in the same category, ranked by Anomalousness Index.
DOW-UAP-PR024, Unresolved UAP Report, Middle East, 2023
DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…
DOW-UAP-PR106, Unresolved UAP Report, Eastern United States, 2020
DOW-UAP-PR108, Unresolved UAP Report, Western United States, 2020
DOW-UAP-PR109, Unresolved UAP Report, Eastern United States, 2015
DOW-UAP-PR110, Unresolved UAP Report, Eastern United States, 2020
Verification
SHA-256:
This hash is the SHA-256 of the file body war.gov served on the verification date above. War.gov has re-processed some file bodies since first release (re-compression + OCR, no content removed - see /changes); we re-verify and record the change rather than silently serve a stale hash. How to check this yourself →