What is LAANC and how does it work for drone pilots?

LAANC, which stands for Low Altitude Authorization and Notification Capability, is an FAA system that provides Part 107 remote pilots with near-real-time airspace authorization to fly unmanned aircraft in controlled airspace at or below established altitude ceilings. Pilots use an FAA-approved UAS service supplier app to submit a request, and authorization can be granted in seconds based on predefined UAS Facility Map altitudes for a given grid. This replaces the need to wait days or weeks for a manual authorization through the FAA DroneZone portal for routine operations.

What is the difference between LAANC and the FAA DroneZone for getting UAS airspace authorization?

LAANC provides automated, near-instant airspace authorization for controlled airspace operations at or below the altitude ceilings shown on UAS Facility Maps, making it the preferred method for most routine Part 107 flights. The FAA DroneZone portal, by contrast, requires pilots to submit a manual waiver or authorization request that is reviewed by FAA personnel and can take days to weeks to process. If a pilot needs to fly above the published LAANC ceiling, or in an area not covered by LAANC, they must still use the DroneZone manual process to request authorization.

Does LAANC replace the need for radio communication with ATC for drone operations?

LAANC replaces the traditional manual authorization process for operating in controlled airspace but does not substitute for any required radio communication coordination with air traffic control. Part 107 remote pilots are generally not required to communicate via radio with ATC, but the LAANC authorization grants permission to operate within defined airspace and altitude limits, which helps ATC maintain awareness of UAS activity in those areas. Pilots must still comply with any conditions attached to their LAANC authorization and remain responsible for see-and-avoid responsibilities as outlined in 14 CFR Part 107.

LAANC System and Its Role in Replacing Traditional Radio Authorization

Before LAANC's nationwide rollout, a Part 107 remote pilot who wanted to fly a small unmanned aircraft system (sUAS) in controlled airspace had one primary option: submit a manual authorization request through the FAA's airspace authorization process — later unified under the DroneZone portal — and wait, sometimes days or even weeks, for a human air traffic controller to review and approve or deny the request. That process worked, but it was slow, unpredictable, and a significant barrier for time-sensitive commercial or public-safety drone operations. The Low Altitude Authorization and Notification Capability, known universally as LAANC, was developed as a collaborative effort between the FAA and industry partners to solve exactly that problem, with initial deployment beginning in 2017 and expansion continuing through 2018 and beyond. Today, LAANC is the primary gateway through which Part 107 pilots obtain near-real-time authorization to fly in the controlled airspace surrounding thousands of airports across the United States.

Understanding LAANC is not just a knowledge-test requirement — it is a fundamental operational skill. Many airports, towered and non-towered alike, sit within Class B, C, D, or E surface-area airspace that requires prior authorization under 14 CFR Part 107 before you fly there. Having a published instrument approach does not, by itself, mean the surrounding airspace is controlled down to the surface — plenty of non-towered airports with instrument approaches lie in Class G or in Class E airspace that does not extend to the ground, where no Part 107 authorization is required. Knowing how LAANC works, where it applies, and what it does not cover could be the difference between a legal flight and an unauthorized incursion into protected airspace.

How LAANC Works

LAANC is a data-sharing system rather than a single app or website. The FAA publishes UAS Facility Maps (UASFM) — grid-based maps that assign pre-approved altitude ceilings for drone operations in controlled airspace around each participating airport. These altitude values (e.g., 0 ft, 50 ft, 100 ft, 200 ft, 400 ft AGL) represent the maximum altitude at which the FAA has determined UAS operations can generally be conducted without creating an unacceptable conflict with manned aircraft arriving and departing the airport. Cells close to the runway typically show 0 ft, meaning no altitude is pre-approved without further coordination; cells farther from the runway may allow up to 400 ft.

FAA-approved third-party application providers — UAS Service Suppliers such as Aloft and other current FAA-approved providers — access the UASFM data through an FAA interface and integrate it into user-friendly mobile and web apps. When a remote pilot submits a LAANC authorization request through one of these apps, the system automatically checks the pilot's requested altitude and location against the UASFM grid values. If the request fits within the pre-approved parameters, the authorization is typically granted within seconds. If the requested altitude exceeds the UASFM ceiling for that grid cell, the automated system cannot approve it; the pilot must instead submit a manual Part 107 waiver or authorization request through DroneZone.

It is worth emphasizing that LAANC authorizations are tied to a specific location, altitude ceiling, date, and time window. They are not blanket permissions to fly anywhere in the vicinity of an airport. The pilot must accurately describe the operational area and must not exceed the authorized altitude. Exceeding those limits — even by a small margin — constitutes an unauthorized operation under 14 CFR §107.41.

The Relationship to Traditional Radio Communication Authorization

In the manned aviation world, a pilot contacting an air traffic control tower or TRACON for permission to transit controlled airspace does so over radio, in real time. A student pilot flying a Cessna near a Class D airport calls the tower, states intentions, and receives a clearance (or denial) verbally. The drone world historically had an analog to this: the manual DroneZone authorization, which effectively replaced the radio call with a written request reviewed by ATC personnel. LAANC takes this one step further by automating the authorization process entirely for pre-approved altitude bands, removing the need for any direct radio communication or human ATC review for routine low-altitude operations.

This is a significant conceptual shift. A Part 107 remote pilot is not required to have a radio, is not required to contact the control tower before launching under LAANC (once a LAANC authorization is in hand), and will generally never speak with a controller during a typical commercial drone job. The LAANC system itself serves as the communication channel between the remote pilot and the NAS management infrastructure. The approved LAANC authorization functions, for regulatory purposes, as the equivalent of an ATC authorization under 14 CFR §107.41 — it is just delivered digitally rather than verbally.

However, this does not mean a remote pilot should ignore manned traffic or ATC activity. The responsibility to see-and-avoid manned aircraft, comply with NOTAMs, and yield to all manned operations remains fully with the remote pilot at all times. LAANC grants airspace access; it does not provide separation services the way a radar controller does for instrument-rated pilots.

Where LAANC Applies — and Where It Does Not

LAANC currently operates at hundreds of airports where the FAA and ATC facilities have published UAS Facility Maps. Coverage continues to expand, but it is not universal. Remote pilots must verify LAANC availability for a specific location before assuming an automated authorization is possible. The FAA's official resources and approved LAANC provider apps display current coverage areas.

Critically, LAANC does not authorize operations in all controlled airspace. The following scenarios still require a manual Part 107 waiver or authorization through DroneZone:

Altitude requests exceeding the UASFM grid value — if you need 300 ft AGL but the grid cell only allows 100 ft, LAANC will not approve it automatically.
Operations in airspace without a published UASFM — some airports and some Class E surface areas do not yet have facility maps.
Temporary Flight Restrictions (TFRs) — a LAANC authorization does not override an active TFR. TFRs must be checked independently via the FAA's TFR website or a reputable pre-flight planning tool.
Special use airspace — prohibited areas, restricted areas, MOAs with active restrictions, and similar designations are not addressed by LAANC.
National Security Areas and other sensitive airspace — these require separate coordination.

Key Numbers and Rules

14 CFR §107.41 is the regulation requiring authorization before operating in controlled airspace. LAANC and the DroneZone manual process are the two most common FAA-accepted pathways for satisfying this requirement, though a Part 107 airspace waiver or other ATC coordination can also satisfy it in certain circumstances.
UAS Facility Map grid ceilings range from 0 ft to 400 ft AGL, in increments typically of 0, 50, 100, 200, and 400 ft.
400 ft AGL is the standard Part 107 altitude ceiling for uncontrolled (Class G) airspace; LAANC extends this authorization framework into controlled airspace up to that same ceiling where facility maps allow.
Near-real-time approvals are typically issued in seconds through approved LAANC provider apps when the request fits within pre-approved parameters.
LAANC does not replace the 14 CFR §107.49 preflight checklist — the pilot is still responsible for checking weather, NOTAMs, TFRs, and ensuring the aircraft is airworthy before flight.
LAANC authorizations are time-limited. A pilot approved for a four-hour window cannot simply return the next day and fly under the same authorization.

Practical Use in the Field

In practice, obtaining a LAANC authorization before a flight near a controlled airport takes only a few minutes with any approved provider app. The pilot opens the app, draws or selects the operational area on the map, enters the maximum altitude needed, selects a date and time window, and submits. If the request is within the automated approval ceiling, a digital authorization document is generated immediately. The pilot should save or screenshot this document as proof of authorization. If challenged by law enforcement or FAA officials, this record demonstrates compliance with §107.41.

Remote pilots should check multiple LAANC provider apps if one shows conflicting or unclear information, since each provider pulls from the same underlying FAA data but may display it differently. Pilots should also remember that airspace conditions change — a LAANC approval does not mean the airspace will be clear of TFRs or other restrictions by the time of the actual flight. Final NOTAMs and TFR checks within two hours of flight are considered best practice and align with the risk-management principles outlined in the FAA's Risk Management Handbook.

Common Test Traps

Confusing LAANC with a blanket waiver. LAANC authorizes a specific location, altitude, and time window — not an entire airport vicinity or an indefinite period. Exam questions sometimes imply broader coverage.
Assuming LAANC covers all controlled airspace. It does not. If there is no published UAS Facility Map for a location, LAANC is not available and a manual DroneZone authorization is required.
Believing a LAANC approval overrides a TFR. It does not. TFRs are independent restrictions that supersede any standing airspace authorization, including a current LAANC approval.
Thinking a 0 ft UASFM cell means flight is prohibited entirely. A 0 ft ceiling means no altitude is pre-approved through LAANC's automated system, but a manual authorization request through DroneZone may still be submitted and potentially approved.
Forgetting that LAANC is only for Part 107 operations (and recreational flyers using FAA-recognized community-based organization safety guidelines). Hobbyist flyers using the recreational exception under 49 U.S.C. §44809 use a separate recreational authorization path, though some LAANC providers support both workflows.