Autonomous Vehicles AI Safety & Regulation

Software Flaw Prompts Waymo Recall of 3,791 Robotaxis — How a Vehicle Swept into a San Antonio Creek Became an Industry Safety Milestone

TM
Techmediaglobal
| 6 min read
3,791
Vehicles Recalled
0
Injuries Reported
OTA Fix
No Workshop Visit
500K
Weekly Rides Currently

An unoccupied Waymo robotaxi driving itself into a flooded section of road in San Antonio — and being swept into Salado Creek — is the kind of incident that makes headlines. What followed is the kind of response that should define a safety standard for the entire autonomous vehicle industry. Waymo identified the problem within days, paused city operations, filed a voluntary recall with the National Highway Traffic Safety Administration (NHTSA) covering all 3,791 vehicles in its fleet, and began deploying an over-the-air software fix — no service centre visits required. No passengers were on board. No injuries were reported. And the way the company handled it may matter as much as the incident itself.

The San Antonio Incident: What Happened

On April 20, 2026, an unoccupied Waymo robotaxi operating in San Antonio encountered what NHTSA documents describe as "an untraversable flooded section of a roadway." Rather than routing around the hazard — the response a properly functioning autonomous driving system is designed to produce — the vehicle slowed and then proceeded into the floodwater on a higher-speed roadway. The vehicle was subsequently swept into Salado Creek. There were no passengers on board, and no injuries were reported, but the car had to be recovered from the waterway several days later.

The incident was not a singular anomaly. Within two weeks, a second flooding-related event occurred in San Antonio, suggesting the system's flood detection capabilities on higher-speed roads had a consistent gap rather than a one-off failure. Waymo paused operations across the entire city following the second incident while it assessed the software defect and implemented interim constraints.

The Recall: Scope, Timeline, and the OTA Fix

Waymo filed a voluntary recall with NHTSA on April 30, 2026 — within ten days of the first incident. NHTSA acknowledged the recall in a letter dated May 11. The recall covers all 3,791 vehicles equipped with Waymo's 5th and 6th Generation Automated Driving Systems across all of its operating cities: Phoenix, San Francisco, Los Angeles, Austin, San Antonio, and Atlanta.

NHTSA determined that the software defect caused vehicles to slow down and then proceed into standing water on higher-speed roadways — a scenario the regulator said raises the risk of crashes and injuries. Waymo said it had "identified an area of improvement regarding untraversable flooded lanes specific to higher-speed roadways" and confirmed it is working to implement additional software safeguards, including refined extreme weather operations protocols and systems that limit fleet access to areas where flash flooding might occur.

A critical distinction from conventional automotive recalls: Waymo's remedy is delivered entirely over the air (OTA) — similar to how a smartphone receives a security patch. No vehicle needs to visit a service centre. An interim software update with tighter weather-related restrictions and updated navigation maps was deployed to all 3,791 vehicles by April 20 — before the formal recall was even filed. NHTSA noted that a permanent, complete fix has not yet been provided and flagged this in its letter to the company.

Under federal regulations, Waymo is now required to submit eight consecutive quarterly status reports to NHTSA, followed by three annual reports — a reporting process that could span several years as the company works toward a comprehensive resolution.

Why the Response Matters as Much as the Incident

How this recall is framed matters enormously for the autonomous vehicle industry. A robotaxi driving into a flooded road and being swept into a creek is the kind of story that fuels public anxiety about driverless vehicles — but the sequence of events that followed represents something genuinely different from most corporate safety responses.

Waymo identified the defect, paused city operations, deployed an interim fix across its entire fleet, and filed a voluntary recall — all within ten days, and all before a regulator required it to. The OTA remedy model means the fix reaches every vehicle simultaneously, without logistics, without delay, and without requiring owners or operators to take any action. Analysts and safety observers have noted this is precisely the model that the autonomous vehicle industry needs to demonstrate — proactive self-disclosure, rapid technical response, and transparent engagement with regulators — if it is to build the public and regulatory trust required to scale.

Context: Waymo at Scale — 500,000 Weekly Rides and Growing

The recall arrives at a moment of significant growth for Waymo. The Alphabet-owned company currently delivers approximately 500,000 paid robotaxi rides per week across six US cities and is targeting one million weekly rides by year-end — growth underpinned by a $16 billion funding round at a $126 billion valuation completed earlier this year.

The San Antonio flooding incidents are a reminder that expanding operations into new geographic and climatic environments inevitably surfaces edge cases that controlled testing and existing operational areas have not encountered. San Antonio's flash flooding patterns — common across the Texas Hill Country — present a different set of weather challenges than Waymo's established markets in Phoenix and San Francisco. As the company moves toward its next target cities, including Houston, Miami, Nashville, and Washington DC, the range of extreme weather scenarios its system must handle will continue to expand.

This recall also represents the latest in a series of NHTSA investigations into autonomous vehicle behaviour — a process that has intensified as AV operators scale commercially and regulators seek to build appropriate oversight frameworks for a technology that operates outside the traditional automotive safety paradigm. The eight quarterly reports Waymo must now file will provide regulators with a sustained window into the company's progress toward a permanent fix, and the industry with a detailed record of how a software-defined vehicle safety issue is resolved in practice.

"Waymo identified a problem, paused operations in the affected city, filed a voluntary recall within 10 days, and is deploying an OTA fix to its entire fleet. That's the model for how autonomous vehicle safety should work."

— Electrek Analysis, May 2026

What the Recall Signals for the AV Industry

For the autonomous vehicle industry broadly, this incident and recall carry several important signals. First, it demonstrates that AV safety oversight is maturing: NHTSA is actively engaging with software-defined recalls, developing the regulatory vocabulary and process frameworks needed to govern a sector where safety issues are fixed by update, not by workshop visit. The requirement for eight quarterly reports creates an unprecedented level of transparency about how a fleet-wide software defect is tracked and resolved over time.

Second, it reinforces that operational scale surfaces novel edge cases that cannot be fully anticipated in testing — a challenge every AV operator will face as they expand into new cities, climates, and road conditions. The question is not whether edge cases will be encountered, but how quickly and transparently they are identified, disclosed, and resolved.

Third, and most meaningfully for public trust: Waymo's decision to file a voluntary recall rather than waiting for regulatory pressure sets a precedent. Voluntary, proactive self-disclosure is the foundation on which public confidence in autonomous vehicles will ultimately be built — and this incident, handled as it was, is a more compelling argument for that confidence than a flawless safety record that never acknowledged a problem at all.

Key Takeaways

  • Waymo has issued a voluntary recall of 3,791 robotaxis after a software defect caused a vehicle to drive into a flooded road in San Antonio on April 20, where it was swept into Salado Creek. No passengers were on board and no injuries were reported
  • The defect affected 5th and 6th Generation Automated Driving Systems across all six operating cities — Phoenix, San Francisco, Los Angeles, Austin, San Antonio, and Atlanta — causing vehicles to slow and proceed into standing water rather than reroute
  • The recall is resolved via over-the-air software update — no service centre visits required. An interim fix was deployed to all 3,791 vehicles before the formal recall was filed with NHTSA
  • Waymo filed the recall voluntarily within ten days of the first incident and paused San Antonio operations — a proactive safety response that analysts have identified as a model for the AV industry
  • Waymo is now required to submit eight consecutive quarterly NHTSA status reports as it works toward a permanent fix — NHTSA flagged that a complete remedy has not yet been provided
  • The recall arrives as Waymo is delivering 500,000 paid rides per week and targeting one million by year-end, backed by a $16 billion funding round — underscoring that safety governance at scale is now the industry's defining operational challenge
Tags: Waymo Robotaxi Autonomous Vehicles NHTSA AV Safety Software Recall OTA Update Self-Driving