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
NHTSA just escalated its Tesla Cybercab investigation in a big way
NHTSA escalated its Cybercab audit into a sworn Special Order with a September 30 deadline.
Federal regulators have moved from asking Tesla questions about its Cybercab to demanding sworn answers. The National Highway Traffic Safety Administration issued a Special Order that requires a Tesla officer to sign an affidavit attesting to the completeness of the company’s responses, with a deadline of September 30.
The order builds on Audit Query AQ26002, which NHTSA opened on September 3, the same day Tesla began commercial Cybercab service in Austin. Teslarati covered that initial inquiry when it surfaced, noting the agency wanted to understand how Tesla certified a vehicle with no permanently attached steering wheel, pedals, or mirrors as compliant with Federal Motor Vehicle Safety Standards. A Special Order is a different tool and converts a fact finding review into a legally enforceable demand, the same mechanism NHTSA used against Tesla in 2023 during its Autopilot investigation.
Several of the 21 requests target a specific gap in Cybercab’s design. One asks whether Tesla used temporarily attached human controls at any point to help certify the vehicle, and if so, which standards depended on that equipment being present. Another quotes an existing rule directly: “The service brakes shall be activated by means of a foot control.” Cybercab has no foot pedal. NHTSA wants a detailed explanation of how the vehicle satisfies that requirement, and how it complies without the kind of exemption granted to Zoox in July under Part 555, the regulatory pathway built for steering wheel free vehicles.
The order does not claim Cybercab is unsafe or that Tesla broke a rule. It requires Tesla to explain, under oath, the reasoning behind decisions the company already made when it self-certified the vehicle. That distinction matters, but so does the exposure. Motor1’s reporting, summarized here, put potential civil penalty exposure as high as $139 million if NHTSA later finds the certification was flawed, on top of whatever criminal risk comes with a false sworn statement.
Tesla has not said publicly how it plans to respond. Cybercab is still carrying passengers in Austin through the Robotaxi app while the September 30 deadline approaches, and the company has continued expanding the vehicle’s footprint even as the regulatory question remains open. The Special Order does not pause any of that and just sets a date by which Tesla has to put its certification logic on the record, with a company officer’s name attached to it.
In a new interview on Wednesday, Tesla uber bull Ron Baron said that anyone looking to buy the company’s stock should do so as soon as they can.
Baron, founder and CEO of Baron Capital and one of Tesla’s most persistent institutional bulls, used a CNBC Squawk Box appearance on Wednesday to deliver a familiar message with fresh urgency: In his opinion, Tesla stock is a buy:
“The time to buy the stock is now. FSD is catching on, and it’s going to be bigger and bigger. 55% of new buyers are buying it (Teslas) with FSD. It’s going to be everywhere. It’s safer.”
The Baron Capital frontman’s case is built around Full Self-Driving. Tesla reported 1.48 million active FSD subscriptions in the second quarter, up 56 percent year over year, and company officials have said roughly 55 percent of new North American deliveries left with a subscription enabled.
Baron framed that attach rate as proof the product is moving from enthusiast extra to default expectation, and as a reason software, not just vehicle volume, should drive the next phase of value.
His conviction on Tesla shares is not theoretical, as Baron Capital made its first Tesla investment in 2014, after years of meetings that began around the 2010 IPO roadshow. The firm later built a large SpaceX position starting in 2017.
Ron Baron today in new interview on Tesla:
“The time to buy the stock is now. FSD is catching on, and it’s going to be bigger and bigger. 55% of new buyers are buying it (Teslas) with FSD. It’s going to be everywhere. It’s safer.” pic.twitter.com/Rv5PB0bVZ2
— Sawyer Merritt (@SawyerMerritt) September 16, 2026
Baron said those Musk-led bets have generated about $30 billion of the $71 billion in profits Baron Capital has produced for clients. He put the firm’s current exposure at roughly $25 billion in SpaceX and $5 billion in Tesla. Personally, he described SpaceX as his largest holding, at about $5 billion, with about $1.5 billion in Tesla and additional Tesla exposure through the firm’s funds.
That concentration is also a statement of loyalty. Asked about talk of a SpaceX-Tesla combination, Baron said he had already walked Elon Musk through arguments for and against a deal, then declined to repeat them on air. His public position was simpler: “Whatever you decide is better is what I’m going to support,” he said to Musk.
Baron also said that he picked up the farewell edition of the Model S after Tesla decided to sunset the vehicle earlier this year, calling it his favorite car he’s ever driven.
Elon Musk
SpaceX’s next Starship launch is about to attempt its biggest leap yet
SpaceX targets September 22 for Starship Flight 14, its first attempt to reach real orbit.
SpaceX has set September 22 as the target date for Starship’s 14th test flight, and this one carries a different goal than any of the 13 that came before it. Every previous Starship mission has intentionally flown a suborbital arc, reentering the atmosphere within the same hour it launched. Flight 14 is designed to send the craft into a genuine orbit around Earth for the first time.
The launch window opens at 7:15 a.m. Central time at Starbase in South Texas and runs for 75 minutes, pending regulatory approval, according to SpaceX’s mission description published Tuesday. If the flight goes as planned, Starship will circle the planet roughly six times at an altitude near 275 kilometers over about ten hours before a deorbit burn sends it toward a splashdown in the Pacific Ocean west of Chile, a departure from the Indian Ocean recoveries used on the last several flights.
The mission also marks the first attempt to put a working batch of Starlink V3 satellites into actual service. Flight 13 carried 20 of the new satellites in July, but because that mission never left a suborbital trajectory, the payload reentered along with the ship instead of separating into orbit.
SpaceX tells the FCC that Starship Flight 14 is going to orbit
Each V3 satellite is rated for roughly one terabit per second of downlink capacity, so a successful deployment on Flight 14 would be SpaceX’s largest single jump in network bandwidth since Starlink began flying on Falcon 9.
Flight 13 still did the heavier lifting on the technical side. That July mission flew a deliberately more stressful reentry profile to test Starship’s heat shield, and the ship survived its softest splashdown yet, intact enough for drone inspections shortly after landing. Elon Musk said the flight delivered “all the heat shield data we needed and then some,” a result Teslarati covered in detail when he later said SpaceX had solved the vehicle’s biggest reusability challenge. Flight 14 is where SpaceX starts spending that confidence on an actual orbital insertion rather than another controlled fall back to Earth.
One thing Flight 14 will not attempt is a tower catch of the ship. Musk floated the idea right after Flight 13, but walked the timeline back in August, saying a catch attempt was more likely “in a few months.” The Super Heavy booster will still aim for its own recovery, targeting an offshore landing point in the Gulf of America, the same approach used on recent flights.
September 22 is SpaceX’s own target, not a locked date. Starship’s schedule has slipped before over hardware readiness and FAA sign off, and the company has said as much in its own mission notes. But the plan itself represents the clearest marker yet that Starship is moving from a suborbital test program into something meant to carry paying payloads and, eventually, people.
NHTSA just escalated its Tesla Cybercab investigation in a big way
Tesla uber bull Ron Baron says ‘the time to buy the stock is now’
