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

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.

Advertisement

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.

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.

Advertisement

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.

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.

Advertisement

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 v14.2.2.5 might be the most confusing release ever

With each Full Self-Driving release, I am realistic. I know some things are going to get better, and I know some things will regress slightly. However, these instances of improvements are relatively mild, as are the regressions. Yet, this version has shown me that it contains extremes of both.

Published

on

Credit: Tesla

Tesla Full Self-Driving v14.2.2.5 hit my car back on Valentine’s Day, February 14, and since I’ve had it, it has become, in my opinion, the most confusing release I’ve ever had.

With each Full Self-Driving release, I am realistic. I know some things are going to get better, and I know some things will regress slightly. However, these instances of improvements are relatively mild, as are the regressions. Yet, this version has shown me that it contains extremes of both.

It has been about three weeks of driving on v14.2.2.5; I’ve used it for nearly every mile traveled since it hit my car. I’ve taken short trips of 10 minutes or less, I’ve taken medium trips of an hour or less, and I’ve taken longer trips that are over 100 miles per leg and are over two hours of driving time one way.

These are my thoughts on it thus far:

Speed Profiles Are a Mixed Bag

Speed Profiles are something Tesla seems to tinker with quite frequently, and each version tends to show a drastic difference in how each one behaves compared to the previous version.

I do a vast majority of my FSD travel using Standard and Hurry modes, although in bad weather, I will scale it back to Chill, and when it’s a congested city on a weekend or during rush hour, I’ll throw it into Mad Max so it takes what it needs.

Early on, Speed Profiles really felt great. This is one of those really subjective parts of the FSD where someone might think one mode travels too quickly, whereas another person might see the identical performance as too slow or just right.

To me, I would like to see more consistency from release to release on them, but overall, things are pretty good. There are no real complaints on my end, as I had with previous releases.

In a past release, Mad Max traveled under the speed limit quite frequently, and I only had that experience because Hurry was acting the same way. I’ve had no instances of that with v14.2.2.5.

Strange Turn Signal Behavior

This is the first Full Self-Driving version where I’ve had so many weird things happen with the turn signals.

Two things come to mind: Using a turn signal on a sharp turn, and ignoring the navigation while putting the wrong turn signal on. I’ve encountered both things on v14.2.2.5.

On my way to the Supercharger, I take a road that has one semi-sharp right-hand turn with a driveway entrance right at the beginning of the turn.

Only recently, with the introduction of v14.2.2.5, have I had FSD put on the right turn signal when going around this turn. It’s obviously a minor issue, but it still happens, and it’s not standard practice:

When sharing this on X, I had Tesla fans (the ones who refuse to acknowledge that the company can make mistakes) tell me that it’s a “valid” behavior that would be taught to anyone who has been “professionally trained” to drive.

Apparently, if you complain about this turn signal, you are also claiming you know more than Tesla engineers…okay.

Nobody in their right mind has ever gone around a sharp turn when driving their car and put on a signal when continuing on the same road. You would put a left turn signal on to indicate you were turning into that driveway if that’s what your intention was.

Like I said, it’s a totally minor issue. However, it’s not really needed, and nor is it normal. If I were in the car with someone who was taking a simple turn on a road they were traveling, and they signaled because the turn was sharp, I’d be scratching my head.

I’ve also had three separate instances of the car completely ignoring the navigation and putting on a signal that is opposite to what the routing says. Really quite strange.

Parking Performance is Still Underwhelming

Parking has been a complaint of mine with FSD for a long time, so much so that it is pretty rare that I allow the vehicle to park itself. More often than not, it is because I want to pick a spot that is relatively isolated.

However, in the times I allow it to pull into a spot, it still does some pretty head-scratching things.

Recently, it tried to back into a spot that was ~60% covered in plowed snow. The snow was piled about six feet high in a Target parking lot.

Tesla ends Full Self-Driving purchase option in the U.S.

A few days later, it tried backing into a spot where someone failed the universal litmus test of returning their shopping cart. Both choices were baffling and required me to manually move the car to a different portion of the lot.

I used Autopark on both occasions, and it did a great job of getting into the spot. I notice that the parking performance when I manually choose the spot is much better than when the car does the entire parking process, meaning choosing the spot and parking in it.

It’s Doing Things (For Me) It’s Never Done Before

Two things that FSD has never done before, at least for me, are slow down in School Zones and avoid deer. The first is something I usually take over manually, and the second I surprisingly have not had to deal with yet.

I had my Tesla slow down at a school zone yesterday for the first time, traveling at 20 MPH and not 15 MPH as the sign suggested, but at the speed of other cars in the School Zone. This was impressive and the first time I experienced it.

I would like to see this more consistently, and I think School Zones should be one of those areas where, no matter what, FSD will only travel the speed limit.

Last night, FSD v14.2.2.5 recognized a deer in a roadside field and slowed down for it:

Navigation Still SUCKS

Navigation will be a complaint until Tesla proves it can fix it. For now, it’s just terrible.

It still has not figured out how to leave my neighborhood. I give it the opportunity to prove me wrong each time I leave my house, and it just can’t do it.

It always tries to go out of the primary entrance/exit of the neighborhood when the route needs to take me left, even though that exit is a right turn only. I always leave a voice prompt for Tesla about it.

It still picks incredibly baffling routes for simple navigation. It’s the one thing I still really want Tesla to fix.

Continue Reading

Investor's Corner

Tesla gets tip of the hat from major Wall Street firm on self-driving prowess

“Tesla is at the forefront of autonomous driving, supported by a camera-only approach that is technically harder but much cheaper than the multi-sensor systems widely used in the industry. This strategy should allow Tesla to scale more profitably compared to Robotaxi competitors, helped by a growing data engine from its existing fleet,” BoA wrote.

Published

on

Credit: Tesla

Tesla received a tip of the hat from major Wall Street firm Bank of America on Wednesday, as it reinitiated coverage on Tesla shares with a bullish stance that comes with a ‘Buy’ rating and a $460 price target.

In a new note that marks a sharp reversal from its neutral position earlier in 2025, the bank declared Tesla’s Full Self-Driving (FSD) technology the “leading consumer autonomy solution.”

Analysts highlighted Tesla’s camera-only architecture, known as Tesla Vision, as a strategic masterstroke. While technically more challenging than the multi-sensor setups favored by rivals, the vision-based approach is dramatically cheaper to produce and maintain.

This cost edge, combined with Tesla’s rapidly expanding real-world data engine, positions the company to scale robotaxis far more profitably than competitors, BofA argues in the new note:

“Tesla is at the forefront of autonomous driving, supported by a camera-only approach that is technically harder but much cheaper than the multi-sensor systems widely used in the industry. This strategy should allow Tesla to scale more profitably compared to Robotaxi competitors, helped by a growing data engine from its existing fleet.”

The bank now attributes roughly 52% of Tesla’s total valuation to its Robotaxi ambitions. It also flagged meaningful upside from the Optimus humanoid robot program and the fast-growing energy storage business, suggesting the auto segment’s recent headwinds, including expired incentives, are being eclipsed by these higher-margin opportunities.

Tesla’s own data underscores exactly why Wall Street is waking up to FSD’s potential. According to Tesla’s official safety reporting page, the FSD Supervised fleet has now surpassed 8.4 billion cumulative miles driven.

Tesla FSD (Supervised) fleet passes 8.4 billion cumulative miles

That total ballooned from just 6 million miles in 2021 to 80 million in 2022, 670 million in 2023, 2.25 billion in 2024, and a staggering 4.25 billion in 2025 alone. In the first 50 days of 2026, owners added another 1 billion miles — averaging more than 20 million miles per day.

This avalanche of real-world, camera-captured footage, much of it on complex city streets, gives Tesla an unmatched training dataset. Every mile feeds its neural networks, accelerating improvement cycles that lidar-dependent rivals simply cannot match at scale.

Tesla owners themselves will tell you the suite gets better with every release, bringing new features and improvements to its self-driving project.

The $460 target implies roughly 15 percent upside from recent trading levels around $400. While regulatory and safety hurdles remain, BofA’s endorsement signals growing institutional conviction that Tesla’s data advantage is not hype; it’s a tangible moat already delivering billions of miles of proof.

Continue Reading

News

Tesla to discuss expansion of Samsung AI6 production plans: report

Tesla has reportedly requested an additional 24,000 wafers per month, which would bring total production capacity to around 40,000 wafers if finalized.

Published

on

Tesla-Chips-HW3-1
Credit: Tom Cross

Tesla is reportedly discussing an expansion of its next-generation AI chip supply deal with Samsung Electronics. 

As per a report from Korean industry outlet The Elec, Tesla purchasing executives are reportedly scheduled to meet Samsung officials this week to negotiate additional production volume for the company’s upcoming AI6 chip.

Industry sources cited in the report stated that Tesla is pushing to increase the production volume of its AI6 chip, which will be manufactured using Samsung’s 2-nanometer process.

Tesla previously signed a long-term foundry agreement with Samsung covering AI6 production through December 31, 2033. The deal was reportedly valued at about 22.8 trillion won (roughly $16–17 billion).

Advertisement

Under the existing agreement, Tesla secured approximately 16,000 wafers per month from the facility. The company has reportedly requested an additional 24,000 wafers per month, which would bring total production capacity to around 40,000 wafers if finalized.

Tesla purchasing executives are expected to discuss detailed supply terms during their visit to Samsung this week.

The AI6 chip is expected to support several Tesla technologies. Industry sources stated that the chip could be used for the company’s Full Self-Driving system, the Optimus humanoid robot, and Tesla’s internal AI data centers.

The report also indicated that AI6 clusters could replace the role previously planned for Tesla’s Dojo AI supercomputer. Instead of a single system, multiple AI6 chips would be combined into server-level clusters.

Advertisement

Tesla’s semiconductor collaboration with Samsung dates back several years. Samsung participated in the design of Tesla’s HW3 (AI3) chip and manufactured it using a 14-nanometer process. The HW4 chip currently used in Tesla vehicles was also produced by Samsung using a 5-nanometer node.

Tesla previously planned to split production of its AI5 chip between Samsung and TSMC. However, the company reportedly chose Samsung as the primary partner for the newer AI6 chip.

Continue Reading