LAANC further coordination: when the grid says ask first

LAANC further coordination is what happens when the automated answer is no and a human answer is still possible. Most airspace authorizations near airports resolve in seconds because the requested altitude sits at or below the ceiling published for that grid cell. Ask for more than the cell allows and the automation stops, because nobody has pre determined that the operation is safe. The request does not die there. It moves to a manual queue where the responsible air traffic facility considers it directly.

This article covers what triggers a further coordination request, who is eligible to make one, how far in advance to apply, what the facility is weighing when it reviews the request, and how to plan commercial work around a process that has no guaranteed timeline.

What triggers the manual path

The automated part of the system works from published grid values. Request an altitude at or below the ceiling for your cell and the approval usually returns almost immediately. Request more and you are outside what the facility has pre approved. The FAA's description of the LAANC data exchange sets out the alternative: submit a further coordination request if you need to fly above the designated altitude ceiling in a UAS facility map, up to four hundred feet, applying up to ninety days ahead of the flight, with approval coordinated manually through the FAA and available to Part 107 pilots only.

Three limits sit inside that sentence and each one catches somebody. The ceiling for the process is four hundred feet, which is the ordinary Part 107 limit, so further coordination raises you toward that limit rather than beyond it. The ninety day window is the outer bound for how early you can apply, not a processing time. And recreational flyers are excluded entirely, which means a request that a certificated pilot can make on a job is unavailable to the same person flying for pleasure at the weekend.

Zero cells and the other manual route

Cells published at zero are the common case for further coordination, and they cause confusion because operators read zero as closed. It means no altitude has been pre determined as automatically approvable there, which is a statement about automation rather than about the airspace. Those cells sit under the parts of an approach and departure environment where manned traffic is lowest, so the facility wants to look at the request rather than let software answer it.

There is a second manual route worth distinguishing. Where LAANC is not available for a location at all, or where the operation needs something the process does not cover, the authorization request goes through the FAADroneZone instead and is processed on a much longer timeline. Further coordination sits between instant automation and that slower path: it uses the same LAANC service suppliers and the same request format, and it goes to the same facility, but a person makes the decision. Choosing the right route for the situation is most of the skill. Sending a request through the slower manual path when further coordination would have served costs weeks that the job may not have, and sending one the other way produces a refusal that teaches the crew nothing about whether the operation was ever viable.

What the facility is weighing, and how to help

The reviewer is a controller or facility representative deciding whether an operation at your requested altitude, location, and time creates a conflict with the traffic they manage. Specificity helps them say yes. A request describing a defined area, a narrow time window, a modest altitude above the published ceiling, and a clear operational purpose is easier to approve than one asking for a large area, a whole day, and the maximum altitude available. Operators who routinely get further coordination approvals ask for what the job needs rather than for headroom.

Timing helps too. The ninety day window exists so that scheduled work can be requested well ahead of the date, and requests submitted with days to spare give the facility room to come back with questions or conditions. Approvals frequently arrive with conditions attached, such as a narrowed altitude, a restricted time band, or a requirement to contact the tower before launch. Those conditions form part of the authorization, and an operation that ignores them is flying outside it as surely as one that never applied. A refusal is not the end of the road either, because facilities can provide additional guidance on a denied further coordination request so the operator can adjust the operation and resubmit it.

Planning commercial work around an uncertain timeline

The awkward property of further coordination is that it has no guaranteed turnaround. Automated approvals are effectively instant, DroneZone authorizations run on a long published horizon, and further coordination sits in between with a timeline that depends on the facility and its workload. Programs that commit to a client date on the assumption of a quick answer discover the exposure the first time a facility takes three weeks. Programs that build the request into the project schedule at the point of quotation rarely feel it.

That means the request has to become a tracked artifact rather than a message someone sent. The submission date, the requested area and altitude, the response, any conditions attached, and the flights conducted under it belong together, because the question that arrives later is always which authorization a given flight relied on. A program running dozens of sites cannot answer that from an inbox, and clients in regulated sectors increasingly ask for the authorization reference alongside the deliverable. Utilities and infrastructure owners in particular treat the reference as part of the accepted work product, which means a missing one can hold up an invoice as easily as a missing image.

Common mistakes with further coordination requests

Reading a zero cell as a closed airspace. Zero means no pre determined approvable altitude, and further coordination exists for exactly those locations. Operators who stop at the automated refusal leave lawful work unquoted.

Treating the ninety day window as a processing estimate. Ninety days is how early you may apply, not how long it takes. There is no guaranteed turnaround, which is why early submission is the only real mitigation.

Asking for more than the job needs. Wide areas, long time windows, and maximum altitudes make approval harder. Requests scoped to the actual deliverable clear more often and faster.

Ignoring attached conditions. Approvals commonly arrive narrowed or conditioned. The conditions are part of the authorization, and flying outside them is flying without it.

Assuming recreational flyers can use it. Further coordination is available to Part 107 pilots only. The same person flying recreationally at the same site has no equivalent route.

FAQ

What is a further coordination request?

It is a manual airspace authorization request used when the altitude needed sits above the ceiling published for a UAS facility map grid cell. The responsible FAA facility reviews it rather than the automated system.

How far in advance can I submit one?

Up to ninety days before the flight. That is the outer limit for submission rather than an indication of processing time, and earlier submission gives the facility room to ask questions.

Can recreational flyers request further coordination?

No. The process is available to Part 107 certificated pilots only, so a recreational flyer needing an altitude above the published ceiling for a grid cell has no equivalent path through the automated system.

How high can further coordination take me?

Up to four hundred feet, which is the standard Part 107 altitude limit. The process raises you toward that limit from a lower published ceiling rather than authorising flight above it.

Closing thought

Further coordination is the part of the airspace system most likely to be left unused by operators who assume the automated answer is the only answer. It exists because grid values are conservative defaults rather than judgments about a specific operation, and a specific operation described precisely can be approved where a generic one cannot. The cost of using it is lead time and a properly scoped request. The cost of not using it is quoting only the work the automation happens to allow.

If you are booking work that needs approval before a date, FlybyOps was built for the operational record problem at the center of regulated drone work. A project and job hierarchy that scopes work by site, a document vault holding authorizations and their conditions with expiration tracking, per flight records tied to the approvals behind them, and an append-only audit log are all part of how the platform keeps every request, refusal, and approval dated against the operation it governed.