Keolis-operated Navya shuttle struck by truck in Las Vegas during first-day service

A Navya-built autonomous shuttle operated by Keolis was struck by a delivery truck in Las Vegas on November 8, 2017 while on its inaugural public run. Multiple news outlets and a subsequent NTSB investigation reported that the truck was backing up and was cited by police, no injuries were reported, and the collision caused only minor damage.

Keolis North America (operator) and Navya (vehicle manufacturer) · Incident Nov 8, 2017 · Indexed Jun 10, 2026 · 3 sources

The shuttle detected the backing truck and stopped, but the truck backed into the stationary autonomous vehicle.
What
A Navya-built autonomous shuttle operated by Keolis was struck by a delivery truck in Las Vegas on November 8, 2017 while on its inaugural public run.
Incident date
Nov 8, 2017
Who
Keolis North America (operator) and Navya (vehicle manufacturer)
Failure mode
Agentic Action Error
AI surface
Autonomous System
Severity
Low

What happened

On 2017-11-08 a Navya Arma autonomous shuttle operated by Keolis in downtown Las Vegas was involved in a low-speed collision with a delivery truck during its first day of public service. City and police statements said the truck was backing up and was cited for illegal backing; passengers and news reports said nobody was injured and damage was limited to the shuttle's front bumper. Federal transportation safety officials (NTSB) opened an investigation following the incident.

What broke inside the model

Failure path · mode profile · Agentic Action Error
  1. 01 · TriggerAn agent plans a multi-step task.
  2. 02 · Model stepIt chooses a wrong or destructive action.
  3. 03 · Control gapNo confirmation gate guards the write.
  4. 04 · FailureThe action commits to a system of record.
  5. 05 · ConsequenceData is changed or destroyed irreversibly.

A wrong action commits, and the step is written before anything can stop it.

The shuttle's sensors registered the truck and the vehicle came to a stop, but the truck then backed into the stationary shuttle. The failure was not a clear perception error by the shuttle according to contemporaneous statements; instead the incident exposed a breakdown in safe interaction between the autonomous vehicle's operational behavior and the actions of a human driver.

Public visibilityHigh
Regulatory exposureActive
Customer impactFew customers
Financial impactUnknown
Time to disclosureHours
  1. PressSelf-driving shuttle bus in crash on first daybbc.com
  2. PressSelf-driving shuttle in Las Vegas got into an accident on its first daycnbc.com
  3. PrimaryLow-Speed Collision Between Truck-Tractor and Autonomous Shuttle, Las Vegas, Nevada, November 8, 2017 (NTSB report PDF)ntsb.gov
Permalinkhttps://failureindex.ai/failures/keolis-operated-navya-shuttle-struck-truck
CitationAI Failure Index. "Keolis-operated Navya shuttle struck by truck in Las Vegas during first-day service" (FI-0422). Realm Labs. https://failureindex.ai/failures/keolis-operated-navya-shuttle-struck-truck (indexed Jun 10, 2026).
Share cardA branded image of this record for posts and slides.

Data fields CC-BY 4.0, prose citation permitted. Incident ID FI-0422. Full dataset at /data.

Note from Realm Labs, the Index steward

How Realm fits

Controls for this failure mode
  • Prism
  • OmniGuard
  • AgentRealm

This entry sits in the index's predictive wing: a system that scores, ranks, perceives, or steers rather than generates. Realm's runtime layer is built for the generative and agentic systems now moving into these same decision seats, where it watches a model's internal state and holds an unsupported claim or an unchecked action before it commits. The control gap on this record, an automated decision that reached people with no runtime check in front of it, is the same gap. The index keeps predictive failures on the record because the pattern carries straight into the systems shipping today.