DOW-UAP-D168, BAASS Project Management Plan, December 2008

53
⬇ Download HD (6.4 MB)
SHARE Reddit X Facebook HN Email
Agency
DoD
Category
military
Type
PDF
Event Date
12/2/2008
Released
2026-10-23
Size
6.4 MB
Original Filename
DOW-UAP-D168-BAASS_Project_Management_Plan-December_2008.pdf
Location
Las Vegas, Nevada
Status
REDACTED

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 December 2008 Bigelow Aerospace Advanced Space Studies (BAASS) Project Management Plan is an overview paper setting out the contractor’s proposed strategy, priorities, and milestones for executing contract HHM402-08-C-0072 (AAWSAP). The plan states that BAASS would address the program’s 12 technical areas through a smaller number of selected projects, including initiatives focused on physics research, project cooperation with government-held information, academic engagement, database development, oral-history interviewing, and collection or review of materials described as excluded from Project Blue Book. The plan argues that the most productive approach would be to study “craft” or events already believed by BAASS to demonstrate novel behavior across the 12 technical areas, rather than concentrating primarily on then-current academic or industrial state-of-the-art research.

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 992 words from pages 2, 3, 4, 5, 6, 7, 8, 9 of 49.

PAGE 2

Bigelow Aerospace Advanced Space Studies Project Management Plan (Overview Paper) This information 1s proprletaiy and confidential and cannot be disseminated or 11sed witboot prior written consent from the Operating Manager ef BAAss•.

PAGE 3

BIGELOW AEROSPACE ADVANCED SPACE STUDIES AAP Person 4 AAP Person 7 Deputy Administrator This information is proprietary and confidential and cannot be disseminated or used without prior written consent fr 0111 tire Operating Ma11ager of BMss•.

PAGE 4

Importance of the Work There has been over six decades of intensive activity of advanced aerospace craft in the skies over North America and around the world. These have been witnessed, photographed and chased by military pilots, witnessed by ground crews, by commercial airline pilots and by thousands of military and civilian ground based personnel. The importance of this study lies in the possibility that some of these advanced aerospace craft may represent a threat to the security of the United States including its airspace and nuclear facilities. It is thus a very high priority to further our understanding of the physics and engineering feasibility of advanced aerospace weapon systems applications as they apply to the potential future capabilities of foreign threat systems out to the far term, i.e. from now out through the year 2050. BAASS appreciates the high level of trust that has been bestowed on the organization by the sponsors/DIA in assigning us with the responsibility of furthering our understanding of the physics and engineering feasibility of advanced aerospace weapons system applications. BAASS understands the sobering importance and the long term implications of this project. Page ii This information is proprietaFY a Rel eeAfieleAtial and cannot be disseminated or used without prior ·,witteR eoRseRt from the OperatiRg MaRager of BAAss•.

PAGE 5

BAAS$ acknowledges the receipt of three sets of documents that were AAP P submitted in fulfillment of contracts 081006-1 to the Mutual UFO Network a_.._/,,, (MUFON), 080930-1 to Earthtech International and an assignment to l~P Person a BAAS$ employee. These reports that were separately authored by: were prepared and delivered to BAASS under serious time constraints. We appreciate the service of these people. Page iii This inforniation is proprietary and confidential and cannot be disseminated or used without prior writteri eoriserit froFA tt:1e 013erating Manager of 9AASS®.

PAGE 6

TABLE OF CONTENTS BAASS Staff and Advisors ..................................................................................... i Preface................................................................................................................ ii Acknowledgements............................................................................................ iii Table of Contents............................................................................................... iv Key Recommendations .......................................................................................4 Introduction (scope of work)............................................................................... 8 Plans of Action and Milestones ........................................................................ 10 Page iv Tllis i11for 111ation is proprietary and confidential and cannot be disseminated

PAGE 7

This Project Manager Report (PMR) fulfills the requirement to submit a report as part of the Advanced Aerospace Weapon System Application contract HHM402-08-C-0072. The report comprises overview projects that are focused on and include the scope of the final report (due in September 2009) for the twelve effects, (11) Armament (RF and DEW), and {12) Other areas in support of 1-11. The PMR addresses a Plan of Action, Milestones and the composition of BAASS analytical teams for these twelve technical areas. In numerous places throughout the Earth Tech report previously mentioned, ,.~,.1"""'P,,,. .P,,,.e.- rs_o _n ...l.and others refer to the need for "examining more exotic possibilities that might account for reports of truly anomalous characteristics of high­ performance craft of unknown origin whose mode of operation appears to be well advanced beyond that presently known." With that in mind, we present the Plans of Action and Milestones in this report comprising nine separate major projects which collectively address all twelve of the technical areas. It should be emphasized that for each of the nine projects, we envisage extension and expansion into 2010 and 2011. Accordingly, the milestones for each of the nine projects described herein should include extensions into 2010, 2011 and beyond. I his information 1s proprietary a11d confidential and cannot be disseminated or used without prior ·n1ritten eonsent from the Operating Manager ef BAAss• .

PAGE 8

The nine major projects are: Project Physics was mandated by the DIA to study the current research on all twelve technical areas. Earthtech and its subcontractors will deliver approximately 24 in depth position papers targeted to twelve technical areas by Project Engagement will locate and secure small geographic areas that experience very frequent displays of advanced aerospace vehicles. The purpose is to directly observe and measure advanced aerospace vehicle performance. Project Cooperation requires the full cooperation between the DIA and BAASS and lays out the expected frameworks and specifics of this cooperation. This necessitates the help and cooperation from the DIA in assisting BAASS to obtain the high value film, hardware, relevant materials and information that are essential to the successful completion of this project. Project Campus will seek to stimulate, motivate and encourage the senior levels of the academic community in the United States to seriously study advanced aerospace vehicles and their performances. Project Database will bring together all existing data from multiple separate databases on advanced aerospace vehicle performances in the United States, and ultimately in other countries for the past 60 years. This new database will be searchable by keywords that address all twelve technical areas. This inforn ,ation is proprietary and confidential and cannot be disseminated or used without prior written consent fro,11 tlie Ope, ating Manage, of BAASS'"'.

PAGE 9

Project Oral History will contact and record interviews with dozens of highly placed individuals from industry and the military who have had direct knowledge of film evidence, physical material evidence, hardware itself, biological tissue and other material as they pertain to advanced aerial technology in the United States over the past several decades. Project Blue Book Materials will obtain the case files and associated trace materials with the help of DIA of multiple high value cases involving advanced aerospace vehicles that were never included in Project Blue Book presumably because they were deemed too sensitive. Project Northern Tier will obtain all the information and case files pertaining to dozens of cases in which advanced aerospace ve hicles flew over restricted air force bases containing nuclear weapons, hovered over weapon

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 #272 of 282 by Anomalousness Index. Across the entire 478-file archive it ranks #447 of 478.

That places it in the lower-scoring band of the archive (447 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.

sensor quality (eyewitness only) 30 × 0.25 = 7.5

No sensor, camera, or instrument backs this observation - it is testimony, relayed through the Department of War, and scored on the rubric's lowest sensor-quality tier for that reason. That doesn't bear on the witness's credibility (a separate axis); it reflects only that nothing beyond human perception recorded the event.

witness credibility (military personnel) 80 × 0.2 = 16.0

Reported by trained U.S. military personnel during an operational mission (12/2/2008) - a high witness-credibility tier, ranked in the rubric below astronaut, trained-aviator, and federal-agent testimony. This profile is shared across the AARO-submitted infrared-capture cluster that anchors the archive's densest scoring band, at 66.

corroboration (single witness instrument) 60 × 0.2 = 12.0

On corroboration, this file from the Department of War - like every single-tier file in the PURSUE archive - is a single-witness or single-instrument capture per the released metadata. The rubric doesn't infer multi-witness confirmation the summaries don't actually establish; this score reflects the honest limit of what was released, not a judgment about the underlying event.

kinematic anomaly (no kinematic data) 30 × 0.15 = 4.5

The released file contains no speed, acceleration, or vector data precise enough to score on the kinematic axis - and that's true archive-wide, not specific to this file. The rubric declines to infer kinematic anomaly from a witness's narrative estimate of how fast something moved; that itself says something about what PURSUE actually released: descriptive accounts, not flight-path telemetry.

mundane explanation available (weak mundane candidate) 70 × 0.1 = 7.0

Every file in the archive, including this one, scores this tier: a conventional explanation was considered in the released record but isn't treated as dispositive. That's a pattern in how war.gov's own summaries are written - they consistently hedge against strong conclusions either way - and the rubric takes that hedging at face value rather than resolving it for them.

official disposition (unresolved no review) 60 × 0.1 = 6.0

This file from the Department of War is catalogued as unresolved, with no formal review process having concluded - logged into the system, but not yet finalized by any review. The rubric treats that differently from 'open after review,' because the absence of a completed review is itself part of the file's status, not a placeholder for one.

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.

DoD · VIDEO SCORE 68

DOW-UAP-PR024, Unresolved UAP Report, Middle East, 2023

DoD · VIDEO SCORE 68

DOW-UAP-PR072, "ADMINISTRATIVE REVISION: IIR 1777 J0032 22 Kazakhstan - UAP in the vicinit…

DoD · VIDEO SCORE 68

DOW-UAP-PR106, Unresolved UAP Report, Eastern United States, 2020

DoD · VIDEO SCORE 68

DOW-UAP-PR108, Unresolved UAP Report, Western United States, 2020

DoD · VIDEO SCORE 68

DOW-UAP-PR109, Unresolved UAP Report, Eastern United States, 2015

DoD · VIDEO SCORE 68

DOW-UAP-PR110, Unresolved UAP Report, Eastern United States, 2020

BROWSE ALL 478 FILES →

Verification

SHA-256:

f72a51b4199db2d1758ac9796a4c1b669ba6013a7fae10a609150eaf0293eefd

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 →

Source: https://www.war.gov/medialink/ufo/release-07/documents/DOW-UAP-D168-BAASS_Project_Management_Plan-December_2008.pdf

📡 Subscribe via RSS 🔔 Watch on GitHub