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.
Elon Musk
We tested Tesla Full Self-Driving’s ability to let you text and drive
We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.
On Thursday, Tesla CEO Elon Musk said that Full Self-Driving v14.2.1 would enable texting and driving “depending on [the] context of surrounding traffic.”
Tesla CEO Elon Musk announces major update with texting and driving on FSD
We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.
I’d also like to add that, while Tesla had said back in early November that it hoped to allow this capability within one to two months, I still would not recommend you do it. Even if Tesla or Musk says it will allow you to do so, you should take into account the fact that many laws do not allow you to look at your phone. Be sure to refer to your local regulations surrounding texting and driving, and stay attentive to the road and its surroundings.
The Process
Based on Musk’s post on X, which said the ability to text and drive would be totally dependent on the “context of surrounding traffic,” I decided to try and find three levels of congestion: low, medium, and high.
I also tried as best as I could to always glance up at the road, a natural reaction, but I spent most of my time, during the spans of when it was in my hand, looking at my phone screen. I limited my time looking at the phone screen to a few seconds, five to seven at most. On local roads, I didn’t go over five seconds; once I got to the highway, I ensured the vehicle had no other cars directly in front of me.
Also, at any time I saw a pedestrian, I put my phone down and was fully attentive to the road. I also made sure there were no law enforcement officers around; I am still very aware of the law, which is why I would never do this myself if I were not testing it.
I also limited the testing to no more than one minute per attempt.
I am fully aware that this test might ruffle some feathers. I’m not one to text and drive, and I tried to keep this test as abbreviated as possible while still getting some insight on how often it would require me to look at the road once again.
The Results
Low Congestion Area
I picked a local road close to where I live at a time when I knew there would be very little traffic. I grabbed my phone and looked at it for no more than five seconds before I would glance up at the road to ensure everything was okay:
In full: the Low Congestion Area pic.twitter.com/6DqlBnekPn
— TESLARATI (@Teslarati) December 4, 2025
Looking up at the road was still regular in frequency; I would glance up at the road after hitting that five-second threshold. Then I would look back down.
I had no nudges during this portion of the test. Traffic was far from even a light volume, and other vehicles around were very infrequently seen.
Medium Congestion Area
This area had significantly more traffic and included a stop at a traffic light. I still kept the consecutive time of looking at my phone to about five seconds.
I would quickly glance at the road to ensure everything was okay, then look back down at my phone, spending enough time looking at a post on Instagram, X, or Facebook to determine what it was about, before then peeking at the road again.
There was once again no alert to look at the road, and I started to question whether I was even looking at my phone long enough to get an alert:
In full: the Medium Congestion Area pic.twitter.com/gnhIfBVe6Q
— TESLARATI (@Teslarati) December 4, 2025
Based on past versions of Full Self-Driving, especially dating back to v13, even looking out the window for too long would get me a nudge, and it was about the same amount of time, sometimes more, sometimes less, I would look out of a window to look at a house or a view.
High Congestion Area
I decided to use the highway as a High Congestion Area, and it finally gave me an alert to look at the road.
As strange as it is, I felt more comfortable looking down at my phone for a longer amount of time on the highway, especially considering there is a lower chance of a sudden stop or a dangerous maneuver by another car, especially as I was traveling just 5 MPH over in the left lane.
This is where I finally got an alert from the driver monitoring system, and I immediately put my phone down and returned to looking at the road:
In full: the High Congestion Area pic.twitter.com/K9rIn4ROvm
— TESLARATI (@Teslarati) December 4, 2025
Once I was able to trigger an alert, I considered the testing over with. I think in the future I’d like to try this again with someone else in the car to keep their eyes on the road, but I’m more than aware that we can’t always have company while driving.
My True Thoughts
Although this is apparently enabled based on what was said, I still do not feel totally comfortable with it. I would not ever consider shooting a text or responding to messages because Full Self-Driving is enabled, and there are two reasons for that.
The first is the fact that if an accident were to happen, it would be my fault. Although it would be my fault, people would take it as Tesla’s fault, just based on what media headlines usually are with accidents involving these cars.
Secondly, I am still well aware that it’s against the law to use your phone while driving. In Pennsylvania, we have the Paul Miller Law, which prohibits people from even holding their phones, even at stop lights.
I’d feel much more comfortable using my phone if liability were taken off of me in case of an accident. I trust FSD, but I am still erring on the side of caution, especially considering Tesla’s website still indicates vehicle operators have to remain attentive while using either FSD or Autopilot.
Check out our full test below:
Elon Musk
Tesla CEO Elon Musk announces major update with texting and driving on FSD
“Depending on context of surrounding traffic, yes,” Musk said in regards to FSD v14.2.1 allowing texting and driving.
Tesla CEO Elon Musk has announced a major update with texting and driving capabilities on Full Self-Driving v14.2.1, the company’s latest version of the FSD suite.
Tesla Full Self-Driving, even in its most mature and capable versions, is still a Level 2 autonomous driving suite, meaning it requires attention from the vehicle operator.
You cannot sleep, and you should not take attention away from driving; ultimately, you are still solely responsible for what happens with the car.
The vehicles utilize a cabin-facing camera to enable attention monitoring, and if you take your eyes off the road for too long, you will be admonished and advised to pay attention. After five strikes, FSD and Autopilot will be disabled.
However, Musk announced at the Annual Shareholder Meeting in early November that the company would look at the statistics, but it aimed to allow people to text and drive “within the next month or two.”
He said:
“I am confident that, within the next month or two, we’re gonna look at the safety statistics, but we will allow you to text and drive.”
“I am confident that, within the next month or two, we’re gonna look at the safety statistics, but we will allow you to text and drive.”
Does anyone think v14.3 will enable this? pic.twitter.com/N2yn0SK70M
— TESLARATI (@Teslarati) November 23, 2025
Today, Musk confirmed that the current version of Full Self-Driving, which is FSD v14.2.1, does allow for texting and driving “depending on context of surrounding traffic.”
Depending on context of surrounding traffic, yes
— Elon Musk (@elonmusk) December 4, 2025
There are some legitimate questions with this capability, especially as laws in all 50 U.S. states specifically prohibit texting and driving. It will be interesting to see the legality of it, because if a police officer sees you texting, they won’t know that you’re on Full Self-Driving, and you’ll likely be pulled over.
Some states prohibit drivers from even holding a phone when the car is in motion.
It is certainly a move toward unsupervised Full Self-Driving operation, but it is worth noting that Musk’s words state it will only allow the vehicle operator to do it depending on the context of surrounding traffic.
He did not outline any specific conditions that FSD would allow a driver to text and drive.
News
Tesla Semi just got a huge vote of confidence from 300-truck fleet
The confidential meeting marks a major step for the mid-sized carrier in evaluating the electric truck for its regional routes.
The Tesla Semi is moving closer to broader fleet adoption, with Keller Logistics Group wrapping up a key pre-production planning session with the electric vehicle maker’s team this week.
The confidential meeting marks a major step for the mid-sized carrier in evaluating the electric truck for its regional routes.
Keller’s pre-production Tesla Semi sessions
Keller Logistics Group, a family-owned carrier with over 300 tractors and 1,000 trailers operating in the Midwest and Southeast, completed the session to assess the Tesla Semi’s fit for its operations. The company’s routes typically span 500-600 miles per day, positioning it as an ideal tester for the Semi’s day cab configuration in standard logistics scenarios.
Details remain under mutual NDA, but the meeting reportedly focused on matching the truck to yard, shuttle and regional applications while scrutinizing economics like infrastructure, maintenance and incentives.
What Keller’s executives are saying
CEO Bryan Keller described the approach as methodical. “For us, staying ahead isn’t a headline, it’s a habit. From electrification and yard automation to digital visibility and warehouse technology, our teams are continually pressure-testing what’s next. The Tesla Semi discussion is one more way we evaluate new tools against our standards for safety, uptime, and customer ROI. We don’t chase trends, we pressure-test what works,” Keller said.
Benjamin Pierce, Chief Strategy Officer, echoed these sentiments. “Electrification and next-generation powertrains are part of a much broader transformation. Whether it’s proprietary yard systems like YardLink™, solar and renewable logistics solutions, or real-time vehicle intelligence, Keller’s approach stays the same, test it, prove it, and deploy it only when it strengthens service and total cost for our customers,” Pierce said.
We tested Tesla Full Self-Driving’s ability to let you text and drive
Tesla CEO Elon Musk announces major update with texting and driving on FSD
