Google’s car was attempting to make a right-hand turn on red, and moved to the right side of a wide lane on El Camino Real to pass traffic stopped at the light. But as Google’s car neared the intersection of Castro Street, its path was blocked by sandbags around a storm drain, according to a report Google filed with the California DMV.

AD

Google’s car tried to go around the sandbags by cutting into the line of vehicles on the left side of the lane. Instead, it struck a metal piece connecting the two halves of an accordion-style bus, according to a Santa Clara Valley Transportation Authority spokeswoman. Google said its car was going less than 2 mph and the bus was moving at 15 mph. Both parties said there were no injuries and described the crash as minor.

AD

The 15 passengers on the bus were transferred to another bus following the accident.

Google characterized the crash as a misunderstanding and a learning experience, saying its cars will learn that large vehicles are less likely to yield than other types of vehicles.

AD

“We hope to handle situations like this more gracefully in the future,” Google said in a monthly report. “We clearly bear some responsibility, because if our car hadn’t moved there wouldn’t have been a collision.”

The accident highlights the imperfections of the current self-driving technology, which is widely seen as a promising solution to the thousands of lives lost each year on roadways. While many in the tech and auto industry have circled 2020 as a roll-out date for self-driving vehicles, others have warned that it will likely take longer.

Google’s self-driving cars have two employees present, and they are trained to intervene to prevent crashes. Earlier this year, Google revealed that 13 times over a 14-month span, its drivers had to intervene to prevent crashes.

In the Feb. 14 crash, Google said its test driver thought the bus would slow or stop so the Google car could go ahead of it.