Report 30270-8021

Date

Jun 2024

Manufacturer

Waymo LLC

Vehicle

2024 Jaguar I-Pace

Location

San Francisco, CA

Speed

0 mph

Engagement

ADS

Report narrative

What was reported

The content of this report is unchanged from the initial report submitted on July 2, 2024 [REDACTED, MAY CONTAIN CONFIDENTIAL BUSINESS INFORMATION]. On June [XXX], 2024 at 9:24 PM PT a Waymo Autonomous Vehicle (Waymo AV) operating in [XXX], California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southeast on [XXX] in the leftmost lane when it approached the intersection with [XXX]. As the Waymo AV approached the intersection and prepared to make an unprotected left turn onto northbound [XXX], it slowed to yield to a passenger car proceeding straight on northwest [XXX]. As soon as the passenger car had passed the Waymo AV, the Waymo AV began to make the unprotected left turn onto northbound [XXX], turning behind the passenger car. The Waymo AV then slowed to a stop to yield for pedestrians entering the crosswalk ahead. The passenger car then stopped and immediately began to reverse toward the Waymo AV and the rear of the passenger car made contact with the front driver side of the Waymo AV as it yielded for the pedestrians. At the time of the impact, the Waymo AVs 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 vulnerable road user influenced the driving task of a vehicle involved. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash context

Conditions and outcome

Injury severity alleged

No Injuries Reported

Crash with

Passenger Car

Subject movement

Stopped

Roadway

Intersection

Weather

Clear

SGO metadata

Report details

Report type

10-Day Update

Report version

2

Submission date

JUL-2024

Incident time

21:24

Operating entity

Waymo LLC

Driver / operator type

None

Within ODD

Yes

Same vehicle ID

e0846443b7c6da5

Same incident ID

88cda6faf7e7791