Why do air traffic control communication systems fail?

Key takeaways:

• Most air traffic control communication outages start in the circuits between equipment, not in the radios or controller positions themselves.
• Aging copper, single-carrier paths, single equipment chains and manual patching are the most common single points of failure in legacy ATC infrastructure.
• Backups often fail with the primary because they share a conduit, central office, power feed or network.
• Modernization programs reduce long-term risk, but multi-year cutovers create new windows where a single path can fail.
• Diverse circuits combined with fail-soft, physical-layer switching remove the single point of failure without replacing the equipment on either end.

Controllers can only separate aircraft they can talk to and see. That makes the communication circuits behind every frequency, landline and surveillance feed some of the most critical infrastructure in aviation. Yet when air traffic control communication systems fail, the root cause is rarely the radio on the tower or the console in front of the controller. It is usually something less visible: a copper pair, a leased circuit, a modem or a patch panel.

This guide explains why ATC communication systems fail, where single points of failure hide in legacy infrastructure, and what engineers can do about them. For the solution side, see our communication circuit redundancy for air traffic control overview.

What makes ATC communications different from an enterprise network?

An enterprise network can tolerate a few minutes of downtime. ATC communications cannot. A few characteristics set them apart:

• Continuous, safety-of-life operation. Radio frequencies, interphone lines and surveillance data must be available around the clock.
• Geographically distributed. Remote radio sites, radar sites and facilities are linked by long telecom circuits, often provided by third-party carriers.
• Long equipment lifecycles. Voice switches, radio control equipment and interface converters can stay in service for decades, so analog, serial, T1/E1 and V.35 interfaces remain common.
• Mixed generations. IP and fiber links increasingly run alongside legacy circuits that still carry live traffic.

What are the most common causes of ATC communication outages?

Physical circuit failures. Cable cuts from construction, water ingress, corrosion and degraded copper pairs. A single damaged cable can take down every circuit routed through it.

Carrier and telco issues. Central-office equipment faults, carrier maintenance windows, provisioning errors and the retirement of legacy copper services. The ATC operator often has limited visibility into what happens inside the carrier network.

Equipment failures in the chain. Modems, channel banks, codecs, interface converters and their power supplies. When there is one device per circuit, there is nothing to fail over to.

Power events. Loss of facility power, a failed rectifier or UPS, or a single power supply in a critical device.

Configuration and cutover errors. Changes made during upgrades, migrations or circuit moves are a frequent source of unplanned outages.

Why does aging copper infrastructure matter so much?

Much of the telecommunications infrastructure behind ATC was built on copper. As copper ages, failures become more frequent and harder to diagnose, and carriers are steadily retiring the legacy services that run over it. In the United States, the FAA’s Brand New Air Traffic Control System program has made replacing legacy copper with fiber, wireless and satellite connections a top priority, alongside new radios and digital voice switches.

The risk became highly visible in 2025, when controllers at the Philadelphia TRACON handling Newark traffic briefly lost radar and radio contact with aircraft more than once, outages that drew national attention to the state of telecommunications behind the airspace system.

Why do backup systems sometimes fail at the same time as the primary?

Many “redundant” designs are only redundant on paper. The backup circuit shares something with the primary, so a single event takes out both. Common examples of shared fate include:

• Primary and backup circuits ordered from different carriers but routed through the same conduit, building entrance or central office.
• Two circuits terminating on the same modem, channel bank or voice switch card.
• Failover logic that runs on the same IP network or power feed as the primary path.
• A backup that requires a technician to re-patch cables, so it is only as fast as the drive to site.

We compare these approaches in physical layer vs. network layer failover.

How does modernization change the risk?

Modernization reduces long-term risk, but it does not happen overnight. FAA and European programs such as SESAR, supported by EUROCONTROL, are moving voice and data to IP networks over multiple years. During that time, facilities operate hybrid networks, and every cutover window, carrier transition and legacy circuit waiting its turn is a moment where one path is carrying critical traffic alone.

Keeping the legacy circuit available as a switchable fallback while the new path is proven is one of the simplest ways to protect a cutover.

How can engineers reduce the risk of ATC communication failures?

1. Inventory and classify circuits by operational impact: frequencies, interphone, surveillance and data feeds.
2. Map the physical path of each critical circuit, end to end, to find shared conduits, offices and equipment.
3. Add a truly diverse backup path: different carrier, route, entrance or medium.
4. Automate the switchover at the physical layer, so failover does not depend on the network or on someone reaching a patch panel.
5. Make sure the switch is not a new single point of failure: fail-soft operation, latching relays, redundant control and redundant power.
6. Test failover regularly and monitor both paths.

For a step-by-step method, read how to add redundancy to legacy communication circuits.

Frequently asked questions

Are ATC outages usually caused by radios?
Radios and voice switches do fail, but many outages trace back to the telecommunications circuits and supporting equipment that connect facilities to remote sites.

Does migrating to IP eliminate single points of failure?
No. IP networks introduce their own shared dependencies, and legacy circuits remain in service throughout multi-year transitions.

What is the fastest way to protect an existing circuit?
Add a diverse backup circuit and an A/B switch at the physical layer, which protects the circuit without replacing the equipment on either end.

Protecting critical ATC circuits? See how Dataprobe protects ATC circuits on our Communication Circuit Redundancy for Air Traffic Control page, or review the full specifications of the RSS Series Redundancy Switching System.