Connect with us

News

SpaceX schedules second Starship static fire after first test ends prematurely

On January 6th, SpaceX fired up Starship SN9's three Raptor engines for the first time. (NASASpaceflight - bocachicagal)

Published

on

Update: SpaceX appears to have plans for a second triple-Raptor static fire for Starship SN9 after the rocket’s first test was cut short for unknown reasons.

Identical to previous road closure windows, SpaceX will have an opportunity to test Starship SN9 from 8 am to 5 pm CST (UTC-6) on Friday, January 8th, potentially paving the way for a high-altitude launch attempt early next week if the second static fire goes as planned. Stay tuned for updates!

In what is likely one of the last steps before SpaceX’s next high-altitude Starship launch attempt, the company appeared to successfully put Starship serial number 9 (SN9) through its first triple-Raptor static fire test.

Relatively late into a test window that opened at 8 am CST (UTC-6) but was later pushed to noon, SpaceX’s first Starship SN9 static fire attempt began in earnest around 3:15 pm CST. Signified by venting activity at the propellant farm tasked with preparing and loading liquid oxygen and methane on Starships, slight tweaks in the test flow were observed but the static fire occurred more or less when expected at 4:07 pm.

Advertisement

SN9 ignited all three of its Raptors in quick succession and shut the engines down over the course of 1.5-2 seconds – extremely short relative to all previous nominal Starhopper or Starship-mounted Raptor static fires. Long-time followers immediately noted that small discrepancy, speculating that it could either have been a post-ignition abort or intentionally shortened to avoid damaging the pad’s concrete surface (an incident that’s occurred several times during recent tests).

Not long before the short static fire, SpaceX extended the end of its January 6th test window (in the form of road closure notices) from 5 pm to 8 pm. Oddly, rather than the expected response of detanking Starship and reopening the road after a successful test, SpaceX essentially recycled SN9 and began a separate test around 6 pm. The road was never reopened and a SpaceX team never headed back to the pad between the tests, implying that the company may have run into a minor hardware or software bug earlier in the day.

It’s unclear what the actual goal of the second attempt was and it’s more or less impossible to know for sure with confirmation from CEO Elon Musk. It’s possible – if unlikely – that the first static fire went exactly as planned and the follow-up test was meant to be a simple data-gathering wet dress rehearsal (WDR). Either way, after a surprise downpour briefly engulfed Starship SN9 minutes prior, the second test appeared to abort about 30 minutes into propellant conditioning and loading, precluding both a complete WDR and/or static fire.

Starship SN9 is pictured preparing for its first static fire attempt on January 3rd. (NASASpaceflight – bocachicagal)

According to a test notice received on January 6th by NASASpaceflight contributer and photographer Mary (bocachicagal), SpaceX has another test window available on January 7th in the event that Wednesday’s testing was partially unsuccessful. In a rare case, SpaceX’s hand-distributed warning for residents preceded any additional planned road closures, the last of which lifted on January 6th.

On January 5th, SpaceX received a trio of Temporary Flight Restrictions (TFRs) from the FAA that will allow the company to restrict access to nearby airspace for high-altitude Starship launch attempts on January 8th, 9th, and 10th. Lacking an unequivocally successful static fire, it’s highly unlikely – but not impossible – that Starship will be ready for a launch attempt during any of those three windows. Still, it’s safe to say that SN9 is probably less than a week away from its first flight – expected to be a carbon copy of SN8’s 12.5 km (7.8 mi) launch and landing attempt – if SpaceX can complete a full-duration static fire in the next day or two.

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