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

  • Navya unveils six seated autonomous taxi
    December 5, 2017
    Navya has launched its Autonom Cab (AC) to address the challenges urban populations face when travelling in and around cities. The cab, designed to be completely autonomous, comes without a cockpit, steering wheel or pedals and can carry up to six passengers.
  • US economic stimulus package highlights ITS technology
    July 17, 2012
    US Secretary of Transportation Ray LaHood talks to ITS International about economic stimulus funding and the absolute need to maintain and increase the use of technology in transportation. Of the total of $787 billion of funding announced under the American Recovery and Reinvestment Act (ARRA), the economic stimulus package which was signed into law by US President Barack Obama on 17 February 2009, $48.1 billion will go to the US Department of Transportation (USDOT). Of that, $27.5 billion is for highway in
  • Growing world market for night vision and driver monitoring systems
    August 15, 2014
    MarketsandMarkets’ latest report, Night Vision System (NVS) and Driver Monitoring System (DMS) Market for Passenger Cars - by Geography - Trends and Forecasts 2014-2019 classifies and defines the automotive night vision and driver monitoring systems market in terms of volume and value. The report highlights potential growth opportunities in the coming years as well as covers review of the - market drivers, restraints, growth indicators, challenges, legislation trends, market dynamics, competitive landscape,
  • Deadlines approach for Europe’s automatic crash alert system
    September 15, 2016
    The EU-co-funded I_ HeERO (Infrastructure_ Harmonised eCall European Pilot) project is working to ensure the readiness of national networks of call centres - known as public safety answering posts (PSAPs) - to deal with automated crash alerts arriving via the continent-wide 112 emergency phone number. Following on from its HeERO and HeERO2 pre-deployment predecessors, which enjoyed €16m (US$17.76m) in EU funding, the new initiative runs from 1 January 2015 to 31 December 2017. It has €30.9 million (US$34.