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. 

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

Advertisement
-

“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

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’s Powercore could change how data centers get power

Tesla unveiled Powercore, a solid-state transformer that could ease one of the grid’s worst bottlenecks.

Published

on

By

Tesla has unveiled Powercore, a solid-state medium voltage transformer that also handles the jobs of an inverter and a circuit breaker in a single unit. “Solid state medium voltage transformer, inverter and breaker – reliable, safe and secure,” the company’s Tesla Megapack account posted on X Tuesday, adding that the product is “Made in America” and will be “Operating 2027.” Elon Musk followed with his own post: “Advanced solid state transformers at scale from Tesla.”

Tesla rates Powercore at 7.4 MW, or 9 MVA, of continuous output at 34.5 kV AC, with grid-forming support for 10 MVA of peak power. Specs shared by Sawyer Merritt list a peak efficiency of 98.86 percent, a DC range of 800 to 2,000 volts and a built-in solid-state breaker that clears faults in about 100 microseconds. Tesla has not announced pricing, a factory location or a first customer.

The product fills a gap Tesla left open last year. When it introduced Megapack 3 and Megablock in September 2025, Tesla said it would build its own transformers, but shared almost nothing about them. Megablock groups four Megapack 3 units with a transformer and switchgear into a single medium voltage block, as Teslarati reported. Powercore appears to be that missing piece.

A typical battery or solar project today uses low voltage inverters to turn DC into AC, then a large oil-filled transformer to step that power up to grid voltage. A solid-state unit handles both steps with power electronics, which means less equipment, a smaller footprint and no flammable oil. Grid-forming capability lets it actively help hold voltage and frequency steady rather than simply following the grid.

Advertisement
-

Timing is a big part of the pitch. Lead times for conventional transformers have stretched into years as AI data centers and renewable projects crowd utility interconnection queues. Tesla energy executive Max de Zegher pointed to the problem in a post Musk shared, noting that “transformers have barely changed since the 1890s: copper coils in a tank of oil,” while batteries, solar and compute all run on DC. Powercore, he wrote, delivers “one conversion and about half the losses.” Tesla has also said its Megapack supply for 2027 is nearly sold out.

Tesla deployed 13.7 GWh of energy storage in the third quarter, its second best quarter on record. On Tuesday, the company also said customer solar systems deployed by Tesla Energy now generate more than twice the electricity its global operations consume each year.

Continue Reading

News

Tesla changes vehicle computers from ‘AI’ to ‘SI,’ reflecting President Trump change

Published

on

Tesla has officially changed the reference to its vehicles’ internal computers to “Super Intelligence,” or “SI,” reflecting a change that President Donald Trump made when he noted it would no longer be referred to as “Artificial Intelligence,” or “AI.”

Tesla hacker Green posted that a breakdown of Software Version 2026.44.1, noting that the in-car computer is now labeled as “SI Computer,” in system properties:

In September as he spoke at the UN’s General Assembly, President Trump said (via The Verge):

“The United States also totally rejects any attempt to construct a globalist scheme to control for the artificial intelligence being spoken of so much now. Here and after officially called “super intelligence,” changing the name, and that the use of the word artificial makes intelligence fake. It makes it sound fake, and it is not fake. It’s actually amazing. But we have to be careful. In fact, it is exactly the opposite of what it purports. From this point forward, all of the United States documents, and hopefully the world’s, will be changed to use the much more accurate term, super as opposed to artificial. So it’s super intelligence. In other words, welcome to the new world of super intelligence — SI. That’s, uh, let’s see if that does. It sounds much better. It is much better, and it’s much more accurate.”

Tesla and Musk have evidently chosen to adopt the change, as it now appears as an official reference to the company’s in-car computer.

Tesla has long used iterative software updates to refine Autopilot/FSD behavior, vehicle controls, and user interfaces. Renaming an internal identifier fits that pattern of quiet housekeeping far more closely than a sudden capability jump.

Owners on HW3 and later hardware continue to receive the same incremental FSD improvements seen in prior releases, as the property string does not alter compute allocation or model architecture.

Nevertheless, this won’t have any impact on the vehicles themselves, but it is more of an adoption of terms.

Continue Reading

News

Tesla just doubled its Miami Robotaxi geofence

Published

on

Credit: Tesla

Tesla just doubled the serviceable area that its Robotaxi platform can travel in Miami, Florida.

On November 16, Tesla announced a major expansion of its Miami service area with a message stating that it would now service substantially more of the city. A new map shows the new service area, which is roughly double the initial geofence, including key urban districts into Robotaxi for the first time.

Tesla first launched unsupervised Robotaxi rides in Miami on July 3, making it the company’s initial market outside of Texas and California. The original geofence covered a very limited portion of the western Miami-Dade area, including West Miami, Doral, Sweetwater, and Miami International Airport. It was roughly 25 square miles, before a small expansion put it at about 31.

Now, Downtown Miami, the popular Brickell neighborhood, and Miami Beach, which were deliberately left outside the boundary initially, now are included in operations. Riders can now hail Model Y vehicles booked through the Tesla Robotaxi app and have run 24 hours a day since mid-November.

The map now looks to be about 59 square miles, a roughly 92 percent increase. The new eastern edge of the geofence now includes Downtown, Bickell, Wynwood, Little Havana, and the Biscayne Bay waterfront, nailing down a lot of typical tourist locations for Miami visitors. Additionally, the new geofence also extends North, reaching Hialeah, and adding coverage closer to the airport corridor.

At its widest, the zone now stretches roughly 11 miles from west to east. Miami Beach remains outside the service area, though Elon Musk previously indicated beach coverage was “coming soon” after Florida Governor Ron DeSantis publicly called for it.

Relative to Tesla’s other markets, Miami’s roughly 59-square-mile zone is now larger than Orlando (about 26 square miles) and Tampa (about 24 square miles) combined.

It remains smaller than Texas hubs such as Austin (around 443 square miles), San Antonio (about 275), Houston (about 254), and Fort Worth (about 143), but the rapid growth brings it closer to competitor Waymo’s approximately 60-square-mile Miami footprint, which already includes beach areas.

For Miami residents and visitors, the expansion makes driverless rides practical for trips into the city’s densest commercial and residential core, offering a new option amid heavy traffic and limited parking.

For Tesla, covering higher-demand downtown corridors should increase ride volume, generate more real-world autonomy data, and strengthen its competitive position as it scales the Robotaxi network toward broader profitability and eventual Cybercab deployment. The overnight growth also signals accelerating operational confidence less than five months after the city’s launch.

Continue Reading