News
TX fire chief slams inaccurate Tesla crash coverage with firsthand details on Model S fire
Immediately following the fatal Tesla crash in Texas this weekend, reports from both local and national media outlets emerged citing the statements of Harris County Pct. 4 Constable Mark Herman, who remarked that police were 100% certain that there was no one in the driver seat of the ill-fated Model S when it crashed. Herman also commented that the Tesla fire was so severe that it took over 30,000 gallons of water and four hours to extinguish the flames from the crash, and that firefighters had to reach out to the EV maker for help in battling the fire.
These statements have since been debunked (at least to some degree) by Tesla CEO Elon Musk, who noted that data logs that have been recovered so far from the ill-fated Model S indicate that Autopilot was not enabled during the crash, and that the vehicle did not have any Full Sell-Driving functions activated. Musk’s update essentially threw a wrench on the pervading narrative that Autopilot likely caused the tragic crash.
Your research as a private individual is better than professionals @WSJ!
Data logs recovered so far show Autopilot was not enabled & this car did not purchase FSD.
Moreover, standard Autopilot would require lane lines to turn on, which this street did not have.
— Elon Musk (@elonmusk) April 19, 2021
And now, even the reports about the Tesla fire have been thrown into question–by the man whose team extinguished the blaze no less. In a statement to the Houston Chronicle, Palmer Buck, fire chief for The Woodlands Township Fire Department, noted that contrary to some reports in the media, the Tesla Model S fire did not burn out of control for four hours.
Interestingly enough, Buck remarked that his team actually managed to put down the fire within two to three minutes, which was enough for authorities to see that there were occupants in the vehicle. After these first two to three minutes, it was only a matter of keeping the batteries as cool as possible by pouring small amounts of water into the damaged battery pack. Buck described the fire department’s strategy in the following statement.
“With respect to the fire fight, unfortunately, those rumors grew way out of control. It did not take us four hours to put out the blaze. Our guys got there and put down the fire within two to three minutes, enough to see the vehicle had occupants. After that, it was simply cooling the car as the batteries continued to have a chain reaction due to damage.
“We could not tear it apart or move it around to get ‘final extinguishment’ because the fact that we had two bodies in there and it was then an investigation-slash-crime scene. We had to keep it cool, were on scene for four hours, but we were simply pouring a little bit of water on it. It was not because flames were coming out. It was a reaction in the battery pan. It was not an active fire,” Buck said.
As for the rumors that the fire department had to call a Tesla hotline for tips on how to handle a battery fire, the Fire Chief stated that these reports were untrue. “We did not (call Tesla), and I do not know where (that rumor) came from. There is a chance someone else did, maybe the Harris County Fire Marshal, but we did not call (Tesla). Tesla has an emergency manual for first responders,” Buck said. He also noted that he is not aware of Tesla having a hotline for tips on how to control a battery fire.
Buck also provided some new details about the Model S crash and how the fire department was involved. According to the fire chief, the first calls about the incident did not involve reports about a car at all. Instead, initial reports were about a fire in the woods. And while the Model S fire was notable when the firefighters arrived, it only took minutes to control the blaze from the vehicle.
“The first calls that came in were a fire in the woods. Then we got at 9:30 p.m. where we got the first call when someone said, ‘I see a car in a tree, and it is on fire. They reported a car hit a tree, and it had exploded… That is when we added extra units (to the response). There is a big lake, and (the accident) was just to the left of the lake, closer to the exiting part of the street, not the end of the cul de sac. It was at an undeveloped lot.
“(The Tesla) was heavily involved in flames. When the fire was put out, it was noticed there were two bodies (inside), and they were deceased. They continued extinguishment of the woods around (the car), putting out the trees and pine needles and what have you. I was there probably five to 10 minutes after that and at that point, every once in a while, the (battery) reaction would flame and it was mainly keeping water pouring on the battery,” Buck explained, adding that this was a process recommended by Tesla in cases of burning batteries.
While a number of the initial reports about the tragic Tesla crash this weekend have been debunked by Elon Musk and now, the fire chief for The Woodlands Township Fire Department, the incident continues to attract some degree of drama. As per recent reports, Harris County Pct. 4 Constable Mark Herman has stated that investigators would be serving a search warrant on Tesla to gain all data from the ill-fated Model S. Federal regulators from the NHTSA and NTSB have also launched an investigation into the crash.
Don’t hesitate to contact us for news tips. Just send a message to tips@teslarati.com to give us a heads up.
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
