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.
Tesla is set to launch Cybercab on Thursday at an event in Austin, Texas, which will officially bring the company’s first steering wheel-less and pedal-less vehicle to a limited number of consumers for the first time.
The event, which is invite-only, is still thin on details: we’ll be there, and it seems the event will be held at Gigafactory Texas, but the launch of this vehicle truly relies on it being operational outside of the factory and on public roads.
🚨 Close-Up look at Tesla Cybercab without steering wheel: pic.twitter.com/9TXCDeDCz7
— TESLARATI (@Teslarati) July 3, 2026
Nevertheless, there are some big things to expect, and other things to temper expectations on. For what it’s worth, we believe this event could be perhaps the biggest indication that Tesla is ready to truly enter a new phase and chapter in its historic story.
Tesla Cybercab’s First Foray into the Public with Real-World Riders
Cybercab will likely hit the streets of Austin and the surrounding areas, likely in the established geofence that Tesla has expanded on for the past 14 months. Just yesterday, Tesla expanded it once again by 9 percent.
Tesla will put, for the first time, a vehicle without any manual controls on public roads, likely without any help from teleoperators. This is a truly groundbreaking development if it comes through in this fashion: it would be groundbreaking for Tesla to roll out a truly driverless ride-hailing vehicle.
Cybercab Has Already Been Unveiled
This is not an unveiling event. Cybercab has been released for nearly two years, as Tesla first showed it to the public on October 10, 2024.
FIRST LOOK: Tesla ‘Cybercab’ Robotaxi makes its global debut
While there is some small speculation that Tesla could release the Roadster at the event as a surprise, it seems more likely the focus will be on the Cybercab and the huge accomplishment that will come with releasing a vehicle with no manual controls.
There Will Be a Lot of Hype
What’s important to remember about the Cybercab event is that Tesla will continue to prioritize safety and the rollout will likely be slow, just as it has been with Robotaxi.
One of the biggest complaints about Robotaxi is vehicle population, and the fact that the wait for a ride, at least in some instances, has been longer than most want to admit.
It will take time for this project to truly scale. It will take time for Tesla to roll this out in a large fashion. The important thing to note is that they are doing it, and they’re doing it with a vehicle that is completely engineered and built internally. That’s something no other ride-hailing service can say.
Elon Musk recently restated a fact that still defines SpaceX’s origin story: if Falcon 1’s fourth launch had failed, the company would not exist. The comment answered a reminder that after three consecutive losses, SpaceX had money for only one more attempt.
On X, Peter Diamandis said that the present-day acknowledgement of SpaceX’s success does not discount the rough start the company had. “Almost nobody remembers that Elon’s first rocket failed three times, and there was money for exactly only one more attempt.”
Musk said, “If the 4th launch had failed, SpaceX would not exist.”
If the 4th launch had failed, SpaceX would not exist
— Elon Musk (@elonmusk) August 30, 2026
In late 2008, the firm was nearly out of cash. Another failure would have ended payroll, closed the Hawthorne factory, and left the Falcon 9 and Dragon programs as unfinished drawings.
The first flight lifted off from Omelek Island on 24 March 2006. Thirty-three seconds later, a corroded aluminum fitting on a fuel line leaked. Kerosene ignited around the Merlin engine, control was lost, and the vehicle came apart. The small DARPA payload, FalconSAT-2, survived the short flight only to land on a storage shed near the pad. Investigators later traced the fitting to a materials mix-up that should never have reached the rocket.
Flight 2, on 21 March 2007, looked far better at first. The first stage burned cleanly and handed off to the Kestrel-powered upper stage. The vehicle crossed 100 kilometers and reached a peak of about 289 kilometers. Then propellant slosh in the second-stage tank started a circular coning motion that grew until the engine shut down. Telemetry faded as the stage tumbled, and SpaceX had reached space but not orbit. Over the next year, the team redesigned everything from the ground up, including tanks, baffles, and the new regeneratively cooled Merlin 1C.
That engine flew on Flight 3 on 2 August 2008. The first stage performed almost perfectly and reached 217 kilometers. After main-engine cutoff, leftover fuel in the cooling channels produced a faint residual thrust, roughly 10 pounds per square inch of chamber pressure. On a Texas test stand, the effect was invisible beneath ambient air pressure. In vacuum it was enough to push the spent first stage back into the second stage after separation. The stages collided, the upper stage spun, and the mission was lost. Musk later said a slightly longer delay before staging would have saved the flight.
Six weeks later, the team assembled Flight 4 from remaining parts and flew it on 28 September 2008 at 23:15 UTC. The payload was Ratsat, a 165-kilogram aluminum mass simulator built in-house. Staging was delayed so residual thrust could decay. The Kestrel ignited, the fairing split away, and nine and a half minutes after liftoff the vehicle was in orbit. After a coast, the second stage restarted, settling into a 621-by-643-kilometer path at 9.35 degrees inclination. Falcon 1 became the first privately developed liquid-fueled rocket to reach Earth orbit. Musk called the insertion “middle of the bull’s-eye.”
SpaceX restores a Falcon 1 rocket for 10th anniversary of first launch success
That success unlocked NASA’s Commercial Resupply Services award later that year. Without it, there would have been no Falcon 9, no reusable first stages, and no Dragon cargo or crew flights to the International Space Station. Launch prices would have remained far higher. Starlink’s constellation would not exist; broadband from low Earth orbit would still be a paper concept.
Ride-share markets, high launch cadence, and the current pace of lunar and Mars hardware would be years behind. Communications, Earth observation, and the cost of putting anything into space would look more like the 2000s than the 2020s.
One extra second of residual thrust in August 2008 would have written a different decade.
News
Tesla surges Robotaxi fleet ahead of Cybercab launch event
Tesla’s unsupervised robotaxi fleet quietly grew sevenfold in three weeks just before Cybercab Day arrives.
Tesla’s unsupervised Robotaxi fleet has grown far faster than the public numbers suggested, and the timing lines up with the company’s biggest autonomy showcase yet. According to data compiled by the crowdsourced Robotaxi Tracker, Tesla now has nearly 200 vehicles operating without a safety monitor across Austin, Dallas and Houston, yielding a roughly 7X increase in about three weeks.
The jump lands four days before this week’s Tesla Cybercab launch event in Austin, where the company plans to show off its purpose-built, two-seat robotaxi with no steering wheel or pedals in a live commercial setting for the first time. Stick with us on X and Facebook for live reporting from the event.
The strategic logic is straightforward. Tesla has spent the past year scaling Robotaxi in small, deliberate steps, first widening geofences, then extending operating hours, then quietly growing fleet size, usually with little advance notice. Ashok Elluswamy told investors on the Q2 earnings call that the program had logged more than 380,000 unsupervised miles with zero notable incidents, a safety record the company has leaned on to justify moving slowly. Critics have used the flip side of that caution, a fleet that appeared stuck around two dozen vehicles for months, as evidence that Tesla’s driverless ambitions were outrunning its actual deployment.
A fleet quietly scaling to nearly 200 vehicles right before Cybercab Day undercuts that argument without Tesla having to say anything about it directly. It also sets up the event to do double duty. Rather than simply introducing new hardware, Tesla can point to an operating base of unsupervised Model Ys already running at meaningful scale, then argue the Cybercab, which uses the same underlying Full Self-Driving stack according to earlier coverage of the fleet’s software upgrades, is a natural next steps. Tesla has separately been registering the two-seat Cybercabs with Texas regulators this week, with the count climbing from seven to 45 in a matter of days.
The two ramps, one in software-driven Model Y deployment and one in physical Cybercab registrations, are happening in parallel rather than in sequence. That suggests Tesla wants Thursday’s event to land as proof that the robotaxi business is already running at scale, not just a reveal of a new vehicle shape. Whether the unsupervised numbers hold up once Cybercabs start mixing into the same fleet is the detail worth watching once the event wraps.
Tesla Cybercab Event: what to expect from Austin
SpaceX would not exist if this crucial early launch failed, Musk says
