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

  • Vision technology is bringing 2024 into sharp focus
    January 9, 2024
    What vision trends should we be looking out for? AI? Autonomous vehicles? Video analytics? Let’s ask the experts
  • TRW showcases driver assist systems
    June 5, 2014
    TRW Automotive demonstrated its driver assist systems (DAS) and outlined expected trends in sensor technologies during the company's recent bi-annual Ride and Drive event at the Hockenheimring in Germany. According to Andrew Whydell, TRW Electronics’ director of product planning, DAS has and will continue to be a focal point for the automotive industry as governments and industry bodies strive to reduce road fatalities worldwide. For example, the European New Car Assessment Program (EuroNCAP) and the Ins
  • Michigan fosters real-world testing of workzone ITS
    September 19, 2017
    Turning a ‘problem’ into ‘an opportunity’ is the mantra of just about every business book and Michigan Department of Transportation (MDoT) looks set to achieve that aim in Oakland County, where 29km (18 miles) of the I-75 needs to be reconstructed. Running north-northwest from Detroit, the I-75 carries around 170,000 vehicles per day but, being built in the 1970s, it now requires an additional lane in each direction and upgrading to the latest design and safety standards. Upgrading will be carried out in
  • Frequency changes threaten vehicle safety applications
    January 24, 2012
    The use of frequency spectrum at 5.9GHz for vehicle safety applications is at risk because of two draft bills currently before Congress. Here, we look at why and what’s being done to address the issue. In the US, the right of cooperative infrastructure to use frequency at 5.9GHz is under threat as a result of the proposal of two bills in Congress. The chronology of spectrum allocation for Dedicated Short- Range Communications (DSRC)-based Vehicle-to-Infrastructure (V2I) and Vehicle-to-Vehicle (V2V) safety a