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.
Cybertruck
Tesla Cybertruck gets long-awaited safety feature
Tesla has announced the rollout of its innovative anti-dooring protection feature to the Cybertruck via the 2026.8 software update.
Tesla is rolling out a new and long-awaited feature to the Cybertruck all-electric pickup, and it is a safety addition geared toward pedestrian and cyclist safety, as well as accidents with other vehicles.
Tesla has announced the rollout of its innovative anti-dooring protection feature to the Cybertruck via the 2026.8 software update.
This safety enhancement uses the vehicle’s existing cameras to detect approaching cyclists, pedestrians, or vehicles in the blind spot while parked. Upon attempting to open a door, if a hazard is detected, the system activates: the blind spot indicator light flashes, an audible chime sounds, and the door will not open on the initial button press.
Drivers must wait briefly and press the button again to override, providing crucial seconds to avoid an accident.
Anti-dooring protection now rolling out to @Cybertruck
This feature comes standard on every new Model 3, Model Y & Cybertruck – using cameras to delay door opening if a cyclist, pedestrian or other vehicle is detected approaching in your blind spot
— Tesla North America (@tesla_na) March 17, 2026
The feature, also known as Blind Spot Warning While Parked, comes standard on every new Model 3 and Model Y, and is now extending to the Cybertruck. Leveraging Tesla’s vision-based system without requiring new hardware, it represents a cost-effective software solution that builds on community suggestions dating back to 2018.
This technology addresses the persistent danger of “dooring,” where a driver opens a car door into the path of a passing cyclist or pedestrian.
Tesla implemented this little-known feature to make its cars even safer
Dooring incidents are alarmingly common in urban environments.
According to Chicago data, in 2011 alone, there were 344 reported dooring crashes, accounting for approximately 20 percent of all bicycle crashes in the city, nearly one incident per day.
While numbers have fluctuated (dropping to 11 percent in 2014 before rising again), dooring consistently represents 10-20 percent of bike-related crashes in major cities.
A national analysis of emergency department data estimates over 17,000 dooring-related injuries treated in the U.S. over a decade, with many involving fractures, contusions, and head trauma, particularly affecting upper extremities.
By automatically intervening, Tesla’s system not only protects vulnerable road users but also safeguards its owners from potential liability and enhances overall road safety.
As cities promote cycling for sustainable transport, features like this demonstrate how advanced driver assistance and camera systems can evolve beyond highway driving to everyday urban scenarios.
Enthusiastic responses on social media highlight appreciation for the proactive safety measure, with some calling for broader rollout to older models where hardware permits. Tesla continues to push the boundaries of vehicle safety through over-the-air updates, making its fleet smarter and safer over time.
Elon Musk
Tesla Roadster is ‘sorcery and magic’ and might be worth the wait, Uber founder says
Perhaps the wait will be worth it, especially according to Uber founder Travis Kalanick, who recently teased the Roadster’s potential capabilities based on what he has heard from internal Tesla sources.
Tesla is planning to unveil the Roadster in late April after years of waiting. But the wait might be worth it, according to Travis Kalanick, the founder of Uber, who recently shed some light on his expectations for the all-electric supercar.
We all know the Roadster is supposed to have some serious capability. CEO Elon Musk has said on numerous occasions that the Roadster will be unlike anything else ever produced. It might go from 0-60 MPH in about a second, it might hover, it might have SpaceX cold gas thrusters.
However, the constant delays in the Roadster program and its unveiling event continue to send Tesla fans into confusion because they’re just not sure when, or if, they’ll ever see the finished product.
Perhaps the wait will be worth it, especially according to Uber founder Travis Kalanick, who recently teased the Roadster’s potential capabilities based on what he has heard from internal Tesla sources.
Kalanick said on X:
When I’ve run into people who are in the know, I inquire, they tell me nothing, but their eyebrows raise and their eyes widen in a way that can only mean something of sorcery and magic is coming…
— travis kalanick (@travisk) March 17, 2026
Musk has said this vehicle is not going to be geared for safety, and that, “If safety is your number one goal, do not buy the Roadster.”
There has been so much hype regarding the Roadster that it is hard to believe the company could not come through on some kind of crazy features for the vehicle.
However, the latest delay that Tesla put on the unveiling event is definitely eye-opening, especially considering it is the latest in a series of pushbacks the company has put on the vehicle for the past several years.
Tesla has made several jumps in the Roadster project over the past few months, as it has ramped up hiring for the vehicle and also applied for a patent for a new seat design.
The car has been a back-burner project for Tesla, as it has been focusing primarily on autonomy and the rollout of Robotaxi and Cybercab. Additionally, its other vehicle projects, like the Model 3 and Model Y refreshes, took precedence.
Tesla still plans to unveil the Roadster next month, so we can hope the company can stick to this timeframe.
Cybertruck
Elon Musk clarifies viral Tesla Cybertruck accident with driver logs
Musk has come out to say that the driver logs have already shown that the driver “disengaged Autopilot four seconds before crashing,” in a post on X.
Tesla CEO Elon Musk has clarified some details regarding the viral Tesla Cybertruck accident with company driver logs, which show various metrics at the time of an incident.
The logs have been used in the past to pull responsibility off of Tesla when the automaker’s Full Self-Driving (Supervised) or Autopilot platforms are blamed for a collision or accident. It appears this will be no different.
On Tuesday, a video of a Cybertruck crashing into an overpass barrier in August 2025 was shared by Fox Business in a story that reported a woman was suing the automaker for $1 million in a liability and negligence case.
In the suit, Justine Saint Amour said that, “Something terrifying happened, without warning, the vehicle attempted to drive straight off an overpass.” Her attorney, Bob Hilliard, said Amour “tried to take control, but crashed into the barrier and was seriously injured (mostly her shoulder, neck, and back).”
The Tesla Model Y is leading China’s electric SUV segment by a wide margin
Tesla vehicle crashes are widely popular to report by mainstream media outlets because of the sensationalism of the event. Oftentimes, these outlets will include Tesla in the headline, especially because it will pique the interest of the masses, as most who read the story are waiting to see the claim that Autopilot or Full Self-Driving was the culprit of the accident.
However, Tesla has access to the logs of every vehicle in its fleet, which will show the various metrics, like whether either FSD or Autopilot was active, if the accelerator was pressed, the speed, and other important factors.
Musk has come out to say that the driver logs have already shown that the driver “disengaged Autopilot four seconds before crashing,” in a post on X.
Logs show driver disengaged Autopilot four seconds before crashing
— Elon Musk (@elonmusk) March 18, 2026
If the logs do show this, which Tesla will likely have to prove in court, the real question would be why did the Amour disengage the suite?
Tesla’s Full Self-Driving suite is still not fully autonomous, meaning the driver cannot pull attention away from the road and must be ready to take over the vehicle at all times.
It will be interesting to see how this particular case pans out, especially considering the clip that was released by the law firm starts at about four seconds before the collision. Tesla logs have dispelled media reports in the past that have accused the company’s suite of being responsible for an accident, so there will be some major attention on what is proven in this particular case.