Waymo software recall for illegally passing stopped school buses
Waymo filed a voluntary software recall (reported as covering more than 3,000 robotaxis) after its driverless cars illegally passed stopped school buses: Austin ISD documented 19 incidents, Atlanta schools at least six, and NHTSA opened an investigation in October 2025; Austin said five more incidents occurred after an earlier fix.
The damage was public. The root cause was preventable.
Waymo filed a voluntary software recall (reported as covering more than 3,000 robotaxis) after its driverless cars illegally passed stopped school buses: Austin ISD documented 19 incidents, Atlanta schools at least six, and NHTSA opened an investigation in October 2025; Austin said five more incidents occurred after an earlier fix.
What the software actually got wrong
Waymo said it identified a software issue in which its vehicles may initially slow or stop for a school bus with flashing lights and an extended stop arm but then keep going; it updated its fleet software and filed the recall for the way vehicles slow and stop in those scenarios.
Waymo said it identified a software issue in which...
Waymo said it identified a software issue in which its vehicles may initially slow or stop for a school bus with flashing lights and an extended stop arm but then keep going
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
It updated its fleet software and filed the recall...
it updated its fleet software and filed the recall for the way vehicles slow and stop in those scenarios
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.