Connect with us

News

Tesla Model S firetruck crash in California: What we know so far

Published

on

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.

Advertisement
-

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.

Advertisement
-

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.

 

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

Elon Musk

Tesla may test customer-owned Robotaxis as early as next month, Musk says

Published

on

Credit: @AdanGuajardo/X

Elon Musk says that Tesla could test adding customer-owned vehicles to the Robotaxi platform as soon as December.

In a reply on X to an Austin-based Uber driver who uses a Model Y with Full Self-Driving and keeps only 49-63% of fares after the platform’s cut, Musk wrote:

“Coming soon. If things well, may start trials next month. Much better to manage a fleet of cars than have to drive just one car by yourself!”

Advertisement
-

The exchange highlights the appeal of passive income from an autonomous vehicle versus actively driving for rideshare platforms.

This potential December start is technically earlier than prior company guidance, but it also aligns with the currently-projected first delivery of the Tesla Cybercab, a vehicle that has no manual controls.

Nevertheless, Tesla planned to bring customer vehicles into the fleet later on. During Tesla’s Q3 earnings call, AI leadership had pointed to roughly the second quarter of 2027 for customer vehicles joining the network. Musk’s comment suggests an accelerated pilot, most likely beginning in Austin, where Tesla’s Robotaxi service has operated longest and where new features typically roll out first.

December is also the target month for the first customer deliveries of the Cybercab. In mid-November, Tesla began inviting select buyers to purchase the purpose-built, two-seat vehicle for personal use at $29,990 plus a required $299 monthly Autonomy Subscription, with estimated deliveries in Austin.

Tesla Cybercab goes on sale for $29,990, slated for December deliveries

Those initial private Cybercabs are restricted to personal use within existing Robotaxi zones and do not automatically include commercial network participation; the large majority of Cybercabs are expected to remain Tesla-owned fleet vehicles.

Advertisement
-

The coincidence of the two December milestones underscores Tesla’s parallel paths. Customer Model Ys already on the road with FSD hardware could rapidly enlarge the vehicle pool for unsupervised trials, while the Cybercab, which is void of a steering wheel or pedals and equipped with only dedicated Robotaxi hardware, arrives as a purpose-built platform.

Hardware differences, such as additional cameras or cleaning systems on company Robotaxis, may constrain which Model Ys are eligible at the outset. Regulatory approvals, insurance arrangements, and software readiness will also determine whether the “if things go well” condition is met.

For owners, successful trials would fulfill a vision Musk first sketched in Tesla’s 2016 Master Plan: vehicles that earn money while their owners sleep or work.

Combined with the arrival of privately owned Cybercabs in the same month, December could mark the transition from Tesla-controlled Robotaxi operations to a broader ecosystem in which both company fleets and customer vehicles contribute to the company’s autonomous ride-hailing platform, which continues expanding.

Continue Reading

Elon Musk

FAA turned down free Starlink offer before nationwide ground stop, Elon Musk says

Elon Musk says the FAA declined free Starlink terminals before last week’s nationwide ground stop.

Published

on

By

Elon Musk says the Federal Aviation Administration could have had Starlink backing up its air traffic communications for free, and he is pointing to last week’s nationwide ground stop as proof it was needed. “As I was saying … Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” Musk wrote on X Monday.

Musk was quoting his own post from February 2025, when he wrote that “the ancient system that is rapidly declining in capability was made L3Harris,” while a newer replacement system from Verizon was “not yet operational.” The Department of Transportation has not responded publicly to Musk’s account of the offer.

The outage behind the post began at about 3:30 p.m. ET on Friday, November 13. According to the FAA’s own account, its legacy equipment became unstable when data began flooding its FAA Telecommunications Infrastructure network at a rate of 1,000 connection attempts every four to five seconds. The agency traced the flood to two locations, a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas, where L3Harris had been installing a new router.

Instability spread across 17 of the FAA’s 22 Air Route Traffic Control Centers. The agency grounded departures nationwide while about 3,500 aircraft already in the air landed safely, and lifted the stop at 8:15 p.m. ET. Operators canceled roughly 12,462 flights that day, though the FAA notes not all of those were directly caused by the ground stop. L3Harris blocked the two sites to stabilize the network, and the FAA disabled the same router function on about 60 similar units. Officials found no sign of a cyberattack.

Transportation Secretary Sean Duffy has blamed prior administrations and dated systems, and has called on Congress to fund a $50 billion overhaul of the system.

Musk’s history with the FAA network goes back to early 2025, when he was leading the Department of Government Efficiency. He claimed on X that the system was failing and putting air travelers at risk, initially blaming Verizon before correcting himself to name L3Harris. The FAA confirmed at the time it was testing Starlink terminals, one at its Atlantic City, New Jersey facility and two at “non-safety critical sites” in Alaska. SpaceX said it was providing the kits at no cost and had no intent to take over any existing FAA contract.

Advertisement
-

Duffy described Starlink then as “part of a solution” rather than a replacement. By July 2025, the FAA told lawmakers it was not considering replacing its L3Harris and Verizon telecommunications contracts with Starlink.

Whether Starlink would have prevented Friday’s disruption is not clear. The FAA described a fault inside its terrestrial network rather than a loss of connectivity, and Musk did not explain how satellite links would have been used. His post does put SpaceX back in the conversation as Washington debates how to pay for the next air traffic control system. SpaceX already supplies Starlink to commercial airlines for inflight connectivity, and United’s rollout required FAA certification for each aircraft type.

Continue Reading

News

Tesla makes $3.3 billion Cybercab bet at Giga Berlin

Published

on

Credit: Tesla

It is no secret Tesla is prioritizing Cybercab production as it plans to launch a fleet of fully autonomous vehicles without steering wheels or pedals across the world. Today, it made a €3 billion bet to do so in Europe.

Tesla announced on November 16, that it will invest €3 billion (approximately $3.3 billion) to expand its Gigafactory in Grünheide near Berlin, its only vehicle manufacturing site in Europe.

The investment will fund a major new production building—roughly twice the size of the existing main hall—and supporting infrastructure, including an additional wastewater treatment plant. The new facility is designed to produce up to one million Cybercabs annually once fully scaled, alongside continued Model Y output.

Advertisement
-

Tesla plans to file the building permit application before the end of 2026, according to Tagesspiegel, drawing on a broader expansion application submitted in 2023 that targets one million vehicles per year overall. Construction is scheduled to begin in the first half of 2027, with Cybercab production starting in 2029.

The company is already recruiting several hundred workers for construction and production planning. The site currently employs about 12,600 people after recent hiring of roughly 2,000, and it is ramping Model Y production toward 7,500 vehicles per week (around 375,000 annually).

This vehicle expansion comes just days after plant manager André Thierig indicated at the Automobilwoche Congress on November 11 that full battery cell production at Grünheide is on track for mid-2027.

The factory already produces electrodes, which are currently shipped to Texas for cell assembly and returned; the goal is to complete 4680-format cells on site using Tesla’s dry-electrode process, targeting up to 18 GWh annually.

The cumulative investment in the cell operation approaches €1 billion and is expected to create more than 1,500 jobs. Once operational, Giga Berlin would become the first plant in Europe to produce everything from battery cells to finished vehicles under one roof, raising the European content of its Model Ys to roughly 90 percent.

For Tesla’s German operations, the twin moves deepen vertical integration and reduce dependence on transatlantic and Chinese supply chains.

Advertisement
-

They also contrast sharply with the broader German automotive industry, which faces high costs, weak demand, and job cuts; Brandenburg officials have welcomed the investment as a significant economic boost that creates hundreds of new positions and strengthens the region as a manufacturing hub.

Tesla’s expansion advances its strategic pivot toward autonomy and robotaxis. The Cybercab is intended to become a high-volume product; adding major European capacity diversifies production beyond the United States and supports Elon Musk’s vision of autonomous vehicles comprising the majority of Tesla’s future output.

Combined with localized 4680 cell production, the plans position Giga Berlin as a more self-sufficient, technologically advanced European base, enhancing competitiveness as regulatory and market conditions favor higher local content.

Continue Reading