Tensions between the City of Austin and autonomous vehicle operators reached a boiling point this week as the Austin City Council formally invited Waymo — the self-driving subsidiary of Alphabet / Google — to a high-stakes joint committee session. The invitation follows a widely circulated video from the March 1, 2026 mass shooting at Buford's Backyard Beer Garden, which showed a driverless taxi obstructing an ambulance attempting to reach victims.

The joint session of the Public Safety and Mobility committees is scheduled for April 29, 2026, from 11:00 AM to 1:00 PM. It represents the most direct public confrontation yet between Austin's elected leadership and an autonomous vehicle operator — and raises urgent questions about whether AI drivers can be trusted to yield to human life.

THE BOTTOM LINE: A Waymo robotaxi became stuck perpendicular across West 6th Street just as ATCEMS arrived — 57 seconds after the shooting began. An Austin Police officer had to physically enter the vehicle and drive it to a parking garage. It took roughly two minutes. That may not sound like much — but every second of those two minutes was a second in which an ambulance carrying trauma care could not reach 3 fatalities and up to 19 gunshot victims.

Incident Summary & Meeting Details

{incidentFacts.map((row) => ( ))}

Category	Details
{row.label}	{row.value}

The Lead: "Every Second Counts"

The formal letter was authored by Councilmember Zo Qadri (District 9) and co-signed by four colleagues — Vela, Velásquez, Ellis, and Laine — describing the diversion of emergency personnel as "unacceptable." While Austin-Travis County EMS (ATCEMS) confirmed that the obstruction did not ultimately change patient outcomes, the Council's message is unmistakable: first responders should never have to manually move a robotaxi during an active shooter event.

ATCEMS reached the scene in just 57 seconds — an extraordinary response time that underscores exactly how narrow the margins are in mass casualty incidents. The two-minute delay caused by the Waymo obstruction, even if ultimately non-fatal, exposed a gap in the system that no one designed a solution for.

What Happened on West 6th Street

Around 2:00 AM on March 1, 2026, gunfire erupted at Buford's Backyard Beer Garden on West 6th Street in Austin's entertainment district. The shooting ultimately resulted in 3 fatalities and 15–19 injuries, making it one of the city's deadliest bar-district mass shootings in recent memory.

In the chaos that followed, a passenger attempted to flee by summoning a Waymo vehicle through the app. The fully autonomous taxi — operating with no safety driver — responded to the request and attempted a U-turn near the intersection of West 6th Street and Nueces St. The vehicle became "stuck" perpendicular to traffic, physically blocking both lanes at the exact moment an ATCEMS ambulance was arriving.

An Austin Police Department officer ultimately resolved the situation by entering the Waymo vehicle and manually driving it into a nearby parking garage — clearing the lane after approximately two minutes of obstruction.

NOTE ON OUTCOMES: ATCEMS has confirmed that the two-minute obstruction did not ultimately alter patient outcomes in the Buford's shooting. The Council's intervention is prospective — focused on preventing a scenario where the same failure kills someone who might have been saved.

Timeline of Events

The Technical Gap: Flashing Lights vs. Algorithms

The April 29 joint committee session will center on what Councilmembers are calling a "communication gap" between AI drivers and emergency signals. The questions break down into three areas:

1. Detection: Why Didn't It Yield?

Councilmembers are pressing Waymo for a technical explanation of why the vehicle failed to immediately detect and yield to the ambulance's active sirens and emergency lights. Autonomous vehicles from Waymo are equipped with LiDAR, radar, and camera arrays that can theoretically detect emergency vehicles at range — but the Buford's incident suggests the vehicle's decision architecture did not prioritize clearance in a dynamic, chaotic street environment.

This is not a new concern. Earlier in 2026, the NTSB opened a federal investigation into Waymo after its robotaxis were documented passing stopped school buses more than 20 times in Austin and Atlanta — suggesting that the fleet's compliance with road-safety signals is an active and unresolved engineering challenge.

2. Geo-Fencing: 30 Minutes Is Too Long

Councilmember Paige Ellis reported that city officials issued a geo-fencing command to Waymo — ordering all vehicles to evacuate the Buford's area — shortly after the shooting began. Despite that order, Waymo's implementation took approximately 30 minutes. During that window, other Waymo vehicles continued operating in and around an active mass casualty scene.

The delay raises questions about the company's emergency operations infrastructure and whether a real-time command pipeline to its Austin fleet actually exists in a form that can respond at emergency speed.

3. Sovereignty: Texas Law Limits City Authority

In Texas, autonomous vehicles are regulated primarily at the state level under Texas Transportation Code Chapter 545, which grants broad operating permissions to AVs and significantly limits municipal authority to restrict them. The City of Austin cannot unilaterally ban or impose operational mandates on Waymo — meaning the April 29 hearing is as much about public pressure as it is about legislation.

Councilmembers are seeking a voluntary "Coordination Protocol" — an agreement under which Waymo would commit to faster geo-fence response times, real-time emergency vehicle detection improvements, and a direct communication channel with ATCEMS and APD during declared emergencies.

THE JURISDICTIONAL CHALLENGE: Texas state law preempts most municipal AV regulations. The Austin City Council cannot force Waymo to change its software or operating procedures through local ordinance alone. What it can do is summon Waymo to a public hearing, apply political pressure, and negotiate voluntary protocols — backed by the implicit threat of state-level lobbying if voluntary cooperation fails.

Waymo's Response

Waymo has publicly expressed "deep sadness" over the tragedy and maintained that its Waymo Driver platform "generally navigates interactions with emergency vehicles smoothly." A company spokesperson stated that the Alphabet subsidiary is "dedicated to learning from this situation."

The company also pointed to its broader safety record: Waymo vehicles in Austin have been documented to cause 80% fewer injury-causing crashes than comparable human drivers — a figure the company has consistently cited in defense of its deployment. That aggregate figure, however, does not address the specific algorithmic failure of a robotaxi that couldn't clear a lane during an active shooter event.

Waymo has not publicly confirmed whether it will attend the April 29 session, though industry observers expect the company will send representatives given the political stakes.

Related: Waymo's Growing Safety Record Under Scrutiny

The Buford's incident is not the first time Waymo's Austin operations have drawn regulatory attention. In January 2026, the National Transportation Safety Board took the unprecedented step of opening a formal federal investigation into the company:

Related Coverage — Waymo Safety

NTSB Investigation

NTSB Opens Investigation into Waymo Over School Bus Violations

Federal safety board launches first-ever probe into Waymo after robotaxis illegally passed stopped school buses more than 20 times in Austin and Atlanta. — January 23, 2026

Waymo Hub

Waymo: Full Coverage — Autonomous Vehicle News & Updates

ObjectWire's full Waymo coverage hub: safety investigations, regulatory battles, fleet expansion, and the road ahead. 20+ million autonomous miles driven.

Alphabet / Google

Google & Alphabet — Full Coverage Hub

Latest news on Alphabet's business, AI investments, Waymo expansion, and regulatory challenges across the U.S.

What to Watch: April 29 Hearing

The April 29, 2026 joint committee session is a pressure point, not a resolution. Here is what Austin residents and industry observers should watch:

Will Waymo commit to a geo-fence response time? The current 30-minute window is untenable for emergency scenarios. A binding or voluntary commitment to a sub-5-minute command execution would represent a meaningful safety advance.
Will Waymo disclose the technical root cause of the U-turn failure? The Council wants to know whether this was a sensor failure, a routing algorithm decision, or a software edge case — and whether it has been patched.
Will a Coordination Protocol be signed? A formal written agreement between Waymo and ATCEMS / APD establishing emergency override procedures would be the most tangible outcome of the hearing.
Could this push state-level reform? If Austin's public pressure campaign generates enough attention, Texas legislators may revisit the preemptive framework that currently ties the city's hands.

OBJECTWIRE WILL COVER APRIL 29 LIVE. The joint Public Safety and Mobility committee session starts at 11:00 AM CT. Follow our Waymo coverage hub for updates and post-hearing analysis.