News
SpaceX schedules Starship’s first triple-Raptor static fire test
A photo posted by CEO Elon Musk confirms that SpaceX has successfully installed three functional Raptors on Starship SN8 just hours before road closure notices revealed the company’s first triple-engine static fire schedule.
Technically, it’s incorrect to say that Starship serial number 8 (SN8) is the first prototype to receive three Raptor engines. Back in late-September 2019, in the lead-up to Musk’s promised Starship update event, the company installed three Raptors on the first full-scale prototype, known as Starship Mk1. The engines were only installed as an apparent fit test or even a photo opportunity, however – evidenced by the fact that they weren’t actually plumbed to the Starship’s propellant tanks.
Even then, in September 2019, Starship Mk1 was far from ready to make use of Raptor engines and was more than a month away from attempting its first pressure and cryogenic proof tests – tests it quickly failed. As such, Starship SN8 – having more or less successfully passed its ‘cryo proof’ by October 9th – is undoubtedly the first ship to have a shot at igniting multiple Raptor engines at once.
Curiously, SpaceX remained quiet for several days after Starship SN8 passed its first big test. Whereas with past Starship prototypes SpaceX has often filed test plans (appearing in the form of road closures) even before the current phase of testing is complete, the company waited until Tuesday, October 14th to file closure notices for “SN8 static fire” testing.
Same as Starships SN4, SN5, and SN6, all of which successfully graduated from cryo proof to static fire testing (and even flight tests for the latter two), SpaceX began Starship SN8’s test campaign with a cryo proof. It took three days and at least as many attempts but SN8 ultimately “passed cryo proof” according to Elon Musk, likely meaning that the ship reached sustained pressures of 7.5 bar (~110 psi) or more.
Cryo proof complete, SpaceX installed Starship SN8’s engines – the first time multiple Raptors have been fully integrated with a rocket or test stand – in preparation for another Raptor first: multi-engine static fires. While modern computation fluid dynamics (CFD) and modeling mean that the great unknowns of rocket propulsion are rarely as opaque as they used to be, the first test of multiple powerful engines in close proximity is still a guaranteed recipe for surprises.
Thanks to expertise hard-won from nearly 100 Falcon 9 and Falcon Heavy launches, SpaceX is likely the world’s foremost expert in the challenges and dynamics of the proximity operation of more than two rocket engines. At the same time, though, Raptor is a dramatically different engine than Merlin 1D and while Starship will only have six engines at most, those six engines will produce thrust equivalent to almost two entire Falcon 9 boosters.
In other words, even with a (relatively) simple three-Raptor static fire, SpaceX will be treading new ground and will almost certainly end up learning one or several things about Raptor’s design and operation. More likely than not, SpaceX will begin Starship SN8’s static fire test campaign with a wet dress rehearsal (like a cryo proof but with real liquid methane and oxygen propellant) and transition into a Raptor spin prime (turbopump spin-up) or preburner test (a turbopump spin-up but with partial combustion) if the WDR goes smoothly. If all three Raptor engines appear healthy, SpaceX may recycle and attempt the first static fire just an hour or two later.
Starship SN8’s triple-Raptor static fire test window opened at 9pm CDT on October 14th and closes at 6am on the 15th, with an identical 9pm-6am backup on the 15th and another window from 8am to 4:30pm on the 16th. LabPadre (below) will continue to offer 24/7 views of Starship, including any static fire testing, while NASASpaceflight.com will likely provide live coverage once testing begins in earnest.
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.”
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.”
This 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.
Sales in California will continue uninterrupted.
— Tesla North America (@tesla_na) December 17, 2025
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.
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!”
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.
BREAKING! 🚨
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 theGiga Berlin team towards an independent co-determination!
The list called Giga…
— André Thierig (@AndrThie) March 4, 2026
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.
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.
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…
“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.
“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.
Tesla ships out an update for everyone that California caused
Tesla workers push back against Giga Berlin unionization
