_Incident · Collision_

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

Canonical ID: `41a60345-c7cf-42c4-a141-90b7426a77fd`

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

On January [XXX], 2026 at 2:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a traffic cone on [XXX] near [XXX].
The Waymo AV was traveling northwestbound on [XXX] in the right lane when it slowed to a stop for a queue of traffic for a red light at the intersection with [XXX]. After the light turned green and traffic ahead advanced, the Waymo AV proceeded forward. A pickup truck traveling northwestbound on [XXX] in the left lane proceeded forward and a rear seat passenger of the pickup truck threw a traffic cone from the window and into the roadway, and the traffic cone landed in the Waymo AV's lane of travel. As the Waymo AV proceeded forward the front of the Waymo AV made contact with the traffic cone. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV 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-13607

## Common questions

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

On January [XXX], 2026 at 2:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a traffic cone on [XXX] near [XXX].
The Waymo AV was traveling northwestbound on [XXX] in the right lane when it slowed to a stop for a queue of traffic for a red light at the intersection with [XXX]. After the light turned green and traffic ahead advanced, the Waymo AV proceeded forward. A pickup truck traveling northwestbound on [XXX] in the left lane proceeded forward and a rear seat passenger of the pickup truck threw a traffic cone from the window and into the roadway, and the traffic cone landed in the Waymo AV's lane of travel. As the Waymo AV proceeded forward the front of the Waymo AV made contact with the traffic cone. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV 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 January 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-13607)?

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

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

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


_API: GET /v1/incidents/41a60345-c7cf-42c4-a141-90b7426a77fd · sources: /v1/incidents/41a60345-c7cf-42c4-a141-90b7426a77fd/sources · responses: /v1/incidents/41a60345-c7cf-42c4-a141-90b7426a77fd/responses · status: /v1/incidents/41a60345-c7cf-42c4-a141-90b7426a77fd/status · canonical URL: /incidents/nhtsa-sgo-30270-13607_