Google Points the finger at Humans for Accidents Involving Its Self-Driving Autos

Its armada has been involved in 11 accidents in six years.

Car accidents can and do happen in self-driving vehicles, yet you cannot simply accuse the computer, Google states.

The tech giant uncovered in a post on Medium Monday that its armada of autonomous vehicles has been involved in 11 minor accidents since first taking off six years back.

“Even when our software and sensors can detect a sticky situation and take action earlier and faster than an alert human driver, sometimes we won’t be able to overcome the realities of speed and distance; sometimes we’ll get hit just waiting for a light to change.” Chris Urmson, the director of Google’s driverless cars program, composed.

And that’s important context for communities with self-driving cars on their streets; although we wish we could avoid all accidents, some will be unavoidable.” Seven of Google’s accidents involved being rear-ended, the organization said.

Two of the mishaps were sideswiped, and one was a collision with an auto rolling through a stop sign.

Google offered the extra information about its program taking after an Associated Press investigation that discovered three of Google’s driverless cars have been involved in accidents in California since September.

A mysterious source told the AP that in no less than one of the occurrences, the auto was in driverless mode when the accident happened.

Google’s cars have driven a sum of 1.7 million miles, issuing them an accident rate of around 6.5 every million miles traveled.

That is impressively higher than the 2.8 property-damage-only accidents per million miles travelled that included passenger cars nationally in 2012, as per the National Highway Traffic Safety Administration.

Google is fast to bring up that a substantial number of fender bender and other minor accidents are never reported to the police, making it difficult to compare Google’s record.

Google has invested intensely in self-driving car technology.





Leave a Reply

Your email address will not be published. Required fields are marked *