_Incident · Collision_

# ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15984)

Canonical ID: `f0eba2bf-ff59-44f4-b2ee-f67789302ad0`

- **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 10:39 AM PDT a [Waymo](/companies/waymo.md) Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near[XXX].

The Waymo AV was stopped facing southwest, in-lane and near the west curb on [XXX], near the intersection with [XXX] to yield to a heavy truck turning right onto [XXX] from northwestbound [XXX]. While the Waymo AV was stopped, the heavy truck continued to turn right and began maneuvering between the Waymo AV and a passenger car parked facing northeast at the east curb on [XXX]. As the heavy truck proceeded forward, it passed the Waymo AV to the left, and the rear left side of the heavy truck trailer made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo became aware of the tow deployment on August 10, 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-15984

## Common questions

### What happened in ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15984)?

On July [XXX], 2026 at 10:39 AM PDT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] near[XXX].

The Waymo AV was stopped facing southwest, in-lane and near the west curb on [XXX], near the intersection with [XXX] to yield to a heavy truck turning right onto [XXX] from northwestbound [XXX]. While the Waymo AV was stopped, the heavy truck continued to turn right and began maneuvering between the Waymo AV and a passenger car parked facing northeast at the east curb on [XXX]. As the heavy truck proceeded forward, it passed the Waymo AV to the left, and the rear left side of the heavy truck trailer made contact with the rear left side of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo became aware of the tow deployment on August 10, 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 San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15984)?

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 San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15984)?

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 San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15984)?

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


_API: GET /v1/incidents/f0eba2bf-ff59-44f4-b2ee-f67789302ad0 · sources: /v1/incidents/f0eba2bf-ff59-44f4-b2ee-f67789302ad0/sources · responses: /v1/incidents/f0eba2bf-ff59-44f4-b2ee-f67789302ad0/responses · status: /v1/incidents/f0eba2bf-ff59-44f4-b2ee-f67789302ad0/status · canonical URL: /incidents/nhtsa-sgo-30270-15984_