Name: FAA Development & Airspace Screen
Creator: FAA Aeronautical Information Services public layers

API access

Your AI client reaches FAA Development & Airspace Screen through one ParcelOps MCP endpoint, so there is no separate key to hold for it and no per-source client to write. Reaching it takes no credentials of your own.

Set up FAA Development & Airspace Screen in Claude, ChatGPT, or Cursor Get every fact on this page as JSON

Where it came from

PublisherFAA Aeronautical Information Services public layers

Sourcehttps://services6.arcgis.com/ssFJjBXIUyZDrSYZ/arcgis/rest/services

API basehttps://services6.arcgis.com/ssFJjBXIUyZDrSYZ/arcgis/rest/services

Docshttps://www.faa.gov/air_traffic/flight_info/aeronav/aero_data

Freshness and coverage

FreshnessScheduled · FAA aeronautical datasets follow their published update cycles.

Places coveredUnited States FAA-published aeronautical features

Time coveredNot declared

CredentialsNo credentials required

What this source cannot tell you

⚠ Anything outside United States FAA-published aeronautical features. A request past that edge comes back empty rather than approximated.
⚠ Which years it spans, because the covered period is not declared.
⚠ Anything FAA Aeronautical Information Services public layers does not publish. ParcelOps returns this source as it stands and never fills a blank field from a different one.
⚠ This is an early proximity screen and does not replace FAA Form 7460 notice analysis, an OE/AAA filing, a determination, survey, obstruction evaluation, or aviation counsel.
⚠ Proposed height is retained as decision context only.

Methods (2)

A method is one call your agent can make against this source.

searchNearby

read

Search one official FAA airport, runway, obstacle, or class-airspace layer near a site.

What you must providedatasetlatitudelongitude

Records returnedairport, runway, obstacle, class-airspace

How to get more resultsoffset (offsetField: offset, limitField: limit)

Coordinate systemEPSG:4326

FreshnessScheduled (source-level)

Input schema

{
  "type": "object",
  "properties": {
    "dataset": {
      "type": "string",
      "enum": [
        "airports",
        "runways",
        "obstacles",
        "class-airspace"
      ]
    },
    "latitude": {
      "type": "number",
      "minimum": -90,
      "maximum": 90
    },
    "longitude": {
      "type": "number",
      "minimum": -180,
      "maximum": 180
    },
    "radiusMiles": {
      "type": "number",
      "minimum": 0.1,
      "maximum": 50
    },
    "proposedHeightAglFeet": {
      "type": "number",
      "minimum": 0,
      "maximum": 5000
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "maximum": 2000
    }
  },
  "required": [
    "dataset",
    "latitude",
    "longitude"
  ],
  "additionalProperties": false
}

⚠ Use formal FAA review for notice and height decisions.

getServiceInfo
read
Return exact layers, update context, fields, and formal FAA review limits.
FreshnessScheduled (source-level)
Input schema
```
{
  "type": "object",
  "properties": {},
  "required": [],
  "additionalProperties": false
}
```

Where this source is used

Texas grid and land screening
Put Texas grid context next to the state parcel record and the site constraints in one screening call.
Land research
Parcel records, ground conditions, and what reaches the property line, for raw and rural land.
Data center siting
Power, water, transport, airspace, and hazard screening for a site before anyone signs anything.
Will a tall structure here need FAA review?

FAA Development & Airspace Screen API and MCP server