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.
News
Anti-Tesla union leader ditches X, urges use of Threads instead
Tesla Sweden and IF Metall have been engaged in a bitter dispute for over two years now.
Marie Nilsson, chair of Sweden’s IF Metall union and a prominent critic of Tesla, has left X and is urging audiences to follow the union on Meta’s Threads instead.
Tesla Sweden and IF Metall have been engaged in a bitter dispute for over two years now.
Anti-Tesla union leader exits X
In a comment to Dagens Arbete (DA), Nilsson noted that her exit from X is not formally tied to IF Metall’s long-running labor dispute with Tesla Sweden. Still, she stated that her departure is affected by changes to the platform under Elon Musk’s leadership.
“We have stayed because many journalists pick up news there. But as more and more people have left X, we have felt that the standard has now been reached on that platform,” she said.
Jesper Pettersson, press officer at IF Metall, highlighted that the union’s departure from X is only indirectly linked to Tesla Sweden and Elon Musk. “Indirectly it does, since there is a lot of evidence that his ownership has caused the change in the platform to be so significant.
“We have nevertheless assessed that the platform had value for reaching journalists, politicians and other opinion leaders. But it is a microscopic proportion of the public and our members who are there, and now that value has decreased,” Petterson added.
IF Metall sees Threads as an X alternative
After leaving X, IF Metall has begun using Threads, Meta’s alternative to the social media platform. The union described the move as experimental, noting that it is still evaluating how effective the platform will be for outreach and visibility.
Pettersson acknowledged that Meta also does not operate under Sweden’s collective bargaining model, but said the union sees little alternative if it wants to remain visible online.
“In a perfect world, all large international companies would be supporters of the Swedish model when they come here. But unfortunately, the reality is not like that. If we are to be visible at all in this social media world, we have to play by the rules of the game. The alternative would be to become completely invisible, and that would not benefit our members,” he said.
Despite many recent rumors and various reports, Elon Musk confirmed today that SpaceX is not developing a phone based on Starlink, not once, but twice.
Today’s report from Reuters cited people familiar with the matter and stated internal discussions have seen SpaceX executives mulling the idea of building a mobile device that would connect directly to the Starlink satellite constellation.
Musk did state in late January that SpaceX developing a phone was “not out of the question at some point.” However, He also said it would have to be a major difference from current phones, and would be optimized “purely for running max performance/watt neural nets.”
Not out of the question at some point. It would be a very different device than current phones. Optimized purely for running max performance/watt neural nets.
— Elon Musk (@elonmusk) January 30, 2026
While Musk said it was not out of the question “at some point,” that does not mean it is currently a project SpaceX is working on. The CEO reaffirmed this point twice on X this afternoon.
Musk said, “Reuters lies relentlessly,” in one post. In the next, he explicitly stated, “We are not developing a phone.”
Reuters lies relentlessly
— Elon Musk (@elonmusk) February 5, 2026
We are not developing a phone
— Elon Musk (@elonmusk) February 5, 2026
Musk has basically always maintained that SpaceX has too many things going on, denying that a phone would be in the realm of upcoming projects. There are too many things in the works for Musk’s space exploration company, most notably the recent merger with xAI.
SpaceX officially acquires xAI, merging rockets with AI expertise
A Starlink phone would be an excellent idea, especially considering that SpaceX operates 9,500 satellites, serving over 9 million users worldwide. 650 of those satellites are dedicated to the company’s direct-to-device initiative, which provides cellular coverage on a global scale.
Nevertheless, there is the potential that the Starlink phone eventually become a project SpaceX works on. However, it is not currently in the scope of what the company needs to develop, so things are more focused on that as of right now.
Tesla has added a notable improvement to its Dashcam feature after complaints from owners have pushed the company to make a drastic change.
Perhaps one of the biggest frustrations that Tesla owners have communicated regarding the Dashcam feature is the lack of ability to retain any more than 60 minutes of driving footage before it is overwritten.
It does not matter what size USB jump drive is plugged into the vehicle. 60 minutes is all it will hold until new footage takes over the old. This can cause some issues, especially if you were saving an impressive clip of Full Self-Driving or an incident on the road, which could be lost if new footage was recorded.
This has now been changed, as Tesla has shown in the Release Notes for an upcoming Software Update in China. It will likely expand to the U.S. market in the coming weeks, and was first noticed by NotaTeslaApp.
The release notes state:
“Dashcam Dynamic Recording Duration – The dashcam dynamically adjusts the recording duration based on the available storage capacity of the connected USB drive. For example, with a 128 GB USB drive, the maximum recording duration is approximately 3 hours; with a 1 TB or larger USB drive, it can reach up to 24 hours. This ensures that as much video as possible is retained for review before it gets overwritten.”
Tesla Adds Dynamic Recording
Instead of having a 60-minute cap, the new system will now go off the memory in the USB drive. This means with:
- 128 GB Jump Drive – Up to Three Hours of Rolling Footage
- 1TB Jump Drive – Up to 24 Hours of Rolling Footage
This is dependent on the amount of storage available on the jump drive, meaning that if there are other things saved on it, it will take away from the amount of footage that can be retained.
While the feature is just now making its way to employees in China, it will likely be at least several weeks before it makes its way to the U.S., but owners should definitely expect it in the coming months.
It will be a welcome feature, especially as there will now be more customization to the number of clips and their duration that can be stored.
Anti-Tesla union leader ditches X, urges use of Threads instead
Elon Musk confirms SpaceX is not developing a phone
