Fleet compliance & firmware control
Track airframe firmware and configuration, catch drift from the approved baseline, and keep grounded aircraft grounded.
Fleet Compliance is the airworthiness record for an eligible organization's fleet: what firmware and configuration an airframe runs, whether it matches the approved baseline, and whether it may be scheduled.
Open Fleet → Firmware. Firmware is a Fleet section, not a separate top-level destination.
What it tracks
For each organization airframe:
- Identity: serial, chassis, and FAA registration with expiry where provided.
- Components: flight controller, ESC, video transmitter, receiver, motors, GPS, and other installed components.
- Configuration: versioned settings captures so changes can be reviewed.
- Lifecycle: active, maintenance, grounded, or decommissioned, with a reason when grounded.
Approved baselines and drift
A baseline is the known-good configuration approved for an airframe or scope. New captures are compared against it and show added, removed, or changed settings. Differences are classified as Critical safety, Operational, or Informational.
Critical safety drift grounds the airframe until the issue is resolved. Re-capturing a configuration that matches the approved baseline can clear stale drift when no other blocker remains.
Sign-off and directives
Firmware flashes and component changes can create a work order with an ordered sign-off chain: technician attestation, evidence upload, safety review, and final release. Safety officers can publish directives that apply to matching fleet hardware and create grounding blockers.
The Fleet views
- Fleet compliance: airframe status, grounded count, drift, work orders, and component releases.
- Digital twin: one airframe's component tree and configuration history.
- Drift queue: differences by severity and their resolution state.
- Work orders: role-aware sign-off progress.
- Directives: active and retired fleet notices.
Scheduling interlock
A grounded airframe cannot be booked through Scheduling & Dispatch. The booking response includes the blocker reason when available, such as critical drift, a directive, or an open work order.
Fleet Compliance is available on Enterprise Solo and Enterprise. A configuration record supports your operating controls; it does not replace physical inspection or local aviation requirements.