
As reported, voice communications and radar surveillance information became unstable in something like half of the 20 Air Route Traffic Control Centers (ARTCC) that are used for managing aircraft enroute in the lower 48 states.
I am sure there was a lot of angst in the 20 minutes after the problems surfaced and spread across the FAA service area. How extensive would it get and how bad would it get would have been a great concern and this is where action was taken out of an abundance of caution.
- those operating in Alaska and Hawaii
- some trans-Atlantic flights from the east coast and trans-Pacific flights from the west coast.
PART 259—ENHANCED PROTECTIONS FOR AIRLINE PASSENGERS
Source:74 FR 69002, Dec. 30, 2009, unless otherwise noted.
§ 259.1 Purpose.
The purpose of this part is to mitigate hardships for airline passengers during lengthy tarmac delays and otherwise to bolster air carriers' accountability to consumers.
https://www.ecfr.gov/current/title-14/chapter-II/subchapter-A/part-259
(so regrettable to see the term “tarmac” used in a regulation)
Airline crews (both flight crew and cabin crew) are subject to duty limits and must be allowed a period of rest. As a result of the disruption, crew members were timing out Friday night, despite lifting the ground stop. Airlines had to scramble to recover from this mess, and that certainly will take a couple of days to resolve.
History of Ground Stops
Briefing the Public
TDM?
Each phone call was wrapped around an outbound and and inbound voice signal represented (analog to digital) by 8 bits running at 8 kHz sampling rate (4 kHz bandwidth) leading to a composite data rate of 64 kbps for each outbound and inbound voice channel. T1 runs at a data rate of 1.544 Mbps in each direction (inbound and outbound). There were higher speed T carriers, but for now just think of the T1.
The FAA had naturally embraced TDM when configuring remote radio services. There was a great demand for economy (migrating from dedicated two-wire interfaces per voice channel to TDM allowing 24 voice channels on two twisted pair wires. Probably starting in the late 1960s or early 1970s. There would have been lots of options for commercial interconnections (private networks). It certainly would have worked well and have been leading edge in the moment. However, certainly by 1990 it would become apparent that the marketplace was shifting to fiber optics and Internet Protocol (IP).
FCC Sunsets TDM (T1) technology
The TDM (T1) line technology was quickly outpaced by fiber optic technology starting in the 1980s. When the Bell system was broken up in 1984, the existing local subscriber loops running on copper wires were preserved to allow for competition delivering services (while charging for their use).
By 2000, the emergence of cable modems and fiber-optic modems to the home began to overcome copper to the home (dial-up, ISDN, DSL), especially as data rates boomed above 1 Mbps.
Today a 100 Mbps to the home and 20 Mbps from the home data rates are defined as a broadband service.
Telephone companies began to reduce support for copper interfaces in favor of these new technologies.
The FCC took action in 2019 to lessen the need to continue to support copper interfaces.
3. Given the sweeping changes in the communications marketplace since the passage of the 1996 Act, including the increasing migration of consumers of all sorts and sizes away from TDM technology, copper loops, and local telephone service toward newer, any-distance voice services over next-generation wireline and wireless networks and the wide range of competitors offering facilities-based voice service alongside over-the-top Voice over Internet Protocol (VoIP) services, we find that the public interest is no longer served by maintaining these legacy regulatory obligations and their associated costs.
Rather than a foothold for new entrants into the marketplace, they have become a vice, trapping incumbent LECs into preserving outdated technologies and services at the cost of a slower transition tonext-generation networks and services that benefit American consumers and businesses.
https://docs.fcc.gov/public/attachments/FCC-19-72A1.pdf
The 2019 order included a notable dissent.
STATEMENT OF COMMISSIONER JESSICA ROSENWORCEL, DISSENTING
Re: Petition of USTelecom for Forbearance Pursuant to 47 U.S.C. §160(c) to Accelerate Investment in Broadband and Next-Generation Networks, WC Docket 18-141. There was a time, not that long ago, when traditional voice telephony offered over copper loops was the core of our communications system. No longer. The technologies used to provide voice service have expanded and the digital age has brought a whole new range of communications services to homes and businesses across the country.
This change is exciting. But in our haste to make way for the new, I worry we give short shrift to those consumers who depend upon the old. There are still consumers who rely on traditional voice services provided via unbundled copper loops and avoided-cost resale. By ushering these facilities out of the market and erasing their provision under the law, this decision risks cutting off calls and could leave consumers without options at the end of the line.
To this end, I am disappointed that this decision did not do more to guarantee a smooth transition for newly-ordered services, especially when it comes to government users that depend on these facilities. I respectfully dissent.
The FCC took further action in 2026 to sunset support for copper interfaces.
Today, we take the next step to accelerate network deployment and modernization by proposing comprehensive reform of the regulatory framework for voice telecommunications rates.
The voice services market has evolved dramatically over the past several decades—shifting from switched access to Internet Protocol (IP) technologies.
As a result, consumers have gained access to a wide range of competitive alternatives to traditional analog telephone services, including fixed Voice over Internet Protocol (VoIP), mobile, and satellite options. Completing the transition to IP will promote technological modernization and public safety and consumer protection benefits;
1 enhance long-term efficiency, competition, and service quality for consumers; and lead to decreased maintenance expenses for service providers.
2 Although IP-based technologies are widely available, some providers continue to use legacy Time-Division Multiplexing (TDM) equipment, potentially due in part to regulatory incentives embedded in the intercarrier compensation (ICC) regime, as well as the costs associated with transitioning to IP technologies.
We recognize that shifting from the current regulatory framework for intercarrier compensation, interexchange services (i.e., long-distance services), and end user charges—which is rooted in decades-old assumptions and outdated technology—to a full bill-and-keep framework is complex and will take time to ensure that the changes do not create regulatory uncertainty or hinder network modernization.
https://docs.fcc.gov/public/attachments/FCC-26-11A1.pdf
Upgrading Air Traffic Control
When considering upgrades to Air Traffic Control, there are different objectives
1) Modernization – maintaining the existing functions to improve reliability, lower cost, and to manage obsolescence.
2) Enhancement – creating new functionality to improve operational efficiency and safety. To take advantage of new technology.
Modernization
Modernization lives in the shadows. It’s primary purpose is to not break anything, to maintain the status quo, while transitioning to new technology and services.
The FAA had embraced TDM (T1) technology widely. The FAA recognized that an alternative to this technology, primarily shifting to Internet Protocol (IP) networking, was of growing urgency.
In 2015, the FAA issued a white paper on the subject.
The FAA has separate network infrastructures for administrative “agency” functions such as e-mail, time reporting, etc. and operational systems that support the air traffic management functions of the National Airspace System (NAS). Administrative data exchanges are supported by the “Mission Support” network that is 100% IP-based.
The NAS operational network supports a combination of TDM-based and IP-based service interfaces, but most are TDM-based due to the interface requirements of the systems that connect to the operational network. This white paper focuses on the FAA’s plans for migrating TDM-based services on the NAS Operational Network.
Major U.S. telecommunications carriers have stated their intention to discontinue TDM-based services as early as 2020.
The FAA is highly dependent on these services.
As shown below in Figure 1, more than 90% of the 23,000+ services obtained under the FTI contract are TDM-based and support critical NAS services such as surveillance radar, air/ground voice, and interphone (ground/ground voice).

https://www.faa.gov/sites/faa.gov/files/air_traffic/technology/cinp/fens/tdm-to-ip_migration_2015-10-27.pdf
Clearly, the transition from TDM (T1) to IP is a modernization effort. The new IP backbone will serve more and more applications, giving growth not possible with the legacy T1 lines. The initial objective was simply to migrate away from T1 to IP without breaking anything. In 2019, the FAA issued an order.
a. This order advises the Federal Aviation Administration (FAA) acquisition workforce that telecommunication companies are discontinuing Time Division Multiplexing (TDM) telecommunications services.
This order provides guidance on the FAA’s plans to standardize the use of Ethernet interfaces and the Internet Protocol (IP) for ground-to-ground, air-to-ground, intra- and inter-facility communications, for both voice and data.
b. This order directs Program Offices, and others responsible for FAA systems and applications, to undergo a TDM-to-IP assessment.
This order applies to all system owners and Program Offices for all systems and services that use telecommunication services.
This assessment will be conducted by Communications, Information & Network Programs (AJM-31), with support from the affected domain system owner and associated Domain Roadmap Lead, who can be identified by contacting NAS Enterprise Planning & Analysis Division (ANG-B2). NAS domain systems that are currently under development must coordinate their architecture and technology plans with ANG-B2.
Operational NAS, Mission Support, and Research and Development domain systems and applications affected by this policy, that are not planning near-term improvements, will also work with AJM-31 and ANG-B2 to assess the impacts of converting their systems. The outcome of the assessments must show the specific impacts of conversion and note them as distinct line items when combined with other funding requests to the Joint Resources Council (JRC) or Capital Investment Team (CIT). As of the effective date of this order, all provisioning of new services should be based on IP services.
https://www.faa.gov/documentLibrary/media/Order/NG_6100.6.pdf
L3 Harris was awarded an FAA contract to modernize their TDM (T1) technology to IP.
L3Harris is replacing decades-old copper wire connections with modern high-speed networks across all FAA facilities – from major air route traffic control centers to remote radar sites and weather stations.
The new and more reliable infrastructure will accelerate the use of modern equipment throughout the National Airspace System (NAS) while enhancing safety, reducing delays and paving the way for emerging technologies like flying taxis and drones.
What We're Delivering:
- High-speed fiber optic connections replacing copper infrastructure
- Satellite communications for remote and difficult-to-reach locations
- Wireless technology where fiber deployment isn't practical
- Enhanced cybersecurity monitoring at every connection point
- Refreshed equipment at data hubs nationwide

MAINTAINING OPERATIONS DURING TRANSFORMATION
Our team's deep knowledge of the U.S. national airspace allows us to upgrade systems without disrupting air traffic operations.
We maintain 99.99971% network reliability by working during maintenance windows, deploying parallel systems and coordinating closely with FAA technical operations staff to ensure controllers have the connectivity they need.
https://www.l3harris.com/all-capabilities/faa-telecommunications-infrastructure-fti
Just to add a little context: I’ve seen local carriers—including AT&T, Frontier, and Verizon—struggle to maintain the legacy TDM networks needed to keep the FTI network operating, so this incident doesn’t surprise me.In our case, we ended up using a single 64-kbps channel on a DS3/T3, which supports 672 channels, leaving the other 671 unused. That DS3 was carried over a SONET ring, with OC-3 as the smallest configuration. So our one active channel shared the ring with roughly 2,000 other channel-equivalents that were also unused.Adding to the challenge, most of the people who know this legacy equipment have retired, and spare parts are largely salvaged. Telco technicians arrived with a box of old cards for our fiber multiplexer and tried them one at a time until they restored the circuit.I urged my network counterparts to install simple IP-based synchronization devices of the kind the Air Force had successfully deployed on its networks, but that approach wasn’t adopted. It’s frustrating to see a straightforward solution go unused.And when you hear terms like “instability” or “intermittent,” it often points to a timing clock slipping somewhere in the network—a common problem in synchronized systems.
Enhancement
Enhancement is difficult. The new functions have to proven reliable and compelling. Upgrades can take decades, with changes to
- air traffic control workstations
- onboard systems
- procedures
Equipment changes have a real cost and have to be aligned to seamless transitions from what was then and what is now. Airlines, and the aviation industry, fight back whenever a mandate drives new equipage.
A business case has to be made to justify the investment. In many cases the investment up front will not result in meaningful benefits until a critical mass of equipage and procedures are activated - which themselves can take years to realize. This leads to skepticism.
Procedural changes creates a sticking point that can extend the time from conception, to test, to building the regulatory basis, to deploying new equipment, and to training those involved.As a result, enhancement tends to follow incremental changes that builds on emerging capabilities.
I had the opportunity to work on data link enhancements during its most exciting time between 1990 and 1995.
Data link emerged (Aircraft Condition, Addressing and Reporting System, ACARS) in 1978. It began to be used for pre-clearance delivery in the early 1990s, and was first approved for air traffic control in 1995 (FANS-1 Controller Pilot Data Link Communication, CPDLC). The same technology also included a surveillance function (Automatic Dependent Surveillance, ADS-C).
Initially CPDLC was deployed using Inmarsat classic satcom (operating at throughputs between 0.088 and 5 kbps) and using VHF MSK operating at 2.4 kbps (Plain old ACARS, POA) labeled as VHF Data Link mode 0/A. CPDLC was directed initially to oceanic and remote airspace.
ACARS networks have evolved over the last 20 years with the advent of VDL Mode 2 (31.5 kbps) and Inmarsat (Viasat) Swift Broadband-Safety operating at 300-400 kbps and Iridium Certus, operating at 100-700 kbps.
A significant transition for ACARS is still in-work, utilizing IP networks natively (ACARS over IP and ACARS/IPS).
While ACARS networks became faster and faster, the underlying CPDLC and ADS-C payloads have evolved independently to a greater and greater set of functions. CPDLC applications have simply expended their portfolio from what was approved in 1995.
The FAA had successfully deployed data link to the oceanic airspace following the 1995 first certification (it still took years to implement).
After some false starts, the FAA decided to use the same ACARS/CPDLC implementation in domestic airspace through the Nextgen project, starting in about 2015 with a limited set of CPDLC functions and progressively expanding those CPDLC functions to the present day and into the future.
It is an agonizingly slow process, paced by incremental upgrades to Air Traffic Control facilities and procedures.
I am currently promoting the concept of using Ku/Ka-band satellite-based inflight connectivity, IFC, for enhancing data link to the airplane for non-passenger application, and that includes both operational and air traffic control applications (IFC-Safety). The HYCON initiative is promoting the idea that we can use IFC as a supplement to L band or VHF. I am pushing to consider using IFC-safety without restrictions, not just as a supplement. I fully expect this initiative to take more than ten years to gain a foothold, yet the technology is already onboard.
While domestic airspace has VHF voice directly between pilot and controller, oceanic airspace utilizes HF voice, whereby the controller sends a teletype message to a remote radio operator who transcribes the message to the pilot and sends back via teletype any message in response. This technology was evident in the 1920s and largely has not changed in over 100 years.
I was part of the process that brought satellite voice to the flight deck, allowing for using the Plain Old Telephone System (POTS) to dial up any ground telephone number. We built out a private numbering plan (short codes) that would allow a pilot to contact any oceanic air navigation service provider (ANSP) facility (but not to a specific controller). We promoted flight plan changes that informed the controller what number to dial to reach an aircraft. We developed a priority system to distinguish calls between public, operational low/high, and distress/urgency. This was all by 1993.
The Inmarsat native dialing plan uses different country codes for each satellite region, leading to some uncertainty as to which to use to contact an airplane. Famously, Satcom Direct entered the marketplace with a single number approach, automatically dialing the correct country (ocean region) code.
Fast forward to today and the best we can do in the FAA world is to allow the HF radio operator to dial up an airplane while communicating with the oceanic controller using the same teletype messaging interface used previously - standing between pilot and controller. The Radio Operator can patch the call through to the controller.
There are other air navigation service providers around the world (NAV Canada in particular) promoting direct pilot controller satellite voice communication. Keep in mind that voice is used for intervention (impending collision) and is a significant backstop to safe operation. Long range voice therefore becomes a sticking point in reducing separation.
Space-based VHF has emerged as another long-range voice technology, with the advantage of using the existing VHF radios already onboard. This has the potential to extend a "domestic" environment to the oceanic regions. These networks are just be developed and their capabilities are still being explored.
Automatic Dependent Surveillance – Broadcast (ADS-B) emerged following the work in Alaska (Capstone) between 1999 and about 2006. This was an enhancement from the Mode-C transponder.
The FAA recognized that ADS-B opened up a lot of capability that was difficult and expensive to create using radar. As a result, the FAA mandated that all aircraft be equipped with ADS-B, which resulted in a ten year campaign to meet the Jan 1, 2020 compliance date, to which too many aircraft operators waited to the very last minute to upgrade.
Space-based ADS-B, notably as provided by Iridium/Aireon, is in service to many ANSPs, but has not been adopted by the FAA.
Navigation enhancements started with the advent of GPS and then GNSS. This has opened up the opportunity for reduced separation and flexible terminal area procedures. Unfortunately, malicious actors are now routinely interfering with GNSS (jamming and spoofing), undermining its utility.
In all these cases, a performance-based approach has been embraced, with
- Required Navigation Performance, RNP
- Required Communication Performance, RCP
- Required Surveillance Performance, RSP
Enhancement is where the headlines lie, where the savings are realized, and where safety is enhanced.
Enhancements did not drive the ground stop of 2026.
Enhancements have a long history of false starts, higher costs than expected, unrealized benefits, and timelines that keep getting extended.
The FAA is just one ANSP. Enhancements generally seek global adoption, bringing in considerable coordination with other ANSPs, ICAO and EUROCAE.
ITU and the FCC also get into the mix, as radio regulations must consider all users of spectrum, not just aviation.
Enhancement is where the funding challenges lie - aligning all interested parties with realistic objectives yet with a track record of coming up short and spending more than anyone could imagine.
FAA Nextgen has worked hard to allay these concerns, but the cautious approach leads to extended timelines.
Additional Reading
The $30 billion air traffic control modernization plan that isn’t (Reason Foundation)
Ambitious New Modernization Effort Needs to Improve Cost and Schedule Planning (GAO report)
Performance Review Report: An Assessment of Air Traffic Management in Europe (Eurocontrol 2025)
Conclusion
That network reliability number L3 Harris is quoting is going to take a hit based on the ground stop on Friday, 13 Nov 2026.
L3 Harris certainly was not expecting any sort of major upset due to the work they undertook that led to the widespread FTI instability. What happened that caused this has not been revealed, but it is pretty apparent that L3 Harris will take action to not let that happen again. Aviation learns from its mistakes.
The good news is that no aircraft was reported breaking separation standards. No one was injured. No equipment was damaged (outside of whatever happened with L3 Harris actions).
Thankfully aircraft have equipment for detecting and avoiding aircraft collisions regardless of Air Traffic Control, and growing situational awareness onboard of proximate aircraft. Data link was reliable during the instability. Safety is a layered approach.
The simultaneous loss of TDM voice communication and surveillance will hopefully be resolved with the movement to IP networking.
It seems apparent that the FAA has the funding to complete this particular modernization aspect (TDM to IP) and thus the outcry for additional funding must be more directed to other modernization projects and most importantly to enhancements that really had nothing to do with this ground stop.
There is little doubt that the FAA has a continuing need to address modernization projects and to ensure that they will support emerging enhancements. Funding modernization projects is more straightforward if not intermixed with companion enhancements.
Largely, the Nextgen enhancements and the TDM to IP modernization efforts have been done without issue, except for the agonizing time-frame to completion. The ground stop of 2026 stands as a black-eye in what otherwise would be considered quite successful.
Peter Lemme
peter @ satcom.guru
Copyright 2026 satcom.guru All Rights Reserved
Peter Lemme has been a leader in avionics engineering for 45 years. He is the thought leader to the Seamless Air Alliance. He offers independent consulting services largely focused on avionics and L, Ku, and Ka band satellite communications. Peter chaired the SAE-ITC AEEC Ku/Ka-band satcom subcommittee for more than ten years, developing ARINC 791 parts 1, 2, and 3; ARINC 792, Project Paper 793, Project Paper 790, and continues as a member. He also contributes to the Network Infrastructure and Cybersecurity (NISC) subcommittee and the Electronic Flight Bag (EFB) subcommittee. Peter was awarded the Volare Pioneer Award by AEEC/SAE-ITC for Data Link and Satellite Communications in 2025. Peter was chairman of RTCA SC165 working group 5, satellite voice.
Peter was Boeing avionics supervisor for 767 and 747-400 data link recording, data link reporting, and satellite communications. He was an FAA designated engineering representative (DER) for ACARS, satellite communications, DFDAU, DFDR, ACMS and printers. Peter was lead engineer for Thrust Management System (757, 767, 747-400), supervisor for satellite communications for 777, and was manager of terminal-area projects (GLS, MLS, enhanced vision) across all Boeing commercial airplanes.
An instrument-rated private pilot, single engine land and sea, Peter has enjoyed perspectives from both operating and designing airplanes. Hundreds of hours of flight test analysis and thousands of hours in simulators have given him an appreciation for the many aspects that drive aviation; whether tandem complexity, policy, human, or technical; and the difficulties and challenges to achieving success.
With the recent suggestions and acknowledgment that it's a single router in Arkansas that caused all this , do you find that compelling?
ReplyDeleteThe question is why did the "instability" spread. I have no direct knowledge, so waiting for more information to come out.
DeleteExcellent piece as always Peter. In my experience, it’s also worth signposting the funding and oversight issues that have dogged the FAA for decades. Especially when government shutdowns occur. While any government owned monopoly service provider suffers from well known negative characteristics Globally (ask AI) the particular funding mechanisms at the FAA exacerbate rather than solve the challenges that the FAA faces. Bob Poole of Reason Foundation published his latest assessment (of many) in October. Worth a read: https://reason.org/aviation-policy-news/the-30-billion-air-traffic-control-modernization-plan-that-isnt/
ReplyDeleteANSPs around the world have many challenges, the Single European Sky is not immune either, but it does have an effective Performance Review function from which the US could perhaps learn.
Certainly ANSP subject to this annual and public ‘audit’ pay attention to both the findings, recommendations and just how the peers are doing on the same metrics.
Here’s the latest annual report. imagine Having that much data for the US NAS would help to inform and guide users and regulators.
GL
https://www.eurocontrol.int/sites/default/files/2026-03/eurocontrol-performance-review-report-2025.pdf
GL