RESOURCES
Everything you need to understand, use, and verify Flight Atlas.
How the proof system works
A deep technical walkthrough: hashing (SHA-512), manifest assembly, Ed25519 signatures, and verification. Covers what a proof packet contains, how it's constructed, and exactly what it proves — and doesn't prove.
Read the full guide →Regulatory alignment
How Flight Atlas structures records around 14 CFR §61.51(b) logbook-entry elements. Covers which §61.51(b) fields are stored, what signed proof packets prove, the relationship to AC 120-78B, and the current state of instructor endorsements.
Read the regulatory note →Verification walkthrough
Step-by-step: how to verify a proof packet using standard tools. The process is (1) resolve the trusted public key from the Atlas trust registry, (2) load the manifest content, (3) verify the Ed25519 signature against the content. Works with OpenSSL 3+, ssh-keygen, or any RFC 8032-compatible library. No Atlas account needed.
Open the public verifier →Export formats
Flight Atlas produces five self-serve export formats, all built from the same signed record set:
- JSON proof packet. Manifest, record hashes, per-record signatures, signer key IDs, and regulatory alignment metadata.
- Logbook CSV. Standard logbook fields, public proof fields only. No private key material.
- PDF. Pilot-facing archive format with the same field set as CSV.
- ACORD XML. Insurer-verifiable supplementary evidence export. Renders only after manifest and per-record proof checks pass.
- ISO 20022 SupplementaryData. Supplementary XML fragment carrying Atlas verification metadata without fabricating unsupported totals.
Account owners can also create pilot-authorized verifier links — time-limited, revocable URLs that expose selected proof fields without sharing the full export.
Frequently asked questions
Is Flight Atlas an EFB replacement?
No. Flight Atlas doesn't do flight planning, weight-and-balance, charts, or navigation. It's where your flights go after you land — a verifiable archive, not a cockpit tool.
Can I import from ForeFlight or another logbook?
Flight Atlas supports CSV import with field mapping. If your current logbook exports CSV, you can bring your history into Atlas. Manual entry and FlightAware backfill are also available. ForeFlight does not provide a public API for logbook export; direct ForeFlight import requires a manual CSV export from ForeFlight first.
What happens if I lose my signing key?
Your signing key is generated at account creation and stored encrypted. If you lose access to your account, contact support. The key is account-scoped — a new key can be provisioned, but records signed with the old key remain verifiable against the old public key as long as the key registry retains it.
Does Flight Atlas satisfy FAA recordkeeping requirements?
Flight Atlas is not FAA-issued, FAA-approved, or FAA-certified. Signed proof packets are supplementary evidence — they do not replace your duty to maintain an accurate logbook under 14 CFR §61.51. Read the full regulatory alignment note.
Can an examiner or insurer verify my records without an Atlas account?
Yes. Proof packets are self-verifying: the manifest, hashes, and signatures are all in the packet. The verifier resolves the public key from the Atlas trust registry — no account, no login, no trust in Flight Atlas required. You can also create pilot-authorized verifier links for specific records.
How does Flight Atlas handle commercial passenger flights vs. pilot logbook hours?
Flight Atlas keeps them separate. Pilot logbook flights carry §61.51(b) fields and are organized by aircraft tail. Commercial passenger trips are organized by airline and don't carry logbook fields. Both surfaces share the same signing infrastructure and the same unified map. You control which records appear in which exports.