_Incident · Collision_

# ADS crash report in Los Angeles, CA involving a ZEEKR RT (NHTSA SGO 30270-14707)

Canonical ID: `d6426d64-ab0a-471a-bace-75b6ed1e65a7`

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

On April [XXX], 2026 at 9:44 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. 

The Waymo AV was traveling southeastbound on a narrow portion of [XXX], with vehicles parked at the curb in both directions, in autonomous mode. The Waymo AV transitioned to manual mode and the test driver continued proceeding forward on a curve of [XXX] where the roadway continued to the left, and the front right side of the Waymo AV made contact with the rear left side of a passenger car parked facing southeast at the curb. As a result of this collision, the passenger car was pushed forward, and the front of the passenger car made contact with the rear of a second passenger car parked directly in front of the first passenger car. 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. All three 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.

## Sources (1)

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

## Common questions

### What happened in ADS crash report in Los Angeles, CA involving a ZEEKR RT (NHTSA SGO 30270-14707)?

On April [XXX], 2026 at 9:44 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. 

The Waymo AV was traveling southeastbound on a narrow portion of [XXX], with vehicles parked at the curb in both directions, in autonomous mode. The Waymo AV transitioned to manual mode and the test driver continued proceeding forward on a curve of [XXX] where the roadway continued to the left, and the front right side of the Waymo AV made contact with the rear left side of a passenger car parked facing southeast at the curb. As a result of this collision, the passenger car was pushed forward, and the front of the passenger car made contact with the rear of a second passenger car parked directly in front of the first passenger car. 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. All three 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.

### When did this incident occur?

The incident is recorded as occurring on April 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 Los Angeles, CA involving a ZEEKR RT (NHTSA SGO 30270-14707)?

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 Los Angeles, CA involving a ZEEKR RT (NHTSA SGO 30270-14707)?

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 Los Angeles, CA involving a ZEEKR RT (NHTSA SGO 30270-14707)?

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


_API: GET /v1/incidents/d6426d64-ab0a-471a-bace-75b6ed1e65a7 · sources: /v1/incidents/d6426d64-ab0a-471a-bace-75b6ed1e65a7/sources · responses: /v1/incidents/d6426d64-ab0a-471a-bace-75b6ed1e65a7/responses · status: /v1/incidents/d6426d64-ab0a-471a-bace-75b6ed1e65a7/status · canonical URL: /incidents/nhtsa-sgo-30270-14707_