Tesla FSD v14.1 Lite Drove Straight Over a Log — What HW3 Owners Should Take From It

A Tesla owner posted dashcam footage last week of his car driving straight over a log lying across the road while Full Self-Driving (FSD) v14.1 Lite was engaged. No braking. No swerve. The clip has picked up more than 800,000 views, and it's become the latest entry in a growing list of problems with Tesla's "Lite" version of FSD on older Hardware 3 cars.

The video was posted by X user @donvarri on August 21. In it, the car is rolling down a wet, foggy rural road at 32 mph with the "Self-Driving" visualization active. A log sits across the lane. The Tesla runs right over it.

"Mine drove over a log in the road it def wouldn't have stopped same 14.1 lite" — @donvarri

He later confirmed the car is a Hardware 3 vehicle running the newest v14.1 Lite build.

Why v14 Lite Keeps Making Headlines

FSD v14 Lite is a compressed version of the HW4 v14 model, squeezed onto HW3's memory-constrained AI3 computer — 8GB of RAM and roughly one-eighth the bandwidth of the newer hardware. Tesla began rolling it out to Hardware 3 cars in June, and the reports since then haven't been encouraging:

• HW3 computers overheating under the added processing load, throwing an APP_w141_ECU_Thermal_Issue fault above 90°C, with some temperatures reaching 96°C
• "Red hands" warnings and forced disengagements in several cases
• A handful of computers shutting down entirely and needing replacement
• Phantom braking, hesitation, and brake stuttering reported by drivers

Tesla shipped v14.1 Lite partly to address the overheating. This log incident happened on that supposedly improved build.

The larger issue hasn't moved. HW3 can't deliver the unsupervised autonomy Tesla sold, the company has admitted it has no clear plan to get there, and roughly 4 million cars were sold as "full self-driving capable" — for as much as $15,000 in some cases.

The Complacency Trap

The replies to the video turned into a fight over blame. Plenty of people told the owner he should have been watching the road. His response captures the whole problem:

"2 things can be true I should have been paying attention but the car definitely should have stopped."

One commenter was blunter: "No, YOU allowed that to happen for the opportunity to post a video, by failing to properly supervise." The owner pushed back that he's no Tesla hater — 70,000 miles driven, and it's the best car he's ever owned.

That's the trap with a Level 2 system that's good most of the time. The better FSD gets at routine driving, the more the driver relaxes. And that's exactly when it plows over an obstacle a human would have spotted from a hundred feet away. The system trains its own supervisor to stop supervising.

What This Means If You're Behind the Wheel

Both things really are true here. The driver should have been paying attention, and the car should have stopped for a log in the middle of the road at 32 mph. Blaming the driver alone lets the software off the hook; blaming the software alone ignores what supervision is actually for.

Practically speaking, a few takeaways for anyone running FSD on a Hardware 3 car:

• Treat v14.1 Lite as driver assistance, not autonomy. It is a compressed model on hardware Tesla has already conceded can't do the job.
• Be extra skeptical in low-visibility conditions. This incident happened on a wet, foggy rural road — exactly the environment where camera-only perception has the least margin.
• Keep your dashcam running and your USB storage healthy. Footage is what turned this from a one-off into a documented pattern, and it's what protects you in an insurance dispute.
• Watch for thermal warnings. If your car throws thermal faults or forced disengagements on Lite builds, log them and report them.

The Repair Bill Nobody's Talking About

Running over a solid log at 32 mph is violent. Similar-but-lesser impacts have run into five figures in suspension and frame repair on a Model 3, and it wouldn't be shocking if this car ends up totaled once someone inspects the underbody. That's the part that doesn't show up in the view count: the cost lands on the owner and their insurer, not on the software.

The complacency issue is real, but it's a design problem as much as a driver problem. Tesla keeps pushing more capable software onto hardware it has already admitted can't do the job, and the result is a system smooth enough to lull you and brittle enough to run over a log.

Source: Electrek, published August 24, 2026.