News
Cruise in hot seat amid Fire Department’s claims that robotaxis delayed responders in fatal incident
General Motors’ self-driving unit, Cruise, saw protests outside its San Francisco headquarters earlier this week. The protests come amidst the San Francisco Fire Department’s claims that some of the company’s autonomous robotaxis contributed to the tragic death of a pedestrian.
The incident, which happened on August 14, involved a pedestrian who was hit by a car in the South of Market neighborhood of San Francisco. The pedestrian’s injuries were so severe that there was heavy bleeding, and the person was no longer responding to verbal commands. It was evident that the injured pedestrian needed urgent medical care, so it was pertinent to have the person transported to a hospital as early as possible.
Public reports from the San Francisco Fire Department that were obtained by Forbes claimed that the behavior of Cruise robotaxis ended up impeding the workflow of emergency responders, so much so that critical medical care was delayed. One of the Fire Department’s reports about the incident reads as follows.
“On 8/14/2023, I was assigned to Medic 87 and responded to Incident FD23108420, at 7th Street and Harrison, for an auto vs. pedestrian. Harrison Street is 4 lanes of one-way traffic heading westbound. Upon arrival on scene, the victim was found in the (2) left lanes of Harrison Street, suffering from life-threatening injuries. SFPD and E01 had arrived prior to M87’s arrival. SFPD had a vehicle parked in the #1 lane of Harrison, and E01 had positioned its apparatus across the left 2 lanes of Harrison to shield the patient from oncoming traffic. The right 2 lanes of Harrison were blocked by (2) autonomous Cruise vehicles that had stopped and were not moving, blocking ingress and egress to the incident scene.
“The patient was suffering from life-threatening injuries, with a GCS 3, agonal respirations, and absent peripheral pulses. SFPD had applied a tourniquet to the left lower extremity to stop life-threatening bleeding from injuries sustained after being struck by a vehicle. Ventilations were assisted with a BVM, and the patient was packaged for rapid transport to a trauma center.
“While loading the patient to the ambulance, the (2) Cruise vehicles were still stopped in the right 2 lanes of Harrison, prohibiting rapid egress from the scene. SFPD had attempted manual takeover of the autonomous vehicles, but were unsuccessful. This contributed to a delay in transport with a critical trauma patient.
“SFFD members had to locate an SFPD officer and request him to move his vehicle to allow successful egress from the scene, but doing so further delayed patient care. These delays caused by (2) autonomous vehicles blocking a normal egress route from the scene contributed to a poor patient outcome, delaying the definitive care required in severe trauma cases. The patient was pronounced deceased at SFGH approximately 20-30 minutes after arrival due to severe blunt-force trauma.”
Cruise has spoken out against the Fire Department’s account of the event. In a comment to The San Francisco Standard, a Cruise spokesperson noted that “we did not impede the vehicle from getting to the hospital” and “what the fire department said is not accurate.”
“The first vehicle promptly clears the area once the light turns green and the other stops in the lane to yield to first responders who are directing traffic. Throughout the entire duration the AV is stopped, traffic remains unblocked and flowing to the right of the AV. The ambulance behind the AV had a clear path to pass the AV as other vehicles, including the ambulance, proceeded to do so. As soon as the victim was loaded into the ambulance, the ambulance left the scene immediately and was never impeded from doing so by the AV,” Cruise noted in a statement.
Cruise has reportedly provided a video to back up its claims. The video reportedly showed that while one Cruise robotaxi was indeed stopped at an intersection, there was a free lane to its right where traffic was moving. The video, which was reviewed by Forbes, did show numerous vehicles, including a small ambulance, moving through the free lane. However, the publication noted that it was not clear from the footage if the larger SFFD ambulance, which was likely transporting the severely injured pedestrian, could have navigated the area as easily.
Below are incident reports from the San Francisco Fire Department. The case in question is described in Page 68 and 69 of the document.
Cruise San Francisco Reports by Simon Alvarez on Scribd
Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads-up.
Tesla revealed a major new Cybercab detail in a guide it released for First Responders, showing new territory in its beliefs and intentions for the ride-hailing-focused vehicle that entered production in April.
The First Responders Guide is released to give fire departments, paramedics, and other emergency personnel the proper guidance on what to do in the event of an accident, entrapment, or other situation that would require immediate attention.
On one of the pages of the First Responders Guide, Tesla revealed a stark detail about the Cybercab, which could help personnel enter the vehicle more easily in case of an emergency.
Tesla Cybercab has one important piece that AI4 cars might need for FSD
It shows Tesla has no intention of releasing any Cybercab units that were initially proposed for ride-hailing services for the general public with any manual controls, meaning a steering wheel or pedals:
“A Cybercab equipped with steering wheel, brake pedal, and an acceleration pedal is typically an engineering or test vehicle, and operates at SAE Level 2 autonomy. Cybercab is not typically equipped with a steering wheel or acceleration and brake pedals.”
New official Cybercab documentation from Tesla:
“A Cybercab equipped with steering wheel, brake pedal, and an acceleration pedal is typically an engineering or test vehicle, and operates at SAE Level 2 autonomy. Cybercab is not typically equipped with a steering wheel or… https://t.co/P6ut1mZyzr pic.twitter.com/yq6skl9s2J
— Sawyer Merritt (@SawyerMerritt) June 27, 2026
This is a major development for those who continue to believe Tesla planned to release the Cybercab with any sort of manual controls so that passengers could take over if needed. However, when Tesla started manufacturing production versions of the Cybercab in Giga Texas earlier this year, they were spotted without a steering wheel or pedals.
It essentially confirms the company has no intentions of bringing manual controls to the car’s production versions. Some have argued that the likelihood of Tesla having something
There still are some Cybercab units out there with a steering wheel and pedals, and as Tesla said, these cars are engineering or test vehicles, which have Safety Monitors on board to help the car out of a precarious situation or emergency.
Tesla released the Full Self-Driving v14 ‘Lite’ suite to owners of Hardware 3 or AI3 vehicles today, adding several new features to the vehicles that were once believed to be capable of unsupervised self-driving.
Now, Tesla has released this modified suite to older Tesla vehicles, adding plenty of new features and capabilities.
Here are the full release notes for the suite:
- Distilled the intelligence from HW4 V14 into HW3. This allows HW3 to directly learn how to handle scenarios using HW4 V14 as a guide. This process unlocks the improvements that have been made to HW4 including Reinforcement Learning (RL) and offline models for HW3.
- Improved both proactive and reactive responsiveness across a wide variety of categories including navigation handling, merges and forks, pedestrian interactions, traffic lights, and vehicle cut-in scenarios.
- Improved general comfort in nominal scenarios through fewer false slowdowns, smoother steering and more consistent lane centering.
- Introduced parking, unparking, and reversing capabilities.
- Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, or at the Curbside.
- Speed Profiles are now available at all times, to further customize driving style preference.
These improvements, according to Tesla’s Head of AI, Ashok Elluswamy, help distill the driving behavior from AI4’s v14 series into both the camera and compute configurations of AI3.
Tesla Full Self-Driving v14 ‘Lite’ for older cars finally gets released
He added:
“It includes destination options and speed profiles on city roads, but more importantly significantly improved safety. We hope you’ll enjoy it, once the build ships wide.”
FSD v14 Lite is now rolling out to AI3 early-access customers. Based on the feedback, will rollout to more customers over the next few weeks.
This build distills the driving behavior from AI4’s v14 series into both the camera and compute config of AI3. It includes destination…
— Ashok Elluswamy (@aelluswamy) June 29, 2026
Tesla will continue to roll out the v14 Lite suite more widely in the coming weeks, the company said.
Tesla has finally released its Full Self-Driving v14 ‘Lite’ suite for older cars that equip the Hardware 3 or AI 3 chip, which have not been able to handle the newest versions of the company’s driver assistance software.
Tesla officially started releasing the v14 Lite suite to owners in the Early Access Program last night. The company’s Head of AI, Ashok Elluswamy, said that the rollout will continue over the next few weeks. The build distills the driving behavior from AI4’s v14 series into both the camera and compute configurations of an AI3 car.
🚨 Tesla is releasing v14 Lite for AI3 owners who are in early-access
This will give AI3 cars the ability to experience new FSD features like parking preferences. https://t.co/pp6Q5FOKoz pic.twitter.com/tqexMB8SVy
— TESLARATI (@Teslarati) June 29, 2026
It also includes a variety of new features that were available to AI4 cars running v14, including:
- Start Self-Driving from Park
- Arrival and Parking Options
- Speed Profiles
The release is highly anticipated because those owners with AI3 vehicles were early adopters into the FSD platform and were promised that their cars would be capable of achieving Full Self-Driving.
However, Tesla CEO Elon Musk admitted during the company’s recent Q1 Earnings Call that these vehicles would not be capable of achieving unsupervised Full Self-Driving, which is what Tesla had originally said.
Owners were not pleased with this answer, or the idea that their commitment to buying the suite outright for thousands of dollars would not yield the ability to drive without operating the car. Tesla gave some solutions for this, including a discount on a new car, or an upgrade to an AI4 or AI5 self-driving computer and new, upgraded cameras.
Tesla owners do not seem pleased with these options, as they require giving the company more money.
Nevertheless, it is important to note that Tesla came through for owners here by releasing v14 Lite before the end of Q2, something it had promised owners during the previous Earnings Call. Tesla has had trouble keeping up with timelines, but this is a big achievement for the team.
Tesla reveals huge Cybercab detail in new guide for First Responders
Tesla Full Self-Driving v14 ‘Lite’ Release Notes: new capabilities and features
