Connect with us
Cruise car in Hayes Valley, San Francisco Cruise car in Hayes Valley, San Francisco

News

Cruise in hot seat amid Fire Department’s claims that robotaxis delayed responders in fatal incident

Credit: Cruise

Published

on

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. 

Advertisement

“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.” 

Advertisement

“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

Advertisement

Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads-up. 

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

Elon Musk

Tesla Semi’s official battery capacity leaked by California regulators

A California regulatory filing just confirmed the exact battery size inside each Tesla Semi variant.

Published

on

By

A regulatory filing published by the California Air Resources Board in April 2026 has put official numbers on what Tesla Semi owners and fleet buyers have long wanted confirmed: the exact battery capacities of both the Long Range and Standard Range Semi truck variants. CARB is California’s independent air quality regulator, and it certifies zero-emission powertrains before they can be sold or operated in the state. When a manufacturer submits a vehicle for certification, the resulting executive order becomes a public document, making it one of the most reliable sources for confirmed production specs on any EV.

The document lists two certified powertrain configurations. The Long Range Semi carries a usable battery capacity of 822 kWh, while the Standard Range version comes in at 548 kWh. Both use lithium-ion NCMA chemistry and share the same peak and steady-state motor output ratings of 800 kW and 525 kW respectively. Cross-referencing Tesla’s published efficiency figure of approximately 1.7 kWh per mile under full load, the 822 kWh pack supports roughly 480 miles of real-world range, which aligns closely with Tesla’s advertised 500-mile figure for the Long Range trim. The 548 kWh Standard Range pack works out to approximately 320 miles, again consistent with Tesla’s stated 325-mile target.

Here is a direct comparison of the two versions based on the CARB filing and published specs:

Tesla Semi Spec Long Range Standard Range
Battery Capacity 822 kWh 548 kWh
Battery Chemistry NCMA Li-Ion NCMA Li-Ion
Peak Motor Power 800 kW 525 kW
Estimated Range ~500 miles ~325 miles
Efficiency ~1.7 kWh/mile ~1.7 kWh/mile
Est. Price ~$290,000 ~$260,000
GVW Rating 82,000 lbs 82,000 lbs

The timing of this certification is not incidental. On April 29, 2026, Semi Programme Director Dan Priestley confirmed on X that high-volume production is now ramping at Tesla’s dedicated 1.7-million-square-foot facility in Sparks, Nevada. A key advantage of the Nevada location is vertical integration: the 4680 battery cells powering the Semi are manufactured in the same complex, eliminating the supply chain bottleneck that had delayed the program for years.

Advertisement

Tesla’s long-term goal is to reach a production capacity of 50,000 trucks annually at the Nevada factory, which would represent roughly 20 percent of the entire North American Class 8 market. With CARB certification now in hand and the production line running, the regulatory and manufacturing groundwork for that target is in place.

Continue Reading

News

Tesla crushes NHTSA’s brand-new ADAS safety tests – first vehicle to ever pass

Published

on

Credit: Tesla

Tesla became the first company to pass the United States government’s new Advanced Driver Assistance Systems (ADAS) testing with the Model Y, completing each of the new tests with a passing performance.

In a landmark announcement on May 7, the National Highway Traffic Safety Administration (NHTSA) declared the 2026 Tesla Model Y the first vehicle to pass its newly ADAS benchmark under the New Car Assessment Program (NCAP).

Model Y vehicles manufactured on or after November 12, 2025, met rigorous pass/fail criteria for four newly added tests—pedestrian automatic emergency braking, lane keeping assistance, blind spot warning, and blind spot intervention—while also satisfying the program’s original four ADAS requirements: forward collision warning, crash imminent braking, dynamic brake support, and lane departure warning.

NHTSA administration Jonathan Morrison hailed the achievement as a milestone:

“Today’s announcement marks a significant step forward in our efforts to provide consumers with the most comprehensive safety ratings ever. By successfully passing these new tests, the 2026 Tesla Model Y demonstrates the lifesaving potential of driver assistance technologies and sets a high bar for the industry. We hope to see many more manufacturers develop vehicles that can meet these requirements.”

Advertisement

The updates to NCAP, finalized in late 2024 and effective for 2026 models, reflect growing recognition that ADAS features are no longer optional luxuries but essential tools for preventing crashes.

Pedestrian automatic emergency braking, for instance, targets one of the fastest-rising causes of roadway fatalities, while blind spot intervention and lane keeping assistance address common sources of side-swipes and run-off-road incidents. By incorporating objective, performance-based evaluations rather than mere presence of the technology, NHTSA aims to give buyers clearer data on real-world effectiveness.

This milestone arrives at a pivotal moment when vehicle autonomy is transitioning from science fiction to everyday reality.

Tesla’s Full Self-Driving (FSD) software and the impending rollout of robotaxis underscore a broader industry shift toward higher levels of automation. Yet regulators and consumers remain cautious: safety data must keep pace with technological ambition.

Advertisement

The Model Y’s perfect score on these ADAS benchmarks validates that current driver-assist systems—when engineered rigorously—can dramatically reduce human error, which still accounts for the vast majority of crashes.

For Tesla, the result reinforces its long-standing claim of building the safest vehicles on the road. More importantly, it signals to the entire auto sector that meeting elevated federal standards is achievable and expected.

As autonomy edges closer to Level 3 and beyond, where drivers may disengage more fully, such independent verification becomes critical. It builds public trust, informs purchasing decisions, and accelerates the development of systems that could one day eliminate tens of thousands of annual traffic deaths.

In an era when software-defined vehicles promise transformative mobility, the 2026 Model Y’s NHTSA triumph is more than a manufacturer accolade—it is a regulatory green light that autonomy’s future must be built on proven, testable safety foundations. The bar has been raised. The industry, and the roads we share, will be safer for it.

Advertisement
Continue Reading

News

Tesla to fix 219k vehicles in recall with simple software update

Published

on

Credit: Tesla

Tesla is going to fix the nearly 219,000 vehicles that it recalled due to an issue with the rearview camera with a simple software update, giving owners no need to travel to a service center to resolve the problem.

Tesla is formally recalling 218,868 U.S. vehicles after regulators discovered a software glitch that can delay the rearview camera image by up to 11 seconds when drivers shift into reverse.

The affected models include certain 2024-2025 Model 3 and Model Y, as well as 2023-2025 Model S and Model X vehicles running software version 2026.8.6 and equipped with Hardware 3 computers. The National Highway Traffic Safety Administration (NHTSA) determined the lag violates Federal Motor Vehicle Safety Standard 111 on rear visibility and could increase crash risk.

Yet this is no ordinary recall. Owners do not need to schedule a service-center visit, hand over keys, or wait for parts.

Advertisement

Tesla fans call for recall terminology update, but the NHTSA isn’t convinced it’s needed

Tesla identified the issue on April 10, halted further deployment of the faulty firmware the same day, and began pushing a corrective over-the-air (OTA) software update on April 11.

By the time the NHTSA posted the recall notice on May 6, more than 99.92 percent of the affected fleet had already received the fix. Tesla reports no crashes, injuries, or fatalities linked to the glitch.

The episode underscores a deeper problem with regulatory language. For decades, “recall” meant hauling a vehicle to a dealership for hardware repairs or replacements. That definition no longer fits software-defined cars. When a fix arrives wirelessly in minutes — identical to an iPhone update — the term evokes unnecessary alarm and misleads the public about the actual risk and remedy.

Advertisement

Elon Musk has repeatedly called for exactly this change. After earlier NHTSA actions, he stated plainly: “The terminology is outdated & inaccurate. This is a tiny over-the-air software update.” On another occasion, he added that labeling OTA fixes as recalls is “anachronistic and just flat wrong.”

Musk’s point is simple: regulators must evolve their vocabulary to match the technology. Traditional recalls involve physical intervention and downtime; OTA updates do not. Retaining the old label distorts consumer perception, inflates perceived defect rates, and slows the industry’s shift to faster, safer software iteration.

Advertisement

Tesla’s rapid, remote remedy demonstrates the safety advantage of over-the-air capability. Problems that once required weeks of dealer appointments are now resolved in hours, often before most owners notice. As more automakers adopt software-first designs, the entire regulatory framework needs to catch up.

Updating “recall” terminology would align language with reality, reduce public confusion, and recognize that modern vehicles are no longer static hardware — they are continuously improving computers on wheels.

For the 219,000 Tesla owners involved, the process is already complete. The camera works, the car is safe, and no one left their driveway. That is the new standard — and the vocabulary should reflect it.

Advertisement
Continue Reading