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
Tesla expands Robotaxi in a way that was long anticipated
Instead, it has to do with the consumer base it offers Robotaxi to, because it has not offered it to everyone in the past.
Tesla has expanded Robotaxi in a way that was long anticipated, and it does not have to do with a new, larger geofence in a city where it already offered its partially autonomous ride-hailing suite, or a new city altogether.
Instead, it has to do with the consumer base it offers Robotaxi to, because it has not offered it to everyone in the past.
Tesla has taken a major step forward in its autonomous ride-hailing ambitions with the official launch of the Tesla Robotaxi app for Android users. Released on the Google Play Store on April 24. Titled simply “Tesla Robotaxi,” the app is now available to download directly from Tesla.
The @Tesla Robtoaxi App has just officially launched for Android users. Go get some rides y’all!
Download: https://t.co/D2jIONXc91 pic.twitter.com/rQ6TD14zkC
— Sawyer Merritt (@SawyerMerritt) April 24, 2026
This rollout fulfills a long-anticipated expansion that opens the service to hundreds of millions of Android smartphone users who were previously unable to access it on iOS alone.
The app delivers a streamlined, driverless ride experience powered by Tesla’s automated driving technology.
Users sign in with a Tesla Account, view the current service area map within the app, enter a destination, and receive an estimated fare and arrival time before confirming the ride. When a Model Y from the Robotaxi fleet arrives, riders confirm the license plate, enter the vehicle, fasten their seatbelt, and tap “Start Ride” on either the app or the vehicle’s touchscreen.
During the trip, passengers have access to all the same controls that iOS users do, and can adjust climate settings, seat positions, and music while tracking progress on an in-app map. The interface also allows drop-off changes or support requests if needed. After the ride, users exit, close the doors, and submit feedback.
This Android availability directly broadens the rider base for Robotaxi in its initial service areas. Unfortunately, Android users are used to being subject to delayed launches of new features available to Tesla owners.
By removing the iOS-only barrier, Tesla instantly expands the addressable market, enabling far more people to summon and use the autonomous vehicles already operating on public roads.
The move is a foundational requirement for scaling ride volume and gathering the real-world data needed to refine the unsupervised Full Self-Driving system that powers every trip.
For the Robotaxi program itself, the launch signals steady operational progress. It prepares the service for higher utilization rates as the fleet grows and supports the transition from limited early deployments to a more robust network.
Tesla expands Unsupervised Robotaxi service to two new cities
Tesla has indicated that users outside current service areas can sign up at the company’s website for future notifications, pointing to a deliberate, phased geographic rollout.
Looking ahead, the company plans to incorporate Cybercab vehicles to increase fleet capacity and efficiency while continuing to expand service territories. With the Android app now live, Tesla has removed a key adoption hurdle and positioned Robotaxi for the next phase of growth in autonomous urban transportation.
The infrastructure is now in place to support significantly larger rider demand as production and deployment accelerate.
News
UPDATE: SpaceX’s Falcon Heavy that launched a Tesla into space is back on a mission
SpaceX Falcon Heavy returns after 18 months away to deliver a satellite that only it could carry.
UPDATE: 10:29 a.m. et: SpaceX is standing down from today’s Falcon Heavy launch of the ViaSat-3 F3 mission due to unfavorable weather. A new target date will be shared once confirmed.
After an 18-month absence, SpaceX’s Falcon Heavy is returning to mission on Monday morning when it’s scheduled to lift off from Launch Complex 39A at Kennedy Space Center at 10:21 a.m. EDT.
The mission is called ViaSat-3 F3, and the heavy satellite payload needs to reach geostationary orbit, sitting 22,236 miles above Earth where its speed matches the planet’s rotation. Getting a satellite that heavy to that altitude demands more thrust than a single-core Falcon 9 can deliver.
This marks the Falcon Heavy’s 12th flight overall since its debut in February 2018, and its first since NASA’s Europa Clipper mission in October 2024.
Arguably, the most exciting element for spectators will be watching the booster recoveries in action when the two side boosters, B1072 and B1075, will attempt simultaneous landings at Landing Zone 2 and the newer Landing Zone 40 at Cape Canaveral Space Force Station, while the center core will be expended over the ocean.
SpaceX wins its first MARS contract but it comes with a catch
Following satellite deployment, expected roughly five hours after launch, ViaSat-3 F3 will spend several months traveling to its final orbital slot before undergoing in-orbit testing, with service entry expected by late summer 2026
As Teslarati reported, NASA awarded SpaceX a $175.7 million contract on April 16, 2026, to launch the ESA Rosalind Franklin Mars rover aboard a Falcon Heavy no earlier than late 2028, which would mark the first time SpaceX has ever sent a payload to Mars. That contract came on top of an already deep pipeline that includes the Roman Space Telescope, the Dragonfly Saturn mission, and multiple national security payloads.
SpaceX executed 165 missions in 2025 and now accounts for approximately 85% of all global orbital launches. With Starlink surpassing 10 million subscribers and an IPO targeting a $1.75 trillion valuation still ahead, Monday’s launch is one more data point in a company that has quietly become the backbone of both commercial and government space access worldwide.
Tesla is launching its solution to end Supercharger fights once and for all, eliminating any confusion on who is to charge next at a congested location.
Last year, a notable incident at a Tesla Supercharger led to a fight, and it all stemmed from a disagreement over who arrived at the location first.
Congestion at Tesla Superchargers is a pretty infrequent occurrence for most of us, but there are more congested and popular areas where wait times can be extensive. An unfortunate growing pain of EV ownership is the plain fact that chargers are not as available as gas pumps, and there are, at times, lines to charge.
This can cause tensions to flare and people to get entitled when visiting Superchargers. Nobody wants to spend hours at a Supercharger, but now, there will be no more confusion when there is a queue, and that’s thanks to Tesla’s new Virtual Queue for Superchargers.
Tesla is finally starting to build out the Virtual Supercharger Queue, according to Not a Tesla App, but it still relies on drivers to make it work.
When a driver is near a Supercharger that is full, a message will pop up on the Tesla App, using the driver’s location to determine their eligibility to join the virtual queue.
The app states:
“While the app is closed, Tesla uses your location to notify you of accurate wait times at Superchargers when you arrive.”
Another message within the app states:
“There is a waitlist to charge. Are you sure you want to start a charging session now?”
This sounds as if it will require drivers to act appropriately and only plug in when the app prompts them to do so, by letting them know it is their turn.
The app will notify the driver of their position in the queue, as well as how many vehicles are ahead of them.
Tesla launches first ‘true’ East Coast V4 Supercharger: here’s what that means
The company announced a while back that it would be working on a solution for this issue. Personally, I’ve only had to wait at a Supercharger for a charge on one occasion, and there was a line of between 3 and 10 cars during this singular occurrence.
I’m out at the Lancaster, PA Supercharger and showed up with a queue of three vehicles.
It’s now up to five and there have been several issues with order of arrival and confusion about who is first.
Any update on Supercharger queue? @elonmusk @aelluswamy @r_jegaa
— TESLARATI (@Teslarati) January 31, 2026
There were no conflicts or arguments about who had arrived first, but there was some discussion between several drivers during my time there about who was to charge first. Throw a non-Tesla EV into the mix, one that can only charge at a pull-in spot, and that causes even more of a complication.
Tesla expands Robotaxi in a way that was long anticipated
UPDATE: SpaceX’s Falcon Heavy that launched a Tesla into space is back on a mission
