The UAP Index Database Documentation (Version 1.0)

Purpose

The UAP Index is designed to collect, organize, and analyze information related to Unidentified Anomalous Phenomena (UAP) using a source-based and evidence-based approach.

The database does not determine truth. Instead, it records:

  • Who made a statement
  • What was said
  • What event is being described
  • What evidence exists
  • Who corroborates or contradicts the statement
  • Where the information originated

The goal is to help researchers evaluate information using transparency, provenance, and corroboration.


Core Philosophy

The UAP Index is built around a simple principle:

Trust should be earned through evidence and corroboration.

People, organizations, documents, sensor systems, and media sources may all contribute information. The database records these relationships and allows researchers to evaluate credibility independently.


Database Tables

uap_people

Stores information about individual people.

Examples:

  • David Fravor
  • Ryan Graves
  • David Grusch
  • Avi Loeb
  • Luis Elizondo

Purpose:

To identify individuals who make statements, provide testimony, perform investigations, publish research, or participate in events.

Primary Key:

person_id


uap_organizations

Stores information about organizations.

Examples:

  • U.S. Navy
  • NASA
  • AARO
  • FAA
  • SCU

Purpose:

To identify organizations that investigate, sponsor, publish, analyze, or otherwise participate in UAP-related activities.

Primary Key:

organization_id


uap_sources

Stores the original source of information.

Examples:

  • Congressional Hearing
  • Podcast Interview
  • News Article
  • Scientific Paper
  • Government Report

Purpose:

Tracks where information originated and allows verification of original materials.

Primary Key:

source_id


uap_events

Stores significant events.

Examples:

  • Nimitz Encounter
  • Roswell Incident
  • Phoenix Lights
  • Congressional Hearing 2023

Purpose:

Provides a central record for incidents, encounters, investigations, and historical events.

Primary Key:

event_id


uap_statements

Stores statements made by individuals or organizations.

Examples:

  • Witness testimony
  • Analytical assessments
  • Official conclusions
  • Observations

Purpose:

Records what was said and the basis for the statement.

Important Field:

knowledge_basis

Examples:

  • First-Hand Observation
  • Direct Participant
  • Second-Hand Testimony
  • Third-Hand Report
  • Analytical Assessment

Primary Key:

statement_id


uap_evidence

Stores evidence associated with events or statements.

Examples:

  • Radar data
  • FLIR video
  • Photographs
  • Official documents
  • Witness testimony

Purpose:

Provides supporting or contradictory evidence.

Primary Key:

evidence_id


uap_relationships

Stores relationships between entities.

Examples:

  • Person works for organization
  • Person witnessed event
  • Organization investigated event
  • Person corroborates another witness

Purpose:

Connects people, organizations, evidence, statements, and events.

Primary Key:

relationship_id


uap_locations

Stores geographic information.

Examples:

  • Pacific Ocean
  • Roswell, New Mexico
  • Wright-Patterson AFB

Purpose:

Provides standardized location records.

Primary Key:

location_id


uap_observed_characteristics

Stores reported characteristics of observed phenomena.

Examples:

  • No visible propulsion
  • Instant acceleration
  • Transmedium travel
  • Hovering

Purpose:

Allows comparison of reported object behavior across cases.

Primary Key:

characteristic_id


uap_witness_assessments

Stores evaluations of witness credibility.

Examples:

  • Military pilot
  • Radar operator
  • Scientist
  • Civilian witness

Purpose:

Records assessments and qualifications while preserving transparency.

Primary Key:

assessment_id


uap_statement_corroboration

Stores corroboration relationships.

Examples:

  • Witness supports another witness
  • Radar confirms visual observation
  • Official report supports testimony

Purpose:

Measures independent agreement among sources.

Primary Key:

corroboration_id


uap_statement_contradictions

Stores contradictions and disputes.

Examples:

  • Conflicting timelines
  • Disputed observations
  • Alternative explanations

Purpose:

Records disagreements without deleting information.

Primary Key:

contradiction_id


uap_media

Stores media files and media references.

Examples:

  • Videos
  • Audio recordings
  • Photographs
  • Documents

Purpose:

Provides links to supporting materials.

Primary Key:

media_id


uap_tags

Stores searchable tags.

Examples:

  • Tic Tac
  • Radar
  • Navy
  • Transmedium
  • Hypersonic

Purpose:

Improves searchability and categorization.

Primary Key:

tag_id


uap_timelines

Stores chronological information.

Examples:

  • Event dates
  • Observation times
  • Publication dates

Purpose:

Provides structured historical timelines.

Primary Key:

timeline_id


uap_programs

Stores government, military, scientific, and private programs.

Examples:

  • AATIP
  • AAWSAP
  • AARO
  • Project Blue Book

Purpose:

Tracks organizations and programs involved in research and investigations.

Primary Key:

program_id


Guiding Principles

The UAP Index does not determine what is true.

Instead, it seeks to document:

  • Sources
  • Statements
  • Evidence
  • Corroboration
  • Contradictions
  • Relationships

Researchers and readers are encouraged to evaluate information using the complete record rather than relying on a single source.

Version 1.0
TheUAPIndex.com