What was true?
Bring the current aircraft, crew, route, and approval information together.
Operational proof for UAS fleets
Check the flight before release. Keep the proof after landing.
Ledger brings aircraft, crew, route, findings, and approvals into one record before launch. Your team can make a repeatable release decision and keep the supporting evidence connected after landing. Use it under Part 107 or Part 135 today. Run proposed Part 108 checks in shadow mode. The BVLOS compliance software overview shows that release loop.
Built by a commercial pilot. Deterministic checks. Human release decisions.
Why connected records matter
A flight is more than a flight log.
It depends on the aircraft, crew, route, operating conditions, procedures, and approvals. Those facts need to stay connected to the decision they supported.
Who made the decision, and why?
Record the responsible person's decision and the facts that supported it.
Can you show the same record later?
Preserve changes and source evidence in a history that another person can review.
Operational facts
+
Human decision
+
Supporting evidence
One connected record
Ledger is designed to keep the facts, human decisions, and supporting evidence connected throughout the life of a flight.
Why this exists
Autonomy at scale creates a liability problem before it creates a technology problem.
As drafted, Part 108 greatly expands the records and reports that BVLOS operators keep. Even with automated flight ops, operators would still have the responsibility to explain and replay later why a mission was allowed to fly.
The operator must answer for the flight.
The record can span the flight, aircraft, people, maintenance, training, reports, and operating documents.
Separate tools lose the reason behind the decision.
Telemetry and logbooks can hold useful facts. The operator still needs to connect those facts to the rules and procedures used that day.
The record must survive the question years later.
A later review needs the source records, the applicable rule or procedure, and the release decision. Missing context makes a clear answer harder.
Regulated autonomy runs on proof. Ledger is designed to keep the operational work and its evidence connected.
Primary references: proposed Part 108 and FAA electronic-record guidance in AC 120-78B. Ledger applies AC 120-78B electronic records principles as design guidance, not as a mandate for UAS operators.
From plan to proof
One record moves with the operation.
The work changes as the flight moves forward. The record stays connected.
One flight depends on
- Aircraft + crew
- Weather + airspace
- Systems + providers
- Authority + procedures
-
01
Plan
Set the aircraft, crew, route, conditions, procedures, and approvals.
-
02
Release
Review the current facts. Record the responsible person's decision.
-
03
Fly
Capture actual times, handoffs, deviations, and source records.
-
04
Review
Compare new evidence. Correct the record without erasing its history.
-
05
Prove
Prepare a fixed record set and give a reviewer scoped access.
Connected operation record
Current facts, sources, decisions, and full history
- Current state
- What is true now
- Change history
- What changed
- Accountability
- Who decided and why
See it in practice
Four moments where the record matters.
These scenarios are simulated. The operating loop is the product.
Simulated mission record
Day of flight
Release held
Before launch, your team opens the mission, checks the configuration snapshot, reviews open findings, and assigns any required action.
- Open the mission and check the configuration snapshot.
- Check for open findings against the aircraft, operator, or configuration.
- Clear each finding or assign the required action before launch.
- Fly with the evidence record already started.
The decision boundary
The system can prepare the record. A person releases the flight.
Ledger is designed to return the same result when a check runs against the same records. It can surface a finding and cite the rule or company procedure. The operator keeps the decision.
- Deterministic checks
- Human release decisions
- Recorded reasons for overrides
Part 108 is still proposed. Shadow mode is designed to show potential gaps without treating the proposal as a final requirement. Part 108 recordkeeping software maps the proposed record families, including a Part 108 evidence pack under drafted ยง108.45.
What Ledger covers
One operational record for the work behind every release.
Source facts flow into the release decision. The decision and its evidence stay connected for later review.
Dispatch release + Route intent
Airworthiness + Configuration + Associated elements
Roles + Training + Currency
Reports + SMS findings + Source watch
Release record
Facts checked
Decision recorded
Changes preserved
Reviewable output
Evidence pack
Audit history and scoped reviewer access.
Built for operational scale
For teams that have outgrown one pilot and one spreadsheet.
Ledger is for commercial UAS teams with several aircraft, pilots, and reviewers. It supports utility inspection, corridor patrol, energy, survey, and similar operations under Part 107, Part 135, or a BVLOS waiver.
- Team
- Five to fifty people
- Work
- Repeatable commercial operations
- Need
- Shared records without a large compliance staff
If one pilot and one spreadsheet still cover the whole program, you probably do not need Ledger yet.
Part 108 transition scenarios, mapped.
Part 108 transition paths are still unresolved. We are mapping what existing BVLOS waiver holders could face under the final rule, and what to prepare under each path. Read the Part 107 BVLOS waiver to Part 108 transition brief.