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."

Related Content

  • July 17, 2012
    Progress towards a pan-European cooperative infrastructure
    Kallistratos Dionelis, General Secretary of ASECAP, makes the case for a lightly regulated, staged progression towards a pan-European cooperative infrastructure environment, the achievement of which should look to engender cooperation between the public and private sectors. Such an approach, he says, is the only real path to success.
  • December 2, 2013
    Auto safety initiative seeks to reduce driver errors
    A push by the US National Highway Traffic Safety Administration to use technology to reduce traffic fatalities aims to keep drunk drivers off the roads by using in-vehicle technology that immobilises their cars. They are pushing for systems that prevent drivers from starting their cars, help cars avoid collisions and prevent vehicles from starting if the occupants don’t wear seat belts. "Ninety per cent of all crashes have an element of human error," NHTSA administrator David Strickland said. "We really
  • February 7, 2018
    Byton partners with Aurora to bring Level 4 AVs to market
    Byton will incorporate Aurora’s Level 4 (L4) autonomous-driving vehicle capabilities into its vehicles in a partnership which aims to bring L4 and Level 5 cars to market. The two-year project in California will also explore the use of Aurora’s system in Byton’s series production vehicles. Dr. Carsten Breitfeld, CEO and co-founder of Byton, said: "Byton is designed for the age of autonomous driving. We are pleased to partner with Aurora, as Aurora is supremely focused on a mission to deliver the benefits of
  • January 30, 2012
    In-vehicle systems as enforcement enablers?
    From an enforcement perspective at least, Toyota's recent recalls over problems with accelerator pedal assemblies had a positive outcome in that for the first time a major motor manufacturer outside of the US acknowledged publicly what many have known or suspected for quite a while: that the capability exists within certain car companies to extract data from a vehicle onboard unit which can be used to help ascertain, if not prove outright, just what was happening in the vital seconds up to an accident or cr