Connect with us
Merlin 1D's kerolox exhaust is a blindingly bright, opaque yellow-orange. (Tom Cross) Merlin 1D's kerolox exhaust is a blindingly bright, opaque yellow-orange. (Tom Cross)

News

SpaceX static fires Falcon 9 with satellites on board for the first time in years

Falcon 9 B1049 lifts off for the first time in September 2018. The same booster has been assigned to Starlink v0.9. (Tom Cross)

Published

on

SpaceX has successfully completed a Falcon 9 static fire ahead of Starlink’s first dedicated launch, breaking a practice that dates back to Falcon 9’s last catastrophic failure to date.

That failure occurred in September 2016 around nine minutes before a planned Falcon 9 static fire test, completely destroying the rocket and the Amos-6 communications satellite payload and severely damaging Launch Complex 40 (LC-40). Since that fateful failure, all 42 subsequent Falcon 9 and Falcon Heavy satellite launches have been preceded by static fire tests without a payload fairing attached. This process typically adds 24-48 hours of work to launch operations, an admittedly tiny price to pay to reduce the chances of a rocket failure completely destroying valuable payloads. With Starlink v0.9, SpaceX is making different choices.

When supercool liquid oxygen ruptured a composite overwrapped pressure vessel (COPV) in Falcon 9’s upper stage, the resultant explosion and fire destroyed Falcon 9. Perhaps more importantly, the ~$200M Amos-6 satellite installed atop the rocket effectively ceased to exist, a loss that posed a serious threat to the livelihood of its owner, Spacecom. Posed with a question of whether saving a day or two of schedule was worth the potential destruction of customer payloads, both customers, SpaceX, and their insurers obviously concluded that static fires should be done without payloads aboard the rocket.

The only exceptions since Amos-6 are the launch debuts of Falcon Heavy – with a payload that was effectively disposable and SpaceX-built – and Crew Dragon DM-1, in which Falcon 9’s integration with Dragon’s launch abort system had to be tested as part of the static fire. Every other SpaceX rocket launch since September 2016 has excluded payloads during each routine pre-flight static fire.

Falcon Heavy ignites all 27 Merlin 1D engines for the first time ahead of its inaugural launch, January 2018. (SpaceX)
SpaceX completed a successful static fire of the first Falcon 9 rated for human flight on January 24th, 2019. (SpaceX)

SpaceX’s Spacecraft Emporium

Why the change of pace on this launch, then? The answer is simple: for the first time ever, SpaceX is both the sole payload/satellite stakeholder and launch provider, meaning that nearly all of the mission’s risk – and the consequences of failure – rest solely on SpaceX’s shoulders. In other words, SpaceX built and owns the Falcon 9 assigned to the mission, the 60 Starlink test satellites that make up its payload, and the launch complex supporting the mission.

Even then, if Falcon 9 were to fail during an internal SpaceX mission, customer launches could be seriously delayed by both the subsequent failure investigation failure and any potential damage to the launch complex. In short, although an internal mission does offer SpaceX some unique freedoms, it is still in the company’s best interest to treat the launch like any other, even if some customer-oriented corners are likely begging to be cut. Additionally, the loss of SpaceX’s first dedicated payload of 60 Starlink satellites could be a significant setback for the constellation, although it may be less significant than most would assume.

The same pad will host GovSat-1 in just over 24 hours.
A December 2017 panorama of SpaceX’s LC-40 facilities, CRS-13’s Cargo Dragon and Falcon 9. (Tom Cross/Teslarati)

This is not to say that SpaceX won’t take advantage of some of the newfound freedom permitted by Starlink launches. In fact, CEO Elon Musk has stated that one of SpaceX’s 2019 Starlink missions will become the first to reuse a Falcon fairing. Additionally, SpaceX is free to do things that customers might be opposed to but that the company’s own engineers believe to be low-risk. Notably, Starlink missions will be an almost perfect opportunity for SpaceX to flight-prove reusability milestones without having to ask customers to tread outside of their comfort zones.

The sheer scale of SpaceX proposed Starlink constellation – two phases of ~4400 and ~12,000 satellites – means that the company will need all the latent launch capacity it can get over the next 5-10 years, at least until Starship/Super Heavy is able to support internal missions. Extraordinary packing density will help to minimize the number of launches needed, but the fact remains that even an absurd 120 satellites per launch (double Starlink v0.9’s 60) would still require an average of 12 launches per year to finish Starlink before 2030.

One of the first two prototype Starlink satellites separates from Falcon 9’s upper stage in February 2018. (SpaceX)
OneWeb deployed six development satellites in February 2019, the company’s first hardware to reach orbit. (Arianespace)

In the meantime, thoughts of a dozen or more annual Starlink launches are somewhat premature. SpaceX’s first dedicated Starlink launch (deemed Starlink v0.9) is scheduled to lift off no earlier than 10:30 pm EDT (02:30 UTC), May 15th, and is being treated as an advanced but still intermediary step between the Tintin prototypes and a finalized spacecraft design. Still, in an unprecedented step, SpaceX has built sixty Starlink satellites for the development-focused mission, in stark contrast to the six satellites (still a respectable achievement) competitor OneWeb launched in February 2019 as part of its own flight-test program.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

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 update that brings massive change to two big features

“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