Looks to me like the driver realized the truck was going way to fast for the curve and tried to take control from the lane assist system but it was too late to avoid the accident. Four seconds before the crash the truck was traveling far too fast for that corner. This guy has 7 name changes as well.

We review cases like this all the time, and our entire career is spent managing and studying data from these vehicles through our platform (when either consented by vehicle owners or in de-identified form). Multiple test drives have been taken within the past 24 hours at this location on both the latest and older FSD lane assist stacks (including older than the one installed in this incident). In both cases, the vehicle traveled at a slower speed (35-49mph) than in the incident (54-68mph at the 4-second prior mark). This implies that the driver was pressing down on the accelerator, forcing the vehicle to accelerate faster than it would normally. This action does not deactivate lane assist/FSD, but the system treats it as a manual override (as it is). Given the speed of travel, the turn ahead and posted speed signs (and that the vehicle was traveling at 3-4x the posted speed), this all supports the narrative that the driver was not paying attention to the road and was potentially driving recklessly. If the vehicle was operating normally and at its own suggested speed, it would have likely handled the corner turn with ease, as has been tested on the same vehicle, as well as other models. All speculative, all an opinion of course.

@teslascope @GravityAnalyti1 Is it clear what version of FSD was installed?

Not trying to defend the idea that FSD is responsible for this crash (it isn't), but this statement below is very misleading: "In both cases, the vehicle traveled at a slower speed (35-49mph) than in the incident (54-68mph at the 4-second prior mark). This implies that the driver was pressing down on the accelerator, forcing the vehicle to accelerate faster than it would normally. This action does not deactivate lane assist/FSD, but the system treats it as a manual override (as it is)." No, it does not imply that. FSD drives at different speeds for me on the same roads even in the same speed profile! It's really random like there's some ghost variable impacting speed decisions.

@teslascope @GravityAnalyti1 What about the possibility that the vehicle thought it was on the highway next to it? This was on FSD 13.

@teslascope @GravityAnalyti1 Whaam Baam has shown stories before, holding down the accelerator around a curve can disengage FSD and it's counted as a manual disengagement.

@teslascope @GravityAnalyti1 Most objective reply i have seen so far

@teslascope @nafareall @GravityAnalyti1 I maintain the driver was turned around to tend to her child, accidentally used the accelerator to stretch herself to the child, and caused the car to accelerate, thus overriding FSD.

@teslascope @GravityAnalyti1 One has to assume that there is a reason only a 4 second clip has been released. If a 10 second clip incriminated FSD, that’s what would have been released. Lawers and the media both specialize in taking things out of context!

@teslascope @GravityAnalyti1 Ultimately, the proper reaction would be to run over the cones while breaking

@teslascope @GravityAnalyti1 In that state the vehicle even warns that when the user is holding the accelerator it will not brake.

@teslascope @GravityAnalyti1 Skill issue tbh

@teslascope @GravityAnalyti1 That is a very interesting observation