Connect with us

News

SpaceX operational astronaut launch debut back on track after “nail polish” delay

SpaceX's Crew-1 NASA astronauts pose in front of the Crew Dragon that will ferry them to the International Space Station just days before the spacecraft shipped to Florida. (SpaceX)

Published

on

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.

SpaceX COO and President Gwynne Shotwell stands in front of the Falcon 9 booster that will soon ferry four astronauts to the ISS. (TIME/SpaceX)

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.

Crew-1 Falcon 9 booster B1061 arrived in Florida on July 14th. (SpaceX)
Falcon 9 booster B1063 was spotted on its way west from McGregor, Texas to Vandenberg Air Force Base, California in August. (D. Stamos)

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?

Advertisement

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.

A Merlin 1D engine is inspected and tested in McGregor, Texas. (SpaceX)

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.”

A Merlin 1D is prepared at SpaceX’s Hawthorne factory. The small cylindrical tube on the side is the engine’s gas generator. (SpaceX)

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.

A Falcon 9 Block 5 booster’s engine section and heat shield. (SpaceX/Discovery)

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.

NASA astronauts Shannon Walker, Victor Glover, and Mike Hopkins, and JAXA (Japanese) astronaut Soichi Noguchi are nearly set to fly on Crew-1. (SpaceX)
Crew-1 will follow in the fresh footsteps of NASA astronauts Bob Behnken and Doug Hurley’s near-flawless Demo-2 Crew Dragon launch and landing debut. (NASA/Bill Ingalls)

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.

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

Elon Musk

Elon Musk reveals date of Tesla Full Self-Driving’s next massive release

Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.

Published

on

Tesla CEO Elon Musk revealed the date of Full Self-Driving’s next massive release: v14.3.

For months, Tesla owners with Hardware 4 have been utilizing Full Self-Driving v14.2 and subsequent releases. Currently, the most up-to-date FSD version is v14.2.2.5, which has definitely brought out mixed reviews. With releases, some things get better, and other things might regress slightly.

For the most part, things are better in terms of overall behavior.

However, many owners have been looking forward to the next release, which is v14.3, about which Musk has said many great things. Back in November, Musk said that v14.3 “is where the last big piece of the puzzle lands.”

He added:

“We’re gonna add a lot of reasoning and RL (reinforcement learning). To get to serious scale, Tesla will probably need to build a giant chip fab. To have a few hundred gigawatts of AI chips per year, I don’t see that capability coming online fast enough, so we will probably have to build a fab.”

Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.

Tesla Full Self-Driving v14.2 is a considerable improvement from early versions of the suite, but we have written about the somewhat confusing updates that have come with recent versions.

Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever

They’ve been incredibly difficult to gauge in terms of progress because some things have gotten better, but there seems to be some real regression on a handful of things, especially with confidence and assertiveness.

Musk confirmed today on X that Tesla is already testing v14.3 internally right now. It will hit a wide release “in a few weeks,” so we should probably expect it by late April.

Overall, there are high hopes that v14.3 could be a true game changer for Tesla Full Self-Driving, as many believe it could be the version that Robotaxis in Austin, Texas, some of which are driverless and unsupervised, are running.

It could also include some major additions, including “Banish,” also referred to as “Reverse Summon,” which would go find a parking spot after dropping occupants off at their destination.

What Tesla will roll out, and when exactly it arrives, all remain to be seen, but fans have been ready for a new version as v14.2.2.5 has definitely run its course. We have had a lot of readers tell us their biggest request is to fix Navigation errors, which seem to be one of the most universal complaints among daily FSD users.

Continue Reading

Cybertruck

Chattanooga Charge: Tesla and EV fans ready for the Southeast’s wildest Tesla party

From Cybertruck Convoys to Kid-Friendly Fun Zones: The Chattanooga Charge Has Something for Everyone

Published

on

By

Hundreds of like-minded Tesla and EV enthusiasts are descending on Chattanooga Charge this weekend for the largest Tesla meet in the Southeast. Taking place on March 20–22, 2026 at the stunning Tennessee Riverpark.

If you were there last year, you’ll know that it’s the ultimate experience to see the wildest Teslas in action, see the best in EV tech, and arguably the most fun – finally put a name to the face and connect with those social media buddies IRL! Oh, and that epic night time Tesla light show is a once-in-a-lifetime experience that will transform the Riverpark into something out of a sci-fi film that’s remarkably unforgettable and must be seen in person.

This year’s event takes everything up a notch, with over 100 Cybertrucks expected to be on display, many sporting jaw-dropping modifications and custom wraps that push the boundaries of what these stainless steel beasts can look like.

Whether you’re a diehard Tesla fan, EV supporter, or just EV-mod-curious, the sheer spectacle is worth the drive.

The Chattanooga Charge doesn’t wait until Saturday morning to get started. The weekend technically kicks off Friday, March 20th, and the venue sets the tone immediately. Come share roadtrip stories over drinks at the W-XYZ Rooftop Bar on the top floor of the Aloft Chattanooga Hamilton Place Hotel, with sunset views over the city.

Come morning, nurse your hangover with a some good coffee, and convoy with hundreds of other Tesla and EV drivers through Chattanooga to the event for some morning meet and greets before the speaker panel starts and the food trucks fire up.

Tesla owner clubs travel from across the country to be here, not just to show off their vehicles,, but to connect, share, and celebrate a shared passion for the future of driving.

Sounds like a plan to me. See you there, guys. Don’t miss it. Get your tickets at ChattanoogaCharge.com and join the charge. 🔋⚡

Chattanooga Charge is a premier Tesla and EV gathering inspired by the X Takeover, known as one of the largest Tesla event gatherings. What began as a bold idea from the team at DIY Wraps/TESBROS, hosted in their hometown of Chattanooga, Tennessee, the event quickly became a movement across social media. The first annual Chattanooga Charge united over 16 Tesla clubs from 16 states, proof that the EV community was hungry for something big in the South. Year after year, the event has grown in scale, ambition, and heart.

Continue Reading

News

Tesla Full Self-Driving gets latest bit of scrutiny from NHTSA

The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.

Published

on

Credit: Tesla

The National Highway Traffic Safety Administration (NHTSA) has elevated its probe into Tesla’s Full Self-Driving (Supervised) suite to an Engineering Analysis.

The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.

The step up into an Engineering Analysis is often required before the NHTSA will tell an automaker to issue a recall. However, this is not a guarantee that a recall will be issued.

The NTHSA wants to examine Tesla FSD’s ability to assess road conditions that have reduced visibility, as well as detect degradation to alert the driver with sufficient time to respond.

The Office of Defects Investigation (ODI) will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications Tesla makes to the degradation detection system, including the timing, purpose, and capabilities of the updates.

Tesla routinely ships software updates to improve the capabilities of the FSD suite, so it will be interesting to see if various versions of FSD are tested. Interestingly, you can find many examples from real-world users of FSD handling snow-covered roads, heavy rain, and single-lane backroads.

However, there are incidents that the NHTSA has used to determine the need for this probe, at least for now. The agency said:

“Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred.”

It continues to say in its report that a review of Tesla’s responses revealed additional crashes that occurred in similar environments showed FSD “did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path.”

The next steps of the NHTSA Engineering Analysis require the agency to gather further information on Tesla’s attempts to upgrade the degradation detection system. It will also analyze six recent potentially related incidents.

The investigation is listed as EA26002.

Continue Reading