News
SpaceX sues US government to protest mystery launch or rocket R&D contracts
SpaceX has filed a lawsuit – technically a “Bid Protest Complaint” – against the United States government and successfully petitioned for the file to remain sealed, restricting access to additional case details for the time being.
This development follows a quiet series of bid protests SpaceX filed with the Government Accountability Office (GAO) in February 2019, shortly after NASA announced that it had awarded ULA a ~$150M launch contract for Lucy (a robotic Trojan asteroid explorer). SpaceX believed that it could perform the mission at a “dramatically lower” price, potentially saving the federal government tens of millions of dollars. SpaceX withdrew both of its GAO bid protests without comment on April 4th. Whether those prior protests are related to SpaceX’s May 2019 lawsuit is unclear.
Adding even more complexity and uncertainty to the series of events, NASA awarded SpaceX the launch contract for its Double Asteroid Redirection Test (DART) spacecraft on April 20th, about two weeks after SpaceX retracted its Lucy protests. The cause-and-effect relationship between both events is wholly ambiguous. Perhaps SpaceX withdrew before the company was made aware of their DART win. Perhaps they withdrew their protest because they learned of NASA’s award.
Regardless of what did or did not trigger the contract award, the fact remains that SpaceX’s DART launch will cost NASA ~$70M, less than half the price of ULA’s ~$150M Lucy launch contract. As such, it seems likely that launching Lucy on Falcon 9 could have saved the US government as much as $50M, assuming an expendable profile (~$100M per SpaceX’s latest GPS III launch contracts).

Returning to the topic at hand, the simplest explanation is that SpaceX’s GAO bid protests and May 2019 lawsuit are in some way related. Although SpaceX was clearly correct when it insinuated that it could launch Lucy far more affordably than ULA, the company was criticized for its GAO protests because they effectively froze – or at least complicated – work on the NASA spacecraft. In the event that the withdrawals and lawsuit are related, SpaceX would have backed down after entering into the slow GAO protest process, essentially conceding the contract to ULA and allowing spacecraft work to continue without disruption.
Replaced with a lawsuit against the US government, SpaceX could instead be attempting to change the processes that lead NASA to award ULA the Lucy launch contract in spite of potential savings on the order of ~$50M. SpaceX has done something similar once before when it sued the US Air Force for its uncompetitive launch procurement processes, a largely successful endeavor that has helped force some competition back into USAF/DoD launch contracts.


However, there are several additional possibilities for the actual subject of SpaceX’s latest sealed suit. Most recently, NASA distributed ~$46M among 11 companies for studies and prototypes of lunar landers, transfer vehicles, and in-space refueling technology. SpaceX tied with Aerojet Rocketdyne for the least substantial awards out of those 11 companies, each receiving funds for a single study, while most other awardees were contracted for multiple studies and/or prototypes. This is a stretch, however.
The most likely alternative to a continuation of SpaceX’s Lucy protest is a lawsuit focused on the USAF’s latest EELV/NSSL development contracts and its proposed continuation of block-buy launch procurement. Of the four companies involved, Blue Origin and SpaceX have both criticized the USAF for a variety of reasons. Both did agree, however, in their dislike of the USAF’s inexplicable desire to award all launch contracts to two victors, despite there being as many as four different launch vehicles that could feasibly compete for those several-dozen contracts.

For now, details of SpaceX’s latest lawsuit will remain sealed, leaving the company’s motivations veiled in mystery. SpaceX’s next USAF mission could occur as early as June 22nd. Known as STP-2, it will mark Falcon Heavy’s third flight, the rocket’s first defense-related launch, and the USAF’s first use of flight-proven SpaceX boosters. If successful, SpaceX will effectively be able to compete with ULA for all conceivable future launch contracts.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
News
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
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.
Elon Musk
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
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.
News
Tesla Cybercab has one important piece that AI4 cars might need for FSD
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.