FAA Part 108: The BVLOS Rule That Unlocks Drone Delivery at Scale

For nearly a decade, flying a drone beyond the operator's eyesight in the United States required something close to a special favor from the government: a case-by-case waiver from the FAA, negotiated operation by operation, route by route, sometimes taking a year or more to secure. Companies like Amazon, Wing, and Zipline built entire delivery businesses around a small number of these waivers, each one narrowly scoped to a specific aircraft, a specific service area, and a specific set of mitigations. Part 108 changes the premise. Instead of asking the FAA for permission every time, operators will be able to certify against a published rule and scale without renegotiating the basics each time they want to expand.

That shift — from bespoke exemption to standard framework — is the regulatory unlock that drone delivery, infrastructure inspection, and agricultural monitoring companies have been waiting for since routine beyond-visual-line-of-sight (BVLOS) flight became technically feasible. This post explains what Part 108 actually does, why the waiver system it replaces was such a bottleneck, and what it means for businesses building on top of autonomous flight.

What BVLOS means and why it was the hard problem

Visual line of sight (VLOS) is the default condition under existing FAA drone rules: the remote pilot, or a visual observer working with them, must be able to see the aircraft with unaided vision at all times. That constraint is fine for a real estate photographer circling a house or a farmer scanning a single field, but it caps the usable range of a drone at roughly the distance a human eye can track a small object in the sky — typically well under a mile, and often much less depending on terrain, weather, and drone size.

Beyond visual line of sight (BVLOS) operation removes that constraint. The aircraft flies further than the pilot can see, relying instead on onboard sensors, telemetry links, and increasingly, automated detect-and-avoid systems to stay safe. BVLOS is the operating mode that makes drone delivery over multiple miles, long-corridor infrastructure inspection, and wide-area agricultural spraying commercially viable. It is also the mode the FAA has historically treated with the most caution, because the core safety question — how does an uncrewed aircraft avoid a manned aircraft, a bird, or another drone when no human eye is watching it — did not have a settled regulatory answer.

Since 2016, the FAA's main tool for allowing BVLOS anyway was the Part 107 waiver process. Part 107 is the rule that governs most commercial small drone operations, and it includes provisions letting operators request waivers from specific restrictions, including the VLOS requirement, if they can demonstrate an equivalent level of safety through other means. In practice, that meant every operator wanting to fly BVLOS had to submit its own safety case, describing its aircraft, its detect-and-avoid approach, its operating environment, and its risk mitigations, and wait for FAA reviewers to evaluate it individually.

The waiver bottleneck

The waiver system was not designed to fail — it was a reasonable stopgap while the FAA and industry worked out what safe BVLOS operation actually looks like. But it created predictable problems as demand grew:

• Every operator started from zero. A waiver granted to one company for one route did not transfer to another company, or even to the same company for a materially different route. Each application required its own evidentiary package.
• Approval timelines were unpredictable. Waiver review could take many months to over a year, with no statutory deadline forcing a decision, which made it hard for companies to plan capital investment or hiring around a launch date.
• Scope was narrow by design. Waivers were typically tied to specific aircraft models, specific geofenced areas, and specific conditions (daylight only, rural terrain, low population density), which meant scaling to a new city or a new aircraft often meant reapplying rather than extending an existing approval.
• Small operators were disadvantaged. Well-resourced companies could afford the engineering and legal work to build a compelling waiver case; smaller drone operators and service providers frequently could not, which concentrated BVLOS capability among a handful of large players.
• It didn't scale with volume. A handful of pilots for a handful of companies were manageable. Thousands of operators wanting BVLOS authorization for delivery, inspection, and agricultural use cases were not going to move through a manual, individualized review process at the pace the market wanted.

The result was that BVLOS drone delivery existed in the US, but only in pilot-scale form — a small number of cities, a small number of operators, each running under a waiver that was, structurally, an exception rather than a rule.

What Part 108 actually establishes

Part 108 is the FAA's answer to that bottleneck: a standalone rule, rather than a waiver mechanism bolted onto Part 107, that sets out the conditions under which BVLOS operations are permitted by default, without a case-by-case FAA review of each operator's individual circumstances.

The core idea is to shift the FAA's role from adjudicating one-off exceptions to defining a performance-based standard that any qualifying operator can certify against. That means publishing acceptable means of compliance for the hardest technical problems in BVLOS flight — most importantly, how an uncrewed aircraft detects and avoids other air traffic when there's no pilot watching the sky — and then letting operators demonstrate their systems meet that standard, rather than negotiating bespoke terms each time.

Conceptually, Part 108 addresses several pieces that the waiver system handled inconsistently:

The practical effect is that BVLOS shifts from being a privilege granted sparingly to a class of operation that a much wider range of companies can plan around, provided they invest in the aircraft, software, and safety systems the rule requires.

Detect-and-avoid is the crux

It's worth dwelling on why detect-and-avoid (DAA) sits at the center of this rule. A human pilot flying VLOS is, functionally, the collision-avoidance system — they see a hazard and steer around it. Remove the human's eyes from the loop and something else has to do that job: onboard sensors like radar or electro-optical cameras, cooperative systems that let aircraft broadcast their position to each other (comparable to transponders on manned aircraft), or ground-based surveillance that feeds hazard data back to the drone in real time.

Different DAA approaches suit different environments. A delivery drone flying a fixed suburban corridor at low altitude faces a different hazard profile than an inspection drone flying along a rural transmission line at higher altitude, which is part of why a single rigid rule was hard to write and why Part 108 leans on acceptable-means-of-compliance frameworks rather than mandating one specific technology — systems that manufacturers increasingly validate through sim-to-real testing before flying certification routes.

Why it matters now

The significance of Part 108 is less about a single new capability and more about what it replaces. Before this rule, every BVLOS drone delivery program in the US — from grocery delivery pilots to medical supply drops to industrial inspection routes — operated under an individually negotiated exemption from the general rule that pilots must keep their aircraft in sight. That approach worked for proving the technology in controlled pilots, but it was never going to support an industry with thousands of operators and tens of thousands of daily flights.

Replacing case-by-case waivers with a standard framework is the regulatory equivalent of moving from bespoke permits to a building code: instead of asking a regulator to bless every individual project, you build to a published standard and self-certify compliance, with the regulator auditing rather than pre-approving each instance. That is the structural change that lets an industry go from dozens of active BVLOS operations to potentially thousands, because the marginal cost of adding a new operator or a new route drops sharply once the underlying safety case has already been established by the rule itself rather than by each applicant.

Benefits of FAA Part 108

Predictable approval instead of open-ended review

Under the waiver system, an operator could not reliably say when, or whether, approval would arrive. That made it hard to raise capital, sign customer contracts, or hire ahead of a launch. Certifying against a published standard turns approval into a project with known requirements, so timelines and budgets can be planned. For an industry that has spent years waiting on individual reviews with no deadline, that predictability may matter more than any single technical change in the rule.

Approvals that scale across routes and fleets

Waivers were tied to specific aircraft, areas, and conditions, so expanding to a new city or a new model often meant reapplying. A standard that operators certify against is designed to apply across fleets and routes once met. Adding a new corridor becomes an operational decision backed by an existing compliance case, rather than a fresh regulatory negotiation that might take a year.

A realistic entry path for smaller operators

Building a compelling waiver case took engineering and legal resources that mostly large companies could afford, which concentrated BVLOS capability among a few players. With a published standard, a smaller operator knows what it has to build and can compete on execution rather than on its ability to fund an open-ended application process. That should widen the field of companies offering delivery, inspection, and agricultural services.

A clear target for aircraft and DAA makers

Manufacturers of aircraft and detect-and-avoid systems have had to guess what individual FAA reviewers would accept. Acceptable means of compliance give them a defined target to design and test against. That should shorten product development cycles and make it easier for operators to buy equipment that is known to support certification, rather than discovering gaps during review.

Viable economics for long-range services

Multi-mile delivery, long-corridor inspection, and wide-area agricultural monitoring only make sense if aircraft can fly beyond the pilot's sight routinely. A repeatable approval path lets operators model unit economics with confidence, because the regulatory cost of each new route is known rather than open-ended. That is what moves these services from pilot programs toward sustainable businesses.

BVLOS Use Cases Under Part 108

Multi-mile package and grocery delivery

Delivery drones are the most visible BVLOS application, and the one most constrained by waivers. Operators ran pilot programs in a small number of cities, each under its own exemption. With a standard framework, a delivery operator that meets the requirements can plan expansion to new suburbs and corridors without renegotiating its safety case every time. The outcome is delivery networks sized to demand rather than to the number of waivers an operator managed to secure.

Medical supply drops

Moving lab samples, medicines, or urgent supplies between facilities is a strong fit for BVLOS: routes are fixed, payloads are light, and speed matters. Medical delivery pilots have already operated under waivers. A predictable certification path lets health systems and logistics providers treat drone transport as a planned service with defined routes and schedules, rather than a demonstration that might not survive beyond the pilot period.

Pipeline, transmission line, and rail inspection

Linear infrastructure stretches for miles across terrain that is slow and sometimes dangerous to inspect on foot or by crewed aircraft. BVLOS drones can fly the corridor and capture imagery and sensor data along its length in one mission. Under Part 108, inspection operators can certify their aircraft and procedures once and then fly routine inspections across many corridors, which turns occasional surveys into regular monitoring that catches problems earlier.

Wide-area agricultural monitoring and spraying

Large farms need imagery and treatment across far more ground than a pilot can keep in sight. BVLOS operation allows a single drone mission to cover many fields, capturing crop health data or applying treatments where needed. With a standard approval path, agricultural service providers can offer these services across many customers instead of being limited to the small areas a waiver covered.

Remote site and asset monitoring

Solar farms, remote facilities, and large industrial sites benefit from regular aerial checks without sending staff on long drives. BVLOS flights from a central base can survey sites on a schedule, with the telemetry and logging Part 108 expects feeding straight into maintenance systems. Issues such as damaged panels or perimeter breaches surface between scheduled visits instead of at them.

Practical implications for businesses

For companies already operating drone delivery or BVLOS inspection services under existing waivers, Part 108 is primarily a path to scale: it offers a way to expand service areas and fleet sizes without re-litigating the safety case for every new route. For companies that have been waiting on the sidelines because the waiver process was too slow or too resource-intensive to pursue, it lowers the barrier to entering the market in the first place.

A few practical consequences worth planning around:

1. Certification still requires real engineering investment. A published standard is not a free pass — operators still need aircraft, detect-and-avoid systems, and operational procedures that actually meet the rule's requirements. The barrier moves from "win a waiver" to "build a compliant system," which is a different kind of work but not necessarily less of it.
2. New service categories become economically viable. Multi-mile delivery routes, long-corridor infrastructure inspection (pipelines, transmission lines, rail), and wide-area agricultural monitoring all depend on flying further than a human can watch. A standard certification path makes the unit economics of these services more predictable, because operators can model a repeatable approval process instead of an open-ended one.
3. Airspace integration becomes a shared problem. As BVLOS operations scale from a handful of waiver holders to a broader operator base, coordinating who is flying where — separate from air traffic control for manned aviation — becomes more important. Expect continued development of UAS traffic management (UTM) systems that let operators and the FAA share real-time flight data.
4. Insurance and liability frameworks will need to mature alongside the rule. A standard certification path changes who bears responsibility when something goes wrong — the operator's compliance with a published rule, rather than the specific terms the FAA negotiated in a one-off waiver — and insurers will need to price that risk accordingly.
5. Local and state permitting still matters. Part 108 governs federal airspace authorization. It does not preempt local noise ordinances, land-use rules, or state-level restrictions that many cities have already begun layering on top of federal drone rules.

Who benefits most

Not every player in the drone ecosystem gains equally from the shift. Established BVLOS operators that already hold waivers get a smoother path to scaling what they've proven. Smaller operators and new entrants get, for the first time, a realistic route into BVLOS operation that doesn't require winning a lengthy individualized negotiation with the FAA. Aircraft and DAA-system manufacturers benefit from a published standard they can design against, rather than guessing what a case-by-case reviewer might accept — a dynamic playing out in parallel for eVTOL aircraft certification in the broader advanced air mobility space. Manned aviation operators — general aviation pilots, agricultural aircraft, helicopters — have the most to watch closely, since they are the traffic that drone detect-and-avoid systems are built to sense and avoid.

Real limitations and open questions

Part 108 replaces one bottleneck with a different set of constraints, and it's worth being clear-eyed about what it doesn't solve:

• A standard is only as good as its acceptable means of compliance. If the technical bar for detect-and-avoid, communications reliability, or contingency planning is set too conservatively, the rule could still function as a de facto barrier for smaller operators who can't afford top-tier sensor packages. If it's set too loosely, safety incidents could erode public and regulatory trust in the entire framework.
• Airspace density is a real physical constraint. A standard certification path makes it administratively easier to add operators, but it doesn't expand the physical airspace available near airports, in urban corridors, or in areas with existing manned-aircraft traffic. Congestion management remains an open engineering and policy problem.
• Public acceptance isn't guaranteed by regulatory approval. Noise, privacy concerns, and visual clutter from delivery drones have generated local pushback in markets where BVLOS delivery already operates. A federal rule change doesn't automatically resolve community-level friction.
• Enforcement and audit capacity matters. Moving from individualized pre-approval to self-certification against a standard shifts more responsibility onto operators to comply honestly, and onto the FAA to audit compliance after the fact rather than verify it before flight. The credibility of the whole system depends on that audit function actually working at scale.
• International harmonization is still uneven. Other aviation authorities — in Europe, the UK, and elsewhere — have taken different regulatory approaches to BVLOS, which complicates life for drone manufacturers and operators trying to build products for global markets rather than a single jurisdiction.

What to watch next

The rule's real impact will show up less in the text of Part 108 itself and more in how it gets implemented and adopted over the following months and years:

• How quickly existing waiver holders migrate to Part 108 certification, and whether that migration is smoother or slower than the FAA anticipates.
• How many new operators — particularly smaller companies without the legal and engineering resources to have pursued a waiver — actually achieve certification under the new standard.
• Whether UAS traffic management systems mature fast enough to support the airspace coordination that scaled BVLOS operations will require.
• How incident rates and near-miss reports trend as flight volume increases, since that data will shape whether the acceptable means of compliance get tightened or relaxed over time.
• Whether local and state governments respond to increased drone traffic with additional restrictions that offset some of the federal simplification.

Common Part 108 Mistakes

Treating the rule as a free pass

A published standard removes the waiver negotiation, not the engineering. Operators that read Part 108 as "BVLOS is now allowed" and skip the investment in compliant aircraft, detect-and-avoid, and procedures will find certification just as hard to achieve as a waiver was, only with a different set of reviewers asking the questions. Budget for the system the standard requires, not for a paperwork exercise.

Planning in generalities instead of specific operations

"We want to fly BVLOS" cannot be costed or certified. Requirements under a risk-based rule depend on the specific operation: altitude, population underneath, time of day, nearby air traffic, and flight volume. Teams that skip defining concrete corridors and missions end up either overbuilding for scenarios they will never fly or underbuilding for the ones they will.

Underbuilding the data and logging layer

A self-certification regime runs on records. Hardware-first teams often focus on aircraft and sensors and leave flight logs, link-health monitoring, maintenance history, and incident reporting to spreadsheets. When an audit or an incident arrives, those gaps are expensive to fill retrospectively and can undermine an otherwise sound safety case.

Ignoring local rules and community concerns

Federal authorization does not override local noise ordinances, land-use restrictions, or state rules. Operators that design routes purely around FAA requirements can find a takeoff site blocked or a corridor contested by residents after they have already invested. Local engagement belongs in route planning, not after launch.

Assuming existing waivers carry over unchanged

Waiver holders may expect a simple transfer to the new framework. Migration will still require showing that aircraft, DAA, and procedures meet the published means of compliance, which may differ from the mitigations a waiver accepted. Plan a gap analysis rather than assuming continuity, and keep flying under the existing waiver until it is done.

Part 108 BVLOS Best Practices: How Operators Can Prepare

The details of acceptable means of compliance will keep evolving, but the shape of the work is already clear. Teams that want to move quickly once the certification path is open can start on the parts that don't depend on final wording.

Step 1 – Map the operations you actually want to fly

Write down the concrete missions: delivery corridors, inspection routes, altitude bands, population density underneath, time of day, and expected flight volume. Part 108 is risk-based, so the category of operation you pick determines how demanding the safety requirements are. A vague "we want to do BVLOS" plan can't be costed; a specific corridor can.

Step 2 – Audit aircraft and detect-and-avoid capability

Inventory what your current aircraft can sense and how they react. Which hazards are covered by onboard sensors, which by cooperative position broadcasting, and which by ground surveillance? Where are the gaps for the environments in Step 1? This is usually the largest capital line item, so it's worth knowing early whether existing hardware can be upgraded or must be replaced.

Step 3 – Build the data and telemetry backbone

A self-certification regime runs on records. Operators need reliable flight logs, command-and-control link health monitoring, maintenance history, incident and near-miss reporting, and the ability to share position data with UTM services. Much of this is software — real-time data pipelines, dashboards, and alerting — and it's the piece most often underbuilt by teams that started as hardware companies.

Step 4 – Write procedures, then rehearse them

Contingency handling — lost link, GPS degradation, low battery, an intruding manned aircraft — has to be documented and practiced, not just designed. Simulation and staged test flights let teams verify that procedures and software behave as written before anyone audits them.

Step 5 – Engage communities and local authorities early

Federal authorization doesn't settle noise and privacy concerns on the ground. Early outreach to city officials and residents along planned routes reduces the chance of a local ordinance undoing the business case after certification.

If your organization is evaluating how autonomous flight or other physical-AI systems fit into your operations, Woyce Technologies can help you think through the technical and integration questions involved.

FAQ

What is FAA Part 108?

Part 108 is a new FAA rule that establishes a standard certification framework for beyond-visual-line-of-sight (BVLOS) drone operations, replacing the prior system in which operators had to apply for individual, case-by-case waivers under Part 107 to fly beyond the pilot's line of sight. In short, it turns BVLOS from an exception the FAA grants one operator at a time into a defined class of operation with published requirements. Operators still have to meet safety standards for aircraft, detect-and-avoid, and procedures, but they build to a known target rather than negotiating terms individually.

How is Part 108 different from a Part 107 waiver?

A Part 107 waiver is a one-off exemption the FAA grants after reviewing a specific operator's safety case for a specific aircraft and route. Part 108 instead defines a published standard that any qualifying operator can certify against, which is designed to be faster, more predictable, and reusable across fleets and service areas rather than negotiated from scratch each time.

Does Part 108 mean any company can now fly drones beyond visual line of sight?

Not automatically. Operators still need to certify their aircraft, detect-and-avoid systems, and operating procedures against the standards Part 108 sets out. It removes the need to negotiate a bespoke waiver, but it does not remove the underlying safety and engineering requirements for BVLOS flight. In practice, the cost of compliant sensors, software, and procedures will still keep some operators out, at least initially.

Why couldn't drone delivery scale under the old waiver system?

Because each waiver was narrowly scoped to a specific operator, aircraft, and area, and review timelines could run well over a year with no guaranteed deadline. That made it impractical for the industry to expand from a handful of pilot programs to widespread commercial service. Expanding to a new city or a new aircraft model often meant starting a fresh application, so growth was gated by regulatory paperwork rather than demand, capital, or technology readiness.

What is detect-and-avoid and why does it matter for BVLOS?

Detect-and-avoid (DAA) is the set of sensors and systems — onboard radar, cameras, cooperative position broadcasting, or ground-based surveillance — that let an uncrewed aircraft sense and avoid other air traffic without a human pilot watching the sky. It's the core technical substitute for the human eyes a pilot would use under visual-line-of-sight rules, which is why it sits at the center of any BVLOS safety standard.

Which companies are likely to benefit first from Part 108?

Operators that already hold BVLOS waivers, such as established drone delivery and infrastructure inspection companies, are best positioned to move quickly since they already have proven aircraft and safety systems. Smaller operators and new entrants stand to benefit over time as the certification path lowers the barrier that previously favored well-resourced incumbents.

Does Part 108 override local drone restrictions?

No. Part 108 governs federal airspace authorization for BVLOS flight. It does not preempt local noise ordinances, land-use restrictions, or state-level rules that many municipalities have adopted separately in response to increased drone activity. Operators should plan for both layers, checking city and county rules along every planned route, since a corridor that is federally authorized can still face takeoff, landing, or noise limits locally.

Conclusion

The core problem Part 108 addresses is administrative, not technical: BVLOS flight has been feasible for years, but a waiver-by-waiver approval process made it impossible to plan, finance, or scale. By publishing a performance-based standard, the FAA moves from pre-approving individual operators to defining what safe operation looks like and auditing against it. That is what makes multi-mile delivery, corridor inspection, and wide-area agricultural work modelable as businesses rather than one-off pilots.

The caveats are real. Certification still demands serious investment in aircraft, detect-and-avoid, and procedures. Airspace density, community pushback over noise and privacy, and local restrictions are untouched by a federal rule. And a self-certification model only stays credible if operators keep honest records and the FAA's audit function keeps pace with flight volume.

For most teams, the practical next step is to define specific target operations and assess the gap between current systems and what those operations will require — especially the telemetry, logging, and fleet coordination software that a standards-based regime depends on. If you need help building that data and control layer, you can book a call with our engineering team.