This past Saturday, news broke about a Tesla crashing into a parked tow truck and bursting into flames on a motorway in Moscow, Russia. Particularly notable about the incident was that after the initial crash, explosions racked the already burning electric car.
A number of developments have emerged about the story so far, which clarified initial misconceptions about the incident, from the make of the vehicle to the injuries incurred by its occupants. With this in mind, Teslarati has compiled this quick guide about what is currently known about this crash and its ensuing fiery aftermath.
The crash
A video of the accident taken from what appears to be a security camera showed the electric sedan passing a first stopped vehicle that had broken down and catching the corner of a tow truck that was sticking out into the adjacent lane. In a statement to CrimeRussia, Aleksey Tretyakov, the vehicle’s owner, noted that he had been traveling at 100 km/h, the speed limit in the area. The impact from the collision was enough to push the tow truck forward into the central dividing wall.
A video of the exact moment the Tesla crashed into the tow truck could be viewed below.
The make of the car
Initial reports that emerged following the accident tagged the Tesla as a Model S. With more videos of the crash’s aftermath emerging online, it now appears that the electric car involved in the accident was a Model 3, at least based on the shape of the vehicle’s taillights and headlights.
The fire
Videos of the Tesla on fire and the explosions that followed emerged on the heels of the accident. These clips, which were separate from the footage of the electric car crashing into the parked tow truck, showed a vehicle that was already ablaze. Two explosions could be seen in the videos, which resulted in parts of the electric car flying to the air.
Quite interestingly, the explosion within the vehicle seemed to have happened after the tow truck that the Tesla crashed into had been moved (the heavy vehicle does not seem to be in the vicinity when the explosions happened). As observed by Tesla Motors Club member KarenRei, the nature of the explosion in the Model 3 looked notably similar to an explosion that happens when an airbag explodes. A video of such an incident could be viewed here.
The injuries
Initial reports of the injuries that resulted from the accident pointed to the driver of the Tesla and his two children being severely injured. Russian media outlet IXBT.com, for one, noted that Tretyakov was in “intensive care” due to the crash. Later reports would prove this to be false. Speaking with CrimeRussia, the Tesla owner noted that both of his legs were broken due to the accident, but his two children were “practically not injured.”
Update: While CrimeRussia noted in its coverage of the incident that the Model 3 driver had two broken legs as a result of the crash, it appears that the news agency misquoted the Tesla owner’s statements. Vladimir Grinshpun, a native Russian speaker, noted in a message to Teslarati that the Tesla owner clearly stated during a video interview with the news agency that he had one broken leg and a broken nose due to the accident. A video of this interview could be accessed here.
A video depicting what appeared to be Tretyakov hobbling away from his vehicle as his two children walked ahead of him has also been aired on Russian media outlet Russia 24.
On Autopilot
Being a Tesla crash, it was not surprising to note that several reports promptly related the crash to the potential use of Autopilot. Discussing the incident, longtime TMC member mongo noted that since Teslas in Russia are imported through a third party, there was likely no Navigate on Autopilot support in the area. Thus, functions of Autopilot would likely be limited to basic features such as lane-keeping.
This was mentioned by Tretyakov himself, who noted that he was using a “driver-assist” feature and a “trimmed” version of Autopilot when the accident happened. The Tesla owner added that he was holding the wheel in the moments leading up to the crash, though he also admitted that he did not notice the parked tow truck on the road. Based on the video of the Tesla’s crash, it appears that either the vehicle or Tretyakov engaged the brakes just before the car hit the parked truck.
Tesla’s statement
Tesla is yet to issue a formal statement about the incident, though the electric car maker has recently published its most recent vehicle accident and fire data. Tesla notes that from 2012 – 2018, “there has been approximately one Tesla vehicle fire for every 170 million miles traveled. By comparison, data from the National Fire Protection Association (NFPA) and U.S. Department of Transportation shows that in the United States there is a vehicle fire for every 19 million miles traveled.” It should be noted that Tesla’s data set includes instances of vehicle fires caused by structure fires, arson, and other things unrelated to the vehicle, which account for about 15% of Tesla vehicle fires over this time period.
H/T JPR007 on Twitter.
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
