Ground stop API for FAA ground stops, delay programmes and closures
DisruptAPI reads FAA National Airspace System status every two minutes and returns each ground stop, ground delay programme, airport closure and arrival or departure delay as a signal with the airport, reason, start time and severity. You can query them, receive them by webhook, or have them matched to your own flights. FAA publishes no developer API for this data, and DisruptAPI keeps the history of past events.
Where the data comes from
| FAA National Airspace System status | Ground stops, ground delay programmes, closures and delays at US airports. Every 2 minutes. |
| FAA ATCSCC advisories | The command centre's advisories for the day, for context on programmes. |
| NOAA Aviation Weather Center | International SIGMETs and METAR reports from about 5,000 airports, for weather at the airport. |
Every source, with its licence and polling interval, is on the data sources page.
How FAA programmes map to DisruptAPI severity
| FAA programme | Subtype | Severity |
|---|---|---|
| Ground stop | ground_stop | severe |
| Airport closure | airport_closure | severe |
| Ground delay programme | ground_delay_program | moderate |
| Arrival or departure delay | airport_delay | minor |
How are these signals matched to my bookings?
A ground stop matches every watched flight that departs from or arrives at the airport while it is in force, and every trip that connects there. Each match names the reason, for example "arrives at EWR during a ground stop". Send items with an exposure check or a watchlist, or receive matches by webhook.
What it does not cover
- FAA programmes cover US airports only. Elsewhere, DisruptAPI uses airport weather, SIGMETs and official warnings.
- It reports the cause, not the status of each flight. Pair it with a flight status feed if you need per-flight delays.
What a signal looks like
Request GET /v1/signals?type=aviation&airport=EWR. Each item in data looks like this (an example):
{
"id": "sig_7f3a2c",
"type": "aviation",
"subtype": "ground_stop",
"provider": null,
"failure_layer": null,
"title": "Ground stop at Newark Liberty (EWR)",
"severity": "severe",
"countries": [
"US"
],
"airports": [
"EWR"
],
"location": {
"lat": 40.69,
"lon": -74.17
},
"starts_at": "2026-11-17T21:05:00Z",
"ends_at": "2026-11-17T22:30:00Z",
"first_seen_at": "2026-11-17T21:06:12Z",
"updated_at": "2026-11-17T21:06:12Z",
"source": {
"url": "https://nasstatus.faa.gov/",
"attribution": "FAA National Airspace System status",
"stale": false
},
"details": {
"reason": "weather / thunderstorms",
"scope": "departures to EWR"
},
"status": "active",
"version": 1,
"areas": []
}Questions
What is the difference between a ground stop and a ground delay programme?
A ground stop holds every affected flight at its origin until it is lifted. A ground delay programme lets flights depart with assigned delays so arrivals match the airport's capacity. A ground stop is the more severe of the two.
Can I get past FAA ground stops?
Yes. Signals are kept after they end, so you can query past events by airport and date. Enterprise plans include bulk history exports.
How quickly does a new ground stop reach my webhook?
FAA status is polled every two minutes, and webhooks are sent as soon as the new signal is stored, so typically within a few minutes of FAA publishing it.
Other signal types
Hear about the disruption before your customers do
Create a key, add the flights, trips and places you want watched, and get a signed webhook whenever a disruption touches one. Try it on a sandbox key first, no card needed.