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.
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.
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
Top IT Trends to Watch in Financial ServicesIT pros at banks, investment houses, insurance companies, and other financial services organizations are focused on a range of issues, from peer-to-peer lending to cybersecurity to performance, agility, and compliance. It all matters.
Join us for a roundup of the top stories on InformationWeek.com for the week of October 9, 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."