DOW-UAP-D167: Project Capella data and research proposal
Documatica’s December 10, 2008 Project Capella proposal recommends a shared framework for BAASS sighting catalogues, with independent quality control, reliability codes and an initial Excel implementation. Appendices describe behavioral categories, a speculative six-layer model and sample database layouts. The budget and staffing figures are estimates, and the example sightings are catalogue entries rather than newly verified cases.
- File
- Document · Release 07
- Date
- Dec 10, 2008
- Location
- San Fransisco, California
- Extent
- 42 pages
Search This File
Probed Assessment
Capella is a proposal for organizing and testing sighting data; its hypotheses and sample entries are not proof of an anomalous cause.
Key takeaways
- A shared framework would preserve separate catalogues and their different reporting conventions.
- Independent quality control is central to the staffing plan.
- SVP separates source reliability, site inspection and natural explanations.
- The $610,000 and $830,000 budgets are estimates under stated assumptions.
Why it matters
The proposal exposes methodological risks in UAP databases, including duplicate reporting, selection bias, weak source checks and inconsistent coding.
Corroboration
Examples illustrate data design and retain mixed-quality source references. Author identities are redacted, and prototype claims do not demonstrate operational deployment.
Open questions
- • Which parts of Capella were implemented and audited?
- • How were duplicate witness reports reconciled?
- • What independent results followed the proposed quality-control process?
Probed separates this editorial assessment from the source claims below. It summarizes what the released artifact supports; it is not independent verification.
Official Description from War.gov
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 report developed for Bigelow Aerospace Advanced Space Studies (BAASS) outlines Project Capella, a proposed data warehouse framework for the capture, processing, classification, and retrieval of information relating to “unusual” aerial phenomena and related anomalies. The report describes a methodology for integrating existing catalogues, standardizing classification and reliability measures, reviewing foreign and private databases, and building personnel and software capacity to support analysis, literature review, and potential future field investigations. It presents the project as a means of consolidating disparate historical and contemporary case materials into a structured research system capable of supporting multiple BAASS initiatives. By proposing a data architecture centered on unusual aerial phenomena and related anomalies, the document helped lay the groundwork for later BAASS efforts, seeking to formalize UAP-oriented data collection and analysis within BAASS’s execution of AAWSAP.
Preserved verbatim as source metadata. This wording is separate from Probed’s file-specific description and assessment.
File Context
Related entities
Tracker findings
Database plan warned that earlier punched-card records were lost
The proposal reviews Battelle’s Blue Book statistical work and says the punched cards were not retained.
Witness records and sighting records used different units
The historical discussion distinguishes catalogues that store each witness report separately from those using one entry per sighting, an important difference for comparison.
Earlier databases lacked consistent validation
The author identifies poor validation, inconsistent standards and abandoned maintenance as obstacles across existing catalogues.
Separate catalogs were proposed to reduce selection bias
Capella proposes a common structure over separate catalogues rather than merging them into one chronology, and warns that selective observations can support almost any theory.
Project Capella planned a NIDS-first conversion
Initial work would convert NIDS data and record incoming BAASS cases from a proposed January 1, 2009 start, retaining paper source files.
Cost estimates carried substantial uncertainty
The rough budget, stated with a plus-or-minus 30 percent range and existing-office/server assumptions, totals $610,000 for year one and $830,000 for year two.
A 222 rating required minimum scores on three dimensions
A score of 222 or better requires each digit to be at least two; the appendix cites CUFOS, NIDS and French studies as users of the system.
Semiotic interpretation remained a theoretical proposal
The authors use semiotics and cognitive mismatch to speculate about apparent UAP absurdity; their conclusion calls for better investigations and data quality to test the ideas.
Release provenance
- Release
- Release 07
- Official ID
- release-07-file-019-dow-uap-d167-project-capella-december-2008
- Cleared
- Oct 23, 2026
Referenced Timeline
Six-layer paper presented in Porto
Appendix B says it is based on a presentation at University Fernando Pessoa on this date.
Documatica delivers Capella proposal
Report 001 is dated December 10, 2008 and addressed to BAASS.
Proposed start for incoming-case capture
The proposal suggests this date for a new BAASS case register; it does not confirm implementation.
Source Claims
Claims are attributed to the released source and remain distinct from Probed’s assessment and tracker findings.
Documatica Research’s Report 001 to BAASS is dated December 10, 2008 and proposes a data warehouse for unusual aerial phenomena and related anomalies.
December 10, 2008
The proposal reviews Battelle’s Blue Book statistical work and says the punched cards were not retained.
Battelle used punched cards for this work
The author identifies poor validation, inconsistent standards and abandoned maintenance as obstacles across existing catalogues.
Lack of data validation and lack of standards has impeded progress
Capella proposes a common structure over separate catalogues rather than merging them into one chronology, and warns that selective observations can support almost any theory.
Instead we propose a data warehousing system that supersedes the individual databases
The proposed first implementation uses Excel despite its not being a database system, to simplify editing, sorting and tabulation.
Although EXCEL is not a database system
Initial work would convert NIDS data and record incoming BAASS cases from a proposed January 1, 2009 start, retaining paper source files.
starting on January 1
The report recommends examining catalogue-access restrictions case by case and considering publication of Capella’s standards; it does not establish unrestricted rights to third-party data.
This question should be examined on a case-by-case basis with the owners of the catalogues.
The staffing plan requires a quality-control coordinator independent of the other data team members and protected when challenging data integrity.
this person must not report to others in the data warehouse team
The rough budget, stated with a plus-or-minus 30 percent range and existing-office/server assumptions, totals $610,000 for year one and $830,000 for year two.
Total $610,000
Appendix A calls for classification based on reported behavior without presupposing a particular explanatory theory.
And it must not presuppose any particular theory.
The proposed twenty-code scheme combines anomalies, close encounters, maneuvers and flybys with five variants; assigning a code is not verification of the report.
These four major categories, with their five variants, define a very simple system of 20 codes
The SVP code separately scores source reliability, site visits and the difficulty of natural explanations, using values zero through four.
Each of the three digits has a value from zero to four
Appendix B, based on an October 24, 2003 presentation at University Fernando Pessoa, proposes six layers: physical, anti-physical, psychological, physiological, psychic and cultural.
(1) physical manifestations, (2) anti-physical effects, (3) psychological factors, (4) physiological factors, (5) psychic effects and (6) cultural effects.
The six-layer paper criticizes both skeptical dismissal and selective extraterrestrial interpretations as shaped by human assumptions.
the ETH, just like the skeptical argument, is based on anthropocentric self-selection
The authors use semiotics and cognitive mismatch to speculate about apparent UAP absurdity; their conclusion calls for better investigations and data quality to test the ideas.
we need much better investigations, a great upgrading of data quality
Appendix C proposes ten linked Excel screens combining event description, sources, quality controls and the six analytical layers.
implemented in Excel in the form of ten pages or screens
The quality-control screen records date-time accuracy, location accuracy and SVP reliability, while other screens separate physical and psychological or physiological effects.
Date-time accuracy: Y or N depending on the knowledge of the year
Source Material & Evidence
Research Map
Lines appear only when two entities share a row-level source claim or dated timeline event. Unconnected nodes remain visible without implying a relationship.