The Federal Aviation Administration says a surge of connection attempts destabilized parts of its legacy telecommunications network on November 13, leading the agency to stop departures nationwide for nearly five hours. Air traffic resumed at 8:15 p.m. Eastern after technicians isolated the apparent sources and disabled a router function as a precaution. The FAA says the system is stable, while airlines continue restoring aircraft and crew schedules.

According to the agency’s preliminary explanation, data entered the FAA Telecommunications Infrastructure network at about 1,000 connection attempts every four to five seconds. That activity caused instability in aircraft communications and radar feeds. Investigators identified a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas, as potential sources. The network provider had been installing a router at the Arkansas location.

The FAA says blocking the two locations stabilized the network. It also disabled the relevant broadcasting function on approximately 60 similar routers while the agency and its provider investigate the root cause. Officials have said they do not currently believe the disruption was a cyberattack. That assessment is preliminary; the public should rely on later technical findings rather than assume the first explanation resolves responsibility or every contributing factor.

Instability reached 17 of the FAA’s 22 Air Route Traffic Control Centers and several terminal approach facilities. The agency says some radio frequencies and radar feeds remained available, allowing controllers to track and communicate with aircraft. About 3,500 aircraft were in the air when the stop began, and all landed safely. Critical medical, law-enforcement and military flights continued under established procedures.

Operators canceled about 12,462 flights on November 13, including 9,082 cancellations by major airlines, according to the FAA. The agency cautions that not every cancellation was directly caused by the ground stop. A systemwide interruption also leaves aircraft and crews away from planned positions, so disruptions can continue after the technical fault is isolated. Travelers should check the operating airline, not only an itinerary issued days earlier.

For New York-area passengers, conditions can differ at Kennedy, LaGuardia and Newark even during a national recovery. Weather, runway capacity, crew legality and each airline’s network affect an individual flight. The FAA’s public status page provides airport and airspace-program information, while the airline controls cancellation, rebooking and customer communications. Travelers should preserve receipts and review their carrier’s current policy before paying for an alternative.

The agency says it will reconsider when remote router replacements are performed. Maintenance at major facilities generally occurs at night, but similar work at smaller sites had routinely taken place during the day. The incident shows why the risk of a change depends not only on a site’s size but also on how a misconfigured or unstable device can propagate traffic across a shared network. Change controls should account for that network effect.

The outage also renews scrutiny of aging air-traffic infrastructure. The FAA distinguishes the legacy system involved here from its broader modernization program, saying upgraded towers were not the source. That distinction matters for accountability, but modern equipment alone does not guarantee resilience. Network segmentation, rollback procedures, monitoring thresholds and independent testing are as important as replacing hardware. A complete after-action report should address each of those controls.

The immediate safety response worked as designed: departures paused while airborne flights landed and technicians stabilized the network. The remaining questions concern prevention, speed of diagnosis and recovery. Passengers need current operational information; policymakers need a technical timeline and corrective plan. Until the investigation is complete, the most responsible advice is practical—verify the flight directly, watch official airport status and allow recovery conditions to vary by route and carrier.

Primary sources: Federal Aviation Administration ground-stop questions and answers; FAA National Airspace System status. Reviewed November 17, 2026. Development: FAA public explanation updated November 15, 2026.