Breaking News Today: United Airlines System Outage
The breaking news today from America's airports was a reminder of how quickly a single computer failure can bring an airline to a standstill. United Airlines suffered a widespread technology outage on Monday evening, November 16, that delayed departing flights across its network for more than an hour, just three days after a nationwide air traffic control failure grounded flights across the United States. The airline said it had resolved the problem by around 6 p.m. Eastern time, but by then hundreds of flights had been delayed, passengers had been left waiting at gates across the country, and the country's aviation system had suffered its second serious disruption in four days.
The outage began in the late afternoon. Just before 5 p.m. Eastern time, United confirmed that it was dealing with a technology issue affecting departing flights, and that it was working to fix it. Within the hour, the airline said the issue had been resolved. In a statement, United said that while some flights were delayed, there was no impact on flights already in progress, or on United Express regional flights — the distinction that mattered most to the tens of thousands of passengers already in the air when the systems went down. The airline also said there was no indication that the problem was connected to cybersecurity, a point it repeated to several news outlets through the evening.
What Happened on Monday Evening
The first sign of trouble came from the flight deck. Air traffic control audio captured by the website ATC.com showed the moment the outage hit, with United aircraft having trouble receiving dispatch data — the information a flight crew needs before a plane can legally leave the gate. The problem was not with the aircraft themselves, or with the runways, or with the weather. It was with the flow of information between the airline's systems and its planes, and without that information, the planes could not go.
An internal memo from United's pilots' union, seen by Reuters, gave the clearest account of what had failed. A companywide, web-based outage had affected multiple applications used by pilots, including crew communications, the memo said. The airline had been unable to provide final aircraft weights for departing flights — the weight and balance figures that determine how much fuel a plane needs, how its cargo should be loaded, and whether it is safe to take off. Pilots were advised to follow airport station guidance on whether to leave their gates, a holding instruction that left the decision, in effect, to the people on the ground at each airport. A subsequent memo from the union said the airline's systems were coming back online and directed pilots to check updated company communications.
United acknowledged the issue publicly just before 5 p.m. Eastern time, saying a technology outage was affecting departing flights. About an hour later, the airline announced that the issue had been resolved. In its statement, the carrier apologised to customers and directed them to check the status of their flights on its app or its website. The airline did not immediately disclose what had caused the failure, and by Monday evening it still had not offered a technical explanation — only the assurance that the problem was fixed, that it was not a cybersecurity incident, and that flights already in the air and United Express services had not been affected.
The Federal Aviation Administration was quick to distance its own systems from the failure. The FAA said United was experiencing a technology outage on its end, and that it was not an FAA equipment issue. Transportation Secretary Sean Duffy, speaking on Fox News' "Hannity" show on Monday evening, was emphatic on the same point. "This is not an FAA system-wide problem," Duffy said. He added that he did not know what had caused the United outage, but that it was unrelated to the FAA's own systems — a distinction that mattered, because the FAA's systems had failed catastrophically only three days earlier, and the first question on Monday evening was whether the two failures were connected. They were not, according to both the airline and the government. The United outage was United's problem, and it was a problem of the airline's own making.
What Went Wrong: The Systems Behind the Delays
That is what the United outage took away. According to the pilots' union memo, the web-based failure hit the applications the pilots use to communicate with the airline and to receive the data they need. Crew communications — the messaging systems that connect the flight deck to dispatchers and to the airline's operations centre — were affected, along with the systems that produce the final weight figures. Air traffic control audio captured United crews reporting that they could not receive dispatch data, including weight and balance information and aircraft performance calculations. The planes were ready. The crews were ready. The information was not.
The Numbers: Hundreds of Flights Delayed
The scale of the disruption is best measured in the flight-tracking data, which told a story that grew worse through the evening even after the airline said the problem was fixed. As of 6:10 p.m. Eastern time, according to the flight-tracking website FlightAware, 554 United flights had been delayed — about 17 percent of the airline's schedule for the day — and 22 had been cancelled. By 6:50 p.m., the number of delayed flights had risen to 645, or 20 percent of the schedule, with 25 cancellations. By 9:50 p.m., FlightAware was reporting 811 delays, roughly 25 percent of United's flights for the day, and 28 cancellations.
Those figures need to be read with care. Not every delay on Monday was caused by the outage. The airline industry was still recovering from Friday's nationwide ground stop, and some of the delays counted by FlightAware would have happened anyway, as crews and aircraft were out of position from the weekend's chaos. The 645 delayed flights at 6:50 p.m. were not all outage delays, and the 811 delays by the end of the day included the knock-on effects of a system that had been under strain for days. United itself told CNN that fewer than 150 flights were directly affected by the outage — a far smaller number than the FlightAware totals, and a reminder that the airline and the tracking data were measuring different things: the airline counting the flights its systems held back, the trackers counting every flight that ran late for any reason.
What the numbers do show, unambiguously, is a bad day for a major airline. Even the most generous reading — fewer than 150 flights directly held by the outage — means more than a hundred departures delayed, and thousands of passengers affected, on a Monday evening in the week before Thanksgiving. The cancellations were concentrated, in part, at San Francisco, where about five mostly international flights were cancelled, according to flight-tracking data. For the passengers on those flights, the distinction between an outage delay and a knock-on delay was academic. They were not going where they had planned to go, when they had planned to go there.
United, the FAA and the Transportation Secretary Respond
The public response to the outage unfolded over the course of the evening, and it followed a familiar pattern. The airline acknowledged the problem, said it was fixed, apologised, and pointed passengers to its app. The FAA said the problem was not theirs. The Transportation Secretary said the same thing, more forcefully, on television. Nobody, by the end of the night, had said what had actually gone wrong.
United's statement was brief. "Earlier today we experienced a technology-related issue that impacted some departing flights. The issue has been resolved," the airline said, adding that passengers should check the latest status of their flights on its website or in its app. In a separate statement, the airline said: "While some flights were delayed, there was no impact on flights in progress, or on United Express flights." The airline told Fox Digital that there was no indication the incident was a cybersecurity issue, and it repeated that assurance to other outlets. What it did not do was explain the cause — whether a server failure, a software bug, a network problem, or a vendor's system going down. By Monday night, the cause remained unknown, at least publicly.
The FAA's response was equally brief, and it was aimed at a different audience. The agency said United was experiencing a technology outage on its end, and that it was not an FAA equipment issue. The distinction was important to the FAA, because the agency's own equipment had failed on Friday, and the agency was still answering questions about that failure when Monday's outage happened. Duffy, the Transportation Secretary, made the same point on Fox News' "Hannity" show. "This is not an FAA system-wide problem," he said, adding that he did not know what had caused the United outage. The secretary had held a 45-minute news conference on Saturday morning to address the Friday ground stop, and on Monday evening he was back on television, this time to say that the latest failure belonged to someone else.
Days After the FAA's Nationwide Ground Stop
The United outage cannot be understood without the failure that preceded it. On Friday, November 13, the FAA ordered a nationwide ground stop — the longest such stoppage of departing flights since the September 11, 2001 attacks — after a failure in the agency's own telecommunications network. The FAA later described the problem as instability in its network, with excessive data affecting aircraft communications and radar feeds. The instability reached 17 of the agency's 22 Air Route Traffic Control Centers, the facilities that manage high-altitude traffic across the country, and it brought departures to a halt for nearly five hours. Air traffic resumed at around 8:15 p.m. Eastern time on Friday, but the disruption continued through the weekend and into Monday, as airlines worked to get crews and aircraft back into position.
The FAA said it had disabled the relevant functionality on approximately 60 similar routers as a precaution, and Duffy's Saturday news conference was an attempt to reassure the public that the system was stable. But the weekend was chaotic, with cancellations and delays rippling through the system, and the industry had only just begun to return to normal when United's systems failed on Monday evening. The two failures were unrelated — one was the government's, one was the airline's — but together they told a story about an aviation system that is more fragile than the travelling public assumes. Two serious technology failures in four days, from two different parts of the same system, is not a coincidence that can be waved away. It is a pattern.
The Friday ground stop was itself the culmination of years of warnings about the state of America's air traffic control infrastructure. The system that guides planes across American skies is built, in part, on technology that is decades old, and the people who run it have been warning for years that it needs investment. That warning has now been taken up at the highest level of the government. On Monday, the same day as the United outage, TrendSignal reported that the Trump administration was demanding $50 billion to fix air traffic control — a figure that gives a sense of the scale of the problem, and of the political fight that lies ahead over who pays for the fix.
Air Traffic Control Funding and the $50 Billion Question
The demand for $50 billion to modernise air traffic control did not come out of nowhere. It came after a year in which the system's failures have become impossible to ignore: the telecommunications failure on Friday, the staffing shortages at control towers, the near-misses that have made headlines, and the sense, shared across the industry, that the infrastructure is being held together by the dedication of the people who operate it rather than by the quality of the equipment they use. The administration's figure is a starting point for a negotiation with Congress, and it is a large one — large enough to suggest that the problem is not a matter of patching a few systems, but of rebuilding the core of the network.
Thanksgiving Travel Week Looms
The timing of the outage is what makes it more than a one-day story. Monday's failure came just days before the Thanksgiving travel week, the busiest travel period of the year in the United States, when tens of millions of Americans fly to be with their families. The airlines have spent weeks preparing for the surge, adding flights, calling in extra crews, and warning passengers to arrive early. An outage on the Monday before Thanksgiving week is a warning of what could happen when the system is under maximum load — and a reminder that the margin for error is thin.
What Happens Next for Passengers
The immediate aftermath of the outage is a period of recovery. United's systems are back online, the delayed flights have departed, and the airline's schedule is returning to normal. The passengers who were delayed on Monday will, for the most part, have reached their destinations by Tuesday, and the airline will absorb the cost of the disruption in the ordinary way — in rebookings, in compensation, and in the slow erosion of trust that follows every outage. The FAA, for its part, will continue to monitor its own network, and the Transportation Department will continue to insist that the two failures were unrelated, which, on the evidence available, they were.
What is certain is that the events of the last four days have changed the conversation about American aviation. A nationwide ground stop and an airline system outage, in the same week, have made the abstract question of infrastructure investment concrete in a way that years of warnings did not. The travelling public does not need to understand weight and balance calculations, or air route traffic control centres, or the telecommunications networks that connect them. It needs to know that when it buys a ticket, the plane will take off. On Monday evening, for hundreds of United flights, it did not. That is the story, and it is the reason the outage matters — not because it was the longest, or the worst, but because it came when the system was already failing, and because it showed, again, how quickly a technology failure becomes a human one.
Source: AP News