News
Tesla owner shares FSD purchase concerns after vandals set Model X on fire
When Tesla owner Den Dal plugged his family’s 2018 Model X Long Range at a public charger during a recent business trip to Düsseldorf, Germany, he had no idea that it would be the start of a grueling ordeal. Twenty-four hours after plugging in his Tesla, Dal was left with a burned Model X, an FSD purchase that seemed to be up in the air, and a plausible arson incident that seemingly targeted the all-electric SUV.
Den Dal had rented an apartment for his business trip to Düsseldorf which was close to a row of public chargers that his Model X could be plugged in. Unfortunately, all of the public charger’s stalls were being blocked by fossil fuel cars on that day. This resulted in the Tesla owner plugging his Model X at another public charger, which was farther away, about 600 meters from the rented apartment.
The rates of the station were notably higher than Tesla’s charges for its Supercharger Network, but the location at least had a free stall for the all-electric SUV. Dal plugged in his vehicle and went back to his rented apartment, expecting to find his Model X charged and ready to go the next morning.
What he saw was not what he expected at all. To the Tesla owner’s shock, he found his Model X torched, and the burns on the vehicle suggested that it had been deliberately set on fire. A note from the police was placed on the windshield of the all-electric SUV, notifying the Tesla owner that he should head over to the station as soon as possible.
Unfortunately for the Tesla owner, his vehicle did not have a USB drive that was linked to its Sentry Mode feature. Thus, while Sentry Mode was active during the incident, no videos were retrieved from the Model X. The police also stated that there were no local cameras around the public charging station. No other Teslas were in the area either, which may have helped if they were running Sentry Mode as well.
Based on the specifics of the incident, it does appear that the Model X was singled out and deliberately burned. In the street where the vehicle was charging, there were more than 60 cars, some of which were premium vehicles and most of which were from German automakers, yet none were touched. Dal later found out that before his Model X was set on fire, another bike parked in the same area had been torched as well. Local firefighters who responded to the scene also saw where the flames started.
Quite amazingly, the Model X remained drivable despite being burned, which suggested that the vehicle’s batteries and powertrain were still intact after the incident. Describing the vehicle’s status in a message to Teslarati, Dal noted that the interior smelled particularly bad since chemicals of the cooling system seemed to have entered the cabin, as per observations from a Tesla Service Center. Tesla has not provided an update to the Model X owner yet, though there is a pretty good chance that the vehicle may be a total loss.
Dal is a supporter of Tesla and the company’s mission of transitioning the world to sustainable energy, and he purchased Enhanced Autopilot and the Full Self-Driving suite for his Model X despite knowing that the systems’ full features will be rolled out at a later time. That being said, Dal has notable concerns about his FSD purchase after his Model X was set aflame.
The Tesla owner had purchased FSD at a time when Tesla had a discount for the suite, and as such, the system was not insured with the vehicle. From this standpoint, it appears that while the Model X may be insured, its Full Self-Driving system was not. Dal is thus concerned that his FSD purchase will not be carried over if he does purchase another Tesla, which is unfortunate considering that he has not really been able to use much of what Autopilot and Full Self-Driving have to offer yet.
Dal resides in Europe, a region where regulations have forced Tesla to essentially cripple some key features of its Autopilot and Full Self-Driving suite. This results in key FSD capabilities such as Navigate on Autopilot with automatic lane changes and Smart Summon being practically impossible to roll out unless revisions are implemented in the region’s regulations. Tesla is doing what it can to address these regulations, but in the meantime, owners such as Dal, who have purchased FSD with their vehicle, are in a limbo of sorts.
Adding insult to injury, the Tesla owner has unfortunately been subjected to some online attacks from the electric car maker’s critics since posting about his experience online. Some have accused Dal of simply trying to attract attention, while others were insisting that the Model X’s batteries combusted on their own. The former point simply lacks basic empathy, while the latter seems farfetched considering that the Model X remained drivable even after it was torched.
For now, Dal is simply hoping that Tesla could provide a resolution for his vehicle and his FSD purchase. The Tesla owner noted that he would like to acquire another Model X if his SUV is totaled, though he looks forward to hearing about an update from the electric car maker soon.
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 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 crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
