DEPLOYDatabase

Incident · Collision

ADS crash report in Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11412)

On July [XXX], 2025 at 11:39 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] and slowing to a stop in response to a passenger car that was traveling westbound on [XXX] and turning right onto northbound [XXX]. As the passenger car was completing its turn, it crossed the center line into the Waymo AV's lane of travel and the driver side of the passenger car made contact with the driver side of the stationary Waymo AV. 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 2025-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 Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11412)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11412)?
On July [XXX], 2025 at 11:39 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was traveling southbound on [XXX] and slowing to a stop in response to a passenger car that was traveling westbound on [XXX] and turning right onto northbound [XXX]. As the passenger car was completing its turn, it crossed the center line into the Waymo AV's lane of travel and the driver side of the passenger car made contact with the driver side of the stationary Waymo AV. 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, 2025 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 Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11412)?
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 Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11412)?
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 Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11412)?
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-07-14

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-07-14

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 Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11412).

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 25b7889a-3aca-400c-b8b3-3ecee99e09b0