Zoox robotaxi collides with passenger car in Las Vegas
An unoccupied Zoox robotaxi collided with a passenger car in Las Vegas on April 8, 2025, after mispredicting the car's movement. Zoox paused operations and recalled software.
Key facts
- On April 8, 2025, an unoccupied Zoox robotaxi operating autonomously in Las Vegas collided with a passenger car; no one was injured.
- Zoox said the car approached from a driveway and then stopped, while the robotaxi had predicted it would continue into its lane.
- Zoox told NHTSA the prediction problem occurred only at speeds above 40 mph.
- Zoox paused driverless operations the same day and filed recall 25E-029 for 270 vehicles on May 1, 2025.
- Both vehicles sustained minor damage, according to TechCrunch.
What happened
On April 8, 2025, a Zoox robotaxi with no one on board was driving autonomously in Las Vegas when a passenger car approached its lane from a commercial driveway. According to Zoox’s account reported by TechCrunch, the robotaxi predicted the car would keep moving into the road, so it slowed and steered to the right. The car instead stopped and yielded, remaining in the shoulder lane.
Zoox said the robotaxi braked hard but that contact could not be avoided. No injuries were reported, and TechCrunch reported minor damage to both vehicles.
The system involved
Zoox, an Amazon subsidiary, tests purpose-built robotaxis without steering wheels or pedals in Las Vegas and San Francisco, along with retrofitted test vehicles carrying safety operators. In its recall report, Zoox said that at speeds above 40 mph, when another vehicle edged out from a perpendicular driveway toward the Zoox vehicle’s lane and then halted, the software could make an inaccurately confident prediction that the vehicle would proceed, and plan a path that left it unable to respond in time.
Investigation and response
Zoox paused all driverless operations on April 8, 2025, for an internal review. On April 10 it resumed driverless operations in areas with maximum speeds below 40 mph, excluding higher-speed Las Vegas routes. It confirmed the root cause on April 11, reported the crash to NHTSA under the Standing General Order on April 13, and released updated software to its vehicles on April 16 and 17, after which operations resumed everywhere.
On May 1, 2025, Zoox filed Part 573 recall report 25E-029 covering software on 270 vehicles. TechCrunch noted that Zoox had recalled 258 vehicles in March 2025 over unexpected hard braking.
A second incident followed on May 8, 2025, in San Francisco: an e-scooter rider struck a stopped, unoccupied Zoox robotaxi and fell beside it, and the robotaxi then began to move without touching the rider, according to Zoox’s recall report 25E037. Zoox again paused driverless operations and deployed updated software on May 21, 2025.
What is not established
The description of how the two vehicles moved before the collision comes from Zoox; no independent finding on fault was found in the sources opened for this entry.
Outcomes
- Zoox paused all driverless operations on April 8, 2025, and resumed fully after releasing updated software on April 16 and 17, 2025.
- On May 1, 2025, Zoox filed recall 25E-029 covering automated driving software on 270 vehicles.
- Zoox filed a further recall, 25E037, on May 22, 2025, after a separate May 8 incident in San Francisco involving an e-scooter rider.
Sources
- Part 573 Safety Recall Report 25E-029NHTSA, May 1, 2025
- Amazon-owned Zoox issues recall following robotaxi crashTechCrunch, May 6, 2025
- Part 573 Safety Recall Report 25E037NHTSA, May 22, 2025