News
SpaceX Starship booster survives record-breaking 31-engine static fire
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.
The update that's rolling out to the fleet makes full use of the front and rear steering travel to minimize turning circle. In this case a reduction of 1.6 feet just over the air— Wes (@wmorrill3) April 16, 2024
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.
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.


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.
Investor's Corner
Lucid denies rumors of bankruptcy after over 40% stock drop
Electric vehicle maker Lucid Group has denied rumors of an imminent bankruptcy after a report from this morning sent the stock on a dramatic drop on Wall Street, seeing losses of more than 40 percent during trading hours.
Lucid’s Director of Communications, Nick Twork, responded to the report from Eletric-Vehicles.com, which stated the company’s restructuring advisor, AlixPartners, was asked to review two decisions: taking Lucid shares private or filing for Chapter 11 bankruptcy protection.
The report also claims AlixPartners told the Lucid board to “concentrate on Gravity production while improving its quality, and to temporarily hold back the Lucid Air, the sedan that has defined the company since its launch.”
Twork said:
$LCID The rumors are completely false. The company has sufficient liquidity to carry its operations well into next year, as recently published in its last quarterly filings, and it has not formed any special Board committee to explore the scenarios reported today. Our focus is…
— Nick Twork (@ntwork) July 14, 2026
Shares rebounded after the response to the report, halving its losses as the trading day neared 3 p.m. Eastern.
Lucid has struggled to get its sales off the ground and into more respectable numbers, but the company is in its early years, when things are hard to begin with. It is also backed by several notable investors, including the Saudi Public Investment Fund (PIF), which has nearly limitless money and likely would not ditch an investment of this size so soon.
Lucid shares were down just 14 percent at the time of publication, a far cry from the 55 percent its losses topped out at during the day.
News
Tesla owner attempts resale of Model S Signature Edition for over $260k
A Tesla owner who purchased a Model S Signature Edition, one of the final 250 units of the all-electric flagship vehicle that the company discontinued earlier this year, is attempting to sell the car despite a no-resale clause that prohibits reselling for the first year.
The car is being sold by J&S Autohaus in Ewing, New Jersey, and is priced at $260,490, well above the $159,420 that Tesla sold it for earlier this year.
🚨 The first Tesla Model S Signature Edition is up for sale for $260,490
Tesla placed a no-resale clause on the Model S and X Signature, so it will be interesting to see if the company takes any action. https://t.co/N9rKGHnbD6 pic.twitter.com/6FZhDL1KNR
— TESLARATI (@Teslarati) July 14, 2026
To those who do not know, the Model S Signature was a highly exclusive, limited-run farewell variant of the Model S Plaid that was produced this year to mark the end of production of both the Model S and Model X, Tesla’s two flagship vehicles.
Limited to just 250 units with invite-only sales, it serves as a collector’s item celebrating the legacy of the Model S, which helped pioneer Tesla’s electric vehicle success since its 2012 launch.
It bundles top-tier performance with bespoke cosmetic and luxury upgrades, plus Tesla’s Luxe Package. Here’s what the Model S Signature has over the typical Model S Plaid:
- Exclusive Exterior – Unique Garnet Red Paint, matching door handles, gold Tesla “T” badges upfront, gold Plaid and Signature badging at the rear.
- Premium Interior – White Alcantara upholstery with gold piping/accents, gold Plaid seat badges, Signature-marked door sills, individually numbered dashboard plaque, gold puddle lights, special interior lighting sequence, and a custom Signature key fob.
- Performance Upgrades – Carbon-ceramic brakes with gold calipers
- Bundled Luxe Package – Full Self-Driving (Supervised), four years of Premium Connectivity, free lifetime Supercharging
- Performance Metrics – ~1,020 horsepower, sub-2-second 0-60 MPH, ~390-mile range
Tesla quickly introduced a No Resale Agreement for the Signature Editions of the Model S and Model X, which would penalize the seller for “the amount of $50,000 or the value received as consideration for the sale or transfer, whichever is greater.”
The company continues:
“If you sell or otherwise transfer the ownership of your Model S or Model X, the remainder of the Recommended Maintenance, Wheel and Tire Protection Plan, and Windshield Protection Plan will transfer automatically to the buyer. The Full Self-Driving (Supervised), Free Supercharging and Premium Connectivity will not transfer with the vehicle and will terminate once the ownership of the Model S or Model X is transferred.”
Tesla will likely come after the seller, especially as it has been about two months since Tesla launched deliveries.
News
Tesla Full Self-Driving v14.3.5 Early Impressions: new features and early performance
Tesla rolled out Full Self-Driving (Supervised) v14.3.5 yesterday, and about fifty miles of driving on the new version has given me enough time to highlight what seems to be strong about the release and what is not.
Additionally, Tesla has added a few new features with this specific update, which we’ll highlight as well.
Tesla Full Self-Driving v14.3.5 Performance
The new update is business as usual. Things seem to be running completely normal and necessary, but there are a few things that we’ve seemed to pick up on based on our own experience with v14.3.5, as well as what other users are seeing.
Initially, it seems to be more aware of its surroundings, making moves that are incredibly courteous to other drives and operating just a tad more reserved than what the suite might have done previously.
We had two instances where it showed this, the first being FSD needing to pass a Flagger Force vehicle that was placing down signage for the day. Their work truck was right at the front corner of a right-hand turn; typically where most cars travel when they take that turn.
FSD v14.3.5 recognized this, slowed down, and took the turn wide with no issues:
🚨 Tesla Full Self-Driving v14.3.5 takes a wide turn as flagger crews set up signage for the day https://t.co/3v0PL9qhlI pic.twitter.com/i4CKqxE16c
— TESLARATI (@Teslarati) July 13, 2026
Additionally, v14.3.5 backed up for a semi truck that was making a wide turn onto a road my car was on. This is not new, but it seemed to be backing up for courtesy; it didn’t seem completely necessary, but it might have put some peace of mind in the truck driver’s head:
🚨 Tesla Full Self-Driving v14.3.5 backs up for an oncoming tractor trailer taking a wide turn https://t.co/0WuAqNMpRR pic.twitter.com/s6yZGVm5Te
— TESLARATI (@Teslarati) July 13, 2026
X user Mike P, also a Pennsylvania native like myself, shared three clips of his Tesla running v14.3.5 performing similar maneuvers. He said:
“FSD turns right into a small alley that only fits one car at a time, sees oncoming car, reverses out of alley to make space, realizes oncoming car is actually parking, re-enters alley.”
Check it out here:
Rapidfire epic moments on FSD V14.3.5
1) FSD turns right into a small alley that only fits one car at a time, sees oncoming car, reverses out of alley to make space, realizes oncoming car is actually parking, re-enters alley.2) Insane speed to vehicle cues. As FSD approaches… pic.twitter.com/bSnySSlFHR
— Mike P (@mikepat711) July 13, 2026
It seems like Speed Profiles are still in need of some tweaking; I am adjusting what Speed Profile I’m in frequently, constantly changing it to get it to travel at the correct speed. This was an issue for me on v14.3.4. It seems like they’re just a little inconsistent.
Terrible Parking
Parking attempts on v14.3.5 were not good. There are quite a few people who have said this:
Yeah it seems like FSD v14.3.5 is having some issues with parking early on https://t.co/Bw5ULfVmDq pic.twitter.com/RHdpjOEpIo
— TESLARATI (@Teslarati) July 13, 2026
David Moss, the Tesla owner who has taken multiple coast-to-coast drives without any interventions, also has had some issues with parking early on with v14.3.5:
Horrible first impression v14.3.5 on my 2025 Tesla Model 3 LR RWD Premium 😭
3 terrible parking jobs in 23 min including parking on a ramp in a business park & parking perpendicular out in the road on street only parking situation.Wish I had a better drive but I still believe… pic.twitter.com/TtyhRHAFG7
— David Moss (@DavidMoss) July 13, 2026
New Features
Tesla has added the ability to open Camera Preview at any time. Previously, it was only available in Park. Here’s what that feature looks like in action:
🚨 Here’s the new Camera Preview feature on FSD v14.3.5 pic.twitter.com/OodfZgDppy
— TESLARATI (@Teslarati) July 13, 2026
Check back later this week for a longer review of what we’ve noticed on Full Self-Driving v14.3.5.