lightcone systems

Ledger
Book a demo

BVLOS compliance software

BVLOS compliance software that releases each flight with proof.

Ledger is BVLOS compliance software for commercial UAS teams flying under Part 107, Part 135, or a BVLOS waiver. It checks aircraft, people, area, route, and risk before the dispatch release. It keeps the source records after landing. Proposed Part 108 checks run in shadow mode beside that live gate. Part 108 recordkeeping software maps the proposed §108.40 families and the §108.45 evidence pack. Waiver holders can map a Part 107 BVLOS waiver to Part 108 in the transition brief.

Book a 30-minute operator demo Why Ledger

The missing layer

The hard part is not storing the flight. It is reconstructing why the flight was allowed.

Operators build flight operations. They should not have to build an evidentiary system that tracks changing rules, effective dates, source records, and accountable decisions.

System What it answers What the record means
Telemetry What did the aircraft do? Observed machine state
Logbook What did the team record? Recorded event history
Ledger Why was this operation released? Facts evaluated against the governing rules and controls
Mission facts Effective ruleset Human decision Source evidence Release record

Dispatch release

Five facts decide whether an operation should be released.

This is the release gate, not a logbook completed after the flight. For BVLOS waiver holders, Certificate of Waiver special provisions are the operating envelope the gate checks before dispatch. Proposed Part 108 record families stay on the Part 108 recordkeeping software page.

01

Aircraft and configuration

What is installed, accepted, current, and airworthy for this mission. Ledger freezes that state as a snapshot.

02

Personnel and currency

Who is assigned, trained, current, authorized, and rested for each required operational role.

03

Area and route intent

Where the operation is approved to occur, which volume applies, and what path the team intends to fly.

04

Risk and safety findings

Which hazards, incidents, procedures, and open blockers affect this release.

05

Mission record and evidence

What proof will exist after landing, and which source records support it.

How it works

Record. Check. Release. Prove.

One loop runs under each mission. It runs the same way each time.

  1. 01

    Record

    Connect missions, configuration snapshots, components, credentials, checklists, findings, and flight logs in one system.

  2. 02

    Check

    Run deterministic checks against Part 107 or Part 135 workflows today. Run proposed Part 108 checks beside them in shadow mode.

  3. 03

    Release

    Ledger turns the five readiness areas into a release decision before the aircraft flies. Findings show what failed and how to close it.

  4. 04

    Prove

    Create human-attested evidence packs for regulators, insurers, partners, and customer legal teams.

Release control

A model must not make the release call.

Ledger findings cite the regulation or internal control. Run the same check against the same records and you get the same answer. A release decision that you explain to a regulator must be reproducible, so AI does not evaluate release.

  • No hallucinated compliance Findings cite rules or internal controls.
  • No folder archaeology Evidence starts from source records.
  • No compliance theater A person keeps accountability for release.

Shadow mode

Use shadow mode while Part 108 remains proposed.

Proposed Part 108 checks run beside live Part 107, Part 135, or waiver operations. Each check runs. Each finding opens. Nothing blocks the dispatch release until you choose to enforce it. Part 108 recordkeeping software maps those proposed checks, including a Part 108 evidence pack under drafted §108.45. Waiver holders can read the Part 107 BVLOS waiver to Part 108 brief for the three transition paths.

Shadow only Finding open Ready to enforce

What Ledger covers

One operational record for each 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

Why now

Part 108 creates the timetable. Drones are the first proof case.

If the final rule lands near the NPRM, operators that enter Part 108 will inherit broad recordkeeping and reporting duties on the same regulatory timetable. The market does not need a new reason to value proof. The operating authority creates the need. Waiver holders can map a Part 107 BVLOS waiver to Part 108 path in the transition brief before the final rule is published.

Demand by rule

Every scaled operator faces the same class of question.

Show that this aircraft, crew, route, and operating state met the rules that governed this flight.

The wider category

The same proof problem follows regulated autonomy.

We expect ground robots, autonomous vehicles, and other physical systems to face the same demand: show that the machine operated within its rules. Drones are the first market where Lightcone can build that trust infrastructure.

What must be true: the final rule must stay near the proposed accountability model, operators must prepare before enforcement forces the issue, and Ledger must keep its adjudication layer ahead of telemetry platforms that move up the stack.

Part 108 remains proposed. The FAA reopened a limited comment period in January 2026, and the final requirements can change.

See it in practice

Four moments where the record matters.

Day of flight

Before launch, your team opens the mission, checks the configuration snapshot, reviews open findings, and assigns any required action.

  1. Open the mission and check the configuration snapshot.
  2. Check for open findings against the aircraft, operator, or configuration.
  3. Clear each finding or assign the required action before launch.
  4. Fly with the evidence record already started.
Configuration snapshot Open findings Release decision Evidence trail