Incident sheet · SIG-5879 · /enterprise-ai
- Signal
- SIG-5879
- System
- ENT · Enterprise AI
- Filed
- Read
- 2 min · 421 words
- Severity
- Routine
NHTSA opens recall query into Waymo after robotaxis still pass stopped school buses
NHTSA opened a recall query on November 6 into Waymo after robotaxis kept passing stopped school buses with flashing lights, months after a software fix deployed on November 17, 2025.

Event log
- NHTSA opened a recall query into Waymo on November 6 over continued illegal passing of stopped school buses.
- A majority of reported incidents occurred after Waymo's software fix reached all affected vehicles on November 17, 2025.
- The initial ODI investigation opened in October 2025 after footage showed a Waymo vehicle maneuvering around a school bus unloading children in Atlanta.
- Austin Independent School District reported at least five similar incidents in a letter filed with NHTSA.
Federal regulators opened a fresh probe into Waymo on November 6, asking why its robotaxis kept illegally passing stopped school buses even after a software fix and recall. The National Highway Traffic Safety Administration says a majority of the reported incidents occurred after the remedy shipped. The short verdict: the patch did not hold.
Waymo, an Alphabet unit, completed a software update for all affected vehicles on November 17, 2025, the company said last year. That update followed numerous reports of its autonomous vehicles driving past school buses that had stopped and deployed flashing red lights. NHTSA's Office of Defects Investigation has now opened a formal "recall query" to, in the agency's words, "assess the adequacy of the remedy."
Reuters first reported the November 6 filing.
How did the original investigation start?
The ODI opened its initial investigation in October 2025 after reviewing footage of a Waymo autonomous vehicle maneuvering around a stopped school bus in Atlanta. The bus had its stop sign extended, its lights flashing, and was unloading children at the time.
The maneuver was not subtle. The robotaxi crossed perpendicularly in front of the school bus from its right side, then turned left around the front of the bus and continued down the street. Children were unloading. The vehicle proceeded anyway.
What happened in Austin?
Similar incidents piled up in the weeks and months after, in Austin, where Waymo also runs a robotaxi service. Officials at Austin Independent School District reported at least five such incidents, according to a letter filed with NHTSA.
The pattern matters more than any single event. A one-off failure suggests an edge case; repeated failures after a deployed fix suggest the defect model itself was incomplete. That is precisely the question the recall query will examine.
What does this change for fleet operators?
For transit and mobility managers watching autonomous deployments, the lesson is procedural rather than technical. A recall in software-defined vehicles is only as good as its post-deployment verification. Waymo pushed the update, closed the ticket, and the behavior reportedly continued.
The NHTSA query will test whether the November 17, 2025 remedy addressed the root cause or merely the observed symptom. Regulatory scrutiny of autonomous vehicle remedies now looks set to follow the same recall-query playbook used for conventional hardware defects.
TechCrunch has reached out to Waymo and Austin Independent School District officials for comment and will update its reporting if they respond. CIO Monitor will track the ODI's findings as the query proceeds.
via techcrunch.com (Source)
More from Tom Whitfield
Show full bio
Market editor covering people, launches and day-to-day practice in enterprise information technology and the leaders who run at CIO Monitor.
121 articles
The newsroom digest
One email a day with the stories that matter. No noise.
Cross-references
- Grab pauses Singapore driverless testing after pedestrian near-miss
- Australia Adopts All 18 Rapid Review Recommendations After Medicare AI Breach
- Australia Moves to Criminalize AI Failures After OpenAI Breach
- Australia Proposes AI Safety Regulator After Medicare Incident
- Robot Safety Needs Open Incident Data and Shared Standards