US Airport Delays & Weather API - FAA Status, METAR, TAF

Is my airport delayed right now, and will it be in the next hours? This API answers that for any US airport in one call: official FAA ground stops, ground delay programs, arrival/departure delays and closures, plus NOAA METAR/TAF weather and a delay-risk level. No API key, no login, no proxy: official FAA and NOAA data.

What makes it different: history. Our server polls the FAA National Airspace System status every 5 minutes and stores every delay event with its start, end and duration. Ask "how many ground stops did ORD have in the last 30 days?" or "how long did the SAN ground delay program last?". On-demand scrapers cannot backfill that.

What you get

Mode	Returns
status (default)	One row per chosen airport (default: every US airport with an active FAA delay, ground stop or closure plus the 10 busiest): normal/delayed, ground stop, ground delay program (avg/max delay), arrival/departure delays, full closures, METAR now, TAF outlook, delay risk with reasons, local time
delays	Every US airport with an active FAA delay or ground stop right now
history	Past FAA delay events: airport, type, reason, first seen, ended, minutes, avg/max delay
summary	One row per airport over N days: events, ground stops, ground delay programs, disrupted minutes, longest event, worst delay, top reasons

• Codes: IATA/FAA (JFK, ORD, SJU) or ICAO (KJFK, PHNL, PANC).
• Partial NOTAM closures (for example "closed to non-scheduled general aviation") are hidden by default, so normal airline operations are not reported as closed. Turn them on with includeClosures.
• Only new / changed mode with monitorId: schedule it every 5-15 minutes and get a row only when an airport's delay starts, changes or clears. Good for Slack/Telegram/n8n alerts.
• Unknown codes return a row with status: "unknown airport code" instead of failing the run.

Example output (status)

{
  "airport": "SAN", "icao": "KSAN", "name": "SAN DIEGO INTL", "state": "CA",
  "status": "delayed", "groundStop": false, "groundDelayProgram": true, "maxDelayMinutes": 88,
  "faaEvents": [{"event": "ground_delay", "reason": "airport volume", "avgDelayMinutes": 26, "maxDelayMinutes": 88}],
  "delayRisk": "high", "delayRiskReasons": ["FAA ground delay program (avg 26 min)"],
  "weatherNow": {"flightCategory": "VFR", "windSpeedKt": 8, "windGustKt": null, "ceilingFt": null, "raw": "METAR KSAN ..."},
  "forecast": {"hours": 12, "worstFlightCategory": "MVFR", "significantWeather": [], "raw": "TAF KSAN ..."},
  "localTime": "2026-11-08T08:06:46-0800"
}

Use it from code or an AI agent

curl -X POST "https://api.apify.com/v2/acts/martin10291~airport-delays-weather/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode": "status", "airports": ["JFK", "ORD", "ATL"]}'

History of ground stops and delay programs at Chicago O'Hare in the last 30 days:

{"mode": "history", "airports": ["ORD"], "days": 30, "eventTypes": ["ground_stop", "ground_delay"]}

AI agents (Claude, ChatGPT, Cursor, n8n) can call it as a tool through the Apify MCP server: https://mcp.apify.com/?actors=martin10291/airport-delays-weather.

Sources and limits

• FAA NAS Status (nasstatus.faa.gov) public feed: airport-level programs, not individual flights. For flight-by-flight status use a flight data API.
• Weather: NOAA Aviation Weather Center (aviationweather.gov) METAR/TAF.
• delayRisk is a simple, transparent heuristic (FAA programs + IFR/LIFR, thunderstorms, snow, strong wind in the TAF window), not a prediction model. The reasons are always listed.
• Our history archive starts on 2026-11-08 and grows every 5 minutes; every answer says where it starts.
• Pricing: $1.00 per 1,000 rows. No row is charged when the run fails.

Related: Airport Database API - IATA, ICAO, Flight Distance, METAR for airport lookups, distances and flight times.

FAQ

How fresh is the data? Live modes read the FAA feed and NOAA weather at run time (the FAA feed updates every minute or two). History is polled every 5 minutes.

What if no airport is delayed? delays mode returns 0 rows and a note in RUN_SUMMARY (calm weather is normal, not an error). status mode always returns your airports with status: "normal".

What happens on errors? A bad code gives a row with status: "unknown airport code"; a wrong option ends the run with a clear message; if FAA or NOAA is down the run stops cleanly and nothing is charged. RUN_SUMMARY always has lastError.

Does it cover flights? No: the FAA feed is per airport (programs and average/max delays). It is the official source airlines and dispatchers use for ground stops.