Summary

  • The FCC is asking whether its four-factor 2003 test still identifies which services should carry 911/E911 duties.
  • The notice examines objectives, scope, harmonized requirements and legal authority; it does not itself change current rules.

When someone reaches 911, the user experiences a call, not a regulatory category. The rules, however, attach obligations to services and providers. That gap is now before the Federal Communications Commission: how should it decide which technologies belong inside the 911 framework as communications move across more kinds of networks and platforms?

The boundary has an old test. In its 2003 E911 Scope Order, the FCC described four factors: whether a service offers real-time, two-way voice interconnected with the public switched telephone network; whether users reasonably expect 911 or Enhanced 911 access; whether the service competes with traditional wireless or legacy wireline service; and whether E911 is technically and operationally feasible. The framework weighed expectations, competition and capability. It was never the sole basis for every 911 obligation: legislation and service-specific decisions have also shaped the rules.

On September 30, 2026, the Commission adopted FCC 26-63, a Notice of Inquiry in PS Docket 26-197. It asks whether the 2003 criteria remain useful, whether to revise them, and how far requirements should be harmonized across services and technologies. It also asks what enduring objectives 911 policy should serve and how the FCC’s authority applies in a communications landscape that no longer divides neatly into old service labels.

This is not simply a question of whether a technology can place a call. The rules address a chain: delivery to a public safety answering point, location and callback information, routing, and responsibilities split among providers. A service may lead a user to expect access while relying on another network for the connection. Technical ability alone does not decide who should bear a legal duty or what implementation is feasible. A service label can conceal those differences.

The inquiry matters before any rule change. Keep a voice-centred test and some emerging functions may remain hard to classify. Broaden the test around user expectation or function and the FCC must explain what triggers an obligation, which information and performance it requires, and where its authority ends. Harmonization could reduce gaps among categories without making the services’ technical roles identical.

For now, this is an inquiry, not a new mandate. Part 9 of the FCC rules remains operative for the services and providers it defines. The notice does not establish that any named service has failed, is outside current rules, or must change its systems. It puts the criteria for future coverage into a public record before the Commission decides whether to propose or adopt another approach.

The eventual test is whether reasonable expectation of emergency access can be tied to a clearly assigned, technically workable duty: who receives the request, who can locate it, who routes it onward, and which regulator can require each link to work.

Sources