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.
Elon Musk
SpaceX turned a heralding moment for Starship into its greatest moment
Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.
SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.
The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.
Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.
Splashdown confirmed. Congratulations to the entire SpaceX team on the first orbital flight of Starship! pic.twitter.com/urjmiwnvNl
— SpaceX (@SpaceX) September 28, 2026
That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.
The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.
SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.
Starship’s 14th flight is set to launch on Monday, Sept 28. The 75-minute launch window opens at 7:15 a.m. CT. Live coverage of the mission starts ~35 minutes before launch → https://t.co/uQKQvgaTmJ
— SpaceX (@SpaceX) September 27, 2026
Tesla quietly doubled the size of its Cybercab fleet within the Robotaxi program in Austin, Texas, over the weekend to well over 100 units.
The move not only establishes more of the steering-wheel-less and pedal-less vehicles within the ride-sharing fleet Tesla has been operating for a year, but it also solidifies a more robust Robotaxi fleet as a whole.
Riders started receiving notifications from the Robotaxi app that stated: “Cybercab fleet has doubled: more rides available.”
I got this notification on the robotaxi app. They are saying the Cybercab fleet has doubled. Glad that they are advertising this pic.twitter.com/FFrnw4FRCF
— Abhimanyu Yadav (@WorldlyReviewer) September 26, 2026
Tesla first launched rides in the Cybercab in early September, although the Robotaxi fleet has been active for over a year, as rides began last Summer. Cybercab is truly Tesla’s most crucial vehicle release yet, as it is the first car any company has built that is geared toward full-fledged and end-to-end autonomy, never needing human intervention for anything.
Only available in Austin at the current time, Cybercab has two seats and has been spotted testing around various U.S. states and regions; Tesla plans to deploy the Cybercab in various U.S. cities in the coming months as a best-case scenario.
Tesla Cybercab gets initial tie-in to localized, in-house cathode plant
The availability of the Cybercab has doubled from just 58 units last Monday to 125 the following Friday. Marking a substantial increase in Cybercab availability, the additional ride-sharing units are more than welcome, as wait times for Cybercabs, especially, were quite high.
The dramatic increase is a sign that demand for Robotaxi is growing and Tesla is feeling more confident that its driverless ride-hailing suite, especially its Full Self-Driving software, is able to handle any traffic situation without explicit direction or supervision from a human being.
Tesla is advancing a fully automated pipeline for the 4680 battery cells used in its all-electric Semi, spanning production from Giga Texas through shipment and direct consumption on the line at the new dedicated Semi Factory in Sparks, Nevada.
The approach was outlined by Tesla at its September 24 Semi Handover event, which launched high-volume production at its new 1.8-million-square-foot plant in Nevada, which sits adjacent to Gigafactory Nevada and is designed for an annual production rate of 50,000 trucks per year.
After years of pilot builds and what was a four-year-long redesign of the truck, Tesla moved the Semi from 2170 batteries to its in-house 4680 cells, which are made in Austin. The change cuts battery mass and total energy while holding range, a key step in making volume production a realistic possibility.
Cells will leave Giga Texas in trailers, and at the Nevada Semi plant, Tesla intends for a dedicated line to unload those trailers automatically, station the cells, and feed them straight into pack and vehicle assembly.
🚨 Tesla plans to use a completely automated unloading process for cells coming from Giga Texas arriving at the Semi factory in Nevada
A line will “consume” cells from the trailer
The goal is to have zero human touch point throughout the entire process. Insane! pic.twitter.com/wdBFM8LC3F
— TESLARATI (@Teslarati) September 25, 2026
Both Lars Moravy, Tesla’s VP of Vehicle Engineering, and Dan Priestley, the Head of Tesla’s Semi program, described the goal as a “zero human touch point” from the moment the trailer arrives in Texas until a finished Semi drives off the production line in Nevada.
The unloading system that Moravy and Priestley described is just one piece of a much broader automation push. The plant uses what Tesla calls the highest-capacity electric monorail conveyance in vehicle manufacturing, carrying frames-in-white simultaneously. Powder-coating replaces conventional paint, and many processes that would normally require operators have been designed out.
Tesla has repeatedly said that “the best part is no part,” and the cell-handling plan extends that philosophy from the cell factory floor in Texas all the way to final assembly in Nevada.
If executed as described, the closed-loop flow would reduce labor, handling damage, and inventory buffers while tightening quality control on a component that represents a large share of the truck’s cost and weight. It also shortens the physical and organizational distance between two factories separated by more than 1,200 miles. The Semi itself now shares a bar-wound stator and other components with the Cybertruck, further linking Tesla’s passenger and commercial production systems.
High-volume output is expected to ramp gradually after the first trucks left the new line in April 2026. Early customers include PepsiCo, DHL, and U.S. Foods. Whether the automated trailer-to-line process reaches the promised zero-touch standard will be visible in the coming months as production scales. For Tesla, the Semi factory is another test of how far it can push “the machine that builds the machine” across sites.
SpaceX turned a heralding moment for Starship into its greatest moment
Tesla Cybercab fleet doubles to well over 100 units
