10-10-2016 -- On a foggy Monday morning in Silicon Valley this week, I took a ride in Google’s self-driving car and nothing happened.

That’s a big deal.

That’s because the company announced its self-driving car project, which was created in 2009, has racked up over two million miles of driving experience. It’s a significant marker for Google — no other company has that many miles of fully self-driving experience.

But that landmark actually doesn’t mean much on its own, because the real milestone is how well the technology has developed in that time.

“It’s a nice round number, but it’s really about the quality of those miles,” said Google’s head of self-driving tech Dmitri Dolgov. “We’re building a driver,” he later added.

Mistakes are still made and collisions happen — Google has been involved in 14 real ones so far, 13 of which were caused by other drivers — but the ride we took in its self-driving car was uneventful, which is the goal the company has long been aiming for consistently.

My ride started like your basic self-driving car test drive. A Lexus equipped with Google’s proprietary sensors and cameras pulled up to the front of its Mountain View headquarters building, with Dolgov in the driver’s seat. Another engineer sat in the passenger seat manning a laptop that was running the self-driving software. 

Read the rest of the story HERE.

3-14-2016, Reuters -- The top U.S. auto safety regulator said on Thursday the agency is seeking additional details of a recent crash of an Alphabet Inc Google self-driving car in California.

The National Highway Traffic Safety Administration (NHTSA) is collecting information to get a "more detailed exploration of what exactly happened," NHTSA chief Mark Rosekind told Reuters on the sidelines of an event on highway safety.

A Google self-driving car struck a municipal bus in Mountain View, Calif. in a minor crash on Feb. 14, and the technology company said it bears "some responsibility" for the incident in what may be the first crash that was the fault of the self-driving vehicle.

Rosekind said he spoke to Google officials on Wednesday and the company has been "very forthcoming" in answering requests for details on the crash. "We have to see what's going on," Rosekind said.

A Google spokesman confirmed NHTSA has asked for more information and the company plans to discuss the crash with regulators.

U.S. safety officials said in January they are working on new guidance on self-driving vehicles that they hope to release by July. Rosekind said understanding the Google car crash is important in that process.

"One of the lessons learned would be: there's an incident, how do you make that sure that (the issue) ends up getting corrected and there is quality assurance to make sure it effectively changes what happened," Rosekind said.

Google said last week it made changes to its software after the crash to avoid future incidents. A U.S. Senate panel will hold a hearing on Tuesday on the future of autonomous vehicles that will include the director of Google's self-driving car program.

Last month, NHTSA said the artificial intelligence system piloting a self-driving Google car could be considered the driver under federal law, a major step toward winning approval for autonomous vehicles on the roads.

The California Department of Motor Vehicles said last week it is reviewing the Google crash.

California rules say the state could "suspend or revoke the manufacturer’s testing permit for any act or omission which the department finds makes the conduct of autonomous vehicle testing on public roads an unreasonable risk to the public," the agency said.

Read the rest here: http://www.reuters.com/article/us-google-selfdrivingcar-idUSKCN0WC1YS