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.
In Pennsylvania, we got between 10 and 12 inches of snow over the weekend as a nasty Winter storm ripped through a large portion of the country, bringing snow to some areas and nasty ice storms to others.
I have had a Model Y Performance for the week courtesy of Tesla, which got the car to me last Monday. Today was my last full day with it before I take it back to my local showroom, and with all the accumulation on it, I decided to run a cool little experiment: How long would it take for Tesla’s Defrost feature to melt 8 inches of snow?
Tesla’s Defrost feature is one of the best and most underrated that the car has in its arsenal. While every car out there has a defrost setting, Tesla’s can be activated through the Smartphone App and is one of the better-performing systems in my opinion.
It has come in handy a lot through the Fall and Winter, helping clear up my windshield more efficiently while also clearing up more of the front glass than other cars I’ve owned.
The test was simple: don’t touch any of the ice or snow with my ice scraper, and let the car do all the work, no matter how long it took. Of course, it would be quicker to just clear the ice off manually, but I really wanted to see how long it would take.
Tesla Model Y heat pump takes on Model S resistive heating in defrosting showdown
Observations
I started this test at around 10:30 a.m. It was still pretty cloudy and cold out, and I knew the latter portion of the test would get some help from the Sun as it was expected to come out around noon, maybe a little bit after.
I cranked it up and set my iPhone up on a tripod, and activated the Time Lapse feature in the Camera settings.
The rest of the test was sitting and waiting.
It didn’t take long to see some difference. In fact, by the 20-minute mark, there was some notable melting of snow and ice along the sides of the windshield near the A Pillar.
However, this test was not one that was “efficient” in any manner; it took about three hours and 40 minutes to get the snow to a point where I would feel comfortable driving out in public. In no way would I do this normally; I simply wanted to see how it would do with a massive accumulation of snow.
It did well, but in the future, I’ll stick to clearing it off manually and using the Defrost setting for clearing up some ice before the gym in the morning.
Check out the video of the test below:
❄️ How long will it take for the Tesla Model Y Performance to defrost and melt ONE FOOT of snow after a blizzard?
Let’s find out: pic.twitter.com/Zmfeveap1x
— TESLARATI (@Teslarati) January 26, 2026
Tesla Robotaxi ride-hailing without a Safety Monitor is proving to be a difficult task, according to some riders who made the journey to Austin to attempt to ride in one of its vehicles that has zero supervision.
Last week, Tesla officially removed Safety Monitors from some — not all — of its Robotaxi vehicles in Austin, Texas, answering skeptics who said the vehicles still needed supervision to operate safely and efficiently.
BREAKING: Tesla launches public Robotaxi rides in Austin with no Safety Monitor
Tesla aimed to remove Safety Monitors before the end of 2025, and it did, but only to company employees. It made the move last week to open the rides to the public, just a couple of weeks late to its original goal, but the accomplishment was impressive, nonetheless.
However, the small number of Robotaxis that are operating without Safety Monitors has proven difficult to hail for a ride. David Moss, who has gained notoriety recently as the person who has traveled over 10,000 miles in his Tesla on Full Self-Driving v14 without any interventions, made it to Austin last week.
He has tried to get a ride in a Safety Monitor-less Robotaxi for the better part of four days, and after 38 attempts, he still has yet to grab one:
Wow just wow!
It’s 8:30PM, 29° out ice storm hailing & Tesla Robotaxi service has turned back on!
Waymo is offline & vast majority of humans are home in the storm
Ride 38 was still supervised but by far most impressive yet pic.twitter.com/1aUnJkcYm8
— David Moss (@DavidMoss) January 25, 2026
Tesla said last week that it was rolling out a controlled test of the Safety Monitor-less Robotaxis. Ashok Elluswamy, who heads the AI program at Tesla, confirmed that the company was “starting with a few unsupervised vehicles mixed in with the broader Robotaxi fleet with Safety Monitors,” and that “the ratio will increase over time.”
This is a good strategy that prioritizes safety and keeps the company’s controlled rollout at the forefront of the Robotaxi rollout.
However, it will be interesting to see how quickly the company can scale these completely monitor-less rides. It has proven to be extremely difficult to get one, but that is understandable considering only a handful of the cars in the entire Austin fleet are operating with no supervision within the vehicle.
Tesla has given its biggest hint that Full Self-Driving in Europe is imminent, as a new feature seems to show that the company is preparing for frequent border crossings.
Tesla owner and influencer BLKMDL3, also known as Zack, recently took his Tesla to the border of California and Mexico at Tijuana, and at the international crossing, Full Self-Driving showed an interesting message: “Upcoming country border — FSD (Supervised) will become unavailable.”
FSD now shows a new message when approaching an international border crossing.
Stayed engaged the whole way as we crossed the border and worked great in Mexico! pic.twitter.com/bDzyLnyq0g
— Zack (@BLKMDL3) January 26, 2026
Due to regulatory approvals, once a Tesla operating on Full Self-Driving enters a new country, it is required to comply with the laws and regulations that are applicable to that territory. Even if legal, it seems Tesla will shut off FSD temporarily, confirming it is in a location where operation is approved.
This is something that will be extremely important in Europe, as crossing borders there is like crossing states in the U.S.; it’s pretty frequent compared to life in America, Canada, and Mexico.
Tesla has been working to get FSD approved in Europe for several years, and it has been getting close to being able to offer it to owners on the continent. However, it is still working through a lot of the red tape that is necessary for European regulators to approve use of the system on their continent.
This feature seems to be one that would be extremely useful in Europe, considering the fact that crossing borders into other countries is much more frequent than here in the U.S., and would cater to an area where approvals would differ.
Tesla has been testing FSD in Spain, France, England, and other European countries, and plans to continue expanding this effort. European owners have been fighting for a very long time to utilize the functionality, but the red tape has been the biggest bottleneck in the process.
Tesla Europe builds momentum with expanding FSD demos and regional launches
Tesla operates Full Self-Driving in the United States, China, Canada, Mexico, Puerto Rico, Australia, New Zealand, and South Korea.
Tesla winter weather test: How long does it take to melt 8 inches of snow?
Tesla Robotaxi ride-hailing without a Safety Monitor proves to be difficult
