DEPLOYDatabase

Incident · Collision

ADS crash report in San Francisco, CA involving a ZEEKR RT (NHTSA SGO 30270-16038)

On July [XXX], 2026 at 7:55 PM PDT 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 parked facing west on a narrow portion of [XXX], with vehicles parked perpendicular to the curb on either side of the roadway, and with its hazard lights activated after a passenger dropoff. While the Waymo AV was parked, a queue of traffic formed in the adjacent eastbound lane on [XXX], stopped facing east for a red light at the intersection with [XXX]. An SUV initially parked facing south, perpendicular to the south curb, reversed into the roadway at an angle and proceeded forward and to the left before stopping at the end of the queue of traffic, facing southeast, partially in both the eastbound and westbound lanes of [XXX]. The Waymo AV unparked and proceeded forward on westbound [XXX], then came to a stop to yield to the stopped SUV in the Waymo AV's lane of travel. The vehicles in the queue of traffic, including the stopped SUV, nudged forward momentarily, and the Waymo AV proceeded forward at a low rate of speed to maneuver between the stopped SUV and a passenger car parked facing south perpendicular to the north curb, on the Waymo AV's immediate right, and the right side of the Waymo AV made contact with the front of the parked passenger car. 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.

Occurred 2026-07-01 · Waymo

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.

Machine-readable surfaces

Sources (1)

  1. https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30270-16038

Common questions

What happened in ADS crash report in San Francisco, CA involving a ZEEKR RT (NHTSA SGO 30270-16038)?
On July [XXX], 2026 at 7:55 PM PDT 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 parked facing west on a narrow portion of [XXX], with vehicles parked perpendicular to the curb on either side of the roadway, and with its hazard lights activated after a passenger dropoff. While the Waymo AV was parked, a queue of traffic formed in the adjacent eastbound lane on [XXX], stopped facing east for a red light at the intersection with [XXX]. An SUV initially parked facing south, perpendicular to the south curb, reversed into the roadway at an angle and proceeded forward and to the left before stopping at the end of the queue of traffic, facing southeast, partially in both the eastbound and westbound lanes of [XXX]. The Waymo AV unparked and proceeded forward on westbound [XXX], then came to a stop to yield to the stopped SUV in the Waymo AV's lane of travel. The vehicles in the queue of traffic, including the stopped SUV, nudged forward momentarily, and the Waymo AV proceeded forward at a low rate of speed to maneuver between the stopped SUV and a passenger car parked facing south perpendicular to the north curb, on the Waymo AV's immediate right, and the right side of the Waymo AV made contact with the front of the parked passenger car. 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.
When did this incident occur?
The incident is recorded as occurring on July 1, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in ADS crash report in San Francisco, CA involving a ZEEKR RT (NHTSA SGO 30270-16038)?
The incident is recorded as involving Waymo on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to ADS crash report in San Francisco, CA involving a ZEEKR RT (NHTSA SGO 30270-16038)?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of ADS crash report in San Francisco, CA involving a ZEEKR RT (NHTSA SGO 30270-16038)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 1 source (1 primary) · last reviewed 2026-09-29

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-09-29

Sources by quality tier

1
primary-regulatory-filing
Regulatory filing

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for ADS crash report in San Francisco, CA involving a ZEEKR RT (NHTSA SGO 30270-16038).

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.


Canonical ID 3e9db4c7-6956-49d7-b83b-de14404d6e0c