Keyboard shortcuts are available for common actions and site navigation.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
1/ Follow through to the end of this thread. The progression here is instructive. It begins with the crash and fire of a Model X on March 23 in San Francisco. Unfortunately it ends in tragedy for the driver. $TSLApic.twitter.com/MLNObVXSf5
2/ $TSLA releases a statement on March 27. Says it is unclear whether Autopilot was on at the time of the crash. Seems to imply the highway situation was partially to blame for the severity of the accident. Quotes NHTSA on Autopilot being 40% more safe.pic.twitter.com/uednfvITGZ
3/ A few days later, after market on Friday of Easter weekend (March 30), $TSLA puts out a statement confirming Autopilot was in fact engaged. The language around the driver's culpability raises some eyebrows. More highway condition stuff. And the 40% more safe quote again.pic.twitter.com/xgKVBAivw5
4/ Literally minutes after the official $TSLA statement, this is tweetedpic.twitter.com/8WNHXZYOy3
5/ On April 1, the NTSB let's it be known via the Washington Post that it is 'unhappy' with $TSLA disclosing details of the accident before the investigation is complete. Officials are quoted by name and on the record.pic.twitter.com/0JGIth2xkR
6/ The next day, a giant middle finger to the NTSB via Twitter. You can disagree with my assessment, but let's call it what is was. Proclaims the NHTSA as the real regulator in charge. $TSLApic.twitter.com/3Bn0X1gj4y
7/ On April 10, In response to a heartbreaking interview given by the widow of the deceased on TV, $TSLA releases a strongly worded statement that more overtly blames the driver. The lack of empathy in this statement catches attention.pic.twitter.com/U6SOLqoFsr
8/ On April 11, the chair of the NTSB calls to tell $TSLA that it has been removed from the investigation. Apparently, Elon hangs up on the chair. The public is, for a day at least, unaware that this conversation has occurred.pic.twitter.com/JCS5FWJkUh
9/ The next day, April 12, $TSLA proclaims via the media that it has withdrawn from the NTSB investigation. It is pretty hard to characterize this as anything other than an overt and knowing misrepresentation of the facts. This headline doesn't last long nor age well.pic.twitter.com/nKoJTgymdD
10/ Hours later, the chair of the NTSB corrects the record via a formal press release, and makes public the letter it sent $TSLA from Tweet 8 above. To say this is unusual would be an understatement.pic.twitter.com/U9f3ok3cC7
11/ Later that evening, in what has to be among the most bizarre and self-destructive official statements in the history of corporate PR, $TSLA releases this...pic.twitter.com/OwXr95u4rZ
12/ On April 25, it is reported that Jim Keller, head of autopilot, has left $TSLApic.twitter.com/kIExuqraAc
13/ On May 2, the NHTSA proactively points out that the 40% statistic so often cited by $TSLA is not something they stand behind.pic.twitter.com/Fn0FLz185X
14/ On the May 3 earnings call, Elon berates reporters again with respect to Autopilot. If you read the full commentary, you'll see the threads of the previous PR statements $TSLApic.twitter.com/l3iFiTsX97
15/ On May 8, a crash and fire of a $TSLA Model S in Florida leads to two teens dying in what can only be described as a horrific tragedy.pic.twitter.com/zoGD9BJ55Z
16/ The next day, it is reported that the NTSB will investigate this $TSLA crash as well.pic.twitter.com/vghRbmwpPH
18/ On May 11, a $TSLA crashes into a stationary fire truck in Utah. Reports are that the car did not brake whatsoever prior to impact. Thankfully, the driver survived.pic.twitter.com/ji6P4JuJxh
19/ The WSJ breaks that Matthew Schwall, the key interface between $TSLA and the NTSB and the NHTSA, has left the company.pic.twitter.com/GI51TYeKjU
20/ Just today, $TSLA agains claims it is unclear whether Autopilot was engaged in the Utah accident. Time will tell I guess.pic.twitter.com/QhOGH4GBQS
20/ If you've made it to the end of this thread, it should be pretty clear what's likely about to happen. $TSLA
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
