Skip to content

Methodology

Every fact links to a US-government primary source

Sources

  • FAA Aircraft Registry →

    Public domain (US Government)

    Weekly bulk download

    Identity, type, year, owner, address, status, and certification dates. Rendered cell-by-cell with each cell linking back to the FAA inquiry record.

  • NTSB CAROL →

    Public domain (US Government)

    Per-tail query at build time; daily delta planned

    Event metadata, narrative, and probable-cause text. Probable cause is rendered verbatim — never paraphrased — and every row links to its ntsb.gov investigation page.

  • Federal Register — FAA Airworthiness Directives →

    Public domain (US Government)

    Per-make/model query at build time; weekly refresh planned

    AD title, abstract, and publication date. Each entry links to the Federal Register publication. We do not author summaries.

  • FAA Service Difficulty Reports →

    Public domain (US Government)

    No public API — pointer only

    FAA does not currently expose a public SDR API. The platform links to the agency portal rather than republishing or paraphrasing.

FAA Privacy Program

Aircraft owners enrolled in the FAA Privacy ICAO Address (PRO) program are surfaced here without owner identity — tail, type, year, and status only, with a Privacy Program notice in place of the registrant. PRO state is re-checked on every refresh; we never serve cached non-PRO data after a record has opted in.

What we do not do

  • No risk scores or "low / watch / high" tags.
  • No accidents-per-hour or rate calculations.
  • No make-vs-make or model-vs-model comparisons.
  • No "repaired aircraft" flags or inferred status.
  • No news or editorial summaries.
  • No NASA ASRS data.
  • No paraphrasing of NTSB narrative or probable cause.
  • No author voice on any specific aircraft or owner.

Disputes & takedown

If the agency is wrong: the platform reflects what the FAA or NTSB published. Disputes over the underlying record belong with the agency; we refresh weekly and reflect any agency correction on the next refresh.

If our render is wrong: wrong N-number, wrong field mapping, ingest bug — use the contact form with the tail number and the specific field disputed.

We acknowledge submissions within 5 business days and resolve within 14.