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 Full Self-Driving is now the centerpiece of the company’s newly revised Referral Program, which launched on October 29.
Instead of referring people to purchase vehicles and the referrer receiving $250 in Tesla Credit, the new program now incentivizes Full Self-Driving subscriptions.
If a Tesla owner is on an FSD trial and uses a referral code to subscribe to Full Self-Driving, the person whose Referral Link was used will receive one month of FSD (Supervised). Their code can be utilized 12 times per year, with January 1 marking the reset date.
Realistically, this means that if your Referral Code is used by 12 Tesla owners on an FSD trial, you will receive a full year of FSD for free.
🚨 Here is Tesla’s new Referral Program for Full Self-Driving (Supervised):
When someone subscribes to FSD using your link, you’ll get a month free. Up to a year of FSD is available to you for free!
If you’d like to use my link: https://t.co/g00IX9OCE3 https://t.co/GFBzEO2jjS
— TESLARATI (@Teslarati) October 30, 2026
The previous program made it pretty difficult to get referrals; buying a vehicle is obviously a much larger financial strain than subscribing to Full Self-Driving for a month.
Of course, the previous Referral Program also offered a tangible benefit: $250 in credits you could use on Service, Supercharging, or anything in the Tesla Shop. It truly could pay for someone’s travel for a year. It recently bought me a new backpack and a T-shirt.
However, this new program is much more attainable for those who do not have a massive online presence of a slew of friends in the Tesla community who will use the code and max out subscriptions for vehicle purchases.
Woke up to maxed out Referrals! Thank you guys, that’s awesome!
Share your referral link below so others can use it! https://t.co/kesbwTcoTV
— TESLARATI (@Teslarati) October 30, 2026
The Full Self-Driving suite will now be the keystone of the Referral Program, which makes it more inclusive and more fun for everyone with an awesome benefit.
It also gives the impression that Tesla is truly focused on FSD subscriptions, something that saw a tremendous increase in volume in Q3, as 75 percent of deliveries for the quarter came with an FSD subscription attached.
Full Self-Driving data is so instrumental to the suite’s improvement that this kind of program benefits Tesla as much as it does the consumer.
Elon Musk
Tesla made napping in a Robotaxi easier with its latest update
Tesla’s quiet mode reaches Model Y Robotaxis, blacking out the screen for riders wanting rest.
Tesla’s quiet mode, the setting that blacks out the screen for riders who want to rest, has moved beyond the Cybercab. A video posted Thursday by Spencer (@scotsrule08) shows the feature running in a Model Y Robotaxi on a night ride that appears to be in Dallas.
New quiet mode now on @Robotaxi https://t.co/2cM2eM9NeN — Spencer (@scotsrule08) October 29, 2026
The rider taps a small crescent moon icon in the bottom right corner of the map screen. The map, media player, app shortcuts and Grok prompt disappear, leaving a dark display with “Arriving soon,” the destination and a line reading “Tap display to exit quiet mode.” Controls a passenger may still need, including Pull Over, cabin temperature, volume and Support, stay visible. One tap anywhere brings the full map back.
Quiet mode first showed up in the Cybercab last week, which Teslarati reported alongside a new rear camera view. Tesla has been trimming cabin noise in other ways too. On October 25, Spencer reported that Robotaxi turn signals now chime for the first four blinks and then go silent. Tesla has not published release notes for either change.
Elon Musk has been pitching this use for more than a decade. In October 2014, he said that “maybe five or six years from now I think we’ll be able to achieve true autonomous driving where you could literally get in the car, go to sleep and wake up at your destination,”
By 2017 he was setting a higher bar. Speaking at TED, Musk said the hard part was not making self-driving work 99.9 percent of the time, “because, like, if a car crashes one in a thousand times, then you’re probably still not going to be comfortable falling asleep. You shouldn’t be, certainly.”
Owners asked for something similar in their own cars. In December 2019, a Tesla owner requested a Nap Mode that would keep the climate running and wake the occupant with an alarm, and Musk answered “Ok,” as Teslarati covered at the time.
The line returned when the Cybercab was unveiled at the We, Robot event in October 2024. “We’ll move from supervised Full Self-Driving to unsupervised Full Self-Driving, where you can fall asleep and wake up at your destination,” Musk said. On Tesla’s first quarter earnings call in April 2025, he called it the deciding measure: “The acid test is, can you go to sleep in your car and wake up in your destination and I’m confident that will be available in many cities in the US by the end of this year,”
Tesla has run driverless Model Y rides in Dallas and Houston since April, so a passenger dozing off on the way home is now a realistic use of the button. Tesla is also offering new riders a free first trip in both cities, according to an in-app screen shared by tracker Ethan McKanna, and said on its third quarter call that Cybercab rides would launch in Dallas next month.
News
FCC green lights SpaceX’s move to a showdown with Verizon and AT&T
The FCC advanced plans opening 482 MHz to satellite phone service, boosting SpaceX’s Starlink Mobile.
The Federal Communications Commission voted Thursday to move forward with a proposal that would open an additional 482 MHz of spectrum to satellite service beamed directly to ordinary phones, a step that could widen the road for SpaceX’s Starlink Mobile to compete with the country’s largest wireless carriers.
The commission adopted the notice of proposed rulemaking at its October open meeting in Washington, Reuters reported. The proposal would raise the number of bands eligible for Supplemental Coverage from Space from five to 13, according to the FCC fact sheet. Commissioners also advanced a companion item proposing an auction of 25 MHz in the 1675 to 1695 MHz and 2020 to 2025 MHz bands, which could be used for terrestrial service, direct to device service or both.
Thursday’s vote does not hand any spectrum to SpaceX. It opens a public comment period, and final rules will come later. Under the draft, comments would be due 60 days after the notice is published in the Federal Register. The FCC had not released the adopted text at the time of writing, so it is not yet clear whether any bands were changed before the vote.
That question is where the fight now moves. AT&T, Verizon and T-Mobile, through industry group CTIA, asked the FCC to drop the 2.5 GHz and 3.45 GHz bands, which make up 290 MHz of the 482 MHz on the table, as Teslarati reported ahead of the vote. T-Mobile argued satellite interference could wipe out up to 96% of a cell site’s uplink coverage area. SpaceX asked the commission to go the other way and add the 902 to 928 MHz band.
The rule change that matters most to SpaceX may be a structural one. Today, a satellite operator must lease spectrum from every carrier holding co-channel licenses across an entire region such as the contiguous United States. The proposal would replace that with a certification that the operator has coexistence agreements covering only the areas it plans to serve, or that it holds the terrestrial licenses itself.
SpaceX has spent this year building that second path. It bought EchoStar’s AWS-4 and H-block licenses in a deal worth roughly $17 billion, and earlier this month agreed to acquire Grain Management’s nationwide 800 MHz portfolio, which the company said would pave the way for Starlink to become a major US mobile carrier. The FCC approved SpaceX’s purchase of three unused AWS-3 licenses from Tristar on October 21, and cleared its plan for 15,000 next generation direct to cell satellites on October 6.
The regulator has not always sided with SpaceX. In April, the FCC dismissed a SpaceX petition seeking access to Mobile Satellite Service spectrum held by incumbents, and it rejected 2.5 GHz for satellite coverage when it first adopted the framework in 2024.
The carriers are also building their own defenses. In May, the three companies agreed in principle to form a joint venture pooling spectrum for satellite service, and T-Mobile remains SpaceX’s US launch partner for Starlink Mobile even as it leads the push to keep satellites out of 2.5 GHz. SpaceX President Gwynne Shotwell has said service on SpaceX’s own airwaves is targeted for early 2028.
Tesla Full Self-Driving becomes main pillar of new Referral Program
Tesla made napping in a Robotaxi easier with its latest update
