_Incident · Collision_

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

Canonical ID: `90e5f9c5-0d4a-4aae-aa44-2a9db6a1bc5e`

- **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 5:45 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 an SUV on [XXX] near [XXX].

The Waymo AV was traveling eastbound on [XXX], approaching an SUV facing southeast and executing a parking maneuver along the south curb of [XXX], near the intersection with [XXX]. The Waymo AV slowed to yield to the SUV as the SUV maneuvered forward towards the south curb and came to a stop, partially in the Waymo AV's lane of travel. While the SUV was stopped, the Waymo AV maneuvered left to pass the SUV, and as the SUV began to reverse , the rear left side of the SUV made contact with the rear right side of the 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-16258

## Common questions

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

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

The Waymo AV was traveling eastbound on [XXX], approaching an SUV facing southeast and executing a parking maneuver along the south curb of [XXX], near the intersection with [XXX]. The Waymo AV slowed to yield to the SUV as the SUV maneuvered forward towards the south curb and came to a stop, partially in the Waymo AV's lane of travel. While the SUV was stopped, the Waymo AV maneuvered left to pass the SUV, and as the SUV began to reverse , the rear left side of the SUV made contact with the rear right side of the 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-16258)?

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

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

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


_API: GET /v1/incidents/90e5f9c5-0d4a-4aae-aa44-2a9db6a1bc5e · sources: /v1/incidents/90e5f9c5-0d4a-4aae-aa44-2a9db6a1bc5e/sources · responses: /v1/incidents/90e5f9c5-0d4a-4aae-aa44-2a9db6a1bc5e/responses · status: /v1/incidents/90e5f9c5-0d4a-4aae-aa44-2a9db6a1bc5e/status · canonical URL: /incidents/nhtsa-sgo-30270-16258_