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.
A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.
The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.
TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.
Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.
Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.
TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.
This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.
This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.
However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.
Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.
Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.
The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.
A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”
Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.
This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.
The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.
Musk teased that a similar feature was “coming” back in February:
Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says
It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.
Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.
Here’s an example of that from December:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.
We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
