FAA APInasstatus.faa.gov ↗
Real-time FAA National Airspace System data: airport delays, ground stops, closures, reroutes, EDCTs, and airspace flow programs across 14 endpoints.
What is the FAA API?
The FAA NAS Status API exposes 14 endpoints covering real-time National Airspace System conditions, including active ground stops, ground delay programs, airport closures, en-route restrictions, and reroute advisories. The get_airport_event_details endpoint returns per-airport fields like groundStop, groundDelay, arrivalDelay, departureDelay, airportConfig, and deicing for any FAA or ICAO airport code. The get_edct_lookup endpoint resolves Expected Departure Clearance Times by callsign, departure, and arrival airport.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/50079e35-59ba-45b3-8c45-cb01899253ef/get_airport_status_xml' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace nasstatus-faa-gov-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: FAA NAS Status SDK — real-time airspace status, bounded and typed."""
from parse_apis.faa_nas_status_api import FAAStatus, ViewFormat, AirportNotFound
faa = FAAStatus()
# Get NAS-wide status summary — counts of active events by type.
summary = faa.airports.status_summary()
print(summary.active_airport_events_count, summary.ground_stops_count)
print(summary.affected_airports)
# Fetch detailed status for a specific airport by code.
try:
airport = faa.airports.get(airport_code="EWR")
print(airport.airport_code, airport.airport_long_name)
print(airport.ground_stop, airport.arrival_delay, airport.deicing)
except AirportNotFound as exc:
print(f"No events for airport: {exc.airport_code}")
# List normalized airport events — limit caps total items iterated.
for event in faa.airports.list_events(limit=3):
print(event.airport, event.event, event.reason)
# Get current reroute advisories.
reroute_report = faa.reroutereports.get()
print(reroute_report.count, reroute_report.last_updated)
for reroute in reroute_report.reroutes:
print(reroute.name, reroute.constrained_area)
# Get forecast events from the operations plan.
forecast = faa.forecasts.get()
print(forecast.link)
# Combined status view using the ViewFormat enum.
status = faa.airports.status_by_view(view=ViewFormat.TILE)
print(status.view, len(status.airport_events))
print("exercised: status_summary / airports.get / list_events / reroutereports.get / forecasts.get / status_by_view")
Fetch airport status data from the FAA XML feed, including delay types and airport closure information. Returns a structured representation of the XML feed with update timestamp and delay/closure entries.
No input parameters required.
{
"type": "object",
"fields": {
"Delay_types": "array of delay type objects, each with Name and Airport_Closure_List",
"Update_Time": "string with timestamp of last update"
},
"sample": {
"data": {
"Delay_types": [
{
"Name": null,
"Airport_Closure_List": [
{
"ARPT": "JFK",
"Start": "Jun 08 at 18:17 UTC.",
"Reason": "!JFK 06/106 JFK AD AP CLSD TO TRANSIENT GA ACFT EXC 24HR PPR +1 (555) 012-3456",
"Reopen": "Jul 20 at 03:59 UTC."
}
]
}
],
"Update_Time": "Wed Jun 10 09:43:33 2026 GMT"
},
"status": "success"
}
}About the FAA API
Airport Event Data
get_active_airport_events returns all airports currently experiencing NAS events, with fields including Event (one of Ground Stop, Ground Delay Program, Airport Closure, Free Form, or None), AAR (arrival acceptance rate), Avg_Delay_POE, Scope, Reason, and runway configuration strings for arrivals and departures. For a focused drill-down, get_airport_event_details accepts an airport_code parameter (e.g., JFK, SFO, DCA) and returns a structured object with each event type as its own sub-object — or null when that event type is not active. The get_nas_status_summary endpoint aggregates counts for all event categories, including ground_stops_count, ground_delay_programs_count, arrival_delays_count, departure_delays_count, airport_closures_count, deicing_count, and the list of affected_airports.
En-Route and Flow Program Events
get_active_en_route_events returns the current count and event array for restrictions like miles-in-trail and airspace flow programs. The array may be empty during periods of low congestion. get_airspace_flow_programs isolates active AFPs specifically. get_current_reroutes returns structured reroute advisories with name, constrained_area, valid_time, and advisory text fields, plus a last_updated timestamp. All three endpoints reflect real-time NAS conditions.
Planning and Forecast Data
get_forecast_events pulls from the FAA operations plan, returning terminalPlanned and enRoutePlanned arrays — each item carries a time and event description — alongside a link to the full advisory. get_atcscc_announcements returns free-text announcements from the Air Traffic Control System Command Center. The raw get_airport_status_xml endpoint exposes the underlying FAA XML feed parsed into Delay_types (with Name and Airport_Closure_List per type) and an Update_Time string.
Combined and EDCT Endpoints
get_status_by_view accepts an optional view parameter (list, tile, or map) and returns both airport_events and enroute_events arrays in one call — useful for dashboard-style consumers. get_edct_lookup requires callsign, dept, and arr parameters and returns raw_text with the Expected Departure Clearance Time result for that specific flight. This is the only flight-specific (rather than airport- or system-level) query the API supports.
The FAA API is a managed, monitored endpoint for nasstatus.faa.gov — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when nasstatus.faa.gov changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official nasstatus.faa.gov API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Alert flight operations teams when
get_ground_stopsreturns a non-empty array affecting their hub airports. - Display per-airport delay widgets using
arrivalDelayanddepartureDelayobjects fromget_airport_event_details. - Build a pre-departure checklist tool that checks
get_edct_lookupby callsign before push-back. - Monitor nationwide deicing activity counts via the
deicing_countfield inget_nas_status_summary. - Feed
get_current_reroutesdata into dispatch systems to flag active constrained areas and valid times. - Aggregate
get_forecast_eventsterminal and en-route planned events into a daily briefing digest. - Track ground delay program progression over time using
Avg_Delay_POEfromget_active_airport_events.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does nasstatus.faa.gov have an official developer API?+
What does `get_airport_event_details` return when a specific event type is not active for an airport?+
groundStop, groundDelay, arrivalDelay, departureDelay, airportClosure, airportConfig, and deicing — is returned as null when that condition is not currently active. If the airport has no active events at all, the endpoint returns a stale_input indicator rather than a fully populated object.Can I look up historical NAS delays or past ground stop events?+
Does the API cover international airports or only US airspace?+
What is the freshness of the data returned by these endpoints?+
get_airport_status_xml endpoint includes an Update_Time field reflecting when the FAA feed was last updated. get_current_reroutes includes a last_updated timestamp. Other endpoints reflect the NAS state at time of request; during low-traffic periods, event arrays (e.g., get_active_en_route_events, get_ground_stops) may return empty results rather than stale data.