News
Tesla Model S firetruck crash in California: What we know so far
All eyes are on Tesla once more, after a Model S traveling at highway speeds crashed into a parked fire truck in Culver City, California earlier this week. The collision, which allegedly happened while the car was on Autopilot, has incited renewed debates, criticisms, and an upcoming government probe on Tesla and its evolving driving-assist software.
As more details about the accident emerge, here is a brief discussion on the latest and most pertinent information relating to the recent Model S collision.
The accident
As we stated in a previous report, the Tesla Model S was traveling at 65 mph on Interstate 405 on Monday morning when it crashed into a stationary fire truck. The emergency vehicle was parked on the road after being deployed to a separate accident in the area.
The driver of the electric car was able to walk away unharmed from the accident. Upon being questioned by the authorities, the Model S driver stated that the vehicle was on Autopilot when it collided with the parked fire truck. Tesla released a brief statement on Monday, stating that Autopilot is intended only to be used by an attentive driver.
More details emerge
As the online forum community continued to debate about the benefits and risks of Tesla’s Autopilot software, a member of the r/TeslaMotors subreddit who claimed to know the driver of the crashed Model S spoke up and provided some details about the accident. According to the Redditor, the Model S was traveling behind a pickup truck with Autopilot engaged. Due to the truck’s size, the Tesla’s driver was unable to see beyond the vehicle in front.
“The driver of the Tesla is my dad’s friend. He said that he was behind a pickup truck with AP engaged. The pickup truck suddenly swerved into the right lane because of the firetruck parked ahead. Because the pickup truck was too high to see over, he didn’t have enough time to react.” notes mikhpat.
Tesla Model S crashes into a stationary firetruck [Credit: Culver City Fire Department via Twitter]
Tesla’s Autopilot system allegedly did not have enough time to react while driving at 65 mph. The driver stated that the Model S’ emergency braking system might have activated moments before the car hit the emergency vehicle, but he could not be certain, according to mikhpat‘s statement.
“As for the 65mph detail, the braking system could’ve intervened before the collision, but there’s no way he could tell.”
The impact was strong enough to push the steering wheel two feet into the cabin, however. The Model S driver had some minor cuts and bruises from the accident but was otherwise unharmed. According to the Redditor, the driver admits that he was at fault for not paying close attention to the road. The Model S owner also refused to blame Tesla for the accident.
While it’s still unconfirmed if Tesla’s Autopilot suite, including Traffic-Aware Cruise Control and Autosteer, was activated at the time of the accident, Tesla’s Model S Owner’s Manual warns of a similar scenario that would not be detected by the driving-assist system.
According to the About Drive Assistance section of the owner’s manual:
“Traffic-Aware Cruise Control cannot detect all objects and may not brake/decelerate for stationary vehicles, especially in situations when you are driving over 50 mph (80 km/h) and a vehicle you are following moves out of your driving path and a stationary vehicle or object is in front of you instead.”
The warning appears to mimic the exact situation being described by Redditor mikhpat.
The investigations begin
As the online forum community exploded amidst heated debates on who is to blame for the recent Model S collision, the US National Transportation Safety Board announced that it is sending two of its investigators to California to study the crash. According to the NTSB, the investigators will be examining both “driver and vehicle” factors in Monday’s accident.
By Tuesday, the National Highway Traffic Safety Administration announced that it is also sending a team of investigators to California to evaluate the recent accident, as well as to assess any “lessons learned” from the crash, as noted in a Bloomberg report. The NHTSA did not specify which team of investigators it was sending to California, but expectations are high that the regulating body would be deploying its Special Crash Investigations unit.
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
