Navya Arma Autonom DL Incident

InjuryADS

Report ID: 30490-6359 ยท AUG-2023 at 17:54

Crash Details

Weather

๐ŸŒค๏ธ Clear

Roadway Type

๐Ÿ›ฃ๏ธ Intersection

Crash Type

๐Ÿ’ฅ Passenger Car

Pre-crash Movement

Proceeding Straight

Vehicle Information

MakeNavya
ModelArma Autonom DL
YearUnknown
ManufacturerBeep, Inc.
System EngagedADS
Driver TypeIn-Vehicle (Commercial / Test)

๐Ÿ“ Location

San Francisco, CA

Operating Entity: Beep, Inc.

Evidence & Data

๐ŸŽฅVideo Availableโœ“
๐Ÿ‘ฎPolice Reportโœ—
๐Ÿ“ŠEDR Dataโœ—
๐ŸŽˆAirbag Deployedโœ—
๐Ÿš›Vehicle Towedโœ—

Narrative

VIN # VG9A2CB2CIV[XXX] At approximately 5:54 p.m. on Wednesday, August [XXX], 2023, P84, travelling eastbound on [XXX], approached the three-way stop at [XXX] and [XXX]. P84 arrived at the intersection at the same time as two other vehicles: a grey van heading northbound on [XXX] and a red sedan heading westbound on [XXX]. The safety driver yielded to the northbound vehicle, which proceeded to make a right-hand turn eastbound onto [XXX]. After allowing the intersection to clear, the safety driver onboard P84 confirmed that it was safe for the shuttle to proceed through the intersection. As the shuttle entered the intersection, a second vehicle travelling northbound on [XXX], a white sedan, entered the intersection intending a left-hand turn onto westbound [XXX]. Both vehicles entered the intersection simultaneously, subsequently colliding at a low rate of speed in the middle of the intersection. At approximately 5:57 p.m., the Beep Command Center (BCC) was informed by the safety driver that P84 was involved in a minor collision with another vehicle at the intersection of [XXX] and [XXX]. The incident response protocol was initiated, and a supervisor dispatched to the scene. Local law enforcement (San Francisco Police Department) was contacted to report the collision but declined to respond given the minor nature of the collision, directing both parties to exchange information. After the Beep supervisor arrived on scene at approximately 6:49 p.m., the safety driver and supervisor removed the shuttle from the roadway and exchanged insurance information with the driver of the other vehicle. Damage to both vehicles was noted to be very minor. The shuttle sustained light scuffs, chips, and small paint transfer. The other vehicle sustained a small dent on the fender. Neither vehicle required towing, and both were safely driven from the scene. Beeps safety driver was subsequently subjected to a standard post-collision drug & alcohol screening which has since cleared. Contributing Factors Based on an analysis of the available evidence, Beep has determined the following factors may have contributed to the higher likelihood of a collision occurring in this instance: 1.The white sedan failed to yield to P84 in accordance with California state law governing intersection priority. 2.The slight bend in P84s path to accommodate the lane shift through the intersection may have reduced the available stopping distance as the white sedan was not perceived as an obstacle in P84s path until it proceeded further into the intersection. Incident Findings Beep developed the following findings regarding this incident: 1.P84 behaved as expected, detecting and maintaining awareness of the white sedan in the moments preceding the collision, commanding hard braking maneuver, and achieving a 3m/s2 deceleration rate once the white sedan encroached on P84s path. 2.The safety driver observed California state law and had the right of way when releasing P84 into the intersection. 3.The safety driver could have avoided the collision by using the emergency stop. The safety driver indicated that they were aware of the other vehicle through the duration of the incident and were aware of the proper procedure in this scenario but panicked in the moment. Mitigation: Implement a priority zone to account for the slight bend in the shuttles path and for future vehicles that may fail to yield.
View Beep, Inc. Profile โ†’CA Incidents โ†’All Incidents โ†’