UAS Facility Maps: how to read LAANC altitude grids

A UAS facility map is the FAA's published answer to the question of how high a drone can be authorized in controlled airspace at a given location. The maps divide the airspace around participating air traffic facilities into a grid, and each cell carries a number in feet above ground level. That number is the ceiling the agency has determined it can approve without additional safety analysis, which makes the maps the single most useful planning tool for anyone scoping work near an airport.

This article covers what the numbers mean and what they do not, how to read a grid before committing to a site, what a zero value implies, and how the maps fit alongside the authorization systems that grant permission. The distinction between information and authorization runs through all of it.

What the numbers on the grid mean

Each cell shows a maximum altitude in feet above ground level, usually one of a small set of values running from zero up to four hundred. The FAA describes the maps plainly: UAS facility maps show the maximum altitudes around airports where the agency may authorise Part 107 operations without additional safety analysis, and they should be used to inform requests for airspace authorizations and waivers in controlled airspace.

The values are not arbitrary. They reflect the local air traffic facility's assessment of where manned traffic operates, which is why the lowest ceilings cluster beneath approach and departure paths and near runway thresholds, and why values rise with distance from the airport until the grid ends at the boundary of controlled airspace. Beyond that boundary the airspace is uncontrolled and the ordinary Part 107 altitude limit applies without any authorization requirement, which is why the edge of the grid is frequently the most useful line on the map for a site planner.

The maps inform requests, they do not grant them

The FAA states the point in capitals on its own page, which suggests how often it is misread. The maps do not authorise operations at the depicted altitudes and are for informational purposes only. Operators must still apply to operate in controlled airspace by submitting an airspace authorization request through LAANC or the FAADroneZone, or a waiver application through the FAADroneZone. A grid showing three hundred feet is a prediction about what will be approved, not the approval.

This matters more than it sounds, because the consequence of confusing the two is flying in controlled airspace without authorization, which is among the deviations that attract real enforcement. The rule requiring prior authorization applies to any operation in Class B, C, D, or surface area E airspace regardless of altitude, so even a flight at fifty feet in a cell marked four hundred needs the authorization. The map answers how high, and only after something else has answered whether.

Reading a grid before committing to a site

The practical workflow starts before a quote goes out. Open the map viewer, find the site, and read the cell the work sits in along with the cells around it, because a job that spans a boundary between a three hundred and a hundred foot cell is governed by whichever cell the aircraft is over at that moment. Compare the ceiling against the altitude the deliverable genuinely needs, which for facade and roof work is often lower than people assume and for tower or stack inspection is frequently higher than the grid allows.

Two site level factors deserve attention at the same moment. Terrain matters because the values are above ground level, so a site in a valley and a site on a ridge inside the same cell present different pictures relative to surrounding obstacles. And the maps are periodically updated on the aeronautical chart production cycle, so a value checked six months ago for a repeat client may have changed. Checking the grid at quotation and again at scheduling costs a minute and prevents the discovery that a promised deliverable was never approvable.

Zero cells, and what the grid does not tell you

A zero value does not mean the airspace is closed. It means the FAA has not pre determined an altitude it can approve automatically there, so an automated request will not clear and the operator needs the manual route or a further coordination request. Zero cells sit where manned traffic operates lowest, which is exactly where an unauthorized drone would matter most, and treating them as a hard no leaves lawful work on the table while treating them as a formality invites the opposite mistake. Operators working repeatedly near one airport learn which of its zero cells tend to be approvable on request and which never are, and that local knowledge is worth writing down rather than carrying in one person's head.

The grid is also silent on everything other than that one altitude question. Temporary flight restrictions, special use airspace, security related restrictions, and local ordinances all sit outside it, and the FAA has said explicitly that operators are responsible for checking those separately rather than assuming an authorization covers them. A site that clears on the facility map can still be unflyable on the day for reasons the map was never designed to show. Treating the grid as one input among several, checked alongside restriction sources at the same point in the planning process, is what stops a clean cell value from creating false confidence about a location.

Common mistakes in reading UAS facility maps

Treating the grid value as permission. The maps inform requests and do not authorise anything. Flying in controlled airspace still requires an authorization obtained through LAANC or the FAADroneZone.

Reading one cell for a site that spans several. The applicable ceiling is the one for the cell the aircraft is over. Jobs that cross a boundary are governed by the lower value for part of the flight.

Assuming a zero cell means never. Zero indicates no pre determined approvable altitude, not a prohibition. Manual requests and further coordination exist precisely for those locations.

Checking the map once. Values are revised on the chart production cycle. A grid confirmed at the time of a quote should be confirmed again before the crew travels.

Expecting the map to cover other restrictions. Temporary flight restrictions, special use airspace, and security restrictions live elsewhere and are the operator's responsibility to check independently.

FAQ

Does a UAS facility map authorise my flight?

No. The FAA states the maps are informational and do not authorise operations at the depicted altitudes. An authorization request through LAANC or the FAADroneZone is still required for controlled airspace.

What does a zero on the grid mean?

That the FAA has not pre determined an altitude it can approve automatically in that cell. Automated requests will not clear, so the operator needs a manual request or a further coordination request instead.

Are the grid altitudes above ground or sea level?

Above ground level rather than sea level. Terrain therefore changes what a given value means in practice, and two sites inside the same grid cell can present very different clearances relative to the obstacles around them.

How often do the maps change?

They are revised periodically in line with the aeronautical chart production cycle, so a value confirmed months earlier may no longer hold. Rechecking before a crew travels is worth the minute it takes.

Closing thought

The facility map is the cheapest planning tool in commercial drone work and the one most often misused. Read correctly it tells you, before anyone quotes a price, whether the altitude a deliverable requires is one the FAA is likely to approve quickly at that location. Read as permission it produces flights that were never authorized. The habit worth building is to check the grid at the point of scoping, record the value against the job, and confirm it again before the crew leaves.

If you are scoping sites near controlled airspace, 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 on a map, a document vault holding authorizations with expiration tracking, per flight records tied to the jobs they served, and an append-only audit log are all part of how the platform keeps the altitude a job was approved for stored with the job itself.