Connect with us

News

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

Credit: Gladwyne Volunteer Fire Company/Facebook

Published

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. 

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. 

Advertisement

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

Advertisement

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.

Advertisement

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

SpaceX Starship Flight 13 faces wrath of the Texas skies

SpaceX pushed Starship Flight 13 to Friday, blaming weather instead of the previous engine issues.

Published

on

By

SpaceX called off Thursday’s launch attempt of Starship Flight 13, pushing the mission to Friday because of weather tied to Tropical Storm Bertha. The company confirmed the delay on X, noting “Now targeting Friday, July 24 for Starship’s thirteenth flight test, due to weather. A key objective for the flight test is to get clear imagery from the ground of Starship’s heatshield as it flies at a higher dynamic pressure during ascent, which won’t be possible with today’s weather conditions.”

This is the second delay for Flight 13 in two weeks. SpaceX first tried to launch the mission on July 16, but the countdown ended in an automated abort at T-0 when four of Super Heavy Booster 20’s 33 Raptor engines failed to ignite. Musk said at the time that two Raptors would need to be removed and replaced, as Teslarati reported. The company spent the following week destacking Ship 40 and Booster 20, swapping engines, and running leak checks before restacking the vehicle on Pad 2 Wednesday night, according to Spaceflight Now’s live coverage.

Elon Musk debunks $52 billion SpaceX-NVIDIA GPU deal

 

Unlike the engine problem, Thursday’s delay has nothing to do with the hardware. SpaceX wants clean footage of Starship’s heat shield captured from the ground as the vehicle flies through max dynamic pressure, something the storm’s cloud cover over South Texas would not allow. The company said visibility should improve for Friday’s attempt, with the same 90 minute window opening at 5:45 p.m. CT.

Flight 13 will be the second outing for the V3 versions of Starship and Super Heavy, following their debut on Flight 12 in May. The mission carries 20 production Starlink V3 satellites, the first time SpaceX has flown operational satellites rather than mass simulators on Starship. Six of those satellites are fitted with cameras to inspect the heat shield from a different angle during ascent, giving engineers a second data source beyond the ground imagery the weather is currently blocking.

Booster 20 will attempt a boostback burn and a splashdown landing burn in the Gulf of America, while Ship 40 follows a suborbital trajectory toward a landing in the Indian Ocean. The flight plan largely mirrors Flight 12, though the booster will run a more aggressive ascent burn after max Q this time, and the ship’s heat shield includes load sensing tiles meant to measure stress at the higher dynamic pressure SpaceX is targeting.

If Friday’s attempt succeeds, Flight 13 could be the last suborbital test in the program. SpaceX is already looking to push for an orbital flight on Flight 14.

Continue Reading

Investor's Corner

Tesla stock tumbles after earnings, one of its sharpest single-day declines

Published

on

Credit: Tesla

Tesla stock (NASDAQ: TSLA) endured one of its sharpest single-day declines in years on July 23, tumbling approximately 14.5 percent and closing near $320 after opening the session around $374. The drop erased more than $140 billion in market value amid heavy trading volume and left the shares at multi-week lows.

The sell-off followed the company’s second-quarter 2026 results, released the previous evening. Tesla reported record revenue of $28.2 billion, up 26 percent year over year, driven by a Q2-record 480,126 vehicle deliveries. Energy storage deployments also rose strongly.

Tesla (TSLA) Q2 2026 earnings results: miss on EPS, beat on revenue

Yet profitability disappointed sharply. Operating income fell 57 percent to $398 million, compressing the operating margin to just 1.4 percent. Non-GAAP earnings per share came in at $0.33, well below the roughly $0.53 analysts had expected. Free cash flow turned negative by $1.1 billion as capital expenditures surged 142 percent to $5.8 billion, largely tied to accelerated spending on artificial intelligence, robotics, and autonomous systems.

The losses on capex were expected, as Tesla said it would be spending heavily in 2026.

Investors also reacted to lingering uncertainty surrounding key product timelines. During the Earnings Call, management reiterated ambitions for Robotaxi deployment and the Optimus humanoid robot, but offered limited new concrete milestones, renewing questions about execution pace that have long accompanied Tesla’s ambitious roadmap.

The magnitude of the decline places it among Tesla’s more severe one-day percentage losses since its 2010 initial public offering. Historically, the two largest single-day drops (split-adjusted) remain September 8, 2020, when shares fell 21.1 percent amid broader market volatility and valuation concerns, and January 13, 2012, with a 19.3 percent plunge during the company’s early growth struggles.

Other notable declines include an 18.6 percent drop on March 16, 2020, at the onset of pandemic-related market turmoil. Thursday’s move ranks roughly ninth on the all-time list but stands out as the steepest in more than a year.

Despite the short-term pain, Tesla’s long-term trajectory has repeatedly recovered from such volatility. The latest results underscore both the strength of its core automotive and energy businesses and the near-term costs of heavy investment in next-generation technologies.

Continue Reading

Elon Musk

Elon Musk is not happy about this Tesla Full Self-Driving approval delay

Published

on

Credit: Tesla

Elon Musk clapped back at France’s decision to withhold the approval for Tesla’s Full Self-Driving (FSD) Supervised system, projecting a clear and blunt message to French Transport Minister Phillippe Tabarot, after he publicly rejected the technology in its current form.

Tabarot outlines several concerns with Tesla Full Self-Driving in a detailed video statement, where he said, “The safety trade-offs are not yet sufficient to authorize it as it currently stands,” he said. He emphasized that FSD is not a true self-driving system and that the driver remains fully responsible.

Key issues Tabarot also brought up included allowing speeding when surrounding traffic exceeds limits and what he believes are insufficient guarantees of driver attention during complex urban maneuvers such as lane changes, intersections, and roundabouts.

While acknowledging technological progress and France’s support for autonomous innovation, Tabarot stressed that deployment must prioritize road safety. He noted ongoing technical discussions with Tesla, the Netherlands, and other European partners, with further ecosystem meetings planned for the fall.

Musk’s rebuke highlights the human cost of regulatory caution. Tesla’s latest safety reports provide compelling data supporting accelerated adoption. In the most recent 12-month period, vehicles using FSD (Supervised) recorded one major collision per approximately 5.1 million miles driven, dramatically better than the U.S. national average of one crash per 698,000 miles.

Even Tesla vehicles driven manually with active safety features outperform the average by a wide margin. These figures come from billions of real-world miles of telemetry, showing FSD vehicles involved in far fewer incidents than both manual Teslas and the broader U.S. fleet.

Critics argue Tesla’s comparisons require careful scrutiny regarding reporting thresholds and fleet demographics, yet the data consistently positions FSD as a potential lifesaver. With road fatalities remaining a leading cause of death worldwide, Musk contends that proven safer technology should not face prolonged bureaucratic hurdles.

France’s measured approach reflects the broader European regulatory caution, which many, especially Musk, have been critical of in the past. However, as autonomous systems from Tesla and competitors like Waymo demonstrate superior safety in independent studies, pressure is mounting for harmonized approvals.

Musk’s warning carries the belief that every month of delay may equate to avoidable tragedies on European roads.

Continue Reading