> ## Content Index > Fetch the complete content index at: https://bytevyte.com/llms.txt > Use this file to discover other available public pages before exploring further. # Waymo Robotaxi Incidents Expose San Antonio's Hidden Municipal Bill - URL: https://bytevyte.com/waymo-robotaxi-incidents-expose-san-antonios-hidden-municipal-bill/ - Published: 2026-09-20T12:04:52.000Z - Updated: 2026-09-20T12:04:52.000Z - Description: San Antonio police logged 50 Waymo robotaxi incidents in 10 months before rides stopped. Records show city crews absorbing what the fleet could not. - Author: Bytevyte Editorial - Tags: ai-beats **Waymo** has resumed testing its autonomous Jaguar I-PACE vehicles on San Antonio streets, but the passenger service that made the city a robotaxi market is still switched off. Police records show that at least 50 Waymo robotaxi incidents drew San Antonio officers over the 10 months before the company halted rides in April, ranging from blocked lanes to a car carried off a flooded road. None of those calls involved an injury to someone riding autonomously, and each one required a public employee to resolve. Passenger service started in late February, roughly eight months after Waymo, the Alphabet-owned autonomous driving company, began testing in the city in June 2025\. It stopped after the night of April 20, when an unoccupied Waymo entered a flooded road and was swept into a creek. Paid rides have not restarted, making the pause the company's longest known stoppage. Testing has. ## Inside the 50 Waymo Robotaxi Incidents Traffic obstruction accounts for most of the log. The cars stopped where they should not have, mid-lane and at intersections, and officers sometimes had to move them by hand, including one Waymo stranded on Broadway. Beyond that, the reports cover collisions, vehicles stuck in high water, complaints of wrong-way and reckless driving, and three separate instances of cats being struck. The records contain no case of a Waymo injuring anyone while driving autonomously. San Antonio's most serious pedestrian casualty came in April, when a person at the wheel of a Waymo hit someone who required hospital treatment. Waymo's safety case rests on that split between autonomous and human-driven miles. An officer directing traffic around a stalled SUV deals with one category of problem. Not every Waymo robotaxi incident in the log reflects a failure of the driving system. Some stemmed from other road users, from weather, or from the behavior of passengers inside. The aggregate points one way: a fleet that halts when it meets an edge case generates work for whoever arrives first, and in San Antonio that was the police department. Flooding produced two incidents in a fortnight. Before the April 20 loss, another Waymo was caught in high water at McCollough Avenue and Contour Drive. The first stranding did not stop the second, and the second took the city's service offline and triggered a recall covering thousands of vehicles nationally. The account exists because municipal records are public. No operator publishes a comparable ledger of vehicle stoppages, and no federal database separates a blocked lane from a collision. Anyone trying to measure what a driverless fleet costs a host city has to assemble the figure from dispatch logs, which is why 270 pages carry more weight than their size suggests. ## The Municipal Labor Behind the Unit Cost This is the part of the robotaxi cost model that sits outside the operator's income statement. Waymo's per-mile economics turn on sensor hardware, compute, remote assistance staffing, insurance and depreciation. They do not include the patrol car that cones off a lane, the tow called to a stationary Jaguar, or the fire crew rerouted around a vehicle parked in the wrong place during an emergency. | Recorded category | What it costs the city | | --------------------------------- | -------------------------------------------- | | Blocked traffic (most calls) | Patrol time, manual vehicle relocation | | Collisions and stranded cars | Officer response, towing, scene management | | Wrong-way and reckless complaints | Traffic enforcement, follow-up investigation | | High-water strandings | Fire and rescue standby, recovery operations | Those costs land on a city budget. San Antonio absorbed 50 dispatches across 10 months from a fleet that had been carrying paying passengers for only the last two of them. A metro with a wider service area and a longer operating history carries a proportionally larger tab, and none of it appears in a fare. City officials have no standard way to price that exposure. A permit can require an operator to report incidents, and San Antonio's records show the reporting working as intended. Converting those reports into a charge against the operator is a separate exercise, and no municipal template exists for turning officer hours, tow fees and rescue standby into a per-mile cost that a robotaxi business would have to absorb. ## The Enforcement Gap and the Restart Police departments and state agencies are still devising procedures for citing, fining or otherwise penalizing vehicles that have no driver, a question no jurisdiction has settled. Departments write rules case by case because there is no standard answer to who receives the citation when the operator is a company and the driver is software. Zoox and other operators sit inside the same blank space. Enforcement also shapes who carries the liability. Without a citation, a blocked intersection or a damaged roadway becomes an insurance claim between the operator and the city, a slower route than a traffic ticket and one that pushes administrative work back onto municipal staff. Federal attention followed the Texas cases. NHTSA warned robotaxi companies about interfering with first responders, citing a March incident in San Antonio where a human driving a Waymo was cited for crossing barriers at an active house fire, and a May episode in Austin where officers had to get a Waymo moving again after it stopped near a rollover crash at West 15th and San Antonio streets. Waymo then recalled roughly 3,800 vehicles in a software fix aimed at the flooded-road failure that ended San Antonio service, and paused operations in four Texas cities and Atlanta. San Antonio has not been switched back on, and the sequence is the point: testing returned before rides did. The recall is instructive on its own terms. The remedy reaches the fleet as a software update rather than a hardware retrofit, which places the failure inside a decision rule in the driving stack instead of a worn component. A rule that can be revised in an afternoon can also remain wrong for months, and San Antonio's two high-water events show the detection gap closing only after a car was lost. Waymo has a counter-example ready. On September 3 in San Francisco, one of its vehicles detected a violation by its riders, pulled itself over, and the company disabled the car and alerted police. The fleet acted as its own enforcement layer and handed the matter to officers with evidence attached. In July, a similar handoff followed two 15-year-olds who were detained after a Waymo was disabled and police were alerted, an episode that raised questions about how much data a ride-hailing vehicle carries to law enforcement. The commercial cost of the pause is straightforward. Robotaxi economics depend on utilization, and a parked vehicle earns no fare while depreciation, insurance and depot costs continue. Waymo's calculation in keeping San Antonio dark weighs two months of passenger revenue against the risk of a second high-water event in a market where the local police log is already public. - **San Antonio:** passenger service offline since April, autonomous testing resumed - **Four other Texas markets:** paused alongside the software recall - **Atlanta:** paused over flooded-road risk San Francisco's July 4 celebrations produced a queue of robotaxis stuck behind a single stalled Waymo while an officer stood by, and later a similar jam with a tow truck on scene. The scene repeats the San Antonio pattern at a larger scale, with the same division of labor between the company that owns the car and the city that clears it. ## Why this matters The Waymo robotaxi incidents in San Antonio are a preview of the bill that arrives before any safety verdict does. Cities hosting driverless fleets are underwriting the exceptions with patrol hours, tow contracts and fire response, and none of that cost appears in a fare or a safety report. For operators the near-term risk is regulatory: a city holding records of 50 dispatches has the evidence to keep a service dark, and San Antonio has done exactly that since April. For officials weighing a permit, the practical question is who pays when a car stops in a live lane. Photo by [Anil Baki Durmus](https://unsplash.com/@anldrms?utm%5Fsource=bytevyte&utm%5Fmedium=referral) on [Unsplash](https://unsplash.com/?utm%5Fsource=bytevyte&utm%5Fmedium=referral) ## Related Articles - [Waymo Robotaxi Ghost Gun Incident Exposes Enforcement Gap](https://bytevyte.com/waymo-robotaxi-ghost-gun-incident-exposes-enforcement-gap/) - [The Waymo Fatal Pedestrian Crash in Dallas Tests Robotaxi Tolerance](https://bytevyte.com/the-waymo-fatal-pedestrian-crash-in-dallas-tests-robotaxi-tolerance-2/) - [How Waymo San Francisco parking tickets hit 8,300 with nearly $1M in fines](https://bytevyte.com/how-waymo-san-francisco-parking-tickets-hit-8-300-with-nearly-1m-in-fines/) ✔Human Verified --- *Researched and cross-referenced against primary sources by the Bytevyte editorial team. This article was generated with the assistance of artificial intelligence and reviewed by the Bytevyte editorial team.*