ABOUT FLIGHT ATLAS

A logbook that proves itself — built by someone who knows why that matters.

Where this started

I served in USMC aviation supply. In that world, a part without a paper trail isn't a part — it's a problem. Every component carries documentation that traces its origin, inspection history, and fitness for flight. When the paper trail is solid, the aircraft flies. When it isn't, the aircraft stays on the ground.

Pilots face the same problem with their logbooks. A logbook is the paper trail of a pilot's entire career — the evidence that says "I have the hours, the experience, the currency to fly this aircraft." But a paper logbook can be lost. A spreadsheet can be edited. And when an examiner, employer, or insurer asks "prove it," the answer usually comes down to "trust me."

That answer never worked in aviation supply. It shouldn't work for your logbook either.

The verified-records thesis

Flight Atlas is built on a simple thesis: a flight record should testify for itself. Every entry in your Atlas is signed the moment it's logged — not when you export it, not when someone asks for it, but at the source. The signature is a cryptographic proof that the record existed in this form at this time. Change one field and the signature fails.

This isn't a new idea. It's the same principle that secures software updates, financial transactions, and identity systems. Ed25519 — the signature scheme Flight Atlas uses — is an RFC-standard algorithm deployed across the internet. The math is well-understood, widely audited, and doesn't depend on trusting Flight Atlas.

The result: you can hand a proof packet to anyone — an examiner, an employer, an insurer — and they can verify it themselves. No account required. No trusting us. The records speak for themselves.

What Flight Atlas is

• A verifiable archive. Your flights, signed, in sequence. The cumulative map of everywhere you've flown. Exportable as proof packets, CSV, PDF, ACORD XML, and ISO 20022.
• A tool for pilots and travelers. Log pilot hours with signed §61.51(b) fields, or track commercial passenger trips on a signed map. One platform, two surfaces.
• Built for the long term. The append-only ledger, the open-standard signatures, the key registry — all designed so the records outlast the platform.

What Flight Atlas is not

• Not an EFB replacement. Flight Atlas doesn't do flight planning, weight-and-balance, or navigation. It's where your flights go after you land.
• Not FAA-issued or FAA-certified. Flight Atlas is supplementary record evidence. The pilot remains responsible for logbook accuracy under 14 CFR §61.51.
• Not a black box. The proof format is documented. The verification algorithm is standard Ed25519. You can check the results with OpenSSL, ssh-keygen, or any RFC 8032 library. No proprietary verification tool required.

Who runs this

I built Flight Atlas alone — one person, no team, no venture backing, no growth-at-all-costs plan. The business model is straightforward: you pay for the product, so I don't need to sell your data, run ads, or monetize your attention. The free tier signs and maps your first 50 flights. Paid tiers are listed plainly on the pricing page — what you pay is what it says. And because verification is math, not membership, the signatures on records you've already exported never expire with a plan.

If you need to reach me: support@atlasfly.io.

Your data, your exit

Your flights are yours. At any time you can export everything — as a signed JSON proof packet, logbook CSV, PDF, ACORD XML, or ISO 20022 supplementary data. The proof packet carries Ed25519 signatures that anyone can verify with standard tools (OpenSSL, ssh-keygen, any RFC 8032 library). No proprietary software required.

The proof packet is plain JSON you can read yourself, and the verification algorithm is standard Ed25519 (RFC 8032) — nothing proprietary to reverse-engineer. The public keys that anchor the signatures are served from a trust registry that you can query directly — no account needed. If this service disappeared tomorrow, your proof packets would still verify. The records outlast the platform.

What "kept honest by math" means

Every flight record is signed the moment it's written — not later, not on export, but at insert time. The database is append-only: records can be added but never silently altered. The signature covers the whole record, including its position in the append-only sequence, so a record can't be quietly reordered or replaced. Change one byte and the signature fails.

When someone verifies your proof packet, the verifier resolves the signing key from the Atlas trust registry — never from the request, never from the packet itself. The key resolution happens server-side, against a registry that only contains keys the platform has published. If a key isn't in the registry, verification fails closed. There is no backdoor, no override, no "trust us" escape hatch.

The math is Ed25519 — an RFC-standard algorithm deployed across the internet for software updates, financial transactions, and identity systems. The same math that secures those systems secures your logbook. You don't have to trust me. You can verify the records yourself.

The showcase: proof at scale

The map on the homepage isn't a mockup. It's a real working archive — 1,095 signed flights, each one independently verifiable, accumulated over years of actual flying. Every line on that map carries a signature. Every data point in the proof packet resolves to a hash in the manifest. It's a logbook that's been proving itself, flight after flight, since day one.

See it work →