And it’s easy to see where this is going, as the likelihood of an accident is obviously more significant if you don’t use voice guidance and hands-free input to interact with such apps.
One 25-year-old driver says he was just looking at a navigation app to find a place to eat when his lorry crashed into a railway bridge in Glasgow Road, Camelon. Fortunately, despite the violent crash, the man escaped without any injuries, but the collision caused damage to both the bridge and the trailer.
Without a doubt, it’s not uncommon for navigation apps to send drivers on roads that don’t match their vehicles. For example, Google Maps is missing a dedicated truck mode for navigation, despite users out there repeatedly calling for such an update in the last few years.
So while at first, this is a crash that once again shows the limits of navigation apps, it actually isn’t, as the driver initially forgot to share one "tiny" detail. He was four times over the drug driving limit, according to local media, and a blood sample revealed he had 200 micrograms of benzoylecgonine, one of the most abundant metabolites of cocaine.
The man was banned from driving for a little over 21 months and also ordered to do 90 hours of unpaid works in the next 12 months.
At the end of the day, this story once again shows that navigation apps do come with their own shortcomings, but when used correctly, the distraction is reduced substantially. And of course, just keep in mind a lie has no legs, but a violent crash picked up by the media has big wings.