Zoox Robotaxi Collision and Software Recall in Las Vegas (2025)

Incident Summary

On April 8, 2025, an autonomous robotaxi operated by Zoox, a subsidiary of Amazon, collided with a passenger vehicle in Las Vegas, Nevada.^[1] The collision was attributed to a software defect that caused the vehicle’s autonomous driving system to inaccurately predict another vehicle’s movement trajectory.

Following the collision, Zoox paused all driverless operations and subsequently issued a recall of 270 vehicles. This was the company’s second recall of 2025; an earlier March recall covered 258 vehicles for a separate issue involving unexpected hard braking events.

Key Facts

• Date: April 8, 2025
• Location: Las Vegas, Nevada
• Cause: Software defect causing inaccurate prediction of another vehicle’s movement
• Recall scope: 270 vehicles recalled (second recall of 2025)
• Prior recall: 258 vehicles recalled in March 2025 for unexpected hard braking
• Response: Zoox paused all driverless operations

Threat Patterns Involved

Primary: Goal Drift — The autonomous driving system’s prediction model deviated from accurate trajectory forecasting, resulting in a collision that the system’s safety objectives were designed to prevent.

Significance

This incident highlights recurring software reliability challenges in autonomous vehicle deployment:

1. Prediction model failures — The collision stemmed from the autonomous system’s inability to accurately predict another vehicle’s movement, a core function of autonomous driving systems
2. Repeat safety issues — Two recalls within months of each other indicate persistent quality control challenges in Zoox’s autonomous driving software
3. Operational consequences — The complete pause of driverless operations demonstrates the cascading impact of a single software defect on commercial autonomous vehicle programs
4. Regulatory scrutiny — Multiple recalls increase NHTSA oversight of autonomous vehicle deployments