Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacRumors

macrumors bot
Original poster
Apr 12, 2001
68,434
39,268


With the iPhone 14 models, Apple introduced a Crash Detection feature that is designed to contact emergency services automatically should a collision be detected. Crash Detection has already saved lives, but there have also been a number of complaints about the option accidentally triggering at ski resorts, amusement parks, and in other non-emergency high-activity situations.

iphone-14-pro-car-crash-detection.jpg

Apple has introduced Crash Detection optimizations in the last several iOS 16 updates to try to cut down on false calls, and now the company has new recommendations for users that accidentally activate the crash detection feature. In an updated Crash Detection support document, Apple directs users not to hang up if an accidental call is placed, and to instead explain to the emergency responder that help is not required.
If the call has been made, but you don't need emergency services, don't hang up. Wait until a responder answers, then explain that you don't need help.
Apple also removed a line in the support document that suggested users cancel a call during the timer period. "If you don't need to contact emergency services, tap Cancel and confirm that you don't need emergency services," read the sentence that has been pulled from the document.

The Crash Detection support site continues to suggest that users should dismiss an alert if they are able to do so, but Apple appears to want to put a stop to iPhone users canceling or hanging up on an already-started emergency call and leaving emergency responders wondering what happened.

Emergency dispatchers around ski slopes have been particularly unhappy with the number of accidental calls that are being received from Crash Detection. Skiing and snowboarding tumbles are able to trigger Crash Detection, and with the heavy clothing worn with these activities, iPhone and Apple Watch users sometimes don't notice that an emergency call has been placed.

In Colorado's Summit County, for example, 185 accidental Crash Detection calls were received in a week in January, wasting time and resources needed for actual emergencies. Summit County emergency services director Trina Dummer said in February that the situation threatens to "desensitize dispatchers and divert limited resources from true emergencies."

Apple in response sent four representatives to Summit County to observe the emergency call center, and further optimizations have since been added.

Crash Detection is available on the iPhone 14 models and the latest Apple Watch models. Using sensors like the accelerometer and gyroscope, it can detect a severe car crash and automatically call emergency services if a user does not respond to an alert within 20 seconds.

Article Link: Apple Directs Users Not to Hang Up on Operators in Accidental Crash Detection Calls
 
It’s hard because on the one hand, if I crash on the hill and I’m not able to call for help I want it to do it for me. But if I’m able to still move afterwards, and just don’t hear it calling, I don’t want that.

I’ve heard the geofence suggestion, and maybe for theme parks where the chances of you flying off the roller coaster is next to zero, but for ski resorts I do still want that to be triggered. Just maybe… refined. Which it sounds like they have been! So that’s good.
 
This feature gets a lot of hate on here sometimes.

Personally, I had a bike accident about a year ago and broke some bones. As I was gathering myself, the siren started to go off and I was able to cancel it. Luckily, I didn't need it to call 911, but I was very thankful for it going off. I guess that is why I'd rather it be a little too sensitive instead of not sensitive enough. This is one of those things that will never be perfect and that is okay.
 
This feature gets a lot of hate on here sometimes.

Personally, I had a bike accident about a year ago and broke some bones. As I was gathering myself, the siren started to go off and I was able to cancel it. Luckily, I didn't need it to call 911, but I was very thankful for it going off. I guess that is why I'd rather it be a little too sensitive instead of not sensitive enough. This is one of those things that will never be perfect and that is okay.
This is one view.

Let me give you another standpoint - emergency services have limited capacity and because of these false calls reaction to actual emergency can be delayed and someone may die consequently.
 
This is one view.

Let me give you another standpoint - emergency services have limited capacity and because of these false calls reaction to actual emergency can be delayed and someone may die consequently.
Yet this feature also saves lives, probably more than will ever be at risk due to the rare instance of delaying help to an actual emergency in the case of a false alert.
 
This feature is some hot mess. Can't understand how it could have been approved when it is not and can not be false-positive proof and so it overloads emergency services and it will continue to do so.

That's black-and-white thinking. There will never been a "perfect" implementation. The goal is to *reduce* false-positives. This feature has saved lives and Apple continues to work hard to refine the detection algorithm. We know and appreciate that. It would be silly to demand that they remove this feature because it's not "perfect".
 
This is one view.

Let me give you another standpoint - emergency services have limited capacity and because of these false calls reaction to actual emergency can be delayed and someone may die consequently.
Ehh, maybe. But probably not. In my days of dispatching which was about ten years ago I think about half of the 911 calls that came in were bogus butt dials. Those are a waste of time. A call coming in and the person says “sorry, I’m ok”, probably not that big of a deal.
 
Why not create a sports mode that would also detect crashes but using an adjusted algorithm?
This way, if a skier has an accident and gets covered in snow, he/she could also be saved.
"We can't fix our logic, so it's your responsibility to solve our problem for us"

Seriously, how hard is it to geofence off the ski slopes?
You geofence off the ski slopes and then when someone finds themselves in a situation like this person, then that person will be SOL.


Sorry, but geofencing an area is a dumb idea.
 
This feature gets a lot of hate on here sometimes.

Personally, I had a bike accident about a year ago and broke some bones. As I was gathering myself, the siren started to go off and I was able to cancel it. Luckily, I didn't need it to call 911, but I was very thankful for it going off. I guess that is why I'd rather it be a little too sensitive instead of not sensitive enough. This is one of those things that will never be perfect and that is okay.
It’s a great feature, but for places where there are high levels of false alarms, the local government should be able to ask Apple to geofence it off. If you’re skiing in bounds, there’s usually plenty of other people around to find you. If you’re out of bound….Darwin.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.