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

March 9, 2016, Governing.com -- The storm that rolled through Ann Arbor, Mich., in late November brought nine inches of snow and an experimental opportunity too good to pass up. A team of Ford engineers working to develop self-driving vehicles decided it would be a good time to put their modified Ford Fusion sedans to the test.

Snow, like rain, can be especially tricky for automated vehicles. Precipitation makes it harder for driverless cars to know where they are. Their cameras can’t see lines on snow-covered pavement or in the reflections of puddles. Falling precipitation interferes with radar. Piles of snow make finding the curbs and road edges harder, even for the cars’ laser-powered mapping devices. On top of that, snow is something of a novelty for self-driving cars. Most of them have been confined to sunny locales in states like California, Nevada and Texas, where rain and snow are rarer.

So the Ford team jumped at the chance to test their vehicles in the Michigan winter. Rather than heading to Ford’s proving grounds in Dearborn, they went to Mcity, a 32-acre test track in north Ann Arbor. It’s a shared track that’s operated by the University of Michigan and used by automakers and the state transportation department to try out autonomous and connected cars. Mcity includes elements you wouldn’t expect to find on most test tracks, things like stoplights that broadcast information to vehicles, a railroad crossing, a bus stop, highway on-ramps and gantries, a small hill, gravel roads, sidewalk crossings, stop signs, a simulated tree canopy and overpass, roundabouts, vandalized traffic signs, and a mockup of downtown city blocks.