The dispatch and proof layer for controlled UAS operations
Every flight needs a defensible yes or no before it launches.
Ledger checks aircraft, crew, area, route, and open blockers — then seals the evidence afterward. Run Part 107 or Part 135 today. Rehearse proposed Part 108 requirements in shadow mode without pretending the rule is final.
Built by a commercial pilot. Deterministic checks, no AI in the evaluation loop.
The problem
Logbooks record flights. They do not gate release.
Serious UAS programs outgrow spreadsheets long before Part 108 arrives. The pain is not missing a report template. It is not knowing — before launch — whether this specific flight was authorized, and not being able to prove why months later.
- Audit prep becomes folder archaeology across Drive, vendors, and email.
- Compliance owners cannot see what is open across PICs, aircraft, and missions in one place.
- Part 108 rehearsal should live in the operating record, not a one-time consulting project.
How it works
Record. Check. Release. Prove.
One loop under every mission. The same way every time.
-
Record
Mission-time truth
Missions, configuration snapshots, crew roles, training, checklists, findings, and flight logs connected in one system. Corrections supersede. They do not erase.
-
Check
Deterministic readiness
Part 107 or Part 135 checks run today, with proposed Part 108 checks alongside in shadow mode. Every finding cites the rule or control behind it.
-
Release
A defensible decision
Ledger turns aircraft, personnel, area, route, and risk into a release decision before the aircraft flies. Overrides keep a reason on the record.
-
Prove
Evidence on demand
Hashed, human-attested evidence packs trace every claim back to supporting records for regulators, insurers, partners, and customers.
See it in practice
Four moments where the record earns its keep.
Simulated scenarios. The operating rhythm is the product thesis.
Day of flight
Shadow mode
See where you stand every day — not in a one-time report.
Proposed Part 108 checks run alongside your live Part 107 or Part 135 operations. Every check runs, every finding opens with a citation, and nothing blocks until you choose to enforce it. Your standing against every proposed requirement lives in the operating record, not a one-time report — so when the rule is final, you ratify a record you have already been building.
Part 108 is still proposed rulemaking. Shadow mode keeps that honest while your team rehearses against the NPRM on real records.
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. AI can help prepare work. It never makes the release call, and nothing enters finalized compliance evidence without human attestation.
- No hallucinated compliance.
- No folder archaeology.
- Just the record, the rule, and the receipts.
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
Built for teams with multiple PICs, a compliance owner, and auditors who ask follow-up questions.
Utility and infrastructure inspection, corridor patrol, energy, survey. Five to fifty people. Part 107, Part 135, or BVLOS waiver operations that are too big for a spreadsheet program and too lean for a regulatory affairs department.
Operators land on their work. Compliance officers see what is open across the org. External auditors get a scoped read-only portal — no account required. If a single PIC and a spreadsheet still cover your program, you probably do not need us yet.
Why us
Lightcone Ledger is built by Chris Remboldt, a commercial pilot (multi-engine, instrument, UAS) and software founder — because the gate has to be credible to the people who actually release flights.
The grandfathering question, mapped.
Part 108 transition paths are still unresolved. We are publishing a scenario analysis of what existing BVLOS waivers could face under the final rule — and what to do now under each. Get the brief when it ships.