Connect with us

News

SpaceX Super Heavy booster returns to launch pad after major repairs

Booster 7 has returned to the orbital launch site after suffering damage a few weeks prior. (NASASpaceflight - bocachicagal)

Published

4 years ago

on

SpaceX has returned its newest Super Heavy to Starbase’s orbital launch site (OLS) after rapidly repairing damage the booster suffered during its first round of testing.

Super Heavy Booster 7 (B7) left the High Bay it was assembled in for the first time on March 31st and rolled a few miles down the road to nearby Starship launch and test facilities on a set of self-propelled mobile transporters (SPMTs). On April 2nd, the roughly 67-meter-tall (~220 ft; 69m w/ Raptors) rocket was installed on top of Starbase’s lone orbital launch mount (OLM), setting the stage for crucial qualification testing.

The start of that process was exceptionally successful. On April 4th, after a smooth launch mount installation, SpaceX quickly filled Booster 7’s propellant tanks with a relatively benign cryogenic fluid (liquid nitrogen, liquid oxygen, or both) to simulate the thermal and mechanical characteristics of real flammable propellant. Despite the fact that the test marked the first time SpaceX had fully filled a Super Heavy prototype’s tanks, Booster 7 sailed through the ‘cryoproof’ without any obvious issue.

On April 8th, SpaceX moved Super Heavy B7 from the orbital launch mount to a structural test stand that had been installed and modified just a few hundred feet away in the weeks prior. This is where Booster 7’s near-perfect start to qualification testing took a bit of a turn. Booster 7 is only the third full-size Super Heavy prototype SpaceX has tested since July 2021. Like Booster 3 and Booster 4 before it, Booster 7 features some major design changes that ultimately make the prototype a pathfinder, necessitating extensive qualification testing.

To name just a few of the changes, Super Heavy B7 is the first booster fitted with a 33-engine puck and the first finished Starship prototype of any kind designed to use new Raptor V2 engines. With all 33 engines installed and operating a full thrust, Booster 7’s entire structure – and its aft thrust section especially – would be subjected to around 40% more thrust and stress than Booster 4, which indirectly completed structural testing with the help of a sacrificial test tank. Beyond differences in thrust and mechanical stress, Booster 7 is also the first Super Heavy to reach the test stand with secondary ‘header’ tanks meant to store landing propellant.

Advertisement
-->

It’s unclear if those header tanks were fully filled and drained during Booster 7’s cryoproof, but they would not be quite as cooperative during a different kind of cryogenic testing on the structural test stand. The stand SpaceX modified specifically for Super Heavy B7 was outfitted with 13 hydraulic rams to simulate the full thrust of the booster’s central Raptor V2 engines – up to almost 3000 tons (~6.6M lbf) compared to Booster 4’s ~1700 tons (~3.7M lbf) with a smaller cluster of nine engines.

Implosion at the Structural Test Stand

After a few false starts and minor tests on the stand, Booster 7 finally managed some significant testing on April 14th. Judging by the rhythmic shattering of ice that built up on Super Heavy’s tanks, the test stand was able to simulate the thrust of Raptors to some degree and subject the booster to major mechanical stress that was felt from tip to tail. Within a few days, Booster 7 was removed from the test stand and returned to the high bay on April 18th. Around April 21st or 22nd, an image was leaked showing extensive damage inside Booster 7, confirming that the Super Heavy’s test campaign had been forced to end prematurely.

A leaked image looking up inside B7’s LOx header tank after testing. Above, B7’s aft section and LOx header before the booster was fully assembled.

Right away, the damage shown in the photo hinted at an operational failure, meaning that mistakes made by the rocket’s operators may have been more to blame than a possible design flaw. The photo shows a short portion of B7’s liquid methane (LCH4) transfer tube that runs through the booster’s new liquid oxygen (LOx) header tank, which itself sits inside Super Heavy’s main LOx tank at the aft end of the rocket – a tube inside a small tank inside a large tank, in other words. Super Heavy’s LCH4 transfer tube generally does what it says, allowing methane to safely fly down through the main LOx tank and fuel up to 33 Raptor engines. At full thrust, that tube would need to supply around 20 tons (~45,000 lb) of methane per second.

However, on top of merely transferring methane through the oxygen tank, Booster 7 introduced a design change that allows some or all of that tube to change functions and become a header tank mid-flight. That would require a system of valves that could seal off the main LCH4 tank once it was emptied, turning the transfer tube into a sort of giant steel straw filled with enough LCH4 to fuel Super Heavy’s boost-back and landing burns.

The damaged transfer tube in the leaked photo of Booster 7 doesn’t look that unlike what one might expect to see if they sucked through one end of a straw while blocking the other end, collapsing the center. Translated to the scale of Super Heavy, after an otherwise successful day of structural testing, SpaceX operators may have accidentally closed or opened the wrong valves while draining the booster’s transfer tube of liquid oxygen or nitrogen. As the heavy liquid drained from the tube, a lack of pressure equalization could have quickly drawn a vacuum and caused the tube to implode.

The

On April 29th, a SpaceX fan turned analyst published an analysis that convincingly pinpointed the moment Booster 7’s transfer tube collapsed. Simultaneously, because it showed that the transfer tube likely imploded during detanking, the analysis more or less confirmed the above speculation that the failure had been caused by a degree of operator error or poor test design. Of course, it’s possible that a hardware or software design flaw contributed to or caused the anomaly or that something like a pressure differential in the LOx header tank and LCH4 header tube could also explain the damage, but the accidental formation of a vacuum during detanking is arguably the simplest (obvious) explanation.

Advertisement
-->

After the image of the internal damage leaked, the immediate consensus among fans and close followers was that Booster 7 was beyond repair. Instead, SpaceX appears to have proven those assumptions wrong and somehow managed to repair the upgraded Super Heavy to the point that it was worth testing again less than three weeks after returning to the high bay. On May 6th, B7 was rolled back to the launch site and installed, for the second time, on the orbital launch mount.

Prior to the failure, the general expectation was that SpaceX would begin installing Raptor V2 engines as soon as Booster 7 passed structural testing. It remains to be seen if SpaceX wants to repeat Booster 7’s cryoproof or structural testing to ensure that its quick repairs did the job before proceeding into static fire testing as previously planned. Nonetheless, hope lives on for the Super Heavy prototype and new test windows have been scheduled from 10am to 10pm on May 9th, 10th, and 11th.

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 removes Safety Monitors, begins fully autonomous Robotaxi testing

This development, in terms of the Robotaxi program, is massive. Tesla has been working incredibly hard to expand its fleet of Robotaxi vehicles to accommodate the considerable demand it has experienced for the platform.

Published

4 hours ago

on

December 14, 2025

By

Credit: @Mandablorian | X

Tesla has started Robotaxi testing in Austin, Texas, without any vehicle occupants, the company’s CEO Elon Musk confirmed on Sunday. Two Tesla Model Y Robotaxi units were spotted in Austin traveling on public roads with nobody in the car.

The testing phase begins just a week after Musk confirmed that Tesla would be removing Safety Monitors from its vehicles “within the next three weeks.” Tesla has been working to initiate driverless rides by the end of the year since the Robotaxi fleet was launched back in June.

Two units were spotted, with the first being seen from the side and clearly showing no human beings inside the cabin of the Model Y Robotaxi:

Another unit, which is the same color but was confirmed as a different vehicle, was spotted just a few moments later:

The two units are traveling in the general vicinity of the South Congress and Dawson neighborhoods of downtown Austin. These are located on the southside of the city.

This development, in terms of the Robotaxi program, is massive. Tesla has been working incredibly hard to expand its fleet of Robotaxi vehicles to accommodate the considerable demand it has experienced for the platform.

However, the main focus of the Robotaxi program since its launch in the Summer was to remove Safety Monitors and initiate completely driverless rides. This effort is close to becoming a reality, and the efforts of the company are coming to fruition.

It is a drastic step in the company’s trek for self-driving technology, as it plans to expand it to passenger vehicles in the coming years. Tesla owners have plenty of experience with the Full Self-Driving suite, which is not fully autonomous, but is consistently ranked among the best-performing platforms in the world.

Continue Reading

News

Tesla refines Full Self-Driving, latest update impresses where it last came up short

We were able to go out and test it pretty extensively on Saturday, and the changes Tesla made from the previous version were incredibly impressive, especially considering it seemed to excel where it last came up short.

Published

15 hours ago

on

December 14, 2025

By

Credit: TESLARATI

Tesla released Full Self-Driving v14.2.1.25 on Friday night to Early Access Program (EAP) members. It came as a surprise, as it was paired with the release of the Holiday Update.

We were able to go out and test it pretty extensively on Saturday, and the changes Tesla made from the previous version were incredibly impressive, especially considering it seemed to excel where it last came up short.

Tesla supplements Holiday Update by sneaking in new Full Self-Driving version

With Tesla Full Self-Driving v14.2.1, there were some serious regressions. Speed Profiles were overtinkered with, causing some modes to behave in a strange manner. Hurry Mode was the most evident, as it refused to go more than 10 MPH over the speed limit on freeways.

It would routinely hold up traffic at this speed, and flipping it into Mad Max mode was sort of over the top. Hurry is what I use most frequently, and it had become somewhat unusable with v14.2.1.

It seemed as if Speed Profiles should be more associated with both passing and lane-changing frequency. Capping speeds does not help as it can impede the flow of traffic. When FSD travels at the speed of other traffic, it is much more effective and less disruptive.

With v14.2.1.25, there were three noticeable changes that improved its performance significantly: Speed Profile refinements, lane change confidence, and Speed Limit recognition.

Speed Profile Refinement

Speed Profiles have been significantly improved. Hurry Mode is no longer capped at 10 MPH over the speed limit and now travels with the flow of traffic. This is much more comfortable during highway operation, and I was not required to intervene at any point.

With v14.2.1, I was sometimes assisting it with lane changes, and felt it was in the wrong place at the wrong time more frequently than ever before.

However, this was one of the best-performing FSD versions in recent memory, and I really did not have any complaints on the highway. Speed, maneuvering, lane switching, routing, and aggressiveness were all perfect.

Lane Changes

v14.2.1 had a tendency to be a little more timid when changing lanes, which was sort of frustrating at times. When the car decides to change lanes and turn on its signal, it needs to pull the trigger and change lanes.

It also changed lanes at extremely unnecessary times, which was a real frustration.

There were no issues today on v14.2.1.25; lane changes were super confident, executed at the correct time, and in the correct fashion. It made good decisions on when to get into the right lane when proceeding toward its exit.

It was one of the first times in a while that I did not feel as if I needed to nudge it to change lanes. I was very impressed.

Speed Limit Recognition

So, this is a complex issue. With v14.2.1, there were many times when it would see a Speed Limit sign that was not meant for the car (one catered for tractor trailers, for example) or even a route sign, and it would incorrectly adjust the speed. It did this on the highway several times, mistaking a Route 30 sign for a 30 MPH sign, then beginning to decelerate from 55 MPH to 30 MPH on the highway.

This required an intervention. I also had an issue leaving a drive-thru Christmas lights display, where the owners of the private property had a 15 MPH sign posted nearly every 200 yards for about a mile and a half.

The car identified it as a 55 MPH sign and sped up significantly. This caused an intervention, and I had to drive manually.

It seems like FSD v14.2.1.25 is now less reliant on the signage (maybe because it was incorrectly labeling it) and more reliant on map data or the behavior of nearby traffic.

A good example was on the highway today: despite the car reading that Route 30 sign and the Speed Limit sign on the center screen reading 30 MPH, the car did not decelerate. It continued at the same speed, but I’m not sure if that’s because of traffic or map data:

A Lone Complaint

Tesla has said future updates will include parking improvements, and I’m really anxious for them, because parking is not great. I’ve had some real issues with it over the past couple of months.

Today was no different:

Full Self-Driving v14.2.1.25 is really a massive improvement over past versions, and it seems apparent that Tesla took its time with fixing the bugs, especially with highway operation on v14.2.1.

Continue Reading

News

Tesla hints at Starlink integration with recent patent

“By employing polymer blends, some examples enable RF transmission from all the modules to satellites and other communication devices both inside and outside the vehicle.”

Published

1 day ago

on

December 13, 2025

By

Credit: Grok

Tesla hinted at a potential Starlink internet terminal integration within its vehicles in a recent patent, which describes a vehicle roof assembly with integrated radio frequency (RF) transparency.

The patent, which is Pub. No U.S. 2025/0368267 describes a new vehicle roof that is made of RF-transparent polymer materials, allowing and “facilitating clear communication with external devices and satellites.”

Tesla believes that a new vehicle roof design, comprised of different materials than the standard metallic or glass elements used in cars today, would allow the company to integrate modern vehicular technologies, “particularly those requiring radio frequency transmission and reception.

Instead of glass or metallic materials, Tesla says vehicles may benefit from high-strength polymer blends, such as Polycarbonate, Acrylonitrile Butadiene Styrene, or Acrylonitrile Styrene Acrylate.

These materials still provide ideal strength metrics for crashworthiness, stiffness for noise, vibration, and harshness control, and are compliant with head impact regulations.

They would also enable better performance with modern technologies, like internet terminals, which need an uninterrupted signal to satellites for maximum reception. Tesla writes in the patent:

“By employing polymer blends, some examples enable RF transmission from all the modules to satellites and other communication devices both inside and outside the vehicle.”

One of the challenges Tesla seems to be aware of with this type of roof design is the fact that it will still have to enable safety and keep that at the forefront of the design. As you can see in the illustration above, Tesla plans to use four layers to increase safety and rigidity, while also combating noise and vibration.

It notes in the patent that disclosed examples still meet the safety requirements outlined in the Federal Motor Vehicle Safety Standards (FMVSS).

Starlink integrated directly into Tesla vehicles would be a considerable advantage for owners. It would come with a handful of distinct advantages.

Initially, the inclusion of Starlink would completely eliminate cellular dead zones, something that is an issue, especially in rural areas. Starlink would provide connectivity in these remote regions and would ensure uninterrupted service during road trips and off-grid adventures.

It could also be a critical addition for Robotaxi, as it is crucial to have solid and reliable connectivity for remote monitoring and fleet management.

Starlink’s growing constellation, thanks to SpaceX’s routine and frequent launch schedule, will provide secure, stable, and reliable internet connectivity for Tesla vehicles.

SpaceX reaches incredible milestone with Starlink program

Although many owners have already mounted Starlink Mini dishes under their glass roofs for a similar experience, it may be integrated directly into Teslas in the coming years, either as an upgrade or a standard feature.

Continue Reading