Four services, one airspace API
Query airspace, check real-time restrictions and LAANC eligibility, and hand the authorization to AutoPylot when your user needs one.
Airspace Data API
Controlled airspace classes, UAS Facility Map grid ceilings, airports, national security flight restrictions, special use airspace, the Washington DC FRZ, and airspace schedules — sourced from authoritative FAA datasets and refreshed within FAA-required windows.
I want this →Real-time restrictions
TFRs and stadium event restrictions, updated within minutes. Query a point, a radius, or a custom polygon.
I want this →LAANC Eligibility Check
Our LAANC API tells your users before they plan whether a flight qualifies for automatic approval, needs Further Coordination, or isn’t eligible — and why — based on flight area, altitude, date, time, and duration.
I want this →LAANC Handoff
One link sends the pilot from your app into AutoPylot with the flight area pre-loaded. The pilot completes the authorization in AutoPylot, then returns to your app. No FAA certification on your side.
I want this →State & local drone rules layer
State parks, county, and municipal drone restrictions — the data the FAA doesn’t publish.
I want this →Historical airspace
What the airspace, restrictions, and TFRs were at a specific place and time. For insurance, audits, and flight records.
I want this →Three steps. No certification on your side.
The pilot draws a flight area. Call the eligibility endpoint, then create a handoff link.
The link opens their AutoPylot app with the flight area already drawn — nothing to re-enter. They request the LAANC authorization right there.
Opens in the AutoPylot iOS and Android app — not a web portal.
The pilot returns to your product and keeps planning the mission where they started.
{ "area": { … }, "max_altitude_ft": 150, "start_time": "2026-10-02T14:00:00-04:00", "return_url": "yourapp://flights/1234" }
{ "claim_url": "https://go.autopylot.io/h/7Kx2…", "expires_at": "2026-10-01T14:00:00-04:00" }
Your app gets a link. The authorization stays with the pilot in AutoPylot — no status or reference codes come back to your app.
Boring in the right places
One airspace API for the data, one LAANC API path for authorization — both predictable, both documented field by field.
Who this is for
If your users plan, dispatch, or log drone work in U.S. airspace, this is the layer underneath.
Flight logging apps
Pilots leave your app to check airspace and get LAANC — and don’t always come back.
With AutoPylot: Airspace context on every planned and logged flight, plus a one-tap LAANC handoff that returns the pilot to your app.
This is us →Fleet & enterprise ops
Crews find out a site needs authorization when they’re already on site.
With AutoPylot: Check every job site against airspace, TFRs, and LAANC eligibility before dispatch — and flag jobs that need Further Coordination while there’s still time (requests must be in 72+ hours ahead).
This is us →Inspection & mapping
Survey areas get quoted before anyone checks the grid ceiling.
With AutoPylot: Validate survey polygons against UAS Facility Map ceilings while scoping, so the altitude and timeline you sell is one the pilot can fly.
This is us →Drone service marketplaces
Jobs get booked in airspace pilots can’t fly on the requested date.
With AutoPylot: Screen every job request at booking — flyable, needs authorization, or needs Further Coordination — before it reaches a pilot. Then hand the pilot to LAANC in one tap.
This is us →Construction & energy platforms
Your users schedule drone inspections and surveys in your platform, then check airspace somewhere else.
With AutoPylot: Airspace, restrictions, and LAANC eligibility on the job or work order itself — so a flight that needs authorization is flagged when it’s scheduled, not on the day.
This is us →Work order, ERP & CRM systems
Drone work sits inside jobs, tickets, and deals that know nothing about airspace.
With AutoPylot: One call returns airspace and eligibility for a job site address or polygon. Add a “Get LAANC” action to any record.
This is us →Insurance & risk
Underwriters and adjusters can’t easily verify the airspace a flight was flown in.
With AutoPylot: Airspace, restrictions, and TFRs for a specific place and time — for underwriting and claims review.
This is us →Frequently asked
01Is the API available now?
No. It’s in early access and we’re onboarding a limited set of partners while we finalize the endpoints.
02What happens after I request access?
We review every request and reply within 2 business days to set up a short call.
03Do we need to become an FAA-approved provider?
No. The handoff is designed so your app never handles LAANC authorization data. AutoPylot, an FAA-approved provider, handles the authorization with the pilot. If you need authorization status inside your own app, that’s a different, FAA-approved integration — tell us and we’ll walk you through it.
04What does my app get back after the pilot requests LAANC?
Your app gets the handoff link and its expiry — nothing about the authorization itself. No reference code, no status, no updates. The pilot completes the request in AutoPylot, and the return link brings them back to where they started in your app.
05Does my user need an AutoPylot account?
Yes. FAA rules require every operator to have their own account with a login, so pilots sign in or create a free AutoPylot account when they open the handoff link.
06Can we show LAANC status in our app?
Not with the handoff. Showing authorization status inside your product requires the FAA’s third-party integration process. Tell us if that’s what you need.
07Where does the data come from?
Authoritative FAA sources, including UAS Facility Maps, airspace and special use airspace datasets, and TFR feeds — refreshed within FAA-required windows.
08Is there a cost?
We’ll share details with early access partners.
09Who owns the data?
Data you send the API is yours — we don’t claim rights to your users’ location data. Separately, pilots who request LAANC in AutoPylot become AutoPylot users, and their authorization data is handled under our privacy policy and FAA requirements, including the FAA’s privacy statement.