Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

FSD Beta Attempts to Kill Me; Causes Accident

This site may earn commission on affiliate links.
Long time lurker, first time poster. I have been trying to work with Tesla to resolve this issue out of the public domain, but they have been characteristically terrible and honestly don't seem to care. Over the last 3 weeks, I have sent multiple emails, followed up via phone calls, escalated through my local service center, and nobody from Tesla corporate has even emailed or called to say they are looking into this. One of my local service center technicians opened a case with engineering, which she said would take 90 days to review. I find that absurd, especially when Tesla is releasing new versions every 2 weeks. I think it's important for people to be extra cautious about which roads they engage FSD beta on, especially since Tesla seems to be ignoring my report entirely.

49548280121_4d220fbae7_c.jpg



This incident happened almost 3 weeks ago on Monday, November 22nd at around 6:15 in the evening, just shortly after the sun had set. I was driving my Tesla Model Y on a two-lane rural road and had FSD engaged. The car was still on version 10.4 at the time. It was a clear night, no rain or adverse weather conditions. Everything was going fine, and I had previously used FSD beta on this stretch of road before without a problem. There was some occasional phantom braking, but that had been sort of common with 10.4.

A right banked curve in this two lane road came up with a vehicle coming around the curve the opposite direction. The Model Y slowed slightly and began making the turn properly and without cause for concern. Suddenly, about 40% of the way through the turn, the Model Y straightened the wheel and crossed over the center line into the direct path of the oncoming vehicle. I reacted as quickly as I could, trying to pull the vehicle back into the lane. I really did not have a lot of time to react, so chose to override FSD by turning the steering wheel since my hands were already on the wheel and I felt this would be the fastest way to avoid a front overlap collision with the oncoming vehicle. When I attempted to pull the vehicle back into my lane, I lost control and skidded off into a ditch and through the woods.

I was pretty shaken up and the car was in pieces. I called for a tow, but I live in a pretty rural area and could not find a tow truck driver who would touch a Tesla. I tried moving the car and heard underbody shields and covers rubbing against the moving wheels. I ended up getting out with a utility knife, climbing under the car, and cutting out several shields, wheel well liners, and other plastic bits that were lodged into the wheels. Surprisingly, the car was drivable and I was able to drive it to the body shop.

Right after the accident, I made the mistake of putting it in park and getting out of the vehicle first to check the situation before I hit the dashcam save button. The drive to the body shop was over an hour long, so the footage was overridden. Luckily, I was able to use some forensic file recovery software to recover the footage off the external hard drive I had plugged in.

In the footage, you can see the vehicle leave the lane, and within about 10 frames, I had already begun pulling back into the lane before losing control and skidding off the road. Since Teslacam records at about 36 frames per second, this would mean I reacted within about 360ms of the lane departure. I understand it is my responsibility to pay attention and maintain control of the vehicle, which I agreed to when I enrolled in FSD beta. I was paying attention, but human reaction does not get much faster than this and I am not sure how I could have otherwise avoided this incident. The speed limit on this road is 55mph. I would estimate FSD was probably going about 45-50mph, but have no way to confirm. I think the corrective steering I applied was too sharp given the speed the vehicle was going, and I lost grip with the pavement. On the 40% speed slowed down version of the clip, you can sort of see the back end of the car break loose in the way the front end starts to wiggle as the mailbox makes its way to the left side of the frame.

Surprisingly, I somehow managed to steer this flying car through a mini-forest, avoiding several trees (although I did knock off the driver's side mirror). There is no side panel damage whatsoever. The bumper cover is ruined and the car sustained fairly severe structural/suspension damage, both front and rear suspension components.

Luckily, nobody was hurt (except my poor car). I could not imagine the weight on my conscience if I had been too slow to intervene and ended up striking that oncoming vehicle. Front overlap collisions are some of the most deadly ways to crash a car, and bodily injury would have been very likely.

I have a perfect driving record and have never had an at-fault accident in the over 10 years I have been licensed. The thought of filing an insurance claim and increasing my premiums over this incident makes me sick. I am considering legal action against Tesla, but I'm not going to get into that here. Just wanted to make everyone aware and hyper-vigilant about FSD. I thought I was, but then this happened. I am going to be much more careful about the situations in which I decide to engage it. There is too much at stake, it is not mature enough, and frankly, Tesla's apathy and lack of communication around this incident really concerns me, as both an owner and a road-user.


tl;dr: Be careful with FSD, folks. And if you get into an accident, hit the dashcam save button or honk your horn before you put it in park.



Display of a Tesla car on autopilot mode showing current speed, remaining estimated range, speed limit and presence of vehicles on motorway lanes” by Marco Verch is licensed under CC BY 2.0.
 
Last edited by a moderator:
He explains in the youtube comments he was trying to get the warning to stop beeping and that he was doing the wheel shaking not the car. Would pressing the brake stop the warning? I don't know, one would assume the warning would have went off when the car detected him moving wheel. It is confusing to watch.
What ?!

You mean it did not happen exactly as described in OP ?

There are so many possibilities - without the interior camera it’s difficult to tell. But it sounds like he got a FCW and not a nag. But he thought it’s just a nag and he tried to jerk the wheel harder causing the swerves we see ?

BTW, did OP file a police report ?
 
  • Love
Reactions: Silicon Desert
I can see why that was taken down. The video pretty clearly shows that driver error was the cause of the accident. The oversteer reaction is really bad. Either OP wasn't really gripping the steering wheel, or they are an inexperienced driver. If you have been driving for any length of time, correcting from getting to close to or running over the median line is something you are familiar with and doesn't cause panic.

I suspect that OP was touching the steering wheel, but not grabbing it. This is poor driver behavior for AP, much less FSD. The takeaway here here should be: high alertness is required for the current state of FSD. If you aren't willing to do that, then don't participate. Instead, OP seems to have taken away: Any accident in my shiny new car is someone else's fault, and someone else needs to pay. This isn't how cars have ever worked.
Tesla should add a grip strength sensor to the steering wheel. I find that to disengage AP smoothly without jostling the car you really need a death grip on the wheel.
I’d like to see evidence that AP/FSD was even engaged at time of the double yellow crossing so abruptly. I wonder if this isn’t a case of the driver thinking AP was engaged but it wasn’t or he accidently disengaged it just before or bumped the wheel. At worst I’ve only experienced AP taking turns a little wide and gradually entering, and sometimes crossing the double yellow. But I recall the crossing of the double yellow only occuring with AP1 and only on turns tighter than that. with AP2 I don’t recall crossing the dbl yellow to that degree and certainly not that abruptly.
There are plenty of videos of FSD Beta crossing double yellow lines. AP isn't designed to swerve to avoid objects on the side of the road, FSD Beta is.
 
Regular AP almost certainly wouldn’t have applied that much steering input. It (along with other lane-keep type systems) errs on the side of continuing on its chosen path. I bet it would have phantom braked and that’s it.

That’s what makes FSD Beta potentially more dangerous/unintuitive for experienced AP users. We assume the car won’t do something like steer over the double yellow into oncoming traffic based on our years of driving on regular autopilot.

Just crossing the yellow line on turns could happen in AP but very rare. Even FSD doesn’t cross yellow line on slight bends. There is definitely more to the story than what OP says. For all we know AP/FSD was disengaged before the car started crossing the line.
 
There are plenty of videos of FSD Beta crossing double yellow lines. AP isn't designed to swerve to avoid objects on the side of the road, FSD Beta is.
Interesting. I dont have FSD beta and haven’t been following the FSD beta videos too much (except for this stupid one I clickbaited to).

A prime directive of any flavor of AP/FSD should be to avoid, and certainly not cause, a head-on collision.

I don’t see in the video what might have caused FSD to veer away from something on the right side and into oncoming lane, even briefly. And I wonder if FSD may calculated: “I think I see something on the right to avoid, so I will briefly swerve to clear it and come back into lane in plenty of time to give clearance to the oncoming traffic.” And maybe it would have been fine with no intervention.

I guess I do recall seeing some FSD Beta videos at low speeds in more urban roads pass double parked cars or give clearance to bikes or pedestrians by crossing dbl yellow briefly.
 
I don’t see in the video what might have caused FSD to veer away from something on the right side and into oncoming lane, even briefly. And I wonder if FSD may calculated: “I think I see something on the right to avoid, so I will briefly swerve to clear it and come back into lane in plenty of time to give clearance to the oncoming traffic. I guess I do recall seeing some FSD Beta videos at low speeds in more urban roads pass double parked cars or give clearance to bikes or pedestrians by crossing dbl yellow briefly.

There is nothing on or near the road to the right at the place where the car goes over the line.

Usually FSD would see the obstruction from far and slow down, wait for the oncoming car to pass before going around the obstruction.

I see no evidence of slow down - I won’t be surprised if OP got a nag and they jerked the wheel to the left. This disengaged FSD and made the car cross the yellow line. OP then saw the oncoming car and over corrected to the right.
 
  • Like
Reactions: JanG007 and bhzmark
There’s a mailbox.
Did OP press the report button? We may never know what it saw. It’s also possible that OP accidentally disengaged right before crossing double yellow.
There is no mailbox on the road. FSD won’t go around for stuff on the side.

If FSD misrecognized the mailbox as a person, indeed it could go around - but it will definitely cause hard braking too.

Anyway, so many possibilities and without the log and internal video we can’t tell. But I doubt it happened like OP claimed.
 
  • Funny
Reactions: AlanSubie4Life
Jon
He explains in the youtube comments he was trying to get the warning to stop beeping and that he was doing the wheel shaking not the car. Would pressing the brake stop the warning? I don't know, one would assume the warning would have went off when the car detected him moving wheel. It is confusing to watch.
True I just looked at the first crash report again and the person says the vehicle forcefully steered itself into the adjacent vehicle, which doesn't align with what happened here. But I could easily see someone making a bad move in a tense situation with this warning blaring at you to take over despite clearly having control and then misconstruing events after the fact.

AI Addict isn't even just an older FSD Beta tester, he's a Tesla engineer who works on the FSD labelling team
That’s right. He is one of the most experienced and helpful tester, what he did in that scene was emotional but understandable. However during the warning I think car was under his control, it was not a situation that “AP is taken over control and can’t be overridden”. It was just that once the warning fired off, it won’t stop for at least a few second.
 
In terms of the overcorrection, it seems like there are instances where the system can be difficult to disengage and can require real force that could lead to an overcorrection. I don't think that's what happened here, but look at what AI Addict had to do at the 3:00 mark in this video
Weird the way he tries to take over - instead of just braking.

Ofcourse a very different situation with parked vehicles on both sides.
 
  • Like
Reactions: JanG007
I still can’t see it. Played the video a few times too. What’s the time stamp ?
Sometimes I wonder whether we are watching the same videos!

The car definitely crossed the yellow line far before that mail post. Extremely unlikely car was trying to go around it.
Huh? The car veered about 2-3 seconds before the mail post. If that was a false detection of a pedestrian (conceivable I think), it could explain the behavior (even though it was completely the wrong behavior). That is exactly when you would expect a reaction.

Note that you would not easily be able to see any slowing in the video for a pedestrian detection.

Not saying that is what happened, but it certainly seems possible, and the timing would fit.

If the OP could provide location (won’t of course) then someone could drive that road at night and look at the visualizations. Or drive similar scenarios.

Certainly, I have seen many false pedestrian detections before (they have been partially resolved in the latest software), so it seems possible. This did take place on 10.4 which I think is where I saw them.
 
Huh? The car veered about 2-3 seconds before the mail post. If that was a false detection of a pedestrian (conceivable I think), it could explain the behavior (even though it was completely the wrong behavior). That is exactly when you would expect a reaction.

Note that you would not easily be able to see any slowing in the video for a pedestrian detection.

Not saying that is what happened, but it certainly seems possible, and the timing would fit.
There are two possibilities with false VRU detection. Early and late.

If it’s early - normal behavior would be to slowdown, wait for the oncoming car to pass and then go around.

If it’s late, normal behavior is disengagement and FCW and phantom braking. Not going around.

From YouTube comments, looks like OP got a FCW. He didn’t know want to do and jerked the wheel around. I think the simplest explanation for what happened.
 
  • Like
Reactions: AlanSubie4Life
f it’s early - normal behavior would be to slowdown, wait for the oncoming car to pass and then go around.

If it’s late, normal behavior is disengagement and FCW and phantom braking. Not going around.
Seems fairly accurate, however, I don’t think I’ve encountered enough of these situations to confidently say exactly how FSD would behave “normally” in any given scenario. All I know in any scenario is that FSD can be unpredictable and the driver has to be ready for anything.

An FCW seems pretty likely here, but it’s hard to say what triggered it if they did get one - the mailbox, or the car steering into oncoming traffic are both possibilities. I normally would not expect one from the mailbox but the car could have perceived it as a hazard or VRU in the roadway.