Skip to main content

Google takes some responsibility after self-driving car hits bus in minor crash

Alphabet Inc's Google said on Monday it bears "some responsibility" after one of its self-driving cars struck a municipal bus in a minor crash earlier this month.

The crash may be the first case of one of its autonomous cars hitting another vehicle and the fault of the self-driving car. The Mountain View, California-based internet search leader said it made changes to its software after the crash to avoid future incidents.

In a Feb. 23 report filed with California regulators, Google said the crash took place in Mountain View on Feb. 14 when a self-driving Lexus RX450h sought to get around some sandbags in a wide lane.

Google said in the filing the autonomous vehicle was travelling at less than 2 miles per hour, while the bus was moving at about 15 miles per hour.

The vehicle and the test driver "believed the bus would slow or allow the Google (autonomous vehicle) to continue," it said.

But three seconds later, as the Google car in autonomous mode re-entered the centre of the lane, it struck the side of the bus, causing damage to the left front fender, front wheel and a driver side sensor. No one was injured in the car or on the bus.

Google said in a statement on Monday that "we clearly bear some responsibility, because if our car hadn’t moved, there wouldn’t have been a collision. That said, our test driver believed the bus was going to slow or stop to allow us to merge into the traffic, and that there would be sufficient space to do that."

The Santa Clara Valley Transportation Authority will investigate the circumstances of the accident, Stacey Hendler Ross, spokeswoman for the Santa Clara Valley Transportation Authority, said on Monday.

She said the Google car caused minor damage to the bus, striking the "pivoting joint," or flexible area in the middle of the articulated bus.
After the crash, 15 passengers on the bus were transferred to another bus.

An investigation to determine liability is pending, she said.

John M. Simpson, privacy project director for advocacy group Consumer Watchdog, said the crash "is more proof that robot car technology is not ready for auto pilot."

A spokesman for the California Department of Motor Vehicles said on Monday it will speak to Google to gather additional information, but added "the DMV is not responsible for determining fault."

Software Refined

Google said it has reviewed this incident "and thousands of variations on it in our simulator in detail and made refinements to our software. From now on, our cars will more deeply understand that buses (and other large vehicles) are less likely to yield to us than other types of vehicles, and we hope to handle situations like this more gracefully in the future."

There has been no official determination of fault in the crash. Google has previously said that its autonomous vehicles have never been at fault in any crashes.

The Mountain View Police Department said no police report was filed in the incident.

A spokesman for the US National Highway Traffic Safety Administration declined to comment.

The crash comes as Google has been making the case that it should be able to test vehicles without steering wheels and other controls.

In December, Google criticized California for proposing regulations that would require autonomous cars to have a steering wheel, throttle and brake pedals when operating on public roads. A licensed driver would need to be ready to take over if something went wrong.

Google said in November that in six years of its self-driving project, it has been involved in 17 minor accidents during more than two million miles of autonomous and manual driving combined.

"Not once was the self-driving car the cause of the accident," Google said at the time.

Popular posts from this blog

Explained: Camera Improvements in the New HTC 10

With the HTC 10, the Taiwanese company is promising to undo the past wrongs in the cameras of its previous flagship phones. The camera has long a weak point in HTC devices. At first, HTC sacrificed image resolution in the M8 and made the size of individual pixels larger to capture more light (what HTC called Ultrapixel). But the resulting 4 megapixel images were often fuzzy, especially when cropped or enlarged. To fix the issue, in its next flagship - the M9 - HTC went with smaller individual pixels in a 20-megapixel camera last year, but it still underperformed in extreme situations, such as indoors and close-ups. In the HTC 10, the company attempts to strike a balance with larger individual pixels (1.55µm), but not as large as before and a 12 megapixel sensor in its camera coupled with a ƒ/1.8 lens. HTC accepts that in the imaging performance in the M9 was not up to the kind of spec of what they really like to see in a flagship. HTC is giving a slight boost to the selfi...

Flexible Camera Developed That Can Be Wrapped Around Objects

A team led by an Indian-origin professor at Columbia University has created a novel sheet camera that can be wrapped around everyday objects to capture images that cannot be taken with one or more conventional cameras. "Cameras today capture the world from essentially a single point in space. While the camera industry has made remarkable progress in shrinking the camera to a tiny device with ever increasing imaging quality, we are exploring a radically different approach to imaging," said Shree K Nayar, computer science professor at Columbia University. "We believe there are numerous applications for cameras that are large in format but very thin and highly flexible," added Nayar who graduated from the Birla Institute of Technology, Ranchi, in 1984. Nayar's team designed and fabricated a flexible lens array that adapts its optical properties when the sheet camera is bent. This optical adaptation enables the device to produce high quality images over a wide ...

Samsung Galaxy J1 (2016) Leaked in Press Images

The anticipated successor to the popular Samsung Galaxy J1, tipped to be called the Galaxy J1 (2016), has once again been leaked in images on the Web. While in the previous leaks we have seen the unannounced smartphone in its Black colour variant, the new leaked image shows the handset in two additional colour variants. The image tweeted by @evleaks on Monday shows the Samsung Galaxy J1 (2016) smartphone in Gold and White colour variants. The design of the handset also fall in line with the models leaked in images previously. It is worth mentioning that the screen bezel seen in the image stay black in all the three colour variants. The smartphone is seen featuring a physical home button, along with a multi-window, and a back capacitive button on either side. At the back, the smartphone sports a camera at the centre with a LED flash and a speaker on either sides. Samsung is yet to announce the smartphone. The Samsung Galaxy J1 (2016)leaked in images last month as well...