News
Tesla Model S Plaid fire: Strange observations and claims to date
Details about the Tesla Model S Plaid fire on Tuesday are starting to emerge. Similar to other dramatic electric vehicle fires, the details and observations emerging about the Tesla Model S Plaid fire are very interesting.
Accounts of the Model S Plaid fire have been shared by an EMT that reportedly responded to the incident, the chief fire officer for the Lower Merion Township Fire Department in Pennsylvania, and the lawyers representing the Model S Plaid owner.
With this in mind, it is pertinent to provide a view of what each party has stated about the incident so far. Going through each statement would potentially make it a lot easier to come up with a legitimate narrative in the future, especially as official investigations into the fire conclude. That being said, here are the accounts that have been shared on the Tesla Model S Plaid fire earlier this week.
What happened?
The Tesla Model S Plaid caught fire in Haverford, Pennsylvania on June 29, 2021. The vehicle, which was a Plaid variant based on the remains of its rear badge, was engulfed in flames when fire crews arrived. A Facebook post from the Gladwyne Volunteer Fire Company indicated that two fire engines were deployed for the incident. Firefighters were at the scene for about three hours, though the vehicle was cooled down for almost 90 minutes to ensure that the batteries were safe.
“Engine 24 with a crew of 7 arrived on scene simultaneously with Engine 25. Due to prior training classes on Tesla Vehicle Fire emergencies, Engine 24 laid a 5 inch supply line into the scene so that we could keep a continual water stream on the fire to extinguish the fire and cool the batteries down to ensure complete extinguishment. Engine 24 and Engine 25 both deployed hand lines to extinguish the fire, each maintained a dedicated water source and continued to cool the vehicle down for almost 90 minutes. Firefighters were on scene for just over 3 hours dealing with this emergency. Nobody was hurt in the incident, and both crews worked hard in the high heat/humidity to mitigate the incident,” the Gladwyne Volunteer Fire Company wrote.
Interestingly enough, this statement, as well as the Gladwyne Volunteer Fire Company’s Facebook post about the Model S Plaid fire has been taken offline. A look at the fire department’s Facebook page and its official website would reveal that the post about the Tesla fire has now been deleted.
A First Responder’s Account
As the story of the Model S Plaid fire gained ground, the incident started to attract a lot of attention on social media as well. On Reddit, u/wilyson, who claimed to be an EMT who responded to the fire, noted that the report they received about the incident was downright strange. According to the EMT, the person who reported the fire stated that the car was driving uphill without an occupant while it was ablaze. The owner was reportedly nowhere to be found. This was a rather dramatic image, and it promptly fueled speculations among the anti-EV crowd about “self-driving” cars catching fire.
Quite understandably, the EMT noted that he could not provide many details as the police are not releasing more information yet. That being said, the EMT later noted that car fires are very common and that electric vehicles are actually incredibly safe.
The Fire Chief’s Account
As noted in a CNBC report, chief fire officer for the Lower Merion Township Fire Department in Pennsylvania Charles McGarvey stated that the Tesla Model S caught fire on Tuesday while the driver was still at the wheel of the vehicle. According to the fire chief, firefighters eventually removed the Model S Plaid to a complex to safely store it overnight. The vehicle’s owner had since taken the remains of the vehicle from the facility, as per McGarvey, and will have the car investigated independently to determine the cause of the blaze.
-
The fire chief also stated that his teams had been in touch with Tesla and that some information about the incident should be made public soon. A National Highway Traffic Safety Administration spokesperson also noted that it was aware of the incident and that it is now in touch with relevant agencies and Tesla to gather more information about the fire. “If data or investigations show a defect or an inherent risk to safety exists, NHTSA will take action as appropriate to protect the public,” the NHTSA spokesperson said. The NTSB is not conducting an investigation to date.
The Lawyers’ Account
The Model S Plaid owner’s lawyers, Mark Geragos of Geragos & Geragos in Los Angeles, and Jason Setchen of Athlete Defender in Miami, have since mobilized to share details about the incident as well. In a statement to CNBC, the attorneys stated that the Tesla owner initially noticed smoke coming from the back of the Model S Plaid. Following this, the owner reportedly tried to unlock and open the vehicle’s doors, but he ended up having to force his way out of the car as the locks seemed to malfunction. The lawyers noted that after the Tesla owner left his car, the Model S began to move on its own while flames engulfed it.
Geragos Global attorney Ben Meiselas later posted a tweet sharing an image of the burning Model S. As per the lawyer, “Our firm & @AthleteDefender represent an exec who purchased new Tesla Plaid Model S, which was 1/250 shipped. On Tuesday it spontaneously combusted. Our client was trapped & could have died. We tried reaching out to Tesla & have been ignored so far. This is car after escape.”
Interesting (and strange) details
Overall, the Model S Plaid fire in PA features a number of interesting accounts that may not necessarily line up perfectly. The EMT that initially shared details about the incident mentioned that the Model S owner was nowhere to be found. The lawyers, on the other hand, shared an image reportedly taken immediately after the owner escaped, suggesting that the Tesla owner was on the scene of the blaze. As per the Model S Plaid’s Owner’s Manual, the vehicle is also equipped with a manual door release that should make it easy for occupants to vacate the car in case of an emergency. This seems to be a bit overlooked by the owner’s lawyers, who noted that their client was trapped inside the car.
Of course, the idea of a car driving on its own uphill while being engulfed in flames is quite strange, considering that neither Tesla’s Autopilot nor Full Self-Driving suite have such features. The only function that may have worked similarly is Smart Summon, but the vehicle was burning on a public street, an area where Smart Summon should have been unavailable.
We’ll definitely keep a pulse on this incident, as well as any details that may emerge as investigations go on, so do keep Teslarati on your radar as we follow developments in this event.
Do you have anything to share with the Teslarati Team? We’d love to hear from you, email us at tips@teslarati.com.
-
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
