News
[Update: Scrubbed] SpaceX Starship to attempt same-day static fire and launch
Update: Starship SN11 did manage a timely static fire around 8am CDT but after hours of work, SpaceX appears to have scrubbed a Friday, March 26th launch attempt.
SpaceX’s website has yet to be updated and Friday’s FAA TFR is still active but a road closure meant to last until 7:30 pm CDT to cover the static fire and launch was retracted after the highway was reopened around 2:45 pm. It’s unclear what caused the scrub but weather or technical issues from the static fire are two likely candidates. SpaceX still has TFRs active on Saturday and Sunday, but the company hasn’t tested or flown on a weekend in months.
Lacking only an official confirmation, SpaceX appears to be readying the fourth full-size Starship prototype to attempt a Raptor static fire test and launch on the same day.
That hopeful day in question happens to be today – Friday, March 26th. If all goes according to plan, Starship serial number SN11 will fire up its three Raptors, verifying their health after an engine was apparently swapped out on Wednesday. Possibly just an hour or two later, after detanking and retanking liquid oxygen and methane propellant, the Starship prototype could lift off on SpaceX’s fourth high-altitude test flight.
Late on March 24th, SpaceX rolled Raptor engine SN46 from its Boca Chica factory to the launch pad, where Starship SN11 is installed on one of two suborbital launch mounts. The engine move and subsequent installation came as a surprise, as nobody managed to catch an implied Starship SN11 engine removal in the two or three days prior (extremely thick fog being the likeliest cause).
The implied issue with the Raptor that was removed is likely to blame for a several-day launch delay that followed Starship’s seemingly successful Monday static fire. After that test, SN11’s launch was initially scheduled as early as Tuesday or Wednesday, only to slip day by day as the week proceeded. SN11 first rolled to the launch pad on March 8th, just 18 days ago, so launch delays don’t come as a huge surprise given that the current factory-to-launch record for a three-engine Starship is 33 days, three static fires, and one engine swap.
If SN11 manages a same-day static fire and launch on March 26th, it will still crush that record by almost 50%. To an extent, the feat also isn’t unprecedented. On March 3rd, Starship SN10 aborted its first true launch attempt milliseconds after Raptor ignition when the rocket’s flight computer detected indications that they were producing too much thrust. Amazingly, instead of scrubbing the launch attempt, SpaceX loosened Starship SN10’s thrust limit parameters and tried again, successfully lifting off just three hours after the abort.
Despite the abort and immediate hands-free recycle, Starship SN10 subsequently became the first prototype of its kind to launch to 10 km (6.2 mi), free-fall back to earth, and land in one piece. Minutes later, a fire and harder landing than expected conspired to make SN10 explode, but the test flight was arguably still a massive success. Simultaneously, the flight indicated that Starships are technically capable of successfully flying hours after a post-ignition launch abort, demonstrating an extraordinary level of robustness for clustered high-performance rocket engines.
As such, while it’s probably reasonable to assume that Starship SN11 wont launch today, SN10 proved that there is nonzero chance of a static fire and launch hours apart. Additionally, given just how close SN10 go to unequivocal success (i.e. a soft and survivable landing), Starship SN11 has the best chance yet at at launching, landing, and making it through the ordeal without exploding.
Starship SN11’s third static fire and first launch attempt are both currently scheduled sometime between 7am and 7:30pm CDT (UTC-5). Stay tuned for updates as we wait for SpaceX’s official confirmation and an evacuation notice of Boca Chica Village residents.
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.”
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.