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.
News
SpaceX completes another secret Pentagon launch, adding to suspected Starshield buildout
SpaceX launched the classified USSF-385 mission from Vandenberg, landing its booster on a tenth flight.
SpaceX launched another classified mission for the U.S. Space Force from California early Saturday morning, and the Falcon 9 booster that carried it landed on a drone ship in the Pacific for the tenth time. The USSF-385 mission lifted off from Space Launch Complex 4E at Vandenberg Space Force Base at 7:00 a.m. PT.
Booster B1100 touched down on Of Course I Still Love You roughly eight and a half minutes after liftoff. It was the booster’s tenth flight and tenth successful landing, following the NROL-95 national security mission and eight Starlink launches. Its previous flight, a Starlink Group 15 mission on August 22, came just 35 days earlier. SpaceX ended its livestream shortly after the landing, which is standard for classified payloads, and neither the company nor the Space Force has said what the rocket carried.
Watch Falcon 9 launch the USSF-385 mission from pad 4E in California https://t.co/CAdbx85Ydy
— SpaceX (@SpaceX) September 26, 2026
USSF-385 is the fourth Space Force launch from the same Vandenberg pad in roughly six weeks, following USSF-366 on August 15, USSF-153 on September 10, and USSF-259 on September 17. When SpaceX flew USSF-366 in August, independent trackers noted that the rocket’s stage drop zones matched SpaceX’s Starlink Group 15 missions, pointing to Starshield, the government version of the Starlink satellite bus. The Space Force later cataloged 23 satellites after both USSF-366 and USSF-153, while USSF-259 placed 17 satellites into a different orbital plane, per KeepTrack. Launch databases describe USSF-385 the same way, though the payload remains officially unidentified.
The cadence lines up with the contracts, because in July, the Space Force awarded SpaceX $1.6 billion in task orders for 18 Falcon 9 missions from Vandenberg through the end of 2027. SpaceX also holds contracts to build pieces of that same network, which pushed its Pentagon contract total for 2026 past $8 billion.
Saturday’s flight was also the sixth and final Falcon 9 launch from Vandenberg in September, according to Spaceflight Now, while only one Falcon 9 flew from the East Coast this month as SpaceX shifts its Florida infrastructure toward Starship. Launch trackers list it as SpaceX’s 112th mission of 2026 and the 108th Falcon 9 flight of the year, with SLC-4E turned around about six and a half days after its previous launch.
The West Coast pad will not stay quiet for long, considering SpaceX has another Starlink mission scheduled from SLC-4E on September 30. Meanwhile, in Texas, the company is two days away from Starship Flight 14, which is targeting Monday at 7:15 a.m. CT for the vehicle’s first attempt to reach orbit.
News
Tesla hints at new Roadster design in surprise clip
Tesla ended its Semi event with a Roadster teaser revealing a new front light bar.
Tesla closed out its Semi event in Nevada on Thursday night with a nod to its own history, dropping a short Roadster teaser that suggests the production car will look noticeably different from the prototype first shown in 2017.
“We can’t have a Semi event without the Roadster,” Tesla engineering executive Lars Moravy told the crowd before the clip played. The line was a deliberate callback. Tesla first revealed the next generation Roadster in November 2017 by driving it out of the back of a Semi trailer at the truck’s original unveiling in Hawthorne, California.
The new video opens on trailer doors swinging apart in the dark. A thin white light bar glows across what appears to be the nose of the car, Tesla and SpaceX logos flash over the frame, and the Roadster name appears before the clip ends on “See you next week.” Tesla posted the nine second clip on X after the livestream wrapped.
See you next week pic.twitter.com/BT52bGVxFu
— Tesla (@Tesla) September 25, 2026
The light bar is the most concrete design detail so far. The 2017 prototype used two separate curved headlamp pods, while a connected front light strip would bring the Roadster in line with the Cybertruck, Cybercab, Semi, and refreshed Model Y. Sawyer Merritt was among the first to point out what looked like part of a SpaceX logo in the video, something Tesla has not addressed.
That logo fits the buildup around the optional SpaceX Package, which Elon Musk has long said would use cold gas thrusters to improve acceleration and possibly allow the car to briefly leave the ground. Tesla’s “Go for launch” post on September 12 set the October 1 date, and invitations sent to reservation holders place the event in Waco, Texas, at 8:30 p.m. Eastern. Waco sits roughly 20 minutes from SpaceX’s McGregor rocket test site, where the FAA has put a temporary flight restriction in place from September 18 through October 2, covering a 1.5 nautical mile radius from the surface up to 10,000 feet.
Tesla is also taking money ahead of the reveal. The company reopened Roadster reservations earlier this week with a $5,000 refundable card payment, followed by a $45,000 wire transfer due within 10 days. That puts buyers at $50,000 committed before Tesla has published a price.
The original pitch set a high bar: 0 to 60 mph in 1.9 seconds before any upgrades, 620 miles of range, a top speed above 250 mph, and production in 2020. That timeline has slipped repeatedly, and Tesla has since pointed to production at Gigafactory Texas no earlier than 2027. The company has said next Thursday’s event will include pricing, specifications, and production targets, the three details original reservation holders have been waiting on for nearly nine years.
Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.
The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.
Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.
That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.
Elon Musk’s reply to the delay was a single word: “Sigh.”
Sigh
— Elon Musk (@elonmusk) September 25, 2026
Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.
Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.
The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.
An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.
Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval
The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.
Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.
SpaceX completes another secret Pentagon launch, adding to suspected Starshield buildout
Tesla hints at new Roadster design in surprise clip
