DEPLOYDatabase

Incident · Collision

ADS crash report in Harbor City, CA involving a ZEEKR RT (NHTSA SGO 30270-16201)

On July [XXX], 2026 at 9:00 AM PDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Harbor City, California was in a collision involving a dip in the roadway on [XXX] near [XXX].

The Waymo AV was traveling northbound on [XXX] in autonomous mode. As the Waymo AV approached a dip in the roadway, the test driver transitioned the Waymo AV into manual mode and began slowing, and the front tires of the Waymo AV entered the dip. As the Waymo AV passed over the dip, the undercarriage of the Waymo AV made contact with the roadway. 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. The Waymo AV 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.
Track ADS crash report in Harbor City, CA involving a ZEEKR RT (NHTSA SGO 30270-16201)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Harbor City, CA involving a ZEEKR RT (NHTSA SGO 30270-16201)?
On July [XXX], 2026 at 9:00 AM PDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Harbor City, California was in a collision involving a dip in the roadway on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] in autonomous mode. As the Waymo AV approached a dip in the roadway, the test driver transitioned the Waymo AV into manual mode and began slowing, and the front tires of the Waymo AV entered the dip. As the Waymo AV passed over the dip, the undercarriage of the Waymo AV made contact with the roadway. 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. The Waymo AV 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 Harbor City, CA involving a ZEEKR RT (NHTSA SGO 30270-16201)?
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 Harbor City, CA involving a ZEEKR RT (NHTSA SGO 30270-16201)?
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 Harbor City, CA involving a ZEEKR RT (NHTSA SGO 30270-16201)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · 1 source (1 primary) · last reviewed 2026-10-04

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-10-04

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 Harbor City, CA involving a ZEEKR RT (NHTSA SGO 30270-16201).

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 674c627f-ad5a-4edb-a64d-c66dd3605609