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
News
Tesla Robotaxi takes over for Uber credits and loaners at Service locations
Tesla is now utilizing its in-house Robotaxi platform to give those waiting for their vehicles during Service visits rides instead of offering Uber credits or Loaner vehicles.
Tesla owners in Austin who bring vehicles in for service are receiving in-app prompts to use the company’s Robotaxi network while their cars are being worked on.
One recent notification, sent during a frunk repair, carried the heading “Try Robotaxi During Your Service Visit” and stated that while the vehicle is being serviced, the customer can take an autonomous Robotaxi ride to the next destination in Austin and download the Robotaxi app to get started.
Interesting. While my frunk gets fixed Tesla suggests taking a Robotaxi 😇 https://t.co/QiUbAmrp4a
— Wadesmith (@LanceWade) November 17, 2026
The suggestion arrives as Tesla has long relied on two main ways to keep customers mobile during longer service visits. Service centers have typically offered loaner vehicles drawn from a limited fleet; when those vehicles were unavailable, centers have issued Uber or Lyft credits. Uber credits were widely eliminated years ago, but some locations will still give them out.
Both approaches carry costs: loaner cars occupy inventory that could otherwise be sold, and third-party credits generate recurring expense.
Code discovered in Tesla app version 4.60.5 in September 2026 already listed “sv_transport_robotaxi” among the transportation options available for service appointments, alongside paid loaners and other alternatives, indicating the company had been preparing to route customers through its own autonomous fleet.
Your Tesla could be in the Robotaxi fleet next month, Elon Musk claims
Austin provides the clearest early example. The city remains Tesla’s primary Robotaxi market, with unsupervised Model Y and Cybercab vehicles operating across an expanded zone of roughly 400–440 square miles and running 24/7 since November 11. Public driverless service is also live in Dallas, Fort Worth, Houston, San Antonio, Miami, Orlando, and Tampa.
Directing service customers into this network keeps the vehicles utilized and reduces reliance on external rideshare credits, while giving owners practical experience with the Robotaxi app and vehicles during the repair window. Once service is complete, the same network can be used for the return trip without a staffed loaner handoff.
The Austin notification is the first public instance of the capability the September app code previewed. As Robotaxi expands into additional U.S. markets and the fleet grows, service centers in those cities are positioned to follow the same pattern, presenting autonomous rides as a primary transportation option during the service appointment rather than defaulting to loaner vehicles or third-party credits.
For customers, the change preserves mobility without the logistics of arranging a temporary car; for Tesla, it links the service operation more tightly to the expanding Robotaxi business.
Elon Musk
Sean Duffy fires back at Elon Musk over free Starlink
Sean Duffy says the FAA picked a ground network over Starlink, and Musk isn’t impressed.
Transportation Secretary Sean Duffy has responded to Elon Musk’s claim that the Federal Aviation Administration turned down free Starlink terminals before last week’s nationwide ground stop, saying the department chose a ground-based network after running into problems with an earlier version of the satellite service. Musk’s reply was a single emoji: “🤦♂️.”
Speaking at a press conference, Duffy said Starlink had been useful in some parts of the system. “I’ve worked well with Elon, and he, Starlink was a great solution for some of our assets in Alaska, but we sent Starlink, in one of its prior iterations, to our tech lab, and, there was some issues that we had to navigate, and we thought that the best method is to have a network that’s based on the ground,” Duffy said, according to a transcript published by ZeroHedge. “Now, I think what he’s doing with Starlink and the speed is remarkable, but, our airspace is very big. We have assets everywhere. And so, again, we used him for different parts of the airspace.”
Duffy did not dispute that the offer was made. He also did not say what problems the FAA found during testing.
The exchange started Monday, when Musk wrote on X, “Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” as Teslarati reported. That post came three days after the FAA grounded departures nationwide on November 13, when its legacy equipment became unstable as data flooded its telecommunications network at 1,000 connection attempts every four to five seconds. The FAA traced the flood to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where L3Harris had been installing a new router. Roughly 12,462 flights were canceled that day.
As I was saying …
Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were.
— Elon Musk (@elonmusk) November 16, 2026
Duffy has also signaled frustration with L3Harris, which runs the FAA’s current network. “I want to get away from L3Harris and get to a new one, but they own the network,” he said. “I can’t cancel the network that they own.” He has asked Congress for $50 billion to modernize air traffic control, arguing against “a patchwork, a fix to a system that’s critical for every single family.”
The FAA’s position on satellite links predates this week. In a July 2025 letter to lawmakers, FAA Administrator Bryan Bedford said the agency “would not use Starlink (or any satellite service) as the sole communications technology” for safety-critical air traffic services. Reuters reported at the time that the FAA was not considering replacing its L3Harris and Verizon contracts with Starlink. Verizon’s FAA Enterprise Network Services contract, awarded in 2023, is valued at up to $2.4 billion over 15 years.
Musk first pressed the issue in February 2025, while he was leading the Department of Government Efficiency, writing that “the Verizon system is not working and so is putting air travelers at serious risk” before correcting himself days later to blame L3Harris. SpaceX said at the time it was supplying Starlink kits to the FAA at no cost and had no intent to take over any existing contract.
Elon Musk
Tesla gears up Cybercab with Starlink for public debut, but with notable changes
Tesla is gearing up Cybercab, its all-electric and fully autonomous ride-hailing vehicle, for a very public debut as it plans to start customer deliveries in December. However, the units that rolled out of Gigafactory Texas this morning seem to differ from what we have seen previously.
Aerial images captured by drone photographer Joe Tegtmeyer at Giga Texas on November 18 reveal a noticeable update to the appearance of Tesla’s Cybercabs equipped with Starlink. Rows of gold production vehicles sit in the outbound lot, each carrying a flush-mounted Starlink V5 terminal on the rear hatch that looks more refined than the version first shown months earlier.
When Tesla first unveiled the integration in July and displayed a physical example in August, the Starlink hardware appeared as a relatively distinct rectangular panel on the hatch. Later September footage of large numbers of Cybercabs leaving the factory still showed a lighter, more obvious rectangular cover that roughly matched the vehicle’s gold paint:

Images via Joe Tegtmeyer
The newest batch stands out for how cleanly the cover blends into the roof’s character lines. Observers and replies to Tegtmeyer’s post describe the result as tighter and more intentional, sitting flush and following the body contours rather than reading as an added panel.
All of the Cybercabs in the latest images also wear prominent “Cybercab” logos on the doors and rear hatch, confirming these are finished production units rather than early prototypes. They are staged near the factory building, end-of-line areas, and covered transport trailers, with some already lined up for shipment.
The scale and consistency of the installation point to factory tooling rather than retrofit work.
A secondary detail noted in related sightings is a darker tone to the Starlink cover compared with earlier lighter panels. Tegtmeyer himself left open whether the darker finish is deliberate. There are a variety of explanations for it: perhaps for thermal performance, signal characteristics, or simple visual identification—or simply a batch variation still being refined.
Either way, the overall effect is a more integrated, production-ready appearance. For a Robotaxi that relies on Starlink for fleet connectivity, passenger services, and backup data links in areas with weak cellular coverage, the cleaner hatch design is more than cosmetic.
It signals that Tesla is polishing the final visual and hardware details as Cybercab volumes continue to climb at Giga Texas ahead of broader Robotaxi deployment. The vehicles now look to be built with Starlink instead of it being added afterward.




