On a Friday evening in mid-November, the nation's skies went quiet for a few hours when the Federal Aviation Administration halted every flight in the United States after telecommunications trouble struck its facilities and terminal radar centers. The stop was lifted by 8:15 p.m. Eastern, but the day left a familiar lesson about how much modern travel depends on invisible threads of communication. Hundreds of flights were diverted, and the ripple reached rail travelers trying to book seats elsewhere. What caused the failure, and whether it is fully mended, remains for the official record to re
FAA Lifts Nationwide Ground Stop After Telecom Outage Diverts Hundreds of Flights
More than 3,500 planes were in the air when the stop came
Mark
Why does a telecom problem ground every plane in the country?
Mimi
Per Duffy, the trouble hit facilities and TRACONs nationwide at 3:36 p.m. The FAA stopped flights as a precaution while more than 3,500 planes were airborne.
Mark
That's a lot of aircraft to bring down at once.
Mimi
By 8 p.m. the count was under 400. Duffy says pilots and controllers followed established procedures to land them.
Luke
Worth noting that's Duffy's account. Nothing independent in this reporting confirms those numbers.
Mark
What about the claim that radar wasn't lost?
Mimi
The FAA says it did not lose all radar or telecom, and medevac, life-saving cargo and law enforcement flights were exempted.
Luke
Note the wording: not all. It doesn't tell us how much was lost.
Mark
And the diversions?
Mimi
The Guardian reported at least 600, and said airports including Reagan National stopped accepting diverted flights.
Luke
That's one outlet's figure, and a floor. We also don't know the cause, or whether the system is fully restored.
Mark
Amtrak got caught up too.
Mimi
Yes, it cited higher-than-normal call volumes and error messages on its site and app because of the airline issues.
Der Puls
- A sudden telecom failure at air traffic facilities forced the FAA to order a nationwide ground stop with more than 3,500 planes still airborne.
- Pilots and controllers scrambled to bring aircraft down safely, cutting the airborne count to under 400 by 8 p.m. Eastern.
- At least 600 flights were diverted, and some airports stopped accepting them, leaving travelers stranded in unexpected places.
- Exemptions for medevac, life-saving cargo, and law enforcement flights kept critical operations moving while the system was restored.
- Amtrak's booking systems buckled under surging calls and errors, and the ground stop was lifted the same day, though the cause remains unexplained.
On a Friday evening in mid-November, the nation's skies went quiet for a few hours when the Federal Aviation Administration halted every flight in the United States after telecommunications trouble struck its facilities and terminal radar centers. The stop was lifted by 8:15 p.m. Eastern, but the day left a familiar lesson about how much modern travel depends on invisible threads of communication. Hundreds of flights were diverted, and the ripple reached rail travelers trying to book seats elsewhere. What caused the failure, and whether it is fully mended, remains for the official record to reveal.
The Friday evening began with a problem that few travelers would have noticed until it was too late. At 3:36 p.m. Eastern, the Federal Aviation Administration began experiencing telecommunications failures at facilities and terminal radar approach control centers across the country. Transportation Secretary Sean Duffy, sharing the account on X, said the agency acted out of an abundance of caution and halted all flights in the United States, at a moment when more than 3,500 planes were in the air.
Those aircraft had to come down, and according to Duffy, pilots and controllers followed established procedures to land them. By 8 p.m. Eastern the airspace had emptied to under 400 planes. The FAA said it had not lost all radar or telecommunications, and exceptions allowed medevac, life-saving cargo, and law enforcement flights to continue.
The disruption reached the ground as well. At least 600 flights were diverted, and several airports, including Ronald Reagan Washington National, stopped accepting them. Amtrak also felt the strain, as customers reported errors booking trains and the railroad blamed high call volumes tied to the airline troubles, apologizing and urging patience.
The stop was lifted at 8:15 p.m. Eastern, but the cause of the telecommunications failure and whether repairs are complete have not yet been explained. The official FAA analysis is the next thing to watch.
At 8:15 p.m. Eastern on a Friday evening, the Federal Aviation Administration lifted a nationwide ground stop that had halted every flight in the United States. Transportation Secretary Sean Duffy announced the end of the stop in a post on X, hours after it began.
Duffy's post laid out the day as the administration understood it. At 3:36 p.m. Eastern, the FAA experienced telecommunications problems at facilities and terminal radar approach control centers, known as TRACONs, across the country. The agency issued the ground stop, Duffy wrote, out of an abundance of caution. At that moment more than 3,500 planes were in the air.
Those aircraft had to come down. According to Duffy, pilots and air traffic controllers followed established procedures to land them safely. By 8 p.m. Eastern, the number of planes in the airspace had fallen to under 400.
Duffy also addressed how far the failure reached. The FAA, he said, confirmed that it did not lose all radar or all telecommunications. Exceptions were made so that critical medevac flights, life-saving cargo, and law enforcement flights could keep operating through the stop.
The effects on the ground and in the air were considerable. The Guardian reported that at least 600 flights were diverted. Several airports, among them Ronald Reagan Washington National Airport, were reported to have stopped accepting diverted flights. The source does not say where those flights ultimately landed or how many passengers were affected.
The disruption spilled into other travel. During the ground stop, a person posted on X to Amtrak that they were getting error messages when trying to book a train. Amtrak replied that it was experiencing higher-than-normal call volumes because of ongoing airline issues. The railroad apologized for error messages on both its website and app, and for the difficulty reaching a representative, and recommended that customers try again later.
The timeline comes from Duffy's own account, and the reporting does not yet say what caused the telecommunications failure or whether it has been fully repaired. Those answers, along with any official FAA analysis of what went wrong at facilities across the country, are what to watch for next.
Bemerkenswerte Zitate
The nationwide ground stop lifted at 8:15pm ET.— Transportation Secretary Sean Duffy, on X
Amtrak said it was experiencing higher-than-normal call volumes due to ongoing airline issues.— Amtrak, on X
Möchten Sie die ganze Geschichte?
Das Original lesen bei Breitbart News Network ↗