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.
News
SpaceX just locked up a NASA record no other U.S. spacecraft can touch
SpaceX’s Crew-13 Dragon reached the ISS in under eight hours, and NASA confirmed a record.
SpaceX now owns every spot on the list of the five fastest trips a U.S. spacecraft has ever made to the International Space Station, and its newest entry beat the old mark by more than four hours.
Crew Dragon Grace docked to the forward port of the station’s Harmony module at 7:05 p.m. ET on October 1, just 7 hours and 55 minutes after lifting off from Space Launch Complex 40 at Cape Canaveral. NASA confirmed the milestone in a space station blog update, writing that the flight “marked the fastest launch‑to‑docking of a U.S. spacecraft in the history of the International Space Station.”
The previous U.S. record also belonged to Dragon. SpaceX’s uncrewed CRS-31 cargo mission reached the station in a little over 12 hours in November 2024. The fastest crewed trip before last week was Crew-11, which took 14 hours and 43 minutes in August 2025, according to Space.com.
A post that Elon Musk reposted on Monday filled out the rest of the ranking. Behind Crew-13, CRS-31 and Crew-11 sit Axiom’s Ax-2 mission at 15 hours and 35 minutes and NASA’s Crew-4 at 15 hours and 44 minutes. All five flew on Dragon.
SpaceX turned a heralding moment for Starship into its greatest
Crew-13 carried NASA astronauts Jessica Watkins and Luke Delaney, Canadian Space Agency astronaut Joshua Kutryk, and Roscosmos cosmonaut Sergey Teteryatnikov. NASA had projected a docking around 8 p.m. ET, as Teslarati reported the day before launch, and Dragon arrived nearly an hour early. Our launch day coverage noted that the flight was lined up to be the quickest Crew Dragon transit yet.
The speed came from timing more than hardware. SpaceX’s Julianna Scheiman said the station “was in an opportune spot in space,” which let Dragon start closing the gap almost immediately after reaching orbit. “This is close to the fastest it could be,” she added. Most Crew Dragon flights still take close to a day, using a series of Draco thruster burns to raise and phase their orbit before arrival.
Dragon’s next job at the station is a departure. NASA said Monday it is targeting 8:05 a.m. ET on Wednesday, October 7, for Crew-12 to undock, setting up a splashdown off the coast of California around 11:34 a.m. on Thursday. Clearing that port makes room for CRS-35, a cargo Dragon carrying the final set of iROSA solar arrays.
Dragon remains NASA’s only operational ride to the station while Boeing’s Starliner stays grounded, and the agency recently added Crew-15, Crew-16 and Crew-17 to SpaceX’s contract in a $946 million modification.
Elon Musk
Elon Musk teases TSMC as potential Terafab partner
Elon Musk has acknowledged that early discussions with Taiwan Semiconductor Manufacturing Company (TSMC) could bring the company into his ambitious Terafab semiconductor project, signaling a possible partnership with the world’s leading contract chipmaker.
Musk confirmed that early talks are underway, but as of right now, they are “just discussions.” There is no confirmation of a deal nor dismissal of the possibility of one, leaving open the prospect of one of the largest advanced-chip collaborations under discussion in the U.S.
@wholemars Just discussions, but something may come of it
— Elon Musk (@elonmusk) October 3, 2026
The report that speculated on potential discussions between Terafab and TSMC comes from Tim Culpan, who outlined a few ways the collaboration could operate. One is TSMC using the project as an “anchor customer” for future facilities in Texas, potentially contributing process expertise, operational know-how, or capacity while Terafab provides capital, long-term purchase commitments, or both.
Tesla and SpaceX jointly developed the Terafab project, with Intel already participating on the tech side. Elon Musk announced the project in March, and it intends to produce more than one terawatt of AI compute capacity annually once fully built.
Company statements place the first phase at approximately $16.8 billion in cost, with later filings pointing to a total that could reach well into the tens of billions across multiple stages.
Intel joined the effort in April 2026 and is expected to supply its 14A manufacturing process for the full-scale plant.
Musk has said existing suppliers, including Samsung and TSMC, remain important for near-term needs; Tesla already has production arrangements with Samsung for AI5 and AI6 chips, but that future demand from Optimus robots, Cybercab vehicles, and planned space-based data centers will eventually exceed what the global industry can currently deliver.
Terafab is positioned as the long-term answer to that projected shortfall, and Tesla did something similar during COVID to avoid a chip shortage. This is just a much larger-scale solution.
If the partnership were to materialize, it would add TSMC’s industry-leading strategies to a project that already combines Tesla’s and SpaceX’s capital and offtake with Intel’s process technology. For now, the only public confirmation is Musk’s brief acknowledgement that conversations are occurring.
News
Tesla reveals early Robotaxi charging strategy, showing scrappy DNA
Tesla’s early strategy for charging units operating within its Robotaxi fleet reveals that the company surely has not lost any of that scrappy DNA that took it from an unlikely success story to the most valuable carmaker in the world.
An observer at a Tesla Supercharger in Austin spotted ten total Robotaxi vehicles arrive: one Cybercab and nine Model Y units. A Tesla employee was waiting at the lot and allowed each unit to park itself; every car that arrived had nobody in it.
Tesla wins FCC approval for wireless Cybercab charging system
The Tesla employee would walk around and plug each car in, adjusting the parking if needed:
So look at what I found. This is how Tesla charges unsupervised robotaxis at a public supercharger. Here is a driverless Cybercab showing up with no one in it. There are 9 other Model Ys that showed up too. A Tesla employee is walking around and plugging each of them in. She also moves the cars if they are not positioned well enough to charge. I love this process. One person charges multiple robotaxis at once
— Abhimanyu Yadav (@WorldlyReviewer) October 3, 2026
It’s a very interesting strategy, but extremely understandable at this early point in the Robotaxi program. It’s only been out for about 15 months, and Cybercab just entered the fleet in early September.
On top of that, Tesla is still working tirelessly on its wireless charging apparatus, and a new patent was just published regarding that product last week.
However, this is just another example of how Tesla still has plenty of that scrappy DNA leftover from the “production hell” days, when CEO Elon Musk slept on the floor of the factory, employees were working crazy hours, Tesla was building Sprung Structures to build cars in, and the company was tiptoeing on the brink of bankruptcy.
@Teslarati Sheer magnitude of the entire production system is hard to appreciate. Almost every element of production is >75% automated. Only wire harnesses & general assembly, which are <10% of production costs, are primarily manual.
— Elon Musk (@elonmusk) October 12, 2020
For now, Tesla is utilizing a simple system for recharging its ride-hailing vehicles, and that is a Tesla employee doing it manually until another solution presents itself. Sure, it’s not the most high-tech thing, and it certainly is not what people might have expected at this point in time, but it works, and it’s keeping the entire suite running.