_Incident · Collision_

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

Canonical ID: `ffb0987f-4df3-4fd9-9484-d96a8c5a17a4`

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

On July [XXX], 2026 at 04:38 AM MST a [Waymo](/companies/waymo.md) Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. 

The Waymo AV was travelling westbound on [XXX] in the third from the right lane and proceeding straight at a green light at the intersection with [XXX]. As the Waymo AV approached the exit of the intersection, a pickup truck travelling westbound in the rightmost lane on [XXX] changed lanes to the adjacent left lane, entering the Waymo AV's lane of travel. The Waymo AV maneuvered to the left as the pickup truck continued to change lanes, and the front left side of the pickup truck made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged. Both vehicles sustained damage. Waymo became aware of the tow deployment on July 11th, 2026 after an additional review of available information.

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-15829

## Common questions

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

On July [XXX], 2026 at 04:38 AM MST a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. 

The Waymo AV was travelling westbound on [XXX] in the third from the right lane and proceeding straight at a green light at the intersection with [XXX]. As the Waymo AV approached the exit of the intersection, a pickup truck travelling westbound in the rightmost lane on [XXX] changed lanes to the adjacent left lane, entering the Waymo AV's lane of travel. The Waymo AV maneuvered to the left as the pickup truck continued to change lanes, and the front left side of the pickup truck made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged. Both vehicles sustained damage. Waymo became aware of the tow deployment on July 11th, 2026 after an additional review of available information.

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

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

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

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


_API: GET /v1/incidents/ffb0987f-4df3-4fd9-9484-d96a8c5a17a4 · sources: /v1/incidents/ffb0987f-4df3-4fd9-9484-d96a8c5a17a4/sources · responses: /v1/incidents/ffb0987f-4df3-4fd9-9484-d96a8c5a17a4/responses · status: /v1/incidents/ffb0987f-4df3-4fd9-9484-d96a8c5a17a4/status · canonical URL: /incidents/nhtsa-sgo-30270-15829_