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 Cybercab stands to gain from new rules that the Trump Administration is aiming to enforce on autonomous vehicles. On Thursday, NHTSA, under the Trump Administration’s U.S. Department of Transportation, commenced rulemaking on the Federal Motor Vehicle Safety Standards (FMVSS).
This effort aims to eliminate the mandate for manual brake pedals in vehicles that are designed to be driven exclusively by automated driving systems. This would impact the Tesla Cybercab, which the company has stated would operate without a steering wheel or pedals.
Tesla Cybercab launch is imminent after latest sighting at Giga Texas
The Trump Administration is looking to revise FMVSS No. 135, which requires standard braking systems on light-duty vehicles.
Currently, the regulation requires light-duty cars to use traditional manual braking systems that allow operators to slow the vehicle. With the advent of self-driving in the U.S., these regulations need updating, and these are the changes that could come to FMVSS No. 135:
- Removes requirements for hand- or foot-operated brake controls for vehicles designed never to be operated by a human. Existing rules still apply to AVs that retain manual controls.
- All subject vehicles must still meet the same stopping distance performance criteria via alternative testing procedures.
- While this update ensures AVs can physically stop when commanded, NHTSA is separately developing safety performance requirements for AVs in real-world driving scenarios.
- NHTSA will continue to use its broad defect enforcement authority to investigate unsafe ADS behavior and oversee recalls.
As autonomy becomes a greater part of passenger travel, these types of rule adjustments will be more than reasonable. It will give manufacturers the ability to self-certify their vehicles and avoid any red tape that could ultimately delay the deployment of these vehicles.
Administrators are also incredibly excited about the opportunity to play a role in the advancement of self-driving vehicles.
“We are at the cusp of the greatest technological revolution in vehicle technology since the innovation of the Model T,” NHTSA Administrator Jonathan Morrison said. “If we want America to lead the way, we have to reimagine our regulatory framework. That’s why under Secretary Sean Duffy’s AV Framework, NHTSA is tearing down pointless barriers to innovative designs while strengthening the fundamental safety requirements that matter and holding AV developers accountable for safe performance.”
The Cybercab entered mass production at Gigafactory Texas in April. Tesla ultimately plans to push the vehicle into its Robotaxi fleet, potentially when frameworks like these are established.
Tesla plans to boost production at its Gigafactory Berlin plant in Germany following a sharp rebound in sales and demand in Europe after a softer 2025.
The plans put Tesla in a better position to compete with strengthening companies in Europe and potentially other markets; demand indicators show Tesla is much better off than in 2025.
Last year was a tough year for Tesla in terms of overall demand in Europe. The company produced over 200,000 vehicles at the German plant last year, a soft figure compared to the 375,000 vehicles Tesla lists as its current capacity at the factory.
🚨 Tesla said this morning it will ramp up production at Gigafactory Berlin to a volume of 7,500 vehicles per week.
This is a 20 percent boost in production. Tesla will hire 1,000 new employees to help with the increase.$TSLA pic.twitter.com/kravKfRO5n
— TESLARATI (@Teslarati) June 25, 2026
Tesla’s overall European sales dropped significantly last year due to a variety of factors. However, sales are rebounding, and demand is strong once again, and only getting stronger. Tesla is now planning to bump production of Model Y vehicles at Giga Berlin upward by about 20 percent. It will also bring 1,000 new jobs to the plant.
Tesla confirmed the details of its planned production expansion in Germany this morning. It is a strategy to keep up with strengthening demand.
In Q1, Tesla saw a record 61,000 vehicles produced at Giga Berlin. European registrations rebounded sharply, with Model Y seeing 117 percent increases in March 2026 compared to last year. Germany alone saw stark increases, with a quadrupling in registrations to 9,252 units.
This trend continued in other key European markets, including France, Denmark and Sweden. Tesla registrations were up over 46 percent in some of these markets, and Model Y continued its trend as a top BEV in the market.
Demand has been recovering strongly in 2026, giving Tesla a reason to expand production efforts at the factory. These increases signal management’s confidence in sustained or growing European pull for Berlin-built vehicles.
Tesla is being sued by the family of the woman who was killed in a Texas crash involving a Model 3. The driver, who is also being sued, claimed the vehicle was operating on Autopilot mode, but Tesla executives have come out challenging that claim, stating that the driver of the vehicle overrode the system.
The lawsuit was filed by 76-year-old Martha Avila’s daughter and her husband, who allege a “design defect” involving a Tesla and a failure to warn. The suit alleges negligence against Tesla and the driver, Michael Butler.
Butler “stated he was operating with an automated driving assistance system engaged at the time of the crash,” the Harris County Sheriff’s Office said in a statement. He showed no signs of intoxication and was cooperative, the Sheriff’s Office said, according to NBC News.
Just after reports of the crash and numerous headlines that immediately blamed Tesla’s Autopilot suite, both Tesla CEO Elon Musk and Head of AI Ashok Elluswamy challenged that. Musk said the crash made “no sense” given that Tesla Autopilot and Full Self-Driving do not travel at the speeds the door cameras captured the car traveling at, which Tesla says was 73 MPH.
Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration
Elluswamy also revealed that Tesla data showed Butler overrode the system by pressing the accelerator to 100%, and that the pedal was compressed fully even after the car had crashed. Tesla has not released this data to the public, likely because it is communicating with agencies like the NHTSA on an investigation.
The suit uses a Washington Post analysis of government data that “identified at least 17 fatal incidents linked to Tesla Autopilot.”
This is far from the first time an accident has been blamed on Autopilot. A fatal crash in Texas was blamed on Autopilot several years ago, but when Tesla released data to the NTSB, which was investigating the crash, Autopilot was not available where the crash occurred, and Autosteer was never enabled, meaning the car was manually controlled at the time of the accident.
“Application of the accelerator pedal was found to be as high as 98.8 percent,” the NTSB said in their findings. The highest recorded speed in the five seconds leading up to the impact was 67 miles per hour. The area where the crash occurred is residential, and Texas State laws… pic.twitter.com/XGD97NHVZ2
— TESLARATI (@Teslarati) March 18, 2026
More information on the accident will be released as Tesla works with agencies to find the cause of the crash. From personal experience, it is hard to imagine Tesla Autopilot or FSD operating in this manner. It drives sometimes too cautiously in residential areas in parking lots, at least in my experience. Speeding happens, but at this rate in this type of area, it is hard to believe.
We look forward to more details being released with time.
Tesla Cybercab stands to gain from new Trump autonomy rules
Tesla plans production boost at Giga Berlin following rebound in Europe
