Launching Q1 2027. Join the waitlist for early access.
AA
AviationAlley
Back to Part 107

Part 107 · Fleet & flights

Drone fleet registry

Every drone sits on a clean row with its FAA registration number, MTOW, Remote ID flag, payload, and battery count, so the fleet is one auditable list rather than a spreadsheet. It replaces the drone inventory kept without an audit trail.

Join the waitlistRequest a demo

Launching the first quarter of 2027.

sUAS fleet
Part 107 · registry + flight records
FAA reg #ModelMTOWRemote ID
FA3X8K2M30T1,987 gCompliant
FA9D11QM3E915 gCompliant
FA77B0LEvo II1,250 gMissing
Flight FP-2207 · Class CLAANC # recorded
KPDX 4 nm · altitude cap 200 ft AGL · 107.205 night waiver applied
Remote ID flagged · waivers + LAANC # captured per flight

Illustrative — every screen reflects your own data.

Who it's for

Part 107 commercial drone operators — from a single-drone shop to a growing sUAS fleet — who need one auditable fleet list to confirm what's airworthy before a job, rather than a spreadsheet nobody is sure is current.

What it replaces

The drone inventory spreadsheet kept without an audit trail, and the side list someone rebuilds before each job to remember what's grounded.

What drone fleet registry gives you

  • FAA registration #, MTOW, payload, and battery count per drone
  • Remote ID flag on every row
  • One auditable list, not a spreadsheet

One auditable fleet row per drone

As planned, every drone would sit on a clean row with its FAA registration number, MTOW, payload, and battery count, so the fleet is one auditable list instead of a spreadsheet nobody is sure is current. When a new aircraft is registered it goes on the same list, and the registry stays the single place the operation looks before a job to confirm what's airworthy and what's grounded.

  • FAA registration #, MTOW, payload, and battery count per drone
  • Remote ID flag on every row
  • One auditable list, not a spreadsheet
sUAS fleet
Part 107 · registry + flight records
FAA reg #ModelMTOWRemote ID
FA3X8K2M30T1,987 gCompliant
FA9D11QM3E915 gCompliant
FA77B0LEvo II1,250 gMissing
Flight FP-2207 · Class CLAANC # recorded
KPDX 4 nm · altitude cap 200 ft AGL · 107.205 night waiver applied
Remote ID flagged · waivers + LAANC # captured per flight

A record of the fleet — not a telemetry link

This is built as a record the operator maintains, not a flight-control or data-ingest connection to the aircraft. Battery count and aircraft details would be entered, not pulled from DJI, AirData, or any telemetry feed, and opening a drone's row would surface the flights and waivers tied to it. The intent is a durable fleet record the operation can inspect, never a live link to the drone.

  • A record you maintain — not ingested from a telemetry feed
  • Open a drone's row to see its flights and waivers
  • A fleet record, not a flight-control tool
Fleet
Per-tail utilization · inspection clock · AD posture
Tails
18
Insp ≤ 14d
3
AOG
1
TailType · 30dNextStatus
N700AOB737-800 · 142 hin 38 hAirworthy
N701AOA320 · 118 hin 12 dInsp soon
N702AOB737-700 · —open ADAOG
30 / 90 / 365-day hours · ADs, SBs, and life-limited parts per tail

How an operator uses this

A Part 107 operator keeps the whole fleet on one screen — each drone a row with its FAA registration number, MTOW, payload, and battery count, instead of a spreadsheet that nobody is sure is current. When a new aircraft is registered it goes on the same list, and the registry stays the single place the operation looks before a job to confirm what's airworthy and what's grounded. It's a record of the fleet, not a telemetry or flight-control link to the aircraft.

Illustrative — every screen reflects what's in your own data, nothing more.

How it works

Drone fleet registry, step by step

  1. Add each drone with its FAA registration number, MTOW, payload, and battery count.

  2. Set the Remote ID flag so any non-compliant aircraft is visible on the list.

  3. Open a drone's row to see its details and the flights and waivers tied to it.

  4. Work from the registry as the one auditable fleet list — no side spreadsheet.

Questions

Drone fleet registry — frequently asked

What does each drone record hold?

The FAA registration number, MTOW, Remote ID flag, payload, and battery count — one clean, auditable row per aircraft instead of a spreadsheet kept without an audit trail.

Does it pull battery or flight data from the drone automatically?

No. The registry is a record you maintain — battery count and aircraft details are entered, not ingested from DJI, AirData, or any telemetry feed. It's a fleet record, not a flight-control or data-ingest tool.

Keep exploring

Other features in Part 107

All of Part 107
Fleet & flights

Flight planning + records

Airspace class (B/C/D/E/G), nearest ICAO, recorded LAANC authorization #, altitude cap, and post-flight notes.

Deep dive
Fleet & flights

107.205 waiver vault

BVLOS / swarms / edge-case night & OOPP waivers with FAA #, scope, expiry, and document.

Deep dive
Fleet & flights

Remote ID flag

Per-drone Remote ID compliance flag; the registry surfaces any drone without it.

Deep dive

Every Part 107 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.

See the backbone

See drone fleet registry on your operation.

It's part of the Part 107 workspace. Request a demo or join the waitlist.

Join the waitlistRequest a demo