Airspace for Drones: The 2026 Operator's Guide

Updated May 18, 2026.

Airspace authorisation is not airspace safety. LAANC will approve a drone flight in controlled airspace under a published facility-map altitude in under a minute. It will not warn the operator about the helicopter route running through the inspection corridor, the stadium TFR that activates an hour before kickoff, or the agricultural spray operation working below the airline approach path. Pilots who stop their airspace homework at the LAANC approval get caught by everything LAANC does not check.

The operator-side view of airspace in 2026 has three moving parts: the legal envelope (14 CFR Part 107 and the airspace classes), the authorisation layer (LAANC and the FAA DroneZone portal), and the live-condition layer (TFRs, NOTAMs, special-use activations). LAANC covers roughly 740 air-traffic facilities as of 2026, which is most of the controlled-airspace surface area in the United States. It does not cover anything outside that surface area, where most of the actual collision risk lives.

Add the Part 108 BVLOS rule (in late-stage rulemaking as of May 2026), the FAA Reauthorization Act of 2024's $75,000-per-violation civil penalty ceiling, and the maturing UTM integration plans for unmanned traffic management, and the 2026 airspace picture looks less like a static chart and more like an operating system that has to be read live before every flight.

Quick answer: Airspace for drones is the layered system of FAA-managed regions, altitudes, and restrictions that every Part 107 flight operates inside. Class B, C, D, and surface Class E (controlled) require prior authorisation, usually through LAANC. Class G (uncontrolled) needs no authorisation but still carries §107.51 altitude limits, right-of-way rules, and special-use overlays.

Table of contents

• What does airspace for drones mean in 2026?
• The six airspace classes and which ones drones actually touch
• Controlled airspace: LAANC, DroneZone, and the gaps between them
• Uncontrolled airspace is not unregulated airspace
• The restrictions LAANC does not see
• Authorisation workflow: from sectional chart to takeoff
• Altitude limits, waivers, and the structure exception
• What airspace enforcement looks like in 2026

What does airspace for drones mean in 2026?

Drone airspace is the three-dimensional volume above the United States that the FAA divides into six classes (A, B, C, D, E, G) with different traffic-control regimes, layered with special-use airspace, restricted areas, and dynamic flight restrictions. Every Part 107 flight, every recreational flight, and every anticipated Part 108 BVLOS operation lives inside that system.

The practical version is simpler. Below 400 feet AGL in Class G (uncontrolled) airspace, a Part 107 pilot can fly without prior authorisation as long as 14 CFR §107.41 and the surrounding rules are met. Anywhere inside Class B, C, D, or surface Class E, prior authorisation is required. Across approximately 740 air-traffic facility areas as of 2026, that authorisation runs through LAANC; outside that footprint, it routes through the FAA DroneZone portal as a manual application.

Three 2026 changes matter for airspace planning. The original FAA-developed B4UFLY mobile app was retired and replaced by a short list of FAA-approved partner providers delivering the same airspace situational data. LAANC facility coverage now spans the vast majority of controlled airspace by surface area, with manual review reserved for non-routine requests. And the Part 108 BVLOS framework, in late-stage rulemaking, brings performance-based aircraft requirements (detect-and-avoid, electronic conspicuity) that intersect with airspace authorisation in new ways.

The six airspace classes and which ones drones actually touch

The FAA defines six airspace classes. Drone operators care about four of them in practice.

Class	Where it sits	What it means for a Part 107 flight
A	18,000 ft to 60,000 ft MSL	Out of reach. Commercial-airliner cruise altitude.
B	Around the busiest airports, surface up to 10,000 ft, layered tiers	Prior authorisation required. Facility-map altitudes are typically low or zero close to runways.
C	Around medium-traffic airports, surface up to ~4,000 ft AGL	Prior authorisation required. LAANC usually handles routine requests.
D	Around towered airports of smaller scale, surface up to ~2,500 ft AGL	Prior authorisation required. Class D airspace is the most common controlled grid LAANC users encounter.
E	Controlled airspace that isn't A/B/C/D. Often from 700 or 1,200 ft AGL up.	Authorisation required only where Class E extends to the surface. The "700 ft / 1,200 ft above" Class E does not affect routine drone flights. Class E reference.
G	Uncontrolled. Surface up to where Class E starts	No prior authorisation required. §107.51 altitude limit (400 ft AGL) and visual line-of-sight rules still apply. Class G airspace covers most rural flights.

The class that trips up new Part 107 operators most often is surface-extension Class E. A non-towered airport with an instrument approach typically has Class E going to the surface around it, and that surface ring requires authorisation despite the absence of a control tower. Surface Class E shows up on sectional charts as a dashed magenta line. The full airspace types overview breaks down the chart conventions.

Controlled airspace: LAANC, DroneZone, and the gaps between them

LAANC (Low Altitude Authorization and Notification Capability) is the FAA program that delegates routine controlled-airspace approvals to a pool of approved UAS Service Suppliers, who deliver authorisation through their own apps. As of 2026, LAANC covers approximately 740 air-traffic facilities, which is most of the controlled-airspace surface area in the United States. The official program page on the FAA LAANC site lists the current providers and coverage.

The mechanism is straightforward. The FAA publishes UAS Facility Maps as a grid of altitude ceilings for each controlled-airspace area. A pilot submits a flight plan through an FAA-approved provider; if the requested altitude is at or below the published ceiling for the grid square, the system returns an automatic authorisation. Above the ceiling, the request becomes a manual review.

FAA DroneZone (the consolidated FAA drone portal) handles everything LAANC does not: manual airspace authorisation requests above facility-map altitudes, requests in non-LAANC areas, Part 107 waivers, Remote ID registration, and the aircraft registration record itself. DroneZone reviews run days to weeks, with complexity driving the timeline. The LAANC authorisation reference covers the request flow in operational detail.

The gap between LAANC and DroneZone is where commercial operators get caught. LAANC approves below the facility-map ceiling. It does not see helicopter routes that share the airspace, agricultural spray operations under FAR Part 137, military low-level routes, or any special-use overlays. Authorisation is a regulatory check, not a traffic check.

Uncontrolled airspace is not unregulated airspace

Class G airspace requires no prior authorisation, which is the source of an enduring misconception. The §107.51 altitude limit (400 feet AGL, with the structure exception explained below) applies in Class G. The §107.31 visual line-of-sight rule applies. Right-of-way rules under §107.37 require the drone to yield to manned aircraft. And the special-use overlays (military operations areas, restricted areas, prohibited areas, national security UAS flight restrictions) apply in Class G as much as anywhere else.

The collision-risk profile in Class G also flatters the operator. Most general-aviation pattern work, agricultural flying, helicopter EMS, and pipeline patrols happen in Class G airspace at altitudes below 1,000 feet AGL. A drone operating at 380 feet AGL in rural Class G is operating in the same vertical band as a low-flying Cessna or a medevac helicopter at any moment.

The no-fly zones and restricted areas reference covers the static restrictions that ride on top of Class G. Dynamic restrictions, the harder layer to track, are the next section.

The restrictions LAANC does not see

LAANC answers one question: does this proposed flight stay below the published facility-map altitude in this controlled-airspace grid? Everything else is the operator's responsibility, and the everything-else list is long.

• Temporary Flight Restrictions (TFRs). Issued for presidential movements, large-scale emergencies (wildfires, hurricanes), and certain public events. TFRs override existing authorisations. A LAANC-approved flight can become an illegal flight the moment a TFR activates, with no notice from the LAANC system itself.
• Stadium TFRs. A standing flight restriction under FDC NOTAM 4/3621 over MLB, NFL, NCAA Division I football, and certain NASCAR venues. The restriction extends 3 nautical miles laterally and 3,000 feet vertically, in force from one hour before the scheduled event start to one hour after the end. Practice sessions and pre-game activity are covered.
• DC Flight Restricted Zone (FRZ). Roughly 15 nautical miles around DCA, with the broader Special Flight Rules Area extending to 30 nautical miles. Civilian drone flights in the FRZ require explicit federal authorisation.
• Special-use airspace. Military Operations Areas, Restricted Areas, Prohibited Areas, and Alert Areas each have their own activation schedules and rules. A LAANC authorisation in a controlled-airspace grid does not authorise flight inside an overlapping Restricted Area when it is active.
• National Security UAS Flight Restrictions. FAA-published drone-specific restrictions over critical infrastructure (DOE national labs, military bases, certain Coast Guard stations). These are not always visible on standard sectional charts.
• State, local, and tribal restrictions. State parks, wildlife refuges, and tribal lands can prohibit takeoff and landing under their own rules even where the FAA permits the flight overhead. The FAA preempts airborne airspace; ground access is governed by the landowner.

The B4UFLY-equivalent partner apps consolidate most of the above into a single map view. Sectional charts and the FAA NOTAM Search remain the authoritative source. The NOTAM filing reference covers the operator's side of NOTAM use, and the USA aviation maps overview covers how to read the chart conventions.

Authorisation workflow: from sectional chart to takeoff

A repeatable pre-flight workflow for any controlled-airspace operation has six steps.

1. Identify the airspace. Pull the sectional chart for the operating area and confirm the airspace class. Note any surface Class E extensions, special-use overlays, or charted TFRs. The flight planning workflow covers the sequence in operational detail.
2. Check the facility map. The FAA UAS Facility Map gives the altitude ceiling for the grid square. At or below the ceiling, LAANC is the path. Above the ceiling, DroneZone is the path. The FAA Part 107 airspace authorisations page lists the current entry points.
3. Check live conditions. Run a NOTAM search and a TFR check. Stadium TFR check if any covered venue is within 3 nautical miles. National security UAS restriction check if any critical infrastructure is in the area.
4. Submit the LAANC request. Through any FAA-approved provider. Routine requests below the facility-map ceiling return automatic authorisation in seconds.
5. Verify equipment compliance. Remote ID broadcast active. Anti-collision lighting if operating in twilight or night. The pre-flight checklist covers the rest of the equipment checks.
6. Confirm right-of-way and yield procedures. §107.37 places the burden on the drone to yield. Visual observer placement and audio monitoring (where applicable) should be set before the launch sequence begins.

For operations that fall outside the LAANC envelope (above the facility-map ceiling, in non-LAANC airspace, or as part of a waiver request), the DroneZone application is the path. Lead time runs from a few days to several weeks. Waiver applications under §107.200 require a written description of how the operation will be conducted safely, which is where a risk assessment artefact enters the picture. BVLOS operations specifically route through the BVLOS compliance workflow and, for anyone tracking the rulemaking, the Part 108 requirements checklist.

Altitude limits, waivers, and the structure exception

§107.51(b) sets the baseline altitude for Part 107 operations at 400 feet AGL. Above that, the flight is non-compliant unless a waiver or the structure exception applies.

The structure exception is the most-used workaround. A Part 107 drone may operate up to 400 feet above the highest point of a structure, within a 400-foot radius of the structure, as long as the structure is being inspected, used, or otherwise associated with the operation. The exception is what makes cell-tower, wind-turbine, and tall-building inspections possible at the altitudes they require. The how-high-can-a-drone-fly reference covers the boundaries.

Altitude waivers under §107.200 unlock operations above 400 feet for cases the structure exception does not cover. The application requires a written justification, risk mitigations, and operational limitations. Waivers come with explicit altitude caps, geographic boundaries, and operational requirements written into the grant.

Controlled-airspace altitude limits are independent of the §107.51 baseline. A 100-foot LAANC ceiling in a Class D grid is a separate restriction from the 400-foot Part 107 limit. The lower of the two governs. Zero-altitude grids prohibit any drone operation in the affected airspace.

What airspace enforcement looks like in 2026

The FAA's airspace-enforcement posture in 2026 mirrors the rest of Part 107: the agency does not patrol airspace looking for violations, but it does respond to complaints, incidents, and any operation captured by Remote ID broadcasts or radar. The civil penalty ceiling for Part 107 violations is $75,000 per violation under the FAA Reauthorization Act of 2024, applied per violation rather than per flight.

Detection mechanisms have expanded. Remote ID broadcasts from any aircraft above 0.55 lb are receivable by law enforcement and counter-UAS systems. The FAA can correlate broadcast data with registration records to identify the remote pilot in command. Radar-based detection has improved at major airports. The asymmetry between "we didn't think they'd notice" and "the data is logged for years" has closed.

The most common enforcement triggers in 2026 are TFR violations (often around political events), critical-infrastructure overflights, airport surface-area incursions, and operations without Remote ID broadcast. The defence in any of these is the documentation trail: pre-flight check, LAANC or DroneZone authorisation, NOTAM and TFR confirmation, post-flight log. The drone compliance reference covers the documentation expected during enforcement actions, and a recurring audit scheduling cadence keeps the trail discoverable when an inspector asks.

Three things to fix this quarter

A clean LAANC record does not equal a clean airspace posture. Three concrete actions tighten the picture:

1. Re-run a NOTAM and TFR check on every flight, not every site. A location that was clear last week is not necessarily clear this week. Stadium TFRs, presidential TFRs, and security TFRs activate on schedules that do not align with operational cadence.
2. Map the special-use overlays for every regular operating area. Restricted areas, MOAs, and national-security UAS restrictions do not always appear in LAANC apps. A one-time sectional-chart review for each operating zone catches what the automated tools miss.
3. Verify Remote ID broadcast at the start of every flight. A drone that takes off without Remote ID broadcast in controlled airspace produces a violation distinct from any airspace violation. The check is two seconds at the pre-flight panel.

A single TFR or special-use violation now costs up to $75,000 per occurrence. The three checks above cost a few minutes per operation.

FAQ

Do I need LAANC authorisation in Class G airspace?

No. Class G is uncontrolled airspace and requires no prior FAA authorisation. The §107.51 altitude limit (400 feet AGL), the §107.31 visual line-of-sight rule, the §107.37 right-of-way rule, and any special-use airspace overlays still apply. Class G has no authorisation requirement, but the rule book underneath it is intact.

What replaced the FAA B4UFLY app?

The original FAA-developed B4UFLY app was retired. The FAA approved a short list of partner UAS Service Suppliers to deliver the same airspace situational data through their own apps and websites. The FAA B4UFLY landing page lists the current approved providers.

How long does LAANC authorisation take?

For requests at or below the published UAS Facility Map ceiling, LAANC returns automatic authorisation in seconds to a few minutes. Above the ceiling, the request becomes a manual review through DroneZone, which takes days to weeks depending on complexity and the airspace involved.

Can I fly a drone inside a Temporary Flight Restriction?

Generally no. TFRs override existing authorisations. Some TFRs allow specific operations under explicit authorisation (a press-credentialed drone covering an event, for example), but the default is no civilian drone operation inside an active TFR. NOTAM and TFR status should be checked immediately before flight, not at the start of the day.

Ready to keep airspace authorisations and pre-flight records in one place?

DroneBundle ties LAANC authorisations, pre-flight checklists, Remote ID compliance, and the post-flight log into one operations record. Each flight's airspace paperwork attaches to the flight it covered, so renewal and audit pulls do not require digging through email threads. Tour the features to see how it fits with the rest of the operations stack, alongside live tracking for in-flight monitoring and weather integration for the conditions that drive go/no-go decisions. Crews in the public safety and emergency response industry and the utilities and energy industry lean on the same pattern.

Start your free trial today, no credit card required.

Or try the live demo to see airspace tracking, flight logs, and compliance documentation in one workflow.