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

Photo credit: Steven Xu

Advertisement
-

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.

Advertisement
-

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.

Advertisement
-

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

Advertisement
-

"I write about technology and the coming zero emissions revolution."

Advertisement
Comments

News

Tesla Model Y L gets suspension complaints in over odd issue China

Published

on

Credit: @TeslaNewswire/X

The Tesla Model Y L is arguably the most hyped trim of the all-electric crossover, other than the Performance configuration that comes with white-knuckle speed and sports car-level handling.

However, it is not all perfect. Tesla owners in China who took delivery of the Model Y L, denoted with an L to highlight its longer wheelbase, are experiencing what they are referring to as “collapsing” of the rear wheels, as suspension issues appear to be an issue with some of the builds.

The gap between the wheel arch and tire has narrowed to the point that “not even a single finger” could fit, according to a report from Car News China. The failures are not tied to a specific mileage, as one owner said that after just 9,000 kilometers (5,600 miles), they noticed the suspension issue when their car was fully loaded.

Advertisement
-

Another one had the issue at 30,000 kilometers (18,640 miles) and noticed that the wheel gap shrank to two fingers, so not as drastic as the person who reported a similar issue at 9,000 km.

Tesla Model Y L is gaining momentum in China’s premium segment

Along with the visual recognition of the issue, others are saying the sagging is causing abnormal wear on the inside of the tires. Extra weight and instant torque already provide additional stress on the tires in electric vehicles during normal operation, so it is no surprise that this is another complaint.

There has been no recall issued by Tesla, and the company has not yet publicly acknowledged the issue.

Some are suggesting that owners use a “finger test” to self-diagnose whether there is an issue with the suspension. There should be four fingers between the tire and the wheel well; anything less than that starts to get dicey.

Advertisement
-
Continue Reading

News

Tesla Cybercab event gains steam ahead of massive launch

Published

on

Credit: TechOperator | X

Tesla is starting to truly tease and hype its groundbreaking Cybercab event, which takes place tomorrow in Austin, Texas. It will be the first time members of the public will be able to ride in a Cybercab, a vehicle without any manual controls, on public roads.

Tesla has been dropping some hype on X over the past several days, but this morning, the excitement has truly started to build up for the event. Although Cybercab has been unveiled before, this is truly Tesla’s announcement that it is ready to start offering autonomous rides for public passengers in its new ride-hailing-geared vehicle for the first time.

The hype has started with a variety of different social media posts that are a true indication that Tesla is preparing for something big. Teasing so much of the potential of Cybercab, including its ability to truly revolutionize how people hail rides for local travel, is what the big idea for the event entails. The time that many Tesla owners, fans, and investors have been waiting for is potentially here:

The event has remained slim on details. Even invitees are still awaiting true details about what the event will entail, where they’ll go, and what is in store for the evening. This is pretty typical for an event run by Tesla; they keep things under wraps for the most part until the very last minute.

Advertisement
-

However, there is no secret about what the real intention of Tesla is for this event: it is going to be a huge reveal party for a vehicle that has no steering wheel and no pedals. It is a truly massive step for the company moving forward.

Speculation persists as to whether this is going to be an event that simply announces that rides will begin with the Cybercab, or it will be something more substantial. Tesla has said in the past that they plan to sell the Cybercab to the general public in what could become a great way to earn passive income by adding it to a more global fleet of Robotaxi-geared vehicles.

Tomorrow, the show begins in Austin, and the Cybercab goes live at some capacity; we just don’t know exactly how quite yet.

Advertisement
-
Continue Reading

News

SpaceX tells the FCC that Starship Flight 14 is going to orbit

SpaceX filed with the FCC for Starship Flight 14, its first true orbital launch attempt.

Published

on

By

SpaceX has asked the Federal Communications Commission for permission to fly Starlink terminals during Starship’s fourteenth flight test, and the filing lays out a genuine trip to orbit, something the program has never attempted.

Every Starship flight so far, including Flight 13’s successful splashdown in the Indian Ocean on July 24, has flown a suborbital arc that ends with the ship reentering the atmosphere within the same hour it launches. The FCC paperwork describes a mission profile built around an actual orbital insertion instead.

The payload is the other half of the story. Flight 13 carried 20 production Starlink V3 satellites, but because that mission never reached orbit, the satellites reentered along with the ship rather than joining the constellation, something Teslarati covered in detail after SpaceX released footage shot from one of those satellites as it drifted away from Starship in space. Flight 14 is designed to close that gap. If the orbital insertion holds, the roughly 20 V3 satellites onboard would separate into an operational orbit and could eventually go into service, each one rated for about 1 terabit per second of downlink capacity by SpaceX’s own account.

SpaceX announces new Starbase for ‘thousands of Starship launches annually’

Elon Musk first flagged the orbital attempt during SpaceX’s August 4 earnings call, the company’s first as a public entity following its June IPO under the ticker SPCX. He also floated catching the ship with the Starbase tower on the same flight, an idea he walked back on August 20, saying the catch attempt would more likely come “in a few months,” as Teslarati reported at the time. Flight 14 will instead target a splashdown for the ship in the Indian Ocean, the same recovery method used since Flight 12.

Hardware has been catching up to the ambition. Booster 21 completed a full 33-engine static fire on August 28, and Ship 41 finished its own six-engine test the week before. An airspace briefing circulated to pilots on August 20 listed September 15 as the target date, later than the end of August window Musk mentioned on the earnings call, though SpaceX has not confirmed a launch date publicly and Starship schedules routinely slip while hardware and FAA paperwork line up.

Advertisement
-

The FCC filing itself does not guarantee a launch date. It covers communications authority, and not flight readiness, considering SpaceX still needs Ship 41 fully stacked and cleared by the FAA before Flight 14 can fly. But the filing is a real marker of intent and it puts a specific regulatory process behind what had so far only been Musk’s word on the earnings call.

Continue Reading