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.
Elon Musk
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.
An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.
Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.
The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.
Footage of the plane crash from earlier today | #ONLYinDADE pic.twitter.com/iGoOtnd6cD
— ONLY in DADE (@ONLYinDADE) September 6, 2026
Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.
The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.
Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.
Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
Tesla crosses major Unsupervised Self-Driving milestone
