News
Blue Origin lawsuit forces SpaceX, NASA to stop joint work on Starship Moon lander
Days after Jeff Bezos space startup Blue Origin sued NASA over its decision to solely award SpaceX a contract to turn Starship into a Moon lander, it’s become clear that the space agency will again have to freeze work on the program.
Earlier this week, it was reported that Blue Origin had made good on a veiled threat to sue NASA over disagreements over the space agency’s latest Human Landing System (HLS) procurement decisions. Namely, NASA decided not to proceed with Blue Origin’s National Team Moon lander proposal, which was twice as expensive as SpaceX’s Starship proposal, less technically sound, and promised significantly less cost-sharing.
SpaceX, on the other hand, proposed to turn Starship into a safe, crew-rated, reusable Moon lander for about the same cost as Blue Origin’s proposal price: $6 billion, give or take. However, NASA says that the company offered to pay for more than half of the Starship Moon lander’s development, lowering NASA’s actual cost to just $2.9 billion. Coincidentally or not, $2.9 billion – with some minor concessions on when that funding would be dispersed to the HLS winner – would end up being almost exactly what NASA could afford over the program’s four to five-year lifespan.
As previously discussed on Teslarati, NASA repeatedly and explicitly warned all three HLS Option A competitors (SpaceX, Blue Origin, and Dynetics) that it withheld the ability to award as many or as few contracts as it wanted – including none at all. Ultimately, exactly as it had cautioned, NASA weighed the three proposals it received against its existing budget (a middling $850M of $3.4B requested in FY21) and selected just one – a proposal from SpaceX that was conveniently both the cheapest and most technically sound.
“The fixed-price [Starship] contract will cost NASA $2.9B over four or so years – narrowly within the space agency’s reach if Congress continues to appropriate around $850M annually ($3.4B over four years). The numbers are very simple. As GAO notes [in its protest denial], the Broad Agency Announcement (BAA) tool NASA used for its HLS Option A acquisition also explicitly allowed the agency to select as many or as few proposals as it wants, including none at all. In the lead-up to proposal submission, official NASA documents repeatedly cautioned as much, warning that the agency might not even award one contract depending on funding or the quality of proposals it received.
For Blue Origin’s lawsuit to succeed, the increasingly desperate company will have to convince a federal judge that basic realities and longstanding precedents of federal procurement – not just NASA’s HLS award to SpaceX – are flawed and need to be changed. The odds of success are thus spectacularly low. However, if the presiding judge allows the case to proceed and awards Blue Origin an injunction against NASA, it could force the space agency to cease work on SpaceX’s HLS contract for months and potentially freeze SpaceX’s access to the $300M NASA recently disbursed.”
Teslarati.com — August 16th, 2021
Unfortunately, just as speculated, Blue Origin’s lawsuit appears to have found just enough footing to disrupt the HLS program yet again. Thanks to the first protests of Blue Origin and Dynetics, NASA and SpaceX were forced to stop cooperative work on the Starship Moon lander for more than three months. Now, on August 19th, NASA reportedly “voluntarily paused” work on SpaceX’s HLS Moon lander contract and will continue to do so until November 1st – potentially adding another ~74 days to the 95-day delay Blue Origin’s meddling has already partially caused.
Schedule submitted jointly by all the parties today, and the judge’s order granting the schedule. pic.twitter.com/gyHS4R4j50— Joey Roulette (@joroulette) August 19, 2021
On its own, the announcement is already fairly bizarre. For unknown reasons, Blue Origin apparently agreed to “an expedited litigation schedule” in return for NASA voluntarily pausing work on SpaceX’s HLS contract. It’s unclear why any plaintiff that believes it has a strong case would allow an artificial limit to be placed on the amount of time available for litigation, but that’s exactly what Blue Origin has agreed to.
-
Per that “expedited schedule,” NASA’s voluntary work halt will end on November 1st after several scheduled rounds of motions and cross-motions from Blue Origin, SpaceX, and the space agency. It’s unclear when a ruling might be expected but the schedule published seems to imply that it would come sometime before NASA and SpaceX resume work.
It’s now increasingly likely that being forced to spend more than five months without the ability to seriously work or collaborate with SpaceX on its HLS contract will significantly delay NASA’s necessary contributions and thus humanity’s return to the Moon. Thankfully, as was the case with the initial 95-day delay caused by contract protests, no part of Blue Origin’s lawsuit will prevent SpaceX itself from continuing to develop Starship, though it almost certainly hampers the company’s ability to mature its Starship Moon lander design.
In the meantime, while Blue Origin busies itself with a general determination to disrupt NASA’s return to the Moon until it receives a slice of the pie its executives and owner feel entitled to, SpaceX will simply continue a full-court press towards Starship’s orbital launch debut and focus on building, testing, flying, and rebuilding the hardware that will return humanity to the Moon and, just maybe, revolutionize spaceflight as we know it.
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 Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
