Aircraft and configuration
What's installed, what's accepted, what's current, what's airworthy for this mission. Frozen as a snapshot, not a mutable present-state guess.
For compliance officers, safety managers, chief pilots, and accountable executives
The dispatch and proof layer for professional drone operations.
Ledger gives UAS teams a deterministic release gate before launch and a hashed evidence trail afterward. Run today's Part 107 or Part 135 compliance from the same operational record you will need for Part 108 BVLOS readiness.
Used by BVLOS program operators and test sites building toward Part 108 readiness.
BVLOS scale changes who gets trusted.
Under Part 107, the FAA certifies a pilot and trusts that person's judgment, one flight at a time.
The proposed Part 108 permit and certificate model works differently. It asks whether your organization has a system that can prevent unauthorized release, surface exceptions before launch, and prove afterward what was authorized.
That is no longer a recordkeeping problem. It is an operating-system problem. The teams that clear the BVLOS authorization bar will be the ones whose software decides before it flies and proves after.
Ledger is that system of record and release.
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 the 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.
Ledger rolls all five into one verdict: releasable, blocked, or human-overridden with a reason on the record. A decision your team can understand now and defend in an audit later.
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. Nothing overwritten; corrections supersede, they don't erase.
-
02
Check
Deterministic checks against Part 107 or Part 135 workflows today, with Part 108 readiness checks running alongside in shadow mode. Every check is codified. Every finding cites the actual regulation or control behind it.
-
03
Release
Ledger turns the five readiness areas into a release decision before the aircraft flies. Where it says no, citation-backed findings show what's exposed and what it takes to close it. Overrides are recorded inside the decision with reason and accepting role, never quietly edited away.
-
04
Prove
Hashed, human-attested evidence packs you can hand to a regulator, insurer, partner, or customer's legal team. Every claim traces back to the record that supports it. Proof on demand, not a deadline scramble.
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
Shadow mode
Start before the final text. Graduate when you're ready.
Part 108 remains proposed, but the operating model is clear enough to prepare against now. You don't have to wait for final text to build the record.
Ledger runs Part 108 readiness checks in shadow mode alongside your live Part 107 or Part 135 operations. Every check runs. Every finding opens. Nothing blocks unless your team chooses to enforce it. You see exactly where your operation stands against permit, certificate, and BVLOS authorization requirements before the scramble.
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.
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.
Just the record, the rule, and the receipts.
Agent-ready, not agent-authorized.
AI can prepare the work. It cannot make the call.
Ledger's governed MCP lets approved AI clients read readiness, stage flight logs and customer jobs, validate external imports, and prepare dispatch, evidence, and auditor packets.
They cannot release flights, override blockers, attest evidence, file reports, or change permissions. Every boundary stays human-gated and audit-logged.
Built for controlled operations.
The same record supports today's flights and tomorrow's readiness work.
Use Ledger under Part 107 or Part 135 while you build the permit, certificate, waiver, customer, and insurer evidence your scaled BVLOS program will need.
The audit isn't an event you prepare for. It's a state you're already in.
Most teams answer hard questions by assembling folders under deadline. Ledger answers them from live records.
At any moment, Ledger knows whether every aircraft is in an accepted configuration, every operator is current, every area is approved, and every open finding is accounted for. Your compliance posture is something you can see, not a report you have to build.
Aircraft configurations change. Rosters change. Rules change. Customers and partners ask for proof on their timeline, not yours. Ledger is built to stay current and review-ready as the operation grows.
See it in practice
Three moments where the record earns its keep.
Day of flight
Built for the people accountable for safe scale.
Compliance officers and safety managers.
Keeping training, findings, reports, procedures, and evidence connected to the flights they control.
Chief pilots and operations leads.
Releasing missions from live aircraft, crew, area, route, and risk records instead of static checklists.
Accountable executives.
Seeing whether the operation is ready, where the blockers are, and what proof exists for customers, insurers, and regulators.
Test sites and readiness programs.
Maintaining durable operational truth across a portfolio of operators and conditions.