Multi-Vehicle Crash in Mountain View California (March 28, 2018) - - PowerPoint PPT Presentation

multi vehicle crash in mountain view california march 28
SMART_READER_LITE
LIVE PREVIEW

Multi-Vehicle Crash in Mountain View California (March 28, 2018) - - PowerPoint PPT Presentation

Multi-Vehicle Crash in Mountain View California (March 28, 2018) Talking TIM Webinar (May 2020) Robert J. Molloy, PhD. Presentation Overview Automation in theory Vehicle automation The crashes The safety areas Actions


slide-1
SLIDE 1

Multi-Vehicle Crash in Mountain View California (March 28, 2018)

Talking TIM Webinar (May 2020) Robert J. Molloy, PhD.

slide-2
SLIDE 2

Presentation Overview

  • Automation in theory
  • Vehicle automation
  • The crashes
  • The safety areas
  • Actions needed

2

slide-3
SLIDE 3

The Theory

Automation can eliminate human error by eliminating the human from the loop

slide-4
SLIDE 4

Crashes Involving Driver Error >90%

slide-5
SLIDE 5

The Reality

Automation can significantly increase productivity, efficiency, reliability, throughput, and safety but the downside . . .

slide-6
SLIDE 6

The Downsides

“In their efforts to compensate for the unreliability of human performance, the designers of automated control systems have unwittingly created

  • pportunities for new error types that can be even

more serious than those they were seeking to avoid.”

  • Prof. James Reason, University of Manchester (UK)

6

slide-7
SLIDE 7

Vehicle Automation

7

slide-8
SLIDE 8

Levels of Automation

8

No Automation Driver Assistance Conditional Automation High Automation Full Automation Partial Automation

Supervise automation Maintain awareness Understand limitations Intervene when needed

slide-9
SLIDE 9

Autopilot Description

9

  • Monitors travel path
  • Maintains set cruise speed
  • Maintains vehicle’s position in travel lane
  • Brakes when detecting slower-moving vehicles ahead
  • Decelerates and follows vehicles ahead at a

predetermined following interval

slide-10
SLIDE 10

The Crashes

10

slide-11
SLIDE 11

Mountain View

11

  • Friday, March 23, 2018
  • 9:27 a.m.
  • Mountain View, California
  • US-101 / SR-85 interchange
  • 2017 Tesla Model X SUV
  • 38-year-old driver
  • Partial automation “Autopilot”

engaged

slide-12
SLIDE 12

Crash Sequence

12

SR-85 HOV exit lane US-101 south lanes

Crash attenuator was collapsed and nonoperational prior to the crash

N S

Source: Caltrans

slide-13
SLIDE 13

Crash Sequence

13

Time to crash: 7.9 seconds Speed: 64.3 mph Lead vehicle: 83.7 feet Distance to crash: 748 feet Lead vehicle Crash attenuator

N S

slide-14
SLIDE 14

Crash Sequence

14

Time to crash: 5.9 seconds Steering: 5.6 degrees left Speed: 64.1 mph Lead vehicle: 82 feet Distance to crash: 560 feet Indication: Hands-off steering wheel Lead vehicle Crash attenuator

N S

slide-15
SLIDE 15

Crash Sequence

15

Time to crash: 3.9 seconds Speed: 61.9 mph Lead vehicle: None detected Distance to crash: 375 feet Vehicle begins to accelerate Hands-off steering wheel indicated Lead vehicle (no longer followed) Crash attenuator

N S

slide-16
SLIDE 16

Crash Sequence

Impact speed: 70.8 mph

slide-17
SLIDE 17

Crash Sequence

17

Source: S. Engleman

slide-18
SLIDE 18

Other NTSB Investigations

18

Lessons learned from three other Tesla crashes were incorporated into the Mountain View crash investigation:

  • Williston, Florida
  • Delray Beach, Florida
  • Culver City, California
slide-19
SLIDE 19

Williston, Florida (May 7, 2016)

19

slide-20
SLIDE 20

Delray Beach, Florida (March 1, 2019)

20

slide-21
SLIDE 21

Culver City, California (January 22, 2018)

21

N S Source: CHP

slide-22
SLIDE 22

The Safety Issues

22 22

slide-23
SLIDE 23

Autopilot Performance

23

  • Lane markings were worn
  • Autosteer vision system likely

lost lane line prediction

  • Identified stronger lane line
  • Steering movement likely due

to vision system limitations

slide-24
SLIDE 24

Crash Attenuator Performance

24 24

Barricade and cones placed in advance

  • f attenuator prior to crash

Source: CHP Barricade Damaged crash attenuator

  • Damaged 11 days earlier
  • Prius collision
  • Driver survived
  • CHP did not notify CalTrans
  • CalTrans repair not timely
slide-25
SLIDE 25

Automation Issues

  • Operational design domain (ODD)
  • Monitoring driver engagement
  • Collision avoidance system (CAS)

25

slide-26
SLIDE 26

Operational Design Domain

  • Conditions in which an automated system is designed

to operate

  • Geographic location, roadway type and markings,

speed range, weather conditions

  • ODD constraints are designed to reduce the effect of

Level 2 limitations

26

slide-27
SLIDE 27

ODD Constraints

  • Autopilot, stated in vehicle manual, is
  • Not for use on city streets, in constantly changing traffic

conditions, on winding roads with sharp curves

  • For use only on divided highways with limited access
  • The system allows a driver to use Autopilot outside its ODD
  • Level 2 system limitations are industry-wide

27

slide-28
SLIDE 28

Geographic ODD: Mountain View

  • Crash location
  • Highway with center median divider
  • Limited access (no cross-traffic)
  • Major interchange (changing traffic conditions)
  • Tesla stated ODD does not apply to Level 2 systems

28

slide-29
SLIDE 29

Geographic ODD: Williston and Delray Beach

  • Williston crash location
  • Outside ODD of Autopilot
  • Delray Beach crash location
  • Highway with center median divider
  • Not limited access (has cross-traffic)
  • Outside ODD of Autopilot

29

slide-30
SLIDE 30

Monitoring Driver Engagement

  • Driver monitors environment in Level 2 systems
  • Tesla stated that Autopilot can be used on undivided roads

with an attentive driver

  • Risk of automation complacency and misuse
  • Tesla’s method of monitoring driver engagement
  • Driver-applied steering wheel torque
  • System provides series of warnings to driver (visual,

3 stages of auditory warnings)

30

slide-31
SLIDE 31

Driver Engagement: Mountain View

  • The crash trip lasted 28.5 minutes
  • Autopilot was engaged for the last nearly 19 minutes

31

  • Two visual warnings; one auditory warning
  • Lack of responsiveness indicates distraction and
  • verreliance on automation
slide-32
SLIDE 32

Driver Engagement: Other Level 2 Crashes

  • Williston and Delray Beach, Florida; Culver City, California
  • Driver-applied steering wheel torque not detected at time
  • f impact
  • Prolonged inattentiveness by drivers
  • Drivers were ineffective monitors
  • Humans are poor monitors of automation
  • Monitoring of steering wheel torque is a poor surrogate

measure of driver engagement

32

slide-33
SLIDE 33

Automation: The Path Forward

33

slide-34
SLIDE 34

Needed ODD Improvements

  • Manufacturers should include system safeguards to

limit the use of Level 2 systems to conditions for which they are designed (H-17-41)

  • NHTSA should verify that manufacturers are

incorporating the safeguards (H-17-38)

  • Lack of guidance on identifying ODD

34

slide-35
SLIDE 35

Needed Driver Monitoring Improvements

  • Manufacturers should implement more effective means
  • f monitoring driver engagement when using Level 2
  • NHTSA and SAE should develop performance standards

for driver monitoring systems to address automation complacency

  • An engaged driver remains a critical component even

with advanced driver assistance systems

35

slide-36
SLIDE 36

Summary

36

  • Technology offers hope
  • Automation must consider the human
  • Infrastructure must support the automation
slide-37
SLIDE 37

Robert Molloy, PhD. Director Cell 202-320-6294 Email molloyr@ntsb.gov