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.
NASA has filed a procurement notice announcing its intent to add six post-certification missions to SpaceX’s existing Commercial Crew Transportation Capability contract. The agency said it would order up to three of those missions immediately upon adding them to the contract, with the remaining three available as needed through the end of the International Space Station’s planned operations in 2030.
The reason for the expansion is straightforward. NASA cited recently shortened ISS mission durations, technical issues and schedule delays encountered by Boeing, the allocation of missions between Boeing and SpaceX, and the ongoing technical challenges of maintaining a reliable crew transportation capability as the driving factors behind the decision. Boeing’s CST-100 Starliner has still not been certified for crewed flights, and a cargo-only Starliner mission was not included on NASA’s most recent mission manifest. With Boeing effectively sidelined for the foreseeable future, SpaceX is the only American company capable of rotating crews to the station.
The history behind this contract tells the fuller story of how SpaceX got here. NASA originally awarded SpaceX its Commercial Crew contract in 2014 for $2.6 billion. In 2022 NASA modified the contract to add five missions covering Crew-10 through Crew-14, worth $1.436 billion, bringing the total contract value at that point to $4.9 billion. The recent May 18 filing by NASA extends that runway further, with Crew-12 currently docked at the station and Crew-13 assigned and targeting a mid-September 2026 launch.
According to a report by SpaceNews, NASA stated in its filing: “It is necessary to award additional PCMs to SpaceX given the recently shortened ISS mission durations, technical issues and schedule delays encountered by Boeing, the allocation of missions between Boeing and SpaceX, NASA’s projections for when an alternative crew transportation system may become available, and the ongoing technical challenges of maintaining a reliable capability for crewed flights to ISS.”
No dollar value for the new six missions has been publicly confirmed yet, but based on the 2022 precedent of roughly $287 million per mission, the new block could represent close to $1.7 billion in additional contract value. With SpaceX simultaneously preparing Starship as NASA’s Artemis lunar lander, filing its S-1 for a June IPO, and now absorbing more ISS crew rotation work, the company’s role as the primary contractor for American human spaceflight is no longer a matter of circumstance. It is NASA policy.
In a notable intersection of Big Tech powerhouses, Meta, led by Mark Zuckerberg, has partnered with Canadian energy infrastructure giant Enbridge on a significant renewable energy initiative that will rely on battery technology from Elon Musk’s Tesla.
The project, which was announced this week, marks another step in Meta’s aggressive push to power its expanding data center operations with clean energy, dispelling many of the complaints people have about them.
This new development is located near Cheyenne, Wyoming, and will feature a 365-megawatt (MW) solar farm paired with a 200 MW/1,600 megawatt-hour (MWh) battery energy storage system, also known as BESS. Tesla is providing the batteries for the project, valued at roughly $200 million.
The story was originally reported by Utility Dive.
This Wyoming project represents the first phase of Enbridge and Meta’s joint “Cowboy Project.” Once operational, it will deliver power to Meta’s regional data centers through Cheyenne Light, Fuel, and Power under Wyoming’s Large Power Contract Service tariff.
This tariff, originally developed in collaboration with Microsoft and Black Hills Energy, is designed specifically for large loads like data centers. It ensures that the renewable supply serves hyperscale customers without impacting retail electricity rates for other users.
The battery system will operate under a long-term tolling agreement, providing dispatchable capacity that enhances grid reliability. During periods of high demand, the utility can access the backup generation, addressing one of the key challenges of integrating large-scale renewables with the explosive growth of data center electricity demand driven by artificial intelligence.
This latest collaboration builds on prior joint efforts between Enbridge and Meta in Texas, including the 600 MW Clear Fork Solar, 152 MW Easter Wind, and 300 MW Cone Wind projects. Together with the Wyoming initiative, the companies have now partnered on roughly 1.6 gigawatts (GW) of combined solar, wind, and storage capacity.
The deal highlights the intensifying demand for reliable, low-carbon power from technology giants. Meta has committed to supporting its data center growth with renewable energy, joining peers like Microsoft and Google in seeking large-scale solutions. Enbridge’s Allen Capps described the project as “one of the larger utility-scale battery installations supporting U.S. data center operations and growth.”
The involvement of Tesla’s battery technology adds an intriguing layer, linking two of the world’s most prominent tech leaders—Zuckerberg and Musk—in the clean energy transition.
As data centers continue to drive unprecedented electricity load growth across the United States, projects like this one illustrate how hyperscalers are turning to strategic partnerships with traditional energy players and innovative storage solutions to meet both sustainability goals and reliability needs.
SpaceX has decided to stand down from what was supposed to be the first test launch of Starship’s v3 rocket tonight after a minor issue with a hydraulic pin delayed the flight once more.
The company scrubbed its first test flight of the upgraded Starship v3 on May 21 in the final minutes of the countdown. SpaceX CEO Elon Musk quickly took to social media platform X, explaining that a hydraulic pin on the launch tower’s “chopsticks” arm failed to retract properly.
Musk added that the company would fix the issue this evening. SpaceX will attempt another launch tomorrow night at 5:30 p.m. CT, 6:30 p.m. ET, and 3:30 p.m. PT.
The hydraulic pin holding the tower arm in place did not retract.
If that can be fixed tonight, there will be another launch attempt tomorrow at 5:30 CT. https://t.co/DJAdvDYQpH
— Elon Musk (@elonmusk) May 21, 2026
The countdown for Starship Flight 12 — featuring the taller and more capable V3 stack with Booster 19 and Ship 39 — had been progressing smoothly until the late-stage issue surfaced. The Mechazilla tower arm, designed to secure the vehicle on the pad and eventually catch returning boosters, could not complete its retraction sequence.
SpaceX teams immediately began troubleshooting the hydraulic system for an overnight repair.
Starship V3 introduces several significant upgrades over earlier versions. These include greater propellant capacity, more powerful Raptor 3 engines, larger grid fins, enhanced heat shielding, and an improved fuel transfer system.
We covered the changes that were announced just days ago by SpaceX:
SpaceX unveils sweeping Starship V3 upgrades ahead of May 19 launch
The changes are intended to increase payload performance, support higher flight rates, and advance the vehicle toward operational missions, including Starlink deployments, NASA Artemis lunar landings, and future crewed Mars flights. The debut flight from Starbase’s new Launch Pad 2 marked an important milestone in scaling up the fully reusable Starship system.
This stand-down highlights the intricate challenges of preparing the world’s most powerful rocket for flight. Despite extensive pre-launch checks, a single component in the ground support equipment can force a scrub.
The incident aligns with Starship’s proven iterative development approach. Previous test flights have encountered both successes and setbacks, each providing critical data that refines hardware and procedures. Some outlets may call some of these flights “failures,” when in reality, they are all opportunities for SpaceX to learn for the next attempt.
With V3, SpaceX aims to reduce ground-system dependencies and increase launch cadence to meet ambitious long-term goals.
NASA just gave SpaceX more crew missions because Boeing can’t certify
Elon Musk called it Epic: The full story of SpaceX’s Starship Flight 12
