NENA ENP study materials
NENA ENP study resources

Wireless Phase II Location Failures After a Small-Cell Deployment

NENA ENP · Put your knowledge to work in context.

All case studies

Wireless Phase II Location Failures After a Small-Cell Deployment

A PSAP serving 210,000 residents handles about 1,100 9-1-1 calls per day, 78% wireless. Over six weeks, supervisors notice that wireless calls from a 1.5-square-mile downtown corridor increasingly arrive with Phase II location that is either missing or shows a horizontal accuracy worse than 300 meters. The affected calls cluster near a newly installed set of small cells mounted on street furniture. Call takers report that re-bidding (re-initiating the location request) sometimes improves the fix but often does not. The PSAP's GIS map displays the initial call routing location instead of the updated dispatchable location, so telecommunicators have been reading the cell-sector centroid aloud to responders. The wireless carrier's engineering contact says the small cells are "not yet fully integrated" and asks the PSAP to "just use Phase I for now."

1. What is the most defensible immediate operational response, and what should the PSAP NOT do while the technical issue is unresolved?

Read the worked answer

The PSAP should not accept a blanket downgrade to Phase I. Phase I (cell sector and centroid) is not a dispatchable location and materially increases response time and responder safety risk in a dense corridor. Immediate steps:

  1. Document the pattern - capture call records, ANI/ALI, Phase II accuracy values, and re-bid outcomes for the affected corridor so the carrier has evidence, not anecdotes.
  2. Change the display behavior - if the CAD/GIS is showing routing location rather than the latest Phase II fix, that is a PSAP-side configuration defect and should be fixed or worked around immediately.
  3. Script the call-taking question - telecommunicators should confirm the address/landmark verbally and read back what they have, rather than reading a centroid aloud as if it were an address.
  4. Escalate in writing to the carrier's regulatory/9-1-1 account team, not just the local engineer, with a defined response deadline and a request for root cause and remediation timeline.

What NOT to do: do not formally agree to Phase I-only service, do not stop logging the failures, and do not let the verbal workaround become the permanent process. A verbal "use Phase I for now" can become the de facto standard if undocumented.

2. The carrier misses the deadline and the failures continue. How should the PSAP frame the escalation, and what internal governance should accompany it?

Read the worked answer

Frame it around public safety impact and measurable harm, not vendor frustration:

  • Quantify: number of affected calls, average accuracy degradation, number of calls where responders were dispatched to an incorrect or imprecise location, and any delayed-response incidents.
  • State the standard being missed in outcome terms: wireless 9-1-1 calls are expected to yield a dispatchable location; persistent 300m+ error in a dense corridor is not operationally usable.
  • Escalate through the carrier's formal 9-1-1/regulatory escalation path and copy the state 9-1-1 authority or governing body that oversees the system.

Internal governance:

  • Brief the PSAP director and legal counsel so messaging is consistent.
  • Notify the governing board/authority in writing.
  • Set a recurring review (e.g., weekly) with named owners and a written decision log.
  • Prepare a contingency: interim responder notification protocol for the corridor, and a documented risk-acceptance record if leadership decides to continue operating with degraded data.

The key judgment: escalation is a management and documentation exercise as much as a technical one. The record you build now is what supports any later regulatory complaint or funding request.