_Incident · Collision_

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

Canonical ID: `60180aec-89b0-4a8a-b76d-53a525ba2922`

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

On September[XXX], 2025 at 9:55 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. 
The Waymo AV was stopped facing southwest on [XXX] in a queue of traffic for a red light at the intersection at 4th Street[XXX]. The SUV stopped in front of the Waymo AV proceeded forward a short distance to close the distance with the vehicle in front of it, which was stopped at the red light. The Waymo AV followed by proceeding forward a short distance before both vehicles came to a stop. While the Waymo AV was proceeding forward, the SUV behind the Waymo AV proceeded forward as well, but did not stop when the Waymo AV came to a stop and the front of the SUV 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-11758

## Common questions

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

On September[XXX], 2025 at 9:55 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. 
The Waymo AV was stopped facing southwest on [XXX] in a queue of traffic for a red light at the intersection at 4th Street[XXX]. The SUV stopped in front of the Waymo AV proceeded forward a short distance to close the distance with the vehicle in front of it, which was stopped at the red light. The Waymo AV followed by proceeding forward a short distance before both vehicles came to a stop. While the Waymo AV was proceeding forward, the SUV behind the Waymo AV proceeded forward as well, but did not stop when the Waymo AV came to a stop and the front of the SUV 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 September 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-11758)?

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

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

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


_API: GET /v1/incidents/60180aec-89b0-4a8a-b76d-53a525ba2922 · sources: /v1/incidents/60180aec-89b0-4a8a-b76d-53a525ba2922/sources · responses: /v1/incidents/60180aec-89b0-4a8a-b76d-53a525ba2922/responses · status: /v1/incidents/60180aec-89b0-4a8a-b76d-53a525ba2922/status · canonical URL: /incidents/nhtsa-sgo-30270-11758_