A fleet registry and flight records the FAA can inspect.
Fleet registry, flight planning, Remote ID tracking, waiver records, and post-flight logs — built so a single-drone operator or a growing sUAS fleet keeps a clean, auditable record.
Launching the first quarter of 2027.
Jump to a feature
Tap any chip to jump to its section below.
+9 more supporting features lower on the page
Inside the Part 107 workspace
01Fleet & 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.
Replaces: the drone inventory kept without an audit trail
- FAA registration #, MTOW, payload, and battery count per drone
- Remote ID flag on every row
- One auditable list, not a spreadsheet
Illustrative — every screen reflects your own data.
02Fleet & flights
Flight planning + records
Each flight records its airspace class, nearest ICAO, the LAANC authorization number you obtained, the altitude cap, and post-flight notes. The LAANC authorization is recorded here — you enter the authorization number you received from your USS provider; the platform doesn't request the authorization for you. It replaces flight records that exist only in someone's memory.
Replaces: flight records that exist only in someone's memory
- Airspace class (B/C/D/E/G), nearest ICAO, altitude cap, and notes
- LAANC authorization number recorded — not requested for you
- A flight record that doesn't live only in someone's memory
Illustrative — every screen reflects your own data.
03Fleet & flights
107.205 waiver vault
Most night operations (107.29 lighting + training) and operations over people (the Subpart D aircraft categories) are authorized directly today, not by waiver. A 107.205 waiver is the narrower fallback — typically for BVLOS, multiple-aircraft operations, or a night/over-people case that doesn't qualify for direct authorization — and each one is a row with its FAA waiver number, scope, expiry, and the stored document; flights record which waivers applied. It replaces waivers on a USB stick.
Replaces: waivers on a USB stick
- BVLOS, swarms, or the narrower night/OOPP cases that need a waiver
- FAA waiver #, scope, expiry, and stored document per row
- Flights record which waivers applied
Illustrative — every screen reflects your own data.
04Fleet & 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.
Replaces: tracking Remote ID status in your head
- A Remote ID compliance flag per drone
- The registry surfaces any drone without it set
- A non-compliant drone visible rather than assumed
Illustrative — every screen reflects your own data.
In every operation
The platform backbone, under every Part
The platform-wide backbone — the same under every FAR Part.
Auto-fills from completed flights, manual entry, and ForeFlight CSV import/export.
Certificates, ratings, medicals, and type ratings with auto-expiry alerts and document storage.
Priority/status/assignee work orders, parts with reorder thresholds, vendors, and purchase orders.
Every requirement on a Compliant → Due-Soon → Overdue timeline with a weekly admin digest.
Utilization, currency, and activity KPIs with CSV export.
Every mutation recorded with actor, entity, and timestamp — searchable and exportable.
Read-only links for FAA/POI/external auditors that expire automatically — no shared logins.
Bearer-token REST API (scoped) and HMAC-signed outbound webhooks for HRIS, ERP, and ops integrations.
Tenant isolation, role-based access, per-employee surface restrictions, TOTP 2FA, and GDPR data export/erasure.
Today
What's slowing you down
- Fleet tracked in a spreadsheet with no audit trail
- Waivers and Remote ID status on a USB stick
- Incidents reported over email with no record
With AviationAlley
What changes
- Every drone on a clean row — registration, MTOW, Remote ID, payload
- Each flight captures airspace class, LAANC authorization #, and altitude cap
- Waivers in a vault with FAA waiver #, scope, and expiry
Recommended for Part 107
Starter plan
Unlimited seats · priced to your fleet
One FAR rule set, unlimited seats. Right-sized for single-rule schools and small operators.
- One operation module included
- Unlimited staff seats
- Public REST API + webhooks
- White-label branding
- Email + community support
Frequently asked questions
Part 107 — common questions
Does AviationAlley request LAANC authorizations for me?+
No — LAANC authorizations are recorded, not automated. You enter the authorization number and altitude cap you obtained from your USS provider, and the flight keeps that record. Direct API integration with a LAANC USS provider is a per-customer add-on, not a built-in.
Does it track Remote ID and 107.205 waivers?+
Yes. Every drone carries a Remote ID flag and the registry surfaces any drone without it, and each active 107.205 waiver is a row with the FAA waiver number, scope, expiry, and stored document — flights record which waivers applied.
What does the Part 107 operation cover today?+
The fleet registry, flight planning and records (with recorded LAANC and applicable waivers), the 107.205 waiver vault, and Remote ID flags — plus the platform-wide logbook, credentials, reporting, and audit trail. It's a clean, auditable record for a single-drone operator or a growing sUAS fleet; it isn't a flight-control or mapping tool.
Built for Part 107.
See it on your operation. Request a demo or join the waitlist.