Each anomaly layer plotted independently. Brighter zones indicate multi-layer convergence — the primary signal of a site warranting ground investigation. Toggle layers to isolate specific signal types.
Sites ordered chronologically. Clustering in certain epochs may indicate bombardment cycles or active periods of unknown causation.
Confidence weights data quality, source independence, publication volume, and recency. A site can have high convergence but lower confidence if it relies on few primary sources or outdated surveys.
Live API feeds are fetched client-side when site cards are opened. Cached data supplements live feeds for sites outside observatory coverage zones. All anomaly descriptions are cross-referenced against peer-reviewed publications.
| Database | Data type | Coverage | Status | Updated |
|---|
| Layer | Type | Weight | What we look for |
|---|
Historical and mythological accounts georeferenced and cross-matched against known geological anomaly zones. Independent cultural convergence on the same region is treated as a supporting data layer.
Witnessed events with official investigations, physical evidence, and geographic coordinates. These cases are distinct from the geological anomaly sites — they represent documented incidents with known or estimated impact locations, investigated by military, government, or scientific bodies.
Primary source declassified government documents relevant to UAP research, crash site investigation, and aerial anomaly analysis. All documents are publicly available through official government archives. Links open the original source document.
If you have identified a location with anomalous geological, geochemical, or historical characteristics that may warrant investigation, submit it here. All submissions are reviewed against our nine-layer scoring methodology before being added to the database.