Part 107 · Fleet & flights
Remote ID flag
Each drone carries a Remote ID compliance flag, and the registry surfaces any aircraft that doesn't have it set — so a non-compliant drone is visible rather than assumed. It replaces tracking Remote ID status in your head.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
What remote id flag gives you
- A Remote ID compliance flag per drone
- The registry surfaces any drone without it set
- A non-compliant drone visible rather than assumed
How an operator uses this
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 — and the registry surfaces any aircraft without its Remote ID flag set. Each flight records its airspace class, nearest ICAO, the LAANC authorization number you obtained from your USS provider, the altitude cap, and post-flight notes; the LAANC authorization is recorded here, not requested for you. Each 107.205 waiver — night, operations over people, BVLOS, multiple aircraft, or other operating limits — is a row with its FAA number, scope, expiry, and stored document, and flights record which waivers applied.
Illustrative — every screen reflects what's in your own data, nothing more.
Keep exploring
Other features in Part 107
Drone fleet registry
FAA registration #, MTOW, Remote ID flag, payload, and battery count per drone.
Deep diveFlight planning + records
Airspace class (B/C/D/E/G), nearest ICAO, recorded LAANC authorization #, altitude cap, and post-flight notes.
Deep dive107.205 waiver vault
Night / OOPP / BVLOS / swarms / operating-limit waivers with FAA #, scope, expiry, and document.
Deep diveEvery Part 107 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee remote id flag on your operation.
It's part of the Part 107 workspace. Request a demo or join the waitlist.