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 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 is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
