_Incident · Collision_

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

Canonical ID: `ef2cfb6e-fc47-4868-8f7b-9fbc3c923b75`

- **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 09:09 PM MST a [Waymo](/companies/waymo.md) Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a heavy truck on [XXX] near  [XXX].

The Waymo AV was traveling southwestbound in the right lane on [XXX] behind a heavy truck traveling southwestbound partially in the right lane and partially in the left lane, on [XXX] with its hazard lights activated. The heavy truck slowed to a stop and the Waymo AV slowed to a stop to yield to the heavy truck. The heavy truck then reversed and made contact with the front of the stationary Waymo AV. The Waymo AV then reversed and slowed to a stop, and the heavy truck reversed again, the Waymo AV reversed again, and the rear of the heavy truck made contact with the front of the Waymo AV a second time. At the time of the impacts, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV 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-15897

## Common questions

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

On July [XXX], 2026 at 09:09 PM MST a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a heavy truck on [XXX] near  [XXX].

The Waymo AV was traveling southwestbound in the right lane on [XXX] behind a heavy truck traveling southwestbound partially in the right lane and partially in the left lane, on [XXX] with its hazard lights activated. The heavy truck slowed to a stop and the Waymo AV slowed to a stop to yield to the heavy truck. The heavy truck then reversed and made contact with the front of the stationary Waymo AV. The Waymo AV then reversed and slowed to a stop, and the heavy truck reversed again, the Waymo AV reversed again, and the rear of the heavy truck made contact with the front of the Waymo AV a second time. At the time of the impacts, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV 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 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 Scottsdale, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-15897)?

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

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

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


_API: GET /v1/incidents/ef2cfb6e-fc47-4868-8f7b-9fbc3c923b75 · sources: /v1/incidents/ef2cfb6e-fc47-4868-8f7b-9fbc3c923b75/sources · responses: /v1/incidents/ef2cfb6e-fc47-4868-8f7b-9fbc3c923b75/responses · status: /v1/incidents/ef2cfb6e-fc47-4868-8f7b-9fbc3c923b75/status · canonical URL: /incidents/nhtsa-sgo-30270-15897_