Connect with us

News

Tesla Model S Plaid fire: Strange observations and claims to date

Credit: Gladwyne Volunteer Fire Company/Facebook

Published

5 years ago

on

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. 

Credit: Gladwyne Volunteer Fire Company

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. 

Advertisement

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. 

Credit: Gladwyne Volunteer Fire Company

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. 

Advertisement

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. 

Advertisement

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.

Related Topics:

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

News

Tesla responds to Robotaxi skeptics with a massive move in Austin

Published

20 minutes ago

on

June 3, 2026

By

Credit: @AdanGuajardo/X

Tesla has responded to the skeptics of its Robotaxi program by launching a massive expansion of the unsupervised program in its initial rollout city of Austin.

The company’s geofence, the enabled area of operation for rides, now covers the entire Austin Metropolitan area, an incredible move just days after media headlines attempted to discredit the ride-hailing service.

Those who have access to the Tesla Robotaxi app on their smartphones can now request a ride in any portion of the Austin Metro area. The company confirmed this on the social media platform X:

This is Tesla’s fifth expansion of the geofence, with the others occurring in July, early August, late August, and late October 2025. It has remained at that size since October 26, but Tesla has now more than doubled that size.

It is now covering the entire area, including suburbs like Pflugerville and Manor, as well as I-35 highways, Gigafactory Texas, and the Austin-Bergstrom Airport.

The move comes just days after various media outlets highlighted the small fleet size of Tesla’s Robotaxi fleet in Austin, something that is a reasonable criticism but an understandable move on the company’s part to prioritize safety.

Tesla expands Robotaxi geofence, but not the garage

Tesla has expanded its Robotaxi geofence many times, but its fleet has remained at a relatively conservative size as the company continues to push safety as its most crucial metric.

The latest expansion is a key indicator of Tesla’s comfort level to expand the ride-hailing service. The move shows Tesla is scaling unsupervised autonomy, as it demonstrates that the company’s Full Self-Driving system has reached sufficient reliability for a broader real-world deployment, which is something the company has worked on extensively.

It also shows Tesla is game for a competition with its rivals in the autonomous ride-hailing sector. Tesla has often matched or exceeded competitors like Waymo in coverage area, despite its smaller fleet. This step highlights Tesla’s iterative, data-driven progress toward a high-margin, app-based Robotaxi network.

It’s not the absolute largest area expansion ever, but achieving full unsupervised operations across a major metro is a key moment in the Robotaxi story. It shifts the program from limited pilot/testing toward a more mature commercial service, while gathering the miles needed for faster growth.

Continue Reading

News

Tesla improves Dashcam playback with awesome addition

Published

19 hours ago

on

June 2, 2026

By

Image Credit: The Kilowatts/Twitter

Tesla has improved Dashcam playback with an awesome new addition, as the company has launched a web-based version that is potentially easier to navigate and operate.

The tool is available at dashcam.tesla.com and will be enabled as your vehicle receives the 2026.20 Software Version. Clips that are captured by your Tesla will be available on the Online Dashcam Clip Viewer once the files on your car’s storage drive are encrypted.

Not a Tesla App first noticed the new feature, and states that once your Tesla updates to 2026.20, the car will automatically protect the clips with an encryption key that is uniquely tied to your owner account.

The web-based viewer should be easier to operate for most. All you will do is head over to dashcam.tesla.com and log in using your account credentials.

Ensure your vehicle is updated to 2026.20 in order for the web-based viewer tool to fetch your vehicle’s saved dashcam clips.

Currently, only a small percentage of owners are updated to this, so it may be a couple of weeks until a majority of owners in the fleet are able to access this feature.

Watching Dashcam clips on the Tesla smartphone app is quick and convenient, as they can also be easily downloaded and stored right on your smartphone.

However, the clips are sometimes tougher to navigate, and in order to get details like self-driving activation, speed, and turn signals, owners have to screen record the Tesla app and crop out the rest of the screen.

It could also be a massive storage saver as you’ll be able to download the Dashcam clips from the online viewer and save them to your laptop, desktop, a flash drive, or even an external hard drive. This will keep all your clips in one place.

Continue Reading

News

Tesla Full Self-Driving attempts 150-mile stress test: the good and the bad

Published

22 hours ago

on

June 2, 2026

By

Credit: TESLARATI

I recently took my Tesla Model Y running Full Self-Driving (Supervised) v14.3.3 over 150 miles on the Pennsylvania Turnpike in an effort to truly put the system under a stress test. There were a lot of good moments, and some bad, but overall, Full Self-Driving impressed me.

Last Thursday, I decided it was time to visit the Flight 93 National Memorial near Shanksville, PA. I go a few times a year, and it was a beautiful day. Others have taken some pretty lengthy drives using FSD, but I haven’t had the opportunity to really do something lengthy in quite a few months on an older version. I decided it was the perfect opportunity to try some things out.

I recorded the entire ride there on a GoPro, edited to highlight the crucial moments, and shared them on our social media accounts. If you want to watch them, I’ll share them throughout the piece, but I did not get to do a real breakdown of what I felt about its performance.

Overall Thoughts

I realize it is probably better to do a summation of its performance toward the end of the piece, but I feel like it is also reasonable to lead with this because I was overly impressed with how well it handled everything. The only moments where I felt a little bit of reason to touch the wheel, at least while traveling on the Turnpike and Rt. 30, were due to other drivers and their behaviors.

I have taken many drives to the Memorial over the past several years, and although it’s not incredibly long, it is a tiring drive. It’s about five hours both ways, close to 300 miles, and I think most of the exhaustion comes from the toll of sitting in the car and then visiting something that is pretty heavy to take in.

This was the first time I’ve ever taken the ride and not felt like I needed to avoid my vehicle after I got home. In the past, I could not even think about driving after I finally arrived at my house, but this was simply different.

It was nice to have something else take the drive for me, while I still had the freedom to take over if I chose to. It made the entire trip more enjoyable.

Full Self-Driving Recognizes Lane-Ending Arrows on Road

After traveling in the fast lane for a little while, FSD noticed the arrows on the road indicating the lane was coming to an end ahead. The car was also in the process of making a pass on a slower vehicle in the middle lane, but aborted this maneuver and backed off to get behind the vehicle.

I was really impressed by this because I thought that the car would absolutely try to make the pass, only to get in front of the other car, and then slow back down to 75 MPH:

Full Self-Driving Notices Veering Tractor Trailer, Adjusts Lane Positioning

My two rules of the road are never cruise in the fast lane and never drive next to a tractor-trailer. This clip is a perfect example as to why.

FSD v14.3.3 recognized this tractor-trailer attempting to change lanes while we were still next to it. The car shifted its lane positioning to the shoulder slightly to make room for the merging semi, executed the pass safely, and on we went.

I will admit this one made me a little nervous, but more so because of the 18-wheeler, and not because of the Tesla:

Full Self-Driving Follows the Rules of Tunnel Travel

Many people who are not familiar with Full Self-Driving and its capabilities are pretty limited in what they know about the really simple things it does well. Part of supervising FSD is being aware of things it might make mistakes with, and anticipating maneuvers it might want to make at the wrong time.

Entering the Blue Mountain Tunnel on the Turnpike, I was ready for FSD to attempt to get back into the right lane after making a pass on a tractor-trailer, but I was pleasantly surprised. Several signs outside the tunnel advise drivers to stay in the lane they’ve chosen while driving through the tunnel; this eliminates the possibility of an accident caused by lane changes, which would impede traffic on a crucial logistics route.

I was happy to see that Tesla Full Self-Driving v14.3.3 did not make this mistake:

Full Self-Driving Navigates Toll Plazas with Ease

I was interested to see how FSD would handle toll plazas, including the speed at which it would travel through them, and whether it would stop on the Turnpike at these booths, which have since been transitioned to a “Toll by Plate” system, which mails you a bill.

It was flawless:

Full Self-Driving Still Struggles with Parking from Time to Time

Since I took delivery in late August, I’ve never had a single instance of my Tesla struggling to park at a Supercharger. Other spots at the mall, market, or gym are another story.

This was the first time it did such a terrible job of backing into a spot. This required me to take over and manually park at another charger:

Full Self-Driving Gets Confused After Arriving at Its Destination

This was the first time I have ever experienced FSD getting confused and just circling the lot. The navigation continued to reroute to try to resolve the issue, but after four laps, I decided it was time to overtake the car’s controls and park manually:

This was a baffling behavior that I truly couldn’t explain. Other owners communicated that they have also experienced this issue.

Final Thoughts

I am so incredibly impressed by FSD that it has really made traveling stress-free. The two issues related to parking were not ideal, but to be fair, I usually take over when arriving at parking lots. However, this shortcoming is something Tesla has to make some serious progress with, because parking has truly stumped FSD at times.

Solving that will be a major breakthrough for autonomy, but Tesla has struggled with it for some time.

All in all, FSD v14.3.3 is unbelievably accurate and handles many of the more stressful maneuvers with ease, one of them being avoiding merging traffic on highways, which was shown above.

Some things that would be great to see improvements on are parking, Speed Profiles, which are relatively tough to adjust (I stayed in Standard for the duration of this drive), and, of course, navigation.

Continue Reading