News
SpaceX sets stage for Starship booster’s first 33-engine static fire
SpaceX has set the stage for a record-breaking Starship booster static fire after the rocket completed a complex fueling test and launch rehearsal earlier this week.
On January 25th, a tower the size of a skyscraper activated a pair of giant mechanical arms to disassemble the largest rocket ever built. The arms carefully grabbed Starship using hard points under its flaps and lifted the 50-meter-tall second stage and spacecraft off of Super Heavy Booster 7. Nicknamed Mechazilla, the robot lowered the hundred-ton (~220,000+ lbs) vehicle hundreds of feet onto a waiting stand and eventually let go. On January 26th, SpaceX transported Ship 24 back to its Starbase, Texas factory for finishing touches.
Booster 7 remained installed on Starbase’s donut-shaped orbital launch mount, which uses clamps and umbilicals to hold Starship in place and power, fuel, and pressurize Super Heavy. In theory, the next time Booster 7 leaves that launch mount, it will do so under its own power. But first, SpaceX must ensure that that unprecedented power can be controlled (and survived).
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
This, unfortunately, is far from the first iteration of this story. SpaceX has been seemingly close to the milestone at many points over the last year and a half. In September 2021, for example, CEO Elon Musk reported that Super Heavy Booster 4 would attempt the first static fire on Starbase’s orbital launch mount later that month. Eleven months later, Super Heavy Booster 7 gave the OLM its inaugural static fire test – albeit with just one of its 33 engines.
In the months following that static fire, Booster 7 completed another single-engine test, a two-engine test, a seven-engine test, a fourteen-engine test, and a long-duration eleven-engine test. All of that slow and steady testing has been fairly successful and caused no major damage to the rocket or pad. But five months after it began, SpaceX has never ignited more than 14 – 42% – of Super Heavy’s 33 Raptor engines at once. That must change before SpaceX can gain enough confidence in Starship for (and convince the FAA to license) an orbital launch attempt.
During Super Heavy B7’s 14-engine static fire, the booster could have produced up to 3220 tons (7.1 million pounds) of thrust. When it ignites all 33 available engines for the first time, its maximum thrust could leap to 7590 tons (16.7 million pounds), beating the next most powerful rocket in history – the Soviet N1 – by nearly 60%. In other words, SpaceX will be attempting something unprecedented in rocketry. Success is far from guaranteed and the worst possible failure mode could almost entirely destroy Starship’s only finished orbital launch site, explaining SpaceX’s unusual caution.
On January 23rd, Ship 24 and Booster 7 completed Starship’s first full wet dress rehearsal (a fueling and launch rehearsal test) on the first try – an extremely impressive achievement for any rocket, let alone the largest in history. With that combined test out of the way, the only unprecedented test standing between Starship and its first orbital launch attempt is a 33-engine Super Heavy static fire.
To reduce risk, Ship 24 was removed from Booster 7. Back at the factory, SpaceX needs to close a few gaps left in its heat shield, and will likely also conduct careful inspections to ensure that the Starship is ready for flight. Unburdened of Ship 24, Booster 7 may finally be on the cusp of the most challenging ground test in Starship and SpaceX history. SpaceX has scheduled 12-hour road closures that could be used for that purpose as early as January 30th, 31st, and February 1st.
Those road closures could be used for Ship 25 static fire testing instead of or in addition to Booster 7. The Super Heavy is also missing an important hydraulic power unit (HPU) that was removed before the wet dress rehearsal. It’s unclear if static fire testing can be conducted without that HPU (one of two), why it was removed, or how long replacing it will take, adding more uncertainty. Nonetheless, it still appears that SpaceX is no more than a few weeks away from Starship’s first 33-engine static fire attempt.
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.
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.
It’s in testing right now. Wide release in a few weeks.
— Elon Musk (@elonmusk) March 19, 2026
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.
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
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.
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.
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 NHTSA said it was upgrading a probe into Tesla’s Full Self-Driving (Supervised) platform to an “engineering analysis”
It will examine 3.2 million vehicles and aims to determine its effectiveness in evaluating degraded road conditions pic.twitter.com/2dkrv1mR8o
— TESLARATI (@Teslarati) March 19, 2026
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.