News
SpaceX waits in the wings as NASA risks maiming Jupiter probe to pinch pennies
SpaceX and its Falcon Heavy rocket continue to wait in the wings as NASA risks maiming its ‘Europa Clipper’ Jupiter probe by pinching the wrong pennies.
For the second time, NASA has performed “continuation/termination reviews” of three of the Europa Clipper spacecraft’s scientific instruments after budget overruns on the order of no more than a few tens of millions of dollars. Thankfully, no instruments were canceled, unlike the “ICEMAG” magnetometer that was functionally killed last year. Still, a NASA program scientist casually noted that the space agency would tolerate launching without one of two cameras and would offer no more funding to a mass spectrometer instrument (MASPEX), raising the risk of instrument failure during the challenging mission.
For any scientific spacecraft or rover, the instruments carried along are effectively the entire reason for their existence: if those instruments are faulty (or even removed before launch), the mission is effectively rendered pointless. Further, due to the sheer complexity and challenges posed by the act of getting to the destination and surviving after arrival, the actual instruments most scientific spacecraft carry represent a tiny fraction of the overall mission cost and mass. It’s not easy to readily imagine a better way to signal inept program management than by singularly focusing on that tiny, lifeblood-esque portion of a spacecraft’s budget. Undeterred, that is exactly what NASA appears to be doing with Europa Clipper – penny-wise, perhaps, but undoubtedly pound-foolish.
It’s not always true that only a small portion of an exploratory spacecraft’s budget is spent on scientific instruments but it absolutely is when it comes to Europa Clipper. Originally hoped to cost as little as $2 billion in 2013, Europa Clipper’s budget allocation has ballooned to $4.5 billion over the life of the program. Of that $4.5 billion, as little as $110M was dedicated to nine scientific instruments assigned to the spacecraft – a ratio of ~41:1. Even if instrument cost ballooned by 100% to ~$220 million, it would still be a measly 20:1. The space environment around Jupiter is admittedly one of the most challenging in the Solar System, warranting some imbalance, but either ratio is still exceptionally bad as far as most exploratory missions go.
Designed to create detailed maps of Europa’s theorized water oceans, ICEMAG, for example, jumped from a $30 million cost estimate to $45 million before NASA abruptly killed it. A Clipper planetary scientist called ICEMAG “a critical instrument that’s been central to Europa science forever”. MASPEX, meanwhile, is a mass spectrometer that will be used to analyze possible chemicals captured by flying through Europa’s transient atmosphere (or, even better yet, plumes from vast ocean geysers). In other words, the instrument most likely to be hobbled next by NASA is also the only instrument on Europa Clipper capable of potentially detecting signs of life by directly sampling material ejected by Europa’s plumes.
Even just with ICEMAG removed, the value proposition of a $4.5 billion mission to an ocean moon of Jupiter becomes much hazier. With ICEMAG removed and MASPEX at risk of being thrown to the wolves, Europa Clipper’s purpose becomes even weaker. Of course, seven valuable instruments remain – some of which partially overlap with MASPEX’ goals – and MASPEX could still technically make it to the finish line in its original handicap-free state, but the tides are definitely not moving in an encouraging direction.
The worst part is that excluding the extraordinarily expensive spacecraft that will host instruments worth ~3-5% its cost, Congress has been dead-set on forcing Europa Clipper to launch on NASA’s chronically-delayed, over-budget Space Launch System (SLS) rocket. SLS has yet to launch once despite more than a decade of development and almost $30 billion spent on the rocket alone, and it would take a miracle for an SLS rocket to be ready to launch Clipper before 2025 or 2026. Europa Clipper is working towards a launch no earlier than 2024, meaning that the spacecraft would have to be stored indefinitely at a cost of at least $125 million per year.
Intrepid readers may note that the cost of simply waiting a single year for SLS to be ready for launch is higher than the cost of all of Europa Clipper’s scientific instruments at their original $110 million budget. The actual cost to NASA for a single SLS launch is expected to $1.5 billion at the absolute minimum, while $2-2.5 billion is far more reasonable. With a little effort and some moderate cruise stage tweaks, Ars Technica has already reported that an expendable SpaceX Falcon Heavy rocket augmented with an off-the-shelf kick stage could send Europa Clipper to Jupiter in 5-6 years, compared to ~3 with SLS.
Ironically, that means that if Falcon Heavy was ready to launch Europa Clipper when the spacecraft is expected to be ready in 2024, it would actually arrive at the same time (or close) if it launched on SLS – once a minimum two-year launch vehicle delay is accounted for. A Falcon Heavy would also save NASA at least $1-2 billion, while it would directly save the Europa Clipper program the ~$250 million it would otherwise need to spend to store the spacecraft while waiting years for an SLS rocket. That $250 million alone – an inevitable add-on cost if SLS is chosen – could easily double the budget of every single Europa Clipper science instrument, adding plenty of breathing room, reinstating ICEMAG, and likely improving the science they output – data-gathering quite literally being the whole purpose of the mission.
Of course, the odds that NASA actually steps out from under the political shadow of SLS and stops playing penny wise and pound foolish with the extraordinarily expensive science missions it shepherds is unlikely. But still, the possibility (and hope) remains. Most recently, a very slight change in the wording of a proposed law (bill) could give the Europa Clipper program the legal wiggle room it needs to sidestep Congress’ desire to force it to launch on SLS. Of course, the senators and representatives with parochial attachment to the rocket will continue to fight tooth and nail to legally force it upon NASA at every possible turn, but there is now at least a chance of a sane outcome.
-
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla claims supplier is holding Cybertruck production hostage
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
