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 entered two new markets this week by advancing its presence in Latvia (Europe) and officially launching operations in Uruguay (South America), marking a rapid dual-continent expansion.
These moves underscore the company’s strategy to tap into emerging EV markets with supportive policies, renewable energy grids, and growing demand for sustainable transport.
Latvia: Strengthening the Baltic Footprint
In Latvia, Tesla has built on its earlier registration of Tesla Latvia SIA in late 2025 with recent steps toward full operations, including job postings for a service center and representation in Riga. This aligns with broader Baltic expansion following Lithuania’s model of pop-up stores and service centers.
Coming to Latvia https://t.co/XNkQQJ2O6a pic.twitter.com/yS9kpcNky1
— Tesla Europe, Middle East & Africa (@teslaeurope) July 17, 2026
EV penetration in Latvia stands at around 7 percent for BEVs in new passenger car registrations. 2025 data showed 1,602 BEVs out of about 22,500 total, or 7.1 percent, with combined plug-ins nearing 19 percent. Growth has been steady but below the European average, supported by government subsidies and infrastructure development. Tesla models like the Model 3 lead local EV registrations.
Vehicles for the Latvian market will likely be sourced from Gigafactory Berlin or Gigafactory Shanghai. Charging infrastructure is robust for the region as well, with over 400- 2,000 public points, with Tesla Superchargers in Riga, Jūrmala, and along Via Baltica routes offering up to 250 kW.
Uruguay: Third South American Country
Tesla teased its Uruguay arrival with “Estamos llegando,” or, “We are arriving,” on social media, followed by an official presentation scheduled for mid-July.
Hola Uruguay 🇺🇾
Nuestros Model 3 y Model Y están cada vez mas cerca! pic.twitter.com/FR41fsA7um
— Tesla Latinoamérica (@Tesla_LatAm) June 30, 2026
The company established Tesla Uruguay SAS, homologated Model 3 and Model Y (three versions each), and appointed local leadership. This makes Uruguay Tesla’s third official South American market after Chile and Colombia.
Uruguay boasts one of Latin America’s highest EV penetrations, with battery-electric vehicles exceeding 20 percent market share recently, driven by tax incentives, high fuel prices, and a nearly 95-100 percent renewable electricity grid. Hundreds of Teslas already operate via grey imports, but official sales bring warranties, service, and support.
Vehicles will be imported from Gigafactory Shanghai, enabling competitive pricing for Model 3 and Model Y. Charging plans include Supercharger development alongside existing infrastructure, leveraging the country’s green energy advantage for affordable operation.
Tesla Superchargers follow Model 3 and Model Y to South American country
Tesla’s Dual Continent Expansion
Tesla’s simultaneous push into Latvia and Uruguay demonstrates efficient scaling: prioritizing service and infrastructure first, then direct sales in high-potential niches. In Europe, it fills Baltic gaps; in Latin America, it counters Chinese dominance while leveraging renewables.
This dual move signals Tesla’s ambition to accelerate global EV adoption amid varying regional paces. By addressing local needs, like subsidies in Latvia or incentives and green grids in Uruguay, Tesla not only boosts volumes but advances its mission of sustainable energy.
For investors and consumers, it highlights resilience and opportunity in diverse markets, potentially paving the way for further growth in underserved regions. With strong fundamentals in both, these entries could yield long-term gains as EV transitions mature worldwide.
SpaceX has announced a new target date for the thirteenth test flight of Starship: Monday, July 20, with the launch window opening at 6:45 p.m ET/5:45 p.m. CT.
This is the first rescheduling attempt of Starship’s 13th test flight. It was set to launch last night, but SpaceX scrubbed the launch attempt.
🚨 SpaceX is now looking at Monday, July 20th at 6:45 p.m ET/5:45 p.m. CT for the 13th test flight of Starship pic.twitter.com/7s8aMJV5Ge
— TESLARATI (@Teslarati) July 17, 2026
CEO Elon Musk revealed that some of the engines on Starship did not start, which automatically triggers a launch abort. Two of the Raptor engines will be removed and replaced.
To be confident of a good flight, 2 Raptors will be removed & replaced. Most probable launch timing is early next week.
— Elon Musk (@elonmusk) July 17, 2026
SpaceX officially announced the new launch window this morning.
Starship’s 13th test launch comes with a few new objectives, but SpaceX does not plan to attempt a catch of the booster, which it has done several times in the past.
For Starship’s Upper Stage, there are some adjustments to ensure engine reusability that will be assessed during the ascent, and 20 operational Starlink V3 satellites are also set to make their way into space. SpaceX also plans to attempt an in-space relight of a single Raptor engine, which is a critical demonstration for future orbital deorbit, refueling, and deep space maneuvers.
Ultimately, it will splash down in the Indian Ocean.
The continuous tests help SpaceX advance the Starship program toward eventual full reusability, operational Starlink V3 deployment, and future missions, which include NASA’s Artemis program.
Elon Musk
SpaceX Starship Flight 13 aborted at Zero and Musk just told us what broke
Four Raptor engines failed to ignite at T-zero, forcing SpaceX to scrub Starship Flight 13 Thursday.
SpaceX scrubbed the Starship Flight 13 launch attempt Thursday evening at the last possible moment, after four of the Super Heavy booster’s 33 Raptor 3 engines failed to ignite during the startup sequence. The 90-minute window had opened at 6:45 p.m. EDT from Starbase in Boca Chica, Texas, and the countdown had proceeded without issue all day, with more than 11.5 million pounds of liquid methane and liquid oxygen being fully loaded into the rocket before the automated abort triggered. SpaceX’s launch directors posted on X, “Standing down from today’s flight test attempt,” and shut down the livestream shortly after.
Musk confirmed the root cause within hours. “Some of the engines didn’t start, triggering an automatic launch abort,” he wrote on X. “To be confident of a good flight, 2 Raptors will be removed and replaced. Most probable launch timing is early next week.” SpaceX engineers began draining propellant tanks immediately and Booster 20 was rolled back to its hangar for inspection.
The timing adds a layer of significance that did not exist during any of the previous 12 Starship flights. This is the first time SpaceX has attempted to launch Starship since the company made its stock market debut in June, listing under ticker SPCX at $135 per share. Public investors are now watching every Starship outcome in real time, and a last-second abort carries more visibility than it would have six months ago.
Flight 13 was designed to be one of the most consequential tests in the program’s history. It was set to carry 20 Starlink V3 satellites, the first operational payload Starship has ever attempted to deploy. Six of those satellites carried external cameras to photograph Starship’s heat shield from the outside during flight, which would act as a self-inspection approach SpaceX has never attempted before. The mission also needed to complete a Raptor engine relight in space, a step SpaceX skipped on Flight 12 in May after losing an engine during ascent. That Flight 12 booster also flipped 90 degrees off course during its boostback burn when five engines failed to reignite.
SpaceX has not announced an official next launch date. Musk’s “early next week” window points to July 21 or 22 at the earliest, pending the engine swap and a return to the pad.
Tesla enters two new markets on two different continents in one week
SpaceX announces new Starship 13 test flight target date
