Connect with us

News

SpaceX Starship booster survives record-breaking 31-engine static fire

Published

3 years ago

on

SpaceX’s Starship rocket has survived a record-breaking engine test – potentially the most powerful static fire in the history of rocketry.

According to CEO Elon Musk, Super Heavy Booster 7 (B7) ultimately ignited 31 of its 33 Raptor engines. One engine was manually disabled “just before” the static fire, while the other faulty engine automatically shut down while attempting to ignite. The other 31 Raptors, however, completed a “full duration” static fire that lasted about five seconds. Musk says that even with two engines disabled, those that remained were “still enough…to reach orbit” – an excellent result despite the static fire’s imperfections.

Most importantly, Super Heavy Booster 7 survived the test without catching fire, exploding, or popping its tanks. To partially counteract the thrust of its Raptor engines, the rocket’s tanks were filled with some 3000 tons (6.6M lbs) of liquid oxygen and methane propellant. The stool-like orbital launch mount (OLM), which also survived the test in one piece, held Starship down with 20 clamps to counteract any remaining thrust. From SpaceX’s perspective, the fact alone that its only orbital-class Starship launch site survived the ordeal is likely enough for it to consider the static fire a success. But the test was much more than that.

Incinerating rocket records

Despite losing two Raptors, SpaceX still broke the all-time record for the number of rocket engines ignited simultaneously. That record was held by the Soviet N1 rocket, which launched four times with 30 NK-15 engines in the late 1960s and early 1970s. None of its test flights were successful, but N1 still set the record for the most thrust produced by a single rocket, generating up to 4500 tons (9.9M lbf) of thrust at liftoff.

Neither SpaceX nor CEO Elon Musk has confirmed it, reducing the odds that Super Heavy Booster 7 broke that historic thrust record. But it certainly could have. Each Raptor 2 engine can generate up to 230 tons (507,000 lbf) of thrust at sea level. Raptor is theoretically designed to throttle as low as 40%, or 92 tons (~200,000 lbf) of thrust. With 33 engines operating nominally at their minimum throttle setting, Super Heavy would have produced 3036 tons (~6.7M lbf) of thrust during today’s static fire – not a record.

For 31 Raptors to break N1’s thrust record, the average throttle setting would have had to be around 64% or higher – far from unreasonable. From a data-gathering perspective, a full-thrust static fire would be the most valuable 33-engine test SpaceX could attempt, but it would also be the riskiest and most stressful for the rocket and pad.

Former SpaceX executive Tom Mueller says that SpaceX broke N1’s record. Mueller is effectively the father of the Raptor engine, and likely still gets information straight from SpaceX engineers he used to work with. Still, one would expect SpaceX itself to proudly confirm as much if a rocket it built became the most powerful in history.

Advertisement
-
-

The most powerful rocket test in history?

Whether or not Starship became the most powerful rocket in history, it has likely become the most powerful rocket ever tested on the ground. The first stage of Saturn V produced around 3400 tons (7.5M lbf) of thrust during its first sea-level static fire in 1965. Likely contributing to its failure, N1’s booster was never static-fired. Other powerful rockets like the Space Shuttle and SLS use or used a combination of solid rocket boosters and liquid engines that cannot be tested together on the ground.

Unless SpaceX’s goal was a minimum-throttle static fire, Starship’s 31-Raptor static fire likely beat Saturn V’s record to become the most powerful ground test in the history of rocketry.

SpaceX’s next steps

While the 31 that did ignite appeared to perform about as well as SpaceX could have hoped, the two engines missing from February 9th’s historic Starship static fire have probably complicated the company’s next steps. To be fully confident in Starship’s ability to launch and fly a safe distance away from the launch site, SpaceX would likely need to complete a full 33-engine test. Meanwhile, Starship can’t fly until the Federal Aviation Administration approves a launch license, and the FAA could be stodgy enough to deny SpaceX a license without a perfect 33-engine static fire.

Alternatively, the FAA may accept that Starship could still safely launch and reach orbit while missing several Raptors. SpaceX could also guarantee that it will only allow Starship to lift off if all 33 engines are active, in which case a second 33-engine static fire attempt may not be necessary.

Booster 7’s historic static fire. (NASASpaceflight – bocachicagal)
A fully-stacked Starship was fully fueled for the first time in January 2023, demonstrating what the rocket will look like just before liftoff. (SpaceX)

If SpaceX is happy with Booster 7’s 31-engine test results and isn’t too put off by any pad damage the test may or may not have caused, it will likely focus on finishing Starship 24. Ship 24 will then be transported back to the pad and reinstalled on top of Booster 7. SpaceX may choose to conduct another wet dress rehearsal or a static fire with the fully-stacked Starship, but it may also deem additional testing unnecessary.

Once all those tasks are completed, Ship 24 and Booster 7 will be ready to support Starship’s first orbital launch attempt. Prior to February 9th’s static fire, SpaceX CEO Elon Musk and COO/President Gwynne Shotwell agreed that Starship’s orbital launch debut could happen as early as March 2023. After today’s test, a March 2023 launch may be within reach.

Rewatch Super Heavy Booster 7’s historic static fire below.

Advertisement
-
-
Related Topics:

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla Full Self-Driving insurance program with heavy discount expands

Published

1 hour ago

on

August 3, 2026

By

Lemonade has expanded its innovative Autonomous Car insurance program to Tennessee, giving Tesla owners in the state a substantial discount on Full Self-Driving (FSD) miles. Announced on August 3, the product offers 50 percent off every mile driven with FSD activated, positioning the digital insurer as a leader in pricing insurance around autonomous technology.

The program, marketed as Lemonade Autonomous Car insurance, uses a direct connection via Tesla’s Fleet API (with customer permission) to automatically distinguish FSD-engaged miles from manual driving. Policyholders pay a low base rate when the vehicle is stationary and a few cents per mile when moving, with the 50 percent reduction applied specifically to FSD miles.

Coverage includes standard protections such as liability, collision, comprehensive, roadside assistance, and Tesla-specific benefits like access to certified repair shops and emergency crash services. Eligible vehicles require Hardware 4, as well as recent firmware.

Lemonade first unveiled the product on January 21 of this year, describing it as a first-of-its-kind offering designed for self-driving cars, starting with Tesla FSD. It began rolling out in Arizona on January 26, followed by Oregon about a month later. Subsequent expansions brought it to Indiana in early June 2026 and Colorado later that month.

Tennessee marks the fifth state.

Tesla Full Self-Driving gets outrageous insurance offer with insanely cheap rates

The discount rests on Lemonade’s strong belief in the safety of Tesla’s FSD system. The company cites Tesla’s data showing that FSD-driven miles are twice as safe as those driven manually, or associated with roughly a 50 percent crash reduction.

Lemonade Co-founder and President Shai Wininger has emphasized this distinction: “Traditional insurers treat a Tesla like any other car, and AI like any other driver. But a car that sees 360 degrees, never gets drowsy, and reacts in milliseconds can’t be compared to a human.”

He added that “Teslas driven with FSD are involved in far fewer accidents” and committed that as FSD software improves and becomes safer, Lemonade’s prices will drop further.

Tesla Full Self-Driving gets an offer to be insured for ‘almost free’

This approach leverages Lemonade’s existing pay-per-mile technology and AI-driven risk models, which analyze nuanced vehicle data including software version and sensor performance. The company expects the model to reward higher FSD usage with greater savings while supporting mixed households that include both Tesla and non-Tesla vehicles under one policy. Bundling with home, renters, or pet insurance can yield additional discounts.

As autonomous driving technology advances, Lemonade’s state-by-state expansion of usage-based pricing that directly reflects real-world safety data represents a notable shift in how insurers evaluate risk.

Tesla owners in the five available states – Arizona, Oregon, Indiana, Colorado, and now Tennessee – can obtain quotes quickly through the Lemonade app or website, potentially lowering the overall cost of ownership for vehicles equipped with advanced driver-assistance systems. Further states are expected as regulatory approvals progress.

Continue Reading

Cybertruck

Tesla quietly made the Cybertruck even stronger

Published

5 hours ago

on

August 3, 2026

By

Credit: Tesla

Tesla has continued to flex the strength, rigidity, and robustness of its all-electric pickup, the Cybertruck. In fact, since 2019, Cybertruck’s ability to avoid dents, dings, and even gunfire has been one of the main selling points Tesla has used to attract buyers who are looking for a vehicle that can handle the most intense challenges.

But that does not mean Tesla is not still actively trying to make it even better.

In a new hardware update, Tesla has decided to change the material of the Cybertruck’s underbody panels from aluminum to carbon fiber, a move that aims to not only increase pricing efficiency but also improve strength.

RELATED:

Tesla Cybertruck is officially the safest pickup, IIHS says

Cybertruck Lead Engineer Wes Morrill confirmed the change was made to the Cybertruck recently after it was spotted by Coleton Guerin of Out of Spec. This particular trim level was a Cyberbeast, but it is being applied to all trims to keep supply chain efficiency high and have less variance across trim levels.

Morrill said that Tesla tested different materials for the underbody panel protection, and carbon fiber performed better than aluminum, which is what the company was using since its first deliveries in 2023.

Additionally, there are some efficiency improvements because Tesla can better form the areas around the bolts to keep underbody airflow cleaner than previously.

Carbon fiber is traditionally lighter and more durable than aluminum, which is why it is such a popular material among luxury automakers, and EV makers will utilize some of the materials around battery packs to save weight.

This is the first instance of Tesla utilizing carbon fiber on the Cybertruck’s exterior to help with overall performance and strength. As previously mentioned, Tesla used aluminum to protect the underside of the body, but it is pretty typical for the company to continue making engineering changes that will improve the car in the future.

Continue Reading

News

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

Published

21 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.

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:

 

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:

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:

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:

Continue Reading