Google Self-Driving Car Crashes Into Bus In California - InformationWeek
IoT
IoT
IT Life
News
3/1/2016
11:05 AM
50%
50%

Google Self-Driving Car Crashes Into Bus In California

It isn't the first accident involving the company's self-driving vehicles, but it is the first time Google has admitted responsibility for the incident.

Google, Tesla And Apple Race For Electric, Autonomous Vehicle Talent
Google, Tesla And Apple Race For Electric, Autonomous Vehicle Talent
(Click image for larger view and slideshow.)

Google has been touting its progress with self-driving cars and the overall safety of the problem, but it's clear that accidents can still happen.

On Valentine's Day, one of the company's vehicles hit a public bus on El Camino Real in Mountain View, California, as it was attempting to reenter traffic after having stopped in front of some sandbags positioned around a storm drain that were blocking its path.

Google's autonomous vehicle (AV) was operating in self-driving mode at 2 mph at the time of the accident.  No injuries were reported, according to the Feb. 14 accident report, but the car sustained body damage to the left front fender, the left wheel, and one of its driver's side sensors.

(Image: Google)

(Image: Google)

Reuters reported that in addition to the initial report of the accident, Google detailed its take on the accident as part of its February monthly report, where it claimed partial responsibility for the accident -- in a first for the company.

"Our car had detected the approaching bus, but predicted that it would yield to us because we were ahead of it," the report noted. "Our test driver, who had been watching the bus in the mirror, also expected the bus to slow or stop. And we can imagine the bus driver assumed we were going to stay put. Unfortunately, all these assumptions led us to the same spot in the lane at the same time."

The statement also noted that from now on, Google's cars will work to more deeply understand that buses and other large vehicles are less likely to yield to them than other types of vehicles.

"We've now reviewed this incident (and thousands of variations on it) in our simulator in detail and made refinements to our software," the report concluded. "We hope to handle situations like this more gracefully in the future."

This is not the first time Google's efforts to make self-driving cars a reality have been accompanied by some very real speed bumps.

In July, one of the company's Lexus vehicles was driving autonomously towards an intersection outside Google's headquarters during evening rush hour.

The light was green, but traffic was backed up on the far side, so three cars, including the Google Lexus, braked and came to a stop so as not to get stuck in the middle of the intersection, after which a car travelling behind hit the vehicle.

[Read about other problems with Google's self-driving car.]

In May, Chris Urmson, the head of Google's self-driving car project, wrote a blog post revealing Google's self-driving cars had been involved in 11 minor accidents over the past six years.

However, Urmson was careful to point out that none of the accidents were the fault of the self-driving car, but rather, distracted drivers around the vehicle.

Not everyone is convinced the technology is ready to hit the roads, however, including a prominent nonprofit consumer advocacy group.

"Clearly Google's robot cars can't reliably cope with everyday driving situations," John M. Simpson of Consumer Watchdog told Phys.org. "There needs to be a licensed driver who can take over, even if in this case the test driver failed to step in as he should have."

Rising stars wanted. Are you an IT professional under age 30 who's making a major contribution to the field? Do you know someone who fits that description? Submit your entry now for InformationWeek's Pearl Award. Full details and a submission form can be found here.

Nathan Eddy is a freelance writer for InformationWeek. He has written for Popular Mechanics, Sales & Marketing Management Magazine, FierceMarkets, and CRN, among others. In 2012 he made his first documentary film, The Absent Column. He currently lives in Berlin. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
TerryB
50%
50%
TerryB,
User Rank: Ninja
3/2/2016 | 3:50:58 PM
Re: Jerk Factor
Well, it's only a 2004 model year sports car. :-)  Liability will be a huge issue on self driving cars. Huge. I'm somewhat surprised so many companies looking to take that on. Google is one deep pocket!
vnewman2
50%
50%
vnewman2,
User Rank: Ninja
3/2/2016 | 3:47:30 PM
Re: Jerk Factor
"But a human would have punched it if deciding to go, certainly could beat a bus going 15 mph if ahead of it at time."

Great point.  

But now that this information is out there, can't you just see people manpulating these exact situations and crashing into these vehicles on purpose - maybe to commit insurance fraud and trade in their beater for a...sports car perhaps???
TerryB
50%
50%
TerryB,
User Rank: Ninja
3/2/2016 | 3:43:34 PM
Re: Jerk Factor
Agreed @vnewman. But a human would have punched it if deciding to go, certainly could beat a bus going 15 mph if ahead of it at time. One reason I drive a sports car. :-)

I'm just calling bus driver a jerk assuming he knew car was cutoff by something goofy like sand bags in road. It's one thing not to yield/give someone a break if normal merging on highway or lane reduction. It's another when driver trapped by accident or sand bags in lane. I've seen jerks speed up just to pin person on purpose, passive aggressive idiots.

Just not sure what you would do to fix that programming? Reminds me of that Seinfeld episode George tries to get his high score Frogger arcade across street before battery runs out. :-) At some point you just gotta go and let person flip you off for making him slow down. If he hits you in rear, his fault. I'm assuming car hit bus in side, never made it fully in front of bus?
vnewman2
50%
50%
vnewman2,
User Rank: Ninja
3/2/2016 | 3:28:15 PM
Re: Jerk Factor
"Our car had detected the approaching bus, but predicted that it would yield to us because we were ahead of it,"

Well, I suppose a human driver could have predicted the same thing, and I know plenty of people who use that aggressive driving style, especially here in California.   However, the way I was taught to drive is you can't really guess what the other person is going to do.  You have to react to what is actually happening.
TerryB
50%
50%
TerryB,
User Rank: Ninja
3/1/2016 | 12:57:47 PM
Jerk Factor
I was just reading this in newspaper this morning. Sounds like bus driver was being a-hole and wanted to cut the car off. Not sure how you program around that.
How Enterprises Are Attacking the IT Security Enterprise
How Enterprises Are Attacking the IT Security Enterprise
To learn more about what organizations are doing to tackle attacks and threats we surveyed a group of 300 IT and infosec professionals to find out what their biggest IT security challenges are and what they're doing to defend against today's threats. Download the report to see what they're saying.
Register for InformationWeek Newsletters
White Papers
Current Issue
2017 State of the Cloud Report
As the use of public cloud becomes a given, IT leaders must navigate the transition and advocate for management tools or architectures that allow them to realize the benefits they seek. Download this report to explore the issues and how to best leverage the cloud moving forward.
Video
Slideshows
Twitter Feed
InformationWeek Radio
Archived InformationWeek Radio
Join us for a roundup of the top stories on InformationWeek.com for the week of November 6, 2016. We'll be talking with the InformationWeek.com editors and correspondents who brought you the top stories of the week to get the "story behind the story."
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.
Flash Poll