Post

Chad Moran
Chad Moran@ChadMoran·
Here's the original video, which looks like it's actual speed. I used two markers and consistently measured it. It took 75 frames in a 30 FPS video to travel 212.63 ft equating to 57.9 MPH (probably 60). The incident occurred in August of 2025. These are just facts. Yes the driver should have intervened sooner. Yes, FSD was approaching way too fast.
Chad Moran tweet mediaChad Moran tweet mediaChad Moran tweet media
Chad Moran@ChadMoran

I normally don't bother armchair quarterbacking these situations. But watching the Tesla Stans come into the comments is funny. Elon said Autopilot (FSD?) was disengaged 4s before the impact which if you watch the video looks like it was going way too fast at that point. Am I missing something?

English
113
22
303
98.8K
Abhimanyu Yadav
Abhimanyu Yadav@WorldlyReviewer·
@ChadMoran @28delayslater Yep it’s too fast. But honestly FSD being on would have been better. I think it would have at least avoided a crash. Would have created a scary and embarrassing situation but would have avoided a crash at least. The driver just disengaged FSD and let thectruck crash lol
English
2
0
1
781
Kastro𓃵
Kastro𓃵@kastroPapiChulo·
@WorldlyReviewer @ChadMoran @28delayslater At the speed d vehicle was going, it seemed the system was thinking it was driving on the highway below. There is no way FSD woulda been going at that speed if it recognized the road it was on. This happens with normal GPS sometimes when one is driving through a flyover sometimes
English
1
0
1
10
Bagikan