LAANC Airspace Authorization Explained

LAANC, the Low Altitude Authorization and Notification Capability, is the system that lets most drone flights in controlled airspace get authorized in seconds rather than weeks. Before LAANC existed, every flight near an airport required a manually reviewed application through the FAA. LAANC automated the common case: a request within a pre-approved altitude ceiling for a specific location is checked against airspace data and, in the overwhelming majority of cases, approved almost immediately.

What LAANC checks and approves

A LAANC request includes your exact takeoff location, requested maximum altitude, and time window. The system checks that request against the UAS Facility Map grid for that location. If the requested altitude sits at or below the pre-approved ceiling for that grid cell, LAANC issues an authorization automatically, typically within seconds to a couple of minutes. If the request exceeds the ceiling, it either routes to further review or gets rejected outright, and you need a different path to fly at that altitude in that location.

UAS Facility Maps and grid ceilings, in practice

Controlled airspace around an airport is divided into a grid on the UAS Facility Map, and each cell in that grid carries its own maximum altitude for near-instant LAANC approval. Cells directly over or very near an active runway commonly show a ceiling of 0 feet, meaning no altitude is pre-approved there at all, while cells farther from the airport typically allow higher ceilings, sometimes up to the general 400 foot limit that applies broadly to drone flight. The map is not a single number for the whole airspace; it changes cell by cell, sometimes dramatically, based on how flight paths and approach corridors are laid out around that specific airport.

This is why checking the exact grid cell for your takeoff point matters more than checking the airspace class alone. Two points a few hundred feet apart, both technically inside the same Class D surface area, can carry very different ceilings depending on which grid cell each one falls into.

LAANC vs DroneZone at a glance

Factor	LAANC	FAA DroneZone
Typical turnaround	Seconds to a couple of minutes	Days to several weeks
Covers	Requests within the published grid ceiling	Requests above the ceiling, or where LAANC is unavailable
Review type	Automated against the UAS Facility Map	Manual FAA review
Where used	Most controlled airspace, Class B, C, D, surface E	Same airspace, above LAANC ceilings, or special cases
Access	FAA-approved third-party apps	faa.gov DroneZone portal directly

Which apps to use

Only apps on the FAA's official list of approved LAANC service suppliers issue valid authorizations. Several apps built specifically around drone flight planning offer LAANC requests directly, showing the grid map, the ceiling for your exact location, and a request flow that submits to LAANC and returns the authorization status inside the app. Using an app that is not on the approved list, even if it displays similar-looking airspace data, does not generate a legally valid authorization, so confirm the specific app you use is on the current FAA list rather than assuming any drone app with a map does the job.

When LAANC is not the right tool

Three situations push a request out of LAANC and into FAA DroneZone instead. First, requesting an altitude above the published grid ceiling for that location; DroneZone reviews these manually rather than issuing an automated approval. Second, flying in airspace where LAANC coverage simply is not available, which does happen at some facilities. Third, certain special use airspace and specific operational categories that fall outside LAANC's automated scope by design. In all three cases, plan well ahead: DroneZone requests are reviewed by FAA staff and commonly take anywhere from several days to a few weeks, which is a poor fit for a same-day or next-day flight plan.

Class G and uncontrolled airspace

Class G airspace is uncontrolled, and flying there does not require a LAANC or DroneZone authorization at all. That does not mean no rules apply. The general altitude limit, any local TFRs, and any restrictions specific to the site itself all still apply in Class G exactly as they would anywhere else. Confirming an area is Class G is worth doing through a current airspace app rather than assuming, since airspace boundaries are not always intuitive from the ground and reading them correctly is its own skill, covered in reading a sectional chart.

How LAANC fits alongside registration and Remote ID

A successful LAANC authorization confirms only that your specific flight, at your specific location, altitude and time window, is cleared with respect to controlled airspace. It does not substitute for or imply compliance with any of the other independent requirements covered elsewhere on this site: the aircraft still needs to be registered if it meets the weight threshold or is flown under Part 107, it still needs to broadcast Remote ID correctly while airborne, and the pilot still needs to hold the appropriate TRUST or Part 107 credential for the type of flying being done. Treat a LAANC authorization as one item on a checklist of independent requirements rather than a single approval that covers everything at once, since each requirement is enforced and verified separately.

What happens if a LAANC request is rejected

A rejected LAANC request is not necessarily a dead end. The most common reason for rejection is a requested altitude above the grid ceiling for that exact location, in which case lowering the requested altitude to match the published ceiling often results in an immediate approval on resubmission. If the operational need genuinely requires the higher altitude, the next step is a manual request through FAA DroneZone rather than repeatedly resubmitting the same LAANC request and hoping for a different result. Some rejections stem from a temporary condition, such as an active TFR or a special event affecting that airspace for a limited window, in which case checking back after the restriction lifts is the more direct path than escalating to a manual request.

Time-sensitive commercial work, such as a roof inspection scheduled for a specific day, benefits from checking the grid ceiling for the job site well in advance rather than the morning of the flight, so there is time to either adjust the flight plan to the available ceiling or start a DroneZone request early enough for it to clear before the appointment. Building this check into client scheduling conversations, rather than assuming authorization will simply work out, avoids a scenario where a job is booked and cannot legally be flown as planned.

Reading the UAS Facility Map directly

Most LAANC-enabled apps overlay the grid directly on a map view, color-coded by ceiling altitude, which is the fastest way to read it in practice. Zooming in on a specific address shows the exact grid cell your takeoff point falls into and its published ceiling in feet AGL. It is worth zooming in carefully rather than reading the ceiling for a general area, since, as covered above, adjacent cells commonly carry different ceilings and a takeoff point a short distance from where you checked can fall into a different cell entirely. This same underlying grid data is also what a Part 107 candidate is expected to interpret correctly on the certification exam, covered further in Part 107 practice questions.

Building airspace checks into your routine

Whichever path applies, check airspace status as a standing step in your preflight checklist, not as a one-time setup task. Authorization requests are typically tied to a specific date and time window, TFRs shift day to day, and a site that was clear last week is not guaranteed clear today. For a broader picture of how airspace classes and altitude limits fit together, see the airspace classes reference, and if you fly commercially, review how airspace authorization interacts with Part 107 operating provisions in what Part 107 lets you do.