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.
Tesla revealed plans to develop its own maps internally to fix Navigation issues and give owners more control over their routing.
On the company’s Q3 2026 Earnings Call, a question was asked about FSD Navigation issues, particularly speed limit recognition, parking, and routing. These are issues that surface from version to version and seem to be seriously challenging for Tesla’s AI team to resolve.
Tesla’s Head of AI, Ashok Elluswamy, said in response to the question:
“You’re totally right that we shouldn’t be depending on external people’s maps. So we are building our own maps, but not like the same way as OneMoreMap. We are building an entirely new architecture with essentially AI-based mapping and navigation.”
He continued:
“It’s going to be super awesome. It’s going to be integrated with voice. You can talk to it, ask for different routes. It’s going to learn your personalized preferences, plus the fleet preferences. The collective intelligence of all the cars is going to flow into making the maps and navigation super cool.”
Elluswamy said this issue should be confronted, and the mapping should be available for people by the time the v15 release starts deploying to customers.
“And over the next several months,” he added, “it’s just going to take over all of the navigation functions, parking, destination handling. And it will know you better than you know yourself in some regard for the driving task, and then handle it fully.”
Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much
Navigation is perhaps the most notable complaint with FSD, and although it has gotten better, it is still flawed. Much of the time, FSD will take people on routes that are not preferred by the driver, but Tesla tried to combat this with a routing feature in the Summer 2026 Update.
Tesla currently relies on Google for map data, but it is sort of counterintuitive to believe the company would rely on a third party for this. These improvements will be welcome, as routing and navigation have been such a pain point for so many owners for so long.
Quotes via Motley Fool
Tesla Full Self-Driving (Supervised) showed a record attach rate at delivery for new vehicles in the third quarter of 2026.
75 percent of new vehicle deliveries in North America included a subscription to FSD software, up from 55 percent in the prior quarter, a 20-percentage-point sequential gain in the company’s most mature market.
Tesla Q3 2026 Earnings results: in-line revenues, slight beat on EPS
Tesla shed light on the Q3 Shareholder Deck that 75 percent of new deliveries came with an FSD subscription:
“FSD (Supervised)⁴ attach rate continued to grow, reaching over 75% of new vehicle deliveries in North America – our most mature market – a nearly twenty percentage point sequential increase. We believe that FSD is driving demand in markets where it is available, and we continue to work with regulators to get it approved in other markets. “
The higher attach rate accompanied strong growth in the overall FSD consumer base, as active subscriptions rose to 1.75 million, a 67 percent year-over-year increase. For the first time, more than half of paid customers are on the monthly subscription, which is priced at $99 per month in the U.S.
People are buying FSD with a car attached, not the other way around
— Elon Musk (@elonmusk) October 21, 2026
The transition to subscriptions has accelerated since Tesla discontinued the one-time purchase option in most markets earlier this year. The recurring model improves revenue visibility and margins compared with large upfront payments. With three-quarters of North American deliveries now including FSD, the software is now an evidently large contributor to Tesla’s economics and ancillary revenue.
Geographic expansion remains important for further gains. FSD is now available in nine countries in the EU, and more than 100,000 customers have driven over 160 million kilometers. Tesla is pursuing broader EU-wide approval, with a related vote expected in December. Similar progress in additional markets could support higher attach rates beyond North America.
These results came as Tesla had a strong quarterly delivery performance of 486,532 vehicles in the quarter, which came with its largest passenger-vehicle backlog in four years. Battery supply continued to limit volume, but the company has pointed to FSD as a clear difference-maker that is helping sustain demand. As supervised capabilities improve, the attach rate will likely continue to improve.
At face value, it is a key measure of how Tesla is converting sales into autonomy progress.
Update: 10/22 10:51a – Para 1 consumers changed to “customers” for accuracy.
Tesla Cybercab units finally got a definitive date for when they will be able to be purchased by customers, ending speculation regarding whether the fully autonomous vehicle would be available in the near term.
During Tesla’s third-quarter 2026 earnings call on October 21, Vice President of Engineering Lars Moravy said the company is aiming to begin delivering its purpose-built Cybercab robotaxi to customers before year-end.
🚨 In short, Cybercabs are slated to go to customers by end of the year. All units are going into Robotaxi fleet currently, per @larsmoravy
Cybercab will be “transport-as-a-service,” but vast majority of Cybercab will be “Tesla-owned,” @elonmusk says https://t.co/R8Qu8QWdmp
— TESLARATI (@Teslarati) October 21, 2026
“We’re trying to get Cybercabs to customers by the end of this year, 2026,” Moravy said. He added that production is underway on the line at Gigafactory Texas, but “all of those are currently going to our own internal Robotaxi fleet.”
Moravy explained that as operations scale, Tesla will “mainly deliver fully designed autonomous vehicles to our customers,” with the Cybercab as the first such vehicle. Initial customer deliveries will start small while the company gains experience with delivery logistics, ownership models, fleet management, and operating autonomous vehicles outside its direct control.
CEO Elon Musk reinforced the limited nature of private sales, describing the Cybercab primarily as a “transport-as-a-service” offering rather than a personal ownership vehicle like the Model 3, Model Y, or upcoming Roadster. “The vast majority of the Cybercab stuff will be Tesla-owned and transport-as-a-service,” Musk said.
The Cybercab is a two-seater vehicle developed by Tesla without a steering wheel or pedals. It relies completely on Tesla’s Full Self-Driving suite and has been in production since February. Early units have been put in Tesla’s Robotaxi service as of early September, when the company launched rides to the public. Tesla previously indicated it would aim to sell Cybercabs for about $30,000.
Unsupervised Full Self-Driving is expected to ship to consumer cars during Q2 2027, Ashok Elluswamy, Tesla’s Head of AI, indicated during the call. Early buyers or fleet operators may receive vehicles whose autonomous operation remains geographically restricted due to lagging regulatory agencies. There are some hurdles that remain ahead of Cybercab deliveries.
Tesla is building its own maps to fix Navigation issues
Tesla buyers are buying for Full Self-Driving and not for the car, data shows
