Robotaxi safety
Do robotaxis get out of the way for emergency responders?
No operator publishes a verified rate for yielding to emergency vehicles.
Robotaxi companies say their vehicles detect sirens and lights and pull over for first responders, and regulators are watching how well that holds up. DEPLOY has not verified an audited yield rate for any operator. What is on the record is the dated, sourced trail below: incidents, investigations, and rules that touch this question.
Find out instantly when it changes.
There is no single verified answer to whether robotaxis reliably get out of the way for emergency responders. Operators including Waymo and Zoox say their vehicles are built to detect emergency lights and sirens and to pull over or stop, and they publish guidance for firefighters and police. Those are the companies' own descriptions of intended behavior, attributed to them, not audited results.
Separately, first responders and regulators have documented cases where a robotaxi blocked or hesitated near an emergency scene, and some of those became federal investigations. DEPLOY tracks each one as a dated, sourced record. Until an operator or a regulator publishes an audited yield rate, the honest answer is that the behavior is claimed, watched, and handled case by case, not verified in the aggregate.
What operators say vs what is documented
Each side is attributed to who said it. The operators' position is their own claim; the documented cases and investigations are attributed to the responders and regulators who reported them.
Built to yield
Operators say their vehicles detect emergency lights and sirens and pull over or stop, and they publish guidance for fire and police departments. This is the companies' own description of intended behavior, attributed to them, not an audited result.
Watching the real cases
First responders have reported robotaxis blocking or hesitating near emergency scenes, and federal regulators have opened investigations that touch this behavior. Each is attributed to who reported or filed it, and an open investigation does not by itself establish fault.
No audited yield rate
No operator or regulator publishes an audited rate for how reliably robotaxis yield to emergency vehicles. Until one does, the answer stays claimed and case by case. The record trail below is what is verified right now.
The record trail
Every incident, investigation, and rule DEPLOY holds that bears on this question, each dated and sourced. The per-operator safety record is on the robotaxi safety tracker.
- Rep. Kevin Mullin proposes AV Emergency Response Coordination Act requiring national safety standards for autonomous vehiclesIncident
Rep. Kevin Mullin (D-Calif.) unveiled the AV Emergency Response Coordination Act on July 28, 2026, at a press conference in San Francisco with Mayor Daniel Lurie and SF Fire Chief Dean Crispen. The bill would direct NHTSA to develop minimum national emergency response standards for AV operators, require 24-hour hotlines for public officials, and give cities the power to geofence AVs during emergencies. The bill follows a pattern of robotaxis blocking ambulances, driving into active crime scenes, and failing to recognize safety signals.
- Waymo robotaxi rear-ended by SUV at Sunset Road and Polaris Avenue in Las Vegas, at least one injuredIncident
On July 19, 2026 at approximately 9:45 a.m., a Waymo autonomous vehicle was struck from behind by a dark-colored SUV near Sunset Road and Polaris Avenue in south Las Vegas. The SUV continued forward after the impact and also hit a light pole. Las Vegas Metropolitan Police confirmed at least one person was injured and the investigation is ongoing. Waymo stated the SUV struck the Waymo vehicle from behind. This is the first reported Waymo crash since the Las Vegas service launched.
- Waymo robotaxi rear-ended by SUV in south Las Vegas, at least one injuredIncident
On July 19, 2026 at approximately 9:45 a.m., a human-driven SUV struck a Waymo robotaxi from behind near Sunset Road and Polaris Avenue in south Las Vegas, then continued forward and also hit a light pole. At least one person was injured. Las Vegas Metropolitan Police Department confirmed the crash and said the investigation is ongoing. Waymo told FOX5 the SUV struck the Waymo vehicle from behind before continuing forward and hitting the light pole.
- Zoox issues software recall after robotaxi drove through heavy smoke at Las Vegas emergency sceneIncident
Zoox issued a software recall after an unoccupied robotaxi drove into an active emergency fire scene clouded with heavy smoke in Las Vegas in June 2026. The NHTSA filing cites the software's failure to detect and respond to heavy smoke near emergency scenes. The recall comes as NHTSA has warned AV companies about vehicles interfering with first responders.
- Zoox recalls 105 robotaxis after vehicle drove into heavy smoke at active Las Vegas fire sceneIncident
Zoox voluntarily recalled 105 autonomous vehicles after an unoccupied robotaxi drove into heavy smoke obscuring an active emergency fire scene in Las Vegas on June 20, 2026. The vehicle braked hard and steered away before stopping; a teleoperator reversed it from the scene. Zoox notified NHTSA of the recall on July 8, and it was publicly reported July 17. The recall follows a NHTSA letter urging AV companies to stop interfering with first responders.
- Zoox recalls entire 105-vehicle fleet after robotaxi drove into smoke-filled active fire sceneIncident
NHTSA recall 26E044 (July 17 2026): On June 20 2026, an unoccupied Zoox robotaxi encountered heavy smoke obscuring an active emergency fire scene that was not cordoned off with cones. The vehicle failed to detect and respond to the smoke-filled scene. Zoox issued a software update to 105 vehicles enhancing detection of active emergency scenes by adding heavy-smoke response capability. No injuries reported. The recall came one week after NHTSA warned AV companies about interfering with first responders.
- Zoox recalls entire 105-vehicle fleet because robotaxis may not detect heavy smoke and could impede emergency respondersIncident
Amazon's Zoox recalled its fleet of 105 autonomous vehicles after an unoccupied Zoox robotaxi entered an active emergency fire scene obscured by heavy smoke on June 20, 2026, braked hard, and reversed under teleguidance. The recall follows a NHTSA letter warning AV companies about a clear pattern of driverless vehicles interfering with law enforcement and first responders. Zoox issued a software update to enhance smoke detection and response capabilities.
- San Francisco Supervisor Connie Chan drafting cost-recovery fee legislation to fine AV companies for impeding emergency responseIncident
San Francisco Supervisor Connie Chan is drafting legislation to impose financial consequences on autonomous vehicle companies when their vehicles interfere with emergency operations, including false emergency reports and impeded emergency response. The SF Fire Department has documented 31 internal incident reports involving AVs blocking emergency routes. Mayor Daniel Lurie and the city attorney are supporting the measure, expected to be presented to the Board of Supervisors in the coming months. This is a local regulatory action distinct from the federal NHTSA directive issued July 8, 2026.
- NHTSA issues directive to AV developers citing clear pattern of driverless AVs interfering with first respondersIncident
In July 2026, NHTSA Administrator Jonathan Morrison issued a directive to autonomous vehicle developers requiring them to ensure their vehicles get out of the way of first responders. The letter cited a clear pattern of driverless AVs interfering with law enforcement and other first responders, including incidents where AVs drove into active emergency scenes, blocked the paths of ambulances or firefighters, or failed to recognize or respond to flashing lights, flares, smoke, fire, and traffic cones. The directive preceded Zoox's smoke-detection recall and follows multiple Waymo recalls for construction-zone and flooded-roadway entry failures.
- NHTSA demands AV developers stop driverless vehicles from interfering with first respondersIncident
NHTSA Administrator Jonathan Morrison issued a directive to autonomous vehicle developers stating that driverless AVs interfering with law enforcement and first responders is a 'functional insufficiency,' not an edge case. The agency cited incidents of AVs driving into active emergency scenes, blocking ambulances and firefighters, and failing to recognize flashing lights, flares, and traffic cones. AV developers were given until end of July to present solutions. While no company was named explicitly, details point to robotaxi operators like Waymo.
- NHTSA issues call to action to AV developers over pattern of driverless AVs interfering with first respondersIncident
On July 8, 2026, NHTSA Administrator Jonathan Morrison issued a public call to action to automated vehicle developers, citing a pattern of driverless AVs driving into active emergency scenes, blocking ambulances and firefighters, and failing to recognize flashing lights, flares, smoke, fire, and traffic cones. NHTSA scheduled meetings with driverless ADS developers by month's end and warned it will exercise enforcement authority for developers that do not address significant safety concerns.
- SF Supervisor Bilal Mahmood launches inquiry into Waymo's July 4 traffic meltdownIncident
On July 7, 2026, San Francisco Supervisor Bilal Mahmood announced a letter of inquiry to the city's Department of Emergency Management, Fire Department, and Municipal Transportation Agency, seeking information on how Waymo robotaxis contributed to massive gridlock following the July 4 Golden Gate Bridge fireworks show. More than 30 Waymo robotaxis became stuck in the Presidio parking area, some running out of charge and requiring towing. Mahmood stated it is 'not acceptable that disruption of service, first responders and our public transit system is a side effect of autonomous vehicles' and requested city departments respond within two weeks. The inquiry follows repeated Waymo run-ins with first responders documented by TechCrunch and a July 8 NHTSA directive demanding AV companies stop interfering with emergency operations.
- California SB 1246 and AB 1777 take effect July 1, 2026 - new AV regulationsIncident
California SB 1246 reinforces requirements for remote assistants and drivers of commercial AVs. AB 1777 establishes requirements for how driverless AVs interact with first responders and emergency operations. Both take effect July 1, 2026.
- California AB 1777 requires driverless vehicles to support first responder communication and emergency geofencingCalifornia rule
California enacted Assembly Bill 1777, authored by Assemblymember Phil Ting, which the state chaptered on September 27, 2024 and which became operative on July 1, 2026. The law requires companies that operate autonomous vehicles without a human driver present to maintain a dedicated emergency response telephone line for first responders during all hours, to equip each vehicle with a two way voice communication device so first responders near the vehicle can reach a remote operator, to provide training for law enforcement and firefighters on the vehicle override system, and to direct their fleet to leave or avoid an area within two minutes of receiving an emergency geofencing message from emergency response officials. This record is attributed to the enacted text of AB 1777 as published by the California Legislature.
- Zoox issues software recall after robotaxi drives through heavy smoke at Las Vegas fire sceneIncident
An unoccupied Zoox robotaxi drove through heavy smoke from an active fire emergency in Las Vegas that had not yet been cordoned off with traffic cones. Zoox investigated the root cause and developed a software update to enhance detection of and response to heavy smoke near active emergency scenes. The voluntary recall covers 105 vehicles with ADS software produced between April 23 and July 8, 2026. Updated software was deployed to all affected vehicles on July 15, 2026.
- Zoox issues software recall after robotaxi drives through heavy smoke at active fire scene in Las VegasIncident
An unoccupied Zoox robotaxi encountered heavy smoke from an active fire emergency in the Las Vegas area that had not yet been cordoned off with traffic cones. The vehicle entered the scene, braked hard, and attempted to steer away before stopping. Zoox notified NHTSA on June 25, 2026, and issued a voluntary software recall covering 105 vehicles with ADS software produced between April 23 and July 8. A software update was developed to enhance detection of and response to heavy smoke near emergency scenes.
- Zoox issues software recall after robotaxi drove into heavy smoke at active fire scene in Las VegasIncident
On June 20, 2026, an unoccupied Zoox robotaxi encountered heavy smoke from an active emergency fire scene in Las Vegas that was not cordoned off with cones. The vehicle braked hard and steered away before stopping. Zoox issued a voluntary software recall covering 105 vehicles on July 8, 2026, shipping an update that adds smoke detection capability. No injuries were reported. The recall follows NHTSA's July 8 letter warning AV companies to stop interfering with first responders.
- Zoox issues software recall after robotaxi drove into heavy smoke at emergency fire sceneIncident
On June 20, 2026, a Zoox robotaxi encountered heavy smoke obscuring an active emergency fire scene that was not cordoned off with cones; the vehicle braked hard and steered away before stopping, and a Zoox teleoperator reversed it from the scene. Zoox issued a voluntary software recall (NHTSA 26E044000) on July 7, 2026 affecting its 105-vehicle fleet, shipping a software update to detect and respond to heavy smoke at emergency scenes. No injuries were reported and no passengers were on board. The recall came a week before NHTSA administrator Jonathan Morrison sent a letter warning AV companies to stop interfering with first responders.
- Zoox issues software recall after robotaxi entered smoke-filled emergency fire sceneIncident
On June 20, 2026, an unoccupied Zoox robotaxi encountered heavy smoke obscuring an active emergency fire scene that was not cordoned off with cones. The vehicle braked hard while attempting to steer away before stopping; a teleoperator reversed it to allow first responders to place cones. No injuries reported. Zoox shipped a software update to its 105-vehicle fleet enhancing detection of heavy smoke at emergency scenes. NHTSA recall ID 26E044000, decided July 7, 2026.
- Zoox recalled 105 robotaxis after an unoccupied vehicle drove into heavy smoke at an active fire scene in Las VegasIncident
On June 20, 2026, an unoccupied Zoox robotaxi entered an active emergency fire scene obscured by heavy smoke in Las Vegas that had not yet been cordoned off with cones. The vehicle braked hard while attempting to steer away before stopping. Zoox notified NHTSA of a voluntary software recall on July 8, 2026, affecting 105 robotaxis. A software update enhancing heavy-smoke detection was released to all affected vehicles on July 15. No injuries were identified. The recall follows NHTSA Administrator Morrison's July 8 letter calling AV interference with first responders a functional insufficiency.
- Zoox recalls 105 robotaxis after one drove into active fire scene in Las VegasIncident
A Zoox robotaxi entered an active fire emergency scene not yet cordoned off by cones in the Las Vegas Valley on June 20, 2026, conducted a hard brake while trying to steer clear, and came to a stop; a Zoox employee had to guide it out. Zoox voluntarily recalled 105 robotaxis and issued a software update to improve detection of and response to heavy smoke. The incident was reported to NHTSA under the Automated Vehicle Exemption Program on June 25.
- Zoox recalls all 105 robotaxis (NHTSA 26E044) after robotaxi drove into heavy smoke at an active fire sceneIncident
Zoox issued a voluntary software recall covering all 105 of its driverless robotaxis after an unoccupied Zoox vehicle entered an active emergency fire scene obscured by heavy smoke on June 20, 2026. The vehicle braked hard and steered away before stopping, and a remote teleguidance operator reversed it out so first responders could cone off the scene. No injuries were reported. Zoox released an updated software remedy on July 15, 2026; the recall (NHTSA 26E044, manufacturer recall 26-01) was submitted July 16.
- Zoox software recall (NHTSA 26E044) — robotaxi drove into active fire scene confused by heavy smokeIncident
On June 20, 2026, a Zoox robotaxi in Las Vegas encountered heavy smoke from an active emergency fire scene that was not cordoned off with cones. The vehicle braked hard and steered away before stopping. A teleoperator reversed the vehicle. Zoox issued voluntary recall of 105 robotaxis on July 7, 2026 (NHTSA Campaign 26E044). Software update deployed to improve heavy smoke detection. No injuries. NHTSA Administrator Morrison sent letter July 8 warning AV companies to stop interfering with first responders.
- Zoox robotaxi involved in minor crash on Las Vegas Boulevard and Harmon Avenue, vehicle towedIncident
A Zoox robotaxi was involved in a minor crash at Las Vegas Boulevard and Harmon Avenue in Las Vegas, requiring the self-driving vehicle to be towed. Metro police closed the case after they could not contact either party. The incident was observed on a Regional Transportation Authority traffic camera livestream.
- ADS crash report in Austin, TX involving a TOYOTA Highlander (NHTSA SGO 30610-15465)Incident
A Zoox vehicle, operating in autonomous mode, was stopped in the westbound left-turn lane of [XXX], yielding to oncoming traffic to turn left onto [XXX] in Austin under a flashing yellow arrow. Eastbound traffic on [XXX] was backed up and slowing down. After receiving a hand gesture from the driver of a slowing SUV in the oncoming lane, the Zoox vehicle operator disengaged from autonomy and proceeded with the left turn. At that time, a pickup truck (Vehicle 2) traveling in the right lane of eastbound [XXX] quickly approached the intersection. Although the driver of Vehicle 2 attempted to steer left, the vehicle collided with the rear right area of the Zoox vehicle in the intersection. Vehicle 2's left side subsequently made contact with the front right corner of the oncoming SUV. Both the Zoox vehicle and Vehicle 2 sustained moderate damage, and the Zoox vehicle was towed. No injuries were reported, and police were notified but did not respond to the scene.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15301)Incident
On June [XXX], 2026 at 1:07 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was involved in a collision involving a motorcycle and an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the dedicated left turn lane for a red light on [XXX] at the intersection with [XXX]. While the Waymo AV remained stopped, a motorcycle traveling in the second from the right lane came to a stop adjacent to an SUV that was stopped in the rightmost lane. After both vehicles briefly remained stopped, the SUV and motorcycle began to proceed forward when the SUV changed lanes into the second from the right lane, towards the motorcycle. The motorcycle maneuvered left towards the dedicated left turn lane, and the SUV continued to change lanes across the second from the right lane, towards the motorcycle into the dedicated left turn lane. While the SUV continued to change lanes, the front right of the SUV made contact with the rear of the motorcycle, and the front left of the SUV made contact with the right side of a passenger car that was stopped behind the Waymo AV. As a result of this initial contact with the SUV, the motorcycle continued forward and the front of the motorcycle then made contact with the rear right of the Waymo AV. The SUV also continued forward, and the front left of the SUV then made contact with the rear right of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All involved vehicles sustained damage, and the motorcyclist was transported to the hospital by ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital by ambulance. Waymo may supplement or correct its reporting with additional information as it may become available.
- Waymo robotaxi blocked Dallas first responders from reaching fatal Oak Cliff apartment explosionIncident
On May 28, 2026, a driverless Waymo robotaxi partially blocked the roadway that fire trucks needed to reach a five-alarm gas explosion at The Clyde apartments in Dallas Oak Cliff that killed three people and injured five. Body camera footage released June 4 shows a Dallas County deputy constable having to manually drive the empty Waymo to clear the street so emergency crews could reach the scene. Waymo said the vehicle was turning around when the constable interacted with its remote assistance team.
- ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-14977)Incident
On May [XXX], 2026 at 10:01 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] in the rightmost lane when it approached the intersection with [XXX], where police officers were directing traffic. The Waymo AV came to a stop and, after cross traffic cleared, proceeded into the intersection. A passenger car traveling southbound on [XXX] in the leftmost lane entered the intersection per the direction of one of the police officers. The Waymo AV slowed to yield to the passenger car and the front left side of the passenger car made contact with the front right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15246)Incident
On May [XXX], 2026 at 11:42 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Inglewood, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] when it slowed to a stop for a stop sign at the intersection with [XXX]. While the Waymo AV was stopped, a passenger car that was initially stopped facing east on [XXX] initiated a left turn onto northbound [XXX]. At the same time, an SUV traveling northbound on [XXX] proceeded straight into the intersection without stopping at the stop sign on [XXX], and the front left side of the SUV made contact with the right side of the passenger car. As a result of this contact, the passenger car shifted northbound towards the stopped Waymo AV, and the front of the passenger car made contact with the front left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage. The driver of the passenger car was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15295)Incident
An unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling north on [XXX], having just completed a left turn from [XXX] in Las Vegas, when it encountered debris in its path. The Zoox vehicle attempted to steer right, then executed hard braking to avoid the debris, at which point it was rear-ended by a passenger car (Vehicle 2) traveling directly behind it. Both vehicles came to a stop following the impact and were subsequently towed due to the damage sustained. Vehicle 2 suffered front-end damage and its driver-side frontal airbags deployed, while the Zoox vehicle sustained moderate damage to its rear. Law enforcement was notified of the event, but did not respond to the scene. Following the impact, Zoox staff inquired if emergency medical services should be called; the driver replied that the police had already been contacted. The driver of Vehicle 2 informed Zoox staff at the scene that they were "shaken" and "pretty bruised".
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15030)Incident
On May [XXX], 2026 at 4:46 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound in the right lane on [XXX] when it slowed to a stop at a green light at the T-intersection with [XXX] to yield to an active fire truck, with lights and sirens activated, traveling eastbound on [XXX] and crossing into westbound [XXX] to traverse through the intersection. While the Waymo AV was stopped, an SUV initially stopped behind the Waymo AV, partially in the left lane and partially in the right lane, proceeded to pass the Waymo AV to the left, and the front right side of the SUV made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Los Angeles, CA involving a ZEEKR RT (NHTSA SGO 30270-15070)Incident
On May [XXX], 2026 at 6:44 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a pickup truck on [XXX] near {XXX}. The Waymo AV was traveling southbound in the right lane on {XXX] in autonomous mode when it began to slow for a queue of traffic stopped for a red light at the intersection with [XXX]. As the Waymo AV was slowing, the Waymo AV transitioned to manual mode and the test driver maneuvered to the right and accelerated forward. As the test driver maneuvered the Waymo AV to pass to the right of a pickup truck that was stopped facing south in the right lane in the queue of traffic ahead, the front left side of the Waymo AV made contact with the rear right side of the pickup truck, the front of the Waymo AV made contact with the west curb of {XXX], and the front right side of the Waymo AV made contact with a street light pole near the curb. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. The test driver of the Waymo AV was transported to a hospital by an ambulance with moderate injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-15174)Incident
On May [XXX], 2026 at 3:59 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling westbound in the second to the right lane on [XXX] and proceeding straight at a green light at the intersection with [XXX]. As the Waymo AV began to cross the intersection, a pickup truck traveling northbound in the designated right turn lane on [XXX]t proceeded to enter the intersection against a red light and began to maneuver to the left. The Waymo AV braked and maneuvered to the right as the pickup truck continued to proceed forward, and the front of the pickup truck made contact with the left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Two passengers in the Waymo AV were not belted at the time of the collision. Two passengers in the Waymo AV were transported to a hospital by an ambulance with moderate injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because individuals involved were transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15021)Incident
On May [XXX], 2026 at 12:02 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] and slowing for a queue of traffic for a red light at the intersection with [XXX] when the Waymo AV passenger opened the rear right door, causing the Waymo AV to stop in-lane and activate its hazard lights for passenger dropoff. While the Waymo AV was stopped, a shuttle bus traveling southbound on [XXX] approached the Waymo AV from the front and slowed to a stop momentarily. The shuttle bus proceeded forward to pass the Waymo AV to the left, between the Waymo AV and a fire truck that was stopped facing north partially in the bike lane and in-lane on southbound [XXX], and the left side of the shuttle bus made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15096)Incident
On May [XXX], 2026 at 11:59 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] with its right turn signal activated when it began to slow to yield to a passenger car stopped facing west near the north curb of [XXX] and partially in-lane. While the Waymo AV was slowing, an SUV traveling westbound on [XXX] at a high rate of speed approached the Waymo AV from behind, and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15250)Incident
On May [XXX], 2026 at 1:07 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was traveling northbound on a narrow portion of [XXX], with vehicles parked at the curb in both directions, when it maneuvered to the right and slowed to a stop in-lane to yield to an inactive ambulance traveling southbound on [XXX]. While the Waymo AV was stopped, the ambulance proceeded to pass the Waymo AV to the left, and the left side of the ambulance made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-15018)Incident
An unoccupied Zoox autonomous vehicle was traveling south on [XXX] on a green light at [XXX] in San Francisco when a pickup truck (Vehicle 2) executed an abrupt left turn from northbound [XXX] and accelerated into the Zoox vehicle's right-of-way. The Zoox vehicle braked hard, but contact was unavoidable. Vehicle 2's front bumper struck the Zoox vehicle's left side door and body panels. After reversing, Vehicle 2 cleared the intersection, pulled over temporarily, and then left without exchanging information. Shortly afterward, the Zoox vehicle cleared the intersection, pulled over, and was towed for inspection. It was found to have sustained moderate damage. No injuries were reported, and police were not called.
- ADS crash report in Santa Monica, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14986)Incident
On May [XXX], 2026 at 8:37 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving multiple vehicles on [XXX] near [XXX]. The Waymo AV was stopped facing southeast in the left lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. Behind the Waymo AV, in the same lane of traffic, were three consecutive SUVs. All three SUVs behind the Waymo AV were initially also stopped in the traffic queue until the rear-most of the three SUVs proceeded forward. The rearmost SUV contacted the SUV in front of it, pushing the second SUV forward into the SUV behind the Waymo AV. The SUV behind the Waymo AV then made contact with the rear of the stationary Waymo AV, and as a result of this contact, the front of the Waymo AV made contact with a passenger car stopped directly in front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All five vehicles sustained damage. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-15022)Incident
On May [XXX], 2026 at 12:43 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling eastbound in the rightmost lane on [XXX] with its right turn signal activated when it began to slow to turn right into a parking lot at [XXX]. As the Waymo AV initiated the right turn, a passenger car traveling eastbound in the rightmost lane on [XXX] approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. A passenger in the passenger car was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14656)Incident
An unoccupied Zoox autonomous vehicle was traveling north on [XXX] past [XXX] in Las Vegas when a passenger car (Vehicle 2) abruptly attempted to turn right onto [XXX] from a parking lot, violating the Zoox vehicle's right-of-way. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The Zoox vehicle's right-front fender, wheel, and fascia contacted Vehicle 2's left-front bumper and headlight. Both vehicles sustained damage, and the Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14732)Incident
An unoccupied Zoox autonomous vehicle was in the left lane traveling north on [XXX] past [XXX] when it slowed for a tractor-trailer (vehicle 2) that was reversing from the roadway into a loading bay on the right side of the road. While reversing, the tractor-trailer swung over into the left lane, and the left side of Vehicle 2's trailer made contact with the stopped Zoox vehicle's front fascia and sensor pods. The Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15064)Incident
An occupied Zoox autonomous vehicle, gradually slowed to a stop behind traffic on southbound [XXX] past [XXX] in Las Vegas, when it was rear ended by a passenger vehicle (Vehicle 2) traveling directly behind. The Zoox vehicle honked at the approaching Vehicle 2, but its driver failed to stop in time. Vehicle 2's driver left the scene without exchanging information. The Zoox vehicle did not sustain any damage. No injuries were reported at that time. Police were notified. One of the passengers later contacted Zoox support and stated, "I began experiencing significant neck pain consistent with a possible soft tissue injury." The passenger has not provided any documentation to Zoox regarding their alleged injury.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15065)Incident
An unoccupied Zoox autonomous vehicle was preparing to turn right from a hotel driveway onto southbound [XXX] in Las Vegas, and came to a gradual stop to yield to cross traffic when it was rear ended by a pickup (Vehicle 2) traveling directly behind. The Zoox vehicle honked at the approaching Vehicle 2, but Vehicle 2's driver failed to stop in time. Vehicle 2's driver then went around the stopped Zoox vehicle, briefly stopped in the right lane, activated their hazard lights, and then proceeded to leave the area. Upon inspection, the Zoox vehicle was found to have sustained moderate damage to its rear. No injuries were reported and police were not notified.
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14660)Incident
On April [XXX], 2026 at 11:38 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was parked facing north on [XXX], partially in-lane and partially in the bike lane, with its hazard lights activated for a passenger dropoff. While the Waymo AV was parked, an SUV traveling northbound on [XXX] without active headlights maneuvered to the right as the SUV approached the Waymo AV from behind, and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passengers of the Waymo AV were transported to a hospital by an ambulance with minor alleged injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because individuals involved were transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14829)Incident
On April [XXX], 2026 at 9:56 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was parked at the east curb facing north on [XXX] with its hazard lights activated for a passenger dropoff. While the Waymo AV was parked, an SUV traveling westbound on [XXX] turned right onto [XXX] and approached the Waymo AV from behind, and the front right side of the SUV made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. A passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14888)Incident
On April [XXX], 2026 at 9:13 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing northwest on [XXX] for a stop sign at the intersection with [XXX] with its left turn signal activated. The Waymo AV proceeded forward into the intersection and began to initiate a left turn onto [XXX], and an SUV, initially stopped behind the Waymo AV, proceeded forward and maneuvered to the right towards the Waymo AV, and the front of the SUV made contact with the rear left side of the Waymo AV. As the Waymo AV continued to turn left, the SUV began to turn left and proceeded forward again, and the front of the SUV made additional contact with the rear right side of the Waymo AV. At the time of the impacts, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. A passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14618)Incident
On April [XXX], 2026 at 9:24 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] when an SUV traveling northbound on [XXX], without activated headlights, maneuvered to the left and entered the Waymo AV's lane of travel. The Waymo AV began to slow to yield to the SUV as the SUV continued to approach, and the left side of the SUV made contact with the left side of the Waymo AV. As a result of this contact, the Waymo AV was pushed to the right and the front right tire of the Waymo AV made contact with the left side of a passenger car parked facing south on the west curb of 47th Avenue. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV and the SUV sustained damage. The passengers of the Waymo AV were transported to a hospital by an ambulance, alleging minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because individuals involved were transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14627)Incident
On April [XXX], 2026 at 8:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling northeastbound on [XXX] when an SUV traveling southwestbound on [XXX] crossed the solid double yellow lane lines and entered the Waymo AV's lane of travel. The Waymo AV braked and maneuvered to the right to yield to the SUV as the SUV continued forward, and the front of the SUV made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the SUV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-15063)Incident
A Zoox vehicle operating in autonomous mode was stopped behind traffic at a red signal on northbound [XXX] at [XXX] in San Francisco. At this time, a passenger vehicle (Vehicle 2) was reversing from a parking spot on the left side of the roadway. The Zoox vehicle honked at the approaching Vehicle 2, but Vehicle 2's rear end made contact with the Zoox vehicle's driver door. The Zoox vehicle operator then disengaged from autonomous mode. The Zoox vehicle sustained minor damage. No injuries were reported, and police were not notified.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-15062)Incident
An occupied Zoox autonomous vehicle traveling north on [XXX] was stopped for a signal at [XXX] in San Francisco, with a passenger vehicle (Vehicle 2) stopped directly behind it. As the light turned green, the Zoox vehicle began to proceed but stopped for traffic and was rear ended by Vehicle 2. Vehicle 2's driver immediately left the scene without exchanging information. Shortly after, the Zoox vehicle proceeded straight and pulled over in the right lane adjacent to the bike lane, and the passengers exited. One passenger reported feeling "whiplash" but declined medical treatment. The police were notified. The Zoox vehicle sustained minor rear-end damage.
- Four Zoox robotaxis stalled on Hacienda Avenue near the Las Vegas Strip, blocking traffic lanesIncident
Four Zoox robotaxis stalled on Hacienda Avenue near Sorrel Street in Las Vegas, taking up most of the two eastbound travel lanes. Las Vegas Metro police responded to the scene, with traffic forced to navigate around the cluster of stationary self-driving vehicles. Zoox stated the incident was caused by external third-party interactions, not a software issue.
- ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-14483)Incident
On March [XXX], 2026 at 8:35 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped facing southeast in the leftmost lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a pickup truck traveling southeastbound in the leftmost lane on [XXX] slowed as it approached the Waymo AV from behind, and the front of the pickup truck made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance, alleging minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Austin, TX involving a TOYOTA Highlander (NHTSA SGO 30610-14264)Incident
A Zoox vehicle operating in autonomous mode, traveling southwest on [XXX] towards [XXX] in Austin, was slowing for a garbage truck (Vehicle 2) approaching from the opposite direction when Vehicle 2 struck it head-on. The Zoox vehicle sustained moderate damage to the left front area, including the hood, bumper, headlight, fender, A-pillar hinge, and driver door. Both parties exchanged information. Police were notified and arrived at the scene. No injuries were reported.
- ADS crash report in Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14389)Incident
On March [XXX], 2026 at 7:59 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Inglewood, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing south on [XXX] in a queue of traffic for a stop sign at the intersection with [XXX]. As traffic ahead advanced, the Waymo AV slowly proceeded forward in the queue of traffic, and an SUV traveling southbound on [XXX] approached the Waymo AV from behind, and the front right side of the SUV made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14263)Incident
An occupied Zoox autonomous vehicle traveling southeast on [XXX] stopped behind traffic in the outer left turn lane (lane #2) for a red traffic signal at [XXX] in Las Vegas. A dumpster-hauling truck (Vehicle 2) was stopped in the adjacent through-lane (lane #3). Shortly after the light turned green and the Zoox vehicle began its left turn, the Vehicle 2 operator abruptly steered left, accelerated, and cut into the Zoox vehicle's path, violating its right of way. The Zoox vehicle braked hard; however, Vehicle 2 struck the Zoox vehicle's right-side front wheel, fender, roof-mounted sensor unit, and body panel. The Zoox vehicle was towed from the scene and sustained moderate damage. No injuries were reported, and police were not called.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14342)Incident
An unoccupied Zoox autonomous vehicle was traveling northeast on [XXX], approaching [XXX] in Las Vegas, when a passenger car (Vehicle 2) abruptly turned right onto [XXX] from a parking lot on the right, violating the Zoox vehicle's right-of-way. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The Zoox vehicle's right front fender and wheel, and its right rear door panel, contacted Vehicle 2's left fender, wheel, headlight, and quarter panel. Both vehicles sustained damage, and the Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14366)Incident
An occupied Zoox autonomous vehicle was traveling east at low speed in a parking lot along [XXX] in Las Vegas when an SUV (Vehicle 2) began reversing out of its parking spot. The Zoox vehicle slowed and attempted to steer left, but it could not before Vehicle 2 struck the Zoox vehicle's right-side rear door, body panel, and wheel. The Zoox vehicle sustained moderate damage and was towed from the scene. No injuries were reported, and police were not notified.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14519)Incident
An unoccupied Zoox autonomous vehicle started to move after a gradual stop at a 3-way stop sign preparing to turn right onto eastbound [XXX] in Las Vegas, when it braked to an abrupt stop as cross-traffic failed to stop and yield the right-of-way. It was then rear ended by an SUV (Vehicle 2) traveling directly behind. The Zoox vehicle was towed from the scene and was found to have sustained moderate damage to the rear. No injuries were reported and police were not notified. Camera footage from the Zoox vehicle shows that the Vehicle 2 driver was not looking ahead at the roadway before the time of contact.
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14387)Incident
On March [XXX], 2026 at 1:20 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a first responder vehicle on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it slowed to a stop at a sign at the intersection with [XXX]. While the Waymo AV was stopped, an active emergency vehicle with emergency lights activated traveling eastbound on [XXX] approached the intersection, and the Waymo AV began to move a short distance to the right to create additional room for the emergency vehicle to pass to the Waymo AV's left before coming to a stop to yield to the oncoming emergency vehicle. While the Waymo AV was stopped, the emergency vehicle continued to exit the intersection along [XXX] and proceeded to pass the Waymo AV to the left. As the emergency vehicle was passing the Waymo AV, the left side of the emergency vehicle made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Miami, FL involving a TOYOTA Highlander (NHTSA SGO 30610-14554)Incident
A Zoox vehicle in autonomous mode was traveling east on [XXX] toward [XXX] in Miami when the operator of a wrong-way-parked semi-trailer suddenly swung open the rear door of the trailer into the path of the approaching Zoox vehicle. The door struck the Zoox vehicle's right-side A-pillar, windshield, and sensor assembly. After the impact, the trailer's door rebounded and struck the operator behind it. The Zoox vehicle operator then disengaged from autonomous mode. The police and emergency personnel arrived at the scene. The operator was transported by an ambulance from the scene.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14287)Incident
On March [XXX], 2026 at 9:06 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing south in the third from the right lane on [XXX] for a red light at the intersection with [XXX] when an active emergency vehicle, with emergency lights activated, traveling westbound on [XXX] proceeded straight through the intersection. After the traffic light turned green, the Waymo AV proceeded forward a short distance and came to a stop momentarily before entering the intersection, as it detected a siren from an emergency vehicle. The Waymo AV began to proceed straight and a passenger car initially stopped behind the Waymo AV approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14425)Incident
On March [XXX], 2026 at 8:56 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX]at a low rate of speed, with vehicles parked at the curb in both directions and active emergency vehicles stopped on both sides of the roadway facing east. The Waymo AV maneuvered to the right and slowed to a stop in-lane to yield to an active ambulance, which was initially stopped, as the ambulance began traveling eastbound on [XXX]. While the Waymo AV was stopped, the ambulance proceeded to pass the Waymo AV to the left, and the left side of the ambulance made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14663)Incident
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling west on [XXX] past [XXX] in San Francisco when it encountered a Pickup truck reversing into its lane from a perpendicular parking spot ahead. The Zoox vehicle slowed to a stop, and while it waited for the lane to clear, a passenger car (Vehicle 2) began to reverse. The Zoox vehicle honked at Vehicle 2, but Vehicle 2 continued to reverse and made contact at low speed with the passenger-side front door of the Zoox vehicle. The Zoox vehicle operator then disengaged from autonomous mode. Both vehicles sustained damage. No injuries were reported, and the police were not notified.
- ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14665)Incident
A Zoox vehicle (Vehicle 1) operating in autonomous mode was stopped behind traffic in the through lane on westbound [XXX] at a red traffic light at [XXX] in San Francisco with a passenger car (Vehicle 2), stopped directly ahead. After both vehicles were fully stopped, Vehicle 2 began moving backward toward the still-stopped Zoox vehicle, and even though the Zoox vehicle honked its horn, Vehicle 2 continued to move backward and made contact with the Zoox vehicle's front bumper. The Zoox vehicle operator then disengaged from autonomy. The Zoox vehicle sustained minor damage. No injuries were reported, and police were not notified.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14388)Incident
An unoccupied Zoox autonomous vehicle (Vehicle 1), traveling southwest on [XXX] in San Francisco, was stopped mid-way through a lane-change maneuver (from lane #2 to lane #1) in stop-and-go traffic, when a passenger car (Vehicle 2) in lane #1 accelerated toward the stopped Zoox vehicle and struck its left front wheel. The Zoox vehicle was towed from the scene for inspection and was found to have sustained no damage. Vehicle 2's front bumper appears to have sustained minor damage. No injuries were reported. Police were notified but did not arrive at the scene. The Zoox vehicle's video footage shows that Vehicle 2's driver was not looking at the road ahead before or at the time of contact.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14419)Incident
A Zoox autonomous vehicle, traveling west on [XXX] toward [XXX] in San Francisco, stopped next to parked vehicles with active hazard lights to pick up a passenger. Just after the passenger entered the Zoox vehicle, a passenger car (Vehicle 2) traveling behind attempted to pass on the left and swiped the Zoox vehicle's left rear fender. The Zoox vehicle was towed from the scene and was found to have sustained minor damage. No injuries were reported, and police were not notified.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14664)Incident
An unoccupied Zoox autonomous vehicle (Vehicle 1), traveling northeast on [XXX] toward [XXX] in San Francisco, stopped next to parked vehicles with active hazard lights to pick up a passenger. Shortly after, one of the parked vehicles (Vehicle 2) was attempting to pull out of the parking spot when the Zoox vehicle's passenger approached and activated its doors. The Zoox vehicle's right rear door contacted Vehicle 2's front bumper. The right rear door on the Zoox vehicle was damaged; no injuries were reported, and police were not notified.
- ADS crash report in Washington, DC involving a JAGUAR I-PACE (NHTSA SGO 30270-14625)Incident
On March [XXX], 2026 at 7:27 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound in the rightmost lane on [XXX] when it began to slow for an emergency vehicle siren from an ambulance traveling northbound. While the Waymo AV was slowing, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
- Waymo robotaxi blocked an ambulance responding to Austin mass shootingIncident
A Waymo robotaxi picking up a passenger near the scene of a mass shooting on West Sixth Street in Austin stopped and completely blocked a street, preventing an ambulance from reaching the scene. An Austin police officer had to manually direct the vehicle away. Austin-Travis County EMS confirmed the vehicle briefly interfered with ambulance access.
- Waymo robotaxi struck in hit-and-run collision on first day of Charlotte operationsIncident
On Waymo's first day of operations in Charlotte, NC, a manually driven Waymo vehicle with a human trainer aboard was struck by another vehicle in a hit-and-run on the 500 block of W. Fourth Street near Truist Field. The other vehicle crossed a double yellow line, cut off the Waymo, then reversed into it before fleeing. No injuries reported and the Waymo vehicle sustained no damage. Charlotte-Mecklenburg Police Department filed an incident report.
- ADS crash report in Las Vegas, NV involving a HYUNDAI Ioniq 5 (NHTSA SGO 30410-14092)Incident
On February [XXX], 2026, at approximately 9:55 AM PT, a Motional Ioniq 5 AV (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a safety driver in the driverâs seat. The AV was stopped southbound on [XXX] in the left-turn lane at the intersection with [XXX], positioned behind two other stopped vehicles. At that time, a sedan traveling eastbound on [XXX] was being actively pursued by a law enforcement vehicle which had its flashing lights and siren activated. Both vehicles turned left and proceeded northbound on [XXX] but using the southbound lanes. As the sedan traveled in the wrong lanes on [XXX], it struck the passenger-side front end and right wheel well of the Motional vehicle which remained stopped in the left turn lane the entire time. The sedan did not stop after striking the Motional vehicle and continued traveling in the wrong (southbound) lanes and counter to the flow of traffic while it continued fleeing from police. No occupants of the Motional vehicle were injured. The Motional vehicle sustained damage to the front end and was towed from the scene. The Las Vegas Metropolitan Police Department is investigating the incident, but a police report is not yet available
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14340)Incident
An occupied Zoox autonomous vehicle traveling south on [XXX] was stopped for a red signal at [XXX] in Las Vegas. After the light turned green, and before the Zoox vehicle started to move, a Pickup (Vehicle 2) traveling directly behind it rear-ended it. Shortly thereafter, both vehicles traveled a few feet ahead and pulled over. The passengers exited the Zoox vehicle onto the sidewalk. After exchanging information, the Zoox vehicle returned to base for inspection, where it was found to have sustained moderate damage. No injuries were reported, and police were not notified.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14341)Incident
An occupied Zoox autonomous vehicle was traveling northeast on [XXX], passing through the intersection of [XXX] in Las Vegas, with a green signal, when an SUV (Vehicle 2) violated the Zoox vehicle's right of way and abruptly entered its travel path. The Zoox vehicle braked hard and attempted to veer left, but the right front fender of the Zoox vehicle made contact with the left front fender and bumper of Vehicle 2. The driver of Vehicle 2 briefly stopped and then drove away from the scene. The Zoox vehicle was found to have sustained minor damage. At the time of the incident, the passengers did not report any injuries, and police were not notified. On March 2, 2026, the passengers notified Zoox Support that they "sustained multiple injuries and have experienced persistent and worsening pain and cognitive symptoms since the impact".
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14118)Incident
On February [XXX], 2026 at 2:50 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was stopped facing southwest in the rightmost lane on [XXX] for an SUV which was in a prior collision stopped facing southeast, partially in the rightmost lane on [XXX] and partially on the curb. While the Waymo AV was stopped, an active emergency vehicle with emergency lights activated traveling eastbound on [XXX] proceeded to turn left onto [XXX] and travel northeastbound in the adjacent lane to the Waymo AV, against the proper direction of traffic. The emergency vehicle proceeded to pass the Waymo AV to the left and began to maneuver towards the curb on its left, and the left side of the emergency vehicle made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger in the Waymo AV was not belted at the time of the collision. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14003)Incident
On February [XXX], 2026 at 11:06 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was parked at the curb facing north on [XXX] with its hazard lights activated for a passenger drop-off. While the Waymo AV was parked, a passenger in the Waymo AV opened the rear right side door in preparation to exit the vehicle. A van traveling northbound on [XXX] in the right lane accelerated as it approached the Waymo AV from behind, and the front of the van made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. A passenger in the Waymo AV was unbelted at the time of the collision as they were preparing to exit the vehicle. Both passengers of the Waymo AV were transported to a hospital by an ambulance, one of the passengers had minor injuries and one of the passengers had moderate injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14075)Incident
On February [XXX], 2026 at 2:12 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was parked in-lane facing northeast near the south curb on [XXX] with its hazard lights activated for a passenger pickup. While the Waymo AV was stopped, the two Waymo AV passengers approached the Waymo AV, opened the rear right door, and one of the passengers entered the Waymo AV. While the other passenger was standing outside of the Waymo AV at the open rear right door, a passenger car traveling northwestbound on [XXX] proceeded straight into the intersection with [XXX] without stopping at the stop sign on [XXX], and the front of the passenger car made contact with the Waymo AV passenger and the right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passengers of the Waymo AV were not belted at the time of collision as they were in the process of entering the vehicle. The passenger that was standing outside of the Waymo AV reported minor injuries and was transported to a hospital by an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle was towed from the scene. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14152)Incident
A Zoox vehicle (Vehicle 1) operating in autonomous mode came to an abrupt stop on [XXX] just after turning left from northbound [XXX] in San Francisco, and was rear ended by a passenger vehicle (Vehicle 2) traveling directly behind it. The Zoox vehicle operator disengaged from autonomy after the impact. There were no reported injuries, and police were not called. The Zoox vehicle was towed from the scene and was found to have sustained moderate damage to its rear end.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14026)Incident
An unoccupied Zoox autonomous vehicle was traveling east on [XXX] toward [XXX] in San Francisco when an SUV (Vehicle 2) that had been stationary while in an apparent attempt to parallel park along the right curb suddenly pulled out into the path of the approaching Zoox vehicle. The Zoox vehicle braked hard and attempted to steer left, but the right front wheel and body panel of the Zoox vehicle made contact with the left front wheel and panel of Vehicle 2. The Zoox vehicle was towed from the scene for inspection and was found to have sustained minor damage. There were no reported injuries, and police were not notified
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14339)Incident
An unoccupied Zoox autonomous vehicle was traveling in the right lane on northwest-bound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. Partway through the right turn, the Zoox vehicle further slowed to yield to a pedestrian crossing [XXX], and at that time, a cyclist traveling northwest on the adjacent sidewalk rapidly entered the crosswalk. The Zoox vehicle braked to yield to the approaching cyclist, and the cyclist made contact with the right rear side of the nearly stopped Zoox vehicle. The bicycle fell to the ground, but its rider remained upright. The cyclist picked up their bicycle and rode away from the scene. Shortly after, the Zoox vehicle resumed operation to return to base. There was minor damage to the Zoox vehicle. There were no reported injuries, and police were not notified.
- ADS crash report in Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14167)Incident
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling southeast on [XXX], preparing to change lanes to the right to turn onto [XXX] in Santa Monica, when it was hit on the right rear corner (rear bumper, hatch, right rear wheel, and right rear quarter panel) by an SUV (Vehicle 2). The Zoox vehicle stopped facing southwest on [XXX], with the front of Vehicle 2 still engaged with the right rear of the Zoox vehicle. The Zoox vehicle sustained severe rear damage, including damage to data recording systems. Vehicle 2 had major damage to its front end. Airbags deployed in both vehicles, and they were towed from the scene. Police and emergency responders arrived to assist, and the driver of vehicle 2 was detained. The Zoox vehicle operator and two passengers reported soreness and a headache after the collision.
- ADS crash report in Scottsdale, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-13955)Incident
On February [XXX], 2026 at 7:09 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane. A passenger car traveling northbound in the second to the left lane, in front of and to the left of the Waymo AV, began to slow and change lanes to the right when a second passenger car made contact with the rear right side of the first passenger car. The second passenger car continued forward and made contact with an SUV stopped in the queue of traffic in the second from the left lane. As a result of the initial contact with the second passenger car, the first passenger car was pushed east across two lanes of travel, and entered the Waymo AV's lane of travel. The Waymo AV slowed and maneuvered to the right to avoid the oncoming passenger car and the front left side of the passenger car made contact with the left side of the Waymo AV. The Waymo AV rotated to the left and came to rest facing southwest in the second and third from the left lanes. During two subsequent maneuvers in which the Waymo AV pulled forward and to the right in an attempt to navigate off the freeway, the front left corner of the Waymo AV made contact with an "Oversized Load" sign attached to a heavy truck stopped in the second from the left lane. At the time of all impacts, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All involved vehicles sustained damage. The driver of the first passenger car was transported to a hospital by an ambulance with unknown injuries, and the passenger of the Waymo AV alleged minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- Zoox robotaxi struck an opening car door in San Francisco, injuring a street ambassadorIncident
On January 17, 2026, around 2 p.m., a Zoox robotaxi in San Francisco collided with a suddenly-opened parked-car door, injuring a street ambassador (Jamel Durden, per reporting). The San Francisco Police Department opened an investigation and the California DMV reviewed the incident; Zoox filed a mandatory crash report. The collision raised questions about Zoox's edge-case detection as it expanded early-rider programs in SF and Las Vegas, adding to a pattern of recalls and operational issues.
- ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13853)Incident
On January [XXX], 2026 at 7:48 AM, a May Mobility Autonomous Vehicle (AV) was in a collision with a fire hydrant in Atlanta, Georgia on [XXX]near[XXX]. The May Mobility AV was traveling westbound on [XXX]in Atlanta, Georgia with its automated driving system engaged in autonomy mode when the Autonomous Vehicle Operator (AVO) fell asleep while his right hand rested on the right side of the steering wheel. In-cabin video and telematics confirms that the AVO's hand restricted the motion of the steering wheel, preventing the autonomous system from keeping the vehicle in its lane. Though the AV braked after perceiving the exit from its travel lane, collision with the fire hydrant could not be avoided. The air bags deployed during the collision and the AV was towed from the scene. The AVO was transported by ambulance to the hospital with minor injuries.
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13664)Incident
On January [XXX], 2026 at 6:54 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southeastbound on [XXX] in the second from the right lane for a green light when it began to slow to yield to a uniformed police officer standing partially in the roadway to the right of the Waymo AV, directing traffic at the intersection with [XXX]. While the Waymo AV was slowing, it began to change lanes to the rightmost lane, and the light turned yellow. The Waymo AV slowed to a stop before entering the intersection, partially in the rightmost lane, and an SUV that was traveling behind the Waymo AV in the second from the right lane approached the Waymo AV from behind and maneuvered to the left, and the front right side of the SUV made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14025)Incident
On January [XXX], 2026 at 6:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing northeast on [XXX] in the third from the right lane for a red light at the intersection with [XXX]. When the light turned green, the Waymo AV proceeded a short distance and then slowed down before entering the intersection to yield to an active emergency vehicle traveling northeastbound on [XXX] against the proper direction of traffic with its emergency lights activated. While the Waymo AV was stopped, an SUV that was initially stopped directly behind the Waymo AV proceeded forward, and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14090)Incident
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling northeast on [XXX] toward [XXX] in San Francisco. At that time, an SUV (Vehicle 2) traveling ahead pulled into the parking lane on the right. Just as the Zoox vehicle was approaching, Vehicle 2 suddenly swerved into the Zoox vehicle's lane without using a turn signal. The Zoox vehicle braked hard and attempted to steer left to avoid the collision. The vehicle operator then disengaged autonomy and continued braking, but contact was unavoidable. The left front of Vehicle 2 struck the right front of the Zoox vehicle. The Zoox vehicle sustained moderate damage, and the right rear passenger reported "experiencing soreness" after the collision. The police were not called.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13662)Incident
An unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling east on [XXX] near [XXX] in San Francisco. It began to slow down for a stopped box truck (Vehicle 2) in the same lane, which had an open liftgate. As the Zoox vehicle was preparing to maneuver around, Vehicle 2 began to reverse. The Zoox vehicle came to a stop however, Vehicle 2 continued reversing. The Zoox vehicle honked, but Vehicle 2's open liftgate made contact with the right front fender and front fascia of the Zoox vehicle. The Zoox vehicle was towed from the scene and was found to have sustained minor damage. The police were notified, and no injuries were reported.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13818)Incident
An occupied Zoox autonomous vehicle began to proceed on a fresh green traffic signal on westbound [XXX] at [XXX] when the driver of a stationary passenger vehicle (Vehicle 2), parallel-parked in the curb lane, rapidly opened the driver door into the path of the approaching Zoox vehicle. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The right side front fender, wheels, bodyside, and door panels made contact with the outside edge of the opening door of Vehicle 2. The Zoox vehicle came to an immediate stop and was later towed from the scene to be inspected for damage. First responders arrived at the scene. The passenger of the Zoox vehicle did not report any injuries. Later media stories reported the driver of Vehicle 2 had a "smashed hand" and his "hand was hurting, and that he was also experiencing pain to his neck area and lower back" based on a third party's account, and that the driver "declined their offer to take him to the hospital." Zoox vehicle camera footage shows clearly that no part of the robotaxi came into contact with the driver themselves, and that their hands, leg, and body did not interact with either the robotaxi or the parked vehicle's door at any moment during the contact event.
- Waymo robotaxi drove past emergency flares into active fire scene in HollywoodIncident
A Waymo robotaxi on Melrose Avenue in Hollywood took a wrong turn and drove past LAFD road flares into an active fire scene near Van Ness, where the Los Angeles Fire Department had blocked the street. The vehicle had at least one passenger in the backseat and remained inside the closure for approximately 10 minutes before making a U-turn and leaving. No injuries were reported.
- ADS crash report in Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-13488)Incident
On December [XXX], 2025 at 10:24 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the right lane on [XXX] when a passenger car that was initially stopped facing north on [XXX], to the right and in front of the Waymo AV, proceeded forward into the intersection at [XXX]. As the passenger car entered the intersection the front of the passenger car made contact with the right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passengers of the Waymo AV were transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-13287)Incident
On December [XXX], 2025 at 4:45 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped facing northwest in the second from the right lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. After the traffic light turned green and traffic ahead advanced, the Waymo AV proceeded a short distance and came to a stop because of the detection of a potential nearby emergency vehicle. A pickup truck that was initially stopped directly behind the Waymo AV proceeded forward, and the front of the pickup truck made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV alleged a minor injury. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-13449)Incident
On December [XXX], 2025 at 3:17 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing east in the fourth from the right lane on [XXX] for a red light at the intersection with [XXX]. When the traffic light turned green, the Waymo AV proceeded a short distance and then slowed down before entering the intersection to yield to an active emergency police vehicle traveling southbound on [XXX] near [XXX] with emergency lights activated. While the Waymo AV was stopped, an SUV that was initially stopped directly behind the Waymo AV proceeded forward and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13302)Incident
On December [XXX], 2025 at 2:14 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a first responder vehicle on [XXX] at [XXX]. The Waymo AV was stopped facing south in the second from the right lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an active fire truck with sirens activated traveling westbound on [XXX] proceeded to turn right to travel north in the rightmost southbound lane of [XXX], to the right of the Waymo AV. The Waymo AV began to move a short distance to the left to create additional room for the fire truck to pass to the AV's right before coming to a stop to yield to the oncoming fire truck. While the Waymo AV was stopped, the fire truck continued to complete the right turn and the right side of the fire truck made contact with the rear right side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13491)Incident
On December [XXX], 2025 at 9:48 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was stopped at the curb facing southeast on [XXX] with its hazard lights activated for a passenger dropoff. While the Waymo AV was stopped, a van traveling southeastbound on [XXX] maneuvered to the right and approached the Waymo AV from behind, and the front of the van made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Palo Alto, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13378)Incident
On December [XXX], 2025 at 8:26 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Palo Alto, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was traveling northwestbound in the rightmost lane on [XXX] with its right turn signal activated and preparing to make a right turn at a green light onto [XXX]. As the Waymo AV began initiating the right turn, the Waymo AV came to a stop within the crosswalk to yield to a cyclist. The cyclist was traveling southbound on the east sidewalk of [XXX] and entered the crosswalk across [XXX] against a red pedestrian crosswalk light. As the cyclist entered the crosswalk, the front tire of the bicycle made contact with the right side of the stationary Waymo AV and the cyclist fell to the ground. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The cyclist was transported to a hospital in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13495)Incident
On December [XXX], 2025 at 1:41 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing northeast on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling northeastbound on [XXX] approached the Waymo AV from behind, and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13539)Incident
On December [XXX], 2025 at 1:21 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] at [XXX]. The Waymo AV was stopped facing east in the left lane on [XXX] for a red light at the intersection with [XXX]. A fire engine with lights and siren activated traveling northbound in the leftmost lane on [XXX] proceeded straight through the intersection with [XXX] before stopping, then reversing into the intersection. The fire engine then proceeded to turn left onto [XXX]. The Waymo AV moved slightly to the right within its lane, then came to a stop to yield to the oncoming fire engine. While the Waymo AV was stopped, the fire engine continued to complete the left turn and the left side of the fire engine made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13660)Incident
An unoccupied Zoox vehicle (Vehicle 1) was stationary in the right lane on northeast-bound [XXX] at [XXX] in San Francisco, stopped behind traffic at a red light. After the light turned green, the Zoox vehicle initially remained stopped to yield to an active police vehicle making a right turn onto [XXX] from the adjacent lane. During the subsequent green light cycle, as the Zoox vehicle began to proceed straight along [XXX], two passenger cars, including Vehicle 2, cut across its path from behind, attempting an illegal right turn onto [XXX] from a through lane. The Zoox vehicle braked hard, but contact was unavoidable, and Vehicle 2 clipped the Zoox vehicle's left front fender. The front-seat passenger of Vehicle 2 exited to inspect the Zoox vehicle before returning to their car and leaving the scene without exchanging information. The Zoox vehicle then cleared the scene and returned to base. Upon inspection, the Zoox vehicle was found to have sustained minor damage. Police were notified, and no injuries were reported.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13661)Incident
An occupied Zoox autonomous vehicle (Vehicle 1) was traveling west on [XXX] past [XXX] when it encountered debris in the lane. The Zoox vehicle braked hard for the debris and was then rear ended by a close-following Pickup (Vehicle 2) that was abruptly merging into the lane directly behind the Zoox vehicle. The Vehicle 2 driver then reversed and left the scene without attempting to exchange information. Shortly after, the Zoox vehicle cleared the scene, turned right onto [XXX], and pulled over to allow the riders to exit the vehicle. The Zoox vehicle then returned to base for inspection and was found to have sustained moderate damage. There were no reported injuries, and the police were notified.
- ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-13060)Incident
On November [XXX], 2025 at 12:37 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing southwest in the designated left turn lane on [XXX] at the intersection with [XXX] with hazard lights activated. A passenger car traveling northeastbound on [XXX], in the Waymo AV's lane of travel and against the proper direction of traffic, approached the front of the Waymo AV, and the front left side of the passenger car made contact with the front left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the passenger car alleged minor injuries and was transported to a hospital in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-13376)Incident
An occupied Zoox autonomous vehicle (Vehicle 1) was stopped behind traffic in the left turn lane on southbound [XXX] at [XXX] in Las Vegas, waiting at a traffic signal. After the light turned green, the Zoox vehicle initially remained stationary and then started moving forward. Shortly after resuming motion, the Zoox vehicle stopped and was rear-ended by the SUV (Vehicle 2) directly behind it. The Zoox vehicle sustained minor damage, and no injuries were reported. The police were not called.
- ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13167)Incident
On November [XXX], 2025 at 4:52 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northeastbound on [XXX], with its right turn signal activated, when it slowed to a stop for a stop sign at the intersection with [XXX]. The Waymo AV proceeded forward slowly as it was yielding to vehicles traveling southeastbound on [XXX] and preparing to turn right onto [XXX]. While the Waymo was proceeding forward, a passenger car traveling northeastbound on [XXX] approached the Waymo AV from behind and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV was not belted at the time of the collision. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Miami, FL involving a TOYOTA Highlander (NHTSA SGO 30610-13377)Incident
A Zoox retrofitted test vehicle (Vehicle 1) in autonomous mode was stopped, yielding to cross-traffic, on westbound [XXX] at [XXX] in Miami while waiting for an opportunity to proceed through the intersection and continue west on [XXX]. The Zoox vehicle inched forward and then stopped again for cross-traffic. The Zoox vehicle operator then disengaged from autonomous mode and proceeded to begin to cross [XXX]. While crossing, a motorcyclist traveling northbound on [XXX] at a high rate of speed collided with the driver's side front fender and door of the Zoox vehicle. The motorcycle and its operator fell to the ground. After the collision, the Zoox vehicle operator cleared the intersection and pulled over. Both the Zoox vehicle and the motorcycle sustained damage. Police and EMT personnel arrived at the scene, but the motorcycle operator was not transported from the scene.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13065)Incident
On November [XXX], 2025 at 1:03 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing north on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling northbound on [XXX] came to a stop directly behind the Waymo AV. While both the Waymo AV and the SUV were stopped, a passenger car traveling northbound on [XXX] approached the stopped SUV from behind and the front of the passenger car made contact with the rear of the SUV, and then the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV, the SUV, and the passenger car sustained damage. The driver of the passenger car alleged injuries and was transported to a hospital by an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13201)Incident
On November [XXX], 2025 at 6:08 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] and came to a stop to yield to a police SUV that was traveling southbound on [XXX] and had stopped in-lane. While the Waymo AV was stopped, the police SUV reversed and the rear of the police SUV made contact with the front of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Scottsdale, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-12051)Incident
On November [XXX], 2025 at 2:13 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] when an SUV traveling eastbound on [XXX] crossed the center dashed yellow line and entered the Waymo AV's lane of travel, and the front left side of the SUV made contact with the front left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the SUV alleged injuries and was transported to a hospital by an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-13192)Incident
On November [XXX], 2025 at 5:31 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing south on [XXX] for a stop sign at the intersection with [XXX] with its right turn signal activated in preparation for a right turn. While the Waymo AV was stopped, a passenger car traveling southbound on [XXX] approached the Waymo AV from behind at a high rate of speed and began to maneuver to the left, and the front right side of the passenger car made contact with the rear left side of the stationary Waymo AV. The front of the passenger car then made contact with the rear of a second passenger car that was stopped at the stop sign in front of and to the left of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage. The driver of the second passenger car was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-11841)Incident
On October [XXX], 2025 at 9:55 AM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and came to a stop at the stop sign at the intersection with [XXX]. A passenger car traveling directly behind the Waymo AV proceeded without stopping, and the front driver side of the passenger car then made contact with the rear side of the stationary Waymo AV. First responders arrived at the scene and assisted the rider out of the Waymo AV. An ambulance was called to the scene and Waymo later learned that the rider was transported to the hospital. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger in the Waymo AV was not belted at the time of the collision they were in the process of locating the belt fastener for the seat they were occupying. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Las Vegas, NV involving a HYUNDAI Ioniq 5 (NHTSA SGO 30410-12017)Incident
On October [XXX], 2025, at approximately 2:30 PM PT, a Motional AV with VIN [XXX] was operating in autonomous mode in Las Vegas, Nevada, with a safety driver in the drivers seat. The vehicle was traveling northbound on [XXX] in the second of four lanes from the left, approaching the intersection with [XXX]. While stopped at a red traffic signal, an adult male pedestrian began crossing [XXX] from the west side of the street, several hundred feet away from a designated crosswalk. The pedestrian proceeded southbound across multiple lanes and paused on a median located ahead and to the left of the AV. The AV detected and classified the pedestrian the entire time. When the traffic signal turned green, the pedestrian remained stopped on the median. Given that the pedestrian remained stopped in place, the AV began to move forward slowly at approximately 2.5 mph and continued to correctly detect and classify the pedestrian. The pedestrian, holding what appears to be an item in a plastic bag, suddenly stepped into the far-left turn lane ahead of the AV, the AV immediately came to a complete stop still in the second lane. The pedestrian continued crossing, making a light physical contact with the rear driverâs side of the vehicle before continuing across the remaining three lanes of traffic still outside of the crosswalk. The vehicle operator then disengaged the autonomous system and pulled over to complete an incident report. No police were notified. There were no injuries, no damage, and no airbag deployments. The pedestrian did not stop at the scene and the identity of the pedestrian is unknown.
- ADS crash report in Las Vegas, NV involving a TOYOTA Highlander (NHTSA SGO 30610-11990)Incident
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling east towards the Passenger Pick-up area in Terminal 3 of [XXX] in Las Vegas. An SUV (Vehicle 2), traveling behind in the left adjacent lane, abruptly attempted to overtake and cut in front of the Zoox vehicle in an apparent attempt to change lanes to the right towards Terminal 3 Departures. The Zoox vehicle braked hard in response to the encroaching vehicle, and the operator then disengaged from autonomy and continued to brake, but contact could not be avoided. The right rear side of Vehicle 2 swiped the left front area of the Zoox vehicle. Both operators stopped after the collision and exchanged information. Both vehicles sustained moderate damage, and the Zoox vehicle was subsequently towed from the scene. There were no reported injuries, and police were not called.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-11847)Incident
An unoccupied Zoox autonomous vehicle was traveling in the right lane on southbound [XXX] towards [XXX] in Las Vegas. The driver of an SUV (Vehicle 2) traveling ahead in the same direction in the adjacent lane to the left suddenly veered right into the path of the Zoox vehicle without using a turn signal, making contact with the left rear wheel and fender, and left side body panels, doors, and rocker. The Zoox vehicle then gradually braked to a stop in the right lane. The Zoox vehicle was towed from the scene for inspection. The Zoox vehicle sustained moderate damage, while Vehicle 2 appears to have sustained damage to the right side fender panel and front bumper. There were no reported injuries, and the police were not called. Zoox is submitting this updated report to correct a previous reporting error in the location field.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-11856)Incident
An unoccupied Zoox autonomous vehicle was traveling north in the right lane on [XXX], towards [XXX], in Las Vegas, when it encountered a slowing tractor-trailer (Vehicle 2) ahead in its lane, also traveling in the same direction. As the Zoox vehicle gradually slowed to a stop, the operator of Vehicle 2 began to reverse. The Zoox vehicle honked at Vehicle 2, but Vehicle 2 continued to reverse and made contact at low speed with the right front fender and bumper of the Zoox vehicle. The Zoox vehicle was towed from the scene for inspection and was found to have sustained minor damage. There were no reported injuries, and the police were not called.
- ADS crash report in Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11929)Incident
On October [XXX], 2025 at 7:48 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing north in the rightmost lane on [XXX] in a queue of traffic for a red light at the intersection at [XXX]. A passenger car traveling northbound in the rightmost lane on [XXX] slowed to a stop directly behind the Waymo AV. After the traffic light turned green and traffic ahead advanced, the Waymo AV proceeded a short distance and came to a stop before entering the intersection, as it detected a siren from an emergency vehicle. The passenger car also proceeded forward initially and then came to a stop to yield to the Waymo AV. While the Waymo AV and the passenger car remained stopped, a second passenger car traveling northbound on [XXX] approached the first passenger car from behind and the front of the second passenger car made contact with the rear of the first passenger car. The front of the first passenger car then made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV, the first passenger car, and the second passenger car sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11855)Incident
On October [XXX], 2025 at 2:55 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an ambulance on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] with vehicles parked on both sides when it maneuvered towards a driveway opening and came to a stop to yield to an ambulance, which did not have lights or sirens activated, traveling southbound on [XXX]. As the ambulance passed the stationary Waymo AV, the left side of the ambulance made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11861)Incident
On October [XXX], 2025 at 1:27 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane when a passenger car traveling directly behind the Waymo AV approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The two passengers in the Waymo AV alleged minor injuries and were transported to a hospital by an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because individuals involved were transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-13121)Incident
A Zoox vehicle (Vehicle 1) operating in autonomous mode was westbound on [XXX], preparing to make an unprotected left turn onto [XXX] in San Francisco. As the Zoox vehicle slowed approaching the intersection at [XXX], a left-turning vehicle in the oncoming lane accelerated abruptly. The Zoox vehicle braked in response to the oncoming vehicle, and was rear ended by a passenger car (Vehicle 2) traveling directly behind. The Zoox vehicle operator then disengaged from autonomy, and shortly after, continued through the intersection along [XXX] and pulled over to exchange information. The Zoox vehicle sustained minor damage to the rear end, and Vehicle 2 appears to have sustained moderate damage to the left front area and hood. The Zoox vehicle operator and the software operator, seated in the front passenger seat, reported injuries after the collision. The police were not called.
- Motorcyclist killed in Tempe crash involving Waymo robotaxi and hit-and-run driver near ASU campusIncident
On September 14, 2025, at approximately 1:30 AM, a motorcyclist was killed in a multi-vehicle crash near Lemon Street and Rural Road in Tempe, Arizona, near the ASU campus. An unoccupied Waymo robotaxi was making a right turn and yielding to pedestrians when the motorcyclist rear-ended the self-driving car. Within a second, a separate vehicle struck the motorcyclist and fled the scene; police later tracked down the hit-and-run driver, an ASU student. The motorcyclist was transported to the hospital and pronounced dead. Waymo stated it was fully cooperating with law enforcement and regulators. This is the third known fatal incident involving a robocar, occurring approximately 2 miles from the 2018 Uber ATG fatality site.
- ADS crash report in Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-11794)Incident
On September [XXX], 2025 at 2:44 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the second to the left lane. As the Waymo proceeded through a green light at the intersection with [XXX], a passenger car that was traveling westbound in the rightmost lane on [XXX] proceeded through the intersection at [XXX] against a red light without stopping. The front of the passenger car made contact with the left side of a pickup truck that was traveling southbound in the leftmost lane on [XXX]. The right side of the pickup truck then made contact with the left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV, the passenger car, and the pickup truck sustained damage. The passenger in the Waymo AV alleged minor injuries and was transported to a hospital in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, vehicles involved were towed away, and airbags were deployed. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-11850)Incident
On September [XXX], 2025 at 8:40 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southbound in the left lane on [XXX] when it came to a stop at a red light at the intersection at [XXX]. As the traffic light turned green and traffic ahead advanced, the Waymo AV initially proceeded forward and then began to slow before entering the intersection, after detecting a siren from an emergency vehicle. As the Waymo AV was slowing, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-11752)Incident
An unoccupied Zoox autonomous vehicle was operating at a reduced speed in lane #5 on westbound [XXX] towards Las Vegas Boulevard in Las Vegas, with a sedan (Vehicle 2) directly behind. The Zoox vehicle gradually slowed to a stop when it was rear ended by Vehicle 2. Vehicle 2 driver initially exited his vehicle to inspect both vehicles, but did not remain at the scene to exchange information. The Zoox vehicle resumed operation and cleared the scene. Shortly afterward, the Zoox vehicle slowed to a stop due to a low tire pressure fault and was subsequently towed. The low tire pressure was attributed to the crash. The Zoox vehicle sustained minor damage. There were no reported injuries, and the police were not notified.
- ADS crash report in Peachtree Corners, GA involving a TOYOTA Sienna (NHTSA SGO 30413-11593)Incident
The May vehicle was travelling in an autonomous vehicle (AV) only lane approaching an intersection. A vehicle travelling to the left of the May shuttle (ego) in the non-AV lane performed a right hand turn across the May vehicle¢ÃÂÃÂs path. Given the full stopping power and the limited space with which the ego had to stop, the ego was physically unable to stop in time before impact. The primary factor that led to this collision was human error on the part of the other vehicle that was required to yield to through traffic in the AV lane but did not. Right turns across a straight lane are uncommon, and drivers are typically not used to them, however there are several signs that instruct other traffic to yield to the vehicles in the AV lane. There were no autonomy faults or errors which led to this incident. Update: There was no indication of injury or request for medical attention at the scene. The police report states "Driver 1 complained of neck pain." For this reason, we are updating the highest severity injury alleged field to reflect the âminor w/o hospitalizationâ injury level. The remaining content of this report is unchanged from the initial report submitted on September [XXX], 2025, Report ID #[XXX].
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11433)Incident
On August [XXX], 2025 at 2:48 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on a narrow portion of [XXX] with vehicles parked at the curb in both directions when it approached a heavy truck that was traveling northbound on [XXX]. The Waymo AV reversed to yield to the heavy truck and came to a stop at the curb at the intersection with [XXX]. The heavy truck proceeded forward past the Waymo AV and began a left turn onto westbound [XXX] and the left side of the heavy truck made contact with the rear left of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger in the Waymo AV alleged a minor injury and was transported to a hospital in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-11497)Incident
An unoccupied Zoox vehicle in autonomy was traveling north on [XXX] toward [XXX] in San Francisco and slowing for an SUV (Vehicle 2) ahead, also heading north on [XXX]. As the Zoox vehicle approached the nearly stopped Vehicle 2, it steered left to pass. The driver of Vehicle 2 then, without using a turn signal, abruptly began reversing in an apparent attempt to parallel park on the right side of [XXX]. The Zoox vehicle then braked to a near stop when it was struck on the right rear wheel by Vehicle 2 as it swung into a parking space. Shortly afterward, the Zoox vehicle was towed from the scene for inspection. The Zoox vehicle did not sustain damage, but the left front bumper of the SUV appeared to have minor damage. There were no reported injuries, and the police were not called.
- ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-11563)Incident
An unoccupied Zoox autonomous vehicle was stopped at a green traffic light on eastbound [XXX], waiting for traffic ahead to clear to turn left onto [XXX] in San Francisco. A pickup truck (Vehicle 2) was also stopped for the same traffic light, directly behind the Zoox vehicle. After the light turned yellow, the Vehicle 2 driver passed the stopped Zoox vehicle on the left side, striking the left rear fender, and proceeded through the red light. The Vehicle 2 driver did not stop to exchange information. Shortly afterward, the Zoox vehicle turned left onto [XXX] to clear the scene, briefly stopped again, and then pulled over. The Zoox vehicle was then towed for inspection. It sustained minor damage. There were no reported injuries and the police were not called.
- ADS crash report in Santa Monica, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11564)Incident
On August [XXX], 2025 at 10:15 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southeastbound in the left lane on [XXX] when it began to change lanes to the right lane and came to a stop for the red light at the intersection with [XXX] and to yield to law enforcement and emergency vehicles that were blocking vehicles from continuing southeastbound on [XXX]. While the Waymo AV remained stopped partially in the left lane and partially in the bike lane, a law enforcement officer arrived and began to direct traffic around the Waymo AV. A passenger car that was initially stopped behind the Waymo AV proceeded to maneuver around the left of the Waymo AV, and the right side of the passenger car made contact with the rear left of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passenger car sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11696)Incident
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling southwest on [XXX] towards [XXX] in Santa Monica when it was struck on the passenger side by an SUV (Vehicle 2), traveling southeast on [XXX], which failed to yield the right-of-way and entered the Zoox vehicle's travel path. The Zoox vehicle braked, the vehicle operator disengaged, continued to brake, and steered left, but contact was unavoidable. The Zoox vehicle sustained moderate damage, and Vehicle 2 also sustained damage. There were no reported injuries, and the police were not notified.
- ADS crash report in Spring Valley, NV involving a ZOOX Zoox (NHTSA SGO 30610-11587)Incident
An unoccupied Zoox autonomous vehicle was traveling west along [XXX] toward [XXX] in Las Vegas when a tractor-trailer (Vehicle 2) operator failed to yield the right-of-way, failed to stop at a stop sign, and quickly pulled out of a driveway crossing the centerline and entering the Zoox vehicle's travel lane in an apparent attempt to make a left turn onto westbound [XXX]. The Zoox vehicle braked hard and steered right within its travel lane, but contact was unavoidable. The right corner of the front bumper and grille of the tractor-trailer made contact with the left front side of the Zoox vehicle. The Zoox vehicle then came to a complete stop. The operator of Vehicle 2 reversed off the roadway and stayed on-site to exchange information with the Zoox operations team. The Zoox vehicle was towed from the scene for inspection and was found to have sustained moderate damage. The front bumper, hood, and grille on Vehicle 2 appeared to be damaged. There were no reported injuries, and the police were not called.
- ADS crash report in Paradise , NV involving a TOYOTA Highlander (NHTSA SGO 30610-11515)Incident
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling south on [XXX] in the right lane and slowing for a red emergency traffic signal at [XXX] in Las Vegas. Shortly after the Zoox vehicle came to a stop, a pickup (Vehicle 2) following directly behind was rear ended by an SUV (Vehicle 3) that failed to stop. Vehicle 2 then rear ended the stopped Zoox vehicle. The police arrived at the scene. The driver of Vehicle 3 reported that their "head hurt" but declined medical attention. The Zoox vehicle sustained minor damage.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11280)Incident
On July [XXX], 2025 at 9:35 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southwestbound on [XXX] and stopped in the right lane for a red traffic light at the intersection with [XXX]. The traffic light then turned green and the Waymo AV proceeded a short distance before stopping again to yield to an oncoming active emergency vehicle. A passenger car traveling behind the Waymo AV also proceeded from the green light and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The rider of the Waymo AV alleged a minor injury. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11358)Incident
On July [XXX], 2025 at 11:03 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a fire truck vehicle on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] with vehicles parked on both sides when it came to a stop to yield to a fire truck, which did not have lights or sirens activated, traveling southbound on [XXX]. As the fire truck passed the stationary Waymo AV, the driver side of the fire truck made contact with the rear driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11428)Incident
On July [XXX], 2025 at 10:45 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing northwest in the second from the left lane on [XXX] for a red light at the intersection at [XXX]. When the light turned green, the Waymo AV began to move forward momentarily and then stopped to yield to an active emergency vehicle traveling southwestbound on [XXX] with emergency lights activated. While the Waymo AV was stopped, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11514)Incident
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling in the left lane on southwest-bound [XXX] toward [XXX] in San Francisco when a ball, immediately followed by a dog, entered the roadway from between parked cars on the left side of [XXX] directly into the path of the Zoox vehicle. The Zoox vehicle braked in response, but its underbody made contact with the dog. The Zoox vehicle operator then disengaged autonomous mode and brought the vehicle to a stop. The Zoox vehicle operator then reversed the vehicle to free the dog. The dog owner did not indicate injuries to the dog at the scene. The dog and its owner then returned to the sidewalk and the Zoox vehicle operator drove the vehicle from the scene. The police were not called. Zoox subsequently received an email alleging injuries to the dog, "abrasions behind its left front leg and a possible cracked rib."
- ADS crash report in Spring Valley, NV involving a TOYOTA Highlander (NHTSA SGO 30610-11405)Incident
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling south on [XXX] and initiating a left turn from a dedicated signalized turn lane onto [XXX] in Las Vegas with a flashing yellow. The Zoox vehicle operator disengaged just prior to the signal turning from flashing yellow to green arrow as they continued to execute the left turn. At that time, a passenger car (Vehicle 2) traveling north on [XXX] failed to stop for the red traffic signal and entered the intersection at a high speed, colliding with the passenger side of the Zoox vehicle. The side impact caused the Zoox vehicle to roll onto its driver's side. Both vehicles sustained major damage with airbag deployments. The police and EMS arrived at the scene. The Zoox vehicle operator was transported to a medical facility by an ambulance, and Vehicle 2's driver was reported to have declined medical attention. Both vehicles were towed from the scene.
- ADS crash report in Winchester, NV involving a ZOOX Zoox (NHTSA SGO 30610-11513)Incident
An unoccupied Zoox vehicle in autonomous mode was traveling in the right turn lane on southbound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. At that time, an e-cyclist was traveling south on the sidewalk adjacent to southbound [XXX]. As the Zoox vehicle slowed to execute its turn, the e-cyclist rapidly approached the crosswalk in the path ahead of the Zoox vehicle. The Zoox vehicle braked to yield to the approaching e-cyclist. The e-cyclist then veered left and accelerated into the roadway, making contact with the right rear side of the nearly stopped Zoox vehicle. The e-cyclist fell to the ground behind the Zoox vehicle. The Zoox vehicle then started to move and completed the right turn onto [XXX] and completed its mission. The cyclist appears to have ridden away from the scene. A bystander reported the event to Zoox. There was minor damage to the Zoox vehicle, and information was not exchanged with the e-cyclist. The police were later notified.
- ADS crash report in Paradise, NV involving a TOYOTA Highlander (NHTSA SGO 30610-11166)Incident
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling in the left through lane (lane #2) on westbound [XXX], approaching [XXX] in Las Vegas. The Zoox vehicle operator disengaged from autonomy after the traffic light at [XXX] transitioned from green to yellow and braked, bringing the Zoox vehicle to a stop, at which point it was rear-ended by a pickup truck (Vehicle 2) traveling behind. Both vehicles sustained minor damage however, the Zoox vehicle was towed from the scene as its operator was not comfortable driving it back. There were no reported injuries, and the police were not notified.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11192)Incident
On June [XXX], 2025 at 2:27 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing north in the rightmost lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV remained stopped, a passenger car that was stopped in the leftmost lane of [XXX], oriented diagonally relative to the roadway facing northeast after exiting a parallel parking spot at the west side curb of [XXX], proceeded northeastbound into the rightmost lane and the front of the passenger car made contact with the rear driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Neither vehicle sustained damage. A passenger in the Waymo AV reported a minor injury and was transported to a hospital in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11205)Incident
On June [XXX], 2025 at 10:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was stopped facing southeast in the right lane on [XXX] for a red light at the intersection at [XXX] when a Waymo AV passenger opted to end their ride prior to reaching their originally specified drop-off location, prompting the Waymo AV to park in-lane and activate its hazard lights for the passenger drop-off. A cyclist was traveling southeastbound on [XXX] in between vehicles in the right lane and vehicles stopped at the curb. As the cyclist passed the Waymo AV to the right, a Waymo AV passenger opened the front passenger side door and the front passenger side door of the Waymo AV made contact with the cyclist. The passengers in the vehicle were not belted at the time of the collision, as they were preparing to exit the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The cyclist reported minor injuries and was transported from the scene in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11331)Incident
A Zoox vehicle (Vehicle 1), operating in manual mode, was heading south on [XXX], in the southbound lane, approaching [XXX] in San Francisco, when it encountered a passenger car (Vehicle 2) traveling north and occupying both the northbound and southbound lanes on [XXX]. The Zoox vehicle slowed and moved to the right for the oncoming Vehicle 2 however, as Vehicle 2 passed, its driver's side mirror made contact with the driver's side rear of the Zoox vehicle. The driver of Vehicle 2 failed to stop and exchange information. The Zoox vehicle did not sustain any damage, but Vehicle 2 appeared to have sustained minor damage to its driver's side mirror. There were no reported injuries, and the police were not notified.
- Cruise robotaxi collided with an SF fire truck responding to an emergency; one passenger injuredIncident
On Aug 17 2023 a Cruise robotaxi collided with a fire truck running lights and sirens through a San Francisco intersection; one passenger hospitalized. Prompted emergency-vehicle handling software changes; superseded weeks later by the Oct 2023 CA-DMV permit suspension and the eventual wind-down.
- Waymo driverless car blocked San Francisco firefighters working a vehicle fireIncident
The San Francisco Fire Department reported that on August 5, 2023 a driverless Waymo vehicle stopped and parked itself between a fire truck and a burning car near the Legion of Honor, forcing firefighters to walk around the vehicle with a charged hose line to reach the fire. Waymo states that its vehicles are designed to detect emergency vehicles and first responders and to yield. This record is attributed to the SFFD incident report as compiled by Mission Local and to Waymo.
- Cruise driverless car ran over San Francisco Fire Department hose lines during firefighting operationsIncident
The San Francisco Fire Department reported that on May 9, 2023 a driverless Cruise vehicle ran over several lengths of fire hose laid across the 1300 block of Powell Street near Fire Station 2 while crews were working, causing equipment damage the department valued in the thousands of dollars and forcing firefighters to work around the vehicle. Cruise states that its vehicles are built to detect and pull clear of active emergency scenes. This record is attributed to the SFFD incident report as compiled by Mission Local and to Cruise.
- San Francisco firefighter broke a Cruise robotaxi window after it advanced toward an active fire sceneIncident
The San Francisco Fire Department reported that on January 22, 2023 a driverless Cruise vehicle continued advancing toward firefighters working an active scene on the 1300 block of Hayes Street, and a firefighter broke the vehicle's front window after verbal warnings and physical contact failed to stop it. Cruise states that its vehicles are built to detect and yield to emergency scenes and first responders. This record is attributed to the SFFD incident report as compiled by Mission Local and to independent reporting by Forbes.
How the record moved
The same records as a dated timeline, newest first.
- Jul 28, 2026Rep. Kevin Mullin proposes AV Emergency Response Coordination Act requiring national safety standards for autonomous vehiclesOn record
Rep. Kevin Mullin (D-Calif.) unveiled the AV Emergency Response Coordination Act on July 28, 2026, at a press conference in San Francisco with Mayor Daniel Lurie and SF Fire Chief Dean Crispen. The bill would direct NHTSA to develop minimum national emergency response standards for AV operators, require 24-hour hotlines for public officials, and give cities the power to geofence AVs during emergencies. The bill follows a pattern of robotaxis blocking ambulances, driving into active crime scenes, and failing to recognize safety signals.
WaymoTechCrunch - Jul 19, 2026Waymo robotaxi rear-ended by SUV at Sunset Road and Polaris Avenue in Las Vegas, at least one injuredOn record
On July 19, 2026 at approximately 9:45 a.m., a Waymo autonomous vehicle was struck from behind by a dark-colored SUV near Sunset Road and Polaris Avenue in south Las Vegas. The SUV continued forward after the impact and also hit a light pole. Las Vegas Metropolitan Police confirmed at least one person was injured and the investigation is ongoing. Waymo stated the SUV struck the Waymo vehicle from behind. This is the first reported Waymo crash since the Las Vegas service launched.
- Jul 19, 2026Waymo robotaxi rear-ended by SUV in south Las Vegas, at least one injuredOn record
On July 19, 2026 at approximately 9:45 a.m., a human-driven SUV struck a Waymo robotaxi from behind near Sunset Road and Polaris Avenue in south Las Vegas, then continued forward and also hit a light pole. At least one person was injured. Las Vegas Metropolitan Police Department confirmed the crash and said the investigation is ongoing. Waymo told FOX5 the SUV struck the Waymo vehicle from behind before continuing forward and hitting the light pole.
- Jul 17, 2026Zoox issues software recall after robotaxi drove through heavy smoke at Las Vegas emergency sceneOn record
Zoox issued a software recall after an unoccupied robotaxi drove into an active emergency fire scene clouded with heavy smoke in Las Vegas in June 2026. The NHTSA filing cites the software's failure to detect and respond to heavy smoke near emergency scenes. The recall comes as NHTSA has warned AV companies about vehicles interfering with first responders.
- Jul 17, 2026Zoox recalls 105 robotaxis after vehicle drove into heavy smoke at active Las Vegas fire sceneOn record
Zoox voluntarily recalled 105 autonomous vehicles after an unoccupied robotaxi drove into heavy smoke obscuring an active emergency fire scene in Las Vegas on June 20, 2026. The vehicle braked hard and steered away before stopping; a teleoperator reversed it from the scene. Zoox notified NHTSA of the recall on July 8, and it was publicly reported July 17. The recall follows a NHTSA letter urging AV companies to stop interfering with first responders.
- Jul 17, 2026Zoox recalls entire 105-vehicle fleet after robotaxi drove into smoke-filled active fire sceneOn record
NHTSA recall 26E044 (July 17 2026): On June 20 2026, an unoccupied Zoox robotaxi encountered heavy smoke obscuring an active emergency fire scene that was not cordoned off with cones. The vehicle failed to detect and respond to the smoke-filled scene. Zoox issued a software update to 105 vehicles enhancing detection of active emergency scenes by adding heavy-smoke response capability. No injuries reported. The recall came one week after NHTSA warned AV companies about interfering with first responders.
Operator (unnamed on record)NHTSA (Part 573, 26E044)TechCrunchNational Highway Traffic Safety Administration - Jul 17, 2026Zoox recalls entire 105-vehicle fleet because robotaxis may not detect heavy smoke and could impede emergency respondersOn record
Amazon's Zoox recalled its fleet of 105 autonomous vehicles after an unoccupied Zoox robotaxi entered an active emergency fire scene obscured by heavy smoke on June 20, 2026, braked hard, and reversed under teleguidance. The recall follows a NHTSA letter warning AV companies about a clear pattern of driverless vehicles interfering with law enforcement and first responders. Zoox issued a software update to enhance smoke detection and response capabilities.
- Jul 11, 2026San Francisco Supervisor Connie Chan drafting cost-recovery fee legislation to fine AV companies for impeding emergency responseOn record
San Francisco Supervisor Connie Chan is drafting legislation to impose financial consequences on autonomous vehicle companies when their vehicles interfere with emergency operations, including false emergency reports and impeded emergency response. The SF Fire Department has documented 31 internal incident reports involving AVs blocking emergency routes. Mayor Daniel Lurie and the city attorney are supporting the measure, expected to be presented to the Board of Supervisors in the coming months. This is a local regulatory action distinct from the federal NHTSA directive issued July 8, 2026.
- Jul 9, 2026NHTSA issues directive to AV developers citing clear pattern of driverless AVs interfering with first respondersOn record
In July 2026, NHTSA Administrator Jonathan Morrison issued a directive to autonomous vehicle developers requiring them to ensure their vehicles get out of the way of first responders. The letter cited a clear pattern of driverless AVs interfering with law enforcement and other first responders, including incidents where AVs drove into active emergency scenes, blocked the paths of ambulances or firefighters, or failed to recognize or respond to flashing lights, flares, smoke, fire, and traffic cones. The directive preceded Zoox's smoke-detection recall and follows multiple Waymo recalls for construction-zone and flooded-roadway entry failures.
- Jul 8, 2026NHTSA demands AV developers stop driverless vehicles from interfering with first respondersOn record
NHTSA Administrator Jonathan Morrison issued a directive to autonomous vehicle developers stating that driverless AVs interfering with law enforcement and first responders is a 'functional insufficiency,' not an edge case. The agency cited incidents of AVs driving into active emergency scenes, blocking ambulances and firefighters, and failing to recognize flashing lights, flares, and traffic cones. AV developers were given until end of July to present solutions. While no company was named explicitly, details point to robotaxi operators like Waymo.
- Jul 8, 2026NHTSA issues call to action to AV developers over pattern of driverless AVs interfering with first respondersOn record
On July 8, 2026, NHTSA Administrator Jonathan Morrison issued a public call to action to automated vehicle developers, citing a pattern of driverless AVs driving into active emergency scenes, blocking ambulances and firefighters, and failing to recognize flashing lights, flares, smoke, fire, and traffic cones. NHTSA scheduled meetings with driverless ADS developers by month's end and warned it will exercise enforcement authority for developers that do not address significant safety concerns.
- Jul 7, 2026SF Supervisor Bilal Mahmood launches inquiry into Waymo's July 4 traffic meltdownOn record
On July 7, 2026, San Francisco Supervisor Bilal Mahmood announced a letter of inquiry to the city's Department of Emergency Management, Fire Department, and Municipal Transportation Agency, seeking information on how Waymo robotaxis contributed to massive gridlock following the July 4 Golden Gate Bridge fireworks show. More than 30 Waymo robotaxis became stuck in the Presidio parking area, some running out of charge and requiring towing. Mahmood stated it is 'not acceptable that disruption of service, first responders and our public transit system is a side effect of autonomous vehicles' and requested city departments respond within two weeks. The inquiry follows repeated Waymo run-ins with first responders documented by TechCrunch and a July 8 NHTSA directive demanding AV companies stop interfering with emergency operations.
- Jul 1, 2026California SB 1246 and AB 1777 take effect July 1, 2026 - new AV regulationsOn record
California SB 1246 reinforces requirements for remote assistants and drivers of commercial AVs. AB 1777 establishes requirements for how driverless AVs interact with first responders and emergency operations. Both take effect July 1, 2026.
- Jul 1, 2026California AB 1777 requires driverless vehicles to support first responder communication and emergency geofencingIn effect
California enacted Assembly Bill 1777, authored by Assemblymember Phil Ting, which the state chaptered on September 27, 2024 and which became operative on July 1, 2026. The law requires companies that operate autonomous vehicles without a human driver present to maintain a dedicated emergency response telephone line for first responders during all hours, to equip each vehicle with a two way voice communication device so first responders near the vehicle can reach a remote operator, to provide training for law enforcement and firefighters on the vehicle override system, and to direct their fleet to leave or avoid an area within two minutes of receiving an emergency geofencing message from emergency response officials. This record is attributed to the enacted text of AB 1777 as published by the California Legislature.
- Jun 22, 2026Zoox issues software recall after robotaxi drives through heavy smoke at Las Vegas fire sceneOn record
An unoccupied Zoox robotaxi drove through heavy smoke from an active fire emergency in Las Vegas that had not yet been cordoned off with traffic cones. Zoox investigated the root cause and developed a software update to enhance detection of and response to heavy smoke near active emergency scenes. The voluntary recall covers 105 vehicles with ADS software produced between April 23 and July 8, 2026. Updated software was deployed to all affected vehicles on July 15, 2026.
- Jun 20, 2026Zoox issues software recall after robotaxi drives through heavy smoke at active fire scene in Las VegasOn record
An unoccupied Zoox robotaxi encountered heavy smoke from an active fire emergency in the Las Vegas area that had not yet been cordoned off with traffic cones. The vehicle entered the scene, braked hard, and attempted to steer away before stopping. Zoox notified NHTSA on June 25, 2026, and issued a voluntary software recall covering 105 vehicles with ADS software produced between April 23 and July 8. A software update was developed to enhance detection of and response to heavy smoke near emergency scenes.
- Jun 20, 2026Zoox issues software recall after robotaxi drove into heavy smoke at active fire scene in Las VegasOn record
On June 20, 2026, an unoccupied Zoox robotaxi encountered heavy smoke from an active emergency fire scene in Las Vegas that was not cordoned off with cones. The vehicle braked hard and steered away before stopping. Zoox issued a voluntary software recall covering 105 vehicles on July 8, 2026, shipping an update that adds smoke detection capability. No injuries were reported. The recall follows NHTSA's July 8 letter warning AV companies to stop interfering with first responders.
- Jun 20, 2026Zoox issues software recall after robotaxi drove into heavy smoke at emergency fire sceneOn record
On June 20, 2026, a Zoox robotaxi encountered heavy smoke obscuring an active emergency fire scene that was not cordoned off with cones; the vehicle braked hard and steered away before stopping, and a Zoox teleoperator reversed it from the scene. Zoox issued a voluntary software recall (NHTSA 26E044000) on July 7, 2026 affecting its 105-vehicle fleet, shipping a software update to detect and respond to heavy smoke at emergency scenes. No injuries were reported and no passengers were on board. The recall came a week before NHTSA administrator Jonathan Morrison sent a letter warning AV companies to stop interfering with first responders.
- Jun 20, 2026Zoox issues software recall after robotaxi entered smoke-filled emergency fire sceneOn record
On June 20, 2026, an unoccupied Zoox robotaxi encountered heavy smoke obscuring an active emergency fire scene that was not cordoned off with cones. The vehicle braked hard while attempting to steer away before stopping; a teleoperator reversed it to allow first responders to place cones. No injuries reported. Zoox shipped a software update to its 105-vehicle fleet enhancing detection of heavy smoke at emergency scenes. NHTSA recall ID 26E044000, decided July 7, 2026.
- Jun 20, 2026Zoox recalled 105 robotaxis after an unoccupied vehicle drove into heavy smoke at an active fire scene in Las VegasOn record
On June 20, 2026, an unoccupied Zoox robotaxi entered an active emergency fire scene obscured by heavy smoke in Las Vegas that had not yet been cordoned off with cones. The vehicle braked hard while attempting to steer away before stopping. Zoox notified NHTSA of a voluntary software recall on July 8, 2026, affecting 105 robotaxis. A software update enhancing heavy-smoke detection was released to all affected vehicles on July 15. No injuries were identified. The recall follows NHTSA Administrator Morrison's July 8 letter calling AV interference with first responders a functional insufficiency.
- Jun 20, 2026Zoox recalls 105 robotaxis after one drove into active fire scene in Las VegasOn record
A Zoox robotaxi entered an active fire emergency scene not yet cordoned off by cones in the Las Vegas Valley on June 20, 2026, conducted a hard brake while trying to steer clear, and came to a stop; a Zoox employee had to guide it out. Zoox voluntarily recalled 105 robotaxis and issued a software update to improve detection of and response to heavy smoke. The incident was reported to NHTSA under the Automated Vehicle Exemption Program on June 25.
- Jun 20, 2026Zoox recalls all 105 robotaxis (NHTSA 26E044) after robotaxi drove into heavy smoke at an active fire sceneOn record
Zoox issued a voluntary software recall covering all 105 of its driverless robotaxis after an unoccupied Zoox vehicle entered an active emergency fire scene obscured by heavy smoke on June 20, 2026. The vehicle braked hard and steered away before stopping, and a remote teleguidance operator reversed it out so first responders could cone off the scene. No injuries were reported. Zoox released an updated software remedy on July 15, 2026; the recall (NHTSA 26E044, manufacturer recall 26-01) was submitted July 16.
- Jun 20, 2026Zoox software recall (NHTSA 26E044) — robotaxi drove into active fire scene confused by heavy smokeOn record
On June 20, 2026, a Zoox robotaxi in Las Vegas encountered heavy smoke from an active emergency fire scene that was not cordoned off with cones. The vehicle braked hard and steered away before stopping. A teleoperator reversed the vehicle. Zoox issued voluntary recall of 105 robotaxis on July 7, 2026 (NHTSA Campaign 26E044). Software update deployed to improve heavy smoke detection. No injuries. NHTSA Administrator Morrison sent letter July 8 warning AV companies to stop interfering with first responders.
- Jun 15, 2026Zoox robotaxi involved in minor crash on Las Vegas Boulevard and Harmon Avenue, vehicle towedOn record
A Zoox robotaxi was involved in a minor crash at Las Vegas Boulevard and Harmon Avenue in Las Vegas, requiring the self-driving vehicle to be towed. Metro police closed the case after they could not contact either party. The incident was observed on a Regional Transportation Authority traffic camera livestream.
- Jun 1, 2026ADS crash report in Austin, TX involving a TOYOTA Highlander (NHTSA SGO 30610-15465)On record
A Zoox vehicle, operating in autonomous mode, was stopped in the westbound left-turn lane of [XXX], yielding to oncoming traffic to turn left onto [XXX] in Austin under a flashing yellow arrow. Eastbound traffic on [XXX] was backed up and slowing down. After receiving a hand gesture from the driver of a slowing SUV in the oncoming lane, the Zoox vehicle operator disengaged from autonomy and proceeded with the left turn. At that time, a pickup truck (Vehicle 2) traveling in the right lane of eastbound [XXX] quickly approached the intersection. Although the driver of Vehicle 2 attempted to steer left, the vehicle collided with the rear right area of the Zoox vehicle in the intersection. Vehicle 2's left side subsequently made contact with the front right corner of the oncoming SUV. Both the Zoox vehicle and Vehicle 2 sustained moderate damage, and the Zoox vehicle was towed. No injuries were reported, and police were notified but did not respond to the scene.
Zooxnhtsa.gov - Jun 1, 2026ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15301)On record
On June [XXX], 2026 at 1:07 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was involved in a collision involving a motorcycle and an SUV on [XXX] at [XXX]. The Waymo AV was stopped in the dedicated left turn lane for a red light on [XXX] at the intersection with [XXX]. While the Waymo AV remained stopped, a motorcycle traveling in the second from the right lane came to a stop adjacent to an SUV that was stopped in the rightmost lane. After both vehicles briefly remained stopped, the SUV and motorcycle began to proceed forward when the SUV changed lanes into the second from the right lane, towards the motorcycle. The motorcycle maneuvered left towards the dedicated left turn lane, and the SUV continued to change lanes across the second from the right lane, towards the motorcycle into the dedicated left turn lane. While the SUV continued to change lanes, the front right of the SUV made contact with the rear of the motorcycle, and the front left of the SUV made contact with the right side of a passenger car that was stopped behind the Waymo AV. As a result of this initial contact with the SUV, the motorcycle continued forward and the front of the motorcycle then made contact with the rear right of the Waymo AV. The SUV also continued forward, and the front left of the SUV then made contact with the rear right of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All involved vehicles sustained damage, and the motorcyclist was transported to the hospital by ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital by ambulance. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - May 28, 2026Waymo robotaxi blocked Dallas first responders from reaching fatal Oak Cliff apartment explosionOn record
On May 28, 2026, a driverless Waymo robotaxi partially blocked the roadway that fire trucks needed to reach a five-alarm gas explosion at The Clyde apartments in Dallas Oak Cliff that killed three people and injured five. Body camera footage released June 4 shows a Dallas County deputy constable having to manually drive the empty Waymo to clear the street so emergency crews could reach the scene. Waymo said the vehicle was turning around when the constable interacted with its remote assistance team.
- May 1, 2026ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-14977)On record
On May [XXX], 2026 at 10:01 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] in the rightmost lane when it approached the intersection with [XXX], where police officers were directing traffic. The Waymo AV came to a stop and, after cross traffic cleared, proceeded into the intersection. A passenger car traveling southbound on [XXX] in the leftmost lane entered the intersection per the direction of one of the police officers. The Waymo AV slowed to yield to the passenger car and the front left side of the passenger car made contact with the front right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - May 1, 2026ADS crash report in Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15246)On record
On May [XXX], 2026 at 11:42 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Inglewood, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] when it slowed to a stop for a stop sign at the intersection with [XXX]. While the Waymo AV was stopped, a passenger car that was initially stopped facing east on [XXX] initiated a left turn onto northbound [XXX]. At the same time, an SUV traveling northbound on [XXX] proceeded straight into the intersection without stopping at the stop sign on [XXX], and the front left side of the SUV made contact with the right side of the passenger car. As a result of this contact, the passenger car shifted northbound towards the stopped Waymo AV, and the front of the passenger car made contact with the front left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage. The driver of the passenger car was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - May 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15295)On record
An unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling north on [XXX], having just completed a left turn from [XXX] in Las Vegas, when it encountered debris in its path. The Zoox vehicle attempted to steer right, then executed hard braking to avoid the debris, at which point it was rear-ended by a passenger car (Vehicle 2) traveling directly behind it. Both vehicles came to a stop following the impact and were subsequently towed due to the damage sustained. Vehicle 2 suffered front-end damage and its driver-side frontal airbags deployed, while the Zoox vehicle sustained moderate damage to its rear. Law enforcement was notified of the event, but did not respond to the scene. Following the impact, Zoox staff inquired if emergency medical services should be called; the driver replied that the police had already been contacted. The driver of Vehicle 2 informed Zoox staff at the scene that they were "shaken" and "pretty bruised".
Zooxnhtsa.gov - May 1, 2026ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15030)On record
On May [XXX], 2026 at 4:46 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound in the right lane on [XXX] when it slowed to a stop at a green light at the T-intersection with [XXX] to yield to an active fire truck, with lights and sirens activated, traveling eastbound on [XXX] and crossing into westbound [XXX] to traverse through the intersection. While the Waymo AV was stopped, an SUV initially stopped behind the Waymo AV, partially in the left lane and partially in the right lane, proceeded to pass the Waymo AV to the left, and the front right side of the SUV made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - May 1, 2026ADS crash report in Los Angeles, CA involving a ZEEKR RT (NHTSA SGO 30270-15070)On record
On May [XXX], 2026 at 6:44 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a pickup truck on [XXX] near {XXX}. The Waymo AV was traveling southbound in the right lane on {XXX] in autonomous mode when it began to slow for a queue of traffic stopped for a red light at the intersection with [XXX]. As the Waymo AV was slowing, the Waymo AV transitioned to manual mode and the test driver maneuvered to the right and accelerated forward. As the test driver maneuvered the Waymo AV to pass to the right of a pickup truck that was stopped facing south in the right lane in the queue of traffic ahead, the front left side of the Waymo AV made contact with the rear right side of the pickup truck, the front of the Waymo AV made contact with the west curb of {XXX], and the front right side of the Waymo AV made contact with a street light pole near the curb. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. The test driver of the Waymo AV was transported to a hospital by an ambulance with moderate injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - May 1, 2026ADS crash report in Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-15174)On record
On May [XXX], 2026 at 3:59 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling westbound in the second to the right lane on [XXX] and proceeding straight at a green light at the intersection with [XXX]. As the Waymo AV began to cross the intersection, a pickup truck traveling northbound in the designated right turn lane on [XXX]t proceeded to enter the intersection against a red light and began to maneuver to the left. The Waymo AV braked and maneuvered to the right as the pickup truck continued to proceed forward, and the front of the pickup truck made contact with the left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Two passengers in the Waymo AV were not belted at the time of the collision. Two passengers in the Waymo AV were transported to a hospital by an ambulance with moderate injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because individuals involved were transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - May 1, 2026ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15021)On record
On May [XXX], 2026 at 12:02 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a bus on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] and slowing for a queue of traffic for a red light at the intersection with [XXX] when the Waymo AV passenger opened the rear right door, causing the Waymo AV to stop in-lane and activate its hazard lights for passenger dropoff. While the Waymo AV was stopped, a shuttle bus traveling southbound on [XXX] approached the Waymo AV from the front and slowed to a stop momentarily. The shuttle bus proceeded forward to pass the Waymo AV to the left, between the Waymo AV and a fire truck that was stopped facing north partially in the bike lane and in-lane on southbound [XXX], and the left side of the shuttle bus made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - May 1, 2026ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15096)On record
On May [XXX], 2026 at 11:59 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] with its right turn signal activated when it began to slow to yield to a passenger car stopped facing west near the north curb of [XXX] and partially in-lane. While the Waymo AV was slowing, an SUV traveling westbound on [XXX] at a high rate of speed approached the Waymo AV from behind, and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - May 1, 2026ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15250)On record
On May [XXX], 2026 at 1:07 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was traveling northbound on a narrow portion of [XXX], with vehicles parked at the curb in both directions, when it maneuvered to the right and slowed to a stop in-lane to yield to an inactive ambulance traveling southbound on [XXX]. While the Waymo AV was stopped, the ambulance proceeded to pass the Waymo AV to the left, and the left side of the ambulance made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - May 1, 2026ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-15018)On record
An unoccupied Zoox autonomous vehicle was traveling south on [XXX] on a green light at [XXX] in San Francisco when a pickup truck (Vehicle 2) executed an abrupt left turn from northbound [XXX] and accelerated into the Zoox vehicle's right-of-way. The Zoox vehicle braked hard, but contact was unavoidable. Vehicle 2's front bumper struck the Zoox vehicle's left side door and body panels. After reversing, Vehicle 2 cleared the intersection, pulled over temporarily, and then left without exchanging information. Shortly afterward, the Zoox vehicle cleared the intersection, pulled over, and was towed for inspection. It was found to have sustained moderate damage. No injuries were reported, and police were not called.
Zooxnhtsa.gov - May 1, 2026ADS crash report in Santa Monica, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14986)On record
On May [XXX], 2026 at 8:37 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving multiple vehicles on [XXX] near [XXX]. The Waymo AV was stopped facing southeast in the left lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. Behind the Waymo AV, in the same lane of traffic, were three consecutive SUVs. All three SUVs behind the Waymo AV were initially also stopped in the traffic queue until the rear-most of the three SUVs proceeded forward. The rearmost SUV contacted the SUV in front of it, pushing the second SUV forward into the SUV behind the Waymo AV. The SUV behind the Waymo AV then made contact with the rear of the stationary Waymo AV, and as a result of this contact, the front of the Waymo AV made contact with a passenger car stopped directly in front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All five vehicles sustained damage. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - May 1, 2026ADS crash report in Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-15022)On record
On May [XXX], 2026 at 12:43 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling eastbound in the rightmost lane on [XXX] with its right turn signal activated when it began to slow to turn right into a parking lot at [XXX]. As the Waymo AV initiated the right turn, a passenger car traveling eastbound in the rightmost lane on [XXX] approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. A passenger in the passenger car was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Apr 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14656)On record
An unoccupied Zoox autonomous vehicle was traveling north on [XXX] past [XXX] in Las Vegas when a passenger car (Vehicle 2) abruptly attempted to turn right onto [XXX] from a parking lot, violating the Zoox vehicle's right-of-way. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The Zoox vehicle's right-front fender, wheel, and fascia contacted Vehicle 2's left-front bumper and headlight. Both vehicles sustained damage, and the Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified.
Zooxnhtsa.gov - Apr 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14732)On record
An unoccupied Zoox autonomous vehicle was in the left lane traveling north on [XXX] past [XXX] when it slowed for a tractor-trailer (vehicle 2) that was reversing from the roadway into a loading bay on the right side of the road. While reversing, the tractor-trailer swung over into the left lane, and the left side of Vehicle 2's trailer made contact with the stopped Zoox vehicle's front fascia and sensor pods. The Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified.
Zooxnhtsa.gov - Apr 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15064)On record
An occupied Zoox autonomous vehicle, gradually slowed to a stop behind traffic on southbound [XXX] past [XXX] in Las Vegas, when it was rear ended by a passenger vehicle (Vehicle 2) traveling directly behind. The Zoox vehicle honked at the approaching Vehicle 2, but its driver failed to stop in time. Vehicle 2's driver left the scene without exchanging information. The Zoox vehicle did not sustain any damage. No injuries were reported at that time. Police were notified. One of the passengers later contacted Zoox support and stated, "I began experiencing significant neck pain consistent with a possible soft tissue injury." The passenger has not provided any documentation to Zoox regarding their alleged injury.
Zooxnhtsa.gov - Apr 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-15065)On record
An unoccupied Zoox autonomous vehicle was preparing to turn right from a hotel driveway onto southbound [XXX] in Las Vegas, and came to a gradual stop to yield to cross traffic when it was rear ended by a pickup (Vehicle 2) traveling directly behind. The Zoox vehicle honked at the approaching Vehicle 2, but Vehicle 2's driver failed to stop in time. Vehicle 2's driver then went around the stopped Zoox vehicle, briefly stopped in the right lane, activated their hazard lights, and then proceeded to leave the area. Upon inspection, the Zoox vehicle was found to have sustained moderate damage to its rear. No injuries were reported and police were not notified.
Zooxnhtsa.gov - Apr 1, 2026ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14660)On record
On April [XXX], 2026 at 11:38 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was parked facing north on [XXX], partially in-lane and partially in the bike lane, with its hazard lights activated for a passenger dropoff. While the Waymo AV was parked, an SUV traveling northbound on [XXX] without active headlights maneuvered to the right as the SUV approached the Waymo AV from behind, and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passengers of the Waymo AV were transported to a hospital by an ambulance with minor alleged injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because individuals involved were transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Apr 1, 2026ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14829)On record
On April [XXX], 2026 at 9:56 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was parked at the east curb facing north on [XXX] with its hazard lights activated for a passenger dropoff. While the Waymo AV was parked, an SUV traveling westbound on [XXX] turned right onto [XXX] and approached the Waymo AV from behind, and the front right side of the SUV made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. A passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Apr 1, 2026ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14888)On record
On April [XXX], 2026 at 9:13 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing northwest on [XXX] for a stop sign at the intersection with [XXX] with its left turn signal activated. The Waymo AV proceeded forward into the intersection and began to initiate a left turn onto [XXX], and an SUV, initially stopped behind the Waymo AV, proceeded forward and maneuvered to the right towards the Waymo AV, and the front of the SUV made contact with the rear left side of the Waymo AV. As the Waymo AV continued to turn left, the SUV began to turn left and proceeded forward again, and the front of the SUV made additional contact with the rear right side of the Waymo AV. At the time of the impacts, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. A passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Apr 1, 2026ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14618)On record
On April [XXX], 2026 at 9:24 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] when an SUV traveling northbound on [XXX], without activated headlights, maneuvered to the left and entered the Waymo AV's lane of travel. The Waymo AV began to slow to yield to the SUV as the SUV continued to approach, and the left side of the SUV made contact with the left side of the Waymo AV. As a result of this contact, the Waymo AV was pushed to the right and the front right tire of the Waymo AV made contact with the left side of a passenger car parked facing south on the west curb of 47th Avenue. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV and the SUV sustained damage. The passengers of the Waymo AV were transported to a hospital by an ambulance, alleging minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because individuals involved were transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Apr 1, 2026ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14627)On record
On April [XXX], 2026 at 8:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling northeastbound on [XXX] when an SUV traveling southwestbound on [XXX] crossed the solid double yellow lane lines and entered the Waymo AV's lane of travel. The Waymo AV braked and maneuvered to the right to yield to the SUV as the SUV continued forward, and the front of the SUV made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the SUV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Apr 1, 2026ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-15063)On record
A Zoox vehicle operating in autonomous mode was stopped behind traffic at a red signal on northbound [XXX] at [XXX] in San Francisco. At this time, a passenger vehicle (Vehicle 2) was reversing from a parking spot on the left side of the roadway. The Zoox vehicle honked at the approaching Vehicle 2, but Vehicle 2's rear end made contact with the Zoox vehicle's driver door. The Zoox vehicle operator then disengaged from autonomous mode. The Zoox vehicle sustained minor damage. No injuries were reported, and police were not notified.
Zooxnhtsa.gov - Apr 1, 2026ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-15062)On record
An occupied Zoox autonomous vehicle traveling north on [XXX] was stopped for a signal at [XXX] in San Francisco, with a passenger vehicle (Vehicle 2) stopped directly behind it. As the light turned green, the Zoox vehicle began to proceed but stopped for traffic and was rear ended by Vehicle 2. Vehicle 2's driver immediately left the scene without exchanging information. Shortly after, the Zoox vehicle proceeded straight and pulled over in the right lane adjacent to the bike lane, and the passengers exited. One passenger reported feeling "whiplash" but declined medical treatment. The police were notified. The Zoox vehicle sustained minor rear-end damage.
Zooxnhtsa.gov - Apr 1, 2026Four Zoox robotaxis stalled on Hacienda Avenue near the Las Vegas Strip, blocking traffic lanesOn record
Four Zoox robotaxis stalled on Hacienda Avenue near Sorrel Street in Las Vegas, taking up most of the two eastbound travel lanes. Las Vegas Metro police responded to the scene, with traffic forced to navigate around the cluster of stationary self-driving vehicles. Zoox stated the incident was caused by external third-party interactions, not a software issue.
- Mar 1, 2026ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-14483)On record
On March [XXX], 2026 at 8:35 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped facing southeast in the leftmost lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a pickup truck traveling southeastbound in the leftmost lane on [XXX] slowed as it approached the Waymo AV from behind, and the front of the pickup truck made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance, alleging minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Mar 1, 2026ADS crash report in Austin, TX involving a TOYOTA Highlander (NHTSA SGO 30610-14264)On record
A Zoox vehicle operating in autonomous mode, traveling southwest on [XXX] towards [XXX] in Austin, was slowing for a garbage truck (Vehicle 2) approaching from the opposite direction when Vehicle 2 struck it head-on. The Zoox vehicle sustained moderate damage to the left front area, including the hood, bumper, headlight, fender, A-pillar hinge, and driver door. Both parties exchanged information. Police were notified and arrived at the scene. No injuries were reported.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14389)On record
On March [XXX], 2026 at 7:59 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Inglewood, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing south on [XXX] in a queue of traffic for a stop sign at the intersection with [XXX]. As traffic ahead advanced, the Waymo AV slowly proceeded forward in the queue of traffic, and an SUV traveling southbound on [XXX] approached the Waymo AV from behind, and the front right side of the SUV made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Mar 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14263)On record
An occupied Zoox autonomous vehicle traveling southeast on [XXX] stopped behind traffic in the outer left turn lane (lane #2) for a red traffic signal at [XXX] in Las Vegas. A dumpster-hauling truck (Vehicle 2) was stopped in the adjacent through-lane (lane #3). Shortly after the light turned green and the Zoox vehicle began its left turn, the Vehicle 2 operator abruptly steered left, accelerated, and cut into the Zoox vehicle's path, violating its right of way. The Zoox vehicle braked hard; however, Vehicle 2 struck the Zoox vehicle's right-side front wheel, fender, roof-mounted sensor unit, and body panel. The Zoox vehicle was towed from the scene and sustained moderate damage. No injuries were reported, and police were not called.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14342)On record
An unoccupied Zoox autonomous vehicle was traveling northeast on [XXX], approaching [XXX] in Las Vegas, when a passenger car (Vehicle 2) abruptly turned right onto [XXX] from a parking lot on the right, violating the Zoox vehicle's right-of-way. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The Zoox vehicle's right front fender and wheel, and its right rear door panel, contacted Vehicle 2's left fender, wheel, headlight, and quarter panel. Both vehicles sustained damage, and the Zoox vehicle was towed from the scene. No injuries were reported, and police were not notified.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14366)On record
An occupied Zoox autonomous vehicle was traveling east at low speed in a parking lot along [XXX] in Las Vegas when an SUV (Vehicle 2) began reversing out of its parking spot. The Zoox vehicle slowed and attempted to steer left, but it could not before Vehicle 2 struck the Zoox vehicle's right-side rear door, body panel, and wheel. The Zoox vehicle sustained moderate damage and was towed from the scene. No injuries were reported, and police were not notified.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14519)On record
An unoccupied Zoox autonomous vehicle started to move after a gradual stop at a 3-way stop sign preparing to turn right onto eastbound [XXX] in Las Vegas, when it braked to an abrupt stop as cross-traffic failed to stop and yield the right-of-way. It was then rear ended by an SUV (Vehicle 2) traveling directly behind. The Zoox vehicle was towed from the scene and was found to have sustained moderate damage to the rear. No injuries were reported and police were not notified. Camera footage from the Zoox vehicle shows that the Vehicle 2 driver was not looking ahead at the roadway before the time of contact.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14387)On record
On March [XXX], 2026 at 1:20 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a first responder vehicle on [XXX] at [XXX]. The Waymo AV was traveling westbound on [XXX] when it slowed to a stop at a sign at the intersection with [XXX]. While the Waymo AV was stopped, an active emergency vehicle with emergency lights activated traveling eastbound on [XXX] approached the intersection, and the Waymo AV began to move a short distance to the right to create additional room for the emergency vehicle to pass to the Waymo AV's left before coming to a stop to yield to the oncoming emergency vehicle. While the Waymo AV was stopped, the emergency vehicle continued to exit the intersection along [XXX] and proceeded to pass the Waymo AV to the left. As the emergency vehicle was passing the Waymo AV, the left side of the emergency vehicle made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Mar 1, 2026ADS crash report in Miami, FL involving a TOYOTA Highlander (NHTSA SGO 30610-14554)On record
A Zoox vehicle in autonomous mode was traveling east on [XXX] toward [XXX] in Miami when the operator of a wrong-way-parked semi-trailer suddenly swung open the rear door of the trailer into the path of the approaching Zoox vehicle. The door struck the Zoox vehicle's right-side A-pillar, windshield, and sensor assembly. After the impact, the trailer's door rebounded and struck the operator behind it. The Zoox vehicle operator then disengaged from autonomous mode. The police and emergency personnel arrived at the scene. The operator was transported by an ambulance from the scene.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14287)On record
On March [XXX], 2026 at 9:06 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing south in the third from the right lane on [XXX] for a red light at the intersection with [XXX] when an active emergency vehicle, with emergency lights activated, traveling westbound on [XXX] proceeded straight through the intersection. After the traffic light turned green, the Waymo AV proceeded forward a short distance and came to a stop momentarily before entering the intersection, as it detected a siren from an emergency vehicle. The Waymo AV began to proceed straight and a passenger car initially stopped behind the Waymo AV approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Mar 1, 2026ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14425)On record
On March [XXX], 2026 at 8:56 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX]at a low rate of speed, with vehicles parked at the curb in both directions and active emergency vehicles stopped on both sides of the roadway facing east. The Waymo AV maneuvered to the right and slowed to a stop in-lane to yield to an active ambulance, which was initially stopped, as the ambulance began traveling eastbound on [XXX]. While the Waymo AV was stopped, the ambulance proceeded to pass the Waymo AV to the left, and the left side of the ambulance made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Mar 1, 2026ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14663)On record
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling west on [XXX] past [XXX] in San Francisco when it encountered a Pickup truck reversing into its lane from a perpendicular parking spot ahead. The Zoox vehicle slowed to a stop, and while it waited for the lane to clear, a passenger car (Vehicle 2) began to reverse. The Zoox vehicle honked at Vehicle 2, but Vehicle 2 continued to reverse and made contact at low speed with the passenger-side front door of the Zoox vehicle. The Zoox vehicle operator then disengaged from autonomous mode. Both vehicles sustained damage. No injuries were reported, and the police were not notified.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14665)On record
A Zoox vehicle (Vehicle 1) operating in autonomous mode was stopped behind traffic in the through lane on westbound [XXX] at a red traffic light at [XXX] in San Francisco with a passenger car (Vehicle 2), stopped directly ahead. After both vehicles were fully stopped, Vehicle 2 began moving backward toward the still-stopped Zoox vehicle, and even though the Zoox vehicle honked its horn, Vehicle 2 continued to move backward and made contact with the Zoox vehicle's front bumper. The Zoox vehicle operator then disengaged from autonomy. The Zoox vehicle sustained minor damage. No injuries were reported, and police were not notified.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14388)On record
An unoccupied Zoox autonomous vehicle (Vehicle 1), traveling southwest on [XXX] in San Francisco, was stopped mid-way through a lane-change maneuver (from lane #2 to lane #1) in stop-and-go traffic, when a passenger car (Vehicle 2) in lane #1 accelerated toward the stopped Zoox vehicle and struck its left front wheel. The Zoox vehicle was towed from the scene for inspection and was found to have sustained no damage. Vehicle 2's front bumper appears to have sustained minor damage. No injuries were reported. Police were notified but did not arrive at the scene. The Zoox vehicle's video footage shows that Vehicle 2's driver was not looking at the road ahead before or at the time of contact.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14419)On record
A Zoox autonomous vehicle, traveling west on [XXX] toward [XXX] in San Francisco, stopped next to parked vehicles with active hazard lights to pick up a passenger. Just after the passenger entered the Zoox vehicle, a passenger car (Vehicle 2) traveling behind attempted to pass on the left and swiped the Zoox vehicle's left rear fender. The Zoox vehicle was towed from the scene and was found to have sustained minor damage. No injuries were reported, and police were not notified.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14664)On record
An unoccupied Zoox autonomous vehicle (Vehicle 1), traveling northeast on [XXX] toward [XXX] in San Francisco, stopped next to parked vehicles with active hazard lights to pick up a passenger. Shortly after, one of the parked vehicles (Vehicle 2) was attempting to pull out of the parking spot when the Zoox vehicle's passenger approached and activated its doors. The Zoox vehicle's right rear door contacted Vehicle 2's front bumper. The right rear door on the Zoox vehicle was damaged; no injuries were reported, and police were not notified.
Zooxnhtsa.gov - Mar 1, 2026ADS crash report in Washington, DC involving a JAGUAR I-PACE (NHTSA SGO 30270-14625)On record
On March [XXX], 2026 at 7:27 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Washington D.C. was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southbound in the rightmost lane on [XXX] when it began to slow for an emergency vehicle siren from an ambulance traveling northbound. While the Waymo AV was slowing, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present (in the driver's seating position). Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Mar 1, 2026Waymo robotaxi blocked an ambulance responding to Austin mass shootingOn record
A Waymo robotaxi picking up a passenger near the scene of a mass shooting on West Sixth Street in Austin stopped and completely blocked a street, preventing an ambulance from reaching the scene. An Austin police officer had to manually direct the vehicle away. Austin-Travis County EMS confirmed the vehicle briefly interfered with ambulance access.
WaymoAxios Austin - Feb 25, 2026Waymo robotaxi struck in hit-and-run collision on first day of Charlotte operationsOn record
On Waymo's first day of operations in Charlotte, NC, a manually driven Waymo vehicle with a human trainer aboard was struck by another vehicle in a hit-and-run on the 500 block of W. Fourth Street near Truist Field. The other vehicle crossed a double yellow line, cut off the Waymo, then reversed into it before fleeing. No injuries reported and the Waymo vehicle sustained no damage. Charlotte-Mecklenburg Police Department filed an incident report.
WaymoGovTech - Feb 1, 2026ADS crash report in Las Vegas, NV involving a HYUNDAI Ioniq 5 (NHTSA SGO 30410-14092)On record
On February [XXX], 2026, at approximately 9:55 AM PT, a Motional Ioniq 5 AV (VIN [XXX]) was operating in autonomous mode in Las Vegas, Nevada, with a safety driver in the driverâs seat. The AV was stopped southbound on [XXX] in the left-turn lane at the intersection with [XXX], positioned behind two other stopped vehicles. At that time, a sedan traveling eastbound on [XXX] was being actively pursued by a law enforcement vehicle which had its flashing lights and siren activated. Both vehicles turned left and proceeded northbound on [XXX] but using the southbound lanes. As the sedan traveled in the wrong lanes on [XXX], it struck the passenger-side front end and right wheel well of the Motional vehicle which remained stopped in the left turn lane the entire time. The sedan did not stop after striking the Motional vehicle and continued traveling in the wrong (southbound) lanes and counter to the flow of traffic while it continued fleeing from police. No occupants of the Motional vehicle were injured. The Motional vehicle sustained damage to the front end and was towed from the scene. The Las Vegas Metropolitan Police Department is investigating the incident, but a police report is not yet available
Motionalnhtsa.gov - Feb 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14340)On record
An occupied Zoox autonomous vehicle traveling south on [XXX] was stopped for a red signal at [XXX] in Las Vegas. After the light turned green, and before the Zoox vehicle started to move, a Pickup (Vehicle 2) traveling directly behind it rear-ended it. Shortly thereafter, both vehicles traveled a few feet ahead and pulled over. The passengers exited the Zoox vehicle onto the sidewalk. After exchanging information, the Zoox vehicle returned to base for inspection, where it was found to have sustained moderate damage. No injuries were reported, and police were not notified.
Zooxnhtsa.gov - Feb 1, 2026ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-14341)On record
An occupied Zoox autonomous vehicle was traveling northeast on [XXX], passing through the intersection of [XXX] in Las Vegas, with a green signal, when an SUV (Vehicle 2) violated the Zoox vehicle's right of way and abruptly entered its travel path. The Zoox vehicle braked hard and attempted to veer left, but the right front fender of the Zoox vehicle made contact with the left front fender and bumper of Vehicle 2. The driver of Vehicle 2 briefly stopped and then drove away from the scene. The Zoox vehicle was found to have sustained minor damage. At the time of the incident, the passengers did not report any injuries, and police were not notified. On March 2, 2026, the passengers notified Zoox Support that they "sustained multiple injuries and have experienced persistent and worsening pain and cognitive symptoms since the impact".
Zooxnhtsa.gov - Feb 1, 2026ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14118)On record
On February [XXX], 2026 at 2:50 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was stopped facing southwest in the rightmost lane on [XXX] for an SUV which was in a prior collision stopped facing southeast, partially in the rightmost lane on [XXX] and partially on the curb. While the Waymo AV was stopped, an active emergency vehicle with emergency lights activated traveling eastbound on [XXX] proceeded to turn left onto [XXX] and travel northeastbound in the adjacent lane to the Waymo AV, against the proper direction of traffic. The emergency vehicle proceeded to pass the Waymo AV to the left and began to maneuver towards the curb on its left, and the left side of the emergency vehicle made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger in the Waymo AV was not belted at the time of the collision. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Feb 1, 2026ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14003)On record
On February [XXX], 2026 at 11:06 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was parked at the curb facing north on [XXX] with its hazard lights activated for a passenger drop-off. While the Waymo AV was parked, a passenger in the Waymo AV opened the rear right side door in preparation to exit the vehicle. A van traveling northbound on [XXX] in the right lane accelerated as it approached the Waymo AV from behind, and the front of the van made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. A passenger in the Waymo AV was unbelted at the time of the collision as they were preparing to exit the vehicle. Both passengers of the Waymo AV were transported to a hospital by an ambulance, one of the passengers had minor injuries and one of the passengers had moderate injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Feb 1, 2026ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14075)On record
On February [XXX], 2026 at 2:12 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was parked in-lane facing northeast near the south curb on [XXX] with its hazard lights activated for a passenger pickup. While the Waymo AV was stopped, the two Waymo AV passengers approached the Waymo AV, opened the rear right door, and one of the passengers entered the Waymo AV. While the other passenger was standing outside of the Waymo AV at the open rear right door, a passenger car traveling northwestbound on [XXX] proceeded straight into the intersection with [XXX] without stopping at the stop sign on [XXX], and the front of the passenger car made contact with the Waymo AV passenger and the right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passengers of the Waymo AV were not belted at the time of collision as they were in the process of entering the vehicle. The passenger that was standing outside of the Waymo AV reported minor injuries and was transported to a hospital by an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle was towed from the scene. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Feb 1, 2026ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14152)On record
A Zoox vehicle (Vehicle 1) operating in autonomous mode came to an abrupt stop on [XXX] just after turning left from northbound [XXX] in San Francisco, and was rear ended by a passenger vehicle (Vehicle 2) traveling directly behind it. The Zoox vehicle operator disengaged from autonomy after the impact. There were no reported injuries, and police were not called. The Zoox vehicle was towed from the scene and was found to have sustained moderate damage to its rear end.
Zooxnhtsa.gov - Feb 1, 2026ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14026)On record
An unoccupied Zoox autonomous vehicle was traveling east on [XXX] toward [XXX] in San Francisco when an SUV (Vehicle 2) that had been stationary while in an apparent attempt to parallel park along the right curb suddenly pulled out into the path of the approaching Zoox vehicle. The Zoox vehicle braked hard and attempted to steer left, but the right front wheel and body panel of the Zoox vehicle made contact with the left front wheel and panel of Vehicle 2. The Zoox vehicle was towed from the scene for inspection and was found to have sustained minor damage. There were no reported injuries, and police were not notified
Zooxnhtsa.gov - Feb 1, 2026ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-14339)On record
An unoccupied Zoox autonomous vehicle was traveling in the right lane on northwest-bound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. Partway through the right turn, the Zoox vehicle further slowed to yield to a pedestrian crossing [XXX], and at that time, a cyclist traveling northwest on the adjacent sidewalk rapidly entered the crosswalk. The Zoox vehicle braked to yield to the approaching cyclist, and the cyclist made contact with the right rear side of the nearly stopped Zoox vehicle. The bicycle fell to the ground, but its rider remained upright. The cyclist picked up their bicycle and rode away from the scene. Shortly after, the Zoox vehicle resumed operation to return to base. There was minor damage to the Zoox vehicle. There were no reported injuries, and police were not notified.
Zooxnhtsa.gov - Feb 1, 2026ADS crash report in Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14167)On record
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling southeast on [XXX], preparing to change lanes to the right to turn onto [XXX] in Santa Monica, when it was hit on the right rear corner (rear bumper, hatch, right rear wheel, and right rear quarter panel) by an SUV (Vehicle 2). The Zoox vehicle stopped facing southwest on [XXX], with the front of Vehicle 2 still engaged with the right rear of the Zoox vehicle. The Zoox vehicle sustained severe rear damage, including damage to data recording systems. Vehicle 2 had major damage to its front end. Airbags deployed in both vehicles, and they were towed from the scene. Police and emergency responders arrived to assist, and the driver of vehicle 2 was detained. The Zoox vehicle operator and two passengers reported soreness and a headache after the collision.
Zooxnhtsa.gov - Feb 1, 2026ADS crash report in Scottsdale, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-13955)On record
On February [XXX], 2026 at 7:09 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane. A passenger car traveling northbound in the second to the left lane, in front of and to the left of the Waymo AV, began to slow and change lanes to the right when a second passenger car made contact with the rear right side of the first passenger car. The second passenger car continued forward and made contact with an SUV stopped in the queue of traffic in the second from the left lane. As a result of the initial contact with the second passenger car, the first passenger car was pushed east across two lanes of travel, and entered the Waymo AV's lane of travel. The Waymo AV slowed and maneuvered to the right to avoid the oncoming passenger car and the front left side of the passenger car made contact with the left side of the Waymo AV. The Waymo AV rotated to the left and came to rest facing southwest in the second and third from the left lanes. During two subsequent maneuvers in which the Waymo AV pulled forward and to the right in an attempt to navigate off the freeway, the front left corner of the Waymo AV made contact with an "Oversized Load" sign attached to a heavy truck stopped in the second from the left lane. At the time of all impacts, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All involved vehicles sustained damage. The driver of the first passenger car was transported to a hospital by an ambulance with unknown injuries, and the passenger of the Waymo AV alleged minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Jan 17, 2026Zoox robotaxi struck an opening car door in San Francisco, injuring a street ambassadorOn record
On January 17, 2026, around 2 p.m., a Zoox robotaxi in San Francisco collided with a suddenly-opened parked-car door, injuring a street ambassador (Jamel Durden, per reporting). The San Francisco Police Department opened an investigation and the California DMV reviewed the incident; Zoox filed a mandatory crash report. The collision raised questions about Zoox's edge-case detection as it expanded early-rider programs in SF and Las Vegas, adding to a pattern of recalls and operational issues.
- Jan 1, 2026ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13853)On record
On January [XXX], 2026 at 7:48 AM, a May Mobility Autonomous Vehicle (AV) was in a collision with a fire hydrant in Atlanta, Georgia on [XXX]near[XXX]. The May Mobility AV was traveling westbound on [XXX]in Atlanta, Georgia with its automated driving system engaged in autonomy mode when the Autonomous Vehicle Operator (AVO) fell asleep while his right hand rested on the right side of the steering wheel. In-cabin video and telematics confirms that the AVO's hand restricted the motion of the steering wheel, preventing the autonomous system from keeping the vehicle in its lane. Though the AV braked after perceiving the exit from its travel lane, collision with the fire hydrant could not be avoided. The air bags deployed during the collision and the AV was towed from the scene. The AVO was transported by ambulance to the hospital with minor injuries.
May Mobilitynhtsa.gov - Jan 1, 2026ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13664)On record
On January [XXX], 2026 at 6:54 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southeastbound on [XXX] in the second from the right lane for a green light when it began to slow to yield to a uniformed police officer standing partially in the roadway to the right of the Waymo AV, directing traffic at the intersection with [XXX]. While the Waymo AV was slowing, it began to change lanes to the rightmost lane, and the light turned yellow. The Waymo AV slowed to a stop before entering the intersection, partially in the rightmost lane, and an SUV that was traveling behind the Waymo AV in the second from the right lane approached the Waymo AV from behind and maneuvered to the left, and the front right side of the SUV made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Jan 1, 2026ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14025)On record
On January [XXX], 2026 at 6:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing northeast on [XXX] in the third from the right lane for a red light at the intersection with [XXX]. When the light turned green, the Waymo AV proceeded a short distance and then slowed down before entering the intersection to yield to an active emergency vehicle traveling northeastbound on [XXX] against the proper direction of traffic with its emergency lights activated. While the Waymo AV was stopped, an SUV that was initially stopped directly behind the Waymo AV proceeded forward, and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Jan 1, 2026ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-14090)On record
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling northeast on [XXX] toward [XXX] in San Francisco. At that time, an SUV (Vehicle 2) traveling ahead pulled into the parking lane on the right. Just as the Zoox vehicle was approaching, Vehicle 2 suddenly swerved into the Zoox vehicle's lane without using a turn signal. The Zoox vehicle braked hard and attempted to steer left to avoid the collision. The vehicle operator then disengaged autonomy and continued braking, but contact was unavoidable. The left front of Vehicle 2 struck the right front of the Zoox vehicle. The Zoox vehicle sustained moderate damage, and the right rear passenger reported "experiencing soreness" after the collision. The police were not called.
Zooxnhtsa.gov - Jan 1, 2026ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13662)On record
An unoccupied Zoox autonomous vehicle (Vehicle 1) was traveling east on [XXX] near [XXX] in San Francisco. It began to slow down for a stopped box truck (Vehicle 2) in the same lane, which had an open liftgate. As the Zoox vehicle was preparing to maneuver around, Vehicle 2 began to reverse. The Zoox vehicle came to a stop however, Vehicle 2 continued reversing. The Zoox vehicle honked, but Vehicle 2's open liftgate made contact with the right front fender and front fascia of the Zoox vehicle. The Zoox vehicle was towed from the scene and was found to have sustained minor damage. The police were notified, and no injuries were reported.
Zooxnhtsa.gov - Jan 1, 2026ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13818)On record
An occupied Zoox autonomous vehicle began to proceed on a fresh green traffic signal on westbound [XXX] at [XXX] when the driver of a stationary passenger vehicle (Vehicle 2), parallel-parked in the curb lane, rapidly opened the driver door into the path of the approaching Zoox vehicle. The Zoox vehicle braked hard and attempted to steer left, but contact was unavoidable. The right side front fender, wheels, bodyside, and door panels made contact with the outside edge of the opening door of Vehicle 2. The Zoox vehicle came to an immediate stop and was later towed from the scene to be inspected for damage. First responders arrived at the scene. The passenger of the Zoox vehicle did not report any injuries. Later media stories reported the driver of Vehicle 2 had a "smashed hand" and his "hand was hurting, and that he was also experiencing pain to his neck area and lower back" based on a third party's account, and that the driver "declined their offer to take him to the hospital." Zoox vehicle camera footage shows clearly that no part of the robotaxi came into contact with the driver themselves, and that their hands, leg, and body did not interact with either the robotaxi or the parked vehicle's door at any moment during the contact event.
Zooxnhtsa.gov - Dec 30, 2025Waymo robotaxi drove past emergency flares into active fire scene in HollywoodOn record
A Waymo robotaxi on Melrose Avenue in Hollywood took a wrong turn and drove past LAFD road flares into an active fire scene near Van Ness, where the Los Angeles Fire Department had blocked the street. The vehicle had at least one passenger in the backseat and remained inside the closure for approximately 10 minutes before making a U-turn and leaving. No injuries were reported.
- Dec 1, 2025ADS crash report in Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-13488)On record
On December [XXX], 2025 at 10:24 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling eastbound in the right lane on [XXX] when a passenger car that was initially stopped facing north on [XXX], to the right and in front of the Waymo AV, proceeded forward into the intersection at [XXX]. As the passenger car entered the intersection the front of the passenger car made contact with the right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passengers of the Waymo AV were transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Dec 1, 2025ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-13287)On record
On December [XXX], 2025 at 4:45 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a pickup truck on [XXX] near [XXX]. The Waymo AV was stopped facing northwest in the second from the right lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. After the traffic light turned green and traffic ahead advanced, the Waymo AV proceeded a short distance and came to a stop because of the detection of a potential nearby emergency vehicle. A pickup truck that was initially stopped directly behind the Waymo AV proceeded forward, and the front of the pickup truck made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV alleged a minor injury. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Dec 1, 2025ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-13449)On record
On December [XXX], 2025 at 3:17 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing east in the fourth from the right lane on [XXX] for a red light at the intersection with [XXX]. When the traffic light turned green, the Waymo AV proceeded a short distance and then slowed down before entering the intersection to yield to an active emergency police vehicle traveling southbound on [XXX] near [XXX] with emergency lights activated. While the Waymo AV was stopped, an SUV that was initially stopped directly behind the Waymo AV proceeded forward and the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Dec 1, 2025ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13302)On record
On December [XXX], 2025 at 2:14 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a first responder vehicle on [XXX] at [XXX]. The Waymo AV was stopped facing south in the second from the right lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an active fire truck with sirens activated traveling westbound on [XXX] proceeded to turn right to travel north in the rightmost southbound lane of [XXX], to the right of the Waymo AV. The Waymo AV began to move a short distance to the left to create additional room for the fire truck to pass to the AV's right before coming to a stop to yield to the oncoming fire truck. While the Waymo AV was stopped, the fire truck continued to complete the right turn and the right side of the fire truck made contact with the rear right side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Dec 1, 2025ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13491)On record
On December [XXX], 2025 at 9:48 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a van on [XXX] near [XXX]. The Waymo AV was stopped at the curb facing southeast on [XXX] with its hazard lights activated for a passenger dropoff. While the Waymo AV was stopped, a van traveling southeastbound on [XXX] maneuvered to the right and approached the Waymo AV from behind, and the front of the van made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Dec 1, 2025ADS crash report in Palo Alto, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13378)On record
On December [XXX], 2025 at 8:26 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Palo Alto, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was traveling northwestbound in the rightmost lane on [XXX] with its right turn signal activated and preparing to make a right turn at a green light onto [XXX]. As the Waymo AV began initiating the right turn, the Waymo AV came to a stop within the crosswalk to yield to a cyclist. The cyclist was traveling southbound on the east sidewalk of [XXX] and entered the crosswalk across [XXX] against a red pedestrian crosswalk light. As the cyclist entered the crosswalk, the front tire of the bicycle made contact with the right side of the stationary Waymo AV and the cyclist fell to the ground. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The cyclist was transported to a hospital in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Dec 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13495)On record
On December [XXX], 2025 at 1:41 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing northeast on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling northeastbound on [XXX] approached the Waymo AV from behind, and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Dec 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13539)On record
On December [XXX], 2025 at 1:21 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] at [XXX]. The Waymo AV was stopped facing east in the left lane on [XXX] for a red light at the intersection with [XXX]. A fire engine with lights and siren activated traveling northbound in the leftmost lane on [XXX] proceeded straight through the intersection with [XXX] before stopping, then reversing into the intersection. The fire engine then proceeded to turn left onto [XXX]. The Waymo AV moved slightly to the right within its lane, then came to a stop to yield to the oncoming fire engine. While the Waymo AV was stopped, the fire engine continued to complete the left turn and the left side of the fire engine made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Dec 1, 2025ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13660)On record
An unoccupied Zoox vehicle (Vehicle 1) was stationary in the right lane on northeast-bound [XXX] at [XXX] in San Francisco, stopped behind traffic at a red light. After the light turned green, the Zoox vehicle initially remained stopped to yield to an active police vehicle making a right turn onto [XXX] from the adjacent lane. During the subsequent green light cycle, as the Zoox vehicle began to proceed straight along [XXX], two passenger cars, including Vehicle 2, cut across its path from behind, attempting an illegal right turn onto [XXX] from a through lane. The Zoox vehicle braked hard, but contact was unavoidable, and Vehicle 2 clipped the Zoox vehicle's left front fender. The front-seat passenger of Vehicle 2 exited to inspect the Zoox vehicle before returning to their car and leaving the scene without exchanging information. The Zoox vehicle then cleared the scene and returned to base. Upon inspection, the Zoox vehicle was found to have sustained minor damage. Police were notified, and no injuries were reported.
Zooxnhtsa.gov - Dec 1, 2025ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-13661)On record
An occupied Zoox autonomous vehicle (Vehicle 1) was traveling west on [XXX] past [XXX] when it encountered debris in the lane. The Zoox vehicle braked hard for the debris and was then rear ended by a close-following Pickup (Vehicle 2) that was abruptly merging into the lane directly behind the Zoox vehicle. The Vehicle 2 driver then reversed and left the scene without attempting to exchange information. Shortly after, the Zoox vehicle cleared the scene, turned right onto [XXX], and pulled over to allow the riders to exit the vehicle. The Zoox vehicle then returned to base for inspection and was found to have sustained moderate damage. There were no reported injuries, and the police were notified.
Zooxnhtsa.gov - Nov 1, 2025ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-13060)On record
On November [XXX], 2025 at 12:37 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing southwest in the designated left turn lane on [XXX] at the intersection with [XXX] with hazard lights activated. A passenger car traveling northeastbound on [XXX], in the Waymo AV's lane of travel and against the proper direction of traffic, approached the front of the Waymo AV, and the front left side of the passenger car made contact with the front left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the passenger car alleged minor injuries and was transported to a hospital in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Nov 1, 2025ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-13376)On record
An occupied Zoox autonomous vehicle (Vehicle 1) was stopped behind traffic in the left turn lane on southbound [XXX] at [XXX] in Las Vegas, waiting at a traffic signal. After the light turned green, the Zoox vehicle initially remained stationary and then started moving forward. Shortly after resuming motion, the Zoox vehicle stopped and was rear-ended by the SUV (Vehicle 2) directly behind it. The Zoox vehicle sustained minor damage, and no injuries were reported. The police were not called.
Zooxnhtsa.gov - Nov 1, 2025ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13167)On record
On November [XXX], 2025 at 4:52 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northeastbound on [XXX], with its right turn signal activated, when it slowed to a stop for a stop sign at the intersection with [XXX]. The Waymo AV proceeded forward slowly as it was yielding to vehicles traveling southeastbound on [XXX] and preparing to turn right onto [XXX]. While the Waymo was proceeding forward, a passenger car traveling northeastbound on [XXX] approached the Waymo AV from behind and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV was not belted at the time of the collision. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Nov 1, 2025ADS crash report in Miami, FL involving a TOYOTA Highlander (NHTSA SGO 30610-13377)On record
A Zoox retrofitted test vehicle (Vehicle 1) in autonomous mode was stopped, yielding to cross-traffic, on westbound [XXX] at [XXX] in Miami while waiting for an opportunity to proceed through the intersection and continue west on [XXX]. The Zoox vehicle inched forward and then stopped again for cross-traffic. The Zoox vehicle operator then disengaged from autonomous mode and proceeded to begin to cross [XXX]. While crossing, a motorcyclist traveling northbound on [XXX] at a high rate of speed collided with the driver's side front fender and door of the Zoox vehicle. The motorcycle and its operator fell to the ground. After the collision, the Zoox vehicle operator cleared the intersection and pulled over. Both the Zoox vehicle and the motorcycle sustained damage. Police and EMT personnel arrived at the scene, but the motorcycle operator was not transported from the scene.
Zooxnhtsa.gov - Nov 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13065)On record
On November [XXX], 2025 at 1:03 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing north on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV was stopped, an SUV traveling northbound on [XXX] came to a stop directly behind the Waymo AV. While both the Waymo AV and the SUV were stopped, a passenger car traveling northbound on [XXX] approached the stopped SUV from behind and the front of the passenger car made contact with the rear of the SUV, and then the front of the SUV made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV, the SUV, and the passenger car sustained damage. The driver of the passenger car alleged injuries and was transported to a hospital by an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Nov 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13201)On record
On November [XXX], 2025 at 6:08 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a first responder vehicle on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] and came to a stop to yield to a police SUV that was traveling southbound on [XXX] and had stopped in-lane. While the Waymo AV was stopped, the police SUV reversed and the rear of the police SUV made contact with the front of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Nov 1, 2025ADS crash report in Scottsdale, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-12051)On record
On November [XXX], 2025 at 2:13 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] when an SUV traveling eastbound on [XXX] crossed the center dashed yellow line and entered the Waymo AV's lane of travel, and the front left side of the SUV made contact with the front left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the SUV alleged injuries and was transported to a hospital by an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Nov 1, 2025ADS crash report in Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-13192)On record
On November [XXX], 2025 at 5:31 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing south on [XXX] for a stop sign at the intersection with [XXX] with its right turn signal activated in preparation for a right turn. While the Waymo AV was stopped, a passenger car traveling southbound on [XXX] approached the Waymo AV from behind at a high rate of speed and began to maneuver to the left, and the front right side of the passenger car made contact with the rear left side of the stationary Waymo AV. The front of the passenger car then made contact with the rear of a second passenger car that was stopped at the stop sign in front of and to the left of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage. The driver of the second passenger car was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Oct 1, 2025ADS crash report in Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-11841)On record
On October [XXX], 2025 at 9:55 AM EDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] and came to a stop at the stop sign at the intersection with [XXX]. A passenger car traveling directly behind the Waymo AV proceeded without stopping, and the front driver side of the passenger car then made contact with the rear side of the stationary Waymo AV. First responders arrived at the scene and assisted the rider out of the Waymo AV. An ambulance was called to the scene and Waymo later learned that the rider was transported to the hospital. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger in the Waymo AV was not belted at the time of the collision they were in the process of locating the belt fastener for the seat they were occupying. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Oct 1, 2025ADS crash report in Las Vegas, NV involving a HYUNDAI Ioniq 5 (NHTSA SGO 30410-12017)On record
On October [XXX], 2025, at approximately 2:30 PM PT, a Motional AV with VIN [XXX] was operating in autonomous mode in Las Vegas, Nevada, with a safety driver in the drivers seat. The vehicle was traveling northbound on [XXX] in the second of four lanes from the left, approaching the intersection with [XXX]. While stopped at a red traffic signal, an adult male pedestrian began crossing [XXX] from the west side of the street, several hundred feet away from a designated crosswalk. The pedestrian proceeded southbound across multiple lanes and paused on a median located ahead and to the left of the AV. The AV detected and classified the pedestrian the entire time. When the traffic signal turned green, the pedestrian remained stopped on the median. Given that the pedestrian remained stopped in place, the AV began to move forward slowly at approximately 2.5 mph and continued to correctly detect and classify the pedestrian. The pedestrian, holding what appears to be an item in a plastic bag, suddenly stepped into the far-left turn lane ahead of the AV, the AV immediately came to a complete stop still in the second lane. The pedestrian continued crossing, making a light physical contact with the rear driverâs side of the vehicle before continuing across the remaining three lanes of traffic still outside of the crosswalk. The vehicle operator then disengaged the autonomous system and pulled over to complete an incident report. No police were notified. There were no injuries, no damage, and no airbag deployments. The pedestrian did not stop at the scene and the identity of the pedestrian is unknown.
Motionalnhtsa.gov - Oct 1, 2025ADS crash report in Las Vegas, NV involving a TOYOTA Highlander (NHTSA SGO 30610-11990)On record
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling east towards the Passenger Pick-up area in Terminal 3 of [XXX] in Las Vegas. An SUV (Vehicle 2), traveling behind in the left adjacent lane, abruptly attempted to overtake and cut in front of the Zoox vehicle in an apparent attempt to change lanes to the right towards Terminal 3 Departures. The Zoox vehicle braked hard in response to the encroaching vehicle, and the operator then disengaged from autonomy and continued to brake, but contact could not be avoided. The right rear side of Vehicle 2 swiped the left front area of the Zoox vehicle. Both operators stopped after the collision and exchanged information. Both vehicles sustained moderate damage, and the Zoox vehicle was subsequently towed from the scene. There were no reported injuries, and police were not called.
Zooxnhtsa.gov - Oct 1, 2025ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-11847)On record
An unoccupied Zoox autonomous vehicle was traveling in the right lane on southbound [XXX] towards [XXX] in Las Vegas. The driver of an SUV (Vehicle 2) traveling ahead in the same direction in the adjacent lane to the left suddenly veered right into the path of the Zoox vehicle without using a turn signal, making contact with the left rear wheel and fender, and left side body panels, doors, and rocker. The Zoox vehicle then gradually braked to a stop in the right lane. The Zoox vehicle was towed from the scene for inspection. The Zoox vehicle sustained moderate damage, while Vehicle 2 appears to have sustained damage to the right side fender panel and front bumper. There were no reported injuries, and the police were not called. Zoox is submitting this updated report to correct a previous reporting error in the location field.
Zooxnhtsa.gov - Oct 1, 2025ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-11856)On record
An unoccupied Zoox autonomous vehicle was traveling north in the right lane on [XXX], towards [XXX], in Las Vegas, when it encountered a slowing tractor-trailer (Vehicle 2) ahead in its lane, also traveling in the same direction. As the Zoox vehicle gradually slowed to a stop, the operator of Vehicle 2 began to reverse. The Zoox vehicle honked at Vehicle 2, but Vehicle 2 continued to reverse and made contact at low speed with the right front fender and bumper of the Zoox vehicle. The Zoox vehicle was towed from the scene for inspection and was found to have sustained minor damage. There were no reported injuries, and the police were not called.
Zooxnhtsa.gov - Oct 1, 2025ADS crash report in Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11929)On record
On October [XXX], 2025 at 7:48 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing north in the rightmost lane on [XXX] in a queue of traffic for a red light at the intersection at [XXX]. A passenger car traveling northbound in the rightmost lane on [XXX] slowed to a stop directly behind the Waymo AV. After the traffic light turned green and traffic ahead advanced, the Waymo AV proceeded a short distance and came to a stop before entering the intersection, as it detected a siren from an emergency vehicle. The passenger car also proceeded forward initially and then came to a stop to yield to the Waymo AV. While the Waymo AV and the passenger car remained stopped, a second passenger car traveling northbound on [XXX] approached the first passenger car from behind and the front of the second passenger car made contact with the rear of the first passenger car. The front of the first passenger car then made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV, the first passenger car, and the second passenger car sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Oct 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11855)On record
On October [XXX], 2025 at 2:55 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an ambulance on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] with vehicles parked on both sides when it maneuvered towards a driveway opening and came to a stop to yield to an ambulance, which did not have lights or sirens activated, traveling southbound on [XXX]. As the ambulance passed the stationary Waymo AV, the left side of the ambulance made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Oct 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11861)On record
On October [XXX], 2025 at 1:27 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane when a passenger car traveling directly behind the Waymo AV approached the Waymo AV from behind, and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The two passengers in the Waymo AV alleged minor injuries and were transported to a hospital by an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because individuals involved were transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Oct 1, 2025ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-13121)On record
A Zoox vehicle (Vehicle 1) operating in autonomous mode was westbound on [XXX], preparing to make an unprotected left turn onto [XXX] in San Francisco. As the Zoox vehicle slowed approaching the intersection at [XXX], a left-turning vehicle in the oncoming lane accelerated abruptly. The Zoox vehicle braked in response to the oncoming vehicle, and was rear ended by a passenger car (Vehicle 2) traveling directly behind. The Zoox vehicle operator then disengaged from autonomy, and shortly after, continued through the intersection along [XXX] and pulled over to exchange information. The Zoox vehicle sustained minor damage to the rear end, and Vehicle 2 appears to have sustained moderate damage to the left front area and hood. The Zoox vehicle operator and the software operator, seated in the front passenger seat, reported injuries after the collision. The police were not called.
Zooxnhtsa.gov - Sep 14, 2025Motorcyclist killed in Tempe crash involving Waymo robotaxi and hit-and-run driver near ASU campusOn record
On September 14, 2025, at approximately 1:30 AM, a motorcyclist was killed in a multi-vehicle crash near Lemon Street and Rural Road in Tempe, Arizona, near the ASU campus. An unoccupied Waymo robotaxi was making a right turn and yielding to pedestrians when the motorcyclist rear-ended the self-driving car. Within a second, a separate vehicle struck the motorcyclist and fled the scene; police later tracked down the hit-and-run driver, an ASU student. The motorcyclist was transported to the hospital and pronounced dead. Waymo stated it was fully cooperating with law enforcement and regulators. This is the third known fatal incident involving a robocar, occurring approximately 2 miles from the 2018 Uber ATG fatality site.
- Sep 1, 2025ADS crash report in Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-11794)On record
On September [XXX], 2025 at 2:44 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on [XXX] in the second to the left lane. As the Waymo proceeded through a green light at the intersection with [XXX], a passenger car that was traveling westbound in the rightmost lane on [XXX] proceeded through the intersection at [XXX] against a red light without stopping. The front of the passenger car made contact with the left side of a pickup truck that was traveling southbound in the leftmost lane on [XXX]. The right side of the pickup truck then made contact with the left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV, the passenger car, and the pickup truck sustained damage. The passenger in the Waymo AV alleged minor injuries and was transported to a hospital in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment, vehicles involved were towed away, and airbags were deployed. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Sep 1, 2025ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-11850)On record
On September [XXX], 2025 at 8:40 AM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was traveling southbound in the left lane on [XXX] when it came to a stop at a red light at the intersection at [XXX]. As the traffic light turned green and traffic ahead advanced, the Waymo AV initially proceeded forward and then began to slow before entering the intersection, after detecting a siren from an emergency vehicle. As the Waymo AV was slowing, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Sep 1, 2025ADS crash report in Las Vegas, NV involving a ZOOX Zoox (NHTSA SGO 30610-11752)On record
An unoccupied Zoox autonomous vehicle was operating at a reduced speed in lane #5 on westbound [XXX] towards Las Vegas Boulevard in Las Vegas, with a sedan (Vehicle 2) directly behind. The Zoox vehicle gradually slowed to a stop when it was rear ended by Vehicle 2. Vehicle 2 driver initially exited his vehicle to inspect both vehicles, but did not remain at the scene to exchange information. The Zoox vehicle resumed operation and cleared the scene. Shortly afterward, the Zoox vehicle slowed to a stop due to a low tire pressure fault and was subsequently towed. The low tire pressure was attributed to the crash. The Zoox vehicle sustained minor damage. There were no reported injuries, and the police were not notified.
Zooxnhtsa.gov - Aug 1, 2025ADS crash report in Peachtree Corners, GA involving a TOYOTA Sienna (NHTSA SGO 30413-11593)On record
The May vehicle was travelling in an autonomous vehicle (AV) only lane approaching an intersection. A vehicle travelling to the left of the May shuttle (ego) in the non-AV lane performed a right hand turn across the May vehicle¢ÃÂÃÂs path. Given the full stopping power and the limited space with which the ego had to stop, the ego was physically unable to stop in time before impact. The primary factor that led to this collision was human error on the part of the other vehicle that was required to yield to through traffic in the AV lane but did not. Right turns across a straight lane are uncommon, and drivers are typically not used to them, however there are several signs that instruct other traffic to yield to the vehicles in the AV lane. There were no autonomy faults or errors which led to this incident. Update: There was no indication of injury or request for medical attention at the scene. The police report states "Driver 1 complained of neck pain." For this reason, we are updating the highest severity injury alleged field to reflect the âminor w/o hospitalizationâ injury level. The remaining content of this report is unchanged from the initial report submitted on September [XXX], 2025, Report ID #[XXX].
May Mobilitynhtsa.gov - Aug 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11433)On record
On August [XXX], 2025 at 2:48 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was traveling southbound on a narrow portion of [XXX] with vehicles parked at the curb in both directions when it approached a heavy truck that was traveling northbound on [XXX]. The Waymo AV reversed to yield to the heavy truck and came to a stop at the curb at the intersection with [XXX]. The heavy truck proceeded forward past the Waymo AV and began a left turn onto westbound [XXX] and the left side of the heavy truck made contact with the rear left of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The passenger in the Waymo AV alleged a minor injury and was transported to a hospital in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Aug 1, 2025ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-11497)On record
An unoccupied Zoox vehicle in autonomy was traveling north on [XXX] toward [XXX] in San Francisco and slowing for an SUV (Vehicle 2) ahead, also heading north on [XXX]. As the Zoox vehicle approached the nearly stopped Vehicle 2, it steered left to pass. The driver of Vehicle 2 then, without using a turn signal, abruptly began reversing in an apparent attempt to parallel park on the right side of [XXX]. The Zoox vehicle then braked to a near stop when it was struck on the right rear wheel by Vehicle 2 as it swung into a parking space. Shortly afterward, the Zoox vehicle was towed from the scene for inspection. The Zoox vehicle did not sustain damage, but the left front bumper of the SUV appeared to have minor damage. There were no reported injuries, and the police were not called.
Zooxnhtsa.gov - Aug 1, 2025ADS crash report in San Francisco, CA involving a ZOOX Zoox (NHTSA SGO 30610-11563)On record
An unoccupied Zoox autonomous vehicle was stopped at a green traffic light on eastbound [XXX], waiting for traffic ahead to clear to turn left onto [XXX] in San Francisco. A pickup truck (Vehicle 2) was also stopped for the same traffic light, directly behind the Zoox vehicle. After the light turned yellow, the Vehicle 2 driver passed the stopped Zoox vehicle on the left side, striking the left rear fender, and proceeded through the red light. The Vehicle 2 driver did not stop to exchange information. Shortly afterward, the Zoox vehicle turned left onto [XXX] to clear the scene, briefly stopped again, and then pulled over. The Zoox vehicle was then towed for inspection. It sustained minor damage. There were no reported injuries and the police were not called.
Zooxnhtsa.gov - Aug 1, 2025ADS crash report in Santa Monica, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11564)On record
On August [XXX], 2025 at 10:15 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Santa Monica, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southeastbound in the left lane on [XXX] when it began to change lanes to the right lane and came to a stop for the red light at the intersection with [XXX] and to yield to law enforcement and emergency vehicles that were blocking vehicles from continuing southeastbound on [XXX]. While the Waymo AV remained stopped partially in the left lane and partially in the bike lane, a law enforcement officer arrived and began to direct traffic around the Waymo AV. A passenger car that was initially stopped behind the Waymo AV proceeded to maneuver around the left of the Waymo AV, and the right side of the passenger car made contact with the rear left of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passenger car sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Aug 1, 2025ADS crash report in Santa Monica, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11696)On record
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling southwest on [XXX] towards [XXX] in Santa Monica when it was struck on the passenger side by an SUV (Vehicle 2), traveling southeast on [XXX], which failed to yield the right-of-way and entered the Zoox vehicle's travel path. The Zoox vehicle braked, the vehicle operator disengaged, continued to brake, and steered left, but contact was unavoidable. The Zoox vehicle sustained moderate damage, and Vehicle 2 also sustained damage. There were no reported injuries, and the police were not notified.
Zooxnhtsa.gov - Aug 1, 2025ADS crash report in Spring Valley, NV involving a ZOOX Zoox (NHTSA SGO 30610-11587)On record
An unoccupied Zoox autonomous vehicle was traveling west along [XXX] toward [XXX] in Las Vegas when a tractor-trailer (Vehicle 2) operator failed to yield the right-of-way, failed to stop at a stop sign, and quickly pulled out of a driveway crossing the centerline and entering the Zoox vehicle's travel lane in an apparent attempt to make a left turn onto westbound [XXX]. The Zoox vehicle braked hard and steered right within its travel lane, but contact was unavoidable. The right corner of the front bumper and grille of the tractor-trailer made contact with the left front side of the Zoox vehicle. The Zoox vehicle then came to a complete stop. The operator of Vehicle 2 reversed off the roadway and stayed on-site to exchange information with the Zoox operations team. The Zoox vehicle was towed from the scene for inspection and was found to have sustained moderate damage. The front bumper, hood, and grille on Vehicle 2 appeared to be damaged. There were no reported injuries, and the police were not called.
Zooxnhtsa.gov - Jul 1, 2025ADS crash report in Paradise , NV involving a TOYOTA Highlander (NHTSA SGO 30610-11515)On record
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling south on [XXX] in the right lane and slowing for a red emergency traffic signal at [XXX] in Las Vegas. Shortly after the Zoox vehicle came to a stop, a pickup (Vehicle 2) following directly behind was rear ended by an SUV (Vehicle 3) that failed to stop. Vehicle 2 then rear ended the stopped Zoox vehicle. The police arrived at the scene. The driver of Vehicle 3 reported that their "head hurt" but declined medical attention. The Zoox vehicle sustained minor damage.
Zooxnhtsa.gov - Jul 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11280)On record
On July [XXX], 2025 at 9:35 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southwestbound on [XXX] and stopped in the right lane for a red traffic light at the intersection with [XXX]. The traffic light then turned green and the Waymo AV proceeded a short distance before stopping again to yield to an oncoming active emergency vehicle. A passenger car traveling behind the Waymo AV also proceeded from the green light and the front of the passenger car made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The rider of the Waymo AV alleged a minor injury. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Jul 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11358)On record
On July [XXX], 2025 at 11:03 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a fire truck vehicle on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] with vehicles parked on both sides when it came to a stop to yield to a fire truck, which did not have lights or sirens activated, traveling southbound on [XXX]. As the fire truck passed the stationary Waymo AV, the driver side of the fire truck made contact with the rear driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Jul 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11428)On record
On July [XXX], 2025 at 10:45 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] at [XXX]. The Waymo AV was stopped facing northwest in the second from the left lane on [XXX] for a red light at the intersection at [XXX]. When the light turned green, the Waymo AV began to move forward momentarily and then stopped to yield to an active emergency vehicle traveling southwestbound on [XXX] with emergency lights activated. While the Waymo AV was stopped, an SUV approached the Waymo AV from behind and the front of the SUV made contact with the rear of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Jul 1, 2025ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11514)On record
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling in the left lane on southwest-bound [XXX] toward [XXX] in San Francisco when a ball, immediately followed by a dog, entered the roadway from between parked cars on the left side of [XXX] directly into the path of the Zoox vehicle. The Zoox vehicle braked in response, but its underbody made contact with the dog. The Zoox vehicle operator then disengaged autonomous mode and brought the vehicle to a stop. The Zoox vehicle operator then reversed the vehicle to free the dog. The dog owner did not indicate injuries to the dog at the scene. The dog and its owner then returned to the sidewalk and the Zoox vehicle operator drove the vehicle from the scene. The police were not called. Zoox subsequently received an email alleging injuries to the dog, "abrasions behind its left front leg and a possible cracked rib."
Zooxnhtsa.gov - Jul 1, 2025ADS crash report in Spring Valley, NV involving a TOYOTA Highlander (NHTSA SGO 30610-11405)On record
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling south on [XXX] and initiating a left turn from a dedicated signalized turn lane onto [XXX] in Las Vegas with a flashing yellow. The Zoox vehicle operator disengaged just prior to the signal turning from flashing yellow to green arrow as they continued to execute the left turn. At that time, a passenger car (Vehicle 2) traveling north on [XXX] failed to stop for the red traffic signal and entered the intersection at a high speed, colliding with the passenger side of the Zoox vehicle. The side impact caused the Zoox vehicle to roll onto its driver's side. Both vehicles sustained major damage with airbag deployments. The police and EMS arrived at the scene. The Zoox vehicle operator was transported to a medical facility by an ambulance, and Vehicle 2's driver was reported to have declined medical attention. Both vehicles were towed from the scene.
Zooxnhtsa.gov - Jul 1, 2025ADS crash report in Winchester, NV involving a ZOOX Zoox (NHTSA SGO 30610-11513)On record
An unoccupied Zoox vehicle in autonomous mode was traveling in the right turn lane on southbound [XXX], slowing and preparing to make a right turn onto [XXX] with a green traffic light. At that time, an e-cyclist was traveling south on the sidewalk adjacent to southbound [XXX]. As the Zoox vehicle slowed to execute its turn, the e-cyclist rapidly approached the crosswalk in the path ahead of the Zoox vehicle. The Zoox vehicle braked to yield to the approaching e-cyclist. The e-cyclist then veered left and accelerated into the roadway, making contact with the right rear side of the nearly stopped Zoox vehicle. The e-cyclist fell to the ground behind the Zoox vehicle. The Zoox vehicle then started to move and completed the right turn onto [XXX] and completed its mission. The cyclist appears to have ridden away from the scene. A bystander reported the event to Zoox. There was minor damage to the Zoox vehicle, and information was not exchanged with the e-cyclist. The police were later notified.
Zooxnhtsa.gov - Jun 1, 2025ADS crash report in Paradise, NV involving a TOYOTA Highlander (NHTSA SGO 30610-11166)On record
A Zoox vehicle (Vehicle 1) operating in autonomous mode was traveling in the left through lane (lane #2) on westbound [XXX], approaching [XXX] in Las Vegas. The Zoox vehicle operator disengaged from autonomy after the traffic light at [XXX] transitioned from green to yellow and braked, bringing the Zoox vehicle to a stop, at which point it was rear-ended by a pickup truck (Vehicle 2) traveling behind. Both vehicles sustained minor damage however, the Zoox vehicle was towed from the scene as its operator was not comfortable driving it back. There were no reported injuries, and the police were not notified.
Zooxnhtsa.gov - Jun 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11192)On record
On June [XXX], 2025 at 2:27 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was stopped facing north in the rightmost lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV remained stopped, a passenger car that was stopped in the leftmost lane of [XXX], oriented diagonally relative to the roadway facing northeast after exiting a parallel parking spot at the west side curb of [XXX], proceeded northeastbound into the rightmost lane and the front of the passenger car made contact with the rear driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Neither vehicle sustained damage. A passenger in the Waymo AV reported a minor injury and was transported to a hospital in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.
Waymonhtsa.gov - Jun 1, 2025ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11205)On record
On June [XXX], 2025 at 10:04 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a cyclist on [XXX] at [XXX]. The Waymo AV was stopped facing southeast in the right lane on [XXX] for a red light at the intersection at [XXX] when a Waymo AV passenger opted to end their ride prior to reaching their originally specified drop-off location, prompting the Waymo AV to park in-lane and activate its hazard lights for the passenger drop-off. A cyclist was traveling southeastbound on [XXX] in between vehicles in the right lane and vehicles stopped at the curb. As the cyclist passed the Waymo AV to the right, a Waymo AV passenger opened the front passenger side door and the front passenger side door of the Waymo AV made contact with the cyclist. The passengers in the vehicle were not belted at the time of the collision, as they were preparing to exit the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. The cyclist reported minor injuries and was transported from the scene in an ambulance. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment and a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.
- Jun 1, 2025ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11331)On record
A Zoox vehicle (Vehicle 1), operating in manual mode, was heading south on [XXX], in the southbound lane, approaching [XXX] in San Francisco, when it encountered a passenger car (Vehicle 2) traveling north and occupying both the northbound and southbound lanes on [XXX]. The Zoox vehicle slowed and moved to the right for the oncoming Vehicle 2 however, as Vehicle 2 passed, its driver's side mirror made contact with the driver's side rear of the Zoox vehicle. The driver of Vehicle 2 failed to stop and exchange information. The Zoox vehicle did not sustain any damage, but Vehicle 2 appeared to have sustained minor damage to its driver's side mirror. There were no reported injuries, and the police were not notified.
Zooxnhtsa.gov - Aug 17, 2023Cruise robotaxi collided with an SF fire truck responding to an emergency; one passenger injuredOn record
On Aug 17 2023 a Cruise robotaxi collided with a fire truck running lights and sirens through a San Francisco intersection; one passenger hospitalized. Prompted emergency-vehicle handling software changes; superseded weeks later by the Oct 2023 CA-DMV permit suspension and the eventual wind-down.
- Aug 5, 2023Waymo driverless car blocked San Francisco firefighters working a vehicle fireOn record
The San Francisco Fire Department reported that on August 5, 2023 a driverless Waymo vehicle stopped and parked itself between a fire truck and a burning car near the Legion of Honor, forcing firefighters to walk around the vehicle with a charged hose line to reach the fire. Waymo states that its vehicles are designed to detect emergency vehicles and first responders and to yield. This record is attributed to the SFFD incident report as compiled by Mission Local and to Waymo.
- May 9, 2023Cruise driverless car ran over San Francisco Fire Department hose lines during firefighting operationsOn record
The San Francisco Fire Department reported that on May 9, 2023 a driverless Cruise vehicle ran over several lengths of fire hose laid across the 1300 block of Powell Street near Fire Station 2 while crews were working, causing equipment damage the department valued in the thousands of dollars and forcing firefighters to work around the vehicle. Cruise states that its vehicles are built to detect and pull clear of active emergency scenes. This record is attributed to the SFFD incident report as compiled by Mission Local and to Cruise.
- Jan 22, 2023San Francisco firefighter broke a Cruise robotaxi window after it advanced toward an active fire sceneOn record
The San Francisco Fire Department reported that on January 22, 2023 a driverless Cruise vehicle continued advancing toward firefighters working an active scene on the 1300 block of Hayes Street, and a firefighter broke the vehicle's front window after verbal warnings and physical contact failed to stop it. Cruise states that its vehicles are built to detect and yield to emergency scenes and first responders. This record is attributed to the SFFD incident report as compiled by Mission Local and to independent reporting by Forbes.
How we know this+
Every record on this page comes from a dated, sourced entry in the DEPLOY registry: AV incidents that mention emergency responders, NHTSA investigations and recalls, and California rules for autonomous vehicles. Here are the sources behind them.
Operators' positions are attributed to the companies; investigations are attributed to the regulator that opened them. Neither is stated as an independent finding.
Common questions
Do self-driving cars stop for ambulances?+
Have robotaxis blocked emergency vehicles?+
Has NHTSA investigated robotaxis over emergency responders?+
Are there laws requiring robotaxis to yield to first responders?+
Is Waymo safe around fire trucks?+
Keep reading
Ask the registry
Track how robotaxis handle emergency responders
Find out instantly when it changes.
Canonical URL: /do-robotaxis-get-out-of-the-way-for-emergency-responders · machine-readable mirror: /do-robotaxis-get-out-of-the-way-for-emergency-responders.md