News
The saga continues with Model X driver involved in Montana crash
Mr. Pang is back this time with a second open letter to Tesla
The Tesla Model X driver involved in a Montana crash while using Autopilot is stirring up controversy once again this time asking Tesla Motors to reveal additional details from the incident. It seems that language differences play a large role in this dispute. Acting as his representative, Steven Xu sent us a second open letter Mr. Pang penned to Elon Musk, in which he takes issue with Tesla’s account of the accident. The open letter reads as follows:
Here is the second letter from my friend, Mr.Pang.
To Tesla Team:
It has been weeks since I published the letter. No one has ever tried to contact us and discus about the crash. To fully understand the reason that caused this crash is critical for all tesla drivers. After awhile tesla published a response towards our letter. Most of parts are fit into the story. However there are few points that I would like to point out.
“From this data, we learned that after you engaged Autosteer, your hands were not detected on the steering wheel for over two minutes. This is contrary to the terms of use when first enabling the feature and the visual alert presented you every time Autosteer is activated.”
I admit that my hands were out of steering wheel after I engaged autopilot. The reason that I was doing that is because I put too much faith in this system. I also believe most Tesla driver would do the something when they
engage autopilot including Elon. The problem here is that Tesla had over advertised this feature by calling it “autopilot”. This feature should named “advance driving assistant”. It is possible that Tesla had known accident like this would come sooner or later. Tesla might think that setting up the term by saying “please put hands on steering wheel at all time” would be response free for Tesla.
2、 As road conditions became increasingly uncertain, the vehicle again alerted you to put your hands on the wheel.
The road condition was better than fine. Lane mark is absolutely clear. Road is flat and there is no incoming car. No matter what my sight was never out of the road. However everything was happened too fast for me to take control. Everything happened in less than a second.
3、No steering torque was then detected until Autosteer was disabled with an abrupt steering action. Immediately following detection of the first impact, adaptive cruise control was also disabled, the vehicle began to slow, and you applied the brake pedal.
No one should avoid the cause of the malfunction of autopilot feature. Since you start explaining it, I realize that you are implying that some sort of force was applied to the steering wheel by me. I had no idea how Tesla got this clue. There are two points I want to make here. First, my hands were not on the steering wheel. Second no obstacle was on the road to alter the steering wheel direction. The one and the only one that was taking control of this entire vehicle and steering it away from the road is autopilot software itself. Somehow I realize if my hands were on the steering wheel with a force, would Tesla blame me for the collision? To me it looks like that if an accident occur by autopilot, either hands are on or not on the steering wheel, Tesla can always find a way out by saying “abrupt steering action”.
Tesla also claimed that “abrupt steering adaptive cruise control was also disabled, the vehicle began to slow.”
This is nowhere near the truth. The real thing is that vehicle was NEVER attended to slow from hitting the first pole towards the last. It only took about a second to hit 12 wood poles. I believe if it wasn’t me who brake the vehicle it would continued cruising. Mr. Huang was injured severely due to high speed impact.
Tesla as a global impact company should respect the truth of every incident. Nothing is more important hand human life. Lying or manipulating towards public about what really happened is unacceptable.
Weeks ago I got contacted by Tesla regarding this accident. Since you cannot find a mandarin translator, we rearranged the call again in four hours. However that was the last time when Tesla tries to contact me. What I am asking is to fully reveal the driving data from the collision. Reliability of Autopilot software matters to hundreds and thousands of Tesla drivers. I wish to know the entire story about what really happened on us on that collision.
Thanks
Sincerely
Mr. Pang
Steven Xu pointed us to comments being made on the Tesla Motors Club forum that seemingly offers Mr. Pang no support at all. In fact, based on those comments, there almost seems to be a cultural bias in play in this situation. One wonders if perhaps things would seem different if they were driving a car in China that only displayed instructions in Mandarin.
Pang’s complaint is very similar to one lodged by a Chinese customer last month whose Tesla crashed on the highway on the way to work. He claimed that the salesman he spoke to before purchasing his car told him specifically that the car could drive itself and proved it by driving with his hands off the wheel during a test drive. Tesla later amended the language it uses to describe its Autopilot system on its Chinese website. It’s possible that same linguistic confusion has a bearing on Mr. Pang’s unfortunate accident.
At this point, it seems the matter will be handled by insurance companies and lawyers. Tesla apparently has had no further contact with Pang. Through Steven, Pang says, “Weeks ago I got contacted by Tesla regarding this accident. Since you cannot find a Mandarin translator, we re-arranged the call again in four hours. However, that was the last time when Tesla tries to contact me.
“What I am asking is to fully reveal the driving data from the collision. Reliability of Autopilot software
matters to hundreds and thousands of Tesla drivers. I wish to know the entire story about what really happened on us on that collision.”
Elon Musk
Elon Musk reveals date of Tesla Full Self-Driving’s next massive release
Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.
Tesla CEO Elon Musk revealed the date of Full Self-Driving’s next massive release: v14.3.
For months, Tesla owners with Hardware 4 have been utilizing Full Self-Driving v14.2 and subsequent releases. Currently, the most up-to-date FSD version is v14.2.2.5, which has definitely brought out mixed reviews. With releases, some things get better, and other things might regress slightly.
For the most part, things are better in terms of overall behavior.
However, many owners have been looking forward to the next release, which is v14.3, about which Musk has said many great things. Back in November, Musk said that v14.3 “is where the last big piece of the puzzle lands.”
He added:
“We’re gonna add a lot of reasoning and RL (reinforcement learning). To get to serious scale, Tesla will probably need to build a giant chip fab. To have a few hundred gigawatts of AI chips per year, I don’t see that capability coming online fast enough, so we will probably have to build a fab.”
Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.
Tesla Full Self-Driving v14.2 is a considerable improvement from early versions of the suite, but we have written about the somewhat confusing updates that have come with recent versions.
Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever
They’ve been incredibly difficult to gauge in terms of progress because some things have gotten better, but there seems to be some real regression on a handful of things, especially with confidence and assertiveness.
Musk confirmed today on X that Tesla is already testing v14.3 internally right now. It will hit a wide release “in a few weeks,” so we should probably expect it by late April.
It’s in testing right now. Wide release in a few weeks.
— Elon Musk (@elonmusk) March 19, 2026
Overall, there are high hopes that v14.3 could be a true game changer for Tesla Full Self-Driving, as many believe it could be the version that Robotaxis in Austin, Texas, some of which are driverless and unsupervised, are running.
It could also include some major additions, including “Banish,” also referred to as “Reverse Summon,” which would go find a parking spot after dropping occupants off at their destination.
What Tesla will roll out, and when exactly it arrives, all remain to be seen, but fans have been ready for a new version as v14.2.2.5 has definitely run its course. We have had a lot of readers tell us their biggest request is to fix Navigation errors, which seem to be one of the most universal complaints among daily FSD users.
Cybertruck
Chattanooga Charge: Tesla and EV fans ready for the Southeast’s wildest Tesla party
From Cybertruck Convoys to Kid-Friendly Fun Zones: The Chattanooga Charge Has Something for Everyone
Hundreds of like-minded Tesla and EV enthusiasts are descending on Chattanooga Charge this weekend for the largest Tesla meet in the Southeast. Taking place on March 20–22, 2026 at the stunning Tennessee Riverpark.
If you were there last year, you’ll know that it’s the ultimate experience to see the wildest Teslas in action, see the best in EV tech, and arguably the most fun – finally put a name to the face and connect with those social media buddies IRL! Oh, and that epic night time Tesla light show is a once-in-a-lifetime experience that will transform the Riverpark into something out of a sci-fi film that’s remarkably unforgettable and must be seen in person.
This year’s event takes everything up a notch, with over 100 Cybertrucks expected to be on display, many sporting jaw-dropping modifications and custom wraps that push the boundaries of what these stainless steel beasts can look like.
Whether you’re a diehard Tesla fan, EV supporter, or just EV-mod-curious, the sheer spectacle is worth the drive.
The Chattanooga Charge doesn’t wait until Saturday morning to get started. The weekend technically kicks off Friday, March 20th, and the venue sets the tone immediately. Come share roadtrip stories over drinks at the W-XYZ Rooftop Bar on the top floor of the Aloft Chattanooga Hamilton Place Hotel, with sunset views over the city.
Come morning, nurse your hangover with a some good coffee, and convoy with hundreds of other Tesla and EV drivers through Chattanooga to the event for some morning meet and greets before the speaker panel starts and the food trucks fire up.
Tesla owner clubs travel from across the country to be here, not just to show off their vehicles,, but to connect, share, and celebrate a shared passion for the future of driving.
Sounds like a plan to me. See you there, guys. Don’t miss it. Get your tickets at ChattanoogaCharge.com and join the charge. 🔋⚡
Chattanooga Charge is a premier Tesla and EV gathering inspired by the X Takeover, known as one of the largest Tesla event gatherings. What began as a bold idea from the team at DIY Wraps/TESBROS, hosted in their hometown of Chattanooga, Tennessee, the event quickly became a movement across social media. The first annual Chattanooga Charge united over 16 Tesla clubs from 16 states, proof that the EV community was hungry for something big in the South. Year after year, the event has grown in scale, ambition, and heart.
News
Tesla Full Self-Driving gets latest bit of scrutiny from NHTSA
The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.
The National Highway Traffic Safety Administration (NHTSA) has elevated its probe into Tesla’s Full Self-Driving (Supervised) suite to an Engineering Analysis.
The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.
The step up into an Engineering Analysis is often required before the NHTSA will tell an automaker to issue a recall. However, this is not a guarantee that a recall will be issued.
🚨 The NHTSA said it was upgrading a probe into Tesla’s Full Self-Driving (Supervised) platform to an “engineering analysis”
It will examine 3.2 million vehicles and aims to determine its effectiveness in evaluating degraded road conditions pic.twitter.com/2dkrv1mR8o
— TESLARATI (@Teslarati) March 19, 2026
The NTHSA wants to examine Tesla FSD’s ability to assess road conditions that have reduced visibility, as well as detect degradation to alert the driver with sufficient time to respond.
The Office of Defects Investigation (ODI) will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications Tesla makes to the degradation detection system, including the timing, purpose, and capabilities of the updates.
Tesla routinely ships software updates to improve the capabilities of the FSD suite, so it will be interesting to see if various versions of FSD are tested. Interestingly, you can find many examples from real-world users of FSD handling snow-covered roads, heavy rain, and single-lane backroads.
However, there are incidents that the NHTSA has used to determine the need for this probe, at least for now. The agency said:
“Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred.”
It continues to say in its report that a review of Tesla’s responses revealed additional crashes that occurred in similar environments showed FSD “did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path.”
The next steps of the NHTSA Engineering Analysis require the agency to gather further information on Tesla’s attempts to upgrade the degradation detection system. It will also analyze six recent potentially related incidents.
The investigation is listed as EA26002.