More news on this day
Flight-tracking data and federal air-traffic status pages showed widespread disruption for travelers moving through Las Vegas and Phoenix, with hundreds of delays logged across the two major Southwest hubs as operational constraints and weather-related slowdowns rippled through airline schedules.
Get the latest news straight to your inbox!
Delay counts climbed at both hubs, led by Las Vegas and Phoenix
Publicly available flight-tracking tallies on Thursday, September 17, 2026, showed notable delay totals at both Harry Reid International Airport (LAS) and Phoenix Sky Harbor International Airport (PHX). FlightAware’s airport statistics pages listed 120 total delays at PHX and 9 total delays at LAS at the time those pages were checked, with the numbers updating throughout the day as operations evolve.
The same FlightAware pages also displayed cancellations, listing 3 cancellations at PHX and 0 at LAS at the time of viewing. Because these are live counters, the figures can move quickly as airlines recover aircraft rotations, crews time out, or conditions improve.
In parallel, the FAA’s real-time airport status pages for both airports indicated only modest average arrival and departure impacts around the time of the latest update, describing general arrival and departure delays at LAS as 15 minutes or less. The contrast between “general” FAA delay messaging and higher flight-tracking delay counts can occur when delays are unevenly distributed by airline, time bank, or route, rather than reflecting a sustained, airport-wide slowdown.
FAA system status pointed to manageable average delays, even amid broader disruption
For travelers trying to determine what conditions look like right now, the FAA’s National Airspace System status pages (the fly.faa.gov airport status views) provide a snapshot of overall airport flow rather than a flight-by-flight prediction. For LAS, the FAA status page showed no destination-specific delays and described gate-hold and taxi delays, plus airborne arrival delays, at 15 minutes or less as of an update timestamped September 17, 2026 at 12:16 AM UTC.
Phoenix’s FAA status page similarly presented a system-level view, and those “general delay” numbers may remain low even when a significant share of flights are delayed for airline-specific reasons, such as late-arriving aircraft, network congestion at connecting hubs, or recovery from earlier ground programs elsewhere in the U.S.
Separately, FAA materials describing the Air Traffic Control System Command Center outline how traffic management initiatives are used nationally to manage demand and reduce airborne holding. When those initiatives are triggered, travelers may see delay codes appear as “ATC” or “NAS” related on airline apps, even if conditions at the departure airport look calm.
Weather and wind can trigger cascading impacts across the Southwest network
FAA’s Daily Air Traffic Report has highlighted weather as a recurring driver of disruption, including thunderstorms that can slow traffic in Phoenix and gusty winds that can reduce arrival rates in Las Vegas. Even when storms are not directly overhead, convective weather in the broader region can force reroutes, spacing, or miles-in-trail restrictions that reduce capacity for flights crossing busy corridors in the Southwest.
Wind in Las Vegas can also affect runway configuration and spacing, which can increase taxi times and gate holds. Those changes may not always show up as severe “general delays” on the FAA airport status page, but they can still contribute to rolling, flight-level delays that stack up as the day progresses.
For passengers, the practical effect is that a delay listed on a specific itinerary may be driven by weather or air-traffic constraints hundreds of miles away. FlightAware also notes that it does not always receive operational details for the specific cause of an individual flight delay, which is why airline notifications and airport status tools can show different levels of detail.
What travelers can do now: check flight status, build buffer time, and plan for gate changes
With delay totals fluctuating by the hour, travelers departing LAS or PHX can reduce surprises by monitoring both the airline’s in-app flight status and the FAA’s airport status pages to understand whether delays are airport-wide or more isolated. Flight-tracking tools can help spot whether an inbound aircraft is running late, which is a common reason flights depart behind schedule even if the local weather is favorable.
At the airport, delays often come with gate changes, especially when arriving aircraft are reassigned to different gates to keep turns moving. Travelers connecting through either hub may want to allow extra time for moving between concourses and re-checking gate information, as airlines can shuffle gate assignments when arrival banks compress.
For those already on a disrupted itinerary, rebooking options can vary widely by carrier and load factors. Monitoring later departures on the same route and considering alternate airports in the same region can sometimes reveal faster options, though availability may tighten quickly when multiple departures slip at once.
Why “hundreds of delays” matters for the region, even without a full shutdown
LAS and PHX are key nodes for leisure and connecting traffic in the Southwest, and both airports have dense schedules that can amplify disruptions. When delays accumulate across a morning or afternoon bank, aircraft and crews can fall out of position, making it difficult for airlines to fully reset even after conditions improve.
Operational disruptions can also spill into the evening, when airports have less slack to absorb late turns. That can be particularly consequential for travelers on the last departures of the day, where a late inbound aircraft or crew legality issue can turn a delay into a cancellation that requires overnight re-accommodation.
For Thursday’s travelers, the headline figures underline a familiar pattern for large hubs: moderate “general” air-traffic slowdowns can still coincide with large numbers of delayed flights, especially when network ripple effects, weather constraints, and tightly timed schedules collide.