FAA BVLOS Waiver — What You Need in Your Application to Get Approved

FAA BVLOS waiver approvals have gotten complicated with all the misinformation and vendor spin flying around. As someone who spent the better part of two years grinding through this process — reviewing approved waiver packages, talking to operators who’ve cycled through multiple submissions, making embarrassing mistakes along the way — I learned everything there is to know about what actually gets these applications across the finish line. What follows is the guide I desperately needed when I started. No “it depends” non-answers. Just what the FAA wants to see in 2026.

One thing upfront — the landscape shifted hard with the FAA’s push toward Part 108 rulemaking. If you’re still planning around the old Part 107 waiver system exclusively, you may be choosing a slower path than you need to. We’ll cover both.

BVLOS Approval Paths in 2026

Two primary routes exist for legal BVLOS operations right now. They are not interchangeable — what you’re flying and where you’re flying it determines which path makes sense.

Part 107 Waiver — Still Active, Still Valid

Under 14 CFR Part 107.200, you can apply for a waiver from the visual line of sight requirement (107.31) through the FAA’s DroneZone portal. This process has existed since 2016. Hundreds of these waivers have been issued — but the approval rate for BVLOS specifically sits well below 50% on first submission. The waiver is operation-specific. Tied to a defined geographic area, a specific aircraft, a stated mission type. There’s no blanket Part 107 BVLOS waiver that covers everything you might want to do.

Part 107 waivers are the right path when your operation is bounded, repeatable, and confined to a tight area with clear risk mitigations. Infrastructure inspection along a fixed pipeline corridor, for example. Or precision agriculture over a single farm with no nearby population. That’s what makes Part 107 appealing to operators who need something defined and manageable.

Part 108 — The New Framework

The FAA finalized the Beyond Visual Line of Sight framework under Part 108 in late 2024, with implementation rolling through 2025 and into 2026. Part 108 is a more structured, scalable path — built specifically for operators who need recurring BVLOS operations across variable areas rather than a single fixed corridor.

But what is Part 108 certification, exactly? In essence, it’s an Air Carrier Certificate equivalent for UAS. But it’s much more than that — it’s a formalized safety case structure with assigned certification teams and defined data requirements, which sounds intimidating until you realize it’s actually more predictable than the waiver process. The tradeoff is front-loaded documentation. Heavier burden at the start, broader operational envelope when approved.

If you’re scaling BVLOS operations — delivery, long-range inspection, public safety support — Part 108 is worth serious consideration over stacking multiple Part 107 waivers. If you need approval for one specific operation by a specific date, Part 107 is still faster when the application is done right.

What the FAA Requires in Your Application

Probably should have opened with this section, honestly, because most rejections come from incomplete submissions rather than fundamentally flawed safety cases. The DroneZone portal asks for specific fields. Missing or vague answers are the fastest way to get a return without action.

The Flight Safety Plan

This is your core document. It needs to cover the operational concept — what you’re doing, where, at what altitude — plus the airspace environment, your command and control link architecture, lost link procedures, and emergency response procedures. The FAA wants specifics. “Pilot will land the aircraft if signal is lost” is not a lost link procedure.

A real lost link procedure specifies what the aircraft does automatically at signal loss — return-to-home behavior, loiter altitude, maximum loiter duration. It addresses how the remote pilot is alerted, how ATC is notified if applicable, and what ground containment measures exist if the aircraft doesn’t return as expected. Every one of those details needs to be in writing.

Write the flight safety plan assuming the reviewer has never seen your aircraft and has no idea what your operational area looks like. That’s literally the situation they’re in.

Equipment Specifications

The FAA requires a detailed equipment list — manufacturer name, model number, firmware version at time of application, and FCC ID for every radio component in your system. Your ground control station radio, your telemetry link, your video downlink if it’s separate — all of it. The FCC ID requirement trips up a lot of operators. Some components, especially third-party telemetry radios, have FCC IDs that are genuinely difficult to locate. Check the FCC Equipment Authorization database at apps.fcc.gov if the ID isn’t printed on the unit itself.

For the aircraft: maximum takeoff weight in grams — not pounds, the FAA’s forms use grams — maximum airspeed, endurance at operational payload, and propulsion type. If your aircraft is a modified commercial platform, say a DJI Matrice 350 RTK with a custom payload, document the modification and how it affects the performance envelope. Unexplained modifications raise flags immediately.

Collision Avoidance Plan

This section gets more scrutiny than almost anything else. The FAA’s primary concern with BVLOS is detect-and-avoid — how does your operation maintain separation from manned aircraft when there’s no human eye on the drone?

Your collision avoidance plan needs to address three distinct layers: strategic deconfliction before the flight, tactical deconfliction during the flight in near-real-time, and emergency procedures when separation is about to be violated. LAANC authorization handles part of the strategic layer in controlled airspace — it doesn’t substitute for a full collision avoidance plan. The FAA wants all three layers addressed explicitly.

For operations below 400 feet AGL in low-traffic Class G airspace — a common BVLOS scenario — you can build a credible collision avoidance case around operational constraints: daylight only, radio monitoring on 122.9 MHz CTAF near airports, filed NOTAMs, ADS-B In on the ground station. ADS-B Out on the UAS strengthens the case considerably, even when it’s not strictly required by rule.

Specific Form Fields That Matter

In DroneZone, the “Proposed Area of Operation” field requires a KMZ or KML file defining your operational area. Make it tight. A 50-square-mile polygon submitted “just to be safe” signals to the reviewer that you haven’t defined a controlled operation. Use the smallest area that actually covers your mission — you can amend it later to expand.

The “Mitigation Measures” free-text field is where most applicants write something generic and lose the reviewer entirely. Be specific: “Operations are limited to the 3.2-mile corridor between GPS coordinates [X] and [Y], at altitudes between 100 and 300 feet AGL, during daylight hours only, with a dedicated visual observer at each end of the corridor positioned to observe and communicate via radio on [frequency].” That’s a mitigation. “Will follow all applicable regulations” is not.

Risk Mitigation Plan — What Gets Approved

Frustrated by a vague first submission that went nowhere, I rebuilt my mitigation approach using publicly available approved waivers as my primary research material. The FAA publishes a database of granted waivers — searchable on the FAA website — and it’s worth several hours of your time before you write a single word of your own application. Don’t make my mistake of skipping that step.

Mitigations That Consistently Appear in Approved Applications

Approved BVLOS waivers in sparsely populated areas almost universally include operations restricted to a specific geographic polygon, altitude caps typically at 400 feet AGL or lower, visual observers at key positions with defined communication protocols, lost link procedures with specific aircraft behavior parameters, and operational restrictions tied to weather minimums — usually 3 statute miles visibility and 500-foot cloud clearance at minimum, often stricter.

For corridor operations along pipelines, power lines, or railways, the strongest applications include a ground risk assessment showing population density along the corridor. The FAA uses the ASSURE ground risk framework internally. You don’t have to submit a formal ASSURE analysis, but structuring your ground risk section around population exposure, casualty probability, and shelter-in-place factors shows the reviewer you’ve actually done the work.

What Gets Rejected

Vague mitigations. Equipment without FCC documentation. Operational areas that include Class B, C, or D airspace without a specific ATC coordination plan — the FAA will not approve BVLOS operations bleeding into controlled airspace without a separate letter of agreement from the relevant TRACON or tower. That coordination has to happen before the waiver is submitted, not after approval.

Over-reliance on detect-and-avoid technology as your primary mitigation also gets pushback. “Our aircraft has obstacle avoidance sensors” is not a collision avoidance plan for manned aircraft. Ground-based obstacle avoidance and air traffic separation are completely different problems. The FAA knows the difference and expects your application to demonstrate that you do too.

Processing Timeline and What to Expect

The FAA targets 90 days for waiver processing. Complex BVLOS applications frequently run 120 to 180 days. Set your project timeline accordingly — and I mean actually set it, not optimistically ignore it. Submitting a BVLOS waiver application expecting approval in time for a contract starting in six weeks is a lesson I learned expensively. Don’t repeat it.

After Submission

After submitting through DroneZone, you’ll receive an acknowledgment email with a case number. Keep this somewhere you’ll actually find it. The FAA’s Flight Technologies and Procedures Division — AFS-80 — handles waiver review. You can follow up by emailing 9-AVS-AFS-800-DroneWaiver@faa.gov with your case number after 60 days if you’ve received no correspondence. Don’t follow up weekly. It doesn’t accelerate anything and generates noise in their queue.

The most common mid-process correspondence is a Request for Additional Information — an RAI. This is not a rejection. It’s the reviewer identifying gaps. Respond to every RAI item completely and specifically. A partial response restarts the clock and signals that you’re going to be a difficult applicant to work with long-term.

Common Rejection Reasons

Incomplete equipment documentation. Missing FCC IDs. Operational area overlapping restricted airspace without prior coordination. Lost link procedures describing pilot intent rather than aircraft automation behavior. No weather minimums defined. Ground risk section absent or perfunctory. Collision avoidance plan relying entirely on ADS-B Out without additional procedural mitigations layered on top.

If you receive a denial, the FAA’s letter specifies the deficiencies. You can reapply — and many operators get approved on the second or third submission after addressing the specific feedback. The denial is data. Use it accordingly.

Equipment That Has Been Approved for BVLOS

While you won’t need the most exotic or expensive platforms on the market, you will need a handful of components with documented FAA standing. What follows isn’t a recommendation — it’s a report of what shows up in the FAA’s public waiver records and in operational accounts from operators who’ve been through the process. Equipment with an existing FAA track record reduces the documentation burden on your application. You’re building on established precedent rather than asking the FAA to evaluate something novel.

Platforms With Documented Approval History

The Skydio X10 — and the earlier X2 Enterprise — appears in multiple approved BVLOS waivers, particularly for infrastructure inspection and public safety applications. Skydio’s obstacle avoidance system has been accepted as a supporting mitigation, not a primary one, in several approved packages. Its logs and autonomous flight capabilities have been evaluated positively in FAA review contexts.

The DJI Dock 2 with the Matrice 3D/3TD has been included in approved BVLOS operations, primarily automated inspection corridors. DJI’s FAA standing is complicated — federal procurement restrictions apply following the American Security Drone Act — but civilian commercial operators are not currently prohibited from using DJI equipment in waiver applications. That may change. Know the current status when you’re writing your application, not after.

uAvionix equipment — specifically the Ping20Si ADS-B transceiver and the tailBeaconX — appears frequently in approved BVLOS packages as the ADS-B Out solution. uAvionix might be the best option here, as BVLOS operations require clear ADS-B Out documentation with established regulatory standing. That is because FAA reviewers already have reference points for uAvionix TSO approvals, which reduces friction during review considerably.

The Percepto Arc autonomous inspection drone has been used in approved BVLOS programs at industrial facilities. Their FAA engagement history and published safety case structures are worth studying if you’re pursuing facility-based BVLOS for critical infrastructure.

What “FAA Track Record” Actually Means

First, you should understand what equipment track record actually does — and doesn’t — do for your application, at least if you’re expecting it to carry the whole thing. Approved for one operator’s specific application doesn’t mean it sails through yours automatically. Track record reduces friction. It gives the reviewer a reference point. Using a Skydio X10 doesn’t excuse a missing collision avoidance plan. Equipment choice is one variable among many.

That’s what makes this process endearing to operators who’ve been through it more than once — it rewards genuine preparation over shortcuts. The operators who get approved consistently treat the application as a real safety communication rather than a compliance exercise. The FAA reviewer reading your package is trying to determine whether your operation is actually safe. Write the application to answer that question, completely and specifically, and your chances improve substantially over the operators who submit the minimum and hope for the best.