Tesla (TSLA) CEO Elon Musk took to his social media platform X (Twitter) to clear the fog off the matter arising from a Washington Post article published yesterday.
The article pivots around the possibility that Full Self-Driving (FSD Beta) was activated when a Tesla employee’s Model 3 car met a fatal crash in 2022.
At the time of this crash, the vehicle had two occupants, a Tesla employee named Hans von Ohain and his friend Erik Rossiter. Sadly, Ohain was killed in this accident and Rossiter survived.
Investigators found that Ohain was heavily intoxicated while driving. Hans von Ohain’s blood was found to have an alcohol level of 0.26 — 3 times above the legal limit.
Ohain’s Tesla Model 3 hit a tree on his way home. The car was on fire when Ohain’s friend Rossiter gained consciousness after the crash.
The Washington Post article and one by Fred Lambert of Electrek are trying to blame Tesla, Inc. partially by somehow proving that Tesla’s Full Self-Driving feature was activated on the car during the crash.
However, Elon Musk has debunked all of the assumptions that the car was somehow using the FSD Beta self-driving feature while it met a regrettable fate. In an X (Twitter) post, Musk said that FSD Beta had “never been downloaded” on Hans von Ohain’s Tesla Model 3.
“He was not on FSD. The software had unfortunately never been downloaded,” Musk posted on X. “I say “unfortunately”, because the accident probably would not have happened if FSD had been engaged,” he further explained.
Looks like the authors of The Washington Post article and the crash survivor Erik Rossiter don’t have a good understanding of how the Tesla Autopilot and Full Self-Driving work.
There is a basic Autopilot feature which can be described as an advanced Traffic-Aware Cruise Control (TACC). Then there is FSD Beta, which is an advanced self-driving feature and is currently working on around 400,000 Tesla cars across North America.
As the name suggests, the Full Self-Driving is still a ‘Beta’ software release. Tesla’s documentation and every FSD Beta software version release notes clearly mention that the driver should always keep his/her hands on the steering wheel and be prepared to take control of the vehicle at any time.
What von Ohain was using might be the basic Autopilot intended for use on Highway. The crash happened on Upper Bear Creek Road, Colorado which is a hilly and curved path.
The original Washington Post article mentions multiple times that Tesla Autopilot was not working well on this road. The vehicle had already swerved multiple times and von Ohain had to intervene. This behavior of the vehicle should have been enough to caution him to not use Autopilot for the rest of the trip. But von Ohain insisted because he wanted the car to cover up his drunk driving behavior and carelessness while it should have been the opposite.
The record of all the Tesla vehicles having Autopilot/FSD is kept on the automaker’s supercomputers at its Engineering HQ in Palo Alto, California. Therefore, it’s easy for Tesla to track if a specific vehicle has Full Self-Driving installed on it or not. Even if it is installed, Tesla can precisely track if it was activated or de-activated at the time of an incident.
This is why Elon Musk was able to confirm that Hans von Ohain’s Tesla Model 3 never had Full Self-Driving installed on it. He might be using basic Autopilot which is way inferior to FSD Beta, and the responsibility lies with the human driver.
According to the widow of Hans von Ohain, no lawyer is taking up her husband’s case because he was involved in intoxicated driving. This is enough to deflate the air mainstream media is trying to put in the anti-Tesla propaganda, especially in terms of Full Self-Driving.
Update: Tesla’s Vice President, Public Policy and Business Development Rohan Patel posted 2 tweets in the context of the Washington Post article and related FUD to clarify his company’s position in this case.
Let us know your thoughts in the comments section below.
Stay tuned for constant Tesla updates. Follow us on:
Google News | Flipboard | X (Twitter) | WhatsApp Channel | RSS (Feedly).
Related
- Tesla merges FSD v14.3.8 and the Summer Update (2026.26.6.5), Grok voice commands gain more control
- Tesla rolls out FSD v14.1 Lite after HW3 ECU overheating issues in FSD v14 Lite
- Tesla FSD v14.3.7 fixes regressions found in the previous version (video reviews)
- Tesla owners report regressions in FSD v14.3.6 (2026.20.6.11), the update still goes wide release
- Tesla FSD v14 Lite finally goes wide release with software update version 2026.20.6.11 (complete release notes)
- Tesla hints at FSD v14 Lite (2026.20.6.10) going wide release (official release notes, early review)
