Connect with us

News

NTSB Prelim Report on fatal Tesla Model X crash: 8-seconds before impact

Published

8 years ago

on

The National Transportation Safety Board has issued a preliminary report on the tragic Tesla Model X crash near Mountain View, CA in March. The NTSB’s preliminary report provided details about the circumstances leading up the accident, as well as observations about the all-electric SUV’s battery pack five days after the crash.

According to the NTSB, preliminary recorded data revealed that the Tesla Model X had its Autopilot engaged with Traffic-Aware Cruise Control set to 75 mph at the time of the accident. The vehicle collided into the crash attenuator, rotating it counterclockwise, removing the front part of the vehicle, and causing subsequent collisions with a 2010 Mazda 3 and a 2017 Audi A4. The NTSB noted that the vehicle’s performance data revealed the following.

The aftermath of the Tesla Model X’s fatal crash. [Credit: S. Engleman/NTSB]

  • Autopilot was engaged on four separate occasions during the 32-minute trip. The driver-assist feature was engaged for the last 18 minutes 55 seconds before the collision.
  • During the 18 minute, 55-second period, the Model X provided two visual and one auditory alert advising the driver to place his hands on the car’s steering wheel. The alerts were triggered more than 15 minutes prior to the accident.
  • For the last 6 seconds before the collision, the Model X’s driver did not have his hands on the steering wheel. 
  • At 8 seconds before the crash, the Model X was following a lead vehicle at about 65 mph. At 7 seconds, the Model X began moving left while still following a lead vehicle. At 4 seconds, the Tesla was no longer following a car. At 3 seconds before the accident, the Model X’s speed increased from 62 mph to 70.8 mph. The vehicle’s emergency braking and evasive steering did not engage.
  • During the collision sequence, the Model X’s lithium-ion battery was breached, causing a fire. The flames were extinguished after the Mountain View Fire Department applied about 200 gallons of water and foam during a period of fewer than 10 minutes. In the afternoon, the battery emanated smoke and audible venting was heard, though no flames were observed.
  • On March 28, 5 days after the accident, the Model X’s battery pack reignited. The San Mateo Fire Department extinguished the fire.

The NTSB noted in its preliminary report that it is continuing work with the California Highway Patrol and the California Department of Transportation in investigating the accident. The NTSB stated that all aspects of the crash remain under investigation, and that it intends to issue safety recommendations to prevent similar incidents from taking place.

Tesla and the NTSB initially worked together in investigating the fatal Model X accident. The electric car company and the safety board eventually parted ways, however, due to Tesla’s decision to release crash data before the NTSB’s investigation was complete. Among the information Tesla released was that the driver did not have his hands on the wheel during the final 6 seconds leading up to the accident — information that has been reiterated in the NTSB’s preliminary report. 

According to a Tesla, it opted to withdraw from its party agreement with the NTSB since collaboration with the safety board prevents the public release of safety information until the investigation was finished. People familiar with the matter, however, noted that the NTSB was the one which opted to terminate its collaboration with Tesla, according to a Bloomberg report.

In an update after the accident, Tesla highlighted that the absence of a crash attenuator — a highway safety device designed to absorb the impact of a collision — was already damaged when the Model X collided with the concrete barrier.  In a statement to ABC7 News, Wil Huang, the brother of the ill-fated Model X driver, noted that a working crash attenuator would have saved his brother’s life. Later statements from CalTrans revealed that safety device had been left unrepaired for 11 days before the tragic Model X accident.

Related Topics:

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 briefly offered this Robotaxi part for your personal car

Published

29 minutes ago

on

July 28, 2026

By

Credit: @tpgoebel | X

Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.

Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.

First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.

This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.

However, this part has since been removed and is no longer visible on the EPC.

Advertisement
-
-

Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?

While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.

AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.

This could be the first hint of that’s where we are headed.

Continue Reading

News

Tesla Robotaxi gets sweeping but polarizing change

Published

2 hours ago

on

July 28, 2026

By

Credit: Tesla

Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.

Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.

But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:

However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.

Advertisement
-
-

Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.

Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.

The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.

Continue Reading

News

Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

23 hours ago

on

July 27, 2026

By

Credit: Tesla

Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.

Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.

However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.

With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.

Turning Hesitancy, Inaccuracy

I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.

Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.

I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.

FSD Disregards Manual Turn Signals

This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.

If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.

FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.

This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.

Advertisement
-
-

This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.

Bird Braking is a Thing of the Past

The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.

There have been zero issues with this so far in v14.3.6, which is an excellent improvement.

FSD Might Already Be Taking Note of Driver Preferences

Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.

This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.

Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.

Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.

It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.

As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

Advertisement
-
-
Continue Reading