Aircraft and configuration
What's installed, accepted, current, and airworthy for this mission. Frozen as a snapshot, not a mutable present-state guess.
For BVLOS waiver holders, compliance officers, chief pilots, and accountable executives.
The dispatch and proof layer for controlled UAS operations.
Ledger checks aircraft, people, area, route, and risk before release, then preserves the evidence afterward. Use it under today's authority while the Part 108 readiness record builds underneath.
Not sure where your program stands against the NPRM? Start with the Readiness Assessment Open scope →Dispatch gate
Five things decide whether an operation should be released. Ledger checks all of them, every time.
This is not a logbook you fill in afterward. It's the surface your team uses during the operation, before wheels-up.
Personnel and currency
Who's assigned, trained, current, authorized, and rested, including operational roles a permit, certificate, or BVLOS authorization requires.
Area and route intent
Where the operation is approved to occur, the volume it's filed against, and the path it intends to fly.
Risk and safety findings
Which hazards, incidents, governing procedures, and open blockers bear on this release.
Mission record and evidence
What proof will exist once the flight is done, and exactly which records it traces back to.
How it works
Record. Check. Release. Prove.
One loop. It runs every mission, and it runs the same way every time.
-
01
Record
Missions, configuration snapshots, serialized components, operator credentials, checklists, and flight logs, connected in one system. Historical truth, preserved at mission time.
-
02
Check
Deterministic checks against Part 107 or Part 135 workflows today, with Part 108 readiness checks running alongside in shadow mode.
-
03
Release
Ledger turns the five readiness areas into a release decision before the aircraft flies. Where it says no, findings show what's exposed and what it takes to close it.
-
04
Prove
Hashed, human-attested evidence packs you can hand to a regulator, insurer, partner, or customer's legal team.
A release decision should not depend on what a model guessed.
Ledger's findings cite the actual regulation or internal control. Run the same check against the same records and you get the same answer, every time. A release decision you can explain to a regulator has to be reproducible, so there is no AI anywhere in the evaluation loop.
- No hallucinated compliance.
- No folder archaeology.
- No consultant theater.
Shadow mode
Shadow mode: build the Part 108 record while flying Part 107.
Part 108 readiness checks run alongside your live Part 107 or Part 135 operations. Every check runs, every finding opens, nothing blocks unless you choose to enforce it. When the rule is final you move from shadow to enforced. You're not starting from zero. You're ratifying a record you've been building all along.
What Ledger covers
One operational record for the work behind every release.
- Dispatch release
- Training and currency
- Mandatory reports
- SMS findings
- Airworthiness and configuration
- Associated elements
- Route intent
- Source watch
- Auditor portal
- Evidence packs and audit journal
See it in practice