_Incident · Collision_

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

Canonical ID: `00823a56-bf1f-431c-bb0a-0d5b85ac773f`

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

On August[XXX], 2025 at 4:54 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. 
The Waymo AV was stopped in the rightmost lane facing northeast on [XXX] in a queue of traffic at the intersection with [XXX] at a location where the rightmost lane and leftmost lane are separated by a raised transit boarding island. As the queue of traffic advanced, the Waymo AV began moving forward. A scooterist traveling northeastbound in the rightmost lane proceeded to pass to the right of the Waymo AV followed closely by a cyclist, and the Waymo AV shifted left towards the raised boarding island and  slowed to a stop to yield to the scooterist and cyclist. A passenger car traveling behind the Waymo AV approached the Waymo AV from behind and the front of the passenger car 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. Both 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-11488

## Common questions

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

On August[XXX], 2025 at 4:54 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. 
The Waymo AV was stopped in the rightmost lane facing northeast on [XXX] in a queue of traffic at the intersection with [XXX] at a location where the rightmost lane and leftmost lane are separated by a raised transit boarding island. As the queue of traffic advanced, the Waymo AV began moving forward. A scooterist traveling northeastbound in the rightmost lane proceeded to pass to the right of the Waymo AV followed closely by a cyclist, and the Waymo AV shifted left towards the raised boarding island and  slowed to a stop to yield to the scooterist and cyclist. A passenger car traveling behind the Waymo AV approached the Waymo AV from behind and the front of the passenger car 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. Both 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 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-11488)?

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

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

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


_API: GET /v1/incidents/00823a56-bf1f-431c-bb0a-0d5b85ac773f · sources: /v1/incidents/00823a56-bf1f-431c-bb0a-0d5b85ac773f/sources · responses: /v1/incidents/00823a56-bf1f-431c-bb0a-0d5b85ac773f/responses · status: /v1/incidents/00823a56-bf1f-431c-bb0a-0d5b85ac773f/status · canonical URL: /incidents/nhtsa-sgo-30270-11488_