The delay board · off the FAA’s own status file
Which airports are delayed.
Right now, in the FAA’s words.
The Federal Aviation Administration publishes one small document that says where the National Airspace System is hurting: which airports are under a ground stop, which are running a ground delay programme and by how much on average and at worst, where arrivals or departures are late and whether that is getting better or worse, and which fields are closed and why. This page lays that document out as a board — red for a stop or a closure, amber for a delay — and prints the FAA’s own update time beside it.
Every duration, reason, trend and NOTAM is the FAA’s string as written. The upstream sends no CORS headers, so the page asks a thin relay on its own origin, which asks the FAA every two minutes at most and hands the parsed file back. A quiet board — a file with nothing in it — is the commonest thing the FAA publishes, and it is drawn here as the state it is.
119 airports on the register, Canada included · four kinds of programme · a read every 2 minutes · the FAA’s update time printed · nothing interpreted
The board
Every programme in force.
Ground stops first, then closures, then ground delay programmes with their average and maximum delay, then arrival and departure delays with the FAA’s trend. The chips count the file; the stamp says when the FAA last wrote it and how long ago that was by your clock.
The FAA’s file
waiting for the FAA
Reading the FAA’s file…
Not read yet.
The map
Where the trouble is.
Every airport on the register is a dot; the ones the FAA names are lit — red for a stop or a closure, amber for a delay — and carry their code. Click a lit dot and the board scrolls to its tile.
The register, plotted
Longitude scaled by the cosine of the mid-latitude; graticule every ten degrees.
The register
119 airports, each with its answer.
The FAA’s Core 30, the rest of the fields its status board reports on, the reliever and resort airports that turn up in its closure and ground-stop lists, and the Canadian airports it names when a US-bound programme covers them. The file is the authority: an airport it names that is missing here still gets its tile, marked as off the register.
Airports
The register fills once the FAA’s file has been read.
About
A board, not a forecast.
The source is the FAA’s National Airspace System status feed at nasstatus.faa.gov — a two-kilobyte XML document the agency rewrites roughly every minute, listing ground stops, ground delay programmes, general arrival and departure delays and airport closures. It is keyless and open, but it sends no CORS headers, so a browser cannot read it directly. This page asks a relay on its own origin; the relay has one hardcoded upstream, takes no parameters at all, keeps a two-minute file cache, parses the XML and hands the page JSON. It can fetch nothing else.
Nothing is interpreted. “6 hours and 24 minutes” is printed as the FAA wrote it, not converted; “WX:Wind” is printed with the plain word for the prefix beside it, never instead of it; a NOTAM is printed whole. The trend on a delay is the FAA’s field, not a slope this page computed. The only figures of this page’s own making are counts of entries and the age of the FAA’s update time against your clock — and the register’s coordinates, which are published airport reference points rounded to a hundredth of a degree, enough to place a dot.
This says what the FAA says about airports; it does not say whether your flight is late, and an airline’s own board is the place for that. A closure in this file is often a NOTAM restricting general aviation, not a shut airport, which is why the NOTAM text is printed rather than summarised. If the relay cannot reach the FAA it serves its last good copy marked stale, and if it has none it says so; nothing is invented in between. Nothing is stored anywhere but this browser and the relay’s cache file. Questions and corrections: labs@labs.llc.