UAS Sustainment Workbench

Readiness board for a small civil unmanned aircraft fleet, built from flight logs.

What this page is

The workbench is a tool an operator runs on their own machine to keep the maintenance and operations records of a small civil unmanned aircraft fleet. It reads PX4 and ArduPilot flight logs, counts what each aircraft and each part has used, and says what is due and why.

This page is its output for a demo fleet of nine aircraft: seven synthetic, two from public logs. CI builds it from the code on main, which can hold changes not yet released.

It is for an operator who must keep maintenance and operations records, for example under UAS.SPEC.050(1)(g) of Regulation (EU) 2019/947: (ii) maintenance activities and (iii) operations information, including unusual occurrences, each kept at least 3 years. It holds no (g)(i) training records. Further down are one sample "Draft records summary for the operator's own review" and the same summary for the whole fleet.

It does not certify airworthiness or release an aircraft to service, and it takes each entry at the word of the person who made it. How to try it in a few minutes, and LIMITS.md with what each part cannot tell, are in the repository.

Loading fleet.json…

Due soon and overdue

Findings: flight the logs do not cover

Each line compares consecutive logs of one aircraft with the autopilot's own lifetime counter. Flight found this way counts toward component life.

Flights logged while the records show the aircraft grounded

Fleet

AircraftDataStatusDueAutopilot FlightsFlight hoursFindings

Status is computed from each aircraft's maintenance record, its components and its flights; every state but serviceable says why. Click an aircraft for its due list, flights and reconciliation detail. Values a log cannot support are shown as unknown with the reason.

Draft evidence pack for OSO #03: one sample

Draft records summary for the operator's own review: one sample

Assistant: recorded runs, not live