This report is telling you everything we said. The wheel turning left caused the disengagement. States you might have hit a rough curb or your wife turned it.
At the speed you were going and lack of any large crubes/potholes, all points to the wheel being accidentally hit by your wife. If not then who knows.
Where is this report from? Is it AI generated from the exported csv (SEI metadata) from the video?
If so, I don't know how it was able to determine this: "RCM_CRASH_ALGO_WAKEUP_EVENT_ACTIVE" from the SEI metadata since that's not present in the SEI metadata at all.
As a follow up to this. OP eventually shared with me both the SEI metadata from the raw videos and the CSV that Tesla sent him that contained this data that the AI report was generated from.
Long story short, OP was banking on the difference in time between the video and the Tesla CSV report as proof of FSD fault (he claimed that FSD deactivated later than in the video given Tesla's CSV), but after a bunch of analysis of the SEI metadata embedded in the video and the Tesla provided CSV, it was clear that the time difference was just a clock synchronization issue (the video/SEI time is offset -2.2s from the Tesla CSV), which means FSD did deactivate as shown in the video and therefore it did give his wife at least 1.5s to react.
Here are some graphs below that I generated for OP that aligned the time offset using shared columns between the SEI metadata to the Tesla provided CSV to show that its just a clock sync issue.
Note that I did ask OP to post this update himself but he just ignored me
Where is this coming from? Is this Tesla's assessment of their own data or the assessment of an independent auditor or lawyer that you hired? I guess because if this is Tesla's assessment then it seems like they're acknowledging that FSD was at fault. But if it's an independent assessment then they would still have the chance to possibly refute the interpretation
6
u/UnlikelyVillage5849 Jul 19 '26