News
Driver of Model X crash in Montana pens open letter to Musk, calls Tesla drivers “lab rats” [Updated]
Pang, the driver of the Model X that crashed in Montana earlier this month has posted an open letter to Elon Musk and Tesla asking the company to “take responsibility for the mistakes of Tesla products”. He accuses Tesla for allegedly using drivers as “lab rats” for testing of its Autopilot system.
In an email sent to us and also uploaded to the Tesla Motors Club forum, Pang provides a detailed account of what happened the day of the crash. He says he and a friend drove about 600 miles on Interstate 90 on the way to Yellowstone National Park. When he exited the highway to get on Montana route 2, he drove for about a mile, saw conditions were clear, and turned on Autopilot again. Pang describes what happened next as follows:
“After we drove about another mile on state route 2, the car suddenly veered right and crashed into the safety barrier post. It happened so fast, and we did not hear any warning beep. Autopilot did not slow down at all after the crash, but kept going in the original speed setting and continued to crash into more barrier posts in high speed. I managed to step on the break, turn the car left and stopped the car after it crashed 12 barrier posts.
“After we stopped, we heard the car making abnormal loud sound. Afraid that the battery was broken or short circuited, we got out and ran away as fast as we could. After we ran about 50 feet, we found the sound was the engine were still running in high speed. I returned to the car and put it in parking, that is when the loud sound disappeared.”
Pang goes on to explain how his Tesla Model X driving on Autopilot continued to travel on its own even after veering off the road and crashing into a roadside stake. “I was horrified by the fact that the Tesla autopilot did not slow down the car at all after the intial crash. After we crashed on the first barrier post, autopilot continued to drive the car with the speed of 55 to 60 mph, and crashed another 11 posts. Even after I stopped the car, it was still trying to accelerate and spinning the engine in high speed. What if it is not barrier posts on the right side, but a crowd?”
Photo credit: Steven Xu
After the accident, Tesla reviewed the driving logs from the Model X and reported that the car was operating for more than two miles with no hands on the steering wheel, despite numerous alarms and warnings issued by the car. Pang says he never heard any audible warnings. Comments on TMC range from the incredulous to the acerbic. Most feel Teslas simply don’t operate the way Pang said his car did. Among other discrepancies, the cars are designed to put themselves in Park if the driver’s door is opened with no one in the driver’s seat.
But that hasn’t stopped Pang from voicing his strong opinions on Tesla’s Autopilot system. “It is clear that Tesla is selling a beta product with bugs to consumers, and ask the consumers to be responsible for the liability of the bugging autopilot system. Tesla is using all Tesla drivers as lab rats.”
A car that crashes but continues to accelerate is certainly a scary thought. There is no way to resolve the discrepancy between what Pang says happened and Tesla’s account of what occurred. In an updated email sent to us by friend and english translator for Mandarin speaking Pang, Tesla has reached out to Pang to address the matter.
The original open letter from Pang reads as follows:
A Public Letter to Mr. Musk and Tesla For The Sake Of All Tesla Driver’s Safety
From the survivor of the Montana Tesla autopilot crash
My name is Pang. On July 8, 2016, I drove my Tesla Model X from Seattle heading to Yellowstone Nation Park, with a friend, Mr. Huang, in the passenger seat. When we were on highway I90, I turned on autopilot, and drove for about 600 miles. I switched autopilot off while we exited I90 in Montana to state route 2. After about 1 mile, we saw that road condition was good, and turned on autopilot again. The speed setting was between 55 and 60 mph. After we drove about another mile on state route 2, the car suddenly veered right and crashed into the safety barrier post. It happened so fast, and we did not hear any warning beep. Autopilot did not slow down at all after the crash, but kept going in the original speed setting and continued to crash into more barrier posts in high speed. I managed to step on the break, turn the car left and stopped the car after it crashed 12 barrier posts. After we stopped, we heard the car making abnormal loud sound. Afraid that the battery was broken or short circuited, we got out and ran away as fast as we could. After we ran about 50 feet, we found the sound was the engine were still running in high speed. I returned to the car and put it in parking, that is when the loud sound disappeared. Our cellphone did not have coverage, and asked a lady passing by to call 911 on her cellphone. After the police arrived, we found the right side of the car was totally damaged. The right front wheel, suspension, and head light flied off far, and the right rear wheel was crashed out of shape. We noticed that the barrier posts is about 2 feet from the white line. The other side of the barrier is a 50 feet drop, with a railroad at the bottom, and a river next. If the car rolled down the steep slope, it would be really bad.
Concerning this crash accident, we want to make several things clear:
1. We know that while Tesla autopilot is on but the driver’s hand is not on the steering wheel, the system will issue warning beep sound after a while. If the driver’s hands continue to be off the steering wheel, autopilot will slow down, until the driver takes over both the steering wheel and gas pedal. But we did not hear any warning beep before the crash, and the car did not slow down either. It just veered right in a sudden and crashed into the barrier posts. Apparently the autopilot system malfunctioned and caused the crash. The car was running between 55 and 60 mph, and the barrier posts are just 3 or 4 feet away. It happened in less than 1/10 of a second from the drift to crash. A normal driver is impossible to avoid that in such a short time.
2. I was horrified by the fact that the Tesla autopilot did not slow down the car at all after the intial crash. After we crashed on the first barrier post, autopilot continued to drive the car with the speed of 55 to 60 mph, and crashed another 11 posts. Even after I stopped the car, it was still trying to accelerate and spinning the engine in high speed. What if it is not barrier posts on the right side, but a crowd?
3. Tesla never contacted me after the accident. Tesla just issued conclusion without thorough investigation, but blaming me for the crash. Tesla were trying to cover up the lack of dependability of the autopilot system, but blaming everything on my hands not on the steering wheel. Tesla were not interested in why the car veered right suddenly, nor why the car did not slow down during the crash. It is clear that Tesla is selling a beta product with bugs to consumers, and ask the consumers to be responsible for the liability of the bugging autopilot system. Tesla is using all Tesla drivers as lab rats. We are willing to talk to Tesla concerning the accident anytime, anywhere, in front of the public.
4. CNN’s article later about the accident was quoting out of context of our interview. I did not say that I do not know either Tesla or me should be responsible for the accident. I might consider buying another Tesla only if they can iron out the instability problems of their system.
As a survivor of such a bad accident, a past fan of the Tesla technology, I now realized that life is the most precious fortune in this world. Any advance in technology should be based on the prerequisite of protecting life to the maximum extend. In front of life and death, any technology has no right to ignore life, any pursue and dream on technology should first show the respect to life. For the sake of the safety of all Tesla drivers and passengers, and all other people sharing the road, Mr. Musk should stand up as a man, face up the challenge to thoroughly investigate the cause of the accident, and take responsibility for the mistakes of Tesla product. We are willing to publicly talk to you face to face anytime to give you all the details of what happened. Mr. Musk, you should immediately stop trying to cover up the problems of the Tesla autopilot system and blame the consumers.
Tesla’s Response on TMC
TM Ownership, Saturday at 12:11 PM
Dear Mr. Pang,
We were sorry to hear about your accident, but we were very pleased to learn both you and your friend were ok when we spoke through your translator on the morning of the crash (July 9). On Monday immediately following the crash (July 11), we found a member of the Tesla team fluent in Mandarin and called to follow up. When we were able to make contact with your wife the following day, we expressed our concern and gathered more information regarding the incident. We have since made multiple attempts (one Wednesday, one Thursday, and one Friday) to reach you to discuss the incident, review detailed logs, and address any further concerns and have not received a call back.
As is our standard procedure with all incidents experienced in our vehicles, we have conducted a thorough investigation of the diagnostic log data transmitted by the vehicle. Given your stated preference to air your concerns in a public forum, we are happy to provide a brief analysis here and welcome a return call from you. 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. As road conditions became increasingly uncertain, the vehicle again alerted you to put your hands on the wheel. 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.
Following the crash, and once the vehicle had come to rest, the passenger door was opened but the driver door remained closed and the key remained in the vehicle. Since the vehicle had been left in Drive with Creep Mode enabled, the motor continued to rotate. The diagnostic data shows that the driver door was later opened from the outside and the vehicle was shifted to park. We understand that at night following a collision the rotating motors may have been disconcerting, even though they were only powered by minimal levels of creep torque. We always seek to learn from customer concerns, and we are looking into this behavior to see if it can be improved. We are also continually studying means of better encouraging drivers to adhere to the terms of use for our driver assistance features.
We are still seeking to speak with you. Please contact Tesla service so that we can answer any further questions you may have.
Sincerely,
The Tesla team
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
