FAA's Part 108 Would Open Routine BVLOS Drone Flights. The Records Are the Work.

The FAA's proposed Part 108 rule would end the case-by-case waiver most commercial drone operators need to fly beyond the pilot's line of sight. The shift operators will feel is on the other side of the rule: the daily documentation, pilot-currency, and maintenance records that turn a one-off flight into a compliant program.

Released as a Notice of Proposed Rulemaking in the Federal Register on August 7, 2025, Part 108 would create a standardized framework for routine beyond-visual-line-of-sight (BVLOS) drone operations, the kind of flights where the pilot cannot see the aircraft and has to rely on instruments, observers, or onboard systems to keep it safe (Federal Register filing).

Today, most commercial BVLOS flights happen through a waiver application. An operator files evidence the flight is safe, waits, and gets permission for a defined scope. Part 108 would replace that workflow with a standing authorization, the same way Part 107 created a standard license for small commercial drones in 2016. The waiver-by-application model was built for exceptions. The proposed rule is built for routine work.

Wire coverage will lead with the standing authorization. The operators who have read the proposed rule closely treat it as the smaller half of the shift.

The larger shift is what happens after the rule lands. AirData, a drone operations and fleet management platform that read the proposed rule through an operator's lens, calls documentation "the biggest day-to-day change." A waiver is a one-time document you assemble to ask for permission. A compliant BVLOS program is a continuous set of records you maintain to keep that permission. Different problem, different discipline.

The records are not new to the industry. Maintenance history, pilot currency (proof each pilot has logged the required recent flight hours and training to stay current), operational safety documentation, and risk management procedures are already on the FAA's checklist for any BVLOS waiver. What changes under Part 108 is who has to keep them and how often they get reviewed. The same records that used to live in a waiver packet become standing program artifacts: pilot logbooks updated continuously, maintenance entries logged per flight or per inspection cycle, risk assessments refreshed whenever the operation adds aircraft, locations, or mission profiles.

For a small operator flying a handful of aircraft out of one site, that load is manageable. A spreadsheet and a shared folder can carry it. The break point shows up as the program scales. Add a second aircraft and a second pilot and the maintenance log stops being one file. Add a third site and the risk assessment is no longer a single document. Add a fourth pilot and the currency tracking becomes a quarterly job. Each step is incremental. The cumulative effect is that the record system that worked for a five-drone program collapses under a fifty-drone one.

Standardization lowers the entry barrier for new operators by removing the waiver queue. It raises the documentation floor for everyone who enters. The operators who arrive at the final rule with a record system already designed for growth will scale into the new authority cleanly. The ones who arrive with a waiver-era spreadsheet will be rebuilding their compliance stack the day the rule takes effect.

The FAA's Part 108 NPRM is posted to the agency's newsroom and the public comment period has closed. The agency has not announced a final-rule date. The DroneLife summary published this week treats the rule as a regulatory milestone. The operators already running scaled BVLOS programs, the cohort AirData describes, are more interested in the next eighteen months of record-keeping investment than in the rule's passage date.

Earlier coverage from the Commercial Drone Alliance's regulatory summit made the same point from a different angle: the operators pushing hardest for the rule were always the ones who already had the back office to use it.