Connect with us

News

TX fire chief slams inaccurate Tesla crash coverage with firsthand details on Model S fire

Credit: Reuters/Twitter

Published

5 years ago

on

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. 

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. 

Advertisement
-
-

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.

Advertisement
-
-

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.

Related Topics:

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

News

Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Published

8 hours ago

on

August 2, 2026

By

Credit: Teslarati

Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.

Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.

For now, here’s everything I noticed with v14.3.7:

Overall Improvement

Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.

The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.

However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.

I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.

Advertisement
-
-

The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.

Manual Signal Override is More Responsive

On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.

The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.

Parking Lot Performance

Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.

The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:

Advertisement
-
-

 

I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.

Full Self-Driving Averts Disaster

A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:

Advertisement
-
-

There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.

However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.

Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.

It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.

What Needs to Improve

Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps

On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.

However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.

I even tried scrolling down into Sloth quickly, but I ended up just taking over:

Advertisement
-
-

A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.

Navigation

Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.

Auto Wipers

Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.

You can watch our full review of Tesla Full Self-Driving v14.3.7 below:

Advertisement
-
-

Continue Reading

Elon Musk

SpaceX’s biggest test yet arrives this week and it’s not a rocket launch

Published

1 day ago

on

August 1, 2026

By

SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.

The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.

Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.

SpaceX scores another massive Pentagon deal to support military satellites

Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.

The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.

As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.

Advertisement
-
-
Continue Reading

Elon Musk

SpaceX’s Starship just got filmed by its own cargo

SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.

Published

1 day ago

on

August 1, 2026

By

SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.

The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.

The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.

Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.

Advertisement
-
-

Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.

Continue Reading