Mike Hammett has spent more than 20 years building and operating ISP, voice, internet exchange, and colocation networks.
This article is part of a series on government network outages. The other pieces will be published as they are completed.
TL;DR
- The November 13, 2026, ground stop halted U.S. departures for more than four hours and disrupted communications at up to 17 of the FAA’s 22 en route centers [1][2]. The FAA’s initial investigation points to two remote sites, including one where L3Harris, its network contractor, was deploying a new router [2].
- By this article’s count, it was at least the thirty-fourth FAA telecom or network failure since 1988 to take service down. In each of the 30 with a published cause, counting November 13’s preliminary one, one failure alone took service down, or two failures shared a cause, or a second failure came before the first was repaired.
- The FAA leases its network, and the contract sets the design. In 2008, 16,400 of 21,871 planned services, including en route air-to-ground communications, were in a single-path class [3]. Replacing copper with fiber does not fix that.
- The FAA can write diversity audits, staged changes, out-of-band management, and a third path that is not wireline into its new AT&T contract, and it should require the same of L3Harris, which runs today’s network, until the AT&T network replaces it.
November 13, 2026
Shortly after 3:30 p.m. Eastern on November 13, 2026, the FAA saw instability in radar and communications at its centers and terminal radar approach controls (TRACONs) [1]. At 3:54 p.m., it stopped departures nationwide [1]. The FAA later said instability began at 17 of its 22 Air Route Traffic Control Centers and spread into several TRACONs [2], and FAA Administrator Bryan Bedford said “no facilities went dark” [4]. The stop lifted at 8:15 p.m. [1]. FlightAware counted more than 9,000 U.S. flights canceled that day and about 6,700 the next [4], though the FAA says not all of the day’s cancellations were directly caused by the ground stop [2]. That day, Transportation Secretary Sean Duffy said the routers “got overloaded with data” and blamed “analog telecom” [1].
At a briefing on November 14, Duffy said a preliminary investigation found that an L3Harris contractor was switching old copper wire to fiber at a remote FAA location while replacing a router [5]. The router “started flooding other routers in our air traffic control system,” he said, with “over 1,000 connection attempts every four to five seconds” [4][6]. CBS reported that the router flooded the system for 45 minutes and that the FAA could not determine the cause of the instability [5]. “Once we’re able to isolate what was being done at this remote location, all of our systems came back online,” Duffy said [4]. Nick Daniels, who heads the controllers’ union, said, “We know we didn’t have communications with airplanes, or that we were switching airplanes to different frequencies because their communications were being disrupted” [4].
Duffy put the open question as whether it was “user error or install error from L3Harris” or a faulty router, and said, “We haven’t determined what the fault was” [6]. He said that “L3Harris actually owns that network” [7] and that he did not believe the outage was a cyberattack [4][6]. Asked why the work was done at 3 p.m. on a Friday, he said, “It shouldn’t have that kind of impact,” and that there would be “a reevaluation of when we do this work” [4][6]. In May, when L3Harris announced it had passed the halfway mark of its rebuild of the FAA network, it said the work was being done with “zero operational disruptions” [8].
On November 15, The Wall Street Journal reported that the router was a new Juniper Networks device L3Harris had installed at an FAA radio site in El Dorado, Arkansas, and that data from it, and possibly from a router at a radar site in Amarillo, Texas, overwhelmed the system [9]. The same day, Duffy said the Amarillo router, replaced about three weeks earlier, had also flooded the network, and that both routers were at an L3Harris lab in Florida for testing with engineers from the FAA, Juniper, and Cisco [10][11]. He put the number of routers of that type at 69 [10], and the Journal reported about 60 Juniper routers in the FAA’s network [9]. Officials identified a router feature that appeared to cause the overload, which a government official described as a broadcasting feature that sent data “more broadly than necessary,” and the FAA has disabled it on all its Juniper routers [9]. A spokesman for Hewlett Packard Enterprise, which owns Juniper, said the devices did not fail and appeared to have been working as intended [9]. After CenturyLink’s 2018 outage, which spread over a management channel that was enabled by default and unused, the FCC concluded that system features not in use “should be turned off or disabled” [12].
Duffy is right that the work shouldn’t have that kind of impact, at any hour. Night work would have put fewer aircraft in the air when it failed, but it would not have kept the trouble at the sites where it started. More than 1,000 connection attempts every four to five seconds is roughly 200 to 250 a second. The reason for outage should say what kind of traffic that was and why it was enough to destabilize the system, whether control-plane policing or storm control was configured on these routers, whether the feature the FAA switched off was on by default, and whether L3Harris could reach the affected routers over a path that did not run through them.
Two months before the outage, GAO concluded that “the FAA is buying delivery speed at the risk of cost uncertainty and potential disruptions,” and warned that installations scheduled at the same sites without addressing conflicts risked “excessive disruptions to air traffic control operations” [13]. With 5,170 lines to cut over in all, every cutover is a change on a live network, and the program has to make each one unable to reach past its own site.
The FAA has published a preliminary account but not a final reason for outage, and it says it and L3Harris “continue to investigate the root cause” [2]. Duffy said the findings would be shared when the review is done, and Bedford said he expected “a very transparent hearing” [4]. Representatives Rick Larsen and André Carson, the top Democrats on the House Transportation and Infrastructure Committee and its aviation subcommittee, said they expect to hear from Bedford at a hearing by early December [14]. On a properly designed network, a change reaches one half of a redundant pair, proves itself, and only then reaches the other half. A change that can reach every center in one step is a single point of failure, however old the routers are.
The FAA Leases Its Network
The FAA Telecommunications Infrastructure (FTI) program, awarded in 2002, put the agency’s communications on a contracted network [15]. The DOT Inspector General described FTI in 2015 as owned and maintained by Harris Corporation and leased to the FAA [16].
The successor program, FAA Enterprise Network Services (FENS), went to Verizon Business Network Services on March 27, 2023 [17], with a 15-year value of $2.4 billion [15][17]. On August 11, 2026, the FAA used waiver authority to make a direct award to AT&T Enterprise Services [18], with an initial $74.3 million task order while the long-term contract is negotiated [19][20]. Verizon moved to a supporting role [19]. FTI still carries the FAA’s traffic: the FAA’s account of November 13 says its legacy equipment became unstable when data began flooding “the FAA FTI network” [2].
That makes these outages failures of carrier-grade network engineering, delivered by carriers and defense contractors under federal contracts. The FAA’s part is what it specifies, what it pays for, and what it verifies. The public record does not show whether the FAA now verifies physical path diversity on its leased circuits.
1988 to 1991: The Template
On May 8, 1988, fire broke out at Illinois Bell’s Hinsdale central office, west of Chicago [21]. The circuits between Chicago Center in Aurora and O’Hare’s tower ran through that one building, and the fire crippled the center’s communications with O’Hare and Midway [22][23]. Controllers at both airports widened the spacing between flights to 20 miles, and O’Hare, which could handle 150 aircraft an hour, took only 50 arrivals an hour [22].
On May 4, 1991, four of the FAA’s major air traffic control centers shut down for 5 hours and 22 minutes, and the cause was logged as “Fiber cable cut by farmer burying dead cow. Lost 27 circuits” [24]. Later that year, in a report to a House subcommittee, the FAA counted 114 major telecommunications outages that led to flight delays between August 1990 and August 1991 [24].
On September 17, 1991, AT&T moved its Thomas Street switching center in lower Manhattan from Con Edison power to its own diesel generators under a load-shedding agreement. A voltage surge during the transfer disabled the equipment powering the transmission facilities and the alarm system with it, according to the FCC’s report [25]. A burned-out indicator lamp, a muted alarm bell, and a power crew sent to an off-site training class meant nobody noticed until the batteries were nearly drained [26]. GAO reported in 1993 that the outage caused a significant loss of the FAA’s radar sites, radio channels, and computer links, along with 1,174 canceled or delayed flights [27].
2009: One Router Error, 129 Facilities
On November 19, 2009, an FTI routing failure took down flight plan processing nationwide from about 5:15 a.m. to 9 a.m. Eastern. The failure also took down the second national node in Hampton, Georgia [28]. The National Airspace Data Interchange Network (NADIN) ran there and in Salt Lake City, so the geographic redundancy between Utah and Georgia did not help [28].
The DOT Inspector General’s review of the 2009 outage traced the cause to Harris. During FTI’s transition from the old network to the new fiber network, Harris had installed temporary “bridge” routers at 26 core sites. On October 21, 2009, an engineer misconfigured the one at Los Angeles Center, and the error sat dormant for four weeks. On November 19, an engineer put a replacement router in service at Los Angeles and copied over a route map that lacked a needed “no” statement [29]. The error blocked about 75 percent of routes across the FTI fiber network for five hours. It reached 129 facilities instead of the 21 it should have affected, and it delayed 820 flights [29].
Restoration took five hours partly because Harris’s automated alert tool was misconfigured, and its filter “caused the alarms to be filtered for all routers on the FTI network” [29]. When the fix came, it waited on a technician to reach Salt Lake City and pull a router card [30].
The Inspector General’s letter also covered what the outage exposed. Harris had confirmed “either the complete lack or inadequate proof of diversity” between primary and alternate paths at several critical facilities, including the FAA’s William J. Hughes Technical Center and the Baltimore tower, and some FTI sites had lost their diversity after AT&T or Sprint upgraded their networks [29]. FAA had three representatives on site at Harris but had “limited ability to oversee FTI,” could not directly monitor the FTI network, and took a reactive approach to network vulnerabilities [29]. As of December 2009, 8.19 percent of FTI services did not meet their availability requirements, and the FAA’s Automatic Dependent Surveillance-Broadcast (ADS-B) program had chosen not to use FTI because of reliability and security concerns [29].
One latent error, introduced during a network transition, hidden by the alarms meant to catch it, and copied into new equipment, reached six times as many facilities as it should have.
2014: Two Fiber Paths Into One Room
On September 26, 2014, an FAA contract employee deliberately started a fire that destroyed FTI equipment at Chicago Center in Aurora, Illinois [16][31]. The center could not control traffic for more than two weeks [16].
Outside the building, FTI had two independent primary and backup fiber pathways. Inside, all FTI equipment racks, primary and backup, were located close to one another [16]. Water from the fire suppression system destroyed about half of them [16]. Chicago TRACON lost its long-range radar because that feed was routed through Chicago Center [16]. Rerouting communications to other facilities took days rather than hours, and the backup facility could not be used because its equipment was incompatible [16]. Diverse fiber that lands in one room is a single point of failure.
Newark and Philadelphia: The Same Facility Three Times
The FAA moved Newark approach control from the New York TRACON to the Philadelphia TRACON in 2024 [32]. Radar data for Newark still came from an FAA facility in Westbury, on Long Island, over a remote line to Philadelphia [33]. On April 28, 2025, controllers working Newark lost radar and radio for about 90 seconds because of a burnt copper wire, and it happened again on May 9, when primary and redundant communication infrastructure both failed [34]. Duffy said that on April 28, “the primary communication line went down, the backup line didn’t fire” [35]. GAO later reported the FAA’s own attribution, which named old copper wiring and moving the airspace “without adequately testing the reliability of the commercial telecommunications lines used for critical data” [13].
The FAA said later that on September 20, 2026, after a series of error messages on a telecommunications circuit, it had moved the Philadelphia TRACON onto its backup fiber at the request of its contractor, L3Harris, so the primary could be troubleshot [36]. The next morning, a contractor on NJ Transit’s Delco Lead project severed that backup near New Brunswick at about 9:45 a.m. [36][37]. Bedford called the primary one of the “old L3 Verizon circuits” [38], and Verizon said its fiber running beside the rail line had been cut [39]. More than 600 flights into and out of Newark alone were canceled [40]. Two days later, Bedford said replacing the remaining copper with fiber would not be enough to prevent future outages [36].
L3Harris’s FTI page says the network uses multiple local exchange carriers and that the approach “ensures redundancy and reliability across the system” [41]. That describes the network as a whole. At Philadelphia, both paths were Verizon facilities [38][39]. Taking one half of a pair out of service makes the other half a single point of failure until the first comes back, and that window needs its own protection. A same-carrier backup left as the only path, with nothing standing by behind it, breaks the rules of a properly designed network.
Dallas 2025: Primary and Secondary, Cut Together
On September 19, 2025, the FAA’s Dallas TRACON lost radar, frequencies, and automation, and both Dallas airports went into ground stops for hours [13][42]. The FAA blamed “multiple failures of the TDM data telecommunications service provided by Frontier” [42]. American Airlines said the FAA told it two cut fiber cables affected the primary and secondary data paths [43]. Frontier said a third-party contractor in Argyle, Texas, cut its fiber lines, and L3Harris said a fault in the local carrier’s switching gear and a fiber cut both played a part [44]. The FAA itself said an oversight by L3Harris failed to make sure the redundancies in the system functioned properly [43]. More than 1,800 flights were delayed or canceled [13].
By the companies’ own accounts, one afternoon of damage inside one local carrier’s network reached both the primary and secondary paths for the TRACON serving both Dallas airports [43][44]. Whether the two paths also shared a trench, a carrier office, or a TDM switch is what a diversity audit exists to find.
Old Copper Is the Wrong Diagnosis
The FAA attributed Newark to old copper wiring [13], and on November 13 Duffy blamed “analog telecom” [1]. Asked whether its upgrades and modernization efforts caused the ground stop, the FAA said no, that it was “due to the legacy TDM system causing instabilities” [2]. The copper is from the 1960s, the technology is no longer supported by the carriers, and modernization needs money [13]. Congress approved $12.5 billion in 2025 [45], and after the November 13 ground stop, Duffy raised the administration’s request to $50 billion [46]. As of May 2026, the FAA had replaced 2,560 of 5,170 copper lines with fiber [13].
Age explains why components fail more often. It does not explain why a cut on the only working path stops five airports. The Philadelphia backup that was cut in September was fiber, and so were the Dallas paths. On November 13, the change that went wrong was a new router installed during the copper replacement, and data from routers at two sites overwhelmed the system [5][9][10]. Duffy said the telecom provider had forced the move from copper to fiber, and that the cutover work had been done thousands of times and “this has never happened” [47]. Transition work took most of the network down in 2009, when a replacement router put in service during FTI’s move to a new fiber network blocked about 75 percent of the network’s routes [29]. Duffy said on November 15 that disruptions could continue until the last copper lines are replaced at the end of 2028 [9]. A new fiber circuit from the same carrier, in the same right-of-way, landing in the same room, inherits the single points of failure of the copper it replaced. Funding without a diversity requirement buys newer single points of failure.
The Contract Is the Design
When an agency leases its network, the contract decides how diverse it has to be. The DOT Inspector General’s 2008 audit of FTI laid this out. FTI services were sorted into reliability classes. Classes RMA-1 through RMA-3 were built on dual paths. RMA-4 and RMA-5 were single-path, and RMA-4, which included en route air-to-ground communications, made up 16,400 of 21,871 planned services [3]. RMA-4 services had to be restored within 3 hours. In March 2008, the contractor averaged 5 hours and 47 minutes [3].
The same audit found that the Kennedy tower, the New York TRACON, and New York Center had all of their FTI services routed through one switching center run by one telephone company, with no alternate [3]. It found the September 25, 2007, Memphis Center outage, which caused 566 delays over 3 hours, would have been prevented if the alternate path had been routed differently [3]. The audit also counted 21 unscheduled FTI outages with flight delays between December 2006 and August 2007 [3]. FAA told the auditors that FTI was already performing regularly scheduled diversity audits [3]. The contract’s remedy for a missed specification was credits paid back to the FAA [3]. A credit refunds part of the bill. It does not move a circuit out of a shared conduit.
The FAA made its August 2026 award to AT&T without a new competition. Its justification called AT&T the “only Tier-1 provider currently willing and able” to meet the program’s timeline and said a competitive procurement “would require a minimum of 22 months,” too long for the December 2028 deadline [18][20]. It defined a Tier-1 provider as one that “owns core network infrastructure” and said direct engagement with one provides “superior network resiliency” [18]. A buyer that has told one carrier it is the only option has less bargaining power to demand diversity audits, tagging, and penalties. In the industry, Tier-1 describes a network that reaches the whole internet without paying anyone for transit. Neither definition says anything about whether two paths into a center share a trench.
The chain of middlemen makes all of it harder to verify. Under FTI, the FAA contracts with L3Harris; L3Harris buys circuits from Verizon, Frontier, and other local carriers; and those carriers’ outside plant is dug up by other parties’ contractors [39][41][44]. Under FENS, AT&T is prime, Verizon still runs core network functions, and Peraton is the integrator for the wider overhaul [19].
Chaining carriers is a legitimate way to build a diverse route, and it holds up only when someone maps the whole chain to the trench and checks it again after every change. The party that owes the FAA diversity is rarely the party that holds the conduit maps, so every layer between the agency and the trench is another place where a regroomed circuit goes unnoticed. The Defense Department’s rule for its own sites requires the two circuits that connect a site to its core network to stay separate along their entire length, end at two geographically diverse core nodes, and use different “cables, demarks, and digital cross connects” [48].
What a Properly Designed Network Does
Components fail. Fiber gets cut, rectifiers trip, line cards die, and people push bad configurations. A properly designed network accepts that and never lets one failure become a service outage. Two independent failures can still overlap, but two failures that share a cause are a design defect. A “diverse” circuit in the same cable, the same conduit, the same carrier office, or the same equipment room was never diverse. Failures also line up in time, when a backup fails unnoticed or a failed half of a pair stays out of service, and a redundant design runs single-threaded until someone fixes it.
In a properly designed network, primary and backup paths run in separate conduits and through separate building entrances, from different carriers or with documented proof that they share no facility, into equipment in different rooms. The backup carries live traffic or is tested continuously, and a failed half of a pair is repaired as an outage in progress. Every critical device can be reached out of band, over a path that shares nothing with the network it manages. Changes go to one half of a pair at a time, and the reach of any one failure stays small enough that a cut, a card, a power plant, or a change in one place takes down service only where it sits.
The FAA has had its own diversity order since November 1995, when it issued Order 6000.36A, “Communications Diversity”; it was replaced in November 2021 by Order JO 6000.36B, “National Airspace System Service Survivability” [49]. The FAA’s own radio communications order requires engineering for “diversity, redundancy and no single point of failure” based on service criticality [50]. The failures in this record that have a published cause are what those orders are written to prevent.
The Strongest Case for the FAA
The best defense is scale. FTI connects about 5,000 FAA facilities, radars, voice systems, and flight data links, and controllers manage up to 45,000 flights a day [13]. Ground stops are the system failing safe, which is what it should do. Some FAA sites sit where only one carrier or one conduit exists, and true diversity there costs real money.
The ground stops were the right call. Still, at least 29 of the 34 events in the table hit an en route center, a TRACON, a major airport, or the national flight-plan system, and the 2008 audit gives only a location for the other five. The FAA has 22 en route centers [2]. Those buildings and the large TRACONs carry the national system, and most of them sit in or near large metro areas, where a second carrier or a second route is easiest to buy. The 2015 Inspector General report already said the limits seen in Chicago would be similar at many of the centers [16].
What Would Change the Record
The first step is for the FAA to publish a reason for outage for every failure that stops traffic, with an initial report within 72 hours and a final report within 30 days, the same clock its carriers already follow with the FCC [51]. Its carriers already have to file outage reports with the FCC when a primary and backup both fail at a center or airport for at least 30 minutes [51][52], and the FCC’s rules presume those reports are confidential [53]. The public record for most of these events is a press conference and a few sentences. Officials say November 13 began inside L3Harris’s own routers. If so, no carrier may have had an outage to report, and the public record will depend on what the FAA and L3Harris disclose, at the hearing and after.
On August 6, 2026, the FAA paused flights into and out of Minneapolis Center’s airspace over what it called telecommunications issues, and the airport said the ground stop at Minneapolis-St. Paul ran from about 2 p.m. to 4 p.m. [54]. The same day, a power failure at the 511 Building, a downtown Minneapolis carrier hotel and data center, reached the building’s backup power [55]. MPR News reported it was unclear whether the same failure caused the flight pause [55]. The FAA has not said what failed, so the public cannot tell. If the link holds, it is 1991 again, with a federal safety service riding through a single building’s power plant.
The DOT Inspector General suggested in 2010 that the FAA require independent periodic reviews of its network architecture [29], and publishing the findings would let the public see whether the fixes held. The reviewer should be a network engineer who works for the FAA or for a firm with no stake in the contract, and who writes the physical requirements, reads the route maps, and witnesses the failover tests.
The second is to hold FAA circuits to at least the annual audit standard the FCC set for 911 carriers in 2013, which its June 2026 order still accepts from legacy providers even as it ends the annual certification [56], and to the diversity audits the FCC has urged on every provider since at least 2020 [57]. That means an annual physical diversity audit of every critical circuit feeding a center or major TRACON, tagging so carriers cannot regroom those circuits onto a shared route without notice, re-audit after any rearrangement, and certification by an accountable official. The audit has to cover the power behind each path, including where the generators sit and who sees the battery alarms, because Thomas Street and AT&T’s Nashville office both failed on power [25][58].
The third is to write the rest of the design into the contract. The August award to AT&T was undefinitized, with the long-term contract still to be negotiated [18][19]. Terms written into that award reach the FAA’s traffic only as it moves to FENS, so the same requirements belong in L3Harris’s FTI work until then. Carrier diversity, separate building entrances, separate equipment rooms, continuous monitoring of backup paths, and alarms that reach the FAA directly can all be requirements. So can out-of-band management that does not ride the network it manages, limits that keep one site’s routing or management failure at that site, and changes staged one half at a time, with remedies that go beyond service credits. New equipment can also be required to pass tests on a lab network that mirrors production, with unused features turned off, before it reaches the live network. Work that takes one half of a pair out of service should start only after the other half is verified, and that half should be protected until the work is done. Repair times belong on the redundant half as well as the primary, since the Telecommunications Service Priority program sets only the order of repairs [59]. A cap on how many facilities any single element can affect would turn the 129-instead-of-21 problem from 2009 into a contract term [29]. The cap only means something if the contractor has to prove it, by failing elements on a schedule and after major changes, showing the FAA what actually went down, and fixing any domain that turns out larger than the drawing.
For the centers and the largest TRACONs, two wireline paths are not enough. A third path that is not wireline at all, such as licensed microwave or satellite, cannot share a trench, a conduit, or a central office with the other two. It only has to carry the critical minimum, the controllers’ voice to their radio sites and the radar feeds, but it has to be independent in every other way, with its own building entrance, power, carrier, and management. On November 13, a third path that rode FTI’s routers would have shared their failure. In 2018, the FTI program proposed commercial microwave to give the long-range radar at Elwood, Illinois, “telecommunications diversity,” replacing the FAA’s own 2 GHz microwave link [60]. In July 2025, Bedford told lawmakers the FAA would not rely on Starlink “or any satellite service” as the sole technology for safety-critical air traffic services, and that FTI was testing a few dozen Starlink terminals [61]. A third path earns its place only if it fails for reasons the other two do not share. One satellite network can serve every center on those terms, because an outage of that network leaves the two wireline paths up.
The fourth is to finish what the 2015 report asked for, so that any center’s airspace and data can move to a neighboring center in minutes [16]. After the Chicago fire, the center’s automation could not hand its airspace to a neighbor automatically, and the workaround took days [16].
Quick Compare: The FAA Record
The table counts every FAA telecom or network failure since 1988 that this article found documented and that took a service down, even briefly. Rows without a published cause stay in the count, and the pattern claim in the TL;DR covers only the rows that have one. The last column is this article’s reading of each cited cause. Where a row’s source gives only the trigger, the reading is that one trigger was enough to take the service down.
| Date | Service | Reported cause | What was single |
|---|---|---|---|
| May 8, 1988 | Chicago Center lines to O’Hare and Midway | Hinsdale central office fire [21][22] | One central office |
| October 15, 1990 | O’Hare tower, delays up to two hours | Tree-planting contractor cut a line [62] | One cable |
| About November 1990 | Kansas City air traffic center, 4 hours 16 minutes | Beaver chewed a fiber cable [24] | One cable |
| January 4, 1991 | New York ATC | AT&T crew cut fiber in Newark [63] | One cable route |
| May 4, 1991 | Four en route centers, 5 hours 22 minutes | Farmer cut a fiber cable [24] | One cable |
| September 17, 1991 | New York ATC, 1,174 flights | Power transfer, alarms missed, batteries ran flat [25][26][27] | One building’s power plant |
| September 28, 2006 | Atlanta tower, 8 delays | Defective equipment [3] | One equipment failure |
| December 4, 2006 | San Juan Center, 20 hours, 60 delays | Underwater cable cut [3] | One cable |
| December 11, 2006 | Orlando tower, 63 delays | Improper configuration [3] | One configuration error |
| January 9, 2007 | Salt Lake Center, 92 delays | Maintenance procedures not followed [3] | One maintenance error |
| March 30, 2007 | Los Angeles tower, 25 delays | FTI troubleshooting [3] | Troubleshooting work |
| May 23, 2007 | Chicago, 77 delays | Misconfigured FTI equipment [3] | One configuration error |
| July 27, 2007 | FTI en route communications over North Carolina | Primary and backup lost; no cause stated [3] | Unknown |
| September 25, 2007 | Memphis Center, 566 delays | Inadequate physical diversity [3] | Alternate path routing |
| November 9, 2007 | Jacksonville Center, 85 delays | Inadequate physical diversity [3] | Primary and alternate together |
| December 4, 2007 | Merrimack, New Hampshire, 49 delays | Cables dislodged from a patch panel [3] | One patch panel |
| March 24, 2008 | Leesburg, Virginia, 60 delays | No cause identified [3] | Unknown |
| April 12, 2008 | San Diego, 5 delays | Telco failure [3] | One carrier |
| May 15, 2008 | Chamblee, Georgia, 41 delays | FTI circuit failure [3] | One circuit |
| August 2008 | Memphis Center communications with aircraft | Car hit a pole and cut fiber [64] | One cable |
| November 19, 2009 | Flight plans, nationwide, 129 facilities | Dormant router misconfiguration, alarms filtered [29] | One change, one alarm filter |
| September 26, 2014 | Chicago Center, 2+ weeks | Arson in telecom room [16] | One room for primary and backup |
| September 20, 2017 | FAA San Juan Center, Puerto Rico radars | Hurricane Maria destroyed a key generator; two FAA radars inoperable [65][66] | One generator |
| December 25, 2020 | Memphis Center frequencies | Nashville bombing cut central office power and generators [58][67] | One central office |
| April 28, 2025 | Newark approach via Philadelphia TRACON, about 90 seconds | Burnt copper wire; backup line did not take over [34][35] | Backup did not take over |
| May 9, 2025 | Newark approach via Philadelphia TRACON, about 90 seconds | Primary and redundant infrastructure both failed [13][32][34] | Untested commercial lines |
| May 12, 2025 | Denver Center sector frequencies | Both transmitters for a sector failed; cause unpublished [68] | Unknown |
| June 20, 2025 | Jacksonville Center radar, briefly | Fiber line cut; backup kicked in [69] | One fiber line, until the backup took over |
| September 19, 2025 | Dallas TRACON | Primary and secondary paths cut [42][43] | One local carrier |
| August 6, 2026 | Minneapolis Center airspace | Telecom issue, cause unpublished [54] | Unknown |
| September 21, 2026 | Philadelphia TRACON, 5 airports | Primary out for troubleshooting, Verizon backup cut [36][39] | One working path, one carrier |
| October 12, 2026 | Raleigh-Durham arrivals, hours of restrictions | Plumbing contractor cut fiber [70] | One cable cut |
| October 13, 2026 | Houston Intercontinental communications | Construction contractor damaged fiber [71] | One cable cut |
| November 13, 2026 | Up to 17 of 22 en route centers | New routers at two sites flooded the network, one installed during copper-to-fiber work (preliminary) [5][9][10] | One router feature, network-wide |
Cover photo: WhisperToMe / Wikimedia Commons, public domain
Sources
[1] ABC News, “Nationwide ground stop lifted after more than 4 hours as Trump administration blames old, overloaded tech,” November 13, 2026. https://abcnews.com/US/nationwide-ground-stop-ordered-airports-faa/story?id=138121848
[2] FAA, “Nationwide Ground Stop: Questions and Answers,” November 15, 2026 (the address of the FAA’s November 13 statement now redirects here). https://www.faa.gov/newsroom/nationwide-ground-stop-questions-and-answers
[3] DOT Office of Inspector General, FAA’s Progress and Challenges in Meeting FTI Transition Goals, Report AV-2008-089, September 30, 2008. https://govinfo.gov/content/pkg/GOVPUB-TD-PURL-gpo27442/pdf/GOVPUB-TD-PURL-gpo27442.pdf
[4] Yahoo News, “FAA ground stop latest updates,” live coverage, November 14 and 15, 2026 (headline updated during coverage). https://www.yahoo.com/news/us/live/faa-ground-stop-latest-updates-duffy-blames-contractor-l3harris-thousands-more-flights-canceled-saturday-no-sign-of-cyberattack-161329174.html
[5] CBS News, “Travelers stranded and thousands of flights canceled after FAA ground stop. Here’s what we know,” updated November 15, 2026. https://www.cbsnews.com/amp/news/faa-ground-stop-canceled-flights-travelers-what-we-know/
[6] U.S. Department of Transportation, “ICYMI: U.S. Transportation Secretary Sean P. Duffy Provides Update on Restoration of Airspace Following Nationwide Ground Stop,” November 14, 2026. https://www.transportation.gov/briefing-room/icymi-us-transportation-secretary-sean-p-duffy-provides-update-restoration-airspace
[7] Fox Business, account of Duffy’s November 14 briefing on L3Harris, November 14, 2026. https://www.foxbusiness.com/fox-news-air-space/who-l3harris-federal-contractor-sec-duffy-says-may-have-caused-faa-outage
[8] L3Harris, “L3Harris Reaches Over 50% in FAA Telecommunications Modernization,” May 11, 2026. https://www.l3harris.com/newsroom/editorial/2026/05/l3harris-reaches-over-50-faa-telecommunications-modernization
[9] Andrew Tangel and Drew FitzGerald, “The Single Router in Southern Arkansas That Ground Air Travel to a Halt,” The Wall Street Journal, November 15, 2026 (republished by To Vima). https://www.tovima.com/wsj/the-single-router-in-southern-arkansas-that-ground-air-travel-to-a-halt
[10] Quinn Scanlan, ABC News, “Transportation Secretary Duffy says ATC routers’ ability to broadcast data turned off, being investigated,” November 15, 2026. https://abcnews.com/Politics/transportation-secretary-duffy-atc-routers-ability-broadcast-data/story?id=138155545
[11] FOX 4 Dallas-Fort Worth, “FAA ground stop: Routers in Texas, Arkansas being tested after outage,” November 15, 2026. https://www.fox4news.com/news/faa-ground-stop-routers-texas-arkansas-being-tested-after-outage
[12] FCC Public Safety and Homeland Security Bureau, December 27, 2018 CenturyLink Network Outage Report, August 19, 2019. https://docs.fcc.gov/public/attachments/DOC-359134A1.pdf
[13] GAO, Air Traffic Control Systems: Ambitious New Modernization Effort Needs to Improve Cost and Schedule Planning, GAO-26-107992, September 14, 2026. https://files.gao.gov/reports/GAO-26-107992/index.html
[14] CNN, “US flight ground stop latest,” live coverage, November 15, 2026 (headline updated during coverage). https://www.cnn.com/2026/11/15/politics/live-news/trump-administration-ground-stop
[15] Washington Technology, “FAA selects Verizon for $2.4B telecommunications contract,” March 2023. https://www.washingtontechnology.com/companies/2023/03/faa-selects-verizon-24b-telecommunications-contract/384517/
[16] DOT Office of Inspector General, FAA’s Contingency Plans and Security Protocols Were Insufficient at Chicago Air Traffic Control Facilities, Report AV-2015-112, September 29, 2015. https://www.durbin.senate.gov/imo/media/doc/FAA%20contingency%20plans%20and%20security%20protocols%20at%20Chicago%20ATC%20facilities.pdf
[17] SAM.gov, FAA Enterprise Network Services (FENS) award notice 693KA8-23-D-00010. https://sam.gov/opp/7e58b8f050ef40f59761aa3b334528a5/view
[18] SAM.gov, FAA Enterprise Network Services (FENS) award notice 693KA8-26-D-00016 to AT&T, contract award date August 11, 2026, published August 12, 2026. https://sam.gov/opp/89275702a17c4bc4a1906fd596fe8828/view
[19] Washington Technology, “FAA brings in AT&T for network modernization program,” August 2026. https://www.washingtontechnology.com/contracts/2026/08/faa-brings-t-network-modernization-program/415412/
[20] MeriTalk, “FAA Awards AT&T $74M to Kick Off Network Overhaul,” August 14, 2026. https://meritalk.com/articles/faa-awards-att-74m-to-kick-off-network-overhaul/
[21] Office of the State Fire Marshal and Illinois Commerce Commission Staff, Hinsdale Central Office Fire, Final Report, Executive Summary, March 1989. https://archive.decromancer.ca/vtda.org/docs/telephony/Ameritech/The_Hinsdale_Challenge_1988_Executive_Summary.pdf
[22] UPI, “Bell puzzles over cause of crippling blaze,” May 9, 1988. https://www.upi.com/Archives/1988/05/09/Bell-puzzles-over-cause-of-crippling-blaze/6390579153600/ Archived copy: https://archive.ph/9A19S
[23] TELECOM Digest, May 1988 issues on the Illinois Bell Hinsdale fire (archive). https://bio.nic.funet.fi/pub/mirrors/lcs.mit.edu/telecom-archives/TELECOM_Digest_Online/1309.html
[24] RISKS Digest, Volume 12, Issue 62, November 12, 1991 (quoting the Associated Press, November 10, 1991). https://catless.ncl.ac.uk/Risks/12/62
[25] UPI, “FCC orders AT&T to study communications system in wake of outage,” November 8, 1991. https://www.upi.com/Archives/1991/11/08/FCC-orders-ATT-to-study-communications-system-in-wake-of-outage/7189689576400/ Archived copy: https://archive.ph/mSFHD
[26] UPI, “AT&T discloses cause of power failure,” September 20, 1991. https://www.upi.com/Archives/1991/09/20/ATT-discloses-cause-of-power-failure/8379685339200/ Archived copy: https://archive.ph/20261116200152/https://www.upi.com/Archives/1991/09/20/ATT-discloses-cause-of-power-failure/8379685339200/
[27] GAO, Telecommunications: Interruptions of Telephone Service, RCED-93-79FS, March 5, 1993. https://www.gao.gov/assets/rced-93-79fs.pdf
[28] eWeek, “FAA Flight-Plan System Crashes Again, Delays Hundreds of U.S. Flights,” November 19, 2009. https://www.eweek.com/storage/faa-flight-plan-system-crashes-again-delays-hundreds-of-u.s.-flights/
[29] DOT Office of Inspector General, letter to Chairmen Oberstar and Costello on the November 19, 2009, FAA Telecommunications Infrastructure outage, June 17, 2010. https://www.oig.dot.gov/sites/default/files/WEB%20FILE2_FTI%20%20Nov%2019%20outage-6-18-10_Final%20Signature%28a%29%20%282%29.pdf
[30] eWeek, “The Story Behind the FAA Flight-Plan System Crash,” November 20, 2009. https://www.eweek.com/networking/the-story-behind-the-faa-flight-plan-system-crash
[31] CBS News, “Report slams FAA response to fire at Chicago air traffic facility,” September 30, 2015. https://www.cbsnews.com/news/report-slams-faa-response-to-fire-at-chicago-air-traffic-facility
[32] Flying, “Newark Airport Suffers Another 90-Second Radar Outage,” May 2025. https://www.flyingmag.com/newark-airport-suffers-another-90-second-radar-outage/
[33] Pete Muntean, Rene Marsh, TuAnh Dam, and Amanda Musa, CNN, via KVIA, “Newark Airport systems outage was ‘most dangerous situation,’ air traffic controller says,” May 6, 2025. https://kvia.com/cnn-national/2025/05/06/newark-airport-systems-outage-was-most-dangerous-situation-air-traffic-controller-says/
[34] DOT Office of Inspector General, Audit Announcement, FAA’s Relocation of Newark-Area Terminal Radar Approach Control (TRACON) Responsibilities, Project No. 25A3005A000, July 28, 2025. https://www.oig.dot.gov/sites/default/files/library-items/Audit%20Announcement%20-%20FAA%20N90%20Review%207.28.25.pdf
[35] Andrea Margolis and Grady Trimble, Fox Business, “Newark air traffic controllers lost radar, radio communications with planes for over a minute, sparking chaos,” May 5, 2025. https://www.foxbusiness.com/fox-news-travel/newark-air-traffic-controllers-lost-radar-radio-communications-planes-minute-sparking-chaos
[36] Reuters via WHBL, “US FAA says error messages in telecommunications circuit prompted shift to backup on Sunday,” September 23, 2026. https://whbl.com/2026/09/23/us-faa-says-error-messages-in-telecommunications-circuit-prompted-shift-to-backup-on-sunday/
[37] Airways, FAA Northeast ground stops and NJ Transit statement, September 2026. https://airwaysmag.com/new-post/faa-northeast-ground-stops-severed-fiber-philadelphia-tracon
[38] AirlineGeeks, “ATC Outage Cancels, Delays Hundreds of Flights on East Coast,” September 21, 2026. https://airlinegeeks.com/2026/09/21/atc-outage-cancels-delays-hundreds-of-flights-on-east-coast/
[39] Newsweek, Philadelphia TRACON outage and Verizon statement, September 21, 2026. https://www.newsweek.com/hundreds-of-flights-impacted-at-major-us-airports-over-equipment-failure-12469404
[40] Associated Press via WSMV, “Flights disrupted across US Northeast due to technical problems at key air traffic center,” September 21, 2026. https://www.wsmv.com/2026/09/21/flights-disrupted-across-us-northeast-due-technical-problems-key-air-traffic-center/?outputType=amp
[41] L3Harris, “FAA Telecommunications Infrastructure (FTI),” service page. https://www.l3harris.com/all-capabilities/fti-network-managed-services
[42] FOX 4 Dallas, “Aviation expert says outdated infrastructure could cause more airport ground stops,” September 22, 2025. https://www.fox4news.com/news/dfw-love-field-ground-stop-experts
[43] CBS Texas, “Outdated infrastructure is to blame for hours long ground stop at Dallas airports, FAA says,” September 20, 2025. https://www.cbsnews.com/amp/texas/news/outdated-infrastructure-faa-dallas-airport-ground-stops
[44] Reuters via ARY News, “Dallas airports return to normal after over 2,000 flights disruption,” September 22, 2025. https://arynews.tv/dallas-airports-return-to-normal-after-over-2000-flights-disruption
[45] FOX 9, “FAA head says billions more needed to modernize air traffic control,” September 16, 2026. https://www.fox9.com/news/faa-head-billions-modernize-air-traffic-control
[46] The Air Current, “U.S. ends halt on flight departures after nationwide air traffic communications outage,” November 13, 2026. https://theaircurrent.com/feed/dispatches/u-s-halts-flight-departures-nationwide-on-air-traffic-communications-outage/
[47] Kaia Hubbard, CBS News, “Ground stop proves ‘we have to get off old network,’ Transportation Secretary Sean Duffy says,” November 15, 2026. https://www.cbsnews.com/news/ground-stop-faa-telecom-network-sean-duffy-face-the-nation/
[48] DISA, Enterprise Voice, Video, and Messaging Policy Security Requirements Guide, Version 1, Release 4, finding V-259917, December 23, 2025 (STIG Viewer). https://www.stigviewer.com/stigs/enterprise_voice_video_and_messaging_policy_security_requirements_guide/2025-05-29/finding/V-259917
[49] FAA, Order JO 6000.36B, National Airspace System Service Survivability (cancels Order 6000.36A, Communications Diversity, 1995). https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentID/1037633
[50] FAA, Order JO 6500.28, Radio Communications Requirements for Air Traffic Control Facilities. https://www.faa.gov/documentLibrary/media/Order/FAA_Order_JO_6500.28.pdf
[51] 47 CFR § 4.9, Outage reporting requirements, threshold criteria (Legal Information Institute). https://www.law.cornell.edu/cfr/text/47/4.9
[52] 47 CFR § 4.5, Definitions of outage, special offices and facilities, 911 special facilities, and 988 special facilities. https://www.law.cornell.edu/cfr/text/47/4.5
[53] 47 CFR § 4.2, Availability of reports filed under this part (Legal Information Institute). https://www.law.cornell.edu/cfr/text/47/4.2
[54] MPR News, “Flights resume at Minneapolis-St. Paul International Airport after ‘telecommunication issues’,” August 6, 2026. https://www.mprnews.org/story/2026/08/06/flights-halted-at-minneapolisst-paul-international-airport
[55] MPR News, “Outage at Minneapolis data center behind last week’s telecommunications disruptions,” August 10, 2026. https://www.mprnews.org/story/2026/08/10/how-an-outage-at-unassuming-building-in-minneapolis-sent-waves-through-the-midwest
[56] FCC, Facilitating Implementation of Next Generation 911 Services; Improving 911 Reliability, Second Report and Order, FCC 26-39, adopted June 25, 2026. https://docs.fcc.gov/public/attachments/FCC-26-39A1.pdf
[57] FCC Public Safety and Homeland Security Bureau, “Public Safety and Homeland Security Bureau Encourages Communications Service Providers to Implement Important Network Reliability Practices,” Public Notice DA 20-1406, November 25, 2020. https://docs.fcc.gov/public/attachments/DA-20-1406A1.pdf
[58] Data Center Frontier, “Nashville Explosion: AT&T Repairs Damage to its Building and Network,” December 2020. https://www.datacenterfrontier.com/featured/article/11428484/nashville-explosion-at038t-repairs-damage-to-its-building-and-network
[59] CISA, “Telecommunications Service Priority: Priority for Emergency Communications.” https://www.cisa.gov/sites/default/files/publications/TSP%20Priority%20for%20Emergency%20Communications.pdf
[60] NTIA, DOT\FAA 1755-1780 (Rev. 1), Freq-Geo Transition Timeline, FTI Last Mile Microwave for the Elwood ARSR, approved October 3, 2018. https://www.ntia.gov/sites/default/files/publications/releasable_dot_faa_1755-1780_rev-1_sufficient_10_26_2018_0.pdf
[61] David Shepardson, Reuters, “US FAA not considering replacing L3Harris, Verizon contracts with Musk’s Starlink,” July 2025 (via Yahoo News). https://www.yahoo.com/news/us-faa-not-considering-replacing-161335458.html
[62] RISKS Digest, Volume 10, Issue 62, “Telephone cable cut eliminates O’Hare tower communications,” November 19, 1990 (reprinting The New York Times, October 16, 1990). https://catless.ncl.ac.uk/Risks/10/62
[63] RISKS Digest, Volume 10, Issue 75, “NY area fiber-optic telephone cable severed,” January 5, 1991. https://catless.ncl.ac.uk/Risks/10/75
[64] Associated Press via Fox News, “FAA Outage Exposes Odd Computing Practices at Agency,” August 2008 (the page shows January 13, 2015). https://www.foxnews.com/story/faa-outage-exposes-odd-computing-practices-at-agency.print
[65] Air University, “Air National Guard restores air traffic control in Puerto Rico,” October 2017. https://airuniversity.af.edu/News/Display/Article/1331249/air-national-guard-restores-air-traffic-control-in-puerto-rico
[66] NOAA, “Federal collaboration yields radar coverage for Puerto Rico, USVI in wake of Hurricane Maria,” October 2017. https://www.noaa.gov/media-release/federal-collaboration-yields-radar-coverage-for-puerto-rico-usvi-in-wake-of-hurricane
[67] CNN via ABC 17, “Nashville explosion causes AT&T outages and disrupts flight,” December 25, 2020. https://abc17news.com/news/national-world/2020/12/25/nashville-explosion-causes-att-outages-and-disrupts-flight/
[68] Colorado Public Radio, “FAA investigating outage that interfered with communication between pilots and Denver air traffic control,” May 15, 2025. https://www.cpr.org/2025/05/15/faa-investigation-dia-air-traffic-control-outage/
[69] Associated Press via WUSF, “Cut fiber line near Jacksonville briefly disrupts air traffic controllers around Southeast,” June 20, 2025. https://wusf.org/text/local-state/2025-06-20/cut-fiber-line-near-jacksonville-briefly-disrupts-air-traffic-controllers-around-southeast
[70] AVweb, “Severed Fiber Line Disrupts Raleigh-Durham Flights,” October 13, 2026. https://avweb.com/aviation-news/severed-fiber-line-disrupts-raleigh-flight/
[71] AVweb, report on fiber damage and the ground stop for Houston Intercontinental, October 14, 2026. https://www.avweb.com/aviation-news/severed-fiber-line-disrupts-houston-flight/


