DEPLOYDatabase

Incident · Collision

ADS crash report in Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14389)

On March [XXX], 2026 at 7:59 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Inglewood, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing south on [XXX] in a queue of traffic for a stop sign at the intersection with [XXX]. As traffic ahead advanced, the Waymo AV slowly proceeded forward in the queue of traffic, and an SUV traveling southbound on [XXX] approached the Waymo AV from behind, and the front right side of the SUV made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. Waymo may supplement or correct its reporting with additional information as it may become available.

Occurred 2026-03-01 · Waymo

Track ADS crash report in Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14389)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14389)?
On March [XXX], 2026 at 7:59 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Inglewood, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was stopped facing south on [XXX] in a queue of traffic for a stop sign at the intersection with [XXX]. As traffic ahead advanced, the Waymo AV slowly proceeded forward in the queue of traffic, and an SUV traveling southbound on [XXX] approached the Waymo AV from behind, and the front right side of the SUV made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger of the Waymo AV was transported to a hospital by an ambulance with minor injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. 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 March 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 Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14389)?
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 Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14389)?
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 Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14389)?
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-07-12

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-07-12

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 Inglewood, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14389).

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 b17389a0-4a57-41b7-926c-08127857206e