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.
The Tesla Model Y L is arguably the most hyped trim of the all-electric crossover, other than the Performance configuration that comes with white-knuckle speed and sports car-level handling.
However, it is not all perfect. Tesla owners in China who took delivery of the Model Y L, denoted with an L to highlight its longer wheelbase, are experiencing what they are referring to as “collapsing” of the rear wheels, as suspension issues appear to be an issue with some of the builds.
🚨 Model Y L owners in China report rear suspension sag
• Six-seat long-wheelbase Y. Shanghai. On sale since August 2025
• Owners say the rear tire-to-arch gap shrinks after mileage or a full load. Some cases after about 9,000 km loaded. Others near 30,000 km
• Tesla service… pic.twitter.com/Lr6i5Tbi07— Joe Hansen (@joehansen) September 1, 2026
The gap between the wheel arch and tire has narrowed to the point that “not even a single finger” could fit, according to a report from Car News China. The failures are not tied to a specific mileage, as one owner said that after just 9,000 kilometers (5,600 miles), they noticed the suspension issue when their car was fully loaded.
Another one had the issue at 30,000 kilometers (18,640 miles) and noticed that the wheel gap shrank to two fingers, so not as drastic as the person who reported a similar issue at 9,000 km.
Tesla Model Y L is gaining momentum in China’s premium segment
Along with the visual recognition of the issue, others are saying the sagging is causing abnormal wear on the inside of the tires. Extra weight and instant torque already provide additional stress on the tires in electric vehicles during normal operation, so it is no surprise that this is another complaint.
There has been no recall issued by Tesla, and the company has not yet publicly acknowledged the issue.
Some are suggesting that owners use a “finger test” to self-diagnose whether there is an issue with the suspension. There should be four fingers between the tire and the wheel well; anything less than that starts to get dicey.
Tesla is starting to truly tease and hype its groundbreaking Cybercab event, which takes place tomorrow in Austin, Texas. It will be the first time members of the public will be able to ride in a Cybercab, a vehicle without any manual controls, on public roads.
Tesla has been dropping some hype on X over the past several days, but this morning, the excitement has truly started to build up for the event. Although Cybercab has been unveiled before, this is truly Tesla’s announcement that it is ready to start offering autonomous rides for public passengers in its new ride-hailing-geared vehicle for the first time.
The hype has started with a variety of different social media posts that are a true indication that Tesla is preparing for something big. Teasing so much of the potential of Cybercab, including its ability to truly revolutionize how people hail rides for local travel, is what the big idea for the event entails. The time that many Tesla owners, fans, and investors have been waiting for is potentially here:
— Tesla (@Tesla) September 2, 2026
The event has remained slim on details. Even invitees are still awaiting true details about what the event will entail, where they’ll go, and what is in store for the evening. This is pretty typical for an event run by Tesla; they keep things under wraps for the most part until the very last minute.
However, there is no secret about what the real intention of Tesla is for this event: it is going to be a huge reveal party for a vehicle that has no steering wheel and no pedals. It is a truly massive step for the company moving forward.
No steering wheel, no pedals
— Tesla Robotaxi (@robotaxi) September 2, 2026
Speculation persists as to whether this is going to be an event that simply announces that rides will begin with the Cybercab, or it will be something more substantial. Tesla has said in the past that they plan to sell the Cybercab to the general public in what could become a great way to earn passive income by adding it to a more global fleet of Robotaxi-geared vehicles.
Tomorrow, the show begins in Austin, and the Cybercab goes live at some capacity; we just don’t know exactly how quite yet.
News
SpaceX tells the FCC that Starship Flight 14 is going to orbit
SpaceX filed with the FCC for Starship Flight 14, its first true orbital launch attempt.
SpaceX has asked the Federal Communications Commission for permission to fly Starlink terminals during Starship’s fourteenth flight test, and the filing lays out a genuine trip to orbit, something the program has never attempted.
Every Starship flight so far, including Flight 13’s successful splashdown in the Indian Ocean on July 24, has flown a suborbital arc that ends with the ship reentering the atmosphere within the same hour it launches. The FCC paperwork describes a mission profile built around an actual orbital insertion instead.
The payload is the other half of the story. Flight 13 carried 20 production Starlink V3 satellites, but because that mission never reached orbit, the satellites reentered along with the ship rather than joining the constellation, something Teslarati covered in detail after SpaceX released footage shot from one of those satellites as it drifted away from Starship in space. Flight 14 is designed to close that gap. If the orbital insertion holds, the roughly 20 V3 satellites onboard would separate into an operational orbit and could eventually go into service, each one rated for about 1 terabit per second of downlink capacity by SpaceX’s own account.
SpaceX announces new Starbase for ‘thousands of Starship launches annually’
Elon Musk first flagged the orbital attempt during SpaceX’s August 4 earnings call, the company’s first as a public entity following its June IPO under the ticker SPCX. He also floated catching the ship with the Starbase tower on the same flight, an idea he walked back on August 20, saying the catch attempt would more likely come “in a few months,” as Teslarati reported at the time. Flight 14 will instead target a splashdown for the ship in the Indian Ocean, the same recovery method used since Flight 12.
Hardware has been catching up to the ambition. Booster 21 completed a full 33-engine static fire on August 28, and Ship 41 finished its own six-engine test the week before. An airspace briefing circulated to pilots on August 20 listed September 15 as the target date, later than the end of August window Musk mentioned on the earnings call, though SpaceX has not confirmed a launch date publicly and Starship schedules routinely slip while hardware and FAA paperwork line up.
The FCC filing itself does not guarantee a launch date. It covers communications authority, and not flight readiness, considering SpaceX still needs Ship 41 fully stacked and cleared by the FAA before Flight 14 can fly. But the filing is a real marker of intent and it puts a specific regulatory process behind what had so far only been Musk’s word on the earnings call.
Tesla Model Y L gets suspension complaints in over odd issue China
Tesla Cybercab event gains steam ahead of massive launch
