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

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.

Advertisement
-

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.

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.

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

Why SpaceX is finishing another space-internet system that isn’t Starlink

SpaceX launched three final O3b mPower satellites Sunday, finishing a lesser known SES satellite network.

Published

on

By

SpaceX had an 87 minute window opening at 2:49 p.m. Eastern on Sunday to fly a Falcon 9 out of Cape Canaveral carrying the final three satellites for SES’s O3b mPower constellation, a project that has taken more than a decade to finish since Boeing and SES first signed SpaceX on for the work.

Unlike the thousands of Starlink satellites SpaceX has stacked into orbit over the years, O3b mPower flies in a different neighborhood entirely. The three new satellites, tagged F11, F12 and F13, are headed for medium Earth orbit at roughly 5,000 miles up, more than ten times higher than Starlink’s shell around 340 miles but still a small fraction of the 22,000 miles where old school geostationary satellites sit. That middle position is the whole point, because a satellite that far out needs far fewer siblings to blanket the globe than a low orbit constellation does. Essentially, SES only needed 13 satellites total to build a network offering quick, steady service that used to require thousands of spacecraft.

With most people having heard plenty about Starlink and almost nothing about O3b mPower, SES and SpaceX already blend the two networks for some customers. Both SpaceX and SES sell satellite broadband, but they’re aimed at different buyers. Starlink is built for volume, direct to consumers, RVs, homes, small businesses, plus a growing aviation and maritime business. O3b mPower skips consumers entirely and sells enterprise grade connectivity to airlines, cruise lines, offshore energy operators, telecoms needing backhaul, and governments, priced and provisioned more like a dedicated circuit.

A 2023 partnership lets cruise ships combine Starlink’s speed with O3b mPower’s steady capacity depending on what a ship needs at a given moment. Sunday’s completed 13 satellite constellation effectively finishes the medium orbit half of that pairing, years after.

Sunday’s mission was already a something on SpaceX’s manifest well before O3b mPower entered the picture. This flight marked its 29th trip to orbit, a history that includes two crewed Axiom missions, the European Space Agency’s Euclid telescope and 22 separate Starlink batches. SpaceX has landed boosters on the droneship A Shortfall of Gravitas so often that Sunday’s touchdown attempt, if it went as planned, was set to be the 661st successful Falcon booster landing to date.

For a company that pushed the Starlink constellation past 11,000 satellites back in August, almost entirely through bulk launches from California, Sunday’s flight was a reminder that SpaceX’s schedule still has room for someone else’s satellites too. SES gets a finished network built for a narrower set of customers, and Falcon 9 gets one more line on an already long resume.

Continue Reading

Elon Musk

Tesla gives the Roadster an official “Go for launch” demonstration date

Tesla teased an October 1 Roadster reveal, reviving years of delayed SpaceX thruster hover promises.

Published

on

By

Concept rendering of a Tesla Roadster with SpaceX Package via Grok
Concept rendering of a Tesla Roadster with SpaceX Package via Grok

Tesla teased an October 1 event date for its next generation Roadster, posting an image on X Saturday that shows the car lit up like it is sitting on a launch pad, with the date “10.01” stamped across the bottom and the caption “Go for launch.” A countdown clock on Tesla’s Roadster order page now points to the same date, which falls on a Thursday. The company has not said where the event will happen or whether it will be streamed at the moment. Stay with us @Teslarati for live updates.


Tesla has since sent formal invitations to reservation holders confirming the event will take place in Waco, Texas, about 90 minutes north of its Austin headquarters, based on a digital ticket shared on X by Sawyer Merritt. Tesla did not name the exact venue, though Waco sits close to SpaceX’s McGregor, Texas, rocket test site, previously reported as the planned location for a Roadster thruster demonstration. The invite sets the reveal for 8:30 p.m. Eastern on October 1, requires RSVPs by midnight on September 16, and limits entry to guests 21 and older. Invitations are non-transferable.

The tease follows nine years of a project defined by unimaginable specs along with slipped dates. Musk first showed the second generation Roadster in November 2017 as a surprise reveal at the end of the Tesla Semi event, promising a 0 to 60 mph time under two seconds, a top speed above 250 mph, 620 miles of range from a 200 kWh battery, and production starting in 2020. At last November’s shareholder meeting, Musk set an April 1 demo date and joked the choice gave him “deniability” if it slipped again, which it did, moving first to late April, then to “a month or so,” then to August.

Tesla Roadster SpaceX Package’s 1.1-second 0-60 mph launch visualized in concept video

Whatever Tesla shows on October 1 is expected to center on the SpaceX developed thruster package Musk has described since 2018. Internally code named A71, a nod to the Lockheed SR-71 Blackbird, the system reportedly uses cold gas thrusters fed by a composite overwrapped pressure vessel, the same tank design SpaceX uses on Falcon 9. Musk has said a thruster equipped Roadster could hit 60 mph in about 1.1 seconds under roughly 2.75 g of launch force, well past the 1.9 second figure quoted for the standard car. That version reportedly will not be street legal and has reportedly been discussed as a limited run sold through a track only program.

The standard Roadster is still expected to carry the original $200,000 base price and $250,000 Founders Series tier, both set when Tesla opened $50,000 and $250,000 reservations in 2017. Tesla VP of Vehicle Engineering Lars Moravy has confirmed production will happen at Gigafactory Texas, with Musk targeting 2027 or 2028, 12 to 18 months after whatever the company demonstrates next month.

Continue Reading

News

Tesla plans big safety improvements for Full Self-Driving v15

Published

on

Credit: Tesla

Tesla is planning to roll out some pretty significant safety and accident avoidance features with Full Self-Driving version 15, which will be the next major FSD deployment from the company.

Tesla AI lead Ashok Elluswamy used a near-miss this week to preview what the company says is the next leap in Full Self-Driving.

In response to a driver whose car had swerved away from another vehicle pulling out of a parking lot, Elluswamy wrote that he was glad the owner was safe and that “even earlier prediction of hazards, even faster reaction time and overall significantly better safety and collision avoidance” would arrive with FSD v15.

The comment landed as Tesla continues to treat software as the primary safety upgrade path. v15 is described internally as a larger architectural step, with a much bigger neural network and tighter coupling between prediction and control.

The company has already begun using early v15 software in some robotaxi operations while rolling out safety features such as Automatic Collision Evasion into current customer cars, allowing the driving stack to intervene even when the driver is in manual control.

Tesla is rolling out a new FSD version with a massive safety addition

Tesla’s published telemetry is the backbone of its safety argument. In recent North American Vehicle Safety Report data, vehicles with FSD (Supervised) engaged traveled roughly 5.1 million to 5.7 million miles between major collisions, defined as airbag-deployment events.

Tesla’s estimate of the U.S. average over the same period is about 699,000 miles per comparable crash. That is the comparison Tesla often frames as roughly seven times fewer major collisions.

A tighter comparison uses the same Tesla fleet. Cars driven manually with active safety features such as automatic emergency braking still recorded a major collision about every 2.1 million miles. Against that baseline, FSD’s advantage shrinks to roughly 2.4 to 2.7 times fewer severe crashes, which independent researchers argue is the more apples-to-apples figure.

European data released in 2026 pointed in the same direction: Tesla reported FSD as 3.5 times safer than manual driving in the Netherlands and 4.1 times fewer collisions than manually driven Teslas with active safety across more than 100 million kilometers in five approved countries.

Those numbers do not settle every debate. NHTSA’s Standing General Order still shows Tesla accounting for the large majority of U.S. Level 2 driver-assist crash reports, in part because the fleet logs far more assisted miles than rivals. Critics also note that Tesla’s “U.S. average” mixes crash definitions and driving mix.

Even so, Tesla’s own same-car comparisons, plus lower rates of automatic emergency braking and harsh maneuvers when FSD is engaged, are the evidence Elluswamy is pointing to when he says v15 will push prediction and collision avoidance further. The claim is not that software already eliminates risk. It is that each major version is meant to widen the gap between the system and an unaided human driver.

Continue Reading