Requesting Authorization Through the FAA DroneZone
When LAANC can't automatically approve a request ? because the location has no LAANC coverage, or because the requested altitude exceeds the local UAS Facility Map ceiling ? a manual airspace authorization request through FAA DroneZone is the alternative. This closing lesson of the module covers exactly when that manual pathway is needed and how its timeline compares to LAANC's near-instant approval.
When a manual DroneZone request is needed instead of LAANC
FAA DroneZone provides manual airspace authorization requests for situations LAANC cannot handle automatically: airports or locations without LAANC coverage, requests for an altitude above the applicable UAS Facility Map grid cell's ceiling, and certain more complex or non-standard operations that fall outside what LAANC's automated system is designed to evaluate. Every request submitted through DroneZone is processed manually by FAA Air Traffic Service Center staff ? there is no automated near-real-time approval path here, unlike LAANC.
Processing time: plan for weeks, not minutes
Because DroneZone airspace requests require human review rather than automated grid-cell matching, processing takes considerably longer than LAANC ? commonly cited guidance recommends submitting a request at least 60 days before the planned operation, and actual review time can range from several weeks up to around 90 days depending on the complexity of the request and the specific FAA Service Center handling it. A request filed too close to the planned flight date risks being denied or effectively unusable simply due to timing, independent of whether the underlying request would otherwise have been approved.
DroneZone's broader role beyond authorization
FAA DroneZone is a multi-purpose FAA portal ? the same system used for aircraft registration (Module 2, Lesson B) and Part 107 waiver applications (Module 2, Lessons Q and R) also handles manual airspace authorization requests. Recognizing DroneZone as the shared FAA system behind several distinct Part 107 processes, rather than a single-purpose tool, helps make sense of why it appears repeatedly across different parts of this course.
Real-world scenario: a tall-structure inspection exceeding the LAANC ceiling
A pilot is contracted to inspect the upper sections of a 500-foot broadcast tower located within a Class D airport's boundary, where the applicable UAS Facility Map grid cell has a LAANC ceiling of only 300 feet AGL. Recall from Module 2's structure exception (14 CFR 107.51(b)) that flying up to 500 + 400 = 900 feet AGL near this specific tower would be permitted under the base altitude rule ? but the LAANC grid ceiling of 300 feet still caps what can be auto-approved for 107.41 purposes at this location. Since the planned altitude exceeds that LAANC ceiling, the pilot submits a manual DroneZone request more than 60 days ahead of the planned inspection date, rather than assuming LAANC could handle it.
| Feature | LAANC | FAA DroneZone (manual) |
|---|---|---|
| Review type | Automated, grid-based | Manual, human-reviewed |
| Typical speed | Near real-time | Several weeks up to ~90 days |
| When used | Altitude at or below the grid ceiling, at a covered airport | No LAANC coverage, or altitude above the grid ceiling |
| Recommended lead time | Same day generally workable | At least 60 days |
Submitting a manual DroneZone airspace authorization request
Start this process well before you need the authorization.
Confirm LAANC genuinely cannot handle the request
Check for LAANC coverage at the location and compare the planned altitude against the UAS Facility Map ceiling before assuming a manual request is necessary.
Submit the request through FAA DroneZone with complete details
Include the exact location, requested altitude, operation dates/times, and purpose of the flight.
Submit at least 60 days before the planned operation
Manual review takes considerably longer than LAANC's automated process.
Monitor the request status and plan the mission timeline around approval, not before it
Do not commit to a client deadline that depends on an authorization that hasn't been granted yet.
| Mistake | Why it happens | Correct understanding | Regulation / source |
|---|---|---|---|
| "DroneZone approves requests just as fast as LAANC." | Assuming both systems work the same way since they're both FAA-run | DroneZone requests are manually reviewed and can take weeks to months, unlike LAANC's near-real-time automated approval. | FAA DroneZone processing guidance |
| "DroneZone is only for aircraft registration." | Remembering only the registration use case from Module 2 | DroneZone also handles manual airspace authorization requests and Part 107 waiver applications. | FAA DroneZone system scope |
How far in advance should I submit a DroneZone airspace authorization request?
At least 60 days before the planned operation is commonly recommended, since manual review can take considerably longer than LAANC.
Why would I need DroneZone instead of LAANC?
When the location has no LAANC coverage, or the requested altitude exceeds the applicable UAS Facility Map grid cell's ceiling.
Is FAA DroneZone only used for airspace authorization?
No, it's also used for aircraft registration and Part 107 waiver applications ? a shared portal across several distinct FAA processes.
Test Your Knowledge
Answer the questions below to check your understanding. Every answer can be found in the lesson above.