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.
Electric vehicle maker Lucid Group has denied rumors of an imminent bankruptcy after a report from this morning sent the stock on a dramatic drop on Wall Street, seeing losses of more than 40 percent during trading hours.
Lucid’s Director of Communications, Nick Twork, responded to the report from Eletric-Vehicles.com, which stated the company’s restructuring advisor, AlixPartners, was asked to review two decisions: taking Lucid shares private or filing for Chapter 11 bankruptcy protection.
The report also claims AlixPartners told the Lucid board to “concentrate on Gravity production while improving its quality, and to temporarily hold back the Lucid Air, the sedan that has defined the company since its launch.”
Twork said:
$LCID The rumors are completely false. The company has sufficient liquidity to carry its operations well into next year, as recently published in its last quarterly filings, and it has not formed any special Board committee to explore the scenarios reported today. Our focus is…
— Nick Twork (@ntwork) July 14, 2026
Shares rebounded after the response to the report, halving its losses as the trading day neared 3 p.m. Eastern.
Lucid has struggled to get its sales off the ground and into more respectable numbers, but the company is in its early years, when things are hard to begin with. It is also backed by several notable investors, including the Saudi Public Investment Fund (PIF), which has nearly limitless money and likely would not ditch an investment of this size so soon.
Lucid shares were down just 14 percent at the time of publication, a far cry from the 55 percent its losses topped out at during the day.
A Tesla owner who purchased a Model S Signature Edition, one of the final 250 units of the all-electric flagship vehicle that the company discontinued earlier this year, is attempting to sell the car despite a no-resale clause that prohibits reselling for the first year.
The car is being sold by J&S Autohaus in Ewing, New Jersey, and is priced at $260,490, well above the $159,420 that Tesla sold it for earlier this year.
🚨 The first Tesla Model S Signature Edition is up for sale for $260,490
Tesla placed a no-resale clause on the Model S and X Signature, so it will be interesting to see if the company takes any action. https://t.co/N9rKGHnbD6 pic.twitter.com/6FZhDL1KNR
— TESLARATI (@Teslarati) July 14, 2026
To those who do not know, the Model S Signature was a highly exclusive, limited-run farewell variant of the Model S Plaid that was produced this year to mark the end of production of both the Model S and Model X, Tesla’s two flagship vehicles.
Limited to just 250 units with invite-only sales, it serves as a collector’s item celebrating the legacy of the Model S, which helped pioneer Tesla’s electric vehicle success since its 2012 launch.
It bundles top-tier performance with bespoke cosmetic and luxury upgrades, plus Tesla’s Luxe Package. Here’s what the Model S Signature has over the typical Model S Plaid:
- Exclusive Exterior – Unique Garnet Red Paint, matching door handles, gold Tesla “T” badges upfront, gold Plaid and Signature badging at the rear.
- Premium Interior – White Alcantara upholstery with gold piping/accents, gold Plaid seat badges, Signature-marked door sills, individually numbered dashboard plaque, gold puddle lights, special interior lighting sequence, and a custom Signature key fob.
- Performance Upgrades – Carbon-ceramic brakes with gold calipers
- Bundled Luxe Package – Full Self-Driving (Supervised), four years of Premium Connectivity, free lifetime Supercharging
- Performance Metrics – ~1,020 horsepower, sub-2-second 0-60 MPH, ~390-mile range
Tesla quickly introduced a No Resale Agreement for the Signature Editions of the Model S and Model X, which would penalize the seller for “the amount of $50,000 or the value received as consideration for the sale or transfer, whichever is greater.”
The company continues:
“If you sell or otherwise transfer the ownership of your Model S or Model X, the remainder of the Recommended Maintenance, Wheel and Tire Protection Plan, and Windshield Protection Plan will transfer automatically to the buyer. The Full Self-Driving (Supervised), Free Supercharging and Premium Connectivity will not transfer with the vehicle and will terminate once the ownership of the Model S or Model X is transferred.”
Tesla will likely come after the seller, especially as it has been about two months since Tesla launched deliveries.
Tesla rolled out Full Self-Driving (Supervised) v14.3.5 yesterday, and about fifty miles of driving on the new version has given me enough time to highlight what seems to be strong about the release and what is not.
Additionally, Tesla has added a few new features with this specific update, which we’ll highlight as well.
Tesla Full Self-Driving v14.3.5 Performance
The new update is business as usual. Things seem to be running completely normal and necessary, but there are a few things that we’ve seemed to pick up on based on our own experience with v14.3.5, as well as what other users are seeing.
Initially, it seems to be more aware of its surroundings, making moves that are incredibly courteous to other drives and operating just a tad more reserved than what the suite might have done previously.
We had two instances where it showed this, the first being FSD needing to pass a Flagger Force vehicle that was placing down signage for the day. Their work truck was right at the front corner of a right-hand turn; typically where most cars travel when they take that turn.
FSD v14.3.5 recognized this, slowed down, and took the turn wide with no issues:
🚨 Tesla Full Self-Driving v14.3.5 takes a wide turn as flagger crews set up signage for the day https://t.co/3v0PL9qhlI pic.twitter.com/i4CKqxE16c
— TESLARATI (@Teslarati) July 13, 2026
Additionally, v14.3.5 backed up for a semi truck that was making a wide turn onto a road my car was on. This is not new, but it seemed to be backing up for courtesy; it didn’t seem completely necessary, but it might have put some peace of mind in the truck driver’s head:
🚨 Tesla Full Self-Driving v14.3.5 backs up for an oncoming tractor trailer taking a wide turn https://t.co/0WuAqNMpRR pic.twitter.com/s6yZGVm5Te
— TESLARATI (@Teslarati) July 13, 2026
X user Mike P, also a Pennsylvania native like myself, shared three clips of his Tesla running v14.3.5 performing similar maneuvers. He said:
“FSD turns right into a small alley that only fits one car at a time, sees oncoming car, reverses out of alley to make space, realizes oncoming car is actually parking, re-enters alley.”
Check it out here:
Rapidfire epic moments on FSD V14.3.5
1) FSD turns right into a small alley that only fits one car at a time, sees oncoming car, reverses out of alley to make space, realizes oncoming car is actually parking, re-enters alley.
2) Insane speed to vehicle cues. As FSD approaches… pic.twitter.com/bSnySSlFHR
— Mike P (@mikepat711) July 13, 2026
It seems like Speed Profiles are still in need of some tweaking; I am adjusting what Speed Profile I’m in frequently, constantly changing it to get it to travel at the correct speed. This was an issue for me on v14.3.4. It seems like they’re just a little inconsistent.
Terrible Parking
Parking attempts on v14.3.5 were not good. There are quite a few people who have said this:
Yeah it seems like FSD v14.3.5 is having some issues with parking early on https://t.co/Bw5ULfVmDq pic.twitter.com/RHdpjOEpIo
— TESLARATI (@Teslarati) July 13, 2026
David Moss, the Tesla owner who has taken multiple coast-to-coast drives without any interventions, also has had some issues with parking early on with v14.3.5:
Horrible first impression v14.3.5 on my 2025 Tesla Model 3 LR RWD Premium 😭
3 terrible parking jobs in 23 min including parking on a ramp in a business park & parking perpendicular out in the road on street only parking situation.
Wish I had a better drive but I still believe… pic.twitter.com/TtyhRHAFG7
— David Moss (@DavidMoss) July 13, 2026
New Features
Tesla has added the ability to open Camera Preview at any time. Previously, it was only available in Park. Here’s what that feature looks like in action:
🚨 Here’s the new Camera Preview feature on FSD v14.3.5 pic.twitter.com/OodfZgDppy
— TESLARATI (@Teslarati) July 13, 2026
Check back later this week for a longer review of what we’ve noticed on Full Self-Driving v14.3.5.
Lucid denies rumors of bankruptcy after over 40% stock drop
Tesla owner attempts resale of Model S Signature Edition for over $260k
