_Incident · Collision_

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

Canonical ID: `84382b16-2d13-4579-b7e8-961e48600981`

- **Occurred:** 2026-09-01
- **Kind:** `collision`
- **Status (derived):** active
- **Company:** [Waymo](/companies/waymo.md) (id: `2128addc-20c8-4c31-aef5-be5ada97aede`)

On September [XXX], 2026 at 8:43 AM PDT a [Waymo](/companies/waymo.md) Autonomous Vehicle ("Waymo AV") operating in [San Francisco](/locations/san-francisco-ca.md), [California](/locations/california.md) was in a collision involving a passenger car on [XXX] near [XXX].

The Waymo AV was traveling southbound in autonomous mode with its right turn signal activated on [XXX] with vehicles parked at the curb in both directions. The Waymo AV began maneuvering to the right towards the west curb, and the test rider transitioned the Waymo AV into manual mode and began maneuvering the Waymo AV to the left, and the front right side of the Waymo AV made contact with the rear left side of a passenger car parked along the west curb. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test rider was operating the Waymo AV in manual mode. Both vehicles sustained damage.

Waymo is reporting this crash under Request No. 1 of [Standing General Order 2021-01](/regulations/nhtsa-av-framework.md) because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

## Sources (1)

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

## Common questions

### What happened in ADS crash report in San Francisco, CA involving a ZEEKR RT (NHTSA SGO 30270-16500)?

On September [XXX], 2026 at 8:43 AM PDT a [Waymo Autonomous Vehicle](/models/alphabet-waymo.md) ("[Waymo](/companies/waymo.md) AV") operating in [San Francisco](/locations/san-francisco-ca.md), [California](/locations/california.md) was in a collision involving a passenger car on [XXX] near [XXX].

The Waymo AV was traveling southbound in autonomous mode with its right turn signal activated on [XXX] with vehicles parked at the curb in both directions. The Waymo AV began maneuvering to the right towards the west curb, and the test rider transitioned the Waymo AV into manual mode and began maneuvering the Waymo AV to the left, and the front right side of the Waymo AV made contact with the rear left side of a passenger car parked along the west curb. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test rider was operating the Waymo AV in manual mode. Both vehicles sustained damage.

Waymo is reporting this crash under Request No. 1 of [Standing General Order 2021-01](/regulations/nhtsa-av-framework.md) because a vehicle involved was towed away. 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 September 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-16500)?

The incident is recorded as involving [Waymo](/companies/waymo.md) 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-16500)?

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-16500)?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.


_API: GET /v1/incidents/84382b16-2d13-4579-b7e8-961e48600981 · sources: /v1/incidents/84382b16-2d13-4579-b7e8-961e48600981/sources · responses: /v1/incidents/84382b16-2d13-4579-b7e8-961e48600981/responses · status: /v1/incidents/84382b16-2d13-4579-b7e8-961e48600981/status · canonical URL: /incidents/nhtsa-sgo-30270-16500_