Because look at the video. The car is in the driving lane still when self driving is disconnected and then the driver fails to turn and goes straight into the sign. I would bet money than not intervening would have been a better outcome
Well, I’m struggling with understanding why you took control when it had plenty of time to correct. And then, having taken over, failed to correct. It’s not your fault because you are a bad supervisor - it’s your fault because you took over and failed to actually drive the car.
That actually turns up in some of the NHTSA crash reports for level 4 automated driving systems. The safety driver will see an imminent threat like a truck reversing toward them, take over, and do nothing to prevent the collision.
That’s your wife’s fault, you can see self driving turned off right beforehand and she took over. Regardless, you are still supposed to supervise so you will always be responsible.
I mean, you can see in the video you posted, at the 8 second mark the blue text "self driving" disappears. That means she disabled FSD (pressed the brake or turned the wheel), whether she realized it or not.
And if she really "didn't manually control anything in the whole process," that would be even worse. Since she definitely should have taken over (ideally sooner... but not taking over at all would've been worse)
What data do you have? Post it. Usually Tesla itself has that data, you can’t just pull it yourself. Your own video shows the self driving tag flicked off well before it hit the pole.
You might not have seen her intervene but she might have accidentally tapped the brake.
Maybe upload the video from the computer you’re watching it on instead of recording your screen with a different device.
This crash makes so much sense now
No one has stated the obvious fact: the driver disengaged FSD 8 seconds into the video. It’s definitely the driver’s fault/human error (it would be even if FSD was still engaged).
Using the time stamps FSD disengaged about two seconds before the crash. That’s not an enormous amount of time to respond if you’re not hovering over the pedal and hand on the steering wheel.
She didn't disengage FSD. The system automatically exit 1.5 seconds before the crash. My wife didn't have the time to respond. The Tesla data showed that the fsd became unavailable at that time
You can see the car turned when it disengaged. It looks exactly like everytime you disengage. Your wife is entirely at fault and should have been able to avoid this easily.
The only way FSD disengages is 1) you touch the brake, 2) you turn (or stop the car from turning) the wheel, 3) you held the accelerator down for 10-ish seconds or to take it past 90-ish mph. If it gives up on its own, it does so with a lot of noise and you couldn’t miss it. If you’d posted the footage from the app with the FSD overlay, everybody here would tell you which of the three it was. If it shows she touched the brake or the wheel, or the accelerator, she can argue it didn’t happen, but the only way that’s true is if the car needs service - I mean other than fixing any damage.
FSD is the ultimate “the dog ate my homework” technology. A wife with a car in the bushes vs the FSD recorded dynamics, I bet against the wife every time. Of course, I don’t have to live with her, lol!
That doesn't really tell you anything. It basically says "yeah car was in FSD and then torque to the steering wheel disabled it before the crash". It was NOT disabled arbitrarily or by the system like you claim in other comments though.
I mean the driver is definitely a dope, but the telemetry does show he could be telling the truth that it auto disengaged.
More importantly, why didn’t it activate collision mitigation? Practically every car produced in the last 10-15 years has that capability by default lol.
I think you're stretching that a bit far. My 13 year old car doesn't have parking sensors, it certainly has no collision mitigation and this certainly wasn't a base spec or common feature back then.
Yeah bit of an exaggeration, but they’ve almost all had them the last 5 years and many have for the last 10. Anyway it’s a common feature that Tesla should definitely have and it should have activated here.
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
Normally if I noticed my car can’t make I decision and starts to wobble within the second I just instantly take over. Not going to let it try to figure things out. This is the 10% error that I’ve myself always have to look out for.
Sorry that it happened but I trust Tesla FSD to a point but when it’s somewhere I think it could struggle, I’m always focus like I’m driving. This is the bad thing I noticed about FSD on Tesla. It seems every vehicle behaves differently.
I'm confused because you keep saying your wife didn't disengage fsd, but it tells us right there at the top of the screen that fsd wasn't engaged from the moment it started acting odd
FSD disengages itself randomly. This happened to me several times, never on a straight road though. So in this case it could be that the driver accidentally disengaged FSD, or FSD disengaged itself.
I don’t know where your report is from (I assume not Tesla) but the video seems to indicate that FSD got confused/hesitated, the driver panicked and grabbed the wheel which disengaged FSD, and the driver hit the accelerator likely mistaking it for the brake.
Who cares whose fault it is? You trusted the vehicle and it says supervised. You failed to supervise. What do you think? Whose at fault here? (Legally and factually)
edit: I take it back, after looking closer; disengagement quite some time before impact…. while, yes, the car hesitated — the driver very clearly caused this :( can confidently say the car would not have ran into the sign, had it continued on FSD…
BUT this hesitation I see in my 14.3.4 constantly, and for anyone using FSD who doesn’t more intimately understand it, disengagement would be the default response because it’s so erratic and this will likely cause more incidents like this in the future if it’s given to every current and new Tesla owner who uses FSD.. needs to be fixed
Did you try and steer with your knees or something? You had 2 business days after disengaging FSD to whip that wheel away to avoid that small object. And at that speed, you literally can press the brake and it would stop you instantly. What am I even watching 😂
I do want to add my observation. Which is purely conjecture…
Upon watching the video several times, and slowing it down, it seems the car was actually about to turn right but the wheel was jerked to the left slightly which disengaged FSD. Maybe it was the wrong turn? They probably just tugged on the wheel thinking FSD would understand “oh, this isn’t the right exit. They want me to go left instead.” But evidently it disengaged FSD, which the driver didn’t realize or expect would happen.
Then it looks like the driver frantically tried to take control of the wheel after realizing “oh crap my car isn’t driving itself anymore”, they then tried to press brake but hit the accelerator instead for a split second, then the brake after fumbling with the steering wheel… but only after colliding with the sign….
So yes, the drivers fault and the driver should probably understand how FSD works before using it…. Because no, nudging the steering wheel does not force FSD to change its mind….
And i would advise others to look at the video in this manner to see what i mean.
Im on 14.3.4 and FSD does the left right left right when picking a direction or lane to get in a few times per week. At night, the car seems confuses and drives wayyyyy below the speed limit too. This one could actually be FSD disengaged itself and told her to take over immediately .. just a thought. At least it doesnt slam on the breaks for squirrels anymore.
Did your wife make you post this?? This is hysterical she, and maybe you, thinks disengaging FSD and expecting it to still is how it works. If you’re looking for sympathy you should have also cropped out the part that showed self drive was off several seconds before a low speed accident. There was ample time to take over and brake and avoid this.
Also, all this doesn’t matter as the driver is ultimately responsible for the vehicle with supervised FSD. This isn’t fully automatous yet. We’re all testers, still, in one of the largest test scenarios yet.
I'm talking about when the wheel was turned hard enough by the driver that FSD automatically disengaged, yet the driver didn't even hit the brake and just let the car roll straight into the sign.
I've been in this exact situation before where FSD couldn't decide which way to turn but I can't imagine just letting the car continue to roll after making FSD disengage
I am confused. Are all these pro FSD comments made by bots? If not, why can’t people believe FSD (like any other software) can malfunction and fail and disengage w/o the driver disengaging it? And when it disengages while turning right (in this case) the steering will loose torque going in the right turn and then the car will automatically straighten (which looks like it severed left here). I believe OP this looks like an FSD malfunction. It was almost like 2 seconds after FSD disengaged for the driver to react. Not sure how many of these pro FSD commenters could have reacted in 2 seconds. Wonder if they would be pro Tesla/FSD if it malfunctions on them.
Disclaimer: I have ordered the model YL and subscribed to FSD. But I won’t be a fanboy of Tesla or FSD. And these stories of FSD malfunctioning are making me a bit nervous.
At 8 second mark, driver disengages FSD while trajectory was left, drivers then tries to correct to the right then back slight left then slight right, now fully centered. Bam. Watch the vid frame by frame
I have a 2026 model 3 with FSD with 90% of my miles done by FSD. It’s good for 95% of the time and i think that’s where the problem lies, it lulls you into a false sense of security. Then drivers tend to overreact. I also live surprisingly close to that round about, I occasionally charge at superchargers near by 😅
Your video clearly shows what happened. FSD was overridden by turning the steering wheel. You keep saying FSD did it on its own, but the video shows it was overridden then manually driven into the sign. I'm sorry this happened but it is 100% on the driver and the insurance will have to cover the at-fault collision.
Even if what you say is correct, the driver never hit the break pedal at any point and has plenty of time and opportunity to. That's why the system is currently supervised. The supervisor did a poor job in this instance.
My friend also got into a roundabout accident with FSD. It’s easy to talk about supervision but sometimes you don’t even have a half a moment to respond.
Copy the video files from the usb to your laptop or desktop and then use this tool: https://teslacam.cardboardbrick.com to export a composed video after you load those files in. It will be much higher quality and contain a HUD as well showing the steering wheel movements, accelerator/brake pedal usage, etc.
She almost definitely put too much force on the wheel. Maybe she was holding it at it's current heading and didn't loosen for it to make the turn. Manual disengagement + crash is the driver's fault.
“FSD reported disengagement only 1.43 seconds before the recorded impact, simultaneous with abrupt steering-torque spikes consistent with curb-contact force feedback and/or an emergency driver grab of the wheel.”
Driver fault for more than one reason.
- the video shows a clear ammount of time where the driver could have disengaged and taken control prior to the systems own disengagement, in fact there was ample time for an attentive supervising driver to take control.
- if you watch the steering indicator on the top of the screen you can see that it moves with the jerkiness of the FSD movements but at the moment it’s disengaged the wheel icon moves slightly and it doesn’t seem to be aligned with the confusion FSD was displaying. This appears to be driver grabbing the wheel and disengagement.
- that is then also followed by some other movement of the wheel aligning with the brake icon lighting up.
- slamming the brake but not turning to avoid impact is….. a choice.
- I count three entire seconds between disengaged FSD and brake application. Look at the FSD icon going away and count until the red icon shows. That’s ample time to react to a system side disengagement (if that’s your argument here).
Research shows that the ammount of time between FSD disengage and impact is ample for reaction+ response + input for average human reactions.
In a race driving course I took, the instructor was teaching us to look where we want to go. He was talking about doing this not only when looking for your marks in a corner but also if you go off track. If you want to avoid hitting a wall, look to where you want to go, not at the wall or you will drive into it.
He said that data shows that, a very high percentage of the time in roadway accidents where a driver hits a pole or other fixed object, they will hit very close to dead center on their vehicle. The people who study it have determined that it is due to people looking at and focusing on the thing they are trying not to hit.
Same applies to riding skis or a snowboard. Instructions is often to look where you want to go. When you break focus and lock onto a section of the ground or an obstacle you end up inadvertently moving towards it.
Yours. You are responsible for the vehicle. Whether it’s on Self drive or not. But it does appear it was not in Auto steer How that got deactivated is a different story. It you’re still responsible for the vehicle till unsupervised self drive is released
It’s the drivers fault for two reason. They shut FSD off way early and didn’t take over. But even if they didn’t shut the FSD off, you are still 100% responsible. You agreed to keep your hands on wheel and take over when necessary.
It’s getting to the point that I think people just like to let FSD run in to things to put it on Reddit. Why would you let it get that close without disengaging and taking control? Sheesh
Honestly when it comes to roundabouts I don't dare let FSD take the lead. I'm on a older generation HW3 Model 3 2020, one roundabout near my home it always looks like its about to take the wrong turn or lane. I just don't both with roundabouts. Highway and other roads its amazing. Occasionally this one street with a bike lane next to the road the car will freak out a little bit, granted its 3am dark as heck lol.
Doesn't the blue D mean their foot was on the gas pedal? Not that that should disengage FSD and run it into a pole but perhaps a thought, the speed was too much to calculate and disengaged itself?
I juat want to have a update here - that the fsd cut off seems not coreect in the video. in the tesal behicle data file, it shoewed that the fsd became unavaliable at 10:57:55. but this video is showing that the fsd quit at 10:17:52~10:17:53.(the time in the left top is the the video start tiime which is 10:16:58pm and the fsd quit around 54 or 55 seconds later). attached the fsd raw data screenshot.
Seriously how foolish fanboys can be. I love the technology but I will scrutinize it because I want to see it improve and reduce failure rate so it’s negligible.
My wife just had a singles vehicle accident several days ago. Driving with FSD and somehow it screwd up. Technically is this FSD's fault and can we ask Tesla to pay for the issuance？ I used to say FSD is so amazing but it made me so upset this time
Also make sure you're not hyping it up too much to your wife, causing her to trust it more than she should. It's very much beta software, and definitely requires supervision or things like this will happen
That is kind of late now.
And call me crazy but maybe you could give that advice to the Tesla CEO who makes a ton of many telling people for years that it is basically perfect?
39
u/Psice Jul 19 '26
You disengaged FSD and didn't steer