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.
Elon Musk
Elon Musk handed Grok something no other AI company can get their hands on
Elon Musk says SpaceX will feed engineering data into Grok’s next model, avoiding restricted material.
Elon Musk said Tuesday that SpaceX will feed its internal engineering data into the next major training run for Grok, the AI model now folded into SpaceX following February’s merger. In a post on X, Musk wrote that SpaceX’s “massive corpus of world-class engineering data,” excluding anything restricted under U.S. arms export law, will be added during supplemental training of what he called the “2T run,” a reference to a roughly two trillion parameter model that would nearly double the parameters behind the latest Grok 4.5 that’s rolling out.
SpaceX’s massive corpus of world-class engineering data (excluding material blocked by ITAR) will be added during supplemental training of the 2T run.
This will dramatically improve Grok’s engineering capabilities. https://t.co/BbQEViFByn
— Elon Musk (@elonmusk) July 21, 2026
The excluded material that Musk is referring to would fall under the International Traffic in Arms Regulations (ITAR), which restricts export of technical data tied to defense and space hardware. That likely rules out propulsion specifics for Merlin and Raptor engines along with guidance and control details for SpaceX’s launch vehicles, but leaves manufacturing knowledge, materials science, and Starlink hardware design on the table.
The announcement extends a pattern that has been building since SpaceX’s Nasdaq debut in June, when the company went public with Grok and xAI’s Colossus supercomputer folded into the pitch to investors.
Days after that listing, SpaceX closed its $60 billion all stock acquisition of coding startup Cursor, giving xAI both enterprise software distribution and a stream of real world developer data to train on. Grok 4.5 launched July 8 running partly on that Cursor training data, with Musk describing it as roughly comparable to Anthropic’s Opus 4.7 but faster and cheaper to run.
Feeding SpaceX’s own engineering data into the next AI model follows the same logic Musk has applied across xAI’s sister companies. Tesla supplies real world driving data and manufacturing expertise, X supplies conversational data, and now SpaceX supplies aerospace engineering data built up since 2002.
Musk did not give a release date for the upcoming AI model, referred to elsewhere as Grok 4.6. He has said the two trillion parameter run is in its final training phase and expected to wrap this week.
Tesla has extended its Bay Area ride-hailing service to include pickups and drop-offs at San Francisco International Airport (SFO). The update, shared via the company’s official channels on July 21, allows users in the region to request rides directly to and from one of California’s busiest airports.
The expansion builds on Tesla’s secured limousine permit for SFO operations. Public records show the permit became effective March 20, 2026, and remains active through January 31, 2027. Tesla vehicles operating the service now display authorized limousine permits issued by the City and County of San Francisco.
Our Bay Area rideshare service now goes to SFO ✈️
— Tesla AI (@Tesla_AI) July 21, 2026
Tesla’s ride-hailing program in California relies on Model Y vehicles equipped with Full Self-Driving (Supervised) technology. Human safety drivers remain present in compliance with state regulations, distinguishing the service from fully driverless operations.
The Bay Area geofence covers a broad area spanning north of San Francisco to south of San Jose, offering extensive connectivity across the region.
UPDATE: Elon Musk reveals why Tesla didn’t say ‘Robotaxi’ upon California launch
This SFO addition follows earlier progress at other Bay Area airports. Tesla previously expanded service to San Jose Mineta International Airport (SJC) in late 2025. The company had engaged with SFO, SJC, and Oakland International Airport officials as early as September 2025 to secure necessary approvals for passenger transport.
The service provides a new option for travelers seeking electric, app-based transportation integrated with Tesla’s ecosystem. Rides are booked through Tesla’s dedicated ride-hailing application, which handles matching, routing, and payments. Pricing follows standard ride-hailing models, with potential adjustments based on distance, time, and demand.
Tesla’s California ride-hailing program launched in July 2025 with an initial invite-only rollout in the Bay Area. It started alongside operations in Austin, Texas, marking the company’s second major U.S. market.
The Bay Area remains a primary focus in California, with service centered on high-demand corridors connecting residential, commercial, and now major transportation hubs. This latest airport integration represents a practical step in Tesla’s broader mobility ambitions within the state.
Tesla has officially revealed its 2026 Summer Update, which comes with a variety of crazy new features, including Navigation fixes that owners have been wanting for months.
Tesla routinely releases a larger update with the Spring, Summer, Fall, and Winter updates, where it ships a variety of new features, bug fixes, and other additions to customer cars.
The 2026 Spring Update featured things like “Hey Grok” voice assistance, a redesigned self-driving app, Unreal Engine visual upgrades, and more.
🚨 TESLA’S SUMMER UPDATE FOR 2026 IS HERE:
Featuring:
✅ Self-Driving Stats in Mobile App
✅ Caraoke with Scoring
✅ Automatic Navigation
✅ Preferred Routes
✅ Set Arrival Energy from Mobile App
✅ Send Custom Wraps from Mobile App
✅ Rear Display Lock
✅ Other Improvements
🔌… https://t.co/C9IW3egEhH— TESLARATI (@Teslarati) July 21, 2026
Tesla’s Summer Release has about ten new features; we’ll show you each and detail them below:
New Grok Voice Commands
“Grok can now make phone calls, search and play music, adjust climate, open the glovebox, and answer questions about your Tesla.”
Self-Driving Stats in Mobile App
“View and share self-driving stats from the mobile app.”
Caraoke With Scoring
“Caraoke now scores your singing while in Park. High scores are saved to your Tesla profile.”
Automatic Navigation
“Automatic Navigation now adapts to your routine.
In addition to Home, Work, and upcoming calendar events, your vehicle can now suggest and route to places you visit regularly – like a school drop-off on the way to work, or the gym on the way home.”
Preferred Routes
“For a more personalized experience, navigation now prioritizes routes that you’ve taken before”
Set Arrival Energy from Mobile App
“Set your desired Arrival Energy from your phone.”
Send Custom Wraps from Mobile App
“Skip the USB drive and upload a custom wrap of your car from the mobile app. Instructions for creating a custom wrap here: https://github.com/teslamotors/custom-wraps.”
Rear Display Lock
“Kids can watch content on the rear screen, but only the front row can control it through the rear screen app.”
Other Improvements
- Find Superchargers by name when searching for a destination
- Add Apple Music songs to queue from search and artist page
- Set your preferred zoom level for the Self-Driving visualization
- Intro animations for new Model 3 and Y
Elon Musk handed Grok something no other AI company can get their hands on
Tesla expands ridesharing service in California to new hotspot
