News
SpaceX operational astronaut launch debut back on track after “nail polish” delay
In a new NASA briefing, SpaceX vice president of build and flight reliability Hans Koenigsmann was able to explain in far more detail why a recent last-second Falcon 9 launch abort happened and how it wound up delaying the company’s first operational astronaut launch.
Now scheduled to lift off no earlier than (NET) 7:49 pm EST (00:49 UTC) on Saturday, November 14th, SpaceX’s Crew Dragon Crew-1 mission was originally expected to launch in late September, October 23rd, and October 31st. On October 2nd, however, a new Falcon 9 booster – sibling to Crew-1’s own new booster – automatically aborted its GPS III SV04 satellite launch attempt just two seconds before liftoff. The rare last-second abort was quickly blamed on “unexpected pressure rise in the turbomachinery gas generator” by CEO Elon Musk.
Likely built side-by-side with faulty GPS III SV04 Falcon 9 booster B1062 at SpaceX’s Hawthorne, California factory, Crew-1 Falcon 9 booster B1061 was almost immediately inspected to search for any commonality once the cause of the abort was better understood.
Just one week before the latest briefing, NASA human spaceflight program administrator and former Commercial Crew Program manager Kathy Lueders revealed in a statement on Twitter that SpaceX was still analyzing the cause of the abort but had already determined that at least one Crew-1 booster engine would need to be replaced, as well as one engine on Falcon 9 booster B1063.
Now, during NASA’s October 28th Crew-1 briefing, SpaceX’s Koenigsmann revealed that the company had ultimately decided to replace not one but two of Crew-1 booster B1061’s nine Merlin 1D engines. Thanks to Falcon 9’s namesake nine-engine booster design and SpaceX’s prolific rocket factory, that process was completed extraordinarily quickly, simply requiring the redirection of already qualified Merlin 1D engines from a fairly large pool. Based on Koenigsmann’s phrasing, SpaceX has already installed both replacement engines on the Crew-1 booster.
What, though, caused GPS III SV04’s launch abort and how did that affect Crew-1?
Rocket engine vs. “nail polish”
According to Koenigsmann, in the course of the rapid and complex mechanical and electrical ballet preceding Falcon 9 first stage ignition, the rocket’s autonomous flight computer observed that two of the GPS III SV04 booster’s nine Merlin 1D engines appeared to be running ahead of schedule, so to speak. The computer immediately halted the ignition process to avoid what could have otherwise been a “hard” (i.e. stressful or damaging) start. SpaceX quickly began inspecting the rocket within 24 hours but was unable to detect anything physically or electrically wrong with Falcon 9’s Merlin 1D engines and engine section.
Out of an abundance of caution, SpaceX removed both misbehaving engines and shipped them to its McGregor, Texas development and test facilities where – somewhat miraculously – the same premature startup behavior was replicated on the test stand. After a great deal of increasingly granular inspections, SpaceX finally narrowed the likely cause down to a tiny plumbing line feeding one of the engine’s gas generator relief valves. In a seemingly random subset of relatively new Merlin 1D engines, SpaceX eventually discovered that a supplier-provided relief valve line was sometimes clogged by a protective lacquer Koenigsmann likened to “red nail polish.”
Used to selectively exclude parts of the engine tubing during a surface finishing process known as anodization, the lacquer was either unsuccessfully removed on a random selection of engine parts or was accidentally channeled into a blockage by over-enthusiastic cleaning. Ultimately, for whatever, reason that miniscule blockage was enough to cause affected Merlin 1D engines to consistently attempt to ignite a tiny fraction of a second early.
Crucially, when SpaceX discovered the possible cause and cleaned out the blocked plumbing, each previously affected Merlin 1D engine performed perfectly, all but directly confirming both the cause and the cure for Falcon 9’s October 2nd abort.
Astronauts enter quarantine
In anticipation of SpaceX seemingly simple solution to the gas generator problem, NASA Commercial Crew Program manager Steve Stich revealed that SpaceX’s Crew-1 mission astronauts – Shannon Walker, Victor Glover, and Mike Hopkins, and JAXA (Japanese) astronaut Soichi Noguchi – had begun routine prelaunch quarantine procedures in anticipation of a November 14th launch.
Stich also offered a more specific Crew-1 schedule, beginning with an integrated Falcon 9 and Crew Dragon static fire test NET November 9th and a full dry dress rehearsal on November 11th before the first launch attempt on November 14th. Notably, thanks to coincidental orbital dynamics, a successful launch on November 14th would enable Crew Dragon to raise its orbit and rendezvous with the International Space Station a brisk eight and a half hours after liftoff – three times quicker than the more common 27.5-hour transit.
Stay tuned for updates as the mission’s launch date approaches.
Tesla has revealed plans through permit submissions for a massive Robotaxi charging hub in Austin, Texas.
Tesla plans to build the Supercharger hub in multiple phases, with the second phase potentially introducing wireless induction charging, something the company has been developing for the Robotaxi fleet.
Initially, 48 Tesla Robotaxi-geared Superchargers will be built on a lot just across from the St. Elmo, Texas, Service Center. There are about 80 additional spots that will not be impacted by phase 1 of the construction process.
Filings show that the second phase of the project will turn those 80 additional spots into wireless charging for Robotaxi, but it might be an error. The Key Notes state that item 3 is listed as “V4 Charging Cabinet to Support 80 Wireless Chargers in Phase 2. However, the drawings point to V3 Cabinets that are already tied to Superchargers:
There are roughly 128 total spots in the lot, but it is unclear if they will all be used for charging based on what appears to be some sort of typo in the blueprint.
A new Robotaxi fleet charging hub is coming soon to Austin, Texas!!
Permits have been filed for the installation of 48 (V3) stalls in a vehicle storage lot across the road from Tesla’s St Elmo service center. pic.twitter.com/xwRgSWDqht
— MarcoRP (@MarcoRPi1) August 18, 2026
This is among the first Robotaxi charging hubs Tesla has started to develop, as it currently has four others planned throughout various areas: one in Phoenix, one in San Antonio, another in Irving, which will serve the Dallas-Fort Worth area, and another in Las Vegas.
These projects are necessary as Tesla expands its Robotaxi program. Now that preparations have started for the public launch of Cybercab, Robotaxi will likely be expanding aggressively, especially over the next two to three years.
Last night, The Information reported that Tesla was planning to launch Cybercab as soon as the end of August. Hours later, Tesla then announced it was launching a competition for fans to potentially ride in Cybercab during its first public rides.
Tesla’s plan to expand its charging infrastructure in the regions where Robotaxi will initially operate is great preparation for the expanding service. There is still a lot to do, including launching the Cybercab on time.
Tesla got its largest order for the all-electric Class 8 Semi yet, a 500-unit order from Einride AB, a Swedish trucking company.
Einride made the announcement this morning following its second-quarter earnings call. The company said it plans to use 500 Tesla Semi units on its fleet intelligence platform, called Saga AI. The deployments will serve large companies like Amazon and will extend Einride’s electric freight network across logistics routes in California, New Jersey, Texas, Illinois, and Georgia.
🚨 Tesla has received a MASSIVE order from Swedish freight company Einride AB, which placed an order for 500 Tesla Semi trucks
Tesla’s biggest order for the Semi yet! pic.twitter.com/PrtLp5yzvh
— TESLARATI (@Teslarati) August 18, 2026
The deployment is being carried out in several phases over the next two years as Tesla ramps production of the Semi at its dedicated production facility in Sparks, Nevada. Einride will receive its first Semi units in September.
Saga AI
Saga AI is Einride’s dedicated fleet intelligence platform. It enables scaled adoption of electric trucks for freight use and allows shippers to integrate electric capacity without the operational burden or capital risks of managing a fleet. This helps integrate cost-efficient logistics and makes budgeting and forecasting much more accurate.
Tesla Semi’s Adoption
The Tesla Semi is now gathering large-scale clients past those who have helped the company operate a Pilot Program to gain initial information and feedback from real-world drivers.
Perhaps the biggest and most notable is that of Frito-Lay and PepsiCo., who have worked with Tesla for the past several years to dial in the finer details of the truck, including its efficiency and operation-related components.
Tesla Semi gets strange-but-understandable comparison from Jay Leno
There has been tremendous progress in that time, and it even catalyzed Tesla to make some design changes, which were unveiled earlier this year.
But Einride CEO Roozbeh Charli says his company’s partnership with Tesla will continue to push those things forward:
“This deployment is yet another proof point that we can execute at the scale our customers demand. Working closely with Tesla to bring next-generation Semis into active operations quickly and at scale is a testament to the strength of that partnership, and how quickly this technology is maturing from promise to daily operations.”
Additionally, Dan Priestley, the Director of the Semi Program at Tesla, said the partnership is ideal due to Einride’s focus on sustainable transport:
“Einride is at the forefront of sustainable freight, and we are thrilled to deepen our relationship with them through this order of 500 Semis. EV heavy trucks provide lower costs per mile from fuel savings, reduced maintenance, and better uptime over diesel trucks. These savings increase further through operational efficiency when deploying EV trucks at scale, and we are excited that Einride recognizes this and look forward to supporting their deployments.”
Elon Musk
India tells Elon Musk’s X to “Follow the Law” in latest censorship update
Elon Musk says X now exposes government censorship, but India’s secrecy laws complicate that promise.
Elon Musk’s promise to make government censorship requests on X “clearly visible” is running into a wall in India, where the law forbids the very disclosure Musk is promising.
On August 15, Musk responded to an update from X’s open-source algorithm team by writing “Any censorship required by governments is now clearly visible.” The claim referred to a change X pushed two days earlier to its public xai-org/x-algorithm repository, which now includes a controversial filter written directly into the code. The filter suppresses posts from 665 accounts flagged by Brazil’s Superior Electoral Court from appearing in the For You feed of any viewer located in Brazil, unless the viewer already follows the account. The election tied to the filter is scheduled for October 4.
India’s government wasn’t as impressed, and responded on Monday that “X will have to follow the law of the land,” in response to Musk’s transparency push covered by the Times of India. The problem is structural rather than political. India issues content blocking orders under Section 69A of its IT Act, and Rule 16 of the accompanying 2009 Blocking Rules requires those orders to stay confidential. Publishing an India equivalent of the Brazil filter, naming specific accounts and citing specific government orders, would itself violate Indian law. Government use of Section 69A has grown from roughly 6,000 orders a year between 2018 and 2023 to about 24,300 in 2025, according to a Tech Times report.
The contrast puts Musk’s transparency pledge in an odd spot. It works largely as advertised in Brazil, where electoral law requires disclosure and X can point to specific account IDs and a specific court order in public code. It cannot work the same way in India, where the law requires the opposite. X users in India will keep seeing content disappear from search and their feeds without any public accounting of why, even as X tells the rest of the world that its censorship compliance is now inspectable.
This isn’t the first time X’s fights with a national government have shaped how the platform operates. Brazil’s Supreme Court ordered X to suspend the accounts of sitting lawmakers and journalists in 2024, a standoff that cost X its Brazilian revenue for months and froze Starlink’s local accounts before the investigation into Musk and X was closed in March with no evidence of wrongdoing found. X also sued California over a state law requiring moderation disclosures, arguing the mandate itself violated the First Amendment.
Whether India’s government pursues anything beyond a public statement remains to be seen. For now, the mismatch between what X can legally publish and what different governments legally allow it to publish is the real story behind Musk’s seven word claim.
Tesla reveals plans for Robotaxi charging hub in Austin
Tesla Semi gets its largest order yet
