Crash Detection launched with the iPhone 14 and recent Apple Watch models in 2022. The feature uses accelerometer and gyroscope data up to 256 Gs to flag severe motor vehicle collisions and auto-dial 911 if the user doesn't respond in time. It also, famously, cannot tell the difference between a T-bone in an intersection and a snowboarder eating it on a blue run.
Summit County, Colorado fielded 71 automated crash notifications from ski resorts in a single weekend during the 2022–23 season. Zero emergencies. One supervisor said her whole day was managing crash notifications. Apple sent reps. Updates followed. The calls kept coming. What you usually get: a synthetic voice announcing a hard fall, location coordinates, no human on the line. The person is almost always fine and either didn't notice the call went out or is frantically tapping "I'm OK" while you're trying to reach them.
The classic. An open line with ambient noise. Could be a toolbelt pressing against a phone at a job site. Could be someone's kid with a hand-me-down device. Could be someone who was about to call, hit the button, and thought better of it. Could also be a DV victim who dialed in silence because that's the only way they could.
Every center has had the pocket-dial that turned out to be real. Nobody wants to be the one who hung up on it.
Every cellular device in the United States — activated, deactivated, prepaid, SIM-less, it doesn't matter — is required by FCC rule to complete a 911 call. That's why the old phone in grandma's junk drawer is a legitimate piece of emergency equipment. It's also why a seven-year-old with an unclaimed iPhone can tie up your center for half an hour before anybody figures out the caller has no return number because the phone doesn't have a number.
No ANI. No ALI that resolves to a subscriber. Sometimes a rough tower hit, sometimes device-based hybrid location, sometimes nothing at all.
In 2013, nine-year-old Brianna Hunt tried to call 911 four times from a motel room in Marshall, Texas while her mother Kari was being attacked in the next room. The calls never connected. The motel phone system required a 9 for an outside line. Brianna didn't know that. Kari Hunt died. Her father Hank spent the next five years getting Kari's Law passed.
Kari's Law is a federal statute that requires multi-line telephone systems — the PBX-style systems in hotels, offices, campuses, hospitals — to be pre-configured so a user can dial 911 directly, with no prefix, no 9, no access code. It also requires the system to send a notification to a designated on-site location (front desk, security office) when a 911 call is made, so first responders have somebody who can meet them at the door.
The part most people miss: the law is not retroactive. It applies to MLTS that are manufactured, imported, sold, leased, or installed after February 16, 2020. A hotel that installed its phone system in 2017 and hasn't touched it since may still be a "dial 9" property and legally allowed to be. Some states — Texas, Illinois, Maryland among them — passed their own versions that do apply retroactively.
Section 506 of the RAY BAUM'S Act is the companion piece. It requires that MLTS calls to 911 convey "dispatchable location" — typically street address plus floor, suite, or room — not just the main billing address for the building. If you're taking a call from a hotel, hospital, or enterprise phone system, do not assume the ALI is the room. A compliant system should deliver dispatchable location down to the unit. A non-compliant legacy system might drop you the front desk address and nothing else. Ask. Always ask.
The open line that won't talk is a listening exercise. You are listening for background audio that tells you what this is. Traffic noise. A TV. Music. Someone breathing. Someone crying quietly. The two-tap code for a DV hush call. The sound of a phone being picked up and set down. Most centers have a policy on how long to stay before disconnecting a silent open line — know yours, but err on the side of longer when the audio is ambiguous. Before you hang up, callback. If callback rings and rolls to a generic voicemail, you have almost nothing. If callback rings and somebody picks up confused, you usually have your answer. If callback is immediately rejected to voicemail, that's a data point.
For the automated crash notification, treat the coordinates as a strong lead, not gospel. Device-based hybrid location is often better than tower triangulation, but a skier's coordinates can shift 100 meters by the time you've got the call on screen. Try to get the synthetic voice to repeat the location. Callback the number. If you get the user and they say they're fine, document and clear. If you don't, you're running a welfare check on whatever those coordinates say.
"Ping" is loose jargon. What you're usually asking for is an emergency location request from the carrier — sometimes called a RapidSOS pull, sometimes a carrier-initiated location update, sometimes a direct RapidSOS Portal query if your center is integrated. The standard is life-safety. No warrant is needed for an exigent-circumstances location request under 18 U.S.C. § 2702(c)(4), but the carrier will want to hear the exigency articulated. Missing endangered, suicidal caller who hung up, abducted child, welfare check with credible concern — this is your tool. A dropped pocket-dial with no indicators of distress is not.
Full subscriber pull is a different animal. You're asking the carrier for subscriber information — name, address, billing — which generally requires an administrative subpoena or search warrant depending on what you're requesting. That's a detective/records problem, not a real-time dispatcher problem. Know where to hand it off when it gets to that point.
The trap here is assuming Kari's Law and RAY BAUM'S Act solved the problem. They are forward-looking to systems installed after February 16, 2020. A property built in 2015 that hasn't replaced its MLTS may still be a "dial 9" system delivering nothing but the building's main address. Don't trust the display to give you the room.
The work, in order: stay on the line listening for any audio cue at all — voices, TV, breathing, struggle, the hush-call double tap. Hit callback. Engage the front desk by phone in parallel and ask them to physically sweep the building if you can't get the caller to talk. Send units based on your center's threshold for silent opens, with the front desk address as the staging point and the understanding that the actual location is unknown. Document that the property is a probable legacy MLTS so the next call from the same number gets the same posture from the jump.
You can't ignore it. You also don't have to overcommit. The honest answer lives between "ignore" and "full code 3 deployment." Treat the coordinates as a lead, not gospel — device hybrid location is usually better than a tower triangulation but a moving skier's coords can be 100 meters off by the time you read them. Try to get the synthetic voice to repeat the location. Callback once or twice. If nothing, ski patrol or whatever the appropriate jurisdictional resource is at that resort gets the lead with the location and the context that this is a crash notification with no callback. Most resort centers have a workflow for this by now — if yours doesn't, that's a Saturday well spent.
The deeper question for the room: does your center have a documented standard callback script for crash notifications, or are people winging it call by call? If it's the second one, the inconsistency is itself a risk — one call-taker holds for 30 seconds, another holds for 5 minutes, and the difference is whether a real one slips by.
The basis is exigent circumstances under 18 U.S.C. § 2702(c)(4) — the federal statute that allows electronic communication service providers to disclose customer records and location information to a government entity when the provider, in good faith, believes there is an emergency involving danger of death or serious physical injury. That's the standard the carrier's compliance desk is trained to recognize. You don't need a warrant. You do need to articulate the exigency clearly.
Say it like this: agency name, your name and call-back, the nature of the emergency in one sentence ("I have a 911 caller who stated he was going to harm himself before disconnecting"), the phone number you need located, and the phrase "I am requesting emergency location information under exigent circumstances." Most carriers will then walk you through what they need from you in writing within 24 hours. Have your center's exigent-disclosure form ready and know who in your building has signature authority for the after-action paperwork.
If you have RapidSOS integration, this conversation may be unnecessary — you may already have the location at the console. Worth knowing both paths.
This is detective bureau work. Subscriber information — the name, address, and account history behind a number — requires legal process. Generally an administrative subpoena for basic subscriber info, a court order under 18 U.S.C. § 2703(d) for transactional records, and a search warrant for content. That choice depends on what's actually being requested and how the carrier's compliance posture reads it.
The hand-off matters. The investigator needs to know which carrier to serve and where. That's what the SEARCH ISP List is for. Over 700 providers with current legal contact info, fax numbers, emails, and notes on what each carrier retains and for how long. The SEARCH Investigative Toolbar puts the same information in the browser. Both are vetted-LE-only resources. If your detective bureau doesn't already have these bookmarked, the dispatcher who hands them the link is going to look like the smartest person in the building.
Bonus context for the room: harassment by phone may also fall under your state's stalking or telephone harassment statutes. Documentation from the comm center side — preserved CAD entries, recorded calls, ANI/ALI captures — is what makes that case prosecutable.
The reconciliation is a process, not a coin flip. Listen first — really listen. Strip the headset volume up. The audio that turns a pocket dial into something else is usually faint and on the edge: a distant raised voice, a child crying, the rhythm of a struggle, the unnatural pause that says someone is on the other end deciding whether to speak. If you hear nothing for 60-90 seconds and the audio profile is consistent with movement (rustling, footsteps, breathing without speech), pocket dial is the working hypothesis.
Then test it. Callback. If the subscriber answers and confirms, document and clear. If callback rolls to voicemail and the line stays open, hold longer — the most dangerous version of this call is the one where the caller can't speak but is still on the line hoping you'll figure it out. Listen for any change. Many centers code a hush-call indicator (DTMF tones, the "yes/no" tap pattern, prolonged silence followed by a single key press). If your CAD has a flag for "open line / hold extended," use it.
The unhappy truth: you will close some of these as pocket dials and one of them, eventually, will turn out to have been real. The only protection is consistent process applied to every call regardless of how routine it feels. You don't get to be lucky. You get to be careful.
"What floor and suite are you in?" That question is not redundant even on a Section 506-compliant MLTS, because legacy systems, partially configured systems, and systems that were technically updated but never tested in the field will all happily deliver you the building's main address with no granularity. RAY BAUM'S Act requires dispatchable location, but "requires" and "delivers" are not always the same word in practice.
The verbal confirmation is the belt-and-suspenders. You ask, they answer, you write it down. If the system gave you the suite already, beautiful — you've now confirmed it. If the system didn't, you just saved the responding units a stairwell tour of an office tower at 2 a.m. Either way, no time is wasted.
This is a real-world operational exercise dressed up in a vintage-telephone aesthetic, because the core problem — the call that isn't — is as old as the switchboard. The Summit County, Colorado figures cited above are real, drawn from 2022–2023 reporting by The Colorado Sun and The New York Times. The Kari Hunt incident is real. Kari's Law and Section 506 of RAY BAUM'S Act are real federal statutes. The legal mechanism for emergency location requests under 18 U.S.C. § 2702(c)(4) is real and is the daily mechanism by which carriers provide location information to PSAPs. The composite Switchboard Log is illustrative — the calls and call types are accurate to what comm centers field every day; the specific shift is a fiction stitched together from many real ones.