Incidents gathered from public reporting around the world. Each one links to the articles it came from. None of it is a finding that anyone broke the law.
Reports people file about their own experience are not shown here and never will be without their agreement. Tell us what happened to you.
92 incidents closest to “Cruise LLC (General Motors subsidiary; robotaxi operations wound down 2025)” · matched on meaning · public reporting
A Waymo self-driving car mistakenly drove onto light rail tracks in Phoenix, forcing a passenger to flee the vehicle. The incident occurred near moving trains before the car continued along the tracks. Valley Metro confirmed it was notified and responded, and Waymo was contacted.
1 source article · read the reporting →
In June 2022, a Cruise autonomous vehicle operating in San Francisco attempted an unprotected left turn and braked hard after incorrectly predicting an oncoming car would turn right. The other car continued straight and struck the Cruise vehicle, injuring a Cruise employee and a person in the other car. Cruise subsequently recalled the software on 80 vehicles, temporarily restricted left turns, and issued a software update to improve predictions. The US National Highway Traffic Safety Administration oversaw the recall.
7 source articles · read the reporting →
A Waymo self-driving taxi in Phoenix, Arizona, became confused by traffic cones closing a lane and stopped, blocking the road. The vehicle repeatedly drove away from roadside assistance dispatched to help, before a human driver took over. Waymo acknowledged the incident, stating that its remote guidance team provided incorrect instructions and that it has since improved its operational process. The passenger, who documented the event, said such mistakes are rare.
3 source articles · read the reporting →
In June 2025, a Hellobike autonomous taxi in Zhuzhou, Hunan, veered off course and struck two pedestrians crossing the road, causing serious injuries. The company suspended its autonomous driving operations in Zhuzhou and Liyang following the crash. Reports suggest the vehicle may have lacked sufficient underside sensors, leading to detection failures. The incident is believed to be the first publicly known injury-causing crash involving a robotaxi in China.
4 source articles · read the reporting →
On 22 May 2022, three driverless Cruise vehicles stopped in the middle of Masonic Avenue in San Francisco, blocking two lanes of traffic. The cars reportedly became confused and halted, causing disruption. The incident was shared on social media by a witness.
4 source articles · read the reporting →
On April 2, 2022, a driverless Cruise taxi in San Francisco was pulled over by police for driving without headlights. The vehicle initially drove away before stopping at a safe location, confusing officers. Cruise stated the car yielded as programmed and no citation was issued. The incident highlights challenges of autonomous vehicles interacting with law enforcement.
5 source articles · read the reporting →
Delphi Automotive initially reported a near-miss between its self-driving Audi Q5 SUV and a Google Lexus RX400h in Palo Alto, California. A Delphi executive claimed Google's car cut off the Delphi vehicle, which took evasive action. However, Delphi later denied the incident, stating the vehicles were a lane width apart and that both cars performed correctly. Google also confirmed the cars behaved appropriately in an ordinary driving scenario.
7 source articles · read the reporting →
Uber launched a pilot program of self-driving taxis in San Francisco without obtaining a required permit from the California DMV. Two of the vehicles were observed running red lights on the first day. The California attorney general threatened legal action unless Uber removes the cars from the road. Uber argued that its cars are not fully autonomous and therefore not subject to the permit requirement.
10 source articles · read the reporting →
On 14 February 2016, a Google self-driving car sideswiped a public bus in Mountain View, California, in the first crash in which one of Google's autonomous vehicles was considered at fault. Google said the vehicle had tried to move around sandbags and struck the bus, and that the company bore some responsibility. No injuries were reported. Google said it had updated the vehicle's software to account for buses and other large vehicles.
10 source articles · read the reporting →
A Cruise self-driving car collided with a San Francisco Fire Department truck that was responding to an emergency. The incident occurred on August 17, 2023, in the Tenderloin district. One passenger sustained non-severe injuries and was taken to hospital. Cruise acknowledged the crash and offered support to the rider.
10 source articles · read the reporting →
On 7 December 2017, a self-driving Chevrolet Bolt operated by GM's Cruise subsidiary aborted a lane change and re-entered its lane on Oak Street in San Francisco, striking motorcyclist Oscar Nilsson and knocking him to the ground. Nilsson sued General Motors, claiming neck and shoulder injuries requiring lengthy treatment and resulting in disability leave. The San Francisco Police Department's report blamed Nilsson for passing on the right, but his lawyer disputed this, and GM denied responsibility while emphasising safety.
10 source articles · read the reporting →
The California Department of Motor Vehicles suspended Cruise LLC's autonomous vehicle deployment and driverless testing permits, saying the vehicles were not safe for public operation and that Cruise had misrepresented safety information. The suspension took effect immediately under California regulations. Cruise may apply to reinstate the permits once it satisfies the department's requirements. Its permit for testing with a safety driver was not affected.
10 source articles · read the reporting →
Exclusive: Zoox grounds Atlanta test fleet after workers report toxic gas exposure symptoms TechCrunch
1 source article · read the reporting →
A New York Times article alleged that Cruise's autonomous vehicles rely on human operators to achieve autonomous driving, with 1.5 workers per vehicle intervening every 2.5 to five miles. Cruise CEO Kyle Vogt responded on Hacker News, stating that remote assistance is used 2-4% of the time and that many sessions are resolved by the vehicle itself. The company declined an interview request from the NYT.
9 source articles · read the reporting →
A Cruise autonomous vehicle appeared to block emergency crews responding to a mass shooting in San Francisco's Mission District on 9 June 2023. A police officer in video footage says the robotaxi was blocking emergency medical and fire vehicles. Cruise denied obstructing access and said an employee moved the vehicle within half an hour. San Francisco police said they were investigating.
10 source articles · read the reporting →
On Thanksgiving 2022, a Tesla vehicle using its Full Self-Driving feature was involved in a fatal accident on the San Francisco Bay Bridge. Footage published by The Intercept showed the system braking abruptly. The incident highlights safety concerns with autonomous driving technology.
7 source articles · read the reporting →
On 6 February 2024, a Waymo driverless car collided with a bicyclist at a four-way intersection in San Francisco. The cyclist was obscured by a truck and the vehicle braked but could not stop in time. The cyclist sustained minor scratches and left the scene. Waymo stated it is contacting relevant authorities.
4 source articles · read the reporting →
In August 2023, a homeless man named Sammy Davis was fatally struck by a city bus in San Francisco. Emergency responders alleged that two Cruise robotaxis blocked their ambulance, delaying transport. City officials later clarified that Cruise was not at fault for the death, and the man had been hit by a bus. Cruise denied any responsibility, stating the delay was only 90 seconds.
2 source articles · read the reporting →
A Hello Inc. robotaxi struck and injured two pedestrians in Zhuzhou, China, on or around December 5, 2025. Footage showed bystanders and police lifting the vehicle to free a person trapped underneath. Hello has suspended autonomous-driving operations in Zhuzhou. Local police have not yet determined fault, and Hello has not commented. The crash follows a prior incident where a Hello robotaxi allegedly failed to stop after a collision.
3 source articles · read the reporting →
Zoox, Amazon's self-driving car company, recalled 332 robotaxis after they were found veering into oncoming traffic near intersections. The issue was first noticed in August 2025 when a car took a wide right turn crossing the center line. Zoox said no crashes or injuries occurred and fixed the problem with a software update. The National Highway Traffic Safety Administration confirmed the recall and is in ongoing discussions with Zoox.
6 source articles · read the reporting →
Justine Saint Amour is suing Tesla after her Cybertruck, with Full Self-Driving engaged, crashed into a concrete barrier on a Houston overpass on August 18, 2025. The lawsuit alleges that Tesla was negligent in hiring and retaining Elon Musk as CEO, and that the FSD system was defective due to lack of LiDAR and ineffective automatic emergency braking. Saint Amour seeks over $1 million in damages.
3 source articles · read the reporting →
On 11 June 2018, a self-driving Cruise Chevrolet Bolt was rear-ended by another Cruise vehicle driven by a human employee on Bryant Street in San Francisco. The collision caused only minor scuffs and no injuries. Cruise reported the incident to the California DMV as required. The incident highlights the challenges of autonomous vehicles interacting with human drivers.
2 source articles · read the reporting →
Four self-driving cars in California have been involved in accidents since September 2014, when the state began issuing testing permits. Two occurred while the cars were in autonomous mode, and two while a human was driving. Google and Delphi, the companies operating the vehicles, stated that their cars were not at fault and that the collisions were minor, with no injuries. The accidents have raised concerns about transparency, as details are kept confidential under state law.
10 source articles · read the reporting →
An automated bus operated by Beep was rear-ended by a Tesla driver making an illegal lane change in Washington D.C. on 18 January 2026. The bus, part of a pilot programme with the U.S. Department of Transportation, had a human backup driver and sustained minor cosmetic damage. Service was temporarily paused but resumed after a review found the bus operated appropriately. No police were called and the incident was not reported to NHTSA as the damage was under $1,000 and the other driver was at fault.
2 source articles · read the reporting →
