FlightRecord

What Are National Aviation System (NAS) Delays? [DOT Data]

By Sharon Ben-Moshe ·

National Aviation System (NAS) delays account for 20.5% of all US flight delay minutes (47,139,100 minutes across 14,739,704 flights from July 2024 through July 2026). Reported to the US DOT Bureau of Transportation Statistics, NAS delays cover FAA air traffic control flow restrictions, airport volume congestion, and non-extreme weather that slows runway arrival rates.

When a gate agent announces that your plane is waiting on an air traffic control wheels-up time, or when a sunny morning departure in Pittsburgh sits on the ramp because of low clouds in New York, that delay is recorded under the National Aviation System code. All figures below reflect historical observations from our methodology dataset.

Key takeaways

  • National Aviation System (NAS) delays generated 47,139,100 delay minutes between July 2024 and July 2026, or 20.5% of the 229,801,550 total delay minutes recorded across US domestic flights.
  • As a destination, Newark Liberty International Airport (EWR) has the highest NAS share among major US hubs: 48.0% of all arrival delay minutes into Newark are caused by NAS restrictions.
  • San Francisco (SFO) ranks second for destination NAS exposure at 39.8% of arrival delay minutes, followed by LaGuardia (LGA) at 35.5% and Boston Logan (BOS) at 31.6%.
  • Midwest and East Coast feeder airports record the highest departure NAS shares because their flights are held on the ground before takeoff when Northeast hubs back up, led by Pittsburgh (PIT) at 30.2% and Indianapolis (IND) at 28.9%.
  • On short coastal corridors into congested hubs, NAS delays dominate: 58.0% of all delay minutes on Portland to San Francisco (PDX to SFO) and 56.1% on Detroit to Newark (DTW to EWR) stem from NAS flow control.

What counts as a National Aviation System (NAS) delay?

A National Aviation System delay is one of the five official delay categories mandated by the US Department of Transportation under 14 CFR Part 234. According to the Bureau of Transportation Statistics guide to delay causes, NAS encompasses delays and cancellations attributable to the national airspace infrastructure and air traffic management.

Specifically, the DOT assigns five operational triggers to the NAS category:

  • Non-extreme weather conditions: wind shifts, marine layer fog, low cloud ceilings, snow flurries, or nearby thunderstorms that do not prevent flying altogether, yet force air traffic control to space planes farther apart on approach.
  • Airport operations: runway closures, taxiway construction, de-icing pad congestion, or single-runway configurations that reduce how many aircraft an airport can land or launch per hour.
  • Heavy traffic volume: scheduled arrival and departure banks that exceed an airport's current hourly runway acceptance rate.
  • Air Traffic Control (ATC) initiatives: FAA Traffic Management Initiatives such as Ground Delay Programs, Ground Stops, Miles-in-Trail spacing, and airborne holding patterns published on the FAA National Airspace System Status dashboard.
  • Airspace equipment or staffing constraints: radar, communications, or terminal approach control staffing shortages that require reduced sector flow rates.

Across the 25-month dataset from July 2024 through July 2026, the 229,801,550 total arrival delay minutes broke down into five shares: late-arriving aircraft led at 39.5% (90,814,072 minutes), airline carrier causes took 33.6% (77,308,267 minutes), NAS accounted for 20.5% (47,139,100 minutes), extreme weather accounted for 6.2% (14,212,475 minutes), and security delays represented 0.14% (325,818 minutes). If you want the broader overview of how those five buckets fit together, see our guide on why flights are delayed.

How FAA Ground Delay Programs and Ground Stops create NAS delays before you board

The FAA manages arrival bottlenecks by holding aircraft at their origin airports before takeoff. Burning fuel in an airborne holding pattern over New York or San Francisco is expensive and unsafe when dozens of jets arrive at once, so the FAA Air Traffic Control System Command Center issues an Expect Departure Clearance Time (EDCT), commonly called a wheels-up time.

Two main traffic management tools drive most NAS delay minutes:

What is an FAA Ground Delay Program (GDP)?

An FAA Ground Delay Program reduces the hourly arrival rate at a destination airport when weather or runway limits cut capacity below scheduled demand. Suppose San Francisco International Airport (SFO) normally lands 50 to 60 aircraft per hour on parallel runways during clear visual conditions, and morning marine stratus clouds force controllers to switch to instrument approaches that handle 30 arrivals per hour. The FAA calculates the shortfall, assigns each inbound flight a delayed takeoff slot at its departure airport, and logs the resulting wait as an NAS delay.

What is an FAA Ground Stop?

An FAA Ground Stop is a sharper intervention that halts all departures bound for a constrained airport from specific geographic regions until a runway obstruction, thunderstorm cell, or radar outage clears. Flights already in the air continue to the destination (or divert if holding fuel runs low), while flights still at the gate in origin cities must wait until the stop is lifted or converted into a Ground Delay Program.

Because Ground Delay Programs and Ground Stops hold flights at their origin gate, the NAS delay shows up on the departure board hundreds or thousands of miles away from the actual bottleneck. A traveler sitting in Pittsburgh (PIT) or Cleveland (CLE) under clear skies experiences the delay at their home airport, even though the physical constraint is runway spacing at LaGuardia (LGA) or Newark (EWR).

Which US destination airports trigger the most NAS arrival delays?

When we group all route delay minutes by the destination airport (among major airports handling at least 80,000 arrivals in the 25-month sample), coastal and slot-constrained hubs sit at the top of the national table. At Newark Liberty International Airport (EWR), nearly half of all arrival delay time (48.0%) is logged as an NAS delay.

  • Newark Liberty (EWR): 48.0% of arrival delay minutes from NAS (5,240,669 total arrival delay minutes across 256,599 arrivals; 75.1% arrival on-time rate, 22.0-minute average arrival delay).
  • San Francisco (SFO): 39.8% of arrival delay minutes from NAS (5,458,652 total arrival delay minutes across 303,503 arrivals; 72.5% arrival on-time rate, 19.2-minute average arrival delay).
  • New York LaGuardia (LGA): 35.5% of arrival delay minutes from NAS (5,394,600 total arrival delay minutes across 296,216 arrivals; 75.1% arrival on-time rate, 19.9-minute average arrival delay).
  • Boston Logan (BOS): 31.6% of arrival delay minutes from NAS (5,540,044 total arrival delay minutes across 302,054 arrivals; 75.0% arrival on-time rate, 19.6-minute average arrival delay).
  • Denver International (DEN): 28.3% of arrival delay minutes from NAS (10,110,408 total arrival delay minutes across 663,087 arrivals; 78.7% arrival on-time rate, 16.4-minute average arrival delay).
  • New York JFK (JFK): 27.9% of arrival delay minutes from NAS (4,012,487 total arrival delay minutes across 226,508 arrivals; 77.5% arrival on-time rate, 19.2-minute average arrival delay).
  • Chicago O'Hare (ORD): 27.7% of arrival delay minutes from NAS (13,939,029 total arrival delay minutes across 685,486 arrivals; 75.3% arrival on-time rate, 21.9-minute average arrival delay).
  • San Diego (SAN): 26.8% of arrival delay minutes from NAS (2,882,324 total arrival delay minutes across 205,277 arrivals; 74.5% arrival on-time rate, 15.5-minute average arrival delay).
  • Fort Lauderdale (FLL): 26.5% of arrival delay minutes from NAS (3,304,551 total arrival delay minutes across 185,284 arrivals; 74.1% arrival on-time rate, 19.3-minute average arrival delay).
  • Houston Bush Intercontinental (IAH): 26.2% of arrival delay minutes from NAS (3,737,258 total arrival delay minutes across 246,208 arrivals; 79.6% arrival on-time rate, 16.4-minute average arrival delay).

Why do Newark and San Francisco stand out so sharply on inbound NAS share? Both airports rely on closely spaced runways where any drop in ceiling or visibility forces controllers to cut arrival capacity, and both sit inside busy terminal airspace shared with two other major commercial airports (JFK and LGA in New York; Oakland (OAK) and San Jose (SJC) in the Bay Area). You can compare those metro alternatives directly in our New York JFK vs. LaGuardia vs. Newark guide and our Bay Area SFO vs. Oakland vs. San Jose comparison.

Which departure airports and routes lose the most time to NAS delays?

When we flip the lens to origin airports (at least 80,000 departures), the highest NAS shares belong to a mix of Midwest feeder airports and Northeast hubs. Pittsburgh (PIT) leads at 30.2% of outbound delay minutes, followed by Indianapolis (IND) at 28.9% and Cleveland (CLE) at 28.2%.

  • Pittsburgh (PIT): 30.2% NAS share across 90,268 departures (82.8% departure on-time rate, 14.0-minute average departure delay).
  • Indianapolis (IND): 28.9% NAS share across 100,398 departures (82.2% departure on-time rate, 14.2-minute average departure delay).
  • Cleveland (CLE): 28.2% NAS share across 84,688 departures (81.9% departure on-time rate, 15.6-minute average departure delay).
  • New York JFK (JFK): 28.1% NAS share across 226,604 departures (79.0% departure on-time rate, 17.4-minute average departure delay).
  • New York LaGuardia (LGA): 27.7% NAS share across 296,207 departures (78.5% departure on-time rate, 17.9-minute average departure delay).
  • Columbus (CMH): 27.6% NAS share across 92,431 departures (81.9% departure on-time rate, 14.5-minute average departure delay).
  • Boston Logan (BOS): 27.2% NAS share across 302,064 departures (77.9% departure on-time rate, 17.4-minute average departure delay).
  • Newark Liberty (EWR): 27.1% NAS share across 256,361 departures (78.6% departure on-time rate, 18.3-minute average departure delay).

Notice that Pittsburgh, Indianapolis, Cleveland, and Columbus all have strong overall departure on-time rates (81.9% to 82.8%). They rarely generate their own local ground bottlenecks. Instead, when flights leaving those cities do get delayed, a large fraction of the wait happens because those flights are headed into New York, Chicago, Boston, or Washington airspace during FAA flow programs.

At the individual route level (minimum 5,000 flights over 25 months), every single one of the top 10 highest-NAS routes terminates at San Francisco (SFO), Newark (EWR), or LaGuardia (LGA):

Why do short and medium-haul flights into SFO and EWR take the worst hit? When the FAA puts SFO or EWR into a Ground Delay Program, flights already airborne (such as transcontinental flights from the opposite coast or international widebodies) cannot be held at their origin gate. That means short-haul regional and West Coast/East Coast flights still on the ground absorb the immediate ground holds.

Why NAS delays blur the line between weather and air traffic control

Travelers often wonder why the official DOT 'Extreme Weather' category is only 6.2% of delay minutes while NAS is 20.5%. In the DOT reporting system, the 6.2% weather code is reserved for conditions so severe that they prevent a flight from operating at all (such as a blizzard, hurricane, or tornado at the airport).

Ordinary weather that slows down traffic without closing the airport is logged inside the 20.5% NAS bucket. According to FAA operational audits cited by the Bureau of Transportation Statistics, weather conditions are the primary trigger for more than half of all NAS delay minutes. We examine that distinction in detail in our analysis of whether weather is really to blame for flight delays.

For passengers, this reporting boundary matters when an airline decides whether to provide hotel rooms or meal vouchers. Under the US DOT Airline Customer Service Dashboard, airlines only pledge meals, hotels, and ground transportation for 'controllable' delays (airline carrier delays and most late-aircraft rotations caused by carrier issues). Because NAS delays are classified as FAA airspace or weather-related flow restrictions outside the airline's control, airlines do not owe hotel accommodations when an NAS Ground Delay Program strands you overnight, though you are still entitled to a full cash refund if you choose not to travel during a significant delay or cancellation. See our complete guide to flight delay compensation and refund rights.

How to reduce your risk of an NAS air traffic control delay

1. Fly before 8 a.m. when traveling into or out of EWR, SFO, LGA, BOS, or ORD. Early-morning departures launch before FAA Ground Delay Programs build up arrival queues, and marine fog at SFO is already factored into the first morning arrival bank.

2. Consider nearby metro airports with lower NAS exposure. In the Bay Area, San Jose (SJC) has an 81.6% arrival on-time rate compared with 72.5% at SFO. In the Washington region, Dulles (IAD) posts an 82.3% arrival on-time rate versus 72.8% at slot-controlled Reagan National (DCA).

3. Check your specific route's delay-cause breakdown before booking a tight connection. Every route page on FlightRecord displays the exact percentage of delay minutes caused by NAS, carrier, late aircraft, and weather, alongside the most delayed US flight routes leaderboard.

Frequently asked questions

What does a National Aviation System (NAS) delay mean?

A National Aviation System (NAS) delay is an official US DOT delay category covering air traffic control flow restrictions, airport runway capacity limits, heavy traffic volume, and non-extreme weather conditions that slow down arrivals and departures. Across 14.74 million US flights from July 2024 through July 2026, NAS caused 20.5% of all arrival delay minutes.

Do airlines provide hotels or compensation for NAS delays?

No. Because National Aviation System delays stem from FAA air traffic control restrictions, airport congestion, or weather-reduced runway capacity instead of airline operations, US carriers classify NAS delays as uncontrollable. Airlines do not provide complimentary hotel vouchers for NAS delays, though federal law requires a full refund if your flight is cancelled or significantly delayed and you choose not to fly.

Which US airport has the worst NAS air traffic control delays?

Among major destination hubs, Newark Liberty International Airport (EWR) has the highest NAS exposure, with 48.0% of all arrival delay minutes caused by NAS restrictions. San Francisco (SFO) ranks second at 39.8%, followed by New York LaGuardia (LGA) at 35.5% and Boston Logan (BOS) at 31.6%.

Why is my flight delayed by air traffic control when the weather at my airport is clear?

When a destination hub like Newark, LaGuardia, or San Francisco reduces its hourly landing rate due to wind, low clouds, or runway volume, the FAA issues a Ground Delay Program that holds inbound flights at their departure gates before takeoff. Your plane waits on the ground at a sunny origin airport to avoid dangerous airborne congestion at the destination.

What is the difference between a DOT Weather delay and an NAS delay?

In DOT statistics, the Weather category (6.2% of delay minutes) only counts extreme conditions such as blizzards, hurricanes, or severe storms that completely prevent flying. Routine weather that remains safe to fly in but forces air traffic control to space planes farther apart is recorded under the National Aviation System (NAS) category (20.5% of delay minutes).

Written by Sharon Ben-Moshe, founder of FlightRecord. All figures are computed from US DOT Bureau of Transportation Statistics on-time data — see our methodology. Past performance describes history, not any guarantee about a future flight.