_Incident · Collision_

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

Canonical ID: `fcadc402-4f00-4d4d-bf8e-649b86427411`

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

On March [XXX], 2026 at 11:52 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX]near [XXX].

The Waymo AV was stopped facing south on [XXX], partially in-lane and partially at the west curb with its hazard lights activated for a passenger dropoff. While the Waymo AV was stopped, a passenger car traveling southbound on [XXX] began passing the Waymo AV to the left. As the passenger car passed the Waymo AV, a passenger inside the Waymo AV opened the rear left door and the right side of the passenger car 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. The passenger in the Waymo AV was not belted at the time of the collision as they were preparing to exit the Waymo AV.

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

## Common questions

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

On March [XXX], 2026 at 11:52 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX]near [XXX].

The Waymo AV was stopped facing south on [XXX], partially in-lane and partially at the west curb with its hazard lights activated for a passenger dropoff. While the Waymo AV was stopped, a passenger car traveling southbound on [XXX] began passing the Waymo AV to the left. As the passenger car passed the Waymo AV, a passenger inside the Waymo AV opened the rear left door and the right side of the passenger car 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. The passenger in the Waymo AV was not belted at the time of the collision as they were preparing to exit the Waymo AV.

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 March 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-14488)?

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

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

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


_API: GET /v1/incidents/fcadc402-4f00-4d4d-bf8e-649b86427411 · sources: /v1/incidents/fcadc402-4f00-4d4d-bf8e-649b86427411/sources · responses: /v1/incidents/fcadc402-4f00-4d4d-bf8e-649b86427411/responses · status: /v1/incidents/fcadc402-4f00-4d4d-bf8e-649b86427411/status · canonical URL: /incidents/nhtsa-sgo-30270-14488_