FAA Part 108: what the BVLOS rule means for public safety drone programs
FAA Part 108 is the rulemaking that turns beyond-visual-line-of-sight drone flight from a case-by-case waiver into a standing, certificated operation. The final rule was expected in spring 2026 with implementation 6–12 months after publication, and it is what makes drone-as-first-responder work at municipal scale.
If your agency runs, or wants to run, a drone-as-first-responder program, Part 108 is the most consequential FAA rulemaking of the decade. It takes beyond-visual-line-of-sight (BVLOS) flight, which today requires a waiver argued case by case, and turns it into a normal, certificated category of operation. That single change is what makes DFR workable at municipal scale.
Here is what the rule is, what it replaces, what it changes for public safety programs, and what it leaves squarely on the agency's plate.
What is FAA Part 108?
Part 108 is the FAA's rule for routine BVLOS operations. The notice of proposed rulemaking was published in August 2025, drew more than 3,000 comments by the time the comment period closed that October, and the final rule was expected in spring 2026, with implementation generally anticipated 6 to 12 months after publication. Confirm the current status directly with the FAA; rulemaking timelines move.
The core shift is from exception to rule. Today, flying a drone beyond the pilot's sight requires special permission. Under Part 108, an operator that meets the rule's requirements (aircraft, training, operational standards) flies BVLOS as a matter of course, the way Part 107 normalized line-of-sight commercial flight in 2016.
What does Part 108 replace?
Public safety agencies currently reach BVLOS through one of two doors, both narrow:
| Today | How it works | Under Part 108 |
|---|---|---|
| Part 107 waiver | Agency petitions the FAA case by case; approval can take months and is specific to one operation profile | Standing rule: qualify once, operate routinely |
| Public aircraft COA | Certificate of Waiver or Authorization under public aircraft rules; flexible but administratively heavy | A normalized civil pathway most programs can use instead |
The waiver regime worked for pioneers willing to spend a year on paperwork. It does not scale to a thousand mid-sized agencies. That is the gap Part 108 closes.
Note that existing waivers and COAs do not vanish on publication day. Agencies operating under current authority keep operating; the question is whether to transition to the Part 108 framework when it becomes available, and for most programs the answer will be yes: a standing rule is easier to staff, easier to audit, and easier to explain to oversight bodies than a stack of expiring exceptions.
What changes for DFR programs?
Chula Vista proved the model under waivers: drones launched on 911 calls, response times cut roughly in half, and about 90 percent of the city covered from four launch sites. Every agency that wanted to follow had to re-argue the same case with the FAA individually.
Under Part 108, that changes in practical ways:
- Predictable authority. Programs are built against a published standard instead of a negotiated waiver, which is easier to plan, budget, and defend to council.
- Coverage by design. Launch sites can be placed for citywide coverage from day one rather than expanding waiver by waiver.
- Lower pilot overhead. The rule contemplates operations without visual observers stationed along the route, which is the single largest staffing cost in waiver-era BVLOS.
- A bigger vendor field. A standing rule gives dock, aircraft, and detect-and-avoid vendors a stable target, which tends to lower prices and widen choice.
What Part 108 does not change
The rule normalizes flight. It does not run your program. Everything that makes DFR defensible in front of a city council remains agency work:
- Local policy. When drones launch, what calls qualify, how long video is retained: all local decisions, all on you.
- Privacy and transparency. Community engagement, published flight logs, and use policy are what keep a program politically durable. The FAA does not provide them.
- Video distribution. Part 108 governs the aircraft, not the picture. Getting the live feed to the people who need it, namely command, patrol, and the watch commander, is an architecture decision the agency still has to make.
More aircraft airborne moves the bottleneck from flying to seeing
Here is the second-order effect worth planning for now. Under waivers, most agencies could keep one aircraft up at a time, and one feed is easy to watch. Under Part 108, a mid-sized city can plausibly have three or four aircraft airborne across simultaneous calls, plus a helicopter, fixed cameras, and a witness's phone.
That is the part of the stack agencies should pressure-test before the rule lands. BabbarOps exists for exactly this layer: live feeds from any aircraft over standard protocols (RTMP, RTSP, SRT) onto one shared wall that command and responding units open with a login: live-only, never stored, with no per-device licensing to scale as the fleet grows. Whatever tooling you choose, the test is the same: when four feeds are up at once, can the sergeant rolling to the scene see the right one?
What should agencies do before the rule takes effect?
- Track the rule, not the rumors. Watch the FAA's BVLOS docket directly. Publication starts the implementation clock, and early movers will set the procurement queue.
- Start the local groundwork now. Use policy, privacy framework, community engagement, and council briefings take longer than FAA compliance. None of it depends on the final rule text.
- Plan the program, not just the flight. Launch-site placement, staffing, training pipeline, and video distribution can all be designed against the proposed rule and adjusted at publication.
- Keep procurement flexible. Avoid locking the program to hardware or software that assumes the waiver-era world of one aircraft and one screen.
Part 108 is the rare regulation that expands what public safety aviation can do rather than constraining it. The agencies that benefit first will be the ones that treated the waiting period as build time.
Part 108 is the FAA rulemaking that normalizes beyond-visual-line-of-sight (BVLOS) drone operations, replacing the case-by-case waiver system with a standing rule. The proposed rule was published in August 2025, and the final rule was expected in spring 2026 with implementation generally anticipated 6 to 12 months after publication.
A Part 107 waiver is an exception granted case by case: each agency petitions the FAA individually, approval can take months, and it covers a specific operation profile. Part 108 is a standing rule: an operator that meets its requirements for aircraft, training, and operational standards flies BVLOS routinely without negotiating a waiver.
BVLOS authority is what lets a DFR program launch drones on 911 calls across a whole city from fixed sites. Chula Vista did it under waivers and roughly halved response times with about 90 percent city coverage from four launch sites. Part 108 makes that model available by rule instead of by exception, so agencies can plan citywide coverage and staffing against a published standard.
Part 108 governs flight authority, not program policy. Launch criteria, privacy safeguards, transparency, community engagement, video retention, and how live feeds are distributed to command and patrol all remain agency decisions. A program still needs local policy and a video architecture that the FAA rule does not provide.
If Part 108 will put more aircraft over your city, see how their feeds land on one shared picture for command and patrol.
FAA rules and rulemaking timelines change; this article is for general information and is not legal or regulatory advice. Confirm the current status of Part 108 and your agency's operating authority directly with the FAA. BabbarOps is an independent commercial product and is not affiliated with or endorsed by the FAA or any government agency.