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.
Elon Musk
SpaceX secures win as US labor board drops oversight case
The NLRB confirmed that it no longer has jurisdiction over SpaceX.
SpaceX scored a legal victory after the National Labor Relations Board (NLRB) decided to dismiss a case which accused the company of terminating engineers who were involved in an open letter against founder Elon Musk.
The NLRB confirmed that it no longer has jurisdiction over SpaceX. The update was initially shared by Bloomberg News, which cited a letter about the matter it reportedly reviewed.
In a letter to the former employees’ lawyers, the labor board stated that the affected employees were under the jurisdiction of the National Mediation Board (NMB), not the NLRB. As a result, the labor board stated that it was dismissing the case.
As per Danielle Pierce, a regional director of the agency, “the National Labor Relations Board lacks jurisdiction over the Employer and, therefore, I am dismissing your charge.”
The NMB typically oversees airlines and railroads. The NLRB, on the other hand, covers most private-sector employers, as well as manufacturers such as Boeing.
The former SpaceX engineers have argued that the private space company did not belong under the NMB’s jurisdiction because SpaceX only offers services to “hand-picked customers.”
In an opinion, however, the NMB stated that SpaceX was under its jurisdiction because “space transport includes air travel” to get to outer space. The mediation board also noted that anyone can contact SpaceX to secure its services.
SpaceX had previously challenged the NLRB’s authority in court, arguing that the agency’s structure was unconstitutional. Jennifer Abruzzo, the NLRB general counsel under former United States President Joe Biden, rejected SpaceX’s claims. Following Abruzzo’s termination under the Trump administration, however, SpaceX asked the labor board to reconsider its arguments.
SpaceX is not the only company that has challenged the constitutionality of the NLRB. Since SpaceX filed its legal challenge against the agency in 2024, other high-profile companies have followed suit. These include Amazon, which has filed similar cases that are now pending.
News
Tesla accuses IG Metall member of secretly recording Giga Berlin meeting
The union has denied the electric vehicle maker’s allegations.
Police seized the computer of an IG Metall member at Tesla Giga Berlin on Tuesday amid allegations that a works council meeting was secretly recorded.
The union has denied the electric vehicle maker’s allegations.
In a post on X, Gigafactory Berlin plant manager André Thierig stated that an external union representative from IG Metall attended a works council meeting and allegedly recorded the session. Thierig described the event as “truly beyond words.”
“What has happened today at Giga Berlin is truly beyond words! An external union representative from IG Metall attended a works council meeting. For unknown reasons he recorded the internal meeting and was caught in action! We obviously called police and filed a criminal complaint!” Thierig wrote in his post on X.
Police later confirmed to local news outlet rbb24 that officers did seize a computer belonging to an IG Metall member at the Giga Berlin site on Tuesday afternoon. Tesla stated that employees had contacted authorities after discovering the alleged recording.
IG Metall denied Tesla’s accusations, arguing that its representative did not record the meeting. The union alleged that Tesla’s claim was simply a tactic ahead of upcoming works council elections.
The next works council election at Giga Berlin is scheduled for March 2 to 4, 2026. The facility’s management had confirmed the dates to local news outlets. The official announcement marks the start of the election process and campaign period.
Approximately 11,000 employees are eligible to participate in the vote.
The previous works council election at the plant took place in 2024, and it was triggered by a notable increase in workforce size. Under German labor law, regular works council elections must be held every four years between March 1 and May 31.
Elon Musk
Elon Musk’s xAI plants flag in Bellevue AI hotspot
The lease places xAI’s new office in one of the region’s fastest-growing tech hubs.
Elon Musk’s artificial intelligence company xAI has leased a full floor at Lincoln Square South in downtown Bellevue, WA, as per city permit filings.
The lease places xAI’s new office in one of the region’s fastest-growing tech hubs.
Public records indicate that xAI leased roughly 24,800 square feet in Lincoln Square South. The location was previously occupied by video game company Epic Games. Lincoln Square South is part of the Bellevue Collection, which is owned by Kemper Development Co.
The lease was first referenced in January by commercial real estate firm Broderick Group, which noted that an unnamed tenant had secured the space, as stated in a report from the Puget Sound Business Journal. Later filings identified xAI as the occupant for the space.
xAI has not publicly commented on the lease.
xAI hinted at plans to open an office in the Seattle area back in September, when the startup posted job openings with salaries ranging from $180,000 to $440,000. At the time, the company had narrowed its location search to cities on the Eastside but had not finalized a lease.
xAI’s Bellevue expansion comes as Musk continues consolidating his businesses. Last week, SpaceX acquired xAI in a deal that valued the artificial intelligence startup at $250 billion. SpaceX itself is now valued at roughly $1.25 trillion and is expected to pursue an initial public offering (IPO) later this year.
Musk already has a significant presence in the region through SpaceX, which employs about 2,000 workers locally. That initiative, however, is focused largely on Starlink satellite development.
Bellevue has increasingly become a center for artificial intelligence companies. OpenAI has expanded its local office footprint to nearly 300,000 square feet. Data infrastructure firms such as Crusoe and CoreWeave have also established offices downtown.
SpaceX secures win as US labor board drops oversight case
Tesla accuses IG Metall member of secretly recording Giga Berlin meeting
