Skip to main content

Autonomous car data released

California’s Autonomous Vehicle Testing Regulations require every manufacturer authorised to test autonomous vehicles (AV) on public roads to submit an annual report summarising the disengagements, or deactivation of the autonomous mode, of the technology during testing. Eleven manufacturers are currently testing autonomous vehicles on the state’s roads, seven of which (VW/Audi, Mercedes Benz, Google, Delphi Automotive, Tesla Motors, Bosch, and Nissan) were required to submit their first disengagement re
January 14, 2016 Read time: 3 mins
California’s Autonomous Vehicle Testing Regulations require every manufacturer authorised to test autonomous vehicles (AV) on public roads to submit an annual report summarising the disengagements, or deactivation of the autonomous mode, of the technology during testing.

Eleven manufacturers are currently testing autonomous vehicles on the state’s roads, seven of which (VW/2125 Audi, 1685 Mercedes Benz, 1691 Google, 7207 Delphi Automotive, 597 Tesla Motors, 311 Bosch, and 838 Nissan) were required to submit their first disengagement reports by 1 January 2016.  

Bosch, which tested two vehicles over 942 miles, reported 625 disengagements, but claimed all were ‘planned technology tests’.

Delphi’s two cars drove a total of 16,662 miles and reported around 397 disengagements. 28 of these cases had been precautionary, because of nearby pedestrians or cyclists, and 212 had been due to difficulties making out road markings or traffic lights

In 1,485 miles, Nissan’s four vehicles recorded 106 disengagements, mainly to avoid being rear-ended or rear-ending another vehicle, or due to AV system failure.

Mercedes’ two vehicles reported 529 disengagements in 1,379 miles, mainly because the driver was uncomfortable with the software’s behaviour

Tesla reported no disengagements.

Volkswagen tested two vehicles, which drove 14,945 miles and reported 260 disengagements due to watchdog error or ‘basic vehicle requirements not being satisfied’.

Google’s fleet of cars drove a total of 424,331 miles on public roads, reporting 272 disengagements where the vehicle’s software detected a failure and a further 69 where the driver took control of the vehicle because he perceived a safety threat.

Non-profit public interest group Consumer Watchdog called on Google to release any videos of the incidents, as well as technical data gathered immediately preceding the disengagements.

“The DMV got it exactly right and is putting our safety first,” said privacy project director John M. Simpson. “How can Google propose a car with no steering wheel, brakes or driver when its own tests show that over 15 months the robot technology failed and handed control to the driver 272 times and a test driver felt compelled to intervene 69 times?

“Release of the disengagement report was a positive step, but Google should also make public any video it has of the disengagement incidents, as well as any technical data it collected so we can fully understand what went wrong as it uses our public roads as its private laboratory,” Simpson said.

In its report, Google claims that the number of autonomous miles being driven between manual control disengagements is increasing steadily over time, from 785 miles per disengagement in the fourth quarter of 2014 to 5,218 miles per disengagement in the fourth quarter of 2015.

Four other manufacturers (Cruise Automation, 1731 BMW, 1683 Honda, and 278 Ford) are due to submit their first disengagement report by the beginning of January 2017.

For more information on companies in this article

Related Content

  • 5G or not 5G?
    April 16, 2019
    Just a few years ago, there was only one solution in terms of communications protocols for delivering vehicle connectivity. Now, road operators and vehicle manufacturers face choices – including a moral choice, perhaps. Jason Barnes looks at the current state of play There is a debate raging in the ITS world over future communications protocols. Asfinag, Austria’s national strategic road operator, has announced it will from 2020 be using ITS-G5 to support cooperative ITS (C-ITS) applications (‘First thin
  • Developing a wireless cooperative traffic management system
    March 14, 2012
    The use by MDOT of 90-foot concrete poles on which to mount CCTV equipment reduces the number of poles needed to monitor a given area and incidences of occlusion
  • Assessing the potential of in-vehicle enforcement systems
    December 4, 2012
    Jason Barnes considers the social and ethical ramifications of using in-vehicle safety technologies to fulfil enforcement functions. Although policy documents often imply close correlation between enforcement, compliance and safety – in part, as a counter to accusations that enforcement is rather more concerned with revenue generation – there is a noticeable reluctance among policy makers and auto manufacturers to exploit in-vehicle safety systems for enforcement applications. From a technical perspective t
  • Iteris reports strong 2014 growth
    September 4, 2014
    Iteris has reported financial results for its fiscal fourth quarter and full year ended31 March 2014, indicating total revenues in the fourth quarter of 2014 increased 11 per cent to US$17.6 million compared to US$15.9 million in the same quarter last year. This was primarily driven by a 25 per cent increase in roadway sensors. iPerform revenues were also up 14 per cent, while transportation systems revenues were down one per cent. Total revenues in 2014 increased 11 per cent to US$68.2 million compared to