Sourced developments at US airports: what the FAA reports at every airport, and what we measure and our model forecasts at the busiest ones.
Live · checked FAA national advisories 3 minFAA NAS status 1 minForecast cycle 62 minLightning 1 minWeather observations 3 minFAA surface data 1 minFAA flight data 1 min
The FAA issued this advisory: “EVENT TIME: 13/2030 - 14/0500 THE ATCSCC HAS ACTIVATED THE DIVERSION RECOVERY TOOL FOR ALL AIRPORTS. CUSTOMERS SHOULD ENSURE THAT DVRSN IS INCLUDED IN FLIGHT PLAN REMARKS OF DIVERTED AIRCRAFT. NOTE THAT IF THERE IS A GROUND DELAY PROGRAM OR GROUND STOP IN EFFECT FOR THE DESTINATION AIRPORT DIVERTED FLIGHTS ARE NOT AUTOMATICALLY EXEMPT AND WILL STILL RECEIVE AN EDCT. UNLESS OTHERWISE NOTIFIED, DIVERSION RECOVERY WILL CLOSE AT THE END OF THE EVENT TIME SPECIFIED IN THIS ADVISORY.” This is an advisory bulletin; its text defines the affected flights and time period.
The airport closure at Providence (PVD) no longer appears in the FAA’s airport status as of 3:52 PM EST, in 4 consecutive successful checks. It was first listed at 12:16 AM EST.
The FAA’s airport status lists a ground delay program for flights to SFO (SFO), citing “wind”; it gives an average delay of 138 min and a maximum of 690 min. Departures to SFO are given later takeoff times at their origin airports.
The FAA’s airport status lists a ground delay program for flights to San Diego (SAN), citing “airport volume”; it gives an average delay of 34 min and a maximum of 81 min. Departures to SAN are given later takeoff times at their origin airports.
The FAA’s airport status lists a ground delay program for flights to LaGuardia (LGA), citing “wind”; it gives an average delay of 45 min and a maximum of 166 min. Departures to LGA are given later takeoff times at their origin airports.
The FAA’s airport status lists a ground delay program for flights to Boston (BOS), citing “airport volume”; it gives an average delay of 26 min and a maximum of 103 min. Departures to BOS are given later takeoff times at their origin airports.
The airport closure at Melbourne (MLB) no longer appears in the FAA’s airport status as of 8:59 AM EST, in 4 consecutive successful checks. It was first listed at 4:18 PM EST.
What changed: ground delay program no longer listed
The ground delay program for flights to Fort Lauderdale (FLL) no longer appears in the FAA’s airport status as of 11:16 PM EST, in 4 consecutive successful checks. It was first listed at 1:36 PM EST.
What changed: ground delay program no longer listed
The ground delay program for flights to Miami (MIA) no longer appears in the FAA’s airport status as of 11:00 PM EST, in 3 consecutive successful checks. It was first listed at 6:59 PM EST.
What changed: ground delay program no longer listed
The ground delay program for flights to San Diego (SAN) no longer appears in the FAA’s airport status as of 5:41 PM PST, in 4 consecutive successful checks. It was first listed at 5:44 AM PST.
The airport closure at Providence (PVD) no longer appears in the FAA’s airport status as of 4:59 AM EST, in 3 consecutive successful checks. It was first listed at 12:15 AM EST.
What changed: ground delay program no longer listed
The ground delay program for flights to SFO (SFO) no longer appears in the FAA’s airport status as of 8:09 PM PST, in 4 consecutive successful checks. It was first listed at 6:58 PM PST.
The airport closure at Salina (SLN) no longer appears in the FAA’s airport status as of 9:59 PM CST, in 3 consecutive successful checks. It was first listed at 12:00 PM CST.
What changed: ground delay program no longer listed
The ground delay program for flights to Las Vegas (LAS) no longer appears in the FAA’s airport status as of 5:32 PM PST, in 4 consecutive successful checks. It was first listed at 2:56 PM PST.
What changed: ground delay program no longer listed
The ground delay program for flights to Fort Lauderdale (FLL) no longer appears in the FAA’s airport status as of 6:00 PM EST, in 4 consecutive successful checks. It was first listed at 11:43 AM EST.
The airport closure at Salisbury (SBY) no longer appears in the FAA’s airport status as of 5:59 AM EDT, in 3 consecutive successful checks. It was first listed at 11:00 PM EDT.
What changed: ground delay program no longer listed
The ground delay program for flights to Phoenix (PHX) no longer appears in the FAA’s airport status as of 4:24 PM MST, in 3 consecutive successful checks. It was first listed at 2:19 PM MST.
What changed: ground delay program no longer listed
The ground delay program for flights to San Diego (SAN) no longer appears in the FAA’s airport status as of 2:59 PM PDT, in 3 consecutive successful checks. It was first listed at 7:03 AM PDT.
The airport closure at Orange County (SNA) no longer appears in the FAA’s airport status as of 12:33 PM PDT, in 3 consecutive successful checks. It was first listed at 11:31 PM PDT.
The airport closure at LaGuardia (LGA) no longer appears in the FAA’s airport status as of 5:59 AM EDT, in 3 consecutive successful checks. It was first listed at 12:15 AM EDT.
What changed: ground delay program no longer listed
The ground delay program for flights to Las Vegas (LAS) no longer appears in the FAA’s airport status as of 11:31 PM PDT, in 3 consecutive successful checks. It was first listed at 4:00 PM PDT.
What changed: ground delay program no longer listed
The ground delay program for flights to San Diego (SAN) no longer appears in the FAA’s airport status as of 8:30 PM PDT, in 3 consecutive successful checks. It was first listed at 3:45 PM PDT.
What changed: ground delay program no longer listed
The ground delay program for flights to San Diego (SAN) no longer appears in the FAA’s airport status as of 1:15 PM PDT, in 4 consecutive successful checks. It was first listed at 7:29 AM PDT.
Older items
Each item is the latest update matching your filters; the event’s current status is on its chip. All updates shows the full chronological wire.
Confirmed
An official source (the FAA) reports it. We attribute it; we don’t independently verify it.
Observed
We measured it from FAA flight data: window, sample size and the typical level are on the item.
Forecast
Our model predicts it, with its probability, target, horizon and model version. It has not happened. How accurate is it?