_Incident · Collision_

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

Canonical ID: `be63af50-bf36-4048-bc6c-1a4f92ee5a97`

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

On December [XXX], 2025 at 6:32 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving an SUV on [XXX] at the U.S. [XXX] on-ramp.
The Waymo AV was traveling northbound in the leftmost lane on [XXX] when it slowed to a stop to yield to a passenger car stopped facing north in the leftmost lane at a green light at the intersection with the U.S. [XXX] on-ramp. While the Waymo AV was stopped, an SUV traveling northbound in the leftmost lane on [XXX] approached the Waymo AV from behind and slowed to a stop. While the passenger car, the Waymo AV, and the SUV, were all stopped, a van traveling northbound in the leftmost lane on [XXX] approached the stopped SUV from behind and the front left side of the van made contact with the rear right side of the stationary SUV, and as a result the front right side of the SUV then made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous 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-13303

## Common questions

### What happened in ADS crash report in Tempe, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-13303)?

On December [XXX], 2025 at 6:32 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving an SUV on [XXX] at the U.S. [XXX] on-ramp.
The Waymo AV was traveling northbound in the leftmost lane on [XXX] when it slowed to a stop to yield to a passenger car stopped facing north in the leftmost lane at a green light at the intersection with the U.S. [XXX] on-ramp. While the Waymo AV was stopped, an SUV traveling northbound in the leftmost lane on [XXX] approached the Waymo AV from behind and slowed to a stop. While the passenger car, the Waymo AV, and the SUV, were all stopped, a van traveling northbound in the leftmost lane on [XXX] approached the stopped SUV from behind and the front left side of the van made contact with the rear right side of the stationary SUV, and as a result the front right side of the SUV then made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous 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 December 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-13303)?

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

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

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


_API: GET /v1/incidents/be63af50-bf36-4048-bc6c-1a4f92ee5a97 · sources: /v1/incidents/be63af50-bf36-4048-bc6c-1a4f92ee5a97/sources · responses: /v1/incidents/be63af50-bf36-4048-bc6c-1a4f92ee5a97/responses · status: /v1/incidents/be63af50-bf36-4048-bc6c-1a4f92ee5a97/status · canonical URL: /incidents/nhtsa-sgo-30270-13303_