News
SpaceX, NASA finalize contract for second crewed Starship Moon landing
Around eight months after announcing its intention to do so, NASA has awarded SpaceX a contract for a second crewed Starship Moon landing as early as 2027.
Known as Option B, NASA has exercised a baked-in right to modify its Human Landing System (HLS) Option A contract with SpaceX – signed in April 2021 – to extract even more value from investments into the program. In addition to an uncrewed Starship Moon landing planned no earlier than (NET) 2024 and a crewed demonstration that could land two NASA astronauts on the Moon as early as 2025, NASA’s contract modification gives SpaceX the approval and resources it needs to prepare for a second crewed Starship Moon landing.
On top of securing NASA’s Artemis IV mission astronauts a ride to the lunar surface, the Option B contract will also allow SpaceX and NASA to pursue and demonstrate upgrades that will make Starship an even more capable and cost-effective Moon lander.
Update: NASA says that the Option B modification will cost $1.15 billion, raising the maximum value of SpaceX’s HLS contract to approximately $4.2 billion.
When NASA first announced its intention to add a second crewed Moon landing to SpaceX’s existing HLS contract, the agency couldn’t offer specific information about when that landing might occur or which Artemis mission it would be attached to. Part of the reason for that uncertainty was another announcement two months prior that NASA no longer expected a Moon landing to be paired with its Artemis IV (4) mission. And five days after a March 2022 announcement of plans for a second crewed Starship Moon landing, NASA seemingly reaffirmed that there would be a multi-year gap between Starship’s first crewed Moon landing (NET 2025; tied to Artemis III) and NASA’s second crewed Moon landing, which would use an unspecified lander.
But as of November 2022, NASA has thankfully abandoned plans to intentionally allow a gap between Moon landings. SpaceX’s Starship is now on contract to support back-to-back crewed Moon landings NET 2025 and 2027 as part of NASA’s Artemis III and Artemis IV missions. It’s unclear how or why NASA was able to make that change, but it’s a definite improvement over the alternative.
Additionally, NASA will work with SpaceX to debut new capabilities and improvements on Starship’s second crewed Moon landing. While the Artemis III landing will be about as barebones as possible, the Artemis IV Starship will be upgraded with the ability to transport more NASA astronauts (four instead of just two) and more cargo to the lunar surface. It’s not entirely clear, but NASA reportedly wants to land just ~180 kilograms (~400 lb) of cargo with the first crewed Starship, a vehicle likely capable of landing dozens of tons of cargo in addition to several astronauts. NASA hopes that future “sustainable” lander missions, a category that Starship’s Option B landing may or may not fall under, will transport up to one ton (~2200 lb) of cargo to and from the lunar surface.
Finally, the Artemis IV Starship will also be able to dock with NASA’s Lunar Gateway. Gateway is a small deep space station that will be located in a strange, high lunar orbit. It exists almost exclusively to give NASA’s Space Launch System (SLS) rocket and Orion crew capsule a destination they can both reach. The Orion capsule is almost twice as heavy as its Apollo counterpart and its European Service Module (ESM) offers less than half the performance of NASA’s retired Apollo Service Module. Combined, Orion is physically incapable of transporting itself (or astronauts) to the simpler low lunar orbits used by the Apollo Program.
-
Instead, NASA’s new Moon lander(s) have to pick up Orion’s slack. Starship will be responsible for picking up astronauts in a lunar near-rectilinear halo orbit (NRHO), transporting them to low lunar orbit, and returning them to NRHO in addition to landing on the Moon, spending a week on the surface, and launching back into lunar orbit.
Until it’s modestly upgraded in the late 2020s or 2030s, Gateway will be equally underwhelming. In fact, that’s part of the reason that Starship docking with the Gateway is in any way significant. SpaceX and NASA have decades of expertise docking and berthing spacecraft with space stations. But those spacecraft are typically smaller and lighter than the stations they were joining. Even after the Gateway is fully outfitted with a range of international modules, Starship will likely weigh several times more than the tiny station, making docking even more challenging than it already is.
Starship’s Moon lander variant could also have a cabin with hundreds of cubic meters of habitable space, while the Gateway is unlikely to ever have more than a few dozen. Having a Starship docked would thus immediately make the ultra-cramped station far more livable.
NASA says Artemis IV and the second crew Starship Moon landing will occur as early as 2027. But a ‘space prophet’ who predicted in 2017 that NASA’s SLS launch debut would slip from 2019 to “around 2023” and forecasted that SpaceX alone would win NASA’s Moon lander contract recently told Ars Technica’s Eric Berger that Artemis III, the mission before Artemis IV, is unlikely to launch before 2028. At the time, that source’s predictions verged on blasphemy, but they’ve ultimately proven to be eerily accurate. Only time will tell if their third ‘prophecy’ follows the same path.
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
