Connect with us

News

SpaceX tests Starship and Frankenstein ‘test tank’ simultaneously

Starship S20 and test tank B2.1 enjoy some simultaneous venting. (NASASpaceflight - bocachicagal)

Published

5 years ago

on

After another few weeks of downtime, SpaceX has simultaneously tested the first orbital-class Starship prototype and a Frankenstein-esque ‘test tank’ at its South Texas facilities. While nothing that occurred was all that visually spectacular, the afternoon of testing was still noteworthy for a couple of reasons.

First up, following a successful six-engine Raptor static fire – the first in Starbase history – on November 12th, all signs pointed to Starship S20 attempting another static fire (its fourth) on December 1st. In the almost three weeks of inactivity between those planned tests, SpaceX likely performed extensive inspections of the pathfinder prototype and its Raptor engines. Technicians also repaired the minor heat shield damage and tile loss that testing incurred and patched a few other ‘holes’, effectively leaving Ship 20 with the first fully finished heat shield by the end of November.

Earlier this week, one of the few remaining Boca Chica Village residents received a safety notice from SpaceX indicating that a static fire test was scheduled on Wednesday, December 1st – followed soon after by a notice to mariners (NOTAM) warning boaters to keep to a safe distance. Two hours into the 10am to 6pm CST test window, Starship S20 was already venting and starting to get frosty, confirming that propellant loading had begun. A little over an hour later, it was clear that SpaceX had aborted the first static fire attempt of the day. For the next three hours, Ship 20 exhibited some unusual behavior including new vents, an apparent header tank pressurization or fill test, and still more odd venting in new places.

In the middle of Starship’s weird nose-related testing, SpaceX began simultaneously loading a new ‘test tank’ known as B2.1 with liquid nitrogen (LN2) – marking the first truly simultaneous test of multiple Starship test articles. As Ship 20 seemingly detanked for the second time that day, the B2.1 tank was fully loaded with LN2 and apparently pressure-tested not long after. A few hours later, the test tank was also detanked and the road to the pad was reopened, marking the end of the day’s testing.

Normally, nothing is particularly unusual or noteworthy about test tank testing. Since January 2020, SpaceX has routinely built and tested tanks that are effectively just shorter versions of actual tanks and hardware, using them to qualify changes to Starship’s design, materials, operations, and more before applying those changes to full-size prototypes. B2.1 is the tenth dedicated test tank to reach the launch pad in a little under two years.

Normally, the ‘B2.1’ name SpaceX has given the tank would imply that it’s a newer booster test tank (using Bx instead of BNx) following in the footsteps of BN2.1, which passed cryogenic and load testing this summer. Instead, though, B2.1 is a bit of a nightmarish amalgamation of seemingly random Starship and Super Heavy parts. Its forward dome is an old, unused booster section complete with the hexagonal structure grid fins would have been brace against. Its aft section is a booster thrust structure. Up to that point, it’s effectively just a copy of BN2.1.

However, SpaceX inexplicably installed a Starship thrust dome inside B2.1’s booster thrust structure, creating a test tank with no obvious relevance to any conceivable Starship or Super Heavy design or prototype. Further, SpaceX rolled B2.1 to the launch site for testing only after installing it on an unused device that’s believed to be the aft half of a dedicated booster structural test stand. In theory, a sort of ‘cap’ would be fitted on top of a booster or test tank installed in the stand’s base and strong cables would connect the two, allowing SpaceX to subject prototypes to compressive stress – like, perhaps, the forces a booster might experience while carrying a fully-fueled 1300-ton Starship to space. The upper half of that test structure has yet to be moved to the launch site.

Advertisement
-
-
Since this diagram was published, SpaceX has also tested BN2.1, GSE-4, and now B2.1.

Altogether, the weird half-complete test stand and bizarre fusion of ship and booster parts make B2.1’s purpose and initial testing a complete mystery. It’s unclear what value it provides that makes it more of a priority than, say, finally starting to test the first flightworthy Super Heavy booster (B4). Ultimately, the most interesting thing about B2.1’s test debut is the fact that it appears to mark the first use of Starbase’s brand new orbital tank farm, which is approaching completion.

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 Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Published

13 minutes ago

on

August 2, 2026

By

Credit: Teslarati

Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.

Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.

For now, here’s everything I noticed with v14.3.7:

Overall Improvement

Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.

The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.

However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.

I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.

The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.

Manual Signal Override is More Responsive

On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.

The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.

Parking Lot Performance

Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.

The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:

 

I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.

Full Self-Driving Averts Disaster

A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:

There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.

However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.

Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.

It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.

What Needs to Improve

Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps

On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.

However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.

I even tried scrolling down into Sloth quickly, but I ended up just taking over:

A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.

Navigation

Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.

Auto Wipers

Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.

You can watch our full review of Tesla Full Self-Driving v14.3.7 below:

Continue Reading

Elon Musk

SpaceX’s biggest test yet arrives this week and it’s not a rocket launch

Published

18 hours ago

on

August 1, 2026

By

SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.

The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.

Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.

SpaceX scores another massive Pentagon deal to support military satellites

Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.

The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.

As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.

Continue Reading

Elon Musk

SpaceX’s Starship just got filmed by its own cargo

SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.

Published

19 hours ago

on

August 1, 2026

By

SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.

The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.

The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.

Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.

Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.

Continue Reading