_Incident · Collision_

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

Canonical ID: `3c427a0a-bde2-48f6-9fb1-e5d73983d1a0`

- **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 12:55 AM 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 an SUV on [XXX] near [XXX].

The Waymo AV was stopped facing northwest along the north curb on [XXX], partially in-lane, with its hazard lights activated for a passenger dropoff. While the Waymo AV was stopped, an SUV traveling northwestbound on [XXX] in the right lane began to pass the Waymo AV to the left. At the same time, a passenger in the Waymo AV opened the rear left door, and the right side of the SUV made contact with the open rear left door 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. One of the passengers in the Waymo AV was not belted at the time of the collision as they were preparing to exit the vehicle.

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-16456

## Common questions

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

On August [XXX], 2026 at 12:55 AM 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 an SUV on [XXX] near [XXX].

The Waymo AV was stopped facing northwest along the north curb on [XXX], partially in-lane, with its hazard lights activated for a passenger dropoff. While the Waymo AV was stopped, an SUV traveling northwestbound on [XXX] in the right lane began to pass the Waymo AV to the left. At the same time, a passenger in the Waymo AV opened the rear left door, and the right side of the SUV made contact with the open rear left door 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. One of the passengers in the Waymo AV was not belted at the time of the collision as they were preparing to exit the vehicle.

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

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

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

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


_API: GET /v1/incidents/3c427a0a-bde2-48f6-9fb1-e5d73983d1a0 · sources: /v1/incidents/3c427a0a-bde2-48f6-9fb1-e5d73983d1a0/sources · responses: /v1/incidents/3c427a0a-bde2-48f6-9fb1-e5d73983d1a0/responses · status: /v1/incidents/3c427a0a-bde2-48f6-9fb1-e5d73983d1a0/status · canonical URL: /incidents/nhtsa-sgo-30270-16456_