Autonomous Cars Need Waymo Time Out for Floods

  

Pardon the bad pun.  But imagine that you've taken one of the new driverless Waymo taxis from the San Antonio airport right after a big rain.  The car exits the freeway, and on the access road ahead you see where a nearby stream has overflowed, and water the color of coffee with cream is rushing across the road.  The Waymo vehicle keeps going.  You can't be sure, but the water looks deeper than you'd like, and if you were driving, you'd follow the poetic advice to turn around rather than drown.  You look for a panic button in the car:  there is no such thing.  You think about just opening a door and jumping out, but the car's going too fast for you to try that without risking your neck.  Just as the front wheels hit the water, you feel the car skidding, and you decide to try jumping out anyway.  Only now the water pressure on the door is too great, and it won't open. . . .

 

This didn't actually happen.  But it could have. 

 

On April 20, after heavy rains caused flooding on several roadways in San Antonio, an unoccupied Waymo vehicle was swept away from an interstate access road in floodwaters arising from Salado Creek.  The vehicle was later found about half a mile downstream. 

 

Following this and another incident earlier in the month, when a Waymo car became stuck in high water in San Antonio and had to be towed out, Waymo suspended all service in San Antonio and five other cities in three states, including Nashville and Atlanta.  Another Waymo car got stranded in Atlanta during heavy rains as well.  Waymo is working on updating its software to prevent such incidents in the future, but as of today, service still appears to be suspended in Austin and Atlanta, although it has been restored in San Antonio.

 

Waymo is to be commended for taking swift action in the face of obvious problems that could kill passengers in a peculiarly horrifying way.  Especially with high-tech operations of super-wealthy companies such as Alphabet (the parent firm of both Waymo and Google), profit sometimes takes a back seat to safety, and that is as it should be. 

 

Up-to-date information on high water in roadways is currently available through various means, including municipal emergency services and mapping organizations such as Waze.  But especially in Texas, floodwaters can rise within minutes, and few systems can respond that fast.  It looks like the challenge of directly detecting the presence of high water on a road through on-board sensors is something that is either too hard to do, or too unreliable.  So Waymo and other autonomous-vehicle operators may rely mostly on third-party data about where it's too dangerous to drive because of high water. 

 

Despite the drama surrounding the flooded Waymo cars, this is actually part of a process I would call normal engineering.  No matter how many problems a designer anticipates before a new technology is fielded, there will always be some issues that don't show up until the technology has been in use for a while.  This is doubly true for a complex multidisciplinary system such as an autonomous vehicle.  The world is simply too complicated for non-omniscient engineers to anticipate every single thing that might go wrong before deploying a system in the field.

 

Many of the locations where Waymo suspended service were new to the company, so Waymo had its first encounter in those cities with this spring's rainy season.  While California also has flash floods, I don't think they are as prominent a part of the landscape as they are in central Texas, for example. 

 

If I'd been riding in a Waymo car headed toward a flooded road, I wouldn't have had a lot of options.  There is no panic button as such in a Waymo.  But on the Waymo website there is a section titled "Pulling over, collisions, and security events."  They do list an option to ask the car to pull over out of traffic, but the decision as to how and when to do that is up to the system, not the passenger.  There is a way to contact "Support" (presumably a human being on the monitoring staff that every autonomous-vehicle company maintains), but having a conversation with someone possibly thousands of miles away as water surrounds the car is probably not the first thing you'd want to do.

 

All things considered, it was the wisest course for Waymo simply to shut down all service until their engineers can figure out a way to keep their cars out of water, hot or otherwise. 

 

This is also a good example of how semi-serious incidents can flag a problem that could easily lead to more serious consequences, such as customer fatalities.  If you look into the details of many historic engineering disasters, you will commonly find that less serious precursor incidents often happened in the days or years leading up to the big disaster.  This isn't always the case.  But it happens often enough that system designers should train themselves to take very seriously any safety-related problems that constitute narrow escapes.  And they should address the issues allowing such narrow escapes before some unlucky person encounters the combination of circumstances that proves deadly.

 

In shutting down all service in certain cities until the flood problem can be addressed satisfactorily, Waymo did the right thing.  This doesn't guarantee that nobody will ever drown in a Waymo car.  But in taking such a public move that obviously cost the company revenue, Waymo has both given itself time to fix the problem, and has sent a strong message to the public that they regard passenger safety as paramount. 

 

Sources:  I referred to articles in the Austin American-Statesman at https://www.statesman.com/business/technology/article/waymo-freeway-robotaxi-safety-pause-22272052.php, the BBC News website at https://www.bbc.com/news/articles/ckgplyxxl75o, and Waymo's own safety information at https://support.google.com/waymo/answer/9449023?hl=en. 

California Ends Free Ride for Robotaxi Ticketing

  

For good or ill, many things that start in California spread to the rest of the U. S. sooner or later, from Hollywood movies to the Hula Hoop.  So when California's Assembly Bill No. 1777 takes effect this July, companies such as Waymo that operate robotaxis across the country may feel its effects outside just California.

 

The bill, and its implementation by the California Department of Motor Vehicles (DMV), closes a loophole in California law that has up to now allowed driverless vehicles to escape being ticketed for traffic violations.  Previous laws assumed there would always be a driver behind the wheel to cite for illegal U-turns or other roadway malfeasance.  However, existing California law made no provision for ticketing driverless vehicles.

 

That will all change come July 1.  After that, the corporation operating the vehicle will be the designated legal recipient of any citations concerning vehicles under its control.  The ticket takes the form of a "notice of noncompliance," but the effect is the same.  To allow the DMV to track robotaxi company violations, the company must report any citations to the DMV within 72 hours of receipt.  In case a collision was involved, the window shrinks to 24 hours.  If a firm receives too many citations, the DMV is empowered to take drastic action such as limiting the firm's fleet size or even suspending its operating license. 

 

The new law also addresses the problem of how first responders can deal with driverless vehicles that get in the way at a fire or accident scene, for example.  It mandates that the operating companies must respond to calls from first responders within 30 seconds, and requires that companies observe geofencing rules that clear a designated area within two minutes.  Apparently, autonomous vehicles have obstructed the operation of fire and emergency vehicles in the past, and these new laws address that issue.

 

In the modern world, technological developments generally outpace the social infrastructure of laws and customs.  That is why robotaxis in California have been escaping traffic tickets until now, because lawyers and legislators are not prophets, and they can't expect to anticipate every possible new technological development so that the laws are waiting to be used when the technology finally comes along.

 

Most consumer technology is at least intended to have benign effects, but the good of taking people and goods from one place to another is accompanied by problems such as traffic violations.  Getting a traffic ticket is often the only interaction most law-abiding citizens have with law enforcement, but it is a little galling that robotaxis were effectively exempt from such experiences until this year in California. 

 

It's part of the normal progress of technological development for new laws to arise that deal with unexpected problems such as the ones the California bill addresses.  The issue of clearing an area for emergency operations couldn't even happen until there were enough robotaxis around that one of them got caught in such a situation, and led to frustrations and hazards that, while probably not costing a life, made enough trouble for first responders that they reported it to the appropriate authorities.  And while many uncomplimentary things can be said about the California legislature, in this case they seem to have done a good thing in mandating effective communications and actions whenever a driverless vehicle is impeding the work of first responders.

 

It's fair to say that there probably wasn't a popular groundswell of grassroots opinion demanding that robotaxis be able to receive traffic tickets.  The issue is not one to get the average Joe Public's juices going.  Contrast this matter to another technological fault line that is currently the subject of much (mostly local) legislation and discussion:  the construction of data centers around the country. 

 

As an editorial by Charles C. W. Cooke points out, data centers are not new.  In some form we've had them around for decades, and currently there are about 5,000 of them in the U. S. already, with the largest concentration in the liberal state of Virginia. 

 

Yet, to listen to discussions at city council meetings around the country or to see the "No Data Centers" signs popping up in yards, one would think that each data center is a direct portal to Dante's Inferno.  Why are people so upset at data centers, while robotaxis being immune from tickets was never a big deal?

 

Fear has something to do with it—fear of the known unknown.  For most people, robotaxi immunity from ticketing was an unknown unknown.  I didn't even know it was an issue until California fixed it with their new law.  But the publicity about data centers, and their notorious connections with the mysterious and frightening acronym AI, are well known enough, though what the consequences will be in terms of water and energy depletion or increased cost is largely unknown.  After all, if something's not built yet, you can't say exactly what will happen if you build it.

 

Opponents have rushed into that gap of ignorance with highly inflated predictions of disasters that will hit you in your pocketbook:  higher power and water prices, water shortages, and even loss of jobs as AI takes over what you and twenty of your friends do, and does it better and cheaper.  Nobody is threatened in that manner by the fact that robotaxis couldn't get traffic tickets.  Injustice somewhere else never matters as much as injustice to my bank account. 

 

So while even the California legislature can take effective action about a matter that few people knew or cared about, it's not clear that laws slowing down the construction of data centers are going to make anything better.  Saying "not in my back yard" doesn't stop construction as long as back yards don't cover the entire U. S., and that won't happen for a while.  But unless the public understands the issues well enough to make an informed decision, there is not much chance that legislation about data centers that is driven by public opinion will do much good.

 

Sources:  I referred to several articles on California Assembly Bill No. 1777, including https://driveteslacanada.ca/news/california-makes-big-changes-to-autonomous-vehicle-legislation/, https://finance.yahoo.com/economy/policy/articles/robotaxis-driverless-vehicles-now-ticketed-150019014.html, and https://www.carscoops.com/2026/04/california-robotaxi-citation-rules/.  Charles C. W. Cooke's article "Hatred of Data Centers Is Irrational and Self-Defeating" is at https://www.nationalreview.com/2026/04/hatred-of-data-centers-is-irrational-and-self-defeating/.