News
SpaceX CEO Elon Musk explains why Blue Origin’s Starship lawsuit makes no sense
For the first time since SpaceX competitor Blue Origin took NASA to federal court after losing a Moon lander contract to Starship and a protest over that loss, unsealed documents have finally revealed the argument Jeff Bezos’ space startup is focusing on in court.
After the details broke in new court documents filed on Wednesday, SpaceX CEO Elon Musk weighed in on Twitter to offer his take on why the arguments Blue Origin has hinged its lawsuit on make very little sense.
While one seemingly significant portion of the main complaint claiming to reveal “additional substantial errors” in SpaceX’s Starship HLS proposal was almost fully redacted, most of the opening argument is legible. In short, Blue Origin appears to have abandoned the vast majority of arguments it threw about prior to suing NASA and the US government and is now almost exclusively hinging its case on the claim that SpaceX violated NASA’s procurement process by failing to account for a specific kind of prelaunch review before every HLS-related Starship launch.
For NASA’s HLS competition, SpaceX proposed to create a custom variant of Starship capable of serving as a single-stage-to-orbit crewed Moon lander with the help of the rest of the Starship fleet – including Super Heavy boosters, cargo/tanker Starships, and a depot or storage ship. SpaceX would begin a Moon landing campaign by launching a (likely heavily modified) depot Starship into a stable Earth orbit. Anywhere from 8 to 14 Starship tanker missions – each carrying around 100-150 tons of propellant – would then gradually fill that depot ship over the course of no more than six or so months. Once filled, an HLS lander would launch to orbit, refill its tanks from the depot ship, and make its way to an eccentric lunar orbit to rendezvous with NASA’s Orion spacecraft and three Artemis astronauts.
As Blue Origin has exhaustively reminded anyone within earshot for the last five months, SpaceX’s Starship Moon lander proposal is extremely complex and NASA is taking an undeniable risk (of delays, not for astronauts) by choosing SpaceX. Nevertheless, NASA’s Kathy Lueders and a source evaluation panel made it abundantly clear in public selection statement that SpaceX’s proposal was by far the most competent, offering far a far superior management approach and technical risk no worse than Blue Origin’s far smaller, drastically less capable lander.
The bulk of Blue Origin’s argument appears to be that its National Team Lander proposal was drastically disadvantaged by the fact that SpaceX may or may not have incorrectly planned for just three ‘flight readiness reviews’ (FRRs) for each 16-launch HLS Starship mission. While heavily redacted, Blue Origin wants a judge to believe that contrary to the US Government Accountability Office’s (GAO) fair assessment that such a small issue is incredibly unlikely to have changed the competition’s outcome, it would have “been able to propose a substantially lower price” for its lander. To be clear, a flight readiness review is an admittedly important part of NASA’s safety culture, but it ultimately amounts to paperwork and doublechecks over the course of a day or two of meetings.
All else equal, the need to complete an FRR before a launch is incredibly unlikely to cause more than a few days of delays in a worst-case scenario and would have next to no cost impact. There is no reasonable way to argue that being allowed to complete some launches without an FRR would have singlehandedly allowed Blue Origin to “[engineer] and [propose] an entirely different architecture.” Nevertheless, that’s exactly what the company attempts to argue – that it would have radically and completely changed the design it spent more than half a billion dollars sketching out if it had only been able to skip a few reviews.
Curiously, Blue Origin nevertheless does make a few coherent and seemingly fact-based arguments in the document. Perhaps most notably, it claims that when NASA ultimately concluded that it didn’t have funds for even a single award (a known fact) and asked SpaceX – its first choice – to make slight contract modifications to make the financial side of things work, NASA consciously chose to waive the need for an FRR before every HLS Starship launch. Only via purported cost savings from those waived reviews, Blue Origin claims, was NASA able to afford SpaceX’s proposal – which, it’s worth noting, was more than twice as cheap as the next cheapest option (Blue Origin).
Ultimately, it thus appears that Blue Origin may have a case to make that NASA awarded SpaceX the HLS Option A contract despite a handful of errors that violated contracting rules and the HLS solicitation. Relative to just about any other possible issue, though, it’s hard not to perceive the problems Blue Origin may or may have correctly pointed out as anything more than marginal and extraordinarily unlikely to have changed the outcome in Blue’s favor had they been rectified before the award. Most importantly, even if Blue Origin’s argument is somehow received favorably and a judge orders NASA to overturn its SpaceX HLS award and reconsider all three proposals, it’s virtually inconceivable that even that best-case outcome would result in Blue Origin receiving a contract of any kind.
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’
