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
Why automakers keep turning down Elon Musk’s Tesla Full Self-Driving offer
Elon Musk confirms no automaker has ever accepted Tesla’s offer to license Full Self-Driving software.
Elon Musk gave a brief answer on X Monday that confirmed that Tesla’s standing offer to license Full Self-Driving to other automakers still has zero takers. Sawyer Merritt wrote that “Tesla has for years openly invited other automakers to license FSD. None of them have accepted,” responding to a prediction from Boom Supersonic founder Blake Scholl that Tesla would eventually open FSD the way it opened its Supercharger network to rival brands. Musk’s reply to Merritt was one word: “Exactly.”
It is not the first time Musk has made this point. He said something similar in November, when he called legacy automakers reluctance to adopt FSD “crazy,” and Tesla has floated the offer publicly since at least 2021. Scholl’s prediction touches on something real. Once NACS became the de facto charging standard, adoption from Ford, GM, Rivian and others followed within about a year. FSD licensing was supposed to work the same way once Tesla built enough of a lead that switching made sense for everyone.
Tesla has for years openly invited other automakers to license FSD. None of them have accepted. https://t.co/kgz4idpoUM
— Sawyer Merritt (@SawyerMerritt) September 22, 2026
The case for licensing now is stronger than it was two years ago. Waymo and Zoox are logging hundreds of thousands of unsupervised autonomous miles, along with Tesla’s own Robotaxi fleet. Every automaker still selling driver assist systems that lag FSD has given the robotaxi conversation to Tesla, Waymo and Zoox by default. Licensing FSD would let a GM or a Ford compete on the same field without spending a decade and billions of dollars building a stack from scratch, the same argument Tesla made when it opened the Supercharger network to bring more EVs onto its chargers.
But FSD is not a connector standard. As one reply to Musk’s post pointed out, licensing FSD is not a software license the way NACS was a plug spec. It requires adopting Tesla’s eight camera layout and its onboard compute architecture, meaning a licensee’s cars would effectively become Tesla hardware wearing someone else’s badge. That is the visible obstacle. The less visible one is data. A licensed FSD stack would report back the same telemetry Tesla collects from its own fleet, giving Tesla a continuous read on how a competitor’s cars are actually driven, where they struggle, and how often drivers intervene. For an automaker trying to build its own autonomy program, or simply trying to keep its build quality and safety record private, handing Tesla that visibility could be a bigger cost than the hardware bill. It is the reason the Supercharger comparison only goes so far. Opening a charging plug cost Tesla very little. Opening FSD would cost a rival something it cannot get back.
Tesla has reopened reservations for its long-delayed next-generation Roadster, asking buyers for a $50,000 deposit just days before an October 1 reveal event in Waco, Texas. The move revives a reservation process first launched in 2017 and later paused when Tesla pulled pricing from its website in 2021.
The reservation page requires an immediate $5,000 credit-card payment, described as fully refundable, followed by a $45,000 wire transfer due within 10 days, which is identical to what was expected previously. Reservations are not considered final until the wire clears.
The structure matches the 2017 terms Tesla used when it first collected deposits after unveiling a prototype. Tesla has not published a confirmed retail price or production start date on the order page.
Go buy a Roadster pic.twitter.com/n7rhouAmIS
— TESLARATI (@Teslarati) September 21, 2026
The October 1 event is scheduled in Waco, about 90 minutes north of Tesla’s Austin headquarters and near SpaceX’s McGregor rocket test site. Tesla sent invitations to existing reservation holders and posted a “Go for launch” teaser on September 12.
The Federal Aviation Administration (FAA) established a temporary flight restriction over the McGregor area from September 18 through October 2, consistent with plans for a demonstration involving SpaceX-designed cold-gas thrusters. Elon Musk has previously described the optional package as enabling extreme acceleration or brief hovering. Tesla has said the event will include pricing, specifications, and production targets.
The second-generation Roadster was first shown in November 2017 during Tesla’s Semi launch. Musk promised production in 2020, with claimed performance of 0-60 mph in 1.9 seconds, more than 250 mph top speed, and roughly 620 miles of range.
Those targets have slipped repeatedly.
Tesla later pointed to 2022, 2023, 2024, and 2025-2026 before indicating production would not begin until 2027 or 2028 at Gigafactory Texas. Design work has continued, with reports of a sharper, Cybertruck-influenced look replacing the original curvy prototype.
Original reservation holders who paid $50,000 in 2017, or $250,000 for the Founders Series, have waited nearly nine years without a production car. Some high-profile customers canceled. Tesla’s decision to reopen orders now, after previously shutting them down, tests whether new buyers will commit substantial funds before seeing a finalized production vehicle. The October 1 event is intended to answer remaining questions about what those buyers will actually receive and when.
Tesla’s Full Self-Driving (Supervised) is heading to Czechia after the Czech Ministry of Transport recognised the Dutch RDW’s provisional type approval, making the country the seventh EU member state to clear the system for public roads. Tesla Europe announced on 21 September 2026 that “FSD Supervised is now approved in Czechia” and that rollout “will begin soon.”
The decision marks a notable reversal. Earlier in 2026, Prague had declined to automatically recognise the Netherlands’ April approval, citing concerns over speed-limit compliance, traffic-sign recognition and driver-attention monitoring, and arguing that a coordinated EU approach was preferable. Officials said months of expert review, talks with Tesla and other member states, and real-world data from countries already using the system resolved those issues.
🚨 Tesla FSD heading to Czechia 🇨🇿 pic.twitter.com/mkzlM9QjrB
— TESLARATI (@Teslarati) September 21, 2026
“Safety remains the top priority,” the ministry stated.
FSD Supervised remains a Level 2 driver-assistance system: the driver must stay engaged and is legally responsible. Eligible vehicles need AI4, the company’s most up-to-date hardware version. Tesla is expected to push the feature over the air in the coming days, following the pattern seen after earlier national approvals.
Europe’s rollout began when Dutch regulator RDW issued a provisional EU type approval on 10 April 2026 after extensive testing. Mutual recognition then produced a rapid cascade: Lithuania (20 May), Estonia (29 May), Denmark (9 June), Belgium (10 June) and Slovenia (7 September). Czechia now completes that list of seven.
The approvals cover only a modest share of the EU population, but they add political weight ahead of a 6 October vote by the Technical Committee on Motor Vehicles. A qualified majority, at least 15 of 27 member states representing 65 percent of the EU population, could open the remaining markets, including large ones such as Germany, France, Italy and Spain that have so far preferred to wait for a bloc-wide decision.
For Czech Tesla owners, the immediate prize is access to the same supervised highway and city driving already available in the other six countries. For Tesla, each new market generates additional European driving data and strengthens the case that FSD Supervised can operate safely under the continent’s varied road rules. The Czech approval is therefore both a local milestone and another incremental step toward a wider European launch.
Why automakers keep turning down Elon Musk’s Tesla Full Self-Driving offer
Tesla Roadster is available for order once again following brief hold
