Connect with us

News

SpaceX, NASA finalize contract for second crewed Starship Moon landing

Published

4 years ago

on

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.

SpaceX’s three main Human Landing System Starship variants.

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.

Advertisement
-
-

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.

Related Topics:

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

News

Tesla briefly offered this Robotaxi part for your personal car

Published

1 hour ago

on

July 28, 2026

By

Credit: @tpgoebel | X

Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.

Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.

First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.

This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.

However, this part has since been removed and is no longer visible on the EPC.

Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?

While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.

AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.

This could be the first hint of that’s where we are headed.

Continue Reading

News

Tesla Robotaxi gets sweeping but polarizing change

Published

3 hours ago

on

July 28, 2026

By

Credit: Tesla

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:

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.

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.

Continue Reading

News

Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

24 hours ago

on

July 27, 2026

By

Credit: Tesla

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.

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.

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.

Continue Reading