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
Tesla Robotaxi app update now tells riders if Cybercab is the better choice
Tesla’s Robotaxi app now shows ETAs, wait times and availability for Cybercab and Model Y.
Tesla has rolled out a new vehicle selection screen in its Robotaxi app, and it puts the numbers riders care about most in front of them before they book.
Version 26.11.0 of the app shows the estimated arrival time, the expected wait and current availability for each vehicle option on a single screen, according to a video shared by @gheeunit on X on November 7. Riders deciding between a Cybercab and a Model Y Robotaxi can now compare those figures side by side instead of picking a car first and learning how long it will take afterward.
Tesla first gave riders that choice on September 3, the day paid Cybercab rides began in Austin. The original version of the screen listed the Cybercab, which seats two, next to the Model Y, which seats four. A later build, 26.8.2, added a seating capacity indicator so groups knew which car would fit them. What it did not show was whether choosing the Cybercab meant standing on the curb a few extra minutes.
Newest version of @robotaxi app has a new vehicle selector UI for choosing between Cybercab and Model Y and shows you the fare for both simultaneously! https://t.co/7qoDQ0vACX — mantequilla 🧈 (@gheeunit) November 7, 2026
That question matters more now than it did two months ago. Tesla had 45 Cybercabs on the Texas DMV roster when rides started. By late October the state listed 573, alongside 631 Model Ys, and community trackers logged a record 1,576 Cybercab sightings across Austin on Halloween alone. With two large fleets sharing one service area, the closest car and the quickest pickup are not always the same vehicle.
Inline availability also changes what happens when demand spikes. If no Cybercab is free nearby, the rider sees that on the selection screen rather than after trying to book one.
For now the comparison is mostly an Austin feature. Riders in Dallas, Houston, Fort Worth and the Florida markets are still matched with Model Y vehicles, though Tesla said on its third quarter earnings call that Cybercab rides would launch in Dallas this month.
The update follows a steady run of smaller changes to the rider experience. Late last month Tesla brought a quiet mode that blacks out the cabin screen to Model Y Robotaxis after first testing it in the Cybercab, and it has stretched Austin service to run from 6 a.m. to 2 a.m.
The Cybercab side of that selection screen is about to get much busier. Elon Musk said this week that Tesla will wind down Cybertruck production at Gigafactory Texas around the middle of 2027 to make room for more Cybercab output, and Tesla has said it is aiming to get Cybercabs to customers by the end of this year.
Tesla has not published official release notes for version 26.11.0.
Tesla is ending Cybertruck production sometime in mid-2027, according to CEO Elon Musk.
Musk made the announcement on X last night, which came as a shock to many. He said that the Cybertruck will end production “to make room for increased Cybercab production” at Gigafactory Texas.
It is a huge blow to the fans of Tesla who have come to love the Cybertruck and identify with it as a symbol of their fandom. It has been the best-selling electric pickup, but it has had an underwhelming sales performance in terms of what was expected. This is mostly due to Tesla not meeting the prices it planned to offer the Cybertruck, as its unveiling and actual release were four years apart.
Tesla will be winding down production of the Cybertruck at Gigafactory Texas around the middle of next year to make room for increased Cybercab production
— Elon Musk (@elonmusk) November 6, 2026
Overall, the responses were mixed. Some fans understood the move toward Cybercab production, especially as Tesla is truly pushing the autonomous future through its Robotaxi platform. However, others did not understand it.
“Damn, how many Cybercabs do you guys need?” one response read. Another said it was “Sad but understandable.”Even analyst Gary Black had responded to the news, stating he hoped Tesla planned to replace it with a traditional pickup design.
It doesn’t seem like that will be the case.
Tesla is so hell-bent on delivering autonomy and eventually providing a driverless service that owning a car seems like an arbitrary idea, according to their thesis. Instead, Cybercabs will be available to pick you up and drop you off on demand, safely, without any human help.
As a result, Tesla has thinned its lineup considerably, and one can only ask where the vehicle lineup goes from here. Eventually, it seems like Cybercab could be the only vehicle that Tesla will sell.
Elon Musk
SpaceX’s next Starship flight set to make history on Friday the 13th
SpaceX is targeting Friday, November 13 for Starship Flight 15 and its first ship catch.
SpaceX is targeting Friday, November 13 for Starship Flight 15, the mission the company plans to use for its first attempt at catching the ship itself with the launch tower.
SpaceX Vice President of Launch Kiko Dontchev shared the date on stage at the UP.Summit on Thursday, according to Ars Technica’s Eric Berger, who was in attendance. It is the first launch target to come directly from a SpaceX executive. Until now, the public schedule had relied on FAA air traffic planning slides, which listed Flight 15 for no earlier than November 8 and later November 12. SpaceX has not posted an official mission page yet, and no launch time has been shared.
The date lands inside the window Elon Musk sketched out last month. Speaking at Giga Texas on October 10, Musk said the flight would “probably launch a little bit before Thanksgiving,” as Teslarati reported. On SpaceX’s third quarter earnings call ten days later, he confirmed that Flight 15 would try to catch both the Super Heavy booster and the ship, and put the odds of a successful ship catch at “more likely than not.” SpaceX also aired an animation of the maneuver during that webcast, showing the ship swinging vertical over Starbase before dropping into the tower’s chopsticks.
The hardware is ready. Booster 22 fired all 33 of its Raptor engines for a full duration static fire at Pad 2 on October 25. Ship 42 followed with a single engine burn simulating a deorbit maneuver on October 26 and a 60 second firing of all six engines the next day, according to NASASpaceflight. Ship 42 had already rehearsed the catch in September, when the Pad 2 arms lifted it into position and crews connected the quick disconnect arm while the vehicle hung from the tower.
The remaining hurdle is regulatory. The FAA’s Starship page does not yet list a Flight 15 license. SpaceX President Gwynne Shotwell said in October that, after “significant constructive engagement with the FAA,” she expects the license to cover a return to the launch site and a tower catch for both stages. Bringing the ship home means a reentry path that heads toward land, rather than ending over open ocean as every Starship flight so far has.
SpaceX has caught Super Heavy three times, on Flights 5, 7 and 8, but the ship comes back from orbital velocity and has never been caught. Flight 14 on September 28 was the first Starship to reach orbit, deploying 26 Starlink V3 satellites before splashing down despite an early engine shutdown that Musk blamed on engine computer software.
Musk has called a successful ship catch “the first time that there’s been full recovery of an orbital class rocket,” and he has already named the step after it: a Flight 16 where both the booster and the ship fly again. NASASpaceflight reports that Ship 43, the next vehicle in line, is set for static fire testing in December.
Tesla Robotaxi app update now tells riders if Cybercab is the better choice
Tesla is ending Cybertruck production
