Incident · Collision
Navya autonomous shuttle collided with truck in Las Vegas on first day
A Navya autonomous shuttle in Las Vegas was involved in a collision with a human-driven truck on its first day of service. The semi-truck backed into the stationary shuttle, which had stopped correctly. No injuries were reported, but the incident highlighted challenges of deploying autonomous vehicles in mixed traffic.
Occurred 2017-11-08 · Navya
How to read this record
Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.Machine-readable surfaces
- Markdown mirror: /incidents/collision-2017-11-08-navya.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/88ae7449-1b64-44dd-8d94-677bf266dead
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Status history
- Active · 2026-07-03 · agent:depth
Common questions
What happened in Navya autonomous shuttle collided with truck in Las Vegas on first day?
When did this incident occur?
Who was involved in Navya autonomous shuttle collided with truck in Las Vegas on first day?
Has anyone responded to Navya autonomous shuttle collided with truck in Las Vegas on first day?
What is the current status of Navya autonomous shuttle collided with truck in Las Vegas on first day?
Methodology: Verified · 1 source (no primary) · last reviewed 2026-07-14
Verification posture
Verified
Medium confidence
Review state
Stable
Last reviewed 2026-07-14
Sources by quality tier
- 1
- secondary-established-publication
- Established publication
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Navya autonomous shuttle collided with truck in Las Vegas on first day.Deploy Watch
Track this incident.
We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.
Canonical ID 88ae7449-1b64-44dd-8d94-677bf266dead