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

News

Tesla crosses major Unsupervised Self-Driving milestone

Published

on

Credit: Tesla

Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.

Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.

The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.

In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.

Credit: Tesla

Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.

The company has not released a city-by-city breakdown of the one million unsupervised miles.

The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.

Advertisement
-

Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.

The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.

Credit: Tesla

Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.

The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.

Continue Reading

News

Tesla Robotaxi will be a 24/7 service: here’s when

Published

on

Credit: @AdanGuajardo/X

Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.

The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.

That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.

Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.

Advertisement
-

Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.

By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.

Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.

Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.

If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.

That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.

Advertisement
-
Continue Reading

News

Tesla Full Self-Driving will now overtake manual driving to avoid disaster

Published

on

Credit: Tesla

Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.

Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.

Advertisement
-

The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.

The intervention is meant as a last-resort safety net, not a replacement for attentive driving.

Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.

After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.

The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.

Advertisement
-

Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.

The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.

If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.

Continue Reading