News
Tesla Model S Plaid totaled by Service Center employee, leaving owner without answers
Update 9/9/22 12:32 P.M. EST: Jeff contacted me personally and told me Tesla has officially shipped a Model S Plaid identical to his now-totaled vehicle. “I just got a call from Tesla, a clone of my Model S Plaid is on the truck heading for Texas as I text you today.”
A $155,000 Tesla Model S Plaid was totaled several days after the owner dropped the vehicle off for a Service appointment. Now, the owner is attempting to find answers.
After dropping his Model S Plaid with only a few thousand miles off at the Plano, Texas Tesla Service Center on Wednesday, August 24, owner Jeff said he received a call on Tuesday, August 30, from an employee. “We have some bad news,” Jeff heard over the phone. “Your car was totaled.”
“I thought it was a joke,” Jeff told Teslarati in an interview. “I found out very soon it was not a joke.”
After arriving at the Service Center the next day, on Wednesday, August 31, Jeff found his black Model S Plaid in the parking lot. The rear passenger door smashed in, and visibility into the vehicle was limited due to many airbags in the car being deployed. The vehicle had been t-boned by another car traveling just two blocks from the Service Center, located at 5800 Democracy Drive in Plano. The repair had already been completed and an employee was driving the vehicle around to ensure it was completed properly.
- Credit: Teslarati
- Credit: Teslarati
However, the driver of the Model S Plaid, a 31-year-old employee of the Plano Service Center, failed to yield the right of way at a stop sign and was hit by another car. The Model S Plaid was totaled in the accident.
Initially, Jeff was interested in receiving a new car, of course, and there happened to be an exact match of what his Plaid Model S once was at another showroom in the State. He was offered that vehicle on Wednesday, but by Thursday, that had changed. Tesla said they would likely go through insurance, meaning it would take nearly three weeks to get Jeff his vehicle.
The Legalities of the Situation
Teslarati spoke to insurance experts and liability attorneys, who told us the situation in which the vehicle was totaled and determining liability is what truly matters. The fact that this is a customer’s car and an employee crashed it is irrelevant until liability is determined.
We obtained the police report through the City of Plano, which revealed the employee at the Tesla Service Center was at fault. Jeff also told us that when he spoke to the employee driving the vehicle at the time of the accident, they admitted that the accident was his fault.
The report states that the driver of the Model S was officially charged with Failure to Yield the Right of Way at a Stop Sign. The investigating officer describes the accident in the report:
“UNIT 1 WAS STOPPED AT A STOP SIGN IN LANE 2 E/B DEMOCRACY DRIVE FOR PARKWOOD BLVD. UNIT 1 THEN PROCEEDED THROUGH THE INTERSECTION. UNIT 2 WAS N/B PARKWOOD BLVD IN THE RIGHT LANE. DUE TO UNIT 1 FAILING TO YIELD RIGHT OF WAY AT A STOP SIGN TO UNIT 2, THE FRONT END OF UNIT 2 STRUCK THE RIGHT BACK QUARTER OF UNIT 1.”
Illustration of the accident: Unit 1 is the Tesla Model S, while Unit 2 is the Audi A5. Unit 1 is the vehicle at fault, City of Plano officials told Teslarati. (Credit: Teslarati)
The report, obtained by Teslarati, shows there was a second occupant in the Tesla at the time of the crash. The driver is 33. The passenger is 31. Additionally, the Audi A5 that collided with the Tesla was being driven by a 62-year-old who was taken to Plano Presbyterian Hospital.
What’s Next
Tesla has been tight-lipped to Jeff, saying they would be in touch with him regarding the accident within the next three weeks. Tesla may have been attempting to determine liability as its employee who was driving the vehicle may not necessarily be responsible for the accident, especially considering he was t-boned while navigating through an intersection. However, the report filed by the investigating officer determined that the driver of the Tesla was at fault, and the fact that the employee also expressed to Jeff that the accident was his fault would eliminate Tesla’s need to determine this.
Jeff said Tesla has not offered a loaner or a formal replacement vehicle currently, which makes his situation much more complicated. Teslarati reported last month that Tesla had abolished its policy of offering loaners and Uber credits for some service appointments. However, Jeff’s vehicle is totaled, he is without a replacement, and the accident did not happen while he was driving the car, or even in possession of the Model S Plaid.
As of Tuesday, September 6, Tesla has yet to contact Jeff regarding the accident or any information on a replacement vehicle.
I’d love to hear from you! If you have any comments, concerns, or questions, please email me at joey@teslarati.com. You can also reach me on Twitter @KlenderJoey, or if you have news tips, you can email us at tips@teslarati.com.
Elon Musk
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
News
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.

