Connect with us

News

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

Published

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.

Advertisement

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.

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.

Advertisement

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.

Advertisement

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

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

Elon Musk

Elon Musk reveals date of Tesla Full Self-Driving’s next massive release

Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.

Published

on

Tesla CEO Elon Musk revealed the date of Full Self-Driving’s next massive release: v14.3.

For months, Tesla owners with Hardware 4 have been utilizing Full Self-Driving v14.2 and subsequent releases. Currently, the most up-to-date FSD version is v14.2.2.5, which has definitely brought out mixed reviews. With releases, some things get better, and other things might regress slightly.

For the most part, things are better in terms of overall behavior.

However, many owners have been looking forward to the next release, which is v14.3, about which Musk has said many great things. Back in November, Musk said that v14.3 “is where the last big piece of the puzzle lands.”

He added:

“We’re gonna add a lot of reasoning and RL (reinforcement learning). To get to serious scale, Tesla will probably need to build a giant chip fab. To have a few hundred gigawatts of AI chips per year, I don’t see that capability coming online fast enough, so we will probably have to build a fab.”

Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.

Tesla Full Self-Driving v14.2 is a considerable improvement from early versions of the suite, but we have written about the somewhat confusing updates that have come with recent versions.

Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever

They’ve been incredibly difficult to gauge in terms of progress because some things have gotten better, but there seems to be some real regression on a handful of things, especially with confidence and assertiveness.

Musk confirmed today on X that Tesla is already testing v14.3 internally right now. It will hit a wide release “in a few weeks,” so we should probably expect it by late April.

Overall, there are high hopes that v14.3 could be a true game changer for Tesla Full Self-Driving, as many believe it could be the version that Robotaxis in Austin, Texas, some of which are driverless and unsupervised, are running.

It could also include some major additions, including “Banish,” also referred to as “Reverse Summon,” which would go find a parking spot after dropping occupants off at their destination.

What Tesla will roll out, and when exactly it arrives, all remain to be seen, but fans have been ready for a new version as v14.2.2.5 has definitely run its course. We have had a lot of readers tell us their biggest request is to fix Navigation errors, which seem to be one of the most universal complaints among daily FSD users.

Continue Reading

Cybertruck

Chattanooga Charge: Tesla and EV fans ready for the Southeast’s wildest Tesla party

From Cybertruck Convoys to Kid-Friendly Fun Zones: The Chattanooga Charge Has Something for Everyone

Published

on

By

Hundreds of like-minded Tesla and EV enthusiasts are descending on Chattanooga Charge this weekend for the largest Tesla meet in the Southeast. Taking place on March 20–22, 2026 at the stunning Tennessee Riverpark.

If you were there last year, you’ll know that it’s the ultimate experience to see the wildest Teslas in action, see the best in EV tech, and arguably the most fun – finally put a name to the face and connect with those social media buddies IRL! Oh, and that epic night time Tesla light show is a once-in-a-lifetime experience that will transform the Riverpark into something out of a sci-fi film that’s remarkably unforgettable and must be seen in person.

This year’s event takes everything up a notch, with over 100 Cybertrucks expected to be on display, many sporting jaw-dropping modifications and custom wraps that push the boundaries of what these stainless steel beasts can look like.

Whether you’re a diehard Tesla fan, EV supporter, or just EV-mod-curious, the sheer spectacle is worth the drive.

The Chattanooga Charge doesn’t wait until Saturday morning to get started. The weekend technically kicks off Friday, March 20th, and the venue sets the tone immediately. Come share roadtrip stories over drinks at the W-XYZ Rooftop Bar on the top floor of the Aloft Chattanooga Hamilton Place Hotel, with sunset views over the city.

Come morning, nurse your hangover with a some good coffee, and convoy with hundreds of other Tesla and EV drivers through Chattanooga to the event for some morning meet and greets before the speaker panel starts and the food trucks fire up.

Tesla owner clubs travel from across the country to be here, not just to show off their vehicles,, but to connect, share, and celebrate a shared passion for the future of driving.

Sounds like a plan to me. See you there, guys. Don’t miss it. Get your tickets at ChattanoogaCharge.com and join the charge. 🔋⚡

Chattanooga Charge is a premier Tesla and EV gathering inspired by the X Takeover, known as one of the largest Tesla event gatherings. What began as a bold idea from the team at DIY Wraps/TESBROS, hosted in their hometown of Chattanooga, Tennessee, the event quickly became a movement across social media. The first annual Chattanooga Charge united over 16 Tesla clubs from 16 states, proof that the EV community was hungry for something big in the South. Year after year, the event has grown in scale, ambition, and heart.

Continue Reading

News

Tesla Full Self-Driving gets latest bit of scrutiny from NHTSA

The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.

Published

on

Credit: Tesla

The National Highway Traffic Safety Administration (NHTSA) has elevated its probe into Tesla’s Full Self-Driving (Supervised) suite to an Engineering Analysis.

The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.

The step up into an Engineering Analysis is often required before the NHTSA will tell an automaker to issue a recall. However, this is not a guarantee that a recall will be issued.

The NTHSA wants to examine Tesla FSD’s ability to assess road conditions that have reduced visibility, as well as detect degradation to alert the driver with sufficient time to respond.

The Office of Defects Investigation (ODI) will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications Tesla makes to the degradation detection system, including the timing, purpose, and capabilities of the updates.

Tesla routinely ships software updates to improve the capabilities of the FSD suite, so it will be interesting to see if various versions of FSD are tested. Interestingly, you can find many examples from real-world users of FSD handling snow-covered roads, heavy rain, and single-lane backroads.

However, there are incidents that the NHTSA has used to determine the need for this probe, at least for now. The agency said:

“Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred.”

It continues to say in its report that a review of Tesla’s responses revealed additional crashes that occurred in similar environments showed FSD “did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path.”

The next steps of the NHTSA Engineering Analysis require the agency to gather further information on Tesla’s attempts to upgrade the degradation detection system. It will also analyze six recent potentially related incidents.

The investigation is listed as EA26002.

Continue Reading