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

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 holding a 107.205 waiver — typically for BVLOS, multiple-aircraft operations, or a night/over-people case outside direct authorization — who need to produce the right waiver during an inspection without hunting for a file on a USB stick.

What it replaces

The waiver PDFs on a USB stick nobody can find during an inspection, and the disconnected pile of paper that never links back to the flight it authorized.

What 107.205 waiver vault gives you

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

Every 107.205 waiver as a stored row

As planned, each 107.205 waiver the operation holds — typically for BVLOS, multiple-aircraft operations, or a night/over-people case that falls outside direct authorization under 107.29 / Subpart D — would be a row with its FAA waiver number, scope, expiry, and the scanned document attached. Each waiver is held as a record, so the authorization an operation relies on can be pulled up during an inspection instead of searched for across a USB stick.

BVLOS, swarms, or the narrower night/OOPP cases that need a waiver
FAA waiver #, scope, expiry, and stored document per row
Pulled up during an inspection without hunting for the file

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

Waivers linked to the flights they authorized

When a flight is recorded, the operator would tag which waivers applied, so the authorization for a given operation is traceable on the flight record rather than recalled later. The intent is to link the waiver vault and the flight record together — one authorization trail — rather than leave two disconnected piles of paper.

Flights record which waivers applied
Authorization traceable on the flight, not recalled
Vault and flight record linked, not two piles of paper

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

Each 107.205 waiver the operation holds — typically for BVLOS, multiple-aircraft operations, or a night/over-people case that doesn't qualify for direct authorization under 107.29 or Subpart D — is a row with its FAA waiver number, scope, expiry, and the scanned document attached. When a flight is recorded, the operator tags which waivers applied, so the authorization for a given operation is traceable rather than recalled. It replaces the waiver PDFs on a USB stick that nobody can find during an inspection.

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

How it works

107.205 waiver vault, step by step

Add each active 107.205 waiver with its FAA waiver number, scope, and expiry.
Attach the scanned waiver document to the row so it's stored in one place.
When recording a flight, tag which waivers applied to that operation.
Pull up the waiver during an inspection without hunting for the file.

Questions

107.205 waiver vault — frequently asked

Which waivers can the vault hold?

Any 107.205 waiver — most commonly BVLOS or multiple-aircraft operations, since most night operations and operations over people (OOPP) are authorized directly today under 107.29 / Subpart D rather than by waiver — each as a row with its FAA waiver number, scope, expiry, and stored document.

How do flights connect to waivers?

When you record a flight you tag which waivers applied, so the operation's authorization is on the flight record. The waiver vault and the flight record are linked rather than two disconnected piles of paper.

Keep exploring