Connect with us

News

Driver of Model X crash in Montana pens open letter to Musk, calls Tesla drivers “lab rats” [Updated]

Published

on

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?”

Advertisement

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:

Advertisement

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?

Advertisement

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.

Advertisement

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

Advertisement
Comments

News

Tesla robotaxi test details shared in recent report: 300 operators, safety tests, and more

Tesla has launched an initial robotaxi service for its employees in Austin and the San Francisco Bay Area.

Published

on

Credit: Tesla

During the Q1 2025 earnings call, Tesla executives reiterated the idea that the company will be launching a dedicated robotaxi service using its Full Self Driving (FSD) Unsupervised system this coming June.

A recent report from Insider, citing people reportedly familiar with the matter, has now provided a number of details about the preparations that Tesla has been making as it approaches its June target date.

Remote Operators

As noted by the publication, about 300 test operators have been driving through Austin city streets over the past few months using Teslas equipped with self-driving software. These efforts are reportedly part of “Project Rodeo.” Citing test drivers who are reportedly part of the program, Insider noted that Tesla’s tests involve accumulating critical miles. Test drivers are reportedly assigned to specific test routes, which include “critical” tracks where drivers are encouraged to avoid manual interventions, and “adversarial” tracks, which simulate tricky scenarios.

Tesla has launched an initial robotaxi service for its employees in Austin and the San Francisco Bay Area, though the vehicles only operate in limited areas. The vehicles also use safety drivers for now. However, Tesla has reportedly had discussions about using remote operators as safety drivers when the service goes live for consumers. Some test drivers have been moved into remote operator roles for this purpose, the publication’s sources claimed.

While Tesla is focusing on Austin and San Francisco for now, the company is reportedly also deploying test drivers in other key cities. These include Atlanta, GA, New York, NY, Seattle, WA, and Phoenix, AZ.

Advertisement

Safety Tests

Tesla reportedly held training events with local first responders as part of its preparations for its robotaxi service, Insider claimed, citing documents that it had obtained. As per the publication, Tesla had met with the city’s autonomous vehicle task force, which include members of the Austin Fire Department, back in December.

Back in March, Tesla reportedly participated in about six hours of testing with local first responders, which included members of the fire department and the police, at a close test track. Around 60 drivers and vehicles were reportedly used in the test to simulate real-world traffic scenarios. 

Interestingly enough, a spokesperson from the Austin Police Department stated that Tesla did hold a testing day with emergency responders from Austin, Williamson County, as well as the Texas Department of Public Safety.

Reported Deadlines

While Tesla has been pretty open about its robotaxi service launching in Austin this June, the company is reportedly pursuing an aggressive June 1 deadline, at least internally. During meetings with Elon Musk, VP of AI software Ashok Elluswamy’s team reportedly informed the CEO that the company is on track to hit its internal deadline.

One of Insider’s sources, however, noted that the June 1 deadline is more aspirational or motivational. “A June 1 deadline makes a June 30 launch more likely,” the publication’s source noted.

Advertisement
Continue Reading

News

Atty who refused to charge six-time Tesla vandal sparks controversy

Despite the multiple offenses, Moriarty opted to enter Adams into an adult diversion program instead.

Published

on

Pilottap, CC0, via Wikimedia Commons

Hennepin County Attorney Mary Moriarty, who made the decision not to charge 33-year-old vandal Dylan Bryan Adams after he keyed six Teslas around Minneapolis last month, has found herself in the middle of controversy

The controversy came amidst her decision to press charges against a 19-year-old first-time vandal who keyed one vehicle at the White Castle in Brooklyn Park.

The Tesla Vandal

Moriarty’s decision not to charge Adams after he keyed six Teslas was met with widespread criticism. Adams’ actions resulted in more than $20,000 worth of damages, more than $10,000 of which was to a single vehicle, as noted in a New York Post report. Yet despite the multiple offenses, Moriarty opted to enter Adams into an adult diversion program instead.

The fact that Adams is a state employee who works for the Department of Human Services as a program consultant triggered allegations that his dismissal might be partly influenced by Gov. Tim Walz. Walz is a staunch critic of Musk, previously stating that the falling price of TSLA stock gives him a “boost” in the morning.

As noted in a report from The Minnesota Star Tribune, Moriarty’s decision was so controversial that she was asked about the matter on Wednesday. In response, the attorney argued that her office made the decision outside of any political consideration. “We try to make decisions without really looking at the political consequences. Can we always predict how a story will be portrayed in the media or what people will say? No,” Moriarty stated.

Advertisement

Actually Charged

As noted by the Tribune, Moriarty has made arguments around the fact that Adams was a first-time offender, even if he opted to deface six separate Teslas. But even this argument has become controversial since Moriarty recently charged a 19-year-old Robbinsdale woman with no criminal record with first-degree felony property damage after she allegedly keyed a co-worker’s car. The damage incurred by the 19-year-old woman was $7,000, substantially less than the over $20,000 damage that Adams’ actions have caused.

Cases surrounding felony first-degree property damage are fairly common, though they require the damage to be over $1,000. The 19-year-old’s damage to her co-worker’s car met this threshold. Adams’ damage to the six Teslas he vandalized also met this requirement.

When Moriarty was asked about her seemingly conflicting decisions, she noted that her office’s primary goal was to hold the person accountable for keying the vehicle and get restitution to the people affected. She also noted that her office tries to avoid convictions when possible since they could affect a person’s life. “Should we have treated this gentleman differently because it’s a political issue? We made this decision because it is in the best interest of public safety,” she noted.

Continue Reading

News

Tesla faces emission credits tax in Washington state

House Bill 2077 taxes emissions credits, mainly hitting Tesla. Lawmakers expect $100M/year from the taxes.

Published

on

(Credit: Tesla)

Washington state lawmakers are advancing a bill that would tax Tesla’s emission credits, targeting profits under the state’s clean vehicle policy. Lawmakers who support the bill clarify that the Tesla credit tax is unrelated to Elon Musk.

HB 2077, introduced in mid-April, seeks to impose a 2% tax on emission credit sales and a 10% tax on banked credits. The bill primarily affects Tesla due to exemptions for companies with fewer credits.

In 2022, Washington’s Department of Ecology mandated that all new cars sold by 2035 be electric, hydrogen-fueled, or hybrids, with 35% compliance required by next year. Carmakers selling more gas-powered vehicles can buy credits from companies like Tesla, which sells only electric vehicles.

A legislative fiscal analysis projects taxes on those credits would generate $78 million in the 2025-27 biennium and $100 million annually thereafter. About 70% of the taxes will be allocated to the state’s general funds, and the rest will help expand electric car infrastructure.

Advertisement

HB 2077 passed the state House eight days after its introduction and awaits a Senate Ways and Means Committee vote on Friday. At a House Finance Committee hearing, supporters, including union and social service advocates, argued the tax would prevent cuts to state services.

House Majority Leader Joe Fitzgibbon emphasized its necessity amid frozen federal EV infrastructure funds. “We didn’t have a budget crisis until this year. And we didn’t have the federal government revoking huge amounts of federal dollars for EV infrastructure,” he said.

Tesla’s lobbyist, Jeff Gombosky, countered that the proposal “runs counter to the intent” of the state’s zero-emission policy. Rivian’s lobbyist, Troy Nichols, noted a “modest” impact on his company but warned it could undermine the EV mandate. Kate White Tudor of the Natural Resources Defense Council expressed concerns, stating, “We worry it sets a dubious precedent.”

Fitzgibbon defended the tax, noting Tesla’s dominant credit stockpile makes it “one outlier” that is “very profitable.” “That’s the kind of thing legislators take an interest in,” he said. “Is it serving the interest of the public for this asset to be untaxed?”

With the legislative session nearing its end, the bill remains a key focus in budget talks in Washington.

Advertisement
Continue Reading

Trending