_Incident · Collision_

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

Canonical ID: `515dcb5e-ecd3-476d-a0f1-0f1d75ddd17e`

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

On June [XXX], 2025 at 2:27 PM PT a [Waymo](/companies/waymo.md) 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 facing north in the rightmost lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV remained stopped, a passenger car that was stopped in the leftmost lane of [XXX], oriented diagonally relative to the roadway facing northeast after exiting a parallel parking spot at the west side curb of [XXX], proceeded northeastbound into the rightmost lane and the front of the passenger car made contact with the rear driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Neither vehicle sustained damage. A passenger in the Waymo AV reported a minor injury and was transported to a hospital in an ambulance. 
Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. 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-11192

## Common questions

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

On June [XXX], 2025 at 2:27 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 facing north in the rightmost lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV remained stopped, a passenger car that was stopped in the leftmost lane of [XXX], oriented diagonally relative to the roadway facing northeast after exiting a parallel parking spot at the west side curb of [XXX], proceeded northeastbound into the rightmost lane and the front of the passenger car made contact with the rear driver side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Neither vehicle sustained damage. A passenger in the Waymo AV reported a minor injury and was transported to a hospital in an ambulance. 
Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. 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 June 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-11192)?

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

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

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


_API: GET /v1/incidents/515dcb5e-ecd3-476d-a0f1-0f1d75ddd17e · sources: /v1/incidents/515dcb5e-ecd3-476d-a0f1-0f1d75ddd17e/sources · responses: /v1/incidents/515dcb5e-ecd3-476d-a0f1-0f1d75ddd17e/responses · status: /v1/incidents/515dcb5e-ecd3-476d-a0f1-0f1d75ddd17e/status · canonical URL: /incidents/nhtsa-sgo-30270-11192_