News
NASA denies SpaceX Crew Dragon propellant leak report, reveals unrelated heat shield defect
In a partial response to a report alleging evidence of several significant anomalies during a recent private astronaut launch that could affect a crew of NASA astronauts launched last month, the space agency has issued a statement denying those claims. However, the same statement simultaneously revealed that SpaceX recently discovered a different problem with a different Crew Dragon spacecraft component during ground testing.
On May 23rd, Space Explored published a report alleging that a SpaceX Crew Dragon spacecraft experienced major issues during Axiom-1, the company’s first all-private astronaut launch to the International Space Station (ISS). According to sourced info and a possible internal SpaceX memo, some of Dragon’s toxic propellant leaked during the 17-day flight, damaged or weakened parts of its heat shield, and “[caused] dangerously excessive wear upon reentry.” In general, the report appeared to be well-sourced and even alleged that NASA’s Engineering and Safety Center (NESC) had opened an investigation. Additionally, when approached for comment, neither NASA nor SpaceX were initially willing to speak on the record, which also meant that neither denied the accusations.
A day later, NASA provided an official statement to Space Explored explicitly denying that there has been any propellant leak, heat shield contamination, or excessive heat shield wear on any of “Dragon’s recent crew reentries.”
NASA also dismissed concerns about the reuse of a previously-flown Cargo Dragon 2 heat shield structure on Crew-4, which launched just two days after Axiom-1’s recovery and is scheduled to spend four to five more months in orbit. It also noted that the reuse of Dragon’s heat shield tiles – the structures that take the brunt of most reentry heating and are immersed in salt water after every mission – is extremely limited and has only been attempted on occasional Cargo Dragon missions.
Simultaneously, NASA revealed that “a new heat shield composite structure intended for flight on Crew-5 did not pass an acceptance test” at SpaceX’s Hawthorne, California Dragon factory. The unrelated test failure was blamed on a manufacturing defect and NASA betrayed no sign of serious concern in its statement, suggesting that the problem may be less serious than it sounds. In response, NASA says SpaceX will simply use a different heat shield composite structure for Crew-5, which is scheduled to launch no earlier than (NET) September 2022.
The data associated with Dragon’s recent crew reentries was normal – the system performed as designed without dispute. There has not been a hypergol leak during the return of a crewed Dragon mission nor any contamination with the heat shield causing excessive wear. SpaceX and NASA perform a full engineering review of the heat shield’s thermal protection system following each return, including prior to the launch of the Crew-4 mission currently at the International Space Station. The heat shield composite structure (structure below the tile) was re-flown per normal planning and refurbishment processes. The thermal protection system on the primary heat shield for Crew-4 was new, as it has been for all human spaceflight missions. SpaceX has only demonstrated reuse of selected PICA (Phenolic-Impregnated Carbon Ablator) tiles, which is a lightweight material designed to withstand high temperatures, as part of the heat shield on cargo flights.
NASA and SpaceX are currently in the process of determining hardware allocation for the agency’s upcoming SpaceX Crew-5 mission, including the Dragon heat shield. SpaceX has a rigorous testing process to put every component and system through its paces to ensure safety and reliability. In early May, a new heat shield composite structure intended for flight on Crew-5 did not pass an acceptance test. The test did its job and found a manufacturing defect. NASA and SpaceX will use another heat shield for the flight that will undergo the same rigorous testing prior to flight.
Crew safety remains the top priority for both NASA and SpaceX and we continue to target September 2022 for launch of Crew-5.
NASA – May 24th, 2022
Some oddities do remain. While NASA’s explicit refutation should be taken as the definitive final word on the matter, it’s still very unusual that NASA and SpaceX refused or were unable to quickly and publicly deny the claims within a few hours of being asked. That could simply be a consequence of NASA and SpaceX’s poor internal and external communication or both parties’ love for withholding information from taxpayers about systems and technologies that those same taxpayers have paid for.
-
On the opposite hand, after Crew Dragon’s Demo-2 run-in with greater-than-expected heat shield wear in 2020, it’s almost impossible to imagine that NASA and SpaceX would have proceeded with Crew-4’s launch two days after Axiom-1’s recovery without confidently verifying that heat shield erosion was within normal bounds. SpaceX’s upgraded Phenolic-Impregnated Carbon Ablator (PICA-X) Dragon heat shield tiles are reportedly designed to erode [PDF] less than a centimeter of their circa-2017 ~7.5 cm (3 in) thickness after each reentry. Musk has gone even further, stating in 2012 that “[PICA-X] can potentially be used hundreds of times for Earth orbit re-entry with only minor degradation each time.” If true, it would be extremely difficult for even a brisk post-flight inspection of Axiom-1’s Dragon capsule to miss what Space Explored described as “dangerously excessive wear.”
In theory, during recovery, even a minute propellant leak should have also been immediately detected by SpaceX’s recovery team, as the very first part of the hands-on process involves a small team with gas masks and detectors approaching the floating capsule to ensure that it’s safe for others to approach. Crew Dragon’s liquid monomethylhydrazine (MMH) fuel and dinitrogen tetroxide (NTO) oxidizer are highly toxic in small quantities and MMH is a known carcinogen.
All told, news of a potential propellant leak and anomalous heat shield performance appears to have been a false alarm, although – coincidentally or not – a seemingly minor anomaly with an unflown Crew Dragon heat shield structure did occur earlier this month. Despite that anomaly, Crew-4 and Crew-5 are otherwise proceeding nominally and NASA appears to be content with Crew Dragon’s performance during several recent launches and recoveries.
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
Tesla silences Robotaxi turn signals in sweeping but polarizing change
Tesla claims supplier is holding Cybertruck production hostage
