Part 107 · Fleet & 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.

Join the waitlist Request 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 operators who fly jobs in controlled airspace and need each operation to leave a durable, inspectable trail — airspace class, ICAO, the LAANC number they obtained, altitude cap, and notes — instead of a flight that lives only in someone's memory.

What it replaces

Flight records that exist only in someone's memory, and the loose notes a job leaves behind with no airspace class, altitude cap, or applied-waiver trail.

What flight planning + records gives you

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

A LAANC number recorded — never requested for you

As designed, the operator would obtain a LAANC authorization from their USS provider exactly as they do today, then record it here — the authorization number and altitude cap are written down on the flight, not requested or filed by the platform. Direct API integration with a LAANC USS provider is framed as a per-customer add-on, not a built-in. The LAANC authorization is recorded here; it is never automated.

LAANC authorization number recorded — not requested for you
Airspace class (B/C/D/E/G), nearest ICAO, altitude cap, and notes
A flight record that doesn't live only in someone's memory

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

An inspectable trail per operation

Each flight record would capture its airspace class, nearest ICAO, the recorded LAANC authorization number, the altitude cap, the waivers that applied, and post-flight notes added afterward. The aim is that each operation leaves a complete, auditable record an inspector can read, rather than a flight reconstructed from memory after the fact.

Airspace class, nearest ICAO, and altitude cap on the record
Tag which waivers applied to the operation
Post-flight notes make the flight a complete record

Compliance

Part 142 · Part 60 NSP · instructor currency

42 compliant 3 due soon 1 overdue

RequirementDueStatus

14 CFR Part 142 OpSpecsMar 2027Compliant

Part 60 NSP — B737 FFS #1in 11 daysDue soon

CFI currency — Okafor8 days agoOverdue

Aircraft eval renewal — A320in progressIn progress

Facility safety inspectionJan 2027Compliant

Weekly digest to admins · time-limited FAA evaluator access

How an operator uses this

Before a job, the operator obtains a LAANC authorization from their USS provider as they normally would, then records the flight here — airspace class, nearest ICAO, the authorization number, the altitude cap, and which waivers applied. After the flight, post-flight notes go on the same record, so each operation leaves a durable, inspectable trail instead of a memory. The LAANC authorization is written down here; it is never requested or filed for you.

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

How it works

Flight planning + records, step by step

Obtain your LAANC authorization from your USS provider, as you do today.
Create the flight record with its airspace class, nearest ICAO, and altitude cap.
Enter the LAANC authorization number you received and tag the waivers that applied.
Add post-flight notes so the flight is a complete, auditable record afterward.

Questions

Flight planning + records — frequently asked

Does AviationAlley file or request the LAANC authorization for me?

No. The LAANC authorization is recorded, not automated. You obtain it from your USS provider and enter the authorization number and altitude cap; the flight keeps that record. Direct API integration with a LAANC USS is a per-customer add-on, not a built-in.

What does a flight record capture?

Airspace class (B/C/D/E/G), the nearest ICAO, the recorded LAANC authorization number, the altitude cap, the waivers that applied, and post-flight notes — so the flight is inspectable rather than living only in someone's memory.

Keep exploring