Skip to main content

US regulator ‘paves the way for Google’s self-driving car’

A letter to Google, the US federal transport regulator, National Highway Traffic Safety Administration (NHTSA), appears to pave the way for self-driving cars, but adds the proviso that the rule-making could take some time. Google had requested clarification of a number of provisions in the Federal Motor Vehicle Safety Standards (FMVSSs) as they apply to Google’s described design for self-driving vehicles (SDVs). “If no human occupant of the vehicle can actually drive the vehicle, it is more reasonable
February 11, 2016 Read time: 4 mins
A letter to Google, the US federal transport regulator, 834 National Highway Traffic Safety Administration (NHTSA), appears to pave the way for self-driving cars, but adds the proviso that the rule-making could take some time.

Google had requested clarification of a number of provisions in the Federal Motor Vehicle Safety Standards (FMVSSs) as they apply to Google’s described design for self-driving vehicles (SDVs).

“If no human occupant of the vehicle can actually drive the vehicle, it is more reasonable to identify the driver as whatever (as opposed to whoever) is doing the driving,” Paul A. Hemmersbaugh, NHTSA chief counsel said in the letter to Chris Urmson, director of Google’s self-driving car project.  “In this instance, an item of motor vehicle equipment, the SDS, is actually driving the vehicle.”

The NHTSA’s current 49 CFR 571.3 rule defines a driver as “the occupant of a motor vehicle seated immediately behind the steering control system.”

According to Google, its SDVs are fully autonomous motor vehicles, i.e., vehicles whose operations are controlled exclusively by a self-driving system (SDS).  The SDS is an artificial-intelligence driver, which is a computer designed into the motor vehicle itself that controls all aspects of driving by perceiving its environment and responding to it. Google believes that the vehicles have no need for a human driver and has asked the NHTSA for advice on the interpretation of provisions in the Federal Motor Vehicle Safety Standards (FMVSSs) for the operation of the new cars.

Google's description of its proposed vehicles corresponds to Level 4 Full Self-Driving Automation defined by a May 2013 preliminary policy statement of the NHTSA on automated vehicles, according to Hemmersbaugh.

According to that Statement, a Level 4 vehicle “is designed to perform all safety-critical driving functions and monitor roadway conditions for an entire trip. Such a design anticipates that the driver will provide destination or navigation input, but is not expected to be available for control at any time during the trip. This includes both occupied and unoccupied vehicles. By design, safe operation rests solely on the automated vehicle system.”

“In essence, Google seeks to produce a vehicle that contains L4 automated driving capabilities, and removes conventional driver controls and interfaces (like a steering wheel, throttle pedal, and brake pedal, among many other things),” said Hemmersbaugh.

However, the NHTSA is wrong to say the artificial intelligence guiding an autonomous robot car counts as the driver, Consumer Watchdog said, adding that Google's own test data demonstrates the need for a human driver who can take control when necessary.

"Google says its robot technology failed and handed over control to a human test driver 272 times and the driver was scared enough to take control 69 times," said John M. Simpson, Consumer Watchdog's privacy project director. "The robot cars simply cannot reliably deal with everyday real traffic situations. Without a driver, who do you call when the robots fail?"

Consumer Watchdog reiterated its support for regulations proposed by the California Department of Motor Vehicles covering the general deployment of autonomous robot cars on the state's highways.

"The DMV would require a licensed driver behind the wheel," Simpson noted. "If you really care about the public's safety, that's the only way to go."

Commenting on NHTSA's interpretation that the robot technology can count as a driver, Anthony Foxx, Secretary of Transportation said, "We are taking great care to embrace innovations that can boost safety and improve efficiency on our roadways. Our interpretation that the self-driving computer system of a car could, in fact, be a driver is significant. But the burden remains on self-driving car manufacturers to prove that their vehicles meet rigorous federal safety standards."

For more information on companies in this article

Related Content

  • When weather warnings get hyperlocal
    August 24, 2016
    David Crawford looks at new technologies to cope with the age-old problem of driving in bad weather. On the 10-year average, between 2005 and 2014 bad weather contributed to more than 1.5 million vehicle crashes in the US each year, resulting in more than 800,000 injuries and 7,400 deaths. These were the findings of analysis by Booz Allen Hamilton of NHTSA data which concluded that the loss of life, hospital treatment and damage to assets costs an annual average of $42bn.
  • IBTTA seeks transportation innovation
    December 16, 2016
    IBTTA’s Patrick Jones contemplates the need for, sources of and constraints on transportation innovation. For years now, visionary thinkers and doers in the highway transportation community have been laser-focused on the role of innovation in addressing the most pressing mobility challenges.
  • Tattile launches Axle Counter
    October 17, 2019
    Tattile has launched an automatic system for determining the number of axles on a vehicle for tolling solutions. Axle Counter records the axles of any vehicle - driving at speeds up to 180km/h - in order to help toll operators allocate the correct charges.
  • Automation and connectivity on stage in Brussels
    September 21, 2015
    Automation and connectivity take centre stage in Brussels during a series of events to be held in the city during the week of 20-23 October. The week starts off with the FIA Policy Conference, Driving change, connecting mobility, on 20 October. FIA Region will host policymakers and stakeholders to discuss new trends in mobility, while also engaging with how these changes will impact areas such as data protection and liability. On 21 October, the plenary meeting of the iMobility Forum takes place unde