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
Sean Duffy fires back at Elon Musk over free Starlink
Sean Duffy says the FAA picked a ground network over Starlink, and Musk isn’t impressed.
Transportation Secretary Sean Duffy has responded to Elon Musk’s claim that the Federal Aviation Administration turned down free Starlink terminals before last week’s nationwide ground stop, saying the department chose a ground-based network after running into problems with an earlier version of the satellite service. Musk’s reply was a single emoji: “🤦♂️.”
Speaking at a press conference, Duffy said Starlink had been useful in some parts of the system. “I’ve worked well with Elon, and he, Starlink was a great solution for some of our assets in Alaska, but we sent Starlink, in one of its prior iterations, to our tech lab, and, there was some issues that we had to navigate, and we thought that the best method is to have a network that’s based on the ground,” Duffy said, according to a transcript published by ZeroHedge. “Now, I think what he’s doing with Starlink and the speed is remarkable, but, our airspace is very big. We have assets everywhere. And so, again, we used him for different parts of the airspace.”
Duffy did not dispute that the offer was made. He also did not say what problems the FAA found during testing.
The exchange started Monday, when Musk wrote on X, “Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” as Teslarati reported. That post came three days after the FAA grounded departures nationwide on November 13, when its legacy equipment became unstable as data flooded its telecommunications network at 1,000 connection attempts every four to five seconds. The FAA traced the flood to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where L3Harris had been installing a new router. Roughly 12,462 flights were canceled that day.
As I was saying …
Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were.
— Elon Musk (@elonmusk) November 16, 2026
Duffy has also signaled frustration with L3Harris, which runs the FAA’s current network. “I want to get away from L3Harris and get to a new one, but they own the network,” he said. “I can’t cancel the network that they own.” He has asked Congress for $50 billion to modernize air traffic control, arguing against “a patchwork, a fix to a system that’s critical for every single family.”
The FAA’s position on satellite links predates this week. In a July 2025 letter to lawmakers, FAA Administrator Bryan Bedford said the agency “would not use Starlink (or any satellite service) as the sole communications technology” for safety-critical air traffic services. Reuters reported at the time that the FAA was not considering replacing its L3Harris and Verizon contracts with Starlink. Verizon’s FAA Enterprise Network Services contract, awarded in 2023, is valued at up to $2.4 billion over 15 years.
Musk first pressed the issue in February 2025, while he was leading the Department of Government Efficiency, writing that “the Verizon system is not working and so is putting air travelers at serious risk” before correcting himself days later to blame L3Harris. SpaceX said at the time it was supplying Starlink kits to the FAA at no cost and had no intent to take over any existing contract.
Elon Musk
Tesla gears up Cybercab with Starlink for public debut, but with notable changes
Tesla is gearing up Cybercab, its all-electric and fully autonomous ride-hailing vehicle, for a very public debut as it plans to start customer deliveries in December. However, the units that rolled out of Gigafactory Texas this morning seem to differ from what we have seen previously.
Aerial images captured by drone photographer Joe Tegtmeyer at Giga Texas on November 18 reveal a noticeable update to the appearance of Tesla’s Cybercabs equipped with Starlink. Rows of gold production vehicles sit in the outbound lot, each carrying a flush-mounted Starlink V5 terminal on the rear hatch that looks more refined than the version first shown months earlier.
When Tesla first unveiled the integration in July and displayed a physical example in August, the Starlink hardware appeared as a relatively distinct rectangular panel on the hatch. Later September footage of large numbers of Cybercabs leaving the factory still showed a lighter, more obvious rectangular cover that roughly matched the vehicle’s gold paint:

Images via Joe Tegtmeyer
The newest batch stands out for how cleanly the cover blends into the roof’s character lines. Observers and replies to Tegtmeyer’s post describe the result as tighter and more intentional, sitting flush and following the body contours rather than reading as an added panel.
All of the Cybercabs in the latest images also wear prominent “Cybercab” logos on the doors and rear hatch, confirming these are finished production units rather than early prototypes. They are staged near the factory building, end-of-line areas, and covered transport trailers, with some already lined up for shipment.
The scale and consistency of the installation point to factory tooling rather than retrofit work.
A secondary detail noted in related sightings is a darker tone to the Starlink cover compared with earlier lighter panels. Tegtmeyer himself left open whether the darker finish is deliberate. There are a variety of explanations for it: perhaps for thermal performance, signal characteristics, or simple visual identification—or simply a batch variation still being refined.
Either way, the overall effect is a more integrated, production-ready appearance. For a Robotaxi that relies on Starlink for fleet connectivity, passenger services, and backup data links in areas with weak cellular coverage, the cleaner hatch design is more than cosmetic.
It signals that Tesla is polishing the final visual and hardware details as Cybercab volumes continue to climb at Giga Texas ahead of broader Robotaxi deployment. The vehicles now look to be built with Starlink instead of it being added afterward.
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.
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.
Introducing Powercore Solid state medium voltage transformer, inverter and breaker – reliable, safe and secure 7.4 MW/9 MVA continuously at 34.5 kVac w/ grid-forming support for 10MVA of peak power Made in America. Operating 2027 https://t.co/sHxqnpWJrf — Tesla Megapack (@Tesla_Megapack) November 17, 2026
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.