By Samir Ourdyl · Nov. 14, 2026
Airlines were still canceling thousands of flights Saturday after the Federal Aviation Administration issued a rare nationwide ground stop Friday afternoon, halting departures from U.S. airports for more than four hours because of communications problems in the air traffic control system.
Transportation Secretary Sean Duffy said Friday night that getting planes back in the air would take time. "It's going to be slow," he told reporters, according to news accounts of a White House briefing. Officials said there was no indication the outage was a cyberattack, and they attributed the stop to problems with aging communications equipment.
What happened
The FAA said it issued a nationwide ground stop for all U.S. airports "following communication issues impacting multiple Air Route Traffic Control Centers." The agency's notice said the stop was "due to extraordinary circumstances and for reasons of safety," and that technicians were investigating. That initial statement, dated Friday, was marked preliminary and subject to change.
CNBC reported that the FAA halted departing U.S. flights around 4 p.m. Eastern time Friday. The Washington Post and CBS Boston, citing Duffy and the agency's later updates, said the ground stop ended at about 8:15 p.m. ET, after more than four hours. Logan Airport said shortly after 8:30 p.m. that the nationwide stop had been lifted, GBH reported.
A limited number of flights began leaving after the order was lifted, but airlines were left with planes and crews out of position. "Before clearing flights to resume, we thoroughly tested our systems to confirm they were stable and that operations remain reliable," the FAA said late Friday, according to CNBC.
It was the first nationwide ground stop since January 2023, when a key FAA computer system malfunctioned, and only the second since the Sept. 11, 2001, attacks, according to CNBC, GBH and CBS Boston.
Why officials said it happened
At a White House news conference Friday night, Duffy blamed outdated air traffic control technology. He said routers were overloaded with data and began giving air traffic control centers inconsistent information, CNBC and CBS Boston reported. ABC News quoted him calling the situation an "emergency" and asking Congress for $50 billion for a "complete overhaul" of the system.
"We didn't think we would have this kind of outage," Duffy said, according to ABC News. He said the systems in place "kept everybody safe -- everyone landed," but also warned, "you will have more of these" unless the system is upgraded.
Homeland Security Secretary Markwayne Mullin described the problem as a telecommunications outage and said there was no indication it was a cyberattack, though officials said they were still investigating, according to ABC News, GBH and CNBC. Asked whether the episode was connected to Thursday's Microsoft outage, Mullin called them separate issues, NBC Boston reported.
How many flights were hit
Figures from flight-tracking services moved through the night and into Saturday, and they can include delays or cancellations that were not caused only by the ground stop. CNBC, citing FlightAware, noted that some Friday disruptions were due to bad weather.
As of early Saturday, ABC News, citing FlightAware, reported 9,132 cancellations and 7,030 delays on Friday, and said 3,374 flights had already been canceled Saturday, with 1,008 delayed. Combined, ABC said 12,506 flights had been canceled Friday and Saturday as of 6:52 a.m. ET, a total that was expected to grow. CNBC, using FlightAware figures as of 5:45 a.m. ET, similarly reported about 9,000 U.S. cancellations and more than 7,000 delays on Friday, and more than 3,000 cancellations and close to 1,000 delays on Saturday.
Duffy said he believed "it's going to take us some time to get back to capacity," ABC News reported. Airlines offered travel waivers, CNBC said, and some carriers canceled remaining Friday-night flying. CBS Boston and GBH, citing JetBlue, said the airline canceled all remaining domestic flights Friday, with the exception of Europe-bound departures from Boston Logan and New York's Kennedy Airport.
In Massachusetts
Boston Logan International Airport was swept into the nationwide halt. Massport, which operates Logan, told passengers Friday night that as operations gradually returned, some delays might continue, and it urged travelers to check with their airlines, CBS Boston reported.
According to FlightAware figures cited by CBS Boston, Logan had 251 delays and 389 cancellations as of 11:15 p.m. Friday. On Saturday morning, GBH, also citing FlightAware, said there were 184 cancellations and 30 delays at Logan as of 7:30 a.m.
Jennifer Mehigan, a Massport spokesperson, told the Boston Globe, "It might take a day or two to get back to normal, similar to a blizzard." She said some international flights took off, but that most domestic flights were canceled for Friday night, the Globe reported. Massport also said the FAA permitted some transatlantic flights to leave Logan during the ground stop, according to CBS Boston and NBC Boston.
Gov. Maura Healey said she had been briefed and was in touch with Massport "about what it means for people flying in and out of Massachusetts," according to the Globe and NBC Boston.
If you are traveling
People with flights this weekend should check directly with their airline for the latest status, as Massport and the airlines advised. Officials have said it may take days, not hours, for schedules to settle as aircraft and crews are moved back into place.
This account reflects reporting as of Saturday morning, Nov. 14, 2026, Eastern time. Cancellation and delay counts were still changing. Check primary sources and your carrier for the latest.
