Public-source evidence surface

The nuclear-specific UAP proximity claim does not hold in this dataset

We tested public geocoded report rows against nuclear power-plant sites and matched non-nuclear power-plant controls. The stronger visible pattern is reporting geography: where people live, report, and see the sky.

QuestionDo reports cluster near nuclear plants?
ControlCompare with similar non-nuclear power sites
ResultNo nuclear-specific lift observed

Matched controls are the comparison anchor

The 50-mile test compares nuclear power-plant sites with matched non-nuclear power-plant controls. If the nuclear claim were visible here, the nuclear bar would be clearly higher.

Nuclear/control ratio: 0.851823. One-sided p-value for nuclear greater than controls: 0.85015.

Population is the first pattern to notice

Report rows are not evenly distributed across places. Place population and report count move together on a log scale.

0.641288
log population vs. log report-count correlation
105,086 of 105,250 rows matched to Census population places.

Airport proximity mostly follows people

Major airports are close to many reports, but they are also close to much of the U.S. population.

13.277 mi
median report-row distance to a major scheduled airport
Population-weighted Census-place median: 10.764 mi.

Reports span place sizes, with large places carrying much of the volume

These bars show the share of report rows by Census-place population bin. The table tabs remain available for exact rows.

Airport proximity should be read against the population baseline

If public report rows and the population baseline are close, airport proximity is a confounder rather than a standalone explanation.

Within 10 miles of a major scheduled airport
Within 25 miles of a major scheduled airport
Within 50 miles of a major scheduled airport

Uncertainty is visible, not hidden

17,783 U.S. rows did not resolve to Census place centroids. They are excluded from spatial tests until recovered by a public geocoder path.

How to read the evidence

SupportedPopulation/reporting geography is a strong observable factor.
ConfounderAirport proximity is measurable, but close to the population baseline.
Not supported hereA nuclear-specific proximity lift after matched power-plant controls.
Still outside scopeClassified activity, exact witness GPS, and case-level truth claims.
Added public infrastructure layer

Military and nuclear-security infrastructure are descriptive context, not a causation test

This layer adds official NTAD military installations and public NNSA/nuclear-security-enterprise anchors, including an NNSS public coordinate receipt. It helps people inspect proximity without implying classified activity, weapons storage, or attraction.

Public military installations
815 sites
91,139 public report rows within 50 miles (86.6%)
Public NNSA / nuclear-security-enterprise sites
8 sites
4,496 public report rows within 50 miles (4.3%)
Public strategic-delivery subset
10 sites
5,325 public report rows within 50 miles (5.1%)
What this layer can say
  • This layer measures public report proximity to public-source military-installation and NNSA site anchors.
  • The public military layer is official NTAD geometry; the public NNSA layer is official location text anchored to Census place centroids or source-backed public coordinates.
What this layer cannot say
  • This layer does not identify classified activity, weapons storage, operational status, or causation.
  • The public NNSA layer uses place centroids or public coordinate anchors, not exact facility boundaries.
  • Descriptive proximity to military infrastructure is not a matched-control causal or attraction test.
Population signal
78/100
log-pop/report correlation 0.641288
Airport confounder
90/100
event median 13.277 mi
Nuclear non-support
95/100
matched controls beat nuclear in the primary test
Missing geocodes
17783
14.5% of U.S. rows

Nuclear UAP Evidence Surface

This is a public-source, reduced analytical dataset for one question: do public UFO/UAP report rows cluster around nuclear power plants after ordinary controls?

Finding: The better explanation surface is population/reporting geography plus ordinary aviation proximity, while the nuclear-specific proximity claim remains unsupported after controls.

Primary 50-mile test:

  • Public geocoded report rows: 105,250
  • Nuclear sites: 57
  • Matched non-nuclear controls: 285
  • Nuclear/control mean ratio: 0.851823
  • One-sided p-value for nuclear greater than controls: 0.85015

What it is

  • A public-source evidence surface with hashes and receipts.
  • A reduced table of place/date/shape/geocode/proximity features.
  • A way to inspect population, airport, and nuclear-site proximity factors.

What it is not

  • It is not proof that any report is true or false.
  • It is not a claim that aircraft explain every report.
  • It is not exact sighting GPS; rows use public Census place centroids.
  • It is not a test of classified weapons-site activity.

What we can claim

  • The missing NUFORC-derived rows were not geocoded by assumption; they were excluded from spatial tests and logged for recovery.
  • The public geocoded report rows can be compared against Census place population and commercial-airport proximity as explanatory covariates.
  • At the place level, report counts can be assessed against population concentration without claiming reports are true or false.
  • Airport proximity can be treated as a public-source confounder, not as proof that airplanes caused specific reports.
  • The nuclear power-plant proximity claim remains unsupported in this evidence surface after matched non-nuclear power-plant controls.

What we cannot claim

  • This dataset cannot prove what witnesses saw.
  • This dataset cannot claim aircraft explain every report.
  • This dataset cannot treat city/place centroids as exact sighting coordinates.
  • This dataset cannot rule out all nuclear-weapons, military, or classified-site hypotheses.
  • This dataset cannot assume the skipped missing-geocode rows would preserve or reverse the result without a separate recovery run.