Connect with us

News

SpaceX returns Starship booster to factory after two major Raptor tests

Published

on

For the sixth time this year, SpaceX has returned the same Super Heavy booster prototype to its South Texas Starship factory after completing several tests.

Why is unclear. Super Heavy Booster 7 left the factory for the first time in March 2022 and has been stuck in a seemingly continuous state of testing, rework, and retesting ever since. While the pace of testing and progress was in many ways more aggressive from 2019 to mid-2021, it still can’t be said that SpaceX has been slacking off in 2022. Booster 7 alone completed more than 24 distinct tests (including six static fires) between early April and late November.

But in a shift from the first three or so years of steel Starship development, SpaceX CEO Elon Musk has ceased to be a consistent source of information on the purpose and results of many of those tests, even as NASA has begun to funnel hundreds of millions of taxpayer dollars into the Starship program. Save for occasional tidbits from SpaceX, Musk, and NASA; or deep unofficial analyses of public information, the day-to-day or week-to-week status of Starship has generally been relegated to speculation. Over the last few months, that information void has only grown larger.

Perhaps the biggest near-term update this year came from a senior NASA official on October 31st. In an advisory briefing, Mark Kirasich – Deputy Associate Administrator for Artemis Campaign Development – offered a surprising amount of detail about SpaceX’s near-term plans and even reported that Starship’s first orbital test flight was expected as early as December 2022, pending several crucial tests. But more than five weeks later, SpaceX appears to have only made a modest amount of progress towards those milestones and has yet to attempt the two most important tests.

Nonetheless, some progress – however indeterminate without official information – has been made. As of Kirasich’s briefing, SpaceX was in the middle of a relatively minor series of cautious propellant loading tests with Booster 7 and Ship 24, which were stacked on October 20th. After three more partial full-stack tests in the first seven days of November, Ship 24 was removed. Aside from the visible steps SpaceX took after, little is known about the outcome of those propellant loading tests.

Ship 24’s fate is a different story, but Super Heavy B7 appeared to make it through full-stack testing in great shape. On November 14th, Booster 7 completed a record-breaking 14-engine static fire, doubling its previous record of seven engines and likely becoming one of the most powerful rockets in history. Musk simply stated that the “test went well”.

Poor weather undoubtedly contributed, but it would be another 15 days before Booster 7’s next test. On November 29th, after an aborted test on the 28th, SpaceX followed Booster 7’s record-breaking 14-engine static fire with a longer 13-second test of 11 Raptors. Before engine ignition, SpaceX loaded Booster 7 with around 2800 tons (~6.2M lb) of liquid oxygen (LOx) propellant in less than 90 minutes, making it a partial wet dress rehearsal (the methane tank was barely filled) as well. Musk called it “a little more progress towards Mars” and SpaceX shared a photo of the static fire on Twitter, but the results of the test – meant “to test autogenous pressurization” – were kept mostly opaque.

That uncertainty didn’t help when two of Booster 7’s 33 Raptor engines were removed immediately after the long-duration test. Then, Booster 7 was removed from Starbase’s lone ‘orbital launch mount’ on December 2nd and rolled back to the factory’s High Bay assembly facility on December 3rd. Historically, SpaceX has only returned Booster 7 to the factory to repair damage or install missing hardware. Without official information, it’s impossible to say why Booster 7 returned for the sixth time.

The most optimistic explanation is that SpaceX brought the Super Heavy booster back to the factory to fully close out its engine section heat shield, which currently has 20 missing panels for each of its outer Raptor engines. But there’s a good reason that those panels were never reinstalled. Any replacements would need to be modified to ensure that the ad-hoc system installed to prevent the conditions that led to Booster 7’s first explosion from recurring can still be used for future static fire tests. Even then, it’s unclear why SpaceX would need to reinstall those panels now for Booster 7’s upcoming 33-engine static fire(s) and full-stack wet dress rehearsal(s) when they weren’t needed for 11 and 14-engine static fires and a dozen other fire-free tests.

Depending on why Booster 7 is back at the factory, there is a precedent for it returning to the launch site as early as next week. Alternatively, if major work or repairs are required, it could be six weeks before SpaceX returns the rocket to the launch pad. Given that the full wet dress rehearsals and one or several 33-engine static fires standing between Booster 7 and flight readiness will be riskier and more challenging than any other test the prototype has completed to date, there is no real chance that Starship will be ready for its first orbital launch this year.

Advertisement

In fact, without detailed information, especially regarding Ship 24’s mysterious state, it’s difficult to pinpoint a viable target for Starship’s orbital launch debut more specific than the first half of 2023. But with any luck, even if it requires a substantially longer wait, SpaceX’s recent decision to make Starbase move slower and break fewer things will hopefully pay off with a successful debut sometime next year.

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 Robotaxi ride-hailing without a Safety Monitor proves to be difficult

Published

on

Credit: Grok Imagine

Tesla Robotaxi ride-hailing without a Safety Monitor is proving to be a difficult task, according to some riders who made the journey to Austin to attempt to ride in one of its vehicles that has zero supervision.

Last week, Tesla officially removed Safety Monitors from some — not all — of its Robotaxi vehicles in Austin, Texas, answering skeptics who said the vehicles still needed supervision to operate safely and efficiently.

BREAKING: Tesla launches public Robotaxi rides in Austin with no Safety Monitor

Tesla aimed to remove Safety Monitors before the end of 2025, and it did, but only to company employees. It made the move last week to open the rides to the public, just a couple of weeks late to its original goal, but the accomplishment was impressive, nonetheless.

However, the small number of Robotaxis that are operating without Safety Monitors has proven difficult to hail for a ride. David Moss, who has gained notoriety recently as the person who has traveled over 10,000 miles in his Tesla on Full Self-Driving v14 without any interventions, made it to Austin last week.

He has tried to get a ride in a Safety Monitor-less Robotaxi for the better part of four days, and after 38 attempts, he still has yet to grab one:

Tesla said last week that it was rolling out a controlled test of the Safety Monitor-less Robotaxis. Ashok Elluswamy, who heads the AI program at Tesla, confirmed that the company was “starting with a few unsupervised vehicles mixed in with the broader Robotaxi fleet with Safety Monitors,” and that “the ratio will increase over time.”

This is a good strategy that prioritizes safety and keeps the company’s controlled rollout at the forefront of the Robotaxi rollout.

However, it will be interesting to see how quickly the company can scale these completely monitor-less rides. It has proven to be extremely difficult to get one, but that is understandable considering only a handful of the cars in the entire Austin fleet are operating with no supervision within the vehicle.

Continue Reading

News

Tesla gives its biggest hint that Full Self-Driving in Europe is imminent

Published

on

Credit: BLKMDL3 | X

Tesla has given its biggest hint that Full Self-Driving in Europe is imminent, as a new feature seems to show that the company is preparing for frequent border crossings.

Tesla owner and influencer BLKMDL3, also known as Zack, recently took his Tesla to the border of California and Mexico at Tijuana, and at the international crossing, Full Self-Driving showed an interesting message: “Upcoming country border — FSD (Supervised) will become unavailable.”

Due to regulatory approvals, once a Tesla operating on Full Self-Driving enters a new country, it is required to comply with the laws and regulations that are applicable to that territory. Even if legal, it seems Tesla will shut off FSD temporarily, confirming it is in a location where operation is approved.

This is something that will be extremely important in Europe, as crossing borders there is like crossing states in the U.S.; it’s pretty frequent compared to life in America, Canada, and Mexico.

Tesla has been working to get FSD approved in Europe for several years, and it has been getting close to being able to offer it to owners on the continent. However, it is still working through a lot of the red tape that is necessary for European regulators to approve use of the system on their continent.

This feature seems to be one that would be extremely useful in Europe, considering the fact that crossing borders into other countries is much more frequent than here in the U.S., and would cater to an area where approvals would differ.

Tesla has been testing FSD in Spain, France, England, and other European countries, and plans to continue expanding this effort. European owners have been fighting for a very long time to utilize the functionality, but the red tape has been the biggest bottleneck in the process.

Tesla Europe builds momentum with expanding FSD demos and regional launches

Tesla operates Full Self-Driving in the United States, China, Canada, Mexico, Puerto Rico, Australia, New Zealand, and South Korea.

Continue Reading

Elon Musk

SpaceX Starship V3 gets launch date update from Elon Musk

The first flight of Starship Version 3 and its new Raptor V3 engines could happen as early as March.

Published

on

Credit: SpaceX/X

Elon Musk has announced that SpaceX’s next Starship launch, Flight 12, is expected in about six weeks. This suggests that the first flight of Starship Version 3 and its new Raptor V3 engines could happen as early as March.

In a post on X, Elon Musk stated that the next Starship launch is in six weeks. He accompanied his announcement with a photo that seemed to have been taken when Starship’s upper stage was just about to separate from the Super Heavy Booster. Musk did not state whether SpaceX will attempt to catch the Super Heavy Booster during the upcoming flight.

The upcoming flight will mark the debut of Starship V3. The upgraded design includes the new Raptor V3 engine, which is expected to have nearly twice the thrust of the original Raptor 1, at a fraction of the cost and with significantly reduced weight. The Starship V3 platform is also expected to be optimized for manufacturability. 

The Starship V3 Flight 12 launch timeline comes as SpaceX pursues an aggressive development cadence for the fully reusable launch system. Previous iterations of Starship have racked up a mixed but notable string of test flights, including multiple integrated flight tests in 2025.

Interestingly enough, SpaceX has teased an aggressive timeframe for Starship V3’s first flight. Way back in late November, SpaceX noted on X that it will be aiming to launch Starship V3’s maiden flight in the first quarter of 2026. This was despite setbacks like a structural anomaly on the first V3 booster during ground testing.

“Starship’s twelfth flight test remains targeted for the first quarter of 2026,” the company wrote in its post on X. 

Continue Reading