Newark Airport Disruptions Stretch Into a Second Day After a Double Communications Failure

Flights resumed Tuesday, but cancellations and delays continued after a primary FAA circuit failed and construction work severed the backup fiber line needed to keep air traffic controllers connected.

By Karla Alvarado Follow 

NEWARK, N.J. | Published at 12:30 p.m. EDT

Newark Liberty International Airport entered a second consecutive day of flight disruptions Tuesday, leaving passengers to confront dozens of cancellations and delays even after federal officials said the communications failure that brought commercial arrivals to a near standstill had been repaired.

The immediate crisis was over by Tuesday morning. Aircraft were once again taking off and landing at Newark, and federal officials had not reported a repeat of Monday’s widespread communications breakdown.

The consequences, however, remained visible throughout the airport.

FlightAware counted approximately 40 delays and nearly 60 cancellations at Newark early Tuesday, according to reporting by The Associated Press. The remaining problems reflected the complicated recovery from Monday’s extraordinary shutdown, when more than 600 flights into or out of Newark were canceled and arriving commercial aircraft were kept away from the airport for nearly eight hours.

The underlying cause was not a routine airline computer problem or a shortage of aircraft. It was a failure involving two critical communications paths serving an air traffic control facility in Philadelphia.

The primary circuit failed. When the Federal Aviation Administration attempted to shift operations to a backup fiber-optic connection, officials discovered that the backup had also been damaged during construction work in New Jersey.

With both communications routes unavailable, controllers lost essential radar data and radio capabilities used to direct aircraft safely through some of the busiest airspace in the United States.

The result was a cascading breakdown that disrupted Newark, John F. Kennedy International Airport, LaGuardia Airport, Philadelphia International Airport, Teterboro Airport and other facilities across the Northeast.

Why Newark was hit so hard

Newark was the airport most severely affected by the communications failure.

Commercial arrivals were effectively halted from approximately 9:40 a.m. until shortly after 5:20 p.m. Monday, according to flight-tracking information cited by The Associated Press. More than half of Newark’s scheduled flights were canceled, Reuters reported.

Newark is particularly vulnerable to a large air traffic interruption because it serves as a major hub for United Airlines. A disruption affecting the airport does not remain confined to northern New Jersey. Aircraft and crews scheduled to pass through Newark may be needed for later flights to destinations across the United States and overseas.

When hundreds of flights are canceled, airlines must locate replacement aircraft, reposition flight crews, accommodate stranded passengers and determine whether employees remain within federal work-hour limitations. Baggage may also reach a destination at a different time than its owner.

That operational damage does not disappear when a broken cable is repaired.

Transportation Secretary Sean Duffy warned Monday evening that it would take time to clear the accumulated delays even after the communications lines returned to service. United issued a travel waiver for affected passengers, allowing eligible customers greater flexibility to change their itineraries.

The second day of trouble was therefore not evidence of a second identical infrastructure failure. It was largely the aftershock of Monday’s outage, compounded by Tuesday’s weather risks and the difficulty of rebuilding an airline schedule after a major hub loses most of a day’s normal operating capacity.

The FAA’s daily traffic forecast for Tuesday warned that low clouds, reduced visibility and wind could cause additional delays at Newark, JFK and LaGuardia.

A primary failure met a damaged backup

The most troubling part of the incident is the sequence in which it developed.

According to FAA Administrator Bryan Bedford, a replacement circuit failed at the Philadelphia Terminal Radar Approach Control facility, commonly known as Philadelphia TRACON. That facility manages aircraft moving through airspace connected to Newark and other airports in the region.

A healthy backup connection should have prevented the primary failure from escalating into a regional aviation crisis.

Instead, the backup fiber line had already been severed near a rail corridor in New Jersey. When the system attempted to switch over, the secondary route was not available.

“The timing is absolutely horrible, and I’m very sorry for the delays and cancellations,” Bedford told reporters. He said the FAA acted to preserve safety while technicians worked to restore the communications system.

The failure demonstrates why redundancy only works when backup equipment is independently protected, continuously monitored and ready to take over.

A backup circuit that shares physical vulnerabilities with a primary network, or whose damage is not immediately detected, may offer less protection than its designation suggests. In this case, the combination of an equipment failure and construction damage removed both layers of communications service.

Bedford said approximately 600 feet of backup fiber had been damaged. The Wall Street Journal reported that the outage deprived controllers of radar information and radio communications, prompting significant flight restrictions and dozens of diversions.

This was not an instance in which controllers simply worked more slowly. Losing reliable radar and radio functions strikes at the center of safe air traffic management. The FAA’s decision to stop or sharply restrict arrivals was disruptive, but continuing normal traffic without dependable communications would have created an unacceptable safety risk.

Confusion over who cut the cable

Responsibility for the damaged backup line was initially unclear.

Duffy first attributed the fiber cut to an Amtrak construction crew near New Brunswick, New Jersey. Amtrak denied responsibility. New Jersey Transit later said the damage occurred around one of its construction sites, while noting that the digging was approximately 10 feet away from utility markings.

The agency said it was still determining whether Verizon or a contractor had marked the line incorrectly. Verizon confirmed that its technicians were working to repair the damaged cable.

That distinction matters because identifying who physically struck the cable is only part of the investigation.

Officials must also determine whether the line was marked accurately, whether construction personnel followed required procedures, whether the backup circuit’s condition was being monitored and why one damaged fiber path was capable of contributing to such broad disruption when the primary circuit failed.

The investigation should examine the full chain of responsibility rather than focus solely on the operator of the digging equipment.

A construction crew could have followed the markings it was given and still damaged a cable if those markings were inaccurate. Conversely, accurate markings would not excuse excavation that violated required clearance procedures. Federal and state investigators will need documentation from the construction project, Verizon, the FAA, Amtrak and New Jersey Transit to reconstruct the sequence.

Monday’s disruption spread far beyond Newark

The effects extended across the Northeast.

The FAA stopped arrivals at Newark, JFK, LaGuardia, Philadelphia and several smaller airports. Boston temporarily stopped accepting some traffic because of spillover volume, while Reagan Washington National Airport experienced a separate pause related to traffic volume.

Approximately 7,000 flights were delayed or canceled nationwide during the day, including about 1,400 at the three major New York-area airports, according to FlightAware data cited by Reuters. More than 100 flights were diverted to alternate airports.

Later flight-tracking analysis placed the diversion total at 165, including 109 aircraft originally headed to Newark. United reportedly canceled 361 flights and delayed nearly 800 more as its Newark operation absorbed the greatest damage.

Some passengers experienced much more than a delayed departure. International aircraft already in flight had to divert, hold or return to their departure airports. One Lufthansa flight bound for the region reportedly turned back to Munich after spending hours in the air.

The timing intensified the disruption. The outage occurred as international leaders and delegations were arriving in the New York area for the annual high-level meeting of the United Nations General Assembly. Roughly 130 world leaders and dozens of ministers were expected, increasing the concentration of international traffic and security-sensitive movements.

Canadian Prime Minister Mark Carney was among the travelers whose plans were affected, according to The Associated Press.

Why delays persisted Tuesday

Airline schedules depend on tightly coordinated movements of airplanes, pilots, flight attendants, maintenance workers and airport gates. When one part of that system falls out of position, later flights can be disrupted even if their destination is far from the original problem.

Consider an aircraft scheduled to fly from Newark to Chicago, then Chicago to Denver and Denver to Newark. If the first trip is canceled, the aircraft may not be available for either of the later segments. The airline must substitute another plane, reposition the original aircraft or cancel additional flights.

Crews face similar limitations. Pilots and flight attendants are subject to rules governing duty periods and required rest. Spending hours waiting for an airport to reopen can consume the legal time available to operate a later flight.

Passengers who miss connections must also be moved onto other departures. That places additional demand on flights that may already be nearly full.

These are the mechanics behind Newark’s second day of disruption. Tuesday’s cancellations did not necessarily mean the communications system remained broken. They reflected the time needed to restore hundreds of interconnected operations after Monday’s schedule had been severely damaged.

Weather added another variable. The FAA identified low clouds, visibility and wind as potential constraints in the New York region Tuesday. Those conditions can require more spacing between aircraft, reducing the number of arrivals an airport can safely handle within an hour.

At an airport already recovering from hundreds of cancellations, even a moderate reduction in capacity can prolong the backlog.

Newark’s infrastructure problems are not new

Monday’s outage also revived concerns about the Philadelphia facility responsible for guiding Newark traffic.

In spring 2025, Philadelphia TRACON experienced a series of major communications problems affecting radio and radar displays. Those incidents produced flight restrictions, cancellations and renewed questions about aging telecommunications equipment.

The FAA subsequently limited the number of hourly operations at Newark to reduce congestion and match traffic levels more closely with available controller and runway capacity. A federal order increased the allowable total to 72 hourly operations while retaining restrictions through October 24, 2026.

Congress approved $12.5 billion in 2025 to begin modernizing the nation’s aging air traffic control system and expand controller hiring. Duffy is seeking another $17.5 billion to complete the larger modernization program.

“This is unacceptable in America,” Duffy said while discussing the outage and the need for additional investment.

Funding alone will not settle the issue. Modernization must also address physical network routes, backup testing, construction coordination, real-time damage detection and the concentration of vital services in facilities with documented reliability problems.

Replacing old equipment without improving the architecture surrounding it could leave the system exposed to another single point of failure.

What passengers should do now

Travelers scheduled to use Newark should verify their flight directly with the airline before leaving for the airport. Airport departure boards and airline applications may update more quickly than confirmation emails or text messages.

Passengers should also determine whether their airline has issued a travel waiver. A waiver may allow a customer to change travel dates or airports without paying the usual difference in fare, although the terms vary by airline and itinerary.

Customers whose flights are canceled by an airline are generally entitled to a refund if they choose not to accept alternative transportation. Compensation for hotels, meals or other expenses depends on the cause of the disruption, the airline’s policies and any travel insurance or credit-card protections attached to the reservation.

Passengers should keep receipts and preserve screenshots showing cancellation notices, rebooking attempts and flight status information.

Those with flexible plans may also compare departures from JFK, LaGuardia or Philadelphia, but moving between airports should be considered carefully. Monday’s outage affected all of them, and residual congestion can make an alternate airport less useful than it initially appears.

The larger lesson from Newark

The Newark disruption was caused by an unusually damaging combination: a primary communications circuit failed at nearly the same moment the FAA needed a backup fiber line that had been severed during construction.

That combination may be rare, but it cannot be treated as unforeseeable.

Critical infrastructure is designed with backup systems precisely because equipment fails, cables are damaged and human errors occur. The system’s real test is not whether it can avoid every failure. It is whether one failure can be absorbed without producing a second, much larger crisis.

At Newark, that protection did not work.

Flights resumed, but Tuesday’s continued cancellations showed how long the consequences of an infrastructure failure can remain embedded in the aviation network. A damaged cable near a New Jersey rail project disrupted aircraft across the Northeast, diverted international flights and reshaped travel plans well into the following day.

For passengers, the immediate question is when their flights will depart. For federal officials, the more important question is why the country’s busiest airspace was left vulnerable to the simultaneous loss of a primary circuit and one damaged backup line.

Until that question is answered through documents, technical findings and accountable public reporting, Newark’s second day of disruption should not be dismissed as a routine travel backlog. It is evidence of how quickly a localized infrastructure failure can become a regional transportation emergency.

Sources and reporting disclosure

This report uses the FAA’s September 22 Daily Air Traffic Report and National Airspace System information, flight data cited by FlightAware and Flightradar24, public statements from Transportation Secretary Sean Duffy and FAA Administrator Bryan Bedford, and reporting from Reuters, The Associated Press and The Wall Street Journal.

Statements attributed to officials come from public briefings, online statements and interviews published by the named news organizations. The analysis of redundancy, schedule recovery and infrastructure accountability is original reporting analysis by Karla Alvarado based on the cited records and publicly available aviation data.