
Phil Koopman 11/18/26 newsletter – Waymo Growing Pains and Failed Fixes
Phil Koopman is a leading expert on robotaxi safety issues. Koopman’s 11/18/26 newsletter is incredibly useful because it explains and gives examples of how Waymos are not safely handling rare situations, the problem is not being fixed, and it appears to not be fixable. If you want to know more about robotaxi safety I highly recommend that you subscribe to his newsletter at https://philkoopman.substack.com/subscribe
A big-picture perspective on the persistent problems that Waymo can’t seem to fix — even while they push to scale up deployments
Recently we’ve seen a spate of incidents involving Waymo robotaxis, including a recent California DMV action to kick Waymo vehicles off freeways. But I’m not here to hash out specific incidents. Rather, I want to make two related points:
- These incidents aren’t one-offs. They are just the latest pieces in long-term patterns of problems.
- Promises that robotaxis will inexorably improve in response to incidents aren’t working out.
A common theme in the robotaxi safety journey is that every incident is an opportunity to learn and improve. Sure, the opportunity is there. But do they really improve? Here are the receipts showing that some patterns of problems are resisting fixes.
For those who want the high level discussion, here is a 10-minute interview I did with KTLA-TV:
The details are below, but I’ll summarize the trends first. In numerous areas, we’re seeing a pattern. Safety-relevant incidents involving Waymo vehicles keep happening despite attempted fixes. We’ve seen a pattern of recalls that did not prevent further incidents for:
- Improperly passing stopped school buses
- Driving through flood waters
- Driving in closed areas of highway construction zones
There are also persistent patterns of incidents in other areas that might yet lead to recalls. Waymo has not attempted fixes that rise to the level of a federal recall, but there is every reason to believe they have tried and failed to fix these problems.
- Interfering with traffic flow in general, and with emergency responder operations in particular
- Dangerous behavior around rail tracks: getting stuck at rail crossings and driving on dedicated rail right-of-ways
- Intruding into road closures on surface roads
- Problems interpreting manual traffic direction hand signals
- Driving into dangerous situations that are better avoided
If we’re seeing these patterns with a few thousand robotaxis, what does it look like when we see scale-ups of 10s or 100s of thousands of vehicles? With 100x more robotaxis on the road, once-a-year incidents that nobody noticed become twice per week social media clips.
Infrequent loose ends that might be tolerable with perhaps a dozen vehicles need to get fixed before we see them as constant problems on thousands of vehicles. Waymo’s track record shows that fixes for some types of problems aren’t working. Yet scaling-up proceeds apace.
Below is a list to document just some of the publicly-known incidents in each category. No doubt there are more that Waymo knows about (or ought to know about). And I’m sure I’m forgetting some that should be on the list as well. But I think the lists are long enough to make my point here. There are clear patterns of problems that aren’t being fixed, in many cases despite obvious attempts by Waymo to fix them over extended lengths of time.
What I would like to see is more transparent public reporting of misbehaviors that are seen to form a pattern, especially if those behaviors are supposed to be fixed as part of a recall process. If Waymo says they have fixed passing school buses, they should create a public dashboard of how often it is happening. Nothing in this world is perfect, but a credible dashboard showing consistent improvement over time would go a long way toward fostering public acceptance. We shouldn’t have to scour social media to find out that a promised fix didn’t really work.
Having a transparent public dashboard might also make it easier for regulators to accept that a fix will work and permit cars back on the road with less evidence than would be prudent to require otherwise. Right now, California DMV has said that Waymo needs to convince DMV that freeway construction zone intrusions are fixed before Waymo is allowed back on freeways. But the last recall “fix” didn’t work. So how is Waymo supposed to prove that this time is different? This time for sure! Sounds like a tough sell.
All these issues are a problem only sometimes, and mostly involve a small fraction of robotaxis. However, they happen often enough to be an issue, and at times happen to multiple vehicles making the same consistently wrong behavioral mistake in the same situation. And yes, human drivers make all these mistakes too. But we were promised robotaxis would not make stupid human mistakes. Turns out to be harder than claimed.
The issue here is that we need to stop pretending that robotaxis are immune to repeated mistakes because of a false narrative that every mistake results in a permanent fix. We also need to find a way to be able to trust that all autonomous vehicle companies will actually fix things they say are fixed.
Before I dive into the receipts, there are some of my pieces on related topics that support these ideas:
- Metrics based on publicly observable behavior: Beyond Crashes for Autonomous Vehicle Metrics
- Requiring public dashboards for patterns of driving misbehavior: Careful & Competent Computer Drivers: Why aren’t we seeing data about reckless driving by AVs?
- Holding autonomous vehicles accountable when traffic tickets aren’t enough: Making Autonomous Vehicles Accountable
The following sections list patterns of concerning incidents. In each case it is clear that Waymo knew (or should have known) about these problems. In many cases Waymo acted to mitigate the problems — but the problems kept happening anyway.
Driving into flood waters:
Driving into flood waters risks the car being swept away and/or a passenger being trapped sitting in a car while the water rises.
- Sep. 26, 2025: Waymo stranded on a flooded street in Phoenix.
- April 20, 2026: Waymo is swept away by flood waters in San Antonio
- May 6, 2026: Recall 26E026 to fix problems driving into flood waters
- May 21st, 2026: Waymo suspends robotaxi service in five cities due to a Waymo stalled in a flooded Midtown street in Atlanta. A journalist was stuck in standing water that day.
- After this point, problems seemed to shift from driving heedlessly into flood waters to instead being overly timid when water was present compared to human drivers. This presents different issues.
- Sept. 17, 2026: Waymo gets stuck in a retry loop for in a muddy puddle in Phoenix
- Nov. 4, 2026: Waymo stuck in San Diego King Tide flooding in shallow standing water. From the article: “The interim fix doesn’t teach the cars to judge water depth. It narrows where and when they can drive, keeping them out of conditions with a higher chance of meeting a flooded, higher-speed road. Waymo is still working on the permanent fix.”
It seems the fix for now is based on dynamic geofencing around flooded streets and some sort of real-time detection of standing water that provokes a shutdown. That is not the same as teaching the AI driver how to handle standing water appropriately based on conditions.
Passing school buses:
A common traffic law is that cars cannot drive passed stopped school buses that are loading/unloading students on undivided roads. Many school buses, including the ones in reported incidents, have not only flashing lights, but also swing-out stop signs and barrier bars that are deployed when performing loading/unloading.
- Oct. 22, 2025: A social media video showed a Waymo passing a school bus in Atlanta in September. NHTSA launches an investigation.
- Nov. 17, 2025: Recall 25E084 for proceeding past stopped school buses 12 times. (Recall paperwork is dated Dec. 10, 2025; the software update was installed Nov. 5-17, 2025).
- Nov. 20, 2025: Austin Independent School District (ISD) sends a letter to Waymo asking them to cease operations during school transportation times to avoid harm to children. Waymo declined to do so. ISD might not have known the recall remedy had been installed due to the recall not being made public until Dec. 10th. As of Nov. 20th NHTSA was still investigating. Waymo’s public statement: “We have seen material improvement in our performance since our software update.” — which is not the same as saying the problem had been fixed.
- Dec. 2, 2025: A news story shows video of Waymo vehicles passing stopped school buses in Austin 19 times.
- Dec. 4, 2025: Atlanta is up to 6 documented cases.
- Dec. 10, 2025: Recall 25E084 (mentioned above) is published by NHTSA.
- Jan. 15, 2026: Austin ISD renews its call for Waymo to stand down operations during school bus hours due to continuing incidents. Austin is up to 24 documented incidents. A couple more will happen in Spring 2026. Waymo keeps operating throughout.
- Mar. 3, 2026: NTSB releases a preliminary report stating that one school bus incident in Austin was precipitated by a human remote assistant.
- November 2026: NHTSA upgrades its continuing investigation with Recall Query (RQ26006) about why the previous recall did not prevent further incidents: “a majority of the incidents occurred after the November 17, 2025 remedy date”
It seems unlikely Waymo has a permanent fix. If they did, they would tell NHTSA, who would not have needed to promote their investigation into a Recall Query.
Driving in closed areas of highway construction zones:
Many construction zones, especially on highways, have empty lanes that seem unused and obstruction-free, but are there either as buffer space or to reserve space for where work crews have not yet reached. Driving in such areas is against traffic rules, and presents an elevated risk to work crews.
- May 18, 2026: Waymo voluntarily suspended operation in freeways based on incidents in construction zones, including a widely viewed social media post by a passenger when a Waymo accelerated to highway speeds due to a construction lane not having a line of traffic in it.
- Jul. 2, 2026: Recall 26E035 for driving at speed in closed construction zones
- Nov. 11, 2026: California DMV prohibits Waymo operation on highways after three Waymo vehicles entered an active construction closure. (This was in addition to an incident with police vehicles.)
The recall clearly did not fix the problem. California DMV determined that the vehicles pose an “imminent public safety hazard” and revoked highway driving permission. Waymo stood down highway operations in other states, which seems like a good idea for now. We’ll have to see what it takes to convince DMV that the fix really worked this time.
Interfering with emergency responders and related issues:
There have been ongoing problems with Waymo vehicles blocking streets when they shut down due to operational issues and remote assistants are unable to get them unstuck. This sometimes blocks emergency responders or otherwise interferes with their operations.
- August 9, 2023: San Francisco has 55 reports (and counting) of robotaxis (Cruise & Waymo) interfering with the fire department.
- Example: “On Aug. 5 at the Legion of Honor, a Waymo parked itself between a fire truck and a burning car. “This action impacted our suppression efforts negatively, due to members having to walk around the Waymo with a charged hose line and fight active fire,” reads the report. “The car was positioned between the car on fire and the fire engine.” ”
- Jun. 19, 2024: Waymo takes off when police tries a traffic stop for driving the wrong way; related to construction.
- Dec. 20, 2025: Dozens of robotaxis are stuck at intersections during a power outage in San Francisco, blocking streets. Waymo’s remote response team is overwhelmed by the event.
- A later hearing on the event complained that emergency responders are acting as “unpaid roadside assistance” for confused Waymos.
- Mar. 2, 2026: A Waymo blocks the road while emergency medical services were responding to a mass shooting in Austin.
- Jul. 10, 2026: A news story titled: “Delays, detours, and passed-out riders: Waymos keep blocking SF firefighters”
- July 4, 2026: Stopped Waymo vehicles continue to interfere with emergency responders, even though steps had been taken to mitigate the problem after the December power outage.
- July 8, 2026: NHTSA warning letter to all autonomous vehicle developers about interfering with emergency responders.
- Sep. 19, 2026: Waymo gets into a standoff with a fire truck in Austin.
- Oct. 1, 2026: California sets accountability rules for robotaxis that block traffic or interfere with emergency responders.
- Nov. 11, 2026: California DMV prohibits Waymo operation on highways after a Waymo attempts to pass two police cars implementing a moving traffic break. (This was in addition to construction zone issues.)
This is an open issue. The incidents keep coming. This might further break down into obstructing traffic, other interference with emergency responders, and putting unacceptable burdens on emergency responders to deal with robotaxi-specific issues. Expect more regulatory responses when we see more high-profile incidents.
Other potential patterns:
These problems have not resulted in big regulatory action. But they are problems nonetheless. Waymo needs to get ahead of these before regulators are forced to act.
- Waymo vehicles have trouble with rail grade crossings and tracks.
- Jan. 8, 2026: Waymo drives down light rail tracks.
- Mar. 10, 2026: Waymo caught inside rail arms misses being hit by a passing train .
- Nov. 7, 2026: Tesla cybercab stuck at a rail crossing in Seattle. It waits there as the train serves up extra air horn, with a side order of Boeing 737 fuselage. Tesla has had previous issues with rail tracks. (Yes, this is Tesla, but demonstrates that the March Waymo incident was not a freak one-off event.)
- Nov. 16, 2026: Waymo caught on train tracks and bashes through a crossing arm in San Diego, presumably under remote driving control.
- Surface road construction zone and road closure intrusions. These are some examples. It seems likely there are more.
- April 18, 2024: Waymo vehicles block 101 on-ramp, then go down closed road. (with video).
- Dec. 23, 2024: A Waymo vehicle drives into wet concrete, paralleling a misadventure previously performed by a Cruise robotaxi.
- Sep. 12, 2026: Waymo caught driving around street closure sign for a festival street closure
- Sep. 21, 2026: Waymo caught driving through a Denver farmer market.
- Sep. 24, 2026: Waymo gets stuck after driving into closed surface street construction zone.
- Problems interpreting manual traffic direction. This is related to interfering with emergency responders. But there are other situations that apply as well. Imagine a moving crew informally directing traffic while their big moving van maneuvers into a suitable loading position. They aren’t trained police officers, but a typical human driver can figure out from their gestures and the context what to do.
- Feb. 21, 2019: Waymo promotes that they can obey police hand signals.
- Nov. 21, 2025: Austin police say that Waymo vehicles struggle with hand signals. Points out that they struggle with social contextual awareness.
- A Waymo wanders into an area with dangerous conditions, such as an intersection where someone is drift driving. Yes doing donuts in a city intersection is improper. However, Waymo vehicles don’t always recognize the risk of trying to drive through such a scene instead of detouring around the craziness or other dangerous situations. There is overlap here with driving into high-risk emergency response situations.
- Aug. 5, 2024: Near-miss (“within a foot of crashing”) when Waymo enters an intersection where another driver is doing donuts in San Francisco.
- Dec. 5, 2025: Waymo drives into an active police scene in Los Angeles in which officers had weapons drawn and a suspect prone on the pavement. The intersection is clear of traffic to make a left turn. There is a reason for that, and it’s not a good one. The lineup of police cars with lights on, and police officers with guns drawn should have been a clue.
- Nov. 16, 2026: Drift driver hits a Waymo vehicle that entered the intersection in Los Angeles.
(Dates are approximate and may correspond to a news article date rather than an incident date.)
The city of Austin provides a public dashboard of local robotaxi incidents. However, the incidents must be reported by the public. Waymo and other companies do not provide data about incidents they know about.
There are plenty of embarrassing Tesla videos as well, but the presence of a human supervising driving in most of those situations clouds the issue. So we leave those for another time. However, each company should learn from problems that happen to other companies. It seems that there are plenty of learning opportunities to go around.