Cruise turns left and stops right in path of oncoming vehicle resulting in collision
Incident
On 6/3/2022 at 11pm a Cruise robotaxi in autonomous mode was traveling eastbound on Geary Blvd. At Spruce St the Cruise vehicle entered the left-turn lane. On a green signal, it turned left across three lanes of traffic. The Cruise detected a Prius vehicle heading westbound, approaching in the curbside lane, and stopped in its path, resulting in a serious collision. Occupants of both vehicles were treated for reportedly minor injuries.
A software “fix” was made 3 days later to allegedly prevent this particular problem.
In rather poor timing, Cruise was granted permission by the CPUC the day before to charge passengers for rides.
Cruise report submitted to DMV
The DMV report clearly indicates that the Cruise vehicle suffered major damage:
Key text from the DMV report:
A Cruise autonomous vehicle (“Cruise AV”) operating in driverless autonomous mode, was traveling eastbound on Geary Boulevard toward the intersection with Spruce Street. As it approached the intersection, the Cruise AV entered the left hand turn lane, turned the left turn signal on, and initiated a left turn on a green light onto Spruce Street. At the same time, a Toyota Prius traveling westbound in the rightmost bus and turn lane of Geary Boulevard approached the intersection in the right turn lane. The Toyota Prius was traveling approximately 40 mph in a 25 mph speed zone. The Cruise AV came to a stop before fully completing its turn onto Spruce Street due to the oncoming Toyota Prius, and the Toyota Prius entered the intersection traveling straight from the turn lane instead of turning. Shortly thereafter, the Toyota Prius made contact with the rear passenger side of the Cruise AV. The impact caused damage to the right rear door, panel, and wheel of the Cruise AV. Police and Emergency Medical Services were called to the scene, and a police report was filed. The Cruise AV was towed from the scene. Occupants of both vehicles received medical treatment for allegedly minor injuries.
DMV report submitted by Cruise
Cruise report to NHTSA
Key text from the NHTSA report:
In a rare circumstance described below, a safety feature in the prior version of the subject ADS, known as the reflexive planner, caused the AV to hard brake while performing an unprotected left turn (“UPL”) when the ADS determined a hard brake was necessary to avoid a severe front-end collision with an oncoming vehicle or other road use. Cruise has decided to submit this voluntary report in the interest of transparency to the public and based on its discussions with NHTSA. Only one such incident has occurred in over 123,560 driverless UPLs performed prior to the updated software release. The incident involved an oncoming vehicle traveling well above the speed limit in a restricted right-turn/bus-only lane as the Cruise AV was performing a UPL. As the Cruise AV turned left and began traversing the intersection, the Cruise AV predicted that the oncoming vehicle, which was traveling approximately 40 mph in the 25 mph right-turn lane, would turn right and directly into the path of the Cruise AV. After the Cruise AV braked to avoid colliding with the front end of the oncoming vehicle, the oncoming vehicle suddenly moved out of the right-turn lane and proceeded straight through the intersection colliding with the rear right quarter panel of the Cruise AV. Cruise has determined that in this unique UPL situation, the ADS had to decide between two different risk scenarios and chose the one with the least potential for a serious collision at the time, before the oncoming vehicle’s sudden change of direction. Cruise has determined this scenario would not recur after a software update installed on all affected vehicles on July 6, 2022.
NHTSA Safety Recall Report 22E-072
Public Statements by Cruise (none)
Unlike later incidents, Cruise did not post any information about this incident on their website at https://getcruise.com/news/ .
News reports
There is some useful details covered in news reports, such as an overview of the incident, occupants of the vehicles, quotes from Phil Koopman, and Cruise not being transparent about the situation. It is noteworthy that the crash was not publicized until 7/7/22, over a month after the incident, and then only because Automative News discovered the incident by perusing DMV records. Cruise never provided useful information.
Collectively, Koopman said the incidents painted a problematic portrait.
“Everything is very concerning here,” he said. “With this crash in particular, there are a number of very concerning things upon a plain reading of the crash report. The onus should be on Cruise to prove they’re still safe to operate.“
Phil Koopman, CMU professor, in Automotive News
Show news…
Another great quote from Koopman:
“Many people have a word for a driver who cuts in front of them and then stops in the road, and it’s not a polite or charitable word,” he said.
Phil Koopman, CMU professor, in Automotive News
Cannot trust statements by Cruise:
General Motors-backed Cruise said its self-driving vehicle came to a stop in the roadway before completing its left turn, and was stationary when struck.
The company provided further statements about its interpretation of the position and behavior of the human-driven Toyota Prius in its filing, saying the Prius was speeding and that it had continued straight from a right-turn lane.
Those details could not be independently verified. A spokesperson for the San Francisco Police Department could not find an incident report related to the crash Wednesday, and said it was possible no report was generated.
Automotive News
Cruise really tried to not provide detailed information:
A Cruise spokesperson declined Wednesday to say why the AV stopped before completing its turn.
Automotive News
More on how cannot trust Cruise’s story:
Cruise stated that “occupants of both vehicles received medical treatment for allegedly minor injuries.” It’s important to note that we’re working with only one side of the story here; according to Automotive News, the San Francisco Police Department did not generate its own incident report on the matter, and Cruise’s interpretation of the events could not be independently verified.
Jalopnik
Information of occupants of vehicles and injuries:
According to the San Francisco Police Department, the Cruise autonomous vehicle had nobody in the driver’s seat and contained three adult passengers sitting in the rear seats of the vehicle. The Toyota Prius had one driver and one passenger.
When emergency services arrived at the scene, one Cruise passenger was transported to the hospital for non-life threatening injuries. The driver and passenger in the Prius were treated for minor injuries at the scene.
The crash led to major damage to Cruise’s vehicle, which was towed away from the scene. A Cruise spokesperson said that the company’s vehicle was not issued a citation by police related to the crash.
SF Standard
Additional news reports on the crash did not provide any truly useful details but all are listed here for completeness.
- AI Incident Database
Incident 293: Cruise’s Self-Driving Car Involved in a Multiple-Injury Collision at an San Francisco Intersection - SF Standard 7/7/22
Federal Regulators Launch Probe Into Cruise Self-Driving Car Crash in San Francisco - Automotive News 7/7/22
Cruise self-driving crash in San Francisco resulted in injuries; NHTSA investigating - Reuters 7/7/22
U.S. agency probing self-driving Cruise car crash in California - AutoEvolution 7/722
Cruise Robotaxi Was Involved in a Crash in San Francisco That Resulted in Injuries - InsideEVs 7/7/22
GM’s Cruise Self-Driving Car Crash Injured Multiple People - Jalopnik 7/7/22
NHTSA Investigating California Crash Involving Cruise Self-Driving Taxi - CNBC 7/7/22
U.S. safety regulators to probe crash involving self-driving car from GM-backed Cruise - GM Authority 7/7/22
One Of GM’s Cruise AVs Involved In Accident With Injuries - SF Standard 9/1/22
San Francisco Cruise Crash Leads to Software Recall in 80 Self-Driving Vehicles - Wired 9/1/22
GM’s Cruise Recalls Self-Driving Software Involved in June Crash - CNN Business 9/1/22
Cruise recalls its robotaxis after passenger injured in crash - Forbes 9/14/22
Cruise ‘Recalls’ Robotaxis After Crash, But The Recall Is The Wrong Mechanism
Pictures and Social Media (none)
Looked extensively for social media posts and for pictures on the incident, but could not find any. Even asked the neighbors if they happened to have witnessed the event and taken pictures.
This lack of notice is likely due to the crash happening back in June 2022, well before robotaxis had caught a lot of attention in San Francisco.
Police Report
At long last, the San Francisco Police Department provided a police incident report.
Police report…
The police report was not provided until weeks after the original crash analysis was published here. But better late than never. All others who investigated this crash were never able to obtain this report.
The police redacted the report of personally identifying information. They are supposed to provide details, yet not invade privacy.
There are a few key items in the report.
- The Cruise vehicle was indeed in the middle of the transit lane, as was deduced in the original crash analysis. This means that if the Cruise vehicle had simply continued moving forward it would not have been hit by the Prius.
- It is very peculiar that all three passengers of the Cruise vehicle stated that they thought the Prius was going to turn right, yet was moving fast and accelerating. Why would passengers in vehicle make this same, contradictory statement? And why did none of the passengers report that the Cruise vehicle stopped right in front of the path of the Prius? This appears to indicate that the passengers were somehow affiliated with Cruise and were not providing the full story.
- Why did Cruise not provide information to the police when requested? The police officer writing the report clearly did not realize that the Cruise vehicle stopped right in the path of the Prius. Because of this lack of information the police officer blamed the Prius driver for not yielding, which appears to be incorrect interpretation of what happened.
Speed Limit
The speed limit for that portion of Geary Blvd is indeed just 25mph. From the police report and statements from Cruise it appears that the Prius was speeding. But street design was also at fault.
Speed Limit…
The issue with street design is that the speed limit changed from 35mph down to 25mph less than 900 feet before the crash site, and the signage was very inadequate (and the transit lane started just 500 feet before the crash). This means that the Prius driver was not given reasonable notice of the speed limit being lowered to just 25mph. And for the 35mph speed limit section, drivers typically go up to 10mph above the speed limit without being considered speeding, which means that 45mph would not be a complete outlier for where the crash occurred.
In now way does this absolve the Prius driver of speeding. But it is important to note that the driver was not doing something completely out of the ordinary.
The 25mph speed limit sign is clearly out of view of the driver, being to the side and high up, especially since it is not lit at night. On top of that, it being obstructed makes the situation quite dangerous.
Analysis by Retrospect
Michael Woon, CEO of Retrospect, did an excellent analysis of the crash. Their conclusion is that the Prius could not have possibly been going to turn right onto Spruce St. because doing so would violate the laws of physics. The Cruise vehicle should have correctly determined that the Prius was not going to turn right and act accordingly, thereby avoiding the collision.
Show analysis…
Key part of the Retrospective analysis is that they conclude that the Cruise system must not have considered that the Prius was going to travel straight because if it had then it would have determined that stopping would have resulted in Maximum Risk.
Full analysis can be downloaded from Retrospect:
Analysis by Brad Templeton
Brad Templeton, a long-time authority on Autonomous Vehicles, analyzed the crash in Forbes. Templeton explained that either the Cruise should not have stopped where it did or it should not have attempted the left turn at that time.
Show analysis..
Description of the incident:
Reconstructions of the event suggest the Cruise car was hoping to make a left turn — the famous “unprotected left” that many teams have found a challenge. A Prius was approaching in a lane that requires a left [sic Editor: meant right] turn, except for buses and taxis, and the Cruise car presumed that car was indeed going to turn right and that it could make its turn first before the Prius got there.
Brad Templeton – Forbes
The mistakes made by the Cruise ADS are clear. Either the Cruise should not have stopped where it did or it should not have attempted the left turn at that time.
The Cruise Bolt could have prevented the accident either by not stopping and completing its turn, or by not attempting its turn in the first place. Most robocars are conservative and not quite up for avoiding accidents by speeding up, as that can lead to other problems.
Brad Templeton – Forbes
Cruise was not transparent and did not provide information to better understand what exactly happened:
Cruise declined to answer most questions about this event beyond what is in their filings.
Brad Templeton – Forbes
Cruise acknowledged that they need to handle situations, even if other vehicle is “behaving badly”.
They admit that it is their duty to do more to avoid a crash, even when other road users are behaving badly, and that is a good philosophy.
Brad Templeton – Forbes
Templeton reiterates that exactly what the Cruise misjudged on, which is its predictions of what other vehicles might do.
This is also a classic example of the prediction problem. While we talk about sensors all the time in the robocar world, sensing is not the goal, it’s a means towards the real goal which is prediction. It doesn’t matter where everything is now, what matters is where it will be in the near future. Cruise both misjudged where the Prius might go, and also what to do about it when the situation changed.
Brad Templeton – Forbes
And Templeton ends his article with how risk and erratic vehicles need to be handled.
The car should have been constantly saying, “what will I do if this guy doesn’t turn like the rules require” and make sure there is an action that can be taken — including speeding up in the turn or backing up. If there is no action that could work, and the risk has a high enough probability, the car would wait, but ideally there will be a possible action. It is necessary to tolerate some risk of accident when others act in an erratic way. Defensive driving is good but a totally defensive driver will block the roads with caution, which doesn’t get the problem solved.
Brad Templeton – Forbes
Analysis by Robotaxi.rodeo
There are two key issues with respect to this crash. The Cruise vehicle first made a dangerous and illegal left turn in front of approaching traffic. Though Cruise never publicly addressed this issue, it is actually the root cause of the crash and will be covered in depth here. The second issue is that after the Cruise vehicle committed to making a left turn, it made an incorrect decision and stopped directly in the path of the approaching Prius instead of simply continuing and avoiding the crash. These are both points that were also made in the analysis by Brad Templeton.
It was wrong to expect Prius to turn right
Both of these mistakes on the part of the Cruise vehicle were claimed in the reports to the DMV and NHTSA to be due to expecting the approaching Prius to turn right onto Spruce Street. Therefore the first thing to analyze is how that assumption was incorrect and did not take into account many factors.
Vehicle code allows vehicles parking to travel straight in transit lane
Section 601 of the San Francisco Vehicle Code specifically allows multiple vehicle types to use the transit lane even if they are not turning right. The vehicle code specifically excepts buses of all types (not just public transit buses) and taxis. But importantly, all vehicles are excepted if they are pulling into or out of a parking space or a driveway.
SEC. 601. DESIGNATED TRANSIT-ONLY AREAS.
(a) The locations listed in this Section 601 are designated as Transit-only Areas. Any vehicle operating within a Transit-only Area during times that the Transit-only Area is enforced is in violation of Transportation Code, Division I, Section 7.2.72 (Driving in Transit-only Area).
…
2 2 Other Transit-Only Areas. Except for buses, taxicabs, vehicles preparing to make a turn, vehicles entering into or exiting from a stopped position at the curb, and vehicles entering into or exiting from a driveway, no vehicle may operate in the following Transit-only Areas during the times indicated:
All Times
San Francisco Traffic Code Section 601
Geary Blvd. 14th Ave. Collins St.
Taxis allowed to go straight in transit lane, including Prius taxis
In San Francisco a Prius can be a taxi, and taxis are explicitly allowed in the transit lanes and do not need to turn right from them. The Cruise system surely cannot differentiate between taxis and regular vehicles, especially given the large number of Prius taxis in use. Even if the Cruise system can identify the vehicle type, it still cannot determine if the vehicle is allowed to drive straight through a transit lane.
Could have been a Fire Department vehicle
Even the San Francisco Fire Department uses Prius vehicles, which means that such vehicles might be allowed to travel straight in a transit lane.
Other city vehicles look like regular vehicles
San Francisco police cars look like ordinary vehicles and could not be differentiated by the Cruise ADS. And of course police vehicles are allowed in and do use transit lanes.
Regular vehicles do use the transit lane inappropriately
While most vehicles are not allowed in the transit lanes, it is unfortunately still common for vehicles to not always follow the laws. To verify this we simply looked at Google Map Satellite View snapshot of the transit lanes on Geary and O’Farrell. Quickly we were able to find two examples of where vehicles were improperly using the transit lanes. This clearly indicates that one cannot assume that a vehicle is going to turn right at the intersection just because it is in the transit lane. Perhaps most of the time the vehicle would turn right, but there is a significant percentage of times when the vehicle will go straight, even though not allowed to. Any automatic vehicle system must take lack of compliance with vehicle laws into account.
Turning right would have defied laws of physics
As described in the detailed analysis by Retrospective, if the Prius was speeding as claimed by Cruise then the vehicle could not have turned right onto narrow Spruce St. The Cruise system should have been able to determine that the Prius was not going to turn, and should have planned accordingly.
And note in the Google Maps satellite image below that Spruce Street is quite narrow, only 28′ from curb to curb, cars parked on both sides, and only 15′ for two directions of vehicle travel. This is inherently a very slow street, and a vehicle turning onto it from Geary Blvd would have to make the turn quite slowly, thereby not posing a risk for colliding with the Cruise.
Summary of vehicle turning right issue
Given the many possibilities, there was a significant chance that the approaching Prius vehicle was going to continue straight instead of turning right onto Spruce Street. All decisions made by the Cruise planner should have taken this possibility, even high probability, into account. But it did not. Also, all statements and filings with regulators should have made it clear that concluding that the Prius was going to turn right was not correct.
Cruise unsafe left turn
The law says that one must yield the right-of-way to approaching traffic until one can complete the turn safely.
21801. (a) The driver of a vehicle intending to turn to the left or to complete a U-turn upon a highway, or to turn left into public or private property, or an alley, shall yield the right-of-way to all vehicles approaching from the opposite direction which are close enough to constitute a hazard at any time during the turning movement, and shall continue to yield the right-of-way to the approaching vehicles until the left turn or U-turn can be made with reasonable safety.
California Vehicle Code 21801
Since the Prius vehicle was approaching from the opposite direction on Geary, it is clear that the Cruise vehicle dangerously and illegally did not yield the right-of-way and that the left turn was made in a very unsafe manner. Since there was a significant probably that the Prius was heading straight instead of turning, creating a plan based on the Prius turning was incorrect and dangerous. The analysis by Templeton reenforces this conclusion.
It is especially glaring that there was a very simple solution for easily and safely avoiding the approaching Prius: follow the vehicle code and just wait until the road was clear of approaching vehicles, and only then turn left. Given the 11pm time of the crash, there would have been a low volume of vehicles on Geary Blvd. Waiting for a safe time to turn would have only added a few seconds to the trip. And if there was a great deal of traffic the Cruise could have simply waited for the traffic signal on Geary Blvd to turn yellow, which would stop the approaching vehicles, and then turn left safely. That the safe option was not taken is extremely problematic and indicates that there was not a true “safety first” culture at Cruise.
Unsafe stopping in path of approaching Prius
Cruise never provided pictures, video, or other demonstrable evidence of exactly how the crash occurred to either the public, the news, or the regulators. Fortunately we can still piece together what happened.
In the Cruise statement to the NHTSA they claim that the ADS predicted that the Prius would hit the front of the Cruise, and therefore the Cruise initiated hard braking. But Cruise states that then the Prius “suddenly” moved out of the right-hand lane and proceeded straight through the intersection instead of turning right. If the Cruise statement is accurate then it means the Prius entered the intersection in either the right-hand lane, in the 2nd-lane, or somewhere in between. This is shown in the diagram below.
The location of the Cruise at impact must be a bit to the north of the Prius since the impact areas shown in the DMV report show that only the rear half of the right side of the Cruise was damaged.
Since the front of the stopped Cruise vehicle was a half a car length (half of 13.5′) north of the Prius, the location of the Cruise when it was hit by the Prius blocked at least half of the right-hand lane, as shown in the diagram below. Note that the travel lanes are 10′ wide, a Chevy Bolt Cruise vehicle is 13.5′ long, and the Prius is 6′ wide.
The conclusion is that when the Cruise stopped it ended up blocking at least half of the right-hand lane, making a collision inevitable if the Prius did not move out of that lane. The Prius likely tried to avoid the collision by moving towards the 2nd lane, but given the 13.5′ length of the Cruise a collision could still not be avoided. The Cruise had stopped in exactly the wrong place such that whether the Prius went straight or tried to go around the Cruise, a collision was still inevitable.
The Cruise vehicle should not have predicted that it needed to stop in order to avoid a collision because doing so actually made the collision inevitable.
The Cruise statement that a collision was predicted for unless the Cruise vehicle stopped is not credible. Only the rear half of the vehicle, approximately 6.5′, was impacted by the crash. If the Cruise would have continued to move forward it would have easily cleared out of the way of the Prius. It appears that the actual behavior of the Cruise was to do an emergency stop since the strong possibility of a collision was detected. This is exactly the dangerous behavior experienced in other situations, such as the crash at Mission St & 26th St shown in the video below.
And since the Cruise vehicle ended up blocking at least part of the right-hand lane, the issue of whether or not the Prius was turning right is not relevant. If the Prius was going to turn right then both vehicles would have been in the right-hand lane, resulting in a collision, regardless. Plus if the Prius was turning right then it would have slowed down considerably, which would have given the Cruise plenty of time to continue moving and get out of the way instead of stopping and causing the collision.
Untruths
Cruise really tried to limit information on this crash. And when they did provide information it was often false or at least very misleading.
Cruise:
- Did not publicize the crash or inform the public in any way. It was only discovered because Automotive News looked through DMV crash reports a month later.
- As indicated by the police report, Cruise did not provide details of the crash to the police when requested to do so. This caused incorrect interpretation of the crash.
- Did not answer reporter’s further questions.
- Claimed that the Prius was in a bus or right-turn-only lane, which it was not. That lane can also be used by taxis and for when pulling in or out of a curb parking space or driveways.
- Never acknowledged that a significant percentage of vehicles in a transit lane will continue straight through an intersection, even if not legal to do so.
- Mislead regulators by stating that the problem was their system predicting that the Prius was going to make a right turn. But the collision would have occurred even if the Prius had turned right. The whole issue of the Prius turning right appears to be intended to draw attention away from the Cruise vehicle stopping dangerously in the path of the Prius.
- Emphasized to reporters that the Cruise vehicle did not get a ticket by the police, falsely implying that it was not at fault. Cruise of course knows that in California moving violations can only be given to human drivers, not to autonomous vehicles. Not receiving a ticket in no way indicates that the robotaxi was not at fault.
- Emphasized their unverified claim that the Prius was speeding, yet the speed of the Prius was not actually a factor in the collision. The focus on the speed of the Prius was clearly an attempt to deflect blame onto the Prius human driver.
- Never acknowledged that the root problem was the Cruise vehicle prematurely attempting the left turn instead of waiting for a safe interval.
- Claimed to have fixed the problem, but they did not since a root problem was making the left turn improperly in front of an oncoming vehicle.
- Never acknowledged that stopping directly in the path of the Prius was the most dangerous possible maneuver.
- Blamed the other vehicle by stating the collision occurred due to “oncoming vehicle’s sudden change of direction.” But this is false. Yes, the Prius might have had a sudden change of direction, but the collision occurred because the Cruise vehicle stopped in front of the path of the Prius. The Prius then had to suddenly change direction to try as much as possible to avoid the collision.
Conclusions
The Cruise driving system failed twice, first by making an unsafe left turn into approaching traffic, and then by dangerously stopping in the path of the approaching vehicle.
The Cruise system expecting the Prius to turn right was incorrect and part of their problem, if that indeed was the cause of the actions taken by the Cruise vehicle. It is extremely problematic that the Cruise system did not take into account the many factors that indicated that the Prius had a significant probability of continuing straight instead of turning. Such a lack of understanding of real-world traffic situations is likely to cause problems in other complicated situations. Also, even if the Prius was going to turn right, the Cruise vehicle stopping would have still caused a collision.
It appears that after committing to making the unsafe left turn the Cruise vehicle stopped like a “deer in the headlights” in the path of the Prius, instead of simply continuing forward out of harm’s way. This behavior is not safe for the deer, and it is not safe for autonomous vehicles.
Cruise has not indicated that they addressed the multiple problems that actually caused the crash. Given that their vehicles continued in other situations to stop directly in the path of a rapidly approaching vehicle shows that they indeed have not addressed these core issues even though they did a “recall” of the vehicles to update their software.
It is also deeply disturbing that Cruise misrepresented or hid many of the details of the cause of the crash to the regulators and to the public. This behavior implies a culture of “move fast and break things” as opposed to a culture of safety.