_Incident · Collision_

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

Canonical ID: `a378ba18-f18a-4382-bbb3-aa9eaf52aace`

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

On August 16, 2025 at 7:47 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] and [XXX]. 
The Waymo AV was traveling westbound on [XXX] when it came to a stop in the intersection with [XXX] to yield to a heavy truck that was traveling northwestbound on [XXX] and attempting to make a sharp left turn onto southbound [XXX]. The heavy truck reversed momentarily in the Waymo AV's lane of travel and proceeded forward before it stopped facing south for pedestrians that were crossing [XXX]. The Waymo AV proceeded to maneuver around the stationary heavy truck, passing to the rear of the truck. While the Waymo AV was passing behind the heavy truck, the heavy truck began reversing and the rear of the heavy truck made contact with the left side of the 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 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-11516

## Common questions

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

On August 16, 2025 at 7:47 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a heavy truck on [XXX] and [XXX]. 
The Waymo AV was traveling westbound on [XXX] when it came to a stop in the intersection with [XXX] to yield to a heavy truck that was traveling northwestbound on [XXX] and attempting to make a sharp left turn onto southbound [XXX]. The heavy truck reversed momentarily in the Waymo AV's lane of travel and proceeded forward before it stopped facing south for pedestrians that were crossing [XXX]. The Waymo AV proceeded to maneuver around the stationary heavy truck, passing to the rear of the truck. While the Waymo AV was passing behind the heavy truck, the heavy truck began reversing and the rear of the heavy truck made contact with the left side of the 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 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 August 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 San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-11516)?

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

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

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


_API: GET /v1/incidents/a378ba18-f18a-4382-bbb3-aa9eaf52aace · sources: /v1/incidents/a378ba18-f18a-4382-bbb3-aa9eaf52aace/sources · responses: /v1/incidents/a378ba18-f18a-4382-bbb3-aa9eaf52aace/responses · status: /v1/incidents/a378ba18-f18a-4382-bbb3-aa9eaf52aace/status · canonical URL: /incidents/nhtsa-sgo-30270-11516_
