The 2023 Cruise Incident: What Actually Happened

On October 2, 2023, a Cruise autonomous vehicle struck a pedestrian in San Francisco, and the car then drove itself to a nearby parking lot with the injured person still pinned under it. The vehicle did not stop at the scene of the collision. Instead, it continued moving and came to rest in a residential area several blocks away. Cruise, the autonomous vehicle company owned by General Motors, suspended its entire driverless taxi service in California the following day.

The pedestrian was a woman who had been hit by another vehicle first and was already lying in the street when the Cruise car struck her. She was transported to the hospital with serious injuries. The Cruise vehicle's sensors detected the collision, but the car's programming directed it to move to what the system classified as a safer location rather than stopping when ready at the point of impact.

This incident raised when ready questions about how autonomous vehicles respond to emergencies and whether their decision-making in crisis moments prioritizes human safety correctly. It also triggered investigations by the California Public Utilities Commission and the National Highway Traffic Safety Administration.

Key Takeaways

  • A Cruise robotaxi hit a pedestrian in San Francisco on October 2, 2023, and then drove itself away from the scene to a parking lot several blocks away.
  • The pedestrian was already injured from a collision with another vehicle when the Cruise car struck her, and she remained under the vehicle as it moved.
  • Cruise suspended all driverless operations in California when ready after the incident became public.
  • Both state and federal regulators opened investigations into how the vehicle's autonomous system handled the emergency.
  • The incident exposed a gap in autonomous vehicle programming: the car prioritized moving to a "safer" location over staying at the scene of a collision.

Why the Vehicle Moved Instead of Stopping

Cruise's autonomous system is programmed to detect collisions and assess whether the vehicle is in a dangerous location. When the car struck the pedestrian, its sensors registered the impact. The system then made a decision: it classified the current location as unsafe and directed the vehicle to drive to a nearby parking lot to get out of traffic.

This behavior reflects a design choice that prioritizes removing the vehicle from an active roadway. In many scenarios, that logic makes sense—a disabled car blocking traffic can create secondary collisions. However, in this case, the logic failed to account for the fact that a person was trapped beneath the vehicle. The car's programming did not include a protocol for "do not move if a person is under the vehicle."

After the incident, Cruise acknowledged that the vehicle should have remained at the scene. The company stated that it would update its software to prevent similar situations in the future.

What Happened to the Cruise Service After the Incident

Cruise when ready halted all driverless operations in San Francisco and across California. The company had been operating a paid robotaxi service called Cruise Origin in limited areas of San Francisco, with a small fleet of vehicles available to passengers through a mobile app.

Within days, Cruise also suspended operations in other cities where it had been testing, including Phoenix and Austin. The company's leadership acknowledged that the incident revealed a serious flaw in how the vehicles handled emergency situations. Cruise announced it would conduct a comprehensive review of its safety protocols before resuming service anywhere.

The suspension lasted several months. Cruise eventually returned to limited operations in some markets, but with reduced service areas and additional safety measures in place, including improved protocols for collision response.

Regulatory Response and Investigation

The California Public Utilities Commission, which oversees autonomous vehicle testing and deployment in the state, opened a formal investigation. The commission had previously granted Cruise a permit to operate a paid driverless taxi service, which made the incident a direct challenge to the regulator's oversight.

The National Highway Traffic Safety Administration also began investigating whether the vehicle's behavior violated any federal motor vehicle safety standards. NHTSA has authority over how all vehicles—autonomous or human-driven—are designed and manufactured.

Both investigations focused on whether Cruise's system design was safe enough for public roads and whether the company had adequately tested for emergency scenarios. The investigations also examined whether Cruise had disclosed known risks to regulators before the incident occurred.

How This Changed Autonomous Vehicle Safety Standards

The incident accelerated conversations about what safety requirements autonomous vehicles should meet before operating on public streets with passengers. Prior to this event, there was no federal standard requiring autonomous vehicles to remain at the scene of a collision or to prioritize not moving if a person is trapped beneath them.

Several states and cities began reviewing their own autonomous vehicle policies. Some jurisdictions tightened the rules for where and when driverless vehicles could operate. Others required companies to submit more detailed safety data before receiving permits.

The incident also highlighted a gap in how autonomous vehicles are tested. Most testing focuses on normal driving scenarios. Emergency situations—collisions, pedestrians in unexpected places, system failures—receive less attention in some testing protocols. After this event, companies and regulators began emphasizing the need for more rigorous emergency scenario testing.

What the Pedestrian's Outcome Was

The pedestrian was hospitalized with serious injuries. She had already been struck by another vehicle before the Cruise car hit her, which complicated her medical situation. After the incident became public, there were reports that she was receiving treatment, but specific details about her long-term recovery were not widely disclosed.

Cruise and the pedestrian's legal representatives eventually reached a settlement, though the terms were not made public. The incident raised questions about liability when an autonomous vehicle is involved in a collision—specifically, whether the vehicle's manufacturer, the operating company, or the owner bears responsibility.

Frequently Asked Questions

Did the Cruise car know a person was under it when it drove away?

The vehicle's sensors detected the collision, but the system did not have programming to determine whether a person was trapped beneath it. The car's decision to move was based on classifying the location as unsafe, not on assessing what was directly under the vehicle.

Could a human driver have prevented this?

Cruise vehicles operate fully autonomously—there is no human driver or remote operator controlling them during normal service. If a human driver had been present, they would likely have stopped when ready upon hitting someone and called for help.

Did Cruise face criminal charges?

The incident triggered regulatory investigations, but there were no criminal charges filed against Cruise or its employees. The focus was on civil liability and regulatory compliance rather than criminal prosecution.

Are Cruise vehicles back on the road now?

Cruise resumed limited operations in some cities after implementing safety updates, but the company's service area and fleet size remain smaller than before the incident. The company continues to operate under closer regulatory scrutiny.

What did Cruise change to prevent this from happening again?

Cruise updated its software to improve how the vehicle detects and responds to collisions. The company also enhanced its protocols for emergency situations, though specific technical details have not been fully disclosed publicly.