Picture two operators filing waiver requests the same week: a pipeline inspection company that needs to fly a 6-mile corridor no visual observer chain can realistically keep eyes on, and a mapping crew that wants to launch from the bed of a truck moving down a rural access road. Both operations are legal only with an FAA Part 107 waiver, and both sit in the exact category the FAA's own numbers show gets rejected on first submission more often than it gets approved — not because the flights are unsafe, but because the paperwork never proved it.
What a waiver actually authorizes
Under 14 CFR 107.200, a Part 107 waiver lets a certificated remote pilot deviate from specific operating rules within Part 107 — not the regulation as a whole — once the applicant shows the operation stays safe under the waiver's stated conditions. The commonly waived sections are 107.25 (launch or operation from a moving vehicle), 107.31 (visual line of sight), 107.33 (visual observer), 107.35 (one aircraft per pilot), 107.37(a) (yielding right of way), and 107.51 (altitude and speed limits); operation over people under 107.39 is now mostly handled through the Subpart D category system rather than a waiver. Airspace access near an airport is a different process entirely — that goes through LAANC or a standalone airspace authorization, not a 107.200 waiver — and filing the wrong request type is one of the most common first-time mistakes.
Why BVLOS requests fail so often
Waiving 107.31 to fly beyond visual line of sight has historically had one of the lowest approval rates of any waiver category, because a reviewer has to be convinced your mitigations reach an "equivalent level of safety" to a human visual observer, whose real job is catching a runaway aircraft, an intruding manned aircraft, or a lost control link before any of those become an incident. An application that says "we will use ADS-B In and a tracking camera" without stating detection range in seconds or nautical miles, response time, and the exact procedure for a lost-link event reads as boilerplate, and boilerplate gets bounced back for more detail or denied outright. It's also part of why the FAA has spent years developing a dedicated BVLOS rule (Part 108) instead of simply approving more waivers — the agency has signaled that case-by-case review isn't meant to be the long-term path for routine BVLOS work.
Building a safety case that survives review
The application isn't asking you to prove nothing can go wrong; it's asking you to name the specific hazard the waived rule normally controls and show your mitigation replaces that function. For a 107.25 moving-vehicle waiver, the question a reviewer looks for isn't "does the operator have experience" — it's what specifically prevents vehicle speed, road surface, or driver attention from turning a routine launch into a loss of control. FAADroneZone publishes granted waivers with redacted safety cases; pulling two or three from your exact regulation section shows the mitigation language and risk framing the FAA has already accepted, which beats guessing at the right level of detail from scratch.
Mistakes that add months to the timeline
The most avoidable mistake is scoping the waiver wider than the mission needs — requesting standing nationwide BVLOS authority when only one repeatable inspection route is planned invites more scrutiny, not less, because the safety case now has to cover every environment the broader scope implies. A second mistake is timing: straightforward waivers have typically run around 90 days for review, and BVLOS requests or applications stacking multiple waived sections together often take considerably longer, so treating the filing as a same-month formality is a scheduling error, not a paperwork one. A third mistake is leaving contingencies unaddressed — lost command-and-control link, GPS-denied navigation, and an unauthorized person entering the operating area each need a specific, named response, not a single line assuring the reviewer everything will be fine.
Practical checklist
- Confirm the limitation you need lifted actually lives inside Part 107 (Sections 107.25–107.51); airspace access near an airport is a separate LAANC or authorization process, not a 107.200 waiver.
- Scope the request to exactly what the mission needs — one corridor, one altitude band, one time window — rather than broad standing authority.
- Search FAADroneZone's published waiver records for approved requests under your same regulation section before drafting your safety case.
- Give lost-link, GPS-denied, and unauthorized-person scenarios each a named, specific response procedure instead of a general safety assurance.
- File at least 90 days ahead of when the operation is needed, and budget extra time for BVLOS or multi-section waiver stacks.
- Treat this dashboard's airspace and weather layers as planning references only — a granted waiver still binds you to its stated conditions, and this site does not verify or confirm FAA authorization status.