Why the FCC Is Right to Modernize the 911 Framework
By Mark J. Fletcher, ENP
Listen to the audio edition
Watch the video presentation
The Federal Communications Commission is asking a question that is long overdue: Does the nation’s 911 regulatory framework still match the communications environment the public actually uses?
In its circulated draft Notice of Inquiry, “Modernizing the 911 Framework”, the Commission proposes a comprehensive review of rules and assumptions built largely around distinct service categories, dedicated legacy networks, and voice-centric emergency calls.
The document is scheduled for tentative consideration at the Commission’s September 30, 2026 open meeting, so it is not yet final agency action. But the inquiry itself deserves strong support.
This is not about weakening 911. It is about recognizing that protecting yesterday’s architecture is no longer the same as protecting access to emergency services.
A Framework Built for a Different World
The Commission’s current 911 scope analysis dates to 2003. It asks whether a service provides real-time, two-way voice, connects to the public switched telephone network, competes with traditional telephone service, and can feasibly support E911.
Those questions made sense when communications services fit into recognizable boxes. Wireline was wireline. Wireless was wireless. VoIP was the newcomer. The public switched telephone network remained the center of the universe.
That universe has changed.
A single emergency communication may now involve a smartphone, Wi-Fi, a broadband provider, cloud infrastructure, an operating system, an application, an Emergency Services IP Network, and software inside the ECC. Satellite direct-to-device service, wearables, connected vehicles, smart speakers, alarm platforms, telematics, and IoT sensors add even more entry points.
The FCC reports that approximately 71.3% of 911 calls covered by its 2024 data originated on wireless phones. Meanwhile, the boundaries separating wireless, Wi-Fi, satellite, applications, and cloud services continue to dissolve.
Consumers do not know which regulatory category carried their emergency request—and they should not need to know.
If a device or service creates a reasonable expectation that it can reach help, our policies should focus on whether that request is delivered reliably, with the location, callback information, context, and accessibility the emergency requires.
The Legacy Network Earned Its Reputation—Past Tense
For decades, the legacy 911 network was extraordinarily resilient. Dedicated circuits, selective routers, purpose-built databases, and carefully controlled interfaces created predictable service. That architecture saved lives and earned the trust placed in it.
But honoring that history does not require us to preserve every component indefinitely.
Much of that infrastructure is now aging, increasingly difficult to support, and dependent on shrinking pools of replacement parts and specialized expertise. What was once ultra-resilient is becoming brittle and fragile.
Worse, operating legacy and NG911 networks in parallel can introduce additional interfaces, gateways, failure points, testing requirements, and operational ambiguity.
We should stop confusing familiarity with reliability.
A circuit is not resilient simply because we have monitored it for 30 years. A selective router is not strategically valuable merely because it still passes traffic. If most emergency communications are being created by mobile and IP-connected devices, the critical engineering questions have changed.
How many independent paths can deliver the emergency request? Can traffic be rerouted dynamically? Are location and callback data preserved? Can another ECC receive the traffic? Are cloud, software, identity, cybersecurity, and database dependencies visible and tested? Can we fail over without losing the information that makes NG911 valuable?
Those questions protect the mission. Counting and preserving every legacy trunk protects the architecture.
Regulate the Function, Not the Label
The strongest element of the FCC’s proposal is its willingness to consider a baseline set of functional 911 capabilities across technologies.
Routing to the appropriate 911 authority, accurate location, and callback information should not depend on whether an emergency request began as a cellular call, a Wi-Fi session, a satellite message, an application interaction, or an automated event from a connected device.
The same principle should extend to reliability oversight. The provider controlling a critical element of an emergency communications path should not escape responsibility merely because it does not resemble a traditional telephone company.
In an IP ecosystem, operating systems, device manufacturers, cloud platforms, application providers, database operators, network aggregators, and NG911 service providers may each influence whether a request reaches public safety.
Regulation must follow operational responsibility and measurable outcomes—not a historical label attached to a service.
Retirement Is an Engineering Process, Not a Reckless Deadline
Moving forward does not mean pulling the plug on legacy systems tomorrow morning. Public safety does not get the luxury of a maintenance window in which emergencies agree to wait.
The transition must be engineered. Existing traffic patterns must be measured. Alternate paths must be proven. Interoperability and legacy gateways must be tested while they remain necessary. ECCs need documented fallback procedures, trained staff, realistic capacity models, and clear responsibility across every provider in the path.
But “transition carefully” cannot continue to mean “operate everything forever.”
Every dollar and engineering hour spent maintaining obsolete infrastructure is a dollar and hour unavailable for diverse IP transport, georedundant services, cybersecurity, identity management, location validation, network observability, and realistic end-to-end testing.
At some point, preserving the old network stops reducing risk and begins creating it.
Put Engineering Evidence into the Record
If the Commission adopts this Notice of Inquiry, the public-safety community should participate in PS Docket No. 26-197.
911 authorities, ECC leaders, service providers, manufacturers, engineers, and telecommunicators should provide operational evidence—not simply defend familiar business models or existing regulatory classifications.
The record should document actual traffic patterns, failure modes, hidden dependencies, transition costs, consumer expectations, and the capabilities that must be protected regardless of platform.
This is an opportunity to define resiliency around outcomes before another generation of technology is forced into rules written for the previous one.
The Right Measure of Resilience
The future of 911 should not be judged by the survival of a particular circuit, switch, trunk group, or service category. It should be judged by whether the public can reach help and whether public safety receives the information necessary to respond.
That is why this FCC inquiry matters. It begins moving the discussion away from the technology that once carried 911 and toward the capabilities emergency communications must deliver now.
The legacy network served us exceptionally well. It deserves recognition, a disciplined transition plan, and a responsible retirement—not indefinite life support.
It is time to stop coddling the legacy network and start engineering the future with the same seriousness that built the original system. The Commission is asking the right questions. The public-safety community should answer them clearly, technically, and without allowing nostalgia to stand in the way.
Reliable access to 911 is the mission.
Everything else is infrastructure.
Author’s note: This article reflects my personal views and is not an official statement of the Federal Communications Commission or any other organization. The referenced document is a circulated draft subject to Commission consideration and change.
Source references
- Federal Communications Commission, Modernizing the 911 Framework, circulated draft Notice of Inquiry, PS Docket No. 26-197, September 9, 2026.
- Federal Communications Commission, Electronic Comment Filing System. Search for PS Docket No. 26-197.
- Federal Communications Commission, Seventeenth Annual Report to Congress on State Collection and Distribution of 911 and Enhanced 911 Fees and Charges, cited by the Notice for 2024 call-origin data.