Below is official crash footage of my dad being rear-ended while using FSD v12.6.4 on his HW3 Model 3 earlier this year. The telemetry overlay was created using the new crash visualization tools in
@CamCutApp v1.1.
Unfortunately, this experience completely destroyed his trust in FSD, and it’s going to be difficult to earn that trust back.
In this case, traffic ahead was slowing down normally. There was no sudden stop or hard braking. For reasons that aren’t entirely clear, FSD delayed braking until Automatic Emergency Braking (AEB) intervened and forced a much more aggressive stop. (Watch the autopilot status switch to “Aborting”) The driver behind failed to react in time and rear-ended my dad’s car.
One of my biggest concerns with FSD v12 on HW3 is that its reaction timing could occasionally be inconsistent, making these situations difficult to supervise. Everything can appear normal until the system reacts a second or two too late.
FSD v14 on AI4 has been a significant improvement, which is one of the main reasons I upgraded seven months ago. But i think it’s important not to forget that there are many people out there that are still using this outdated software and should be warned about its shortcomings.
To my knowledge, CamCut is the first commercially available tool that can combine Tesla crash footage, telemetry logs, and official crash report data into a synchronized visualization of the entire event.
The crash analysis tools are currently in beta. If you have Tesla crash footage you’d be willing to share to help improve the feature, I’d greatly appreciate it. Feel free to DM me.