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 has scaled back driver monitoring to be less naggy with the latest version of the Full Self-Driving (Supervised) suite, which is version 14.3.3.
The latest version is already earning praise from owners, who are reporting that the suite is far less invasive when it comes to keeping drivers from taking their eyes off the road. The first to mention it was notable Tesla community member on X known as Zack, or BLKMDL3.
14.3.3 nags less too https://t.co/IuiWzuYO6O
— Elon Musk (@elonmusk) May 18, 2026
Musk confirmed that v14.3.3 was made to nag drivers significantly less, something that Tesla has worked toward in the past and has said with previous versions that it is less likely to push drivers to look ahead, at least after looking away for a few seconds.
This refinement aligns with Tesla’s ongoing push toward unsupervised FSD. The update also brings faster Actual Smart Summon (now up to 8 mph), reliable “Hey Grok” voice commands, richer visualizations, smoother Mad Max acceleration, and an intervention streak counter that rewards consistent use. Reviewers describe the drive as more human-like and confident, with fewer twitches or unnecessary maneuvers.
Musk has repeatedly signaled this direction. In late 2025, he stated that FSD would allow phone use “depending on context of surrounding traffic,” noting safety data would justify relaxing rules so drivers could text in low-risk scenarios like stop-and-go traffic.
We tested this, and even still, the cell phone monitoring really seems to be less active in terms of alerting drivers:
Tesla Full Self-Driving v14.2.1 texting and driving: we tested it
Earlier, ahead of v14, Musk promised the system would “nag the driver much less” once safety metrics improved.
In 2023, he confirmed the steering wheel torque nag would be “gradually reduced, proportionate to improved safety,” shifting reliance to the cabin camera. Subsequent updates like v13.2.9 and v12.4 further loosened monitoring, cracking down on workarounds while easing legitimate distractions.
These steps reflect Tesla’s data-driven approach: FSD’s safety record—reportedly averaging millions of miles per crash—now outpaces human drivers in many scenarios, giving the company confidence to dial back interventions. Reduced nags improve usability and trust, encouraging more drivers to rely on the system rather than disengaging out of frustration.
However, there are certainly still some concerns. In many states, it is illegal to handle a cell phone in any way, requiring the use of hands-free devices. In Pennsylvania, it is illegal to use your cell phone at stop lights, which is definitely a step further than using it while the car is actively in motion.
v14.3.3 represents tangible progress. Making FSD less adversarial and more seamless is definitely a step forward, but drivers need to be aware of the dangers of distracted driving. FSD is extremely capable, but it is in no way fully autonomous, nor does its performance warrant owners to take their attention off the road.
Tesla has officially expanded its Full Self-Driving (FSD) suite in Europe once again, as it will now be offered to customer vehicles in Lithuania, marking a significant milestone as the second European Union country to offer the system.
Tesla confirmed FSD’s rollout in Lithuania this morning:
FSD Supervised now rolling out to Teslas in Lithuania 🇱🇹!
Making European roads safer, one by one pic.twitter.com/Uuj0bNG7pP
— Tesla Europe, Middle East & Africa (@teslaeurope) May 20, 2026
Tesla showed several clips of Full Self-Driving navigation in Lithuania to mark the announcement, while Lithuanian Transport Minister Juras Taminskas highlighted the system’s potential to assist with lane-keeping, speed adjustment, and traffic tasks on longer drives, while emphasizing that drivers must stay alert and ready to intervene.
Just a few weeks ago, Tesla officially entered Europe with Full Self-Driving in the Netherlands. The expansion of FSD on the continent is now officially underway.
Full Self-Driving’s European Journey
Europe has long posed one of the toughest regulatory challenges for Tesla’s autonomy ambitions due to stringent safety standards under the United Nations Economic Commission for Europe (UNECE) framework, particularly UN Regulation 171 for Driver Control Assistance Systems.
The Netherlands’ RDW authority granted the pioneering approval after over 18 months of rigorous testing, including 1.6 million kilometers on European roads and extensive data submissions.
This approval enables mutual recognition across the EU, allowing other member states to adopt it nationally without full re-testing. Lithuania quickly leveraged this mechanism, becoming the second adopter. Tesla positions FSD Supervised as a tool to incrementally improve road safety, with the company claiming it reduces incidents when used properly.
Bottlenecks slowing broader European deployment include fragmented national regulations, varying levels of regulatory skepticism, and requirements for robust driver monitoring. Some EU officials have raised concerns about performance in adverse conditions like icy roads or speeding scenarios, alongside frustrations over Tesla’s public advocacy approach.
Additional hurdles involve data privacy, liability frameworks, and the need for EU-wide harmonization. While countries like Belgium appear to be fast-tracking adoption, larger markets such as Germany, France, and Italy are expected to follow in the coming months, with potential EU-wide progress targeted for later in 2026.
Tesla Full Self-Driving Across the World
As of May, Full Self-Driving (Supervised) is available in approximately ten countries.
In North America, it has been live for years in the United States, Canada, Mexico, and Puerto Rico. Asia-Pacific additions include Australia, New Zealand, and South Korea, while China utilizes what Tesla calls “City Autopilot.” In Europe, the Netherlands and now Lithuania join the list, with more countries mulling the possibility of also approving FSD.
Tesla offers FSD via monthly subscriptions (around €99 in Europe) or one-time purchases (with deadlines approaching in many markets), shifting toward recurring revenue models. Today is the final day Europeans will be able to purchase the suite outright.
This expansion underscores Tesla’s push for global autonomy, starting with supervised and building toward greater capabilities. With Lithuania now online, momentum is building across Europe, though regulatory caution will continue shaping the pace. Owners in approved regions report smoother highway and urban driving, but the system remains Level 2, which requires human oversight.
Elon Musk
Tesla ditches India after years of broken promises
Tesla has ditched its plans to build a factory in India after years of failed negotiations.
Tesla’s long-running effort to establish a manufacturing presence in India is officially over. India’s Minister of Heavy Industries H.D. Kumaraswamy confirmed on May 19, 2026 that Tesla has informed authorities it will not proceed with a manufacturing facility in the country.
Tesla first signaled serious interest in India around 2021, when it began hiring local staff and lobbying the Indian government for lower import tariffs. The ask was straightforward: reduce duties enough for Tesla to test the market with imported vehicles before committing capital to a local factory. India’s position was equally firm, with an ask of Tesla to commit to manufacturing first, then receive tariff relief. Neither side moved, and the talks quietly collapsed.
Tesla to open first India experience center in Mumbai on July 15
India had offered a policy that would reduce import duties from 110% down to 15% on EVs priced above $35,000, provided companies committed at least $500 million toward local manufacturing investment within three years. Tesla declined to participate. The tariff standoff was only part of the problem. Analysts pointed to significant gaps in India’s local supply chain, inadequate industrial infrastructure, and a mismatch between Tesla’s premium pricing and the purchasing power of India’s automotive market as additional factors that made the investment difficult to justify.
First signs of an unraveling relationship came in April 2024, when Musk abruptly cancelled a planned trip to India where he was set to meet Prime Minister Modi and announce Tesla’s market entry. By July 2024, Fortune reported that Tesla executives had stopped contacting Indian government officials entirely. The government at that point understood Tesla had capital constraints and no plans to invest.
The more fundamental issue is that Tesla’s existing factories are currently operating at approximately 60% capacity, making a commitment to building new manufacturing capacity in a new market difficult to defend to investors. Tesla will continue selling imported Model Y vehicles through its existing showrooms in Mumbai, Delhi, Gurugram, and Bengaluru, but local production is no longer part of the plan.
Tesla scales back driver monitoring with latest Full Self-Driving release
Tesla Full Self-Driving expands in Europe, entering its second country
