Drone airspace authorization when LAANC is not an option

Drone airspace authorization is the FAA's permission to fly in controlled airspace, and most of the time it arrives through LAANC in seconds. This article is about the other times: the airports LAANC does not cover, the requests it cannot approve automatically, and the operations where a pilot falls back to the manual process. When the automated path is closed, authorization still exists. It just runs slower and demands more planning.

The gap matters because a program that only knows the automated path treats a non-LAANC site as impossible, when it is merely slower. This article covers when LAANC is not an option, how the manual authorization process works through the FAA's DroneZone, how long it takes, and how a program tracks authorizations so the right pilot flies the right job under the right clearance.

When LAANC is not an option

LAANC covers a large share of controlled airspace, but not all of it, and several situations push a request off the automated path. The most common is an airport that is not LAANC-enabled, where no near-real-time option exists and every authorization is handled manually. Another is a request that sits above what the pre-approved parameters allow and beyond what a further coordination request can resolve.

Some operations fall outside LAANC by their nature. Anything that also needs a waiver, such as certain operations over people or beyond standard limits combined with controlled-airspace access, has to go through the manual channel where the waiver and the authorization are considered together. Recognizing which situation applies is the first planning step, because it determines the timeline the whole job has to work around.

The manual authorization process

When LAANC is not available, authorization runs through the FAA's Part 107 airspace authorization process in the FAADroneZone. A pilot logs in, creates an authorization request, and provides the operation's details: the location and airspace, the dates and times, the frequency of flights, and the maximum altitude requested. The request is then reviewed by hand at an FAA Service Center rather than approved by software.

The review is a real evaluation, not a formality. Requests at or below the mapped altitude for a location are approved at the Service Center, while requests above the mapped altitude but still under 400 feet are coordinated by the Service Center with the air traffic facility that manages the airspace. Because a person is assessing each request, the detail and accuracy of the submission matter: a vague description invites questions and delay, and a precise one moves faster.

How long manual authorization takes

The manual process trades speed for reach, and the timeline is the part programs underestimate. Where LAANC returns a decision in seconds, a manual authorization can take weeks, and the FAA advises submitting requests well ahead of the operation, commonly at least 60 days before the planned date. Requests submitted late risk cancellation or denial, and authorizations are handled on a first-come, first-served basis.

That timeline reshapes how a job gets scheduled. A client asking for a controlled-airspace flight at a non-LAANC site next week is asking for something the manual process may not deliver in time. Building the authorization lead time into the project from the start, rather than discovering it when the request is filed, is the difference between a job that flies and one that slips. Programs that handle non-LAANC sites regularly keep a standing sense of the lead time each airspace tends to require.

The responsible party and documentation

A manual authorization names a responsible party for the operation, and that role carries real weight. The responsible party does not have to hold a remote pilot certificate, but they are accountable for the safety of the overall operation and for documenting the pilots and the make and model of every aircraft flown under the authorization. In a program, this is usually a chief pilot or operations lead rather than the individual flying on the day.

The documentation obligation is easy to overlook and important to keep. An authorization that covers multiple flights over a period still requires the operation to track which pilots flew and which aircraft were used under its terms. That record is part of what makes the authorization defensible, and it is far easier to maintain as flights happen than to reconstruct if the FAA or an insurer asks who was operating under a given authorization.

Tracking authorizations across a program

Once a program holds more than a couple of authorizations, keeping them straight becomes its own task. Each authorization applies to a specific location, altitude, and window, and flying outside those terms is the same violation as flying with no authorization at all. A program needs to know, at a glance, which jobs are covered by which authorization and when each one expires.

Access is part of keeping that straight. When authorizations attach to specific jobs and the platform is set up for confining each pilot to the jobs they are assigned, a pilot cannot mistakenly fly a job under an authorization that does not cover it, because the uncovered job is not visible to them. An authorization tracked against the job it belongs to, with the right pilot scoped to it, is a control the system maintains rather than a spreadsheet someone has to remember to update.

Common mistakes in drone airspace authorization

Assuming a non-LAANC airport means you cannot fly there. An airport without LAANC still allows authorized flights; the authorization just comes through the slower manual process. Treating the site as off-limits gives up work that is available with enough lead time.

Starting the manual request too late. Manual authorization can take weeks, and late requests risk cancellation or denial. A controlled-airspace job at a non-LAANC site has to be planned around that lead time from the beginning, not when the request is finally filed.

Expecting the manual process to behave like LAANC. A manual authorization is reviewed by a person at an FAA Service Center, not approved instantly by software. Assuming a same-day turnaround sets the whole schedule up to fail.

Naming a responsible party who cannot account for the operation. The responsible party is accountable for the operation's safety and for documenting its pilots and aircraft. Assigning the role to someone who is not tracking those details leaves a gap exactly where the authorization needs a record.

Letting authorizations live in scattered files. An authorization covers only a specific location, altitude, and window. When those terms are buried in an inbox, a pilot can fly a job the authorization never covered, which is the same violation as flying with none.

FAQ

How do I get airspace authorization if LAANC is not available at my airport?

You apply manually through the FAA's DroneZone. You create an authorization request with your location, dates, altitude, and flight frequency, and an FAA Service Center reviews it by hand. The process is slower than LAANC, so submit well ahead of your planned operation.

How long does manual drone airspace authorization take?

It varies, but the FAA advises submitting at least 60 days before the operation, and manual review can take weeks. Requests are handled first-come, first-served, and late submissions risk cancellation or denial, so lead time has to be built into the job from the start.

Who is the responsible party on a drone airspace authorization?

The responsible party is the person accountable for the operation's overall safety and for documenting the pilots and aircraft flown under the authorization. They are not required to hold a remote pilot certificate, and in a program the role usually sits with a chief pilot or operations lead.

Can I get authorization to fly above the UAS Facility Map ceiling?

Yes, up to 400 feet. Requests above the mapped altitude are coordinated by the FAA Service Center with the air traffic facility that manages the airspace, whether you apply manually or through a LAANC further coordination request. Approval is not guaranteed and depends on the airspace involved.

Closing thought

Drone airspace authorization does not disappear when LAANC is unavailable; it just moves to a slower, manual channel that rewards planning. The airports LAANC does not reach, and the requests it cannot handle automatically, are all workable through the FAADroneZone if a program starts early, submits a precise request, names a responsible party who can account for the operation, and tracks each authorization against the job it covers. Handled that way, a non-LAANC site is a scheduling constraint rather than a closed door.

If you are flying in controlled airspace where LAANC is not an option, FlybyOps was built for the operational record problem at the center of regulated drone work. A project and job hierarchy with map-based scoping, a document vault that tracks authorizations and their expirations, role-based access control, and an append-only audit log are all part of how the platform keeps every authorization matched to the pilot cleared to use it.