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.
A Texas man has been arrested and charged with manslaughter after his Tesla crashed into a home last month, striking a woman inside and killing her. The driver, Michael Butler, claimed the vehicle was in self-driving mode, but information from Tesla shows that Butler overrode the system.
Butler was arrested on Wednesday and booked at the Harris County, Texas, jail. He remained in custody through Thursday and Friday; he did not enter a plea, and his next court hearing is scheduled for Monday.
Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration
There are a handful of new clues in the case that could clear Tesla of any wrongdoing, especially as the woman who was killed’s family, the Avilas, filed a wrongful death lawsuit against Tesla and Butler, seeking at least $1 million in damages.
Charging documents from the Harris County prosecutor now show that Butler, who was working DoorDash the evening of the accident, had been using Full Self-Driving mode without incident through the duration of multiple deliveries that evening.
In the moments leading up to the crash, while in FSD and approaching a left turn, Butler pressed the accelerator pedal, overriding FSD’s speed control, and continued to push it until it reached 100 percent. This caused rapid acceleration; the brake pedal was never pressed, and there is no data to show that Butler aimed to turn away from the curb or house.
The charging documents state:
“I noted that the brake pedal was never pressed in the final minute before the crash. I also did not see any data to indicate that the driver attempted to turn away from the curb that he eventually struck. Further, I observed that no mechanical error was detected or recorded by the vehicle before BUTLER and the Tesla struck the curb.”
Additionally, a forensic analysis of Butler’s phone showed that he searched Google around the time of the crash with queries questioning why FSD was “too timid,” “not aggressive enough,” and even searched, “FSD is not aggressive enough for city driving.”
The documents outlined this:
“Investigator Veal also informed me that he had received BUTLER’s cell phone from Deputy Amad and that HDAO digital forensics team had completed a data extraction and download of the phone. Multiple Google searches related to Tesla had been made from BUTLER’s phone in the months leading up the crash. I noted multiple searches in May of 2026 indicating an apparent frustration with Tesla’s FSD mode, including the following searches: “Tesla fsd not aggressive enough 2026 model,” “Tesla fsd not [sic) aggressive enough 2026,” “FSD is not aggressive enough for city driving,” and “tesla fsd too timid.”‘
Tesla had claimed just after the crash that its internal data showed Butler had overridden the system’s speed control and pressed the accelerator completely, causing the vehicle to travel at an excessive rate of speed. Eventually, the car slammed into Avila’s house, killing her.
Butler has now been formally charged with Manslaughter, a felony.
Tesla shocked with its quarterly delivery report yesterday by reporting it delivered 480,126 vehicles in the second quarter of 2026, a 25 percent year-over-year jump that crushed Wall Street estimates of roughly 400,000–408,000 units. Production reached 451,758, with Model 3 and Model Y accounting for the vast majority.
The result ended two years of annual delivery declines and drew down inventory, signaling demand that outpaced earlier production.
Tesla bears had long warned that the expiration of the U.S. federal EV tax credit would hammer demand. Without the $7,500 incentive, they argued, American buyers would balk at higher effective prices, leading to a sharp slowdown.
Will Tesla thrive without the EV tax credit? Five reasons why they might
That narrative has not played out as predicted. While U.S. EV sales faced broader headwinds, Tesla’s global numbers held firm, underscoring the company’s ability to offset domestic pressure through other levers.
There are several plausible factors that explain Tesla’s strength during this quarter. Let’s take a look at them:
Rising Gas Prices
Rising gas prices provided a powerful tailwind, especially in the U.S.
Geopolitical tensions tied to the Iran conflict pushed fuel costs higher earlier in the year, amplifying the lifetime savings of electric vehicles. Even as oil prices later moderated, the psychological and financial impact lingered, encouraging fleet operators and private buyers to accelerate EV purchases. European sales rebounded sharply, helping drive the quarter’s outperformance.
Full Self-Driving Adoption
Advances in Full Self-Driving (FSD) supervised software also appear to have boosted appeal. Tesla expanded FSD availability in select European markets and continued refining the system.
No complaints from me because I finally got to enjoy this drive on FSD; I usually like to manually drive down this mountain https://t.co/RBFniRPSR0 pic.twitter.com/XQ5sOpN1Yg
— TESLARATI (@Teslarati) June 26, 2026
For tech-oriented buyers, the promise of future autonomy and enhanced driver-assistance features adds perceived value beyond the car itself. This differentiation helps Tesla stand out in a crowded market where competitors focus primarily on hardware and basic range.
Pricing Strategy, Affordable Configurations
Tesla’s offerings and its pricing strategy during Q2 further stimulated demand. Tesla introduced lower-cost versions of the Model 3 and Model Y, widening accessibility without sacrificing core margins.
These moves countered affordability concerns and attracted buyers who had been waiting on the sidelines. Combined with attractive financing and leasing options, the pricing strategy converted interest into actual orders more effectively than many analysts expected.
Broad European Recovery
Supported by government incentives, corporate fleet electrification, and easing political headwinds around CEO Elon Musk, Tesla was supplied additional momentum through stronger registration numbers throughout Europe.
Strong exports from the Shanghai Gigafactory and a production ramp at Giga Berlin ensured supply met this resurgent demand. Corporate buyers, in particular, accelerated transitions to EVs to meet sustainability targets, providing a steady volume base.
These elements created a virtuous cycle that delivered the strong deliveries report. While bears correctly flagged the loss of the U.S. tax credit as a risk, Tesla’s diversified playbook demonstrated that it could remain resilient against those headwinds. The Q2 beat suggests the company remains adept at navigating shifting market conditions, even as competition intensifies.
A Tesla Semi was involved in a fatal collision on U.S. Highway 50 in Dayton, Nevada, on Sunday, June 28, 2026, marking the first known fatal crash involving the electric Class 8 truck. The incident occurred around 7:20 a.m. at the intersection with Traditions Parkway, approximately 40 miles east of Reno and close to Tesla’s Gigafactory Nevada.
According to the Lyon County Sheriff’s Office and the Nevada State Police Highway Patrol, a semi-truck struck two passenger vehicles stopped at a traffic signal. The truck hit the vehicles from behind. Two people were pronounced dead at the scene, and a third person suffered life-threatening injuries and was flown to a hospital, Forbes reported.
Preliminary statements gathered at the scene by the Lyon County Sheriff’s Office suggested the truck driver may have fallen asleep at the wheel. However, the Nevada Highway Patrol, which is leading the investigation, stated that the official cause has not yet been determined.
Additional information is expected to be released early the following week. The truck was seized for evidence as part of the ongoing probe.
Responders at the scene included deputies from the Lyon County Sheriff’s Office, personnel from the Nevada Highway Patrol, Central Lyon County Fire Department, and the Nevada Department of Transportation. The crash led to the temporary closure of U.S. 50 in both directions.
The Tesla Semi is Tesla’s battery-electric heavy-duty truck, produced at the nearby Gigafactory in Nevada. Authorities initially described the vehicle as a semi-truck; its make was subsequently confirmed through reporting and scene identification; an interesting bit of information here, as the Semi is not yet available publicly and many do not know that Tesla builds electric trucks.
The investigation remains active, with no further official details on contributing factors or vehicle systems released as of early July 2026.
This incident highlights ongoing scrutiny of commercial vehicle safety on Nevada highways, particularly involving fatigue. Law enforcement continues to gather evidence and witness statements.
Texas man charged in fatal Tesla crash where he blamed Autopilot
Tesla’s strong Q2 deliveries: Four key drivers behind the surprise
