More news on this day
Travelers at Harry Reid International Airport in Las Vegas faced knock-on flight delays this week after a construction accident on the East Coast damaged communications infrastructure used by air traffic control, disrupting traffic flow in the Northeast and rippling through the national network.
Get the latest news straight to your inbox!

What happened, and why it reached Las Vegas
Published coverage indicates the disruption began when a primary communications circuit serving the Federal Aviation Administration’s air traffic facility in Philadelphia failed, and a backup fiber-optic line was later found to have been cut during rail-related construction work in New Jersey. The failure triggered ground stops and traffic-management restrictions at several major Northeast airports, including Philadelphia, Newark, JFK, and LaGuardia.
When the busiest corridor in the U.S. airspace slows down, the effects are rarely contained to one region. Flights bound for Las Vegas from New York, New Jersey, and Pennsylvania can be held at departure gates, pushed into later arrival slots, or canceled if crews time out. Those disruptions also complicate aircraft rotations, meaning a late inbound airplane to Las Vegas can delay an outbound flight to a different city later in the day.
The timing amplified the problem. The Northeast interruption arrived during a period of heavy demand tied to major events and conferences, and published coverage described a sharp increase in cancellations and delays at affected airports, with impacts extending into the following day as airlines worked through backlogs.
What travelers saw at Harry Reid International Airport
At Las Vegas, the incident most often showed up as delays on routes connected to the Northeast and on aircraft arriving late from earlier segments. Some passengers encountered shifting departure times, longer-than-normal waits for aircraft and crews to be in place, and tighter connection windows for itineraries that linked through Northeast hubs.
Real-time FAA airport status information for Las Vegas around this period generally reflected manageable local conditions, even as inbound flights from constrained airspace arrived behind schedule. That mismatch is a common feature of network disruptions: a destination airport can be operating normally while still receiving late aircraft from elsewhere.
Travelers also reported secondary pain points typical of irregular operations, including rebookings onto later flights, reduced seat availability on the same-day options that remained, and longer lines at customer-service counters when multiple flights were disrupted at once.
The air traffic control and telecom link behind the disruption
The underlying issue was not weather in Nevada or a runway closure in Las Vegas. Public reporting tied the event to a communications outage affecting a key FAA facility responsible for managing high volumes of traffic in the Mid-Atlantic and Northeast. In practice, when that kind of facility experiences a major communications issue, the system often responds with ground stops and metering programs to preserve safety and maintain spacing between aircraft.
Those restrictions can cascade quickly. Even flights that do not plan to fly through the affected area may be delayed if their aircraft is out of position, if crews are delayed elsewhere, or if airlines adjust schedules to protect operations at their largest hubs first.
For Las Vegas, which depends heavily on nonstop traffic from major East Coast markets as well as connections over large hubs, the result can be a broad spread of smaller delays rather than a single visible shutdown at the local airport.
What to do if your Las Vegas flight is delayed or canceled
Published guidance around the Northeast outage emphasized checking flight status before leaving for the airport. For Las Vegas travelers, the practical takeaway is to verify both the departing flight and the inbound aircraft’s status, since a late arriving plane is a frequent cause of late departures during nationwide disruptions.
When rebooking is necessary, flexibility often matters more than loyalty. Travelers can sometimes improve their odds by considering alternate departure times, nearby airports on the origin side, or connecting itineraries if nonstop seats disappear. Those options can narrow quickly during a network event, especially on high-demand routes between Las Vegas and the New York area.
For passengers already at Harry Reid, it can help to monitor gate changes and updated departure estimates closely. Airlines may swap aircraft or consolidate flights as they recover, and the posted information can change several times in a short period during systemwide irregular operations.
What happens next as airlines recover
Once communication lines are repaired, the system does not instantly return to normal. Carriers typically need a full day or more to reposition aircraft, reset crew schedules, and move displaced passengers, particularly when multiple large airports in the same region were constrained at the same time.
Travelers flying between Las Vegas and Northeast airports can continue to see scattered delays after the initial incident, especially on early-morning departures that rely on aircraft arriving from late-night flights the day before. That is also when airlines may proactively adjust schedules to rebuild reliability.
For Las Vegas, the broader story is a reminder that airport performance is often shaped by infrastructure far from the terminal. A single construction-related communications failure in the Northeast can still disrupt a day of departures and arrivals in Nevada, even when local weather and runway conditions are otherwise routine.