Security and Safety

NTSB completes Las Vegas autonomous shuttle crash investigation

Posted on July 11, 2019

The shuttle was equipped with numerous sensing devices that provided a 360-degree view of the environment with hazard detection capabilities.
The shuttle was equipped with numerous sensing devices that provided a 360-degree view of the environment with hazard detection capabilities.Keolis

The National Transportation Safety Board released Highway Accident Brief 19/06, detailing the agency’s investigation of the Nov. 8, 2017, minor collision between a commercial truck and an autonomous shuttle in Las Vegas.

The truck driver’s actions and the autonomous vehicle attendant’s lack of easy access to a manual controller are cited in the probable cause for the collision. There were no injuries to the seven passengers and one attendant aboard the shuttle or to the driver of the truck. The accident caused minor damage to the lower left front of the shuttle’s body and a minor abrasion to the truck’s tire.

“The NTSB would normally not investigate a minor collision, but the involvement of a highly automated vehicle warranted having our investigators examine the circumstances surrounding the collision,” said Kris Poland, deputy director of the NTSB’s Office of Highway Safety. “We wanted to examine the process of introducing an autonomous shuttle onto public roads as well as the role of the operator, the vehicle manufacturer, and the city. The NTSB also examined the technology and the safety considerations that were in place at that time.”

(Detailed in this graphic are the locations of external sensors and communication devices that guided the autonomous vehicle involved in the Nov. 8, 2017, collision in Las Vegas. NTSB graphic adapted from Navya’s owner’s manual)

The autonomous shuttle was a two-axle, battery-powered, test vehicle designed primarily for autonomous operation and therefore did not have a steering wheel, brake pedal, or accelerator pedal. The shuttle allowed for manual operation using a hand-held controller. The shuttle could operate autonomously only on a predetermined route that had been fully mapped. The route was planned by Keolis, Navya, and AAA with input from the city. Navya and Keolis had the required state and federal approval to test autonomous shuttle operations on public roads.

The collision happened after the shuttle turned from Carson Avenue onto South 6th Street, where the truck was backing into an alley. The truck driver said he saw the shuttle turn onto 6th Street and assumed it would stop a “reasonable” distance from the truck. According to Navya’s incident report, the shuttle’s sensor system detected the truck at 147.6 feet and tracked it continuously as it backed up. Programmed to stop 9.8 feet from any obstacle, the shuttle began to decelerate when it was 98.4 feet from the truck. When the shuttle was 10.2 feet from the truck and nearly stopped, the attendant pressed one of the emergency stop buttons. The attendant and passengers waved to gain the truck driver’s attention but 11 seconds after the shuttle stopped, the right front tire of the slow-moving truck struck the shuttle.

The shuttle was equipped with numerous sensing devices that provided a 360-degree view of the environment with hazard detection capabilities. Some of the sensing devices included eight light detection and ranging (lidar) sensors, two stereoscopic cameras, and a differential global positioning system.

The shuttle was also equipped with a dedicated short-range communication system and a long-term evolution antenna that communicated with traffic signals along the route. Navya could monitor the shuttle’s performance in real time from its control center in Lyon, France. The shuttle was equipped with a Lytx DriveCam monitoring and recording device that tracked driving metrics and recorded telematic and visual information triggered by critical events.

Prior to the collision the hand-held controller for manual operation was stored in an enclosed space at one end of the passenger compartment and the attendant did not retrieve the controller during the event. Since the accident, Keolis implemented a new policy to make the controller more accessible, allowing attendants to remove the controller from storage at the start of a trip and keep the controller available throughout a trip.

The full highway accident brief is available here.

View comments or post a comment on this story. (0 Comments)

More News

HART, lawmakers propose bills aimed at protecting transit workers

SB 1416 and HB 951 both seek to curb violent threats against uniformed public servants in the workplace.

NY Gov. announces 3-year ban of sex offenders from transit

This proposal is in response to a number of recent MTA incidents involving repeat sex offenders.

FRA launches web portal for public to report blocked railroad crossings

The agency expects it will take an average of three minutes for users to complete the report.

London testing electric bus sounds to improve road safety

When travelling above 12 mph, the bus will make enough noise that an alert is unnecessary.

Metro-North, LIRR to screen employees in 'safety-sensitive' areas

NTSB recommendations developed from investigation into five accidents that killed six people and injured 126 more.

See More News

Post a Comment

Post Comment

Comments (0)

More From The World's Largest Fleet Publisher

Automotive Fleet

The Car and truck fleet and leasing management magazine

Business Fleet

managing 10-50 company vehicles

Fleet Financials

Executive vehicle management

Government Fleet

managing public sector vehicles & equipment


Work Truck Magazine

The number 1 resource for vocational truck fleets

Schoolbus Fleet

Serving school transportation professionals in the U.S. and Canada

LCT Magazine

Global Resource For Limousine and Bus Transportation