How UAP Logbook verifies a claim

UAP Logbook does not start with the most dramatic version of a story. It starts with the best available record: a document, an original image, a dated video, an official statement, or a named witness speaking on the record.

1. Find the closest source

When a claim begins in a clip, a repost or a headline, the first question is where it came from. The target is the underlying document, recording, archive page, hearing, filing or interview — not an account of an account.

2. Keep the claim and the record separate

A source can make a serious allegation without proving it. Articles state who said what, then distinguish the material that is public from the inference attached to it. This is why a document can be worth reporting even when it does not settle the larger story.

3. Inspect images in context

Images are checked for their original file, adjacent frames, captions, dates, cropping, and stated provenance where those are available. A striking crop may be real and still omit the information needed to interpret it.

4. Say what remains open

A missing source, a single uncorroborated witness, an unclear chain of custody, or a plausible ordinary explanation belongs in the story. Uncertainty is not filler; it is part of the record.

5. Correct the record in public

When new material materially changes a published item, UAP Logbook updates the article and records the correction. Readers can send source material or correction requests through the contact page.

Examples of the method

• Apollo photo claim: adjacent NASA scans were compared with a viral crop.
• Area 51: public maps, satellite imagery and agency histories were separated from the mythology around the site.
• Ghost rockets: the postwar reports were placed beside the documented military and archival record.

For the detailed editorial standard, read the editorial policy. For changes to published work, read the corrections policy.