FAA Grounds Every Departing Flight in the US After Air Traffic Control Communications Failure in Only the Second Nationwide Stop Since 9/11

On Friday afternoon, November 13, 2026, the United States did something it had done only once before in a quarter of a century: it stopped its skies. The Federal Aviation Administration ordered every departing flight in the country to stay on the ground, holding aircraft at their gates at airports from coast to coast while technicians hunted for the cause of a communications failure inside the air traffic control system. Planes already in the air were allowed to land, but nothing new could take off. Within hours, nearly 7,000 flights had been delayed or cancelled, and about 3,100 aircraft were still in the air, heading for airports that could not send a single plane back out. The order, issued at 3:54 p.m. Eastern time, cited “extraordinary circumstances” and “reasons of safety”, and it stayed in force until further notice. What failed, and when normal flying would resume, was still unknown on Friday evening. This is the story of what happened, what officials have said, why the stop is so rare, and what travellers need to know. FAA nationwide ground stop November 2026.

1. What Happened on Friday Afternoon

The trouble began on an ordinary Friday afternoon, one of the busiest travel periods of the week, when millions of Americans were heading home for the weekend or flying out for the days ahead. Reports of serious air traffic control communications problems began to reach the Federal Aviation Administration during the afternoon, and the disruption spread quickly from one part of the system to another. The FAA first halted traffic at Chicago, one of the country’s biggest aviation hubs, after communications problems were reported there. Then, in the space of less than half an hour, the problem became a national one. At 3:54 p.m. Eastern time, the FAA’s Air Traffic Control System Command Center issued Advisory 111, titled “National Ground Stop”, and ordered all airports in the United States to stop departing flights until further notice. It was a decision the agency does not take lightly, and one that brought the world’s largest aviation system to a standstill in a matter of minutes. Airports across the country held their departing aircraft at the gates, passengers waited at terminals with no departure time to count down to, and the flow of aircraft that normally fills American skies every hour of every day simply stopped going up.

The speed of the decision tells its own story. Air traffic controllers cannot safely send a plane into the sky if they cannot be sure they can talk to it once it is there, and the failure on Friday afternoon struck at the very centres that guide aircraft across the country. The FAA’s own website described the cause as an “equipment outage”, and the site itself went down for a brief period at the time of the announcement, carrying a note that it was “experiencing technical difficulties”. By the early evening, the agency was still describing the problem in the most general terms, and no official would say how long the stop would last. For the passengers caught in it, the afternoon turned into an evening of waiting, rebooking and cancelled plans, with no clear answer about when the system would start moving again.

1.1 The 3:54 PM Order

The order itself was short, and its language was unusually blunt for a routine aviation notice. “Due to extraordinary circumstances and for reasons of safety,” the advisory read, “all airports are ground stopped. All departing traffic should remain ground stopped until further notice.” The instruction was sent to every aircraft operator in the country, and it left no room for interpretation: no departing flight was to leave its gate. The advisory was issued by the Air Traffic Control System Command Center, the FAA facility that manages the flow of traffic across the national airspace system, and it applied to every airport in the United States at once. That is what made it different from the ground stops that happen almost every day in American aviation, when a single airport is held because of a thunderstorm or a runway problem. This one covered the whole country, all at the same time, and it did so with no end time attached. The only limit written into the advisory was a stated expiry of 11:30 p.m. Eastern time, but the order itself said “until further notice”, and officials gave no promise that flying would resume by then.

The timing mattered as much as the order. At 3:54 p.m. Eastern time, the afternoon bank of departures was already under way at airports across the eastern United States, and the evening rush was building at hubs in the central and western time zones. Aircraft that had already pushed back from their gates were held where they stood. Crews that had been preparing for departure were told to wait. And because the stop came with no advance warning, there was no chance for airlines to thin out their schedules in advance, the way they do before a forecast storm. The result was a sudden, nationwide freeze that stranded aircraft and crews in the wrong places, a problem that would take hours to untangle even after the order was lifted. By 4:26 p.m. Eastern time, the FAA’s National Airspace System status page no longer listed a nationwide ground stop, a change that raised hopes the order was being lifted, but the agency had issued no statement confirming a full resumption, and travellers were told to check with their airlines.

1.2 What a Ground Stop Means for Planes in the Air

A ground stop does not mean the sky is empty. It means nothing new goes up. The roughly 3,100 aircraft that were already airborne when the order took effect were allowed to continue to their destinations and land, and controllers kept guiding them down even as the system struggled. What the order stopped was departures: aircraft on the ground, at their gates, could not take off, no matter where they were headed or how long they had already waited. That distinction is the reason the stop was so disruptive and yet, in one sense, so controlled. Nobody was asked to stay in the air longer than planned, and nobody was diverted because the system had suddenly closed. The aircraft in the sky came down in an orderly way, one after another, while the ground filled up with planes that had nowhere to go.

International flights were treated separately. The FAA said inbound international flights would be managed on a case-by-case basis, a phrase that covered the long-haul aircraft already crossing the Atlantic and the Pacific toward American airports. Those flights were allowed to land where they could be handled safely, but their onward journeys, and the departures of aircraft waiting to leave the United States for other countries, were caught in the same freeze as domestic flights. The effect rippled outward from there. An aircraft that cannot leave New York cannot arrive in London on time, and an aircraft that cannot leave London cannot arrive in New York. For a few hours on Friday, the busiest aviation network in the world was running in one direction only, taking planes in and sending none out, and the backlog grew with every hour the order stayed in place.

2. The Communications Failure at the Heart of the Stop

The reason for the stop was a failure in the communications that air traffic controllers use to talk to pilots and to track aircraft in flight. Transportation Secretary Sean Duffy said the stop followed “a communication issue impacting all Air Route Traffic Control Centers”, the regional facilities that guide aircraft as they cross the country. A spokesperson for the Federal Aviation Administration confirmed the same point, telling reporters that the ground stop was issued “following communication issues impacting multiple Air Route Traffic Control Centers”. The FAA’s own website described the cause as an “equipment outage”. Beyond those statements, officials said very little on Friday afternoon about what had actually broken, and the agency did not name a cause. What was clear was that the problem was not limited to one airport or one region. It touched the centres that handle aircraft in flight across the whole country, and that was why the response had to be nationwide as well.

The failure was described in different ways by different sources through the afternoon, and the picture that emerged was of a problem that moved. Two sources inside the FAA, speaking to the Washington Examiner, described a “rolling frequency outage” affecting the facilities that monitor aircraft in flight. The Air Current, an aviation trade publication, reported that the FAA had cited “several impacts to ATC frequencies and/or radar capabilities”, and that the agency’s command centre said it did not have further information on the timing or the cause of the outage. The National Weather Service was also reporting a national radar outage on Friday, and the flight-tracking service Flightradar24 and Canadian air traffic control both linked the disruption to an FAA radio outage. Taken together, those accounts point to a failure in the radio frequencies controllers use to speak with pilots, possibly combined with problems in the radar systems that show controllers where aircraft are. But none of it was confirmed by the FAA itself on Friday evening, and the agency said only that its technicians were investigating.

2.1 A Rolling Frequency Outage

The phrase “rolling frequency outage” is the most specific description of the failure to emerge so far, and it matters because it explains why the problem could not be contained to one place. Air traffic control depends on radio frequencies: controllers speak to pilots on assigned channels, and if a frequency fails, the controller and the pilot lose contact. A failure that rolls from one facility to another, or from one frequency to the next, would leave controllers unable to guarantee they could reach the aircraft they were responsible for, and that is a situation in which no responsible authority sends more aircraft into the sky. The FAA’s own account, that the issue affected multiple Air Route Traffic Control Centers, fits the same picture. These centres handle aircraft once they are at cruising altitude, handing them from one region to the next as they cross the country. If several of them lose reliable communications at the same time, the system cannot safely move aircraft between regions, and the only safe option is to stop new departures everywhere until the links are restored.

What is not known is whether the failure was a single equipment breakdown that spread, a software fault, a power problem, or something else entirely. The FAA has not said. The agency’s advisory did not mention a communications problem at all, citing only “extraordinary circumstances”, and the gap between that wording and the statements from the Transportation Secretary left room for speculation through the evening. Officials were quick to say what the failure was not. According to MS NOW, the assessment that the outage was not a national security matter came from the Justice Department, and officials were treating the failure as a communications and frequency problem. No official has established a cause, and until the FAA’s technicians complete their investigation, the most honest description of what happened on Friday remains the one the agency itself gave: an equipment outage that hit the communications of the centres that guide American aircraft.

2.2 The Kansas City Starting Point

The first signs of trouble appear to have come from the middle of the country. Reports indicate that problems began around 3:30 p.m. Eastern time at the FAA’s Kansas City Air Traffic Control Center, before spreading to other centres. The Kansas City centre is one of the regional facilities that guide aircraft across the central United States, and a communications failure there would affect a large stretch of the country’s airspace. From there, the disruption seems to have moved outward. The FAA halted traffic in Chicago shortly before the nationwide order, after communications issues were reported in that area as well, and CBS News reported that Chicago Midway International Airport had been issued a ground stop of its own. By the time the national order was issued at 3:54 p.m., the problem had been described as affecting all of the Air Route Traffic Control Centers, and the FAA’s website was briefly down as well.

The sequence matters because it shows how quickly a local failure became a national one. Air traffic control is a network, and its centres are connected to one another. Aircraft are handed from one centre to the next as they fly, and a failure in one part of the network can leave neighbouring centres unable to accept the traffic they were expecting. On Friday, whatever began in Kansas City appears to have spread fast enough that, within about half an hour, the FAA decided it could not safely keep departures moving anywhere in the country. Whether the spread was caused by the same fault reaching other centres, by the loss of shared systems, or by a deliberate decision to stop traffic as a precaution while the fault was investigated, has not been explained. The National Weather Service’s separate report of a national radar outage on Friday added to the picture of a wider systems failure, but the connection between that outage and the FAA’s communications problem has not been confirmed either.

3. How Many Flights Were Affected

The scale of the disruption became clear within hours. FlightAware, the flight-tracking service, said nearly 7,000 flights were delayed or cancelled because of the nationwide ground stop. That figure covered the flights that could not take off, the flights that were delayed while their aircraft and crews waited, and the cancellations that followed as airlines gave up on getting their schedules back on track for the day. The number was still rising on Friday evening, because every hour the stop stayed in place added more flights to the count, and because a cancelled departure on Friday evening means a missing aircraft somewhere else on Saturday morning. Airlines work on tight rotations, with the same aircraft flying several routes in a day, so a plane held on the ground in one city is a plane that cannot fly its next route from another. The effects of a nationwide stop do not end when the order is lifted; they carry over into the next day, and sometimes the day after that, as airlines work to get their aircraft and crews back to where they belong.

For the passengers, the numbers were felt one flight at a time. Departure boards at airports across the country filled with delays and cancellations. Travellers who had arrived at airports expecting to fly out on Friday evening found themselves with no departure time at all, and no way of knowing when one would be given. Some were rebooked onto later flights that were themselves then delayed or cancelled. Others were told to come back the next day. The disruption hit every kind of traveller at once: people flying home for the weekend, people travelling for work, families with children, and passengers with connecting flights who watched their connections disappear as their first flight sat on the ground. The FAA had given no estimate for when normal operations would resume, and the airlines could give their passengers no better answer than the one the FAA had given them.

3.1 Nearly 7,000 Flights Delayed or Cancelled

The figure of nearly 7,000 delayed or cancelled flights, reported by FlightAware, is a measure of how much of the American aviation system was caught by the stop. The United States operates the busiest airspace in the world, with tens of thousands of flights every day, and a nationwide ground stop on a Friday afternoon catches the system at one of its busiest moments. The afternoon and evening are when the day’s departures peak, when business travellers fly home, when weekend travellers set out, and when the hub airports run their banks of connecting flights. Stopping all departures at that hour does not just delay the flights that were about to leave. It stops the flow that the whole system depends on, and the backlog builds at every airport at once. Airlines began cancelling flights as the evening wore on, because a flight delayed by several hours may be impossible to operate once its crew has run out of its permitted working hours, or once its aircraft is needed for a different route the next morning.

The cancellations were the hardest part for passengers, because a cancelled flight is not a delayed flight. A delayed flight eventually leaves, even if it leaves hours late. A cancelled flight leaves its passengers to find another way, and on a Friday evening, with thousands of other passengers in the same position, there were not many other ways to find. Airlines worked to rebook passengers onto Saturday flights, but the aircraft and crews that should have been in place for Saturday were themselves out of position because of Friday’s stop. The disruption was, in that sense, self-reinforcing: every cancellation on Friday made Saturday harder, and every delayed aircraft on Friday evening was an aircraft that would start Saturday late. That is why a ground stop that lasts a few hours can affect flying for a day or more after it ends, and why the airlines were already warning on Friday evening that the effects would be felt into the weekend.

3.2 The 3,100 Planes Still in the Air

While nothing could take off, the sky was far from empty. Flightradar24, another flight-tracking service, said that about 3,100 aircraft were airborne and bound for airports in the United States when the stop took effect, with no additional aircraft taking off behind them. Those aircraft were the ones that had left before the order was issued, and they were allowed to complete their journeys and land. Controllers continued to guide them down, airport by airport, even as the communications problems persisted, and the landings appear to have gone ahead in an orderly way. For the passengers on those flights, the experience was strange but not frightening: they took off in a normal sky and landed in a country where nothing was taking off behind them. For the controllers, the task was to bring down thousands of aircraft safely while their own systems were failing, a job that required the parts of the system that were still working to carry the load of the parts that were not.

The number also shows the scale of what was at stake. Three thousand aircraft in the air at once is a normal figure for a Friday afternoon in the United States, but it is also a measure of how much depends on the communications that failed. Every one of those aircraft needed to be in contact with a controller, and every one of them needed to be handed from one control centre to the next as it flew. The fact that they all landed safely is a credit to the controllers and to the backup systems that kept working. It is also a reminder of why the FAA stopped departures rather than taking a risk. If the communications failure had grown worse while new aircraft were still climbing into the sky, the controllers would have had more aircraft to look after with fewer tools to look after them. Stopping departures was the way to keep the number of aircraft in the air from growing while the system was already under strain.

4. What Officials Said — and Did Not Say

The official account of Friday’s events came in pieces, and the pieces did not always match. The FAA’s advisory, the most formal statement of the day, said nothing about communications at all. It cited only “extraordinary circumstances” and “reasons of safety”, and it ordered all departing traffic to remain on the ground until further notice. The Transportation Secretary, Sean Duffy, was more specific. In a post on X at 4:16 p.m. Eastern time, he said the FAA had “issued a nationwide ground stop for all U.S. airports following a communication issue impacting all Air Route Traffic Control Centers”, and he added that “FAA technicians are investigating the issue”. An FAA spokesperson gave the same account to reporters, saying the ground stop had been issued “following communication issues impacting multiple Air Route Traffic Control Centers”. The FAA’s website, for its part, described the cause as an “equipment outage”, and the site itself was briefly unavailable at the time of the announcement, carrying a note that it was “experiencing technical difficulties”.

What officials did not say was just as important. Nobody named a cause. Nobody said how long the stop would last. Nobody said how many flights or passengers were affected, or gave an estimate for when normal operations would resume. The FAA’s advisory carried a stated time of 11:30 p.m. Eastern time, but the order itself said “until further notice”, and by 4:26 p.m. Eastern time, the agency’s National Airspace System status page no longer listed a nationwide ground stop, even though the agency had issued no statement confirming that flying had fully resumed. That left travellers, airlines and reporters in the same position: watching the status page, waiting for an official word, and checking with airlines flight by flight. The gap between what was known and what was officially confirmed was the defining feature of Friday evening, and it is the reason this story, as written, has to be careful about what it presents as fact and what it presents as still unconfirmed.

4.1 Transportation Secretary Sean Duffy’s Statement

Sean Duffy, the Transportation Secretary, was the most visible official voice on Friday afternoon, and his statements set the tone for the evening. His post on X at 4:16 p.m. Eastern time was the first clear official explanation of what had happened. “The FAA issued a nationwide ground stop for all U.S. airports following a communication issue impacting all Air Route Traffic Control Centers,” he wrote. “FAA technicians are investigating the issue. We will provide immediate updates as we have them.” The wording was careful. It named the problem as a communication issue, it located the problem in the Air Route Traffic Control Centers, and it said the technicians were investigating, which is another way of saying the cause was not yet known. Duffy’s statement was reported by Reuters and other news agencies, and it became the basis for most of the early coverage of the stop.

Duffy’s role in the story is also a political one. As Transportation Secretary, he is responsible for the FAA, and the failure on Friday happened on his watch, in a system his department has been trying to modernise for years. His statement did not apologise, and it did not promise a quick fix. It said the technicians were investigating and that updates would follow. That is the standard language of a developing incident, and it left the most important questions unanswered: what failed, why it failed, and how long it would take to fix. The Secretary’s office gave no further detail on Friday evening, and the FAA itself said only that it would provide updates as it had them. For the passengers waiting in airports, that meant the official position was, in effect, to wait and see.

4.2 No Cause Confirmed, No Resumption Time Given

By Friday evening, the two questions that mattered most to travellers had no official answers. The first was what had actually failed. The FAA had described an “equipment outage” on its website, the Transportation Secretary had described a communication issue affecting the Air Route Traffic Control Centers, and sources inside the FAA had described a rolling frequency outage. None of those accounts had been confirmed as the full story, and the FAA had not named a cause. The second question was when flying would resume. The advisory said “until further notice”, the FAA’s status page stopped listing a nationwide ground stop at 4:26 p.m. Eastern time, and yet the agency issued no statement confirming a full resumption. Travellers were told to check with their airlines, and airlines were left to work out, flight by flight, whether their aircraft could move.

The uncertainty was made worse by the fact that the FAA’s own website had been briefly down at the time of the announcement, and by the separate report from the National Weather Service of a national radar outage. Neither of those facts proves anything about the cause of the communications failure, but both of them fed the sense on Friday evening that more than one system had gone wrong at once. Officials were, however, clear on one point: according to MS NOW, the assessment that the outage was not a national security matter came from the Justice Department, and officials were treating the failure as a communications and frequency problem. That assessment, if it holds, rules out the most alarming explanations. But it does not explain what broke, and until the FAA’s investigation is complete, the cause of the second nationwide ground stop in American history will remain officially unknown.

5. Why This Stop Is So Rare

Friday’s stop was the second nationwide ground stop of all departures since the September 11, 2001, attacks. That single fact is the reason the story travelled around the world within minutes, and it is the reason the FAA’s decision was so striking. The United States grounds flights all the time, but it grounds them one airport at a time, for a thunderstorm, for snow, for a runway closure, for a problem at a single control tower. A nationwide stop is different in kind, not just in scale. It means the system as a whole cannot be trusted to move aircraft safely, and it is a decision that no FAA administrator takes without good reason. The last time it happened, the country was under attack. This time, the cause was a failure inside the system itself, and that is what makes Friday’s events so unsettling for the people who run American aviation. A system that stops itself because its own communications have failed is a system with a problem that goes deeper than the weather.

The rarity of the stop also explains why there was so much confusion on Friday evening. Airlines, airports and passengers have plans for local ground stops. They know how to handle a thunderstorm at one hub, or a closure at one airport. They do not have a routine for the whole country stopping at once, because it has happened only once before in living memory. The result was a scramble: airlines trying to work out which of their aircraft were where, airports trying to find places to park aircraft that could not leave, and passengers trying to work out whether they were delayed, cancelled, or simply stuck. The FAA’s own procedures for a nationwide stop exist, but they had not been used for a quarter of a century, and the people who would have remembered the last one have mostly retired.

5.1 The Only Other Nationwide Stop: September 11, 2001

The only other time the FAA ordered a nationwide ground stop of all departures was on September 11, 2001, after terrorists hijacked four aircraft and attacked New York and Washington. On that day, the FAA ordered every aircraft in the country to land as soon as possible, and no aircraft was allowed to take off. It was the first time in American history that the national airspace had been closed, and it stayed closed for days. The comparison with Friday is both instructive and misleading. It is instructive because it shows how rare and how serious a nationwide stop is, and because it explains why the phrase “only the second since 9/11” appeared in almost every report of Friday’s events. It is misleading because the two stops happened for entirely different reasons. In 2001, the skies were closed because the country was under attack and nobody knew whether more attacks were coming. On Friday, the skies were closed because the system that guides aircraft could not be relied on to do its job.

The difference matters for how the public should understand what happened. A stop caused by an attack is a security decision, and it ends when the threat is gone. A stop caused by a communications failure is a technical decision, and it ends when the fault is fixed and the system can be trusted again. The first kind of stop is, in a terrible way, straightforward. The second kind raises harder questions, because it suggests that the system itself is fragile, and that a failure in one part of it can bring the whole thing down. That is why the investigation into Friday’s failure matters so much, and why the FAA’s eventual explanation will be read so closely. If the cause was a single broken piece of equipment, the fix may be simple. If the cause was something in the design of the system, or in the way its centres are connected, the fix may be much bigger.

5.2 How Air Traffic Control Normally Works

To understand why a communications failure could stop the whole country, it helps to understand how air traffic control normally works. The system is built in layers. When an aircraft takes off, it is guided by the controllers in the tower at its airport. Once it climbs away from the airport, it is handed to a radar facility that guides it through the airspace around the city. And once it reaches cruising altitude, it is handed to one of the Air Route Traffic Control Centers, the regional facilities that guide aircraft as they cross the country. As the aircraft flies, it is handed from one centre to the next, each one taking responsibility for it as it passes through its region, until it is handed back down to the facilities that guide it into its destination airport. At every stage, the controller and the pilot must be able to talk to each other, and the controller must be able to see the aircraft on radar.

That chain of handoffs is the reason a failure in the centres matters so much. If a centre cannot communicate with the aircraft in its region, it cannot guide them, and it cannot safely hand them to the next centre. And if several centres lose communications at the same time, the chain breaks in several places at once. That is what the FAA said happened on Friday: a communication issue affecting all of the Air Route Traffic Control Centers. In that situation, the safe choice is to stop sending new aircraft into the chain, because every new aircraft is another one that needs to be guided and handed over, and every handoff is another chance for the broken link to cause a problem. The aircraft already in the air could still be brought down, because the parts of the system that guide landings were still working, but nothing new could safely be added. That is the logic of a ground stop, and it is why the FAA’s decision, drastic as it looked, was the cautious one.

6. A System Under Strain for Years

Friday’s failure did not happen in a system that was in good health. The American air traffic control system has been under strain for years, beset by equipment failures, communications problems and shortages of controllers, while the FAA tries to replace aging infrastructure that in some cases dates back decades. That is not a new observation. It has been made by the FAA itself, by Congress, by the airlines, and by the controllers’ union, and it has been made after every major disruption of recent years. What Friday added was a new and more alarming example: a failure that was not local, not caused by weather, and not limited to one facility, but that spread across the centres that handle aircraft in flight across the whole country. The disruption was, in the words of Reuters, “the latest sign of strain on the US air traffic control system”, and it came on the same day that the FAA and the White House were asking Congress for more money to fix it.

The strain has several causes, and they have been building for a long time. The equipment that controllers use is old, and some of it relies on technology that has not been updated in decades. The number of controllers is below what the FAA says it needs, and training new controllers takes years. And the demand on the system keeps growing, with more flights every year and more complex routes to manage. Each of those problems on its own can be managed. Together, they leave a system with very little slack, so that when something goes wrong, there is not much spare capacity to absorb it. Friday’s failure may turn out to have a specific and fixable cause, but it happened in a system that many experts already regarded as fragile, and that context is part of the story.

6.1 Aging Equipment and Controller Shortages

The equipment at the heart of American air traffic control is, in many places, decades old. Some of the radar and communications systems still in use were designed in an era before the internet, and some of the parts they need are no longer made. The FAA has been working for years to replace them, but the work is slow, expensive and complicated, because the system cannot be switched off while it is being rebuilt. Controllers have to keep guiding aircraft with the old equipment while the new equipment is installed alongside it, and the two have to work together without interruption. That is a difficult engineering task at the best of times, and it is one reason the modernisation has taken so long. The result is a system in which new and old technology sit side by side, and in which a failure in one part can affect parts that were supposed to be separate.

The shortage of controllers is the other half of the strain. The FAA has said for years that it does not have enough fully trained controllers, and the gap has been made worse by retirements and by the long time it takes to train a replacement. A controller who guides aircraft across the country needs years of training and experience before they can work on their own, and the pipeline of new controllers cannot be sped up quickly. When there are too few controllers, the ones who are there work longer hours and handle more traffic, and the system has less room to cope when something goes wrong. None of this caused Friday’s communications failure, and it would be wrong to say that it did. But it is the background against which the failure happened, and it is the reason the failure could spread as far and as fast as it did. A system with spare capacity can absorb a shock. A system running close to its limits cannot.

6.2 The $12.5 Billion Fix — and a New $30.1 Billion Ask

The money to fix the system has been a matter of public debate for years, and Friday put it back at the centre of the argument. Last year, Congress approved $12.5 billion to fix the FAA’s aging communications system, a recognition that the equipment controllers rely on was no longer fit for the job. That money is being spent, but the work it pays for takes time, and the system it is meant to fix is still the one that failed on Friday. On the same day as the ground stop, the FAA and the White House asked Congress for another $30.1 billion to address other issues in the system. The timing was a coincidence, but it was a telling one: on the day the system stopped working, the government was already asking for tens of billions of dollars more to fix it.

Whether that money will be approved, and whether it will be enough, are questions for Congress, and they will be argued over in the weeks and months ahead. What is not in doubt is that the modernisation of American air traffic control is one of the largest and most expensive infrastructure projects in the country, and that it has been under way for years without yet delivering a system that can be relied on not to fail. Friday’s ground stop will be used by both sides of that argument. Those who want more money for the FAA will say it proves the system needs urgent investment. Those who are sceptical will ask why $12.5 billion has not already fixed the problem. Both arguments will be made, and both will be heard. But the passengers who were stranded on Friday will not be much interested in the politics. They will want to know that the system they depend on will work the next time they fly.

7. What Travellers Should Do Now

For the passengers caught in Friday’s disruption, the practical advice was simple and unsatisfying: check with your airline before you travel, and do not go to the airport until you know your flight is going. The FAA said no more than that, and the airlines said much the same. With no official resumption time, and with the FAA’s status page no longer listing a nationwide stop by late afternoon but no statement confirming a full resumption, the only reliable source of information about a particular flight was the airline operating it. Passengers were told to check their flight status online or through their airline’s app, to watch for messages from the airline, and to expect delays and cancellations even after the stop was lifted. The advice applied to everyone travelling on Friday evening and into the weekend, because the backlog created by the stop would take time to clear, and because aircraft and crews were out of position.

The disruption also affected people who were not flying on Friday at all. Passengers booked on Saturday flights found their aircraft had not arrived where they were supposed to be, because the aircraft that should have flown in on Friday evening was still sitting on the ground somewhere else. Crews who should have been in place for Saturday morning were in the wrong city. And the rebooking of thousands of stranded Friday passengers onto Saturday flights filled seats that Saturday passengers had already booked. The result was a weekend of knock-on delays and cancellations that spread well beyond the hours of the ground stop itself. Airlines worked through the night to rebuild their schedules, but the work of untangling a nationwide stop takes time, and the effects were still being felt on Saturday.

7.1 Checking Your Flight Before Heading to the Airport

The single most important thing a traveller could do on Friday evening was to check the status of their flight before leaving for the airport. The FAA’s advice, and the airlines’ advice, was the same: do not travel to the airport until you know your flight is operating. That advice sounds obvious, but it matters more in a nationwide disruption than in a normal delay, because in a nationwide disruption the departure boards at the airport are no more informative than the airline’s website, and because an airport full of passengers whose flights have been cancelled is an airport where it is harder for the airlines to help anyone. Checking online, through the airline’s app, or by phone, and waiting for a confirmed departure time before travelling, was the best way to avoid a wasted journey and a long wait in a crowded terminal.

Passengers who had already arrived at the airport were advised to stay in contact with their airline and to watch for updates, but also to be prepared for a long wait or an overnight stay. Airlines began offering rebooking onto later flights, and in some cases onto flights the next day, but the number of passengers needing rebooking was far larger than the number of spare seats available. Some passengers were offered hotel rooms. Others were told to make their own arrangements and claim the cost back later. The details varied from airline to airline, and from airport to airport, and the only consistent advice was to keep checking, keep the airline’s contact details to hand, and keep any receipts for expenses, because the question of who pays for a night in a hotel after a nationwide ground stop is one that airlines and regulators will be sorting out for some time.

7.2 International Flights and Rebooking Rights

International travellers faced a particular kind of uncertainty on Friday, because the FAA’s order treated their flights differently from domestic ones. Inbound international flights were to be managed on a case-by-case basis, which meant that some long-haul flights were allowed to land in the United States while others were held or diverted, depending on where they were and what the controllers could handle. Flights from the United Kingdom to the United States, for example, could still operate, but the FAA was deciding on each inbound international service individually, and nothing could leave a United States airport until the ground stop was lifted. That left passengers on both sides of the Atlantic in limbo: those flying into the United States did not know whether they would be allowed to land, and those flying out of the United States knew they would not be leaving until the order was lifted.

The British Foreign, Commonwealth and Development Office said it kept its travel advice for the United States under review, and the FAA publishes live airport conditions on its national airspace status page. For passengers whose flights were cancelled, the question of rebooking and compensation depends on the airline, the ticket, and the rules of the country where the flight was booked. Airlines generally rebook passengers whose flights are cancelled onto the next available service, but in a disruption on this scale, the next available service may be a day or more away. Passengers were advised to contact their airline directly, to keep records of any extra costs, and to check the terms of their travel insurance. What nobody could tell them on Friday evening was when they would actually be able to fly, and that, more than the question of who would pay, was what most of them wanted to know.

8. The Questions That Remain

Friday’s ground stop left behind a set of questions that will take days, and in some cases much longer, to answer. The first and most important is what actually failed. The FAA has said its technicians are investigating, and the Transportation Secretary has said the same. But until the investigation is complete, nobody outside the agency can say with confidence whether the failure was a broken piece of equipment, a software fault, a power problem, or something in the way the system’s centres are connected to one another. The answer matters, because it determines what has to be fixed, and because it determines whether the same thing could happen again tomorrow. If the cause was a single component, the fix may be quick. If the cause was a weakness in the design of the system, the fix may take years and billions of dollars. The FAA has not said which it is, and the public will have to wait for the investigation to run its course.

The second question is when normal flying will resume, and how long the effects of Friday’s stop will last. By late Friday afternoon, the FAA’s status page no longer listed a nationwide ground stop, but the agency had issued no statement confirming a full resumption, and airlines were still working through the backlog. The third question is what the stop means for the modernisation of the air traffic control system, and whether the money already approved, and the money now being asked for, will be enough to prevent a repeat. And the fourth question is the one that matters most to the people who were stranded: who is responsible, and what will be done to make sure it does not happen again. Those questions will be asked in Congress, in the FAA, and in the airlines, and they will be asked for a long time. The coming days will provide the answers.

8.1 What Actually Failed

The investigation into Friday’s failure will have to answer a series of specific technical questions, and the answers will determine what happens next. The first is what broke. The FAA’s website called it an “equipment outage”. The Transportation Secretary called it a communication issue affecting all of the Air Route Traffic Control Centers. Sources inside the FAA described a rolling frequency outage. The Air Current reported impacts to air traffic control frequencies and radar capabilities. The National Weather Service reported a national radar outage. Those accounts may all describe the same failure from different angles, or they may describe different parts of a wider breakdown. The investigation will have to sort out which is which, and it will have to explain how a problem that appears to have begun at the Kansas City centre around 3:30 p.m. Eastern time spread to other centres within half an hour.

The second technical question is why the failure spread. Air traffic control centres are supposed to be separate from one another, so that a failure in one does not bring down the rest. If a fault in one centre was able to spread to others, the investigation will have to explain how, and whether the connections between the centres are a weakness that needs to be fixed. The third question is why the backup systems did not take over. Air traffic control is supposed to have redundancies, so that if one system fails, another takes its place. On Friday, whatever backups existed were not enough to keep departures moving, and the investigation will have to explain why. And the fourth question is whether the failure was foreseeable. If the equipment that failed was known to be old or unreliable, and if the FAA had already identified it as a risk, the investigation will have to explain why it had not been replaced. Those are the questions the technicians are working on, and their answers will shape the future of American aviation.

8.2 The Questions That Remain

Beyond the technical questions, Friday’s ground stop leaves a set of wider questions that will be debated for months. The first is about money. Congress approved $12.5 billion last year to fix the FAA’s aging communications system, and on Friday the FAA and the White House asked for another $30.1 billion. The stop will be held up as proof that the money is needed, and also as proof that the money already spent has not been enough. The debate over how much to spend, and how quickly, will be sharper now than it was before Friday, and it will be watched closely by everyone who flies. The second question is about accountability. Somebody will have to answer for a failure that stopped the whole country from flying, and the answers will be sought in the FAA, in the Transportation Department, and in Congress.

The third question is about the passengers. Thousands of people were stranded on Friday, and thousands more will be affected over the weekend as the backlog clears. They will want to know what they are owed, and by whom, and whether the airlines and the FAA did enough to look after them. And the fourth question is the simplest and the hardest: could it happen again? The FAA will say that it is investigating, that it is fixing what failed, and that it is working to make the system more resilient. The public will judge those promises by what happens next, and by whether the system holds the next time it is tested. Friday was the second nationwide ground stop since September 11, 2001. The hope, for everyone who flies, is that it is a long time before there is a third. The coming days will provide the answers.

Comments

comments