Competing Explanations for UAP: A Hypothesis Checklist for Analysts

Bottom line: A good UAP analysis doesn’t start with “What is it?” It starts with “What do we actually have?”—which pieces are physical evidence, which are records, which are testimony, and which are interpretation. This guide gives you a practical checklist to compare competing hypotheses without treating every story as equal or every anomaly as exotic.

Why it matters: UAP discussions often collapse into two unhelpful extremes—automatic dismissal or automatic belief. Taming Gravity’s approach is “find the science, not the fiction”: steel-man conventional explanations (misidentification, instrument artifacts, classified tech) while also leaving disciplined room for genuinely unresolved cases. What you’ll learn here is a step-by-step way to build and test explanations, identify missing data, and avoid common traps that inflate certainty.

What counts as evidence (and what doesn’t)

Before you compare hypotheses, sort what you have into categories. This is the fastest way to reduce confusion and prevent a single dramatic detail from dominating the entire case.

1) Physical evidence

• Recovered materials with documented provenance (where they were, who handled them, when, and how contamination was controlled).
• Instrumented measurements that are independently recoverable (e.g., raw sensor logs, not just screenshots).
• Environmental traces tied to time and place (with clear collection methods).

Key question: Can an independent party re-examine the same physical thing and verify chain-of-custody?

2) Official records

• Declassified reports, memos, and archival material.
• Flight logs, radar logs, ATC audio, weather data, and incident timelines—especially when they can be cross-referenced.

For U.S. archival context and how such records are organized, the National Archives’ UAP research topic page is a useful starting reference for what “official record” can mean in practice: https://www.archives.gov/research/topics/uaps.

3) Testimony

• Pilot, operator, or eyewitness accounts.
• Second-hand accounts (clearly labeled as such).

Testimony can be valuable—especially when multiple witnesses independently report consistent details—but it is not the same as a measurement. Treat it as data that needs corroboration, not as a final answer.

4) Inference and reconstruction

• Analyst-made plots, 3D reconstructions, and estimated trajectories.
• Claims derived from partial data (e.g., “instant acceleration”) without full sensor context.

5) Disputed claims and speculation

• Assertions that rely on anonymous sourcing without verifiable documents.
• Origin claims (ET/UT/crypto-terrestrial/time travelers) without evidence that distinguishes them from alternatives.

The hypothesis checklist: a practical workflow

Use this checklist like a scoring rubric. You’re not trying to “win” an argument—you’re trying to see which hypotheses survive contact with the available data.

Step 1: Write the observation statement (not the conclusion)

Start with a minimal, source-bound description:

• Who observed it (roles, not celebrity value).
• When/where (time window, location, altitude band if known).
• What sensors (eyes, radar type, IR pod, phone camera, etc.).
• What was seen/measured (angles, durations, bearings, timestamps).

Avoid embedding interpretation words like “craft,” “intelligently controlled,” or “impossible.” Save those for hypotheses.

Step 2: Inventory the data products and their provenance

• Do you have raw files or only compressed video, cropped clips, or screenshots?
• Is there metadata (timestamps, focal length, sensor mode)?
• Do you know what processing occurred (stabilization, contrast enhancement, tracking box overlays)?

Some dramatic-seeming UAP clips can look far more ordinary once you understand what the camera is doing (auto-exposure shifts, digital zoom, parallax, stabilization artifacts). The reverse also happens: without provenance, a mundane-looking clip can’t be ruled “nothing.”

Step 3: Generate competing hypotheses (at least 5)

Force breadth. A useful set often includes:

• H1: Astronomical/atmospheric (planets, stars, meteors, sprites, lenticular clouds, mirages).
• H2: Conventional airborne objects (commercial aircraft, military aircraft, drones, balloons, birds, insects near the lens).
• H3: Sensor/processing artifacts (aliasing, glare, bokeh, rolling shutter, compression, tracking errors).
• H4: Human factors (stress, expectation, limited reference points over ocean/night, misestimated distance/size).
• H5: Classified or unknown terrestrial tech (test ranges, countermeasures, electronic warfare effects, novel drones).
• H6: Non-human technology (ET/other) as a placeholder hypothesis—only if you can specify what evidence would separate it from H5.
• H7: Hoax or narrative contamination (edited media, miscaptioned dates/locations, viral resharing, “friend-of-a-friend” escalation).

Step 4: List discriminators (what would change your mind?)

For each hypothesis, write 3–5 discriminators—observable things that would push probability up or down. Examples:

• Balloon vs. powered craft: consistent drift with winds aloft; no correlated acceleration in independent sensors.
• Camera artifact vs. object: motion changes with zoom/focus; object disappears when switching modes; parallax inconsistent with claimed range.
• Aircraft vs. “orb”: navigation light timing; ADS-B correlation (when available); contrails/engine heat signature patterns.

This step converts debate into a measurement plan: “What should we go find?”

Step 5: Build a timeline and cross-check independent sources

Create a single timeline with all timestamps and sources. Then ask:

• Do witnesses agree on sequence (not just impressions)?
• Do sensor observations overlap in time, or are they being merged across gaps?
• Do environmental conditions (cloud layers, winds, visibility) support the claimed observation?

Independent corroboration is powerful when it’s truly independent (different sensors, different operators, no shared comms that could align expectations). Also watch for common-mode failure, where multiple readouts may share the same processing pipeline, assumptions, or cueing.

Step 6: Watch for classic “performance claims”

Many UAP cases pivot on implied extraordinary performance: hypersonic speed, instant acceleration, transmedium travel, or no visible propulsion. These can be real—or they can be artifacts of geometry and limited data.

• Speed claims: require actual distance-over-time, not just angular motion in a narrow field of view.
• Acceleration claims: require consistent timing and position measurement; otherwise you may be seeing a track jump, a cut, or a loss of lock.
• “No heat” claims: IR sensors can saturate, change palettes, or miss certain signatures depending on mode and range.

Step 7: Score hypotheses against the evidence—separately by evidence type

Instead of one global “likelihood,” score each hypothesis against:

• Physical evidence (if any)
• Official records
• Sensor data quality
• Testimony consistency
• Provenance and custody

This prevents a compelling witness account from “laundering” a weak video, or a dramatic clip from overwhelming a thin paper trail.

Step 8: Document unknowns and stop conditions

Every case should end with:

• What’s missing (raw files, full-length video, radar logs, metadata, exact coordinates).
• What you tried (checks performed, sources consulted, assumptions tested).
• What would resolve it (specific records or measurements).

Sometimes the honest endpoint is “unresolved due to missing data.” That’s not failure—it’s correct accounting.

Common pitfalls that quietly wreck UAP analysis

Mixing categories of certainty

It’s easy to slide from “a pilot reported” to “it was.” Keep language aligned with evidence: reported, recorded, measured, inferred.

Over-trusting single-sensor narratives

A single sensor can mislead in ways that feel persuasive. Multi-sensor agreement helps—but only if you know the sensors are looking at the same thing at the same time.

Underestimating incentives without assuming conspiracy

Institutions can have incentives: classification culture, reputational risk, bureaucratic inertia, and media dynamics. None of these require a coordinated deception to affect what becomes public.

False dichotomies: “It’s aliens” vs. “it’s nothing”

A disciplined middle is often most accurate: “There is a real observation, but it’s not yet attributable.” That’s compatible with both skeptical and open-minded inquiry.

How to use this checklist on Taming Gravity (with examples)

On this site, you’ll see cases and themes that range from official disclosures to historical and cultural claims. The checklist helps you keep your footing across that range.

• For the site’s guiding philosophy, read Taming Gravity’s manifesto and method and note how it separates curiosity from credulity.
• If you’re exploring high-strangeness claims, compare your evidence categories against reported close encounter narratives in the Close Encounter events collection, and ask what could realistically corroborate each claim.
• For broader orientation across topics and case styles, browse the UAP & Ufology category archive and practice writing a one-paragraph observation statement before reading commentary.
• To test your “disputed claims” filter, try applying the checklist to a story with a complicated provenance like the Project Serpo explainer, focusing on what would count as official records versus lore.

What’s still missing in most UAP cases (open questions worth tracking)

Across many modern cases, the biggest limiting factor is not imagination—it’s access to the right data at the right resolution. A few recurring missing elements:

• Full-duration media instead of curated excerpts.
• Sensor mode and settings (what exactly was the instrument doing?).
• Correlated logs (time-synced radar/EO/IR/ATC) with known clock offsets.
• Provenance documentation showing what has (and hasn’t) been edited.

Until those gaps close, some cases will remain genuinely ambiguous—supporting multiple competing explanations at once.

Conclusion: a fair fight between explanations

Competing explanations aren’t a weakness of UAP analysis—they’re the point. When you systematically separate evidence from interpretation, force multiple hypotheses, and demand discriminators, you get a cleaner outcome: sometimes a conventional identification, sometimes a strong “artifact” explanation, sometimes a credible “unknown,” and only occasionally a case that even begins to justify extraordinary conclusions.

If you adopt one habit from this guide, make it this: write down what would change your mind before you argue for your favorite explanation. That’s how you keep the inquiry scientific—even in a topic crowded with noise.

Q&A

What does “unidentified” actually mean in UAP?

It means the available evidence doesn’t support a confident identification. It does not, by itself, imply extraterrestrial origin. “Unidentified” is an evidence status that can change if better data (raw sensor logs, metadata, corroborating records) becomes available.

What’s the single most important variable in many UAP videos?

Range (distance to the object). Without range, you usually can’t reliably determine true size or speed—only angular motion in the camera’s field of view. Many “extraordinary” performance claims collapse or remain untestable when range is unknown.

How should analysts treat eyewitness testimony?

As real data with known limits. Testimony can establish that something was perceived and can add context, but it can also be affected by stress, expectation, and lack of reference points. The strongest cases use testimony alongside independent records and sensor data, not in place of them.

Why do you recommend generating at least five hypotheses?

Because it prevents false binaries like “aliens vs. nothing” and forces you to consider mundane causes (balloons, aircraft, artifacts) and institutional realities (classification, incomplete release). It also makes your analysis testable by focusing on discriminators that would favor one hypothesis over another.

When is it reasonable to consider a non-human technology hypothesis?

Only after you can articulate what evidence would distinguish it from (a) misidentification and artifacts and (b) advanced but terrestrial technology. If you can’t define unique discriminators, the hypothesis remains speculative and should be labeled accordingly.