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.
Lifestyle
Tesla teases “Halloween Mode” update with Optimus rising from a graveyard
Tesla’s Halloween teaser hides a covered vehicle and an Optimus hand rising from the ground.
Tesla has started teasing a Halloween software update for its vehicles, with a short clip on X that reads, “Halloween is coming.” The clip opens on a glowing pumpkin before pulling back to the car’s center touchscreen, where the usual parked visualization has been replaced by a graveyard scene, and the vehicle draped with a white sheet so it reads as a cartoon ghost.
Halloween is coming pic.twitter.com/lM3ASUeOqX
— Tesla (@Tesla) October 1, 2026
The second detail is a robotic hand clawing its way out of the dirt like a zombie, which looks to be the hand of Tesla’s latest Optimus V3 humanoid robot. While Tesla still has not formally shown Optimus Gen 3 walking around in service, renders pulled from Tesla’s Android app last month gave the clearest look yet, including far more refined hands that Tesla has said carry 22 degrees of freedom. The hand has been the hardest part of the program. Musk has called it the majority of the robot’s engineering difficulty, and Tesla’s patents describe a design driven by tendons with the actuators moved into the forearm.
Tesla Optimus V3 hand and arm details revealed in new patents
Optimus also has a Halloween track record. Last October the robot handed out candy in Times Square, and a costumed “zombie” Optimus shuffled around the Tesla Diner in Los Angeles on Halloween night.
On the software side, Tesla’s 2025 Holiday Update expanded Santa Mode with a Santa sleigh, snowmen, snow effects, and a festive lock chime, so it wouldn’t be too far fetched if we saw something similar but themed for a Halloween Mode.
Tesla Full Self-Driving is set to receive improvements to address its two biggest issues, according to a company engineer.
Director of Engineering at Tesla AI, Phil Duan, revealed in a post on X that improvements to both pothole avoidance and navigation “are coming,’ something we have heard many times in the past. However, there are a few things that seem to hint that things might be different this time around.
Improvements on both are coming.
— Phil Duan (@pduan) October 1, 2026
Pothole avoidance, navigation, speed control, and left lane camping are some of the most prevalent and frequently mentioned shortcomings of the Full Self-Driving suite. These are a few of the biggest issues that have kept Tesla Full Self-Driving as a Supervised suite, meaning drivers must remain attentive during operation.
Pothole Avoidance
Pothole avoidance was first mentioned as an “Upcoming Improvement” with the Tesla Full Self-Driving v14.3 update back in early April of this year. It was listed alongside “Expand reasoning to all behaviors beyond destination handling.”
It’s been six months since we first saw pothole avoidance explicitly mentioned, and it has not moved beyond that and joined the main release notes yet.
Tesla has not shed any light on why pothole avoidance has been such an issue for it to solve, but it also has issues identifying large bumps much of the time, so its modeling of sudden changes in road conditions is likely pretty weak at this particular point. I’ve had more issues with large bumps than potholes, personally, but both are issues that need to be resolved.
This is that big bounce that I mentioned in the quoted post.
It’s just a tad too drastic to take at the speed FSD wants to go over it. You can see me quickly swipe down into Sloth, but I intervened. https://t.co/K20PK9ysBg pic.twitter.com/81Oc82ZJcZ
— TESLARATI (@Teslarati) August 2, 2026
It makes sense that things might be pretty close to being released to the public, as we are going on such an extensive period of time between it being mentioned and it actually being deployed.
Navigation
Navigation is likely the most painful part of using Full Self-Driving, as it routinely takes strange routes, has trouble with local rules (like Except Right Turn Stop Signs in Pennsylvania), and sometimes does not realize that maneuvers it is suggesting are against the law. Turning out of my neighborhood, you cannot turn left, yet my Model Y still suggests it roughly 70 percent of the time when I’m leaving.
However, Tesla might be close to a breakthrough on this. With the Summer Update, Tesla added “Preferred Routes” alongside “Automatic Navigation.”
Preferred Routes prioritized roads that the driver had actually taken before, instead of always defaulting to what the vehicle believes is the most efficient path. This has already solved many of my issues. Formerly, I would turn off the Online Routing setting, and that would eliminate most of my complaints with routing, but then you lose out later on the Live Traffic Visualization.
Tesla’s Navigation has improved tremendously thanks to the Preferred Routes release with the Summer Update, but it still could use some polishing, as it still suggests strange routes from time to time, and it also has a lot of issues getting out of a parking lot. I find that those truly confuse FSD sometimes.
News
SpaceX’s midnight spy satellite launch quietly set a new record
Falcon Heavy launched its first NRO mission while SpaceX landed four boosters in one day.
SpaceX closed out one of its busiest days ever with a midnight Falcon Heavy launch from Florida, and the rocket’s two side boosters came home to finish off a landing record the company had never set before.
Falcon Heavy lifted off from Launch Complex 39A at NASA’s Kennedy Space Center at 11:54 p.m. ET Thursday carrying NROL-97, a classified payload for the National Reconnaissance Office. It was the first time the NRO has flown on Falcon Heavy after 22 missions on Falcon 9, and the first NRO mission bought through the National Security Space Launch Phase 3 Lane 2 contract awarded in 2025, according to Spaceflight Now.
Falcon Heavy lifts off from pad 39A in Florida for the 14th time! pic.twitter.com/uuZLKNTdD7
— SpaceX (@SpaceX) October 2, 2026
Roughly eight minutes after liftoff, side boosters B1104 and B1072 touched down at Landing Zones 1 and 2 at Cape Canaveral Space Force Station, setting off double sonic booms across Brevard County. B1104 was flying for the second time and B1072 for the fourth. Both last flew on August 30 on NASA’s Nancy Grace Roman Space Telescope, making NROL-97 the quickest turnaround between Falcon Heavy missions to date. The brand new center core, B1106, was expended in the Atlantic so the payload could reach its high energy orbit, and SpaceX’s mission page noted the fairing had previously flown on the NROL-95 mission in July.
The two landings capped a record for SpaceX. Earlier Thursday, Falcon 9 booster B1101 returned to Landing Zone 40 after sending the Crew-13 astronauts to the International Space Station, and another Falcon 9 launched the Transporter-18 rideshare with 130 payloads from Vandenberg Space Force Base in California. Spaceflight Now reported it was the first time SpaceX has landed four boosters in a single day, wrapping up the triple header Teslarati previewed on Wednesday.
Falcon Heavy’s side boosters land on LZ-1 and LZ-2 pic.twitter.com/dBPcNeggFx
— SpaceX (@SpaceX) October 2, 2026
The mission also brought Landing Zone 1 back for what may be its final landing. SpaceX first landed an orbital class booster there in December 2015, but its lease on the former Launch Complex 13 site ended in 2025 as the company moved Florida landings to new pads at its own launch complexes. With LZ-40 already holding the Crew-13 booster, SpaceX brought LZ-1 back into service for one more night. Launch tracker Next Spaceflight listed NROL-97 as the final expected landing at the site.
NROL-97 adds to a fast growing stack of national security work for SpaceX. The company has flown four Space Force missions from Vandenberg since mid August, several believed to carry Starshield satellites, pushing its Pentagon contract total for 2026 past $8 billion. Elon Musk was also named this week to help lead the Pentagon’s Project Meridian study on the future of warfare.
The Florida doubleheader stood out for another reason. The Space Coast saw only one launch in all of September as SpaceX shifts more of its East Coast infrastructure toward Starship, which reached orbit for the first time on Flight 14 just three days earlier.
Tesla teases “Halloween Mode” update with Optimus rising from a graveyard
Tesla says fixes on Full Self-Driving’s two biggest issues are on the way
