What happened
A technical problem began affecting the FAA network at approximately 3:30 p.m. ET on November 13, prompting a nationwide ground stop. The agency reported instability at 17 of 22 air route traffic control centers and several approach-control facilities. Some radio frequencies and radar feeds remained available. Traffic resumed around 8:15 p.m. [1]
The FAA identified two potential sources of excessive data: Amarillo, Texas, and El Dorado, Arkansas. Its provider had installed a router at El Dorado. Isolating both sites stabilized the network. The FAA reported no indication of a cyberattack; the root cause remains under investigation. [1]
What the findings tell us
The FAA has not attributed the incident to conventional plain old telephone service (POTS), and its air-traffic network differs from ordinary airport phone lines. It distinguishes routine equipment replacement from its broader modernization program. [1] A trusted advisor's first job is to keep those distinctions clear.
Two questions are worth every operator's attention:
- Could a local change have wider consequences? The investigation is a reminder to map dependencies without assuming a confirmed failure mechanism.
- Is the maintenance window appropriate? The FAA says it will reconsider the timing of replacement and maintenance work. [1]
These questions apply well beyond aviation, wherever a service change could affect critical operations.
The question for every client
How much do you really know about the services your operation depends on, especially the ones that have been in place for years?
Legacy connectivity often supports far more than a desk phone. Depending on the facility, an old line may serve an elevator phone, a fire or intrusion alarm, an access-control panel, an emergency call box or another operational function. Those services are frequently managed by different teams, billed by different providers and documented in different places, if they're documented at all.
The real risk isn't only that an old service fails. It's that a carrier announces a change, a building is renovated or an outage occurs before anyone has confirmed what the circuit supports, who owns it and what a safe replacement requires.
An invoice can tell you a service exists. It can't tell you what depends on it.
Do the discovery before the deadline
When a critical service needs attention, speed matters. But moving faster should mean removing uncertainty and coordination delays, not skipping validation. Here is the approach we recommend:
- Inventory the service. Identify the provider, location, circuit or line, contract terms and the people responsible for it.
- Confirm the function. Determine what is actually connected, how it's used and which teams or third parties rely on it. Never disconnect a line just because it looks unused.
- Assess the replacement. Evaluate available connectivity and device compatibility against the facility's requirements, including power, failover, coverage and applicable codes or approvals.
- Coordinate the change. Bring the facility, carrier, equipment vendor and other responsible parties into one plan, with clear ownership and a realistic cutover window scheduled to limit operational impact.
- Test and document. Agree on acceptance tests, escalation contacts and a rollback or contingency plan before the old service is retired.
For safety-critical and regulated systems, the authority having jurisdiction, the equipment manufacturer and qualified specialists must set the requirements. A replacement that works for an administrative phone is not automatically suitable for an emergency or life-safety application.
If conventional POTS lines are part of your environment, see OPTRIC’s POTS line replacement article for a closer look.
Where OPTRIC fits
Our role is to give you one accountable path through a complicated transition. We help identify services and stakeholders, engage carriers and providers, organize the information you need to make decisions, and follow the transition through the carrier process to completion.
That doesn't replace your operational, engineering or safety teams. It gives them a clearer path through the commercial and coordination work around the technology, so they spend less time chasing disconnected information and more time making informed decisions.
The bottom line
The goal isn't modernization for its own sake. It's knowing what matters, understanding what will change, and making the transition with the right people and safeguards in place.
If you're facing a carrier change, or you have legacy services whose purpose isn't clear, start by identifying the dependencies. The best time to do that is before a deadline or a disruption makes the decision for you. Talk with OPTRIC about the legacy services at your locations and the questions to resolve before making a change.
