Report 30270-9409

Date

Nov 2024

Manufacturer

Waymo LLC

Vehicle

2021 Jaguar I-Pace

Location

Scottsdale, AZ

Speed

0 mph

Engagement

ADS

Report narrative

What was reported

On Saturday, November [XXX], 2024 at 1:27 AM MST, a Waymo Autonomous Vehicle ("Waymo AV") operating in Scottsdale, Arizona was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling north on [XXX] when it encountered a queue of double-parked vehicles in the northbound lane. The Waymo AV began passing the double-parked vehicles on the left, but as it did so the queue of double-parked vehicles began to proceed. The Waymo AV began to merge back into the northbound lane, but a vehicle in the queue then double-parked again before the Waymo AV could fully merge back into the northbound lane. The Waymo AV then began reversing to make space for southbound traffic but came to a stop before completing its reversing maneuver to yield to traffic approaching the Waymo AV from the rear. A passenger car traveling south on [XXX] then crossed the double yellow line to pass the Waymo AV in the northbound lane. As it did so, the rear passenger side of the passenger car made contact with the rear driver side of the Waymo AV. The passenger was not belted at the time, likely because the AV had just departed its pickup location. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The passenger car sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. 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

Street

Weather

Clear

SGO metadata

Report details

Report type

Monthly

Report version

1

Submission date

DEC-2024

Incident time

01:27

Operating entity

Waymo LLC

Driver / operator type

None

Within ODD

Yes

Same vehicle ID

18759114accd4fb

Same incident ID

5f48e9152ed0078