The Robot Saw the Flood, Slowed Down, and Drove In Anyway
Waymo filed a voluntary software recall with NHTSA covering 3,791 robotaxis after an empty vehicle drove into floodwater in San Antonio and was swept into Salado Creek. The fix ships over the air.
TL;DR — Waymo is recalling 3,791 robotaxis after an empty vehicle in San Antonio slowed down and drove into a flooded road in late April, getting swept into Salado Creek; the company is pushing an over-the-air software fix and paused service in the city.
The entire promise of the self-driving car rests on one quietly arrogant claim: that a machine won't make the stupid call. It doesn't get drowsy, doesn't glance at its phone, doesn't talk itself into a bad decision the way a tired human at the end of a shift might. So it is worth pausing, for a moment, on what a Waymo robotaxi in San Antonio actually did in late April 2026. It approached a flooded road. It registered the flooding and slowed down. And then it drove straight in.
That small, almost absurd sequence — the car saw the hazard and proceeded into it anyway — is the whole story, and it's why Waymo is now recalling thousands of vehicles.
The long tail is where self-driving still loses
The temptation is to read this as a Waymo problem. It isn't, really — or not only. Waymo is the most cautious, most data-saturated operator in the robotaxi business, and it still put a vehicle on the road that couldn't reliably handle standing water. That's less an indictment of one company than a reminder of how absurdly long the tail of "edge cases" actually runs. Floods, construction zones, downed power lines, a mattress sitting in the fast lane — the physical world keeps inventing situations no training dataset ever anticipated. Autonomous driving stopped failing at the average case a while ago. It fails at the strange one. And the strange one is precisely the territory where a human's plain common sense still quietly wins.
What happened on Salado Creek
According to the recall report, the vehicle was unoccupied when, on April 20, it met what the filing dryly calls "an untraversable flooded section of a roadway." Rather than stopping or rerouting, the Waymo eased into the floodwater at reduced speed and was eventually swept into Salado Creek, as TechCrunch reported. Nobody was hurt — and that's worth saying plainly — only because nobody was inside. Empty, it's an embarrassing engineering bug. Occupied, it's a very different headline. Waymo paused operations across San Antonio and, on May 12, filed a voluntary software recall with the National Highway Traffic Safety Administration.
What the recall actually covers
The filing reaches 3,791 vehicles running Waymo's fifth- and sixth-generation Automated Driving System. The company's own description of the flaw is a small masterpiece of softened language:
"We have identified an area of improvement regarding untraversable flooded lanes specific to higher-speed roadways, and have made the decision to file a voluntary software recall with NHTSA related to this scenario."
Translated out of the corporate register: on faster roads, when the system hit water it couldn't cross, it would slow down rather than stop. NHTSA noted that Waymo is still "developing the final remedy for this recall."
| The recall at a glance | |
|---|---|
| Vehicles affected | 3,791 |
| Systems | 5th & 6th-gen ADS |
| Trigger incident | April 20, 2026, San Antonio |
| Filed with NHTSA | May 12, 2026 |
| Remedy | Over-the-air software update |
Why "recall" doesn't mean what it used to
Here's the genuinely novel part, and it's also where the word "recall" starts to fray. Nobody has to drive anywhere. The fix arrives over the air, pushed to the entire fleet — no service center, no loaner, no waiting on a back-ordered part. An initial update has already imposed restrictions "at times and in locations where there is an elevated risk of encountering a flooded, higher-speed roadway."
That is the upside of a software-defined car: a flaw that once meant millions of physical trips to a dealership now resolves overnight while the cars sleep. The downside is semantic but real. "Recall" now stretches across everything from a cracked brake line to a logic gap that simply never imagined standing water — and as it stretches, the term loses a little of its bite. A 2008 Takata airbag recall and a software patch for a flooded creek are not remotely the same kind of event, even if they share a name and a federal filing.
FAQ
How many Waymo robotaxis were recalled and why?
Waymo recalled 3,791 robotaxis running its fifth- and sixth-generation self-driving system. The reason was a software flaw that, on higher-speed roads, would let a vehicle slow down and drive into standing water it couldn't cross, rather than stopping — the same behavior that swept an empty Waymo into Salado Creek in San Antonio.
Do owners need to bring the cars in for the Waymo recall?
No. Waymo owns and operates the fleet, and the fix is delivered over the air. No vehicle needs to visit a service center; an initial update already restricts driving near flooded higher-speed roadways while Waymo finalizes the full remedy.
Was anyone hurt in the San Antonio Waymo flood incident?
No. The vehicle that drove into the flooded road and was swept into Salado Creek on April 20, 2026 was unoccupied, with no passenger inside.
Sources: TechCrunch, Electrek, CNBC.
Image: 9yz, CC BY-SA 4.0, via Wikimedia Commons.
← Back to all posts