_Incident · Collision_

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

Canonical ID: `e9fe9194-a9fc-44ca-a952-ade9c59b807e`

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

On August [XXX], 2026 at 6:03 PM PDT a [Waymo](/companies/waymo.md) Autonomous Vehicle ("Waymo AV") operating in [San Francisco](/locations/san-francisco-ca.md), [California](/locations/california.md) was in a collision involving a passenger car on [XXX] at [XXX].

The Waymo AV was stopped facing northwest in the crosswalk across [XXX] at the intersection with [XXX] after a passenger dropoff. While the Waymo AV was stopped, a passenger car traveling westbound on [XXX] proceeded through the intersection with [XXX] and maneuvered to the left as it approached the Waymo AV from behind. As the passenger car continued to maneuver across the crosswalk to pass the Waymo AV, the right side of the passenger car 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. Both vehicles sustained damage.

Waymo is reporting this crash under Request No. 1 of [Standing General Order 2021-01](/regulations/nhtsa-av-framework.md) 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-16410

## Common questions

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

On August [XXX], 2026 at 6:03 PM PDT a [Waymo Autonomous Vehicle](/models/alphabet-waymo.md) ("[Waymo](/companies/waymo.md) AV") operating in [San Francisco](/locations/san-francisco-ca.md), [California](/locations/california.md) was in a collision involving a passenger car on [XXX] at [XXX].

The Waymo AV was stopped facing northwest in the crosswalk across [XXX] at the intersection with [XXX] after a passenger dropoff. While the Waymo AV was stopped, a passenger car traveling westbound on [XXX] proceeded through the intersection with [XXX] and maneuvered to the left as it approached the Waymo AV from behind. As the passenger car continued to maneuver across the crosswalk to pass the Waymo AV, the right side of the passenger car 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. Both vehicles sustained damage.

Waymo is reporting this crash under Request No. 1 of [Standing General Order 2021-01](/regulations/nhtsa-av-framework.md) 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, 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-16410)?

The incident is recorded as involving [Waymo](/companies/waymo.md) 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-16410)?

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

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


_API: GET /v1/incidents/e9fe9194-a9fc-44ca-a952-ade9c59b807e · sources: /v1/incidents/e9fe9194-a9fc-44ca-a952-ade9c59b807e/sources · responses: /v1/incidents/e9fe9194-a9fc-44ca-a952-ade9c59b807e/responses · status: /v1/incidents/e9fe9194-a9fc-44ca-a952-ade9c59b807e/status · canonical URL: /incidents/nhtsa-sgo-30270-16410_