Connect with us

News

SpaceX wants to launch its next Starship ASAP

Starship SN10 is ironically front and center in this SN9 prelaunch photo published by SpaceX.

Published

on

Contrary to recent comments from CEO Elon Musk, SpaceX appears to be forging ahead at full speed in a bid to launch its next Starship ASAP.

Known as Starship serial number 10 (SN10), the prototype is the latest in a series of four ships SpaceX has ultimately set aside from low(er)-altitude development testing. Starship SN8 – the first functional prototype to reach its full height – debuted on December 8th, 2020, blowing expectations out of the water with a failure mere seconds before the end of a more than six-minute flight test. According to Musk, had a fuel tank remained properly pressurized from start to finish, SN8 could have very well stuck the landing on the first try.

Two months later, after the better part of two weeks of licensing and static fire test delays, Starship SN9 attempted to carry the torch forward but suffered an unrelated failure slightly earlier than SN8’s. One of two Raptor engines failed to ignite for a high-risk flip and landing burn, causing the Starship to impact the ground even more violently than its predecessor. It’s unclear why the ill-fated Raptor failed to ignite or why the engine that did ignite appeared to experience a major failure shortly thereafter but rocket propulsion is extraordinarily difficult – and Raptor is near – or at – the end of that scale.

While SpaceX obviously hasn’t spun around and fixed a complex Starship propulsion issue in a matter of days, Musk eventually revealed his opinion that he, his engineers, or some combination of both “were too dumb” to exploit one obvious way to mitigate the risk of engine failure during flip and landing. That ‘obvious’ tweak: reignite all three of Starship’s available landing engines, not just two.

Advertisement

In theory, with a fast-enough response time, Starship could ignite all three Raptors, perform a supercharged flip from a belly- to tail-down orientation, and selectively shut off one of the engines based on the data from what is essentially a midair static fire. In the event that all three engines are performing nominally, Starship would shut down the least useful engine (i.e. the Raptor with the least leverage) for a gentle two-engine landing burn.

A failed two-engine landing burn vs. a successful three-engine ascent burn. (SpaceX)

Impressively, Musk said that SpaceX would implement those changes immediately, attempting the first three-engine reignition as early as Starship SN10’s launch debut. Already at the launch pad when Starship SN9 lifted off, SpaceX revealed plans to launch SN10 as early as February 2021 at the end of SN9’s test flight webcast.

A few days prior to SN9’s ill-fated test flight, Musk had also stated that Starship SN10 would perform a “cryoproof” test and only then have its three Raptor engines installed. Instead, in an apparent change of plans, SpaceX installed Starship SN10’s Raptors – SN39, SN50, and an unknown third engine – from February 5th to 7th.

On Sunday, local longtime resident Mary (aka BocaChicaGal) received an official safety alert from SpaceX, signaling plans for an explosive Starship test of some kind as early as Monday, February 8th. Historically, those overpressure safety warnings have only been distributed when SpaceX is preparing for a Starship static fire attempt. In other words, it’s possible that Starship SN10’s very first test could be a live wet dress rehearsal (WDR) with flammable liquid oxygen and methane propellant. If that WDR goes well, SpaceX could move directly into a one, two, or three-engine static fire.

Of course, as SN9’s lengthy test period rubbed in, Starship is still in the prototype stage and is far from a mature system, meaning that it’s always safer to expect delays than an on-time performance. To be clear, it’s far more likely that SpaceX will perform a familiar “cryo proof” test with non-flammable liquid nitrogen – perhaps hoping to complete a cryoproof and static fire in the same test window.

Either way, stay tuned for updates and follow along with NASASpaceflight’s excellent live coverage in the event that SpaceX really is prepared to static fire Starship SN10 between 9am and 6pm CST (UTC-6) on Monday.

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 ships out an update for everyone that California caused

“This change only updates the name of certain features and text in your vehicle,” the company wrote in Release Notes for the update, “and does not change the way your features behave.”

Published

on

Credit: Tesla

Tesla has shipped out an update for its vehicles that was caused specifically by a California lawsuit that threatened the company’s ability to sell cars because of how it named its driver assistance suite.

Tesla shipped out Software Update 2026.2.9 starting last week; we received it already, and it only brings a few minor changes, mostly related to how things are referenced.

“This change only updates the name of certain features and text in your vehicle,” the company wrote in Release Notes for the update, “and does not change the way your features behave.”

The following changes came to Tesla vehicles in the update:

  • Navigate on Autopilot has now been renamed to Navigate on Autosteer
  • FSD Computer has been renamed to AI Computer

Tesla faced a 30-day sales suspension in California after the state’s Department of Motor Vehicles stated the company had to come into compliance regarding the marketing of its automated driving features.

The agency confirmed on February 18 that it had taken a “corrective action” to resolve the issue. That corrective action was renaming certain parts of its ADAS.

Tesla discontinued its standalone Autopilot offering in January and ramped up the marketing of Full Self-Driving Supervised. Tesla had said on X that the issue with naming “was a ‘consumer protection’ order about the use of the term ‘Autopilot’ in a case where not one single customer came forward to say there’s a problem.”

It is now compliant with the wishes of the California DMV, and we’re all dealing with it now.

This was the first primary dispute over the terminology of Full Self-Driving, but it has undergone some scrutiny at the federal level, as some government officials have claimed the suite has “deceptive” names. Previous Transportation Secretary Pete Buttigieg was one of those federal-level employees who had an issue with the names “Autopilot” and “Full Self-Driving.”

Tesla sued the California DMV over the ruling last week.

Continue Reading

News

Tesla workers push back against Giga Berlin unionization

“IG Metall did not succeed in Giga Berlin‘s works council election earlier today. The union share was reduced from nearly 40% in 2024 to 31% in 2026! This is a clear message by the Giga Berlin team towards an independent co-determination! The list called Giga United, led by the current chairwoman, Michaela Schmitz, received the most votes with more than 40%! Good news for Giga Berlin!”

Published

on

Tesla workers pushed back against unionization efforts at Gigafactory Berlin, and over the past few years, there has been a dramatic decrease in interest to unionize at the German plant.

Gigafactory Berlin Plant Manager André Thierig announced on Wednesday that IG Metall, the European union group, saw its share reduce from 40 to 31 percent in 2026 as employees eligible to vote on the issue. Instead, the Giga Berlin team, known as Giga United, received the most votes with more than 40 percent.

Thierig gave specific details in a post on X:

“IG Metall did not succeed in Giga Berlin‘s works council election earlier today. The union share was reduced from nearly 40% in 2024 to 31% in 2026! This is a clear message by the Giga Berlin team towards an independent co-determination! The list called Giga United, led by the current chairwoman, Michaela Schmitz, received the most votes with more than 40%! Good news for Giga Berlin!”

There were over 10,700 total employees who were eligible to vote, with 87 percent of them turning out to cast what they wanted. There were three key outcomes: Giga United, IG Metall, and other notable groups, with the most popular being the Polish Initiative.

The 37-seat council remains dominated by non-unionized representatives, preserving Giga Berlin as Germany’s only major auto plant without a collective bargaining agreement.

Thierig and Tesla framed the outcome as employee support for an “independent, flexible, and unbureaucratic” future, enabling acceleration on projects like potential expansions or new models. IG Metall expressed disappointment, accusing management of intimidation tactics and an “unfair” campaign.

The first election of this nature happened back in 2022. In 2024, IG Metall emerged as the largest single faction with 39.4 percent, but non-union lists coalesced for a majority.

But this year was different. There was some extra tension at Giga Berlin this year, as just two weeks ago, an IG Metall rep was accused by Tesla of secretly recording a council meeting. The group countersued for defamation.

Tesla Giga Berlin plant manager faces defamation probe after IG Metall union complaint

This result from the 2026 vote reinforced Tesla’s model of direct employee-management alignment over traditional German union structures, amid ongoing debates about working conditions. IG Metall views it as a setback but continues advocacy. Tesla sees it as validation of its approach in a competitive EV market.

This outcome may influence future labor dynamics at Giga Berlin, including any revival of expansion plans or product lines, which Musk has talked about recently.

Continue Reading

News

SpaceX President Gwynne Shotwell details xAI power pledge at White House event

The commitment was announced during an event with United States President Donald Trump.

Published

on

xAI-supercomputer-memphis-environment-pushback
Credit: xAI

SpaceX President Gwynne Shotwell stated that xAI will develop 1.2 gigawatts of power at its Memphis-area AI supercomputer site as part of the White House’s new “Ratepayer Protection Pledge.” 

The commitment was announced during an event with United States President Donald Trump.

During the White House event, Shotwell stated that xAI’s AI data center near Memphis would include a major energy installation designed to support the facility’s power needs.

“As you know, xAI builds huge supercomputers and data centers and we build them fast. Currently, we’re building one on the Tennessee-Mississippi state line. As part of today’s commitment, we will take extensive additional steps to continue to reduce the costs of electricity for our neighbors… 

Advertisement

“xAI will therefore commit to develop 1.2 GW of power as our supercomputer’s primary power source. That will be for every additional data center as well. We will expand what is already the largest global Megapack power installation in the world,” Shotwell said.

She added that the system would provide significant backup power capacity.

“The installation will provide enough backup power to power the city of Memphis, and more than sufficient energy to power the town of Southaven, Mississippi where the data center resides. We will build new substations and invest in electrical infrastructure to provide stability to the area’s grid.”

Shotwell also noted that xAI will be supporting the area’s water supply as well. 

Advertisement

“We haven’t talked about it yet, but this is actually quite important. We will build state-of-the-art water recycling plants that will protect approximately 4.7 billion gallons of water from the Memphis aquifer each year. And we will employ thousands of American workers from around the city of Memphis on both sides of the TN-MS border,” she noted. 

The Ratepayer Protection Pledge was introduced as part of the federal government’s effort to address concerns about rising electricity costs tied to large AI data centers, as noted in an Insider report. Under the agreement, companies developing major AI infrastructure projects committed to covering their own power generation needs and avoiding additional costs for local ratepayers.

Continue Reading