News
Tesla argues human error caused fatal 2019 crash, not Autopilot: report
Tesla now faces the jury’s verdict in a trial alleging that Autopilot caused a fatality, and the trial is expected to set a precedent for future cases surrounding advanced driver assistance systems (ADAS). During closing arguments on Tuesday, an attorney for the plaintiffs pointed to an analysis Tesla conducted two years before the accident, claiming that the automaker knowingly sold the Model 3 with a safety issue related to its steering.
The trial began in California late last month after a 2019 incident in which 37-year-old Micah Lee veered off a highway outside Los Angeles at 65 miles per hour, suddenly striking a palm tree before the vehicle burst into flames. According to court documents, the crash killed Lee and injured both of his passengers, one of whom was an 8-year-old boy.
Lee’s passengers and estate initiated a civil lawsuit against Tesla, alleging that the company knew that Autopilot and its other safety systems were defective when it sold the Model 3.
Tesla has denied any liability in the accident, claiming that Lee had consumed alcohol before getting behind the wheel and saying it could not detect if Autopilot was engaged at the time of the crash.
This and other trials come as regulatory requirements for ADAS suites are just emerging, and the cases are expected to help navigate future court cases related to accidents with the systems.
According to Reuters, the attorney for the plaintiffs, Jonathan Michaels, showed the jury an internal safety analysis from Tesla in 2017 during closing arguments, in which employees identified “incorrect steering command” as a potential safety issue. Michaels said the issue involved an “excessive” steering wheel angle, arguing that Tesla was aware of related safety problems before selling the Model 3.
“They predicted this was going to happen. They knew about it. They named it,” Michaels said.
Michaels also said that Tesla created a specific protocol to deal with affected customers and that the company instructed workers to avoid accepting liability for the issue. Michaels also echoed prior arguments, saying that Tesla knew it was releasing Autopilot in an experimental state, though it needed to do so to boost market share.
“They had no regard for the loss of life,” Michaels added.
Michael Carey, Tesla’s attorney, said that the 2017 analysis wasn’t meant to identify the defect but instead was meant to help avoid any potential safety issues that could theoretically occur. Carey also said that Tesla developed a system to prevent Autopilot from making the same turn that had caused the crash.
Carey said that the subsequent development of the safety system “is a brick wall standing in the way of plaintiffs’ claim,” adding that there haven’t been any other cases where a Tesla has maneuvered the way that Lee’s did.
Instead, Carey argued to the jury that the crash’s simplest explanation was human error, asking jurors to avoid awarding damages on behalf of the severe injuries encountered by the victims.
“Empathy is a real thing, we’re not saying its not,” Carey argued. “But it does not make cars defective.”
Earlier this month, a federal judge in California ruled in Tesla’s favor in a similar case looking at whether the automaker misled consumers about its Autopilot system’s capabilities. In that case, which had the chance to become a class-action lawsuit, the judge ruled that most of the involved plaintiffs had signed an arbitration clause when purchasing the vehicle, requiring the claims to be settled outside of court.
The cases are expected to set precedents in court for future trials involving Tesla’s Autopilot and Full Self-Driving (FSD) beta systems and the degree of the automaker’s responsibility in accidents related to their engagement. Tesla is also facing additional information requests from the U.S. Department of Justice related to its Autopilot and FSD beta.
Tesla has received more requests regarding Autopilot and FSD from DOJ
What are your thoughts? Let me know at zach@teslarati.com, find me on X at @zacharyvisconti, or send your tips to us at tips@teslarati.com.
Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.
Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”
The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.
The new Automatic Collision Evasion feature worked flawlessly! FSD reengaged itself just as I was about to hit a curb.
Kudos @Tesla_AI team! 👏 pic.twitter.com/Fbp15HhpL2
— Spencer (@scotsrule08) September 28, 2026
The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.
Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.
Tesla plans big safety improvements for Full Self-Driving v15
Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.
Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.
Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.
The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:
“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”
Roadster event update
We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule.
New date is October 15. Additional details to…
— Tesla (@Tesla) September 28, 2026
We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.
Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.
Tesla Roadster is available for order once again following brief hold
The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.
The Tesla Roadster will be unveiled in Waco, Texas.
Elon Musk
SpaceX turned a heralding moment for Starship into its greatest
Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.
SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.
The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.
Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.
Splashdown confirmed. Congratulations to the entire SpaceX team on the first orbital flight of Starship! pic.twitter.com/urjmiwnvNl
— SpaceX (@SpaceX) September 28, 2026
That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.
The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.
SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.
Starship’s 14th flight is set to launch on Monday, Sept 28. The 75-minute launch window opens at 7:15 a.m. CT. Live coverage of the mission starts ~35 minutes before launch → https://t.co/uQKQvgaTmJ
— SpaceX (@SpaceX) September 27, 2026
Watch Tesla’s “guardian angel” FSD feature take over for collision evasion
Tesla Roadster event gets delayed due to unfavorable weather
