DEPLOYDatabase

Incident · Recall

ADS Software Error May Cause Crash

Waymo LLC (Waymo) is recalling certain 5th Generation Automated Driving Systems (ADS) with software versions released prior to December 20, 2023. The ADS systems may inaccurately predict the movement of a towed vehicle. [NHTSA campaign 24E013000] source: https://www.nhtsa.gov/recalls?nhtsaId=24E013000

Occurred 2024-02-13 · Waymo

Machine-readable surfaces

Common questions

What happened in ADS Software Error May Cause Crash?
Waymo LLC (Waymo) is recalling certain 5th Generation Automated Driving Systems (ADS) with software versions released prior to December 20, 2023. The ADS systems may inaccurately predict the movement of a towed vehicle. [NHTSA campaign 24E013000] source: https://www.nhtsa.gov/recalls?nhtsaId=24E013000
When did this incident occur?
The incident is recorded as occurring on February 13, 2024 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in ADS Software Error May Cause Crash?
The incident is recorded as involving Waymo on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to ADS Software Error May Cause Crash?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of ADS Software Error May Cause Crash?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Claimed (not independently verified) · no sources on file · last reviewed 2026-06-25

Verification posture

Claimed (not independently verified)

Low confidence

Review state

Stable

Last reviewed 2026-06-25

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for ADS Software Error May Cause Crash.

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 c6af19ce-6abc-44a6-8e96-a4656cf83101