Connect with us

News

SpaceX’s NASA Starship contract safe for now as Blue Origin looks to Congress

SpaceX's NASA HLS contract is safe (for now) but major uncertainty still remains. (SpaceX/NASASpaceflight - bocachicagal)

Published

on

Fresh off of a major contract loss during a competition to build NASA’s next crewed Moon lander, Blue Origin has begun aggressively lobbying Congress for the contract NASA didn’t give it.

Thankfully, albeit not at first, a modification has been made to an amendment first proposed by a Senator that has long pursued favorable treatment of Blue Origin that will prevent that legislation – if it passes – from unfairly interrupting the $2.9 billion contract NASA already awarded SpaceX. Announced on April 16th, that award came as a shock, effectively cementing SpaceX’s lunar Starship as both the cheapest and most technically sound proposal to return humanity to the Moon.

As such, although NASA made it clear that it would have selected two of the three competing proposals in a perfect scenario, Congress allocated just a quarter of the Human Landing System (HLS) funding NASA requested, forcing the agency between a rock and a hard place.

NASA repeatedly stated as much both before and after the decision was announced, effectively implying that the agency had learned its lesson with the Commercial Crew Program, in which it had selected two redundant providers – Boeing and SpaceX – only for Congress to systematically underfund the program for years. As a direct result of years of underfunding during an early and formative period, both providers suffered at least 2-3 years of delays, followed by another few years of more organic delays as development matured and new challenges were unsurprisingly uncovered.

Advertisement

Politically, NASA could never say that – effectively biting the hand that (under)feeds – out loud, but it was strongly implied in an official HLS source selection statement released to partially explain why it had chosen SpaceX and SpaceX alone. Almost instantly, both losing competitors – Blue Origin and Dynetics – filed protests with the US Government Accountability Office (GAO) filled with far more bizarre, rambling tangents than coherent legal arguments.

Unless GAO operates on a different standard than the court of law or uncovers something nefarious behind closed doors, a close reading of both partially redacted protests does not bode well for either document’s ability to sway the office’s opinion. Almost as if Blue Origin itself is aware of just how frivolous its protest really is, the company – seemingly backed by partners Northrop Grumman, Lockheed Martin, and Leidos – wasted no time lobbying Senator Maria Cantwell for an alternate avenue to get what it wants and the government money founder Jeff Bezos feels entitled to.

Cantwell represents Washington State, where both Amazon and Blue Origin are headquartered, and has frequently spoken out in support of – or personally introduced – legislation that would specifically favor Bezos’ space company. On May 12th, Cantwell introduced an amendment that would purportedly “maintain competitiveness” by forcing NASA to select a second HLS winner in addition to SpaceX. Without irony, the authorization bill also demanded that NASA make that decision within a mere 30 days.

Under those conditions, Congress would authorize $10 billion for NASA to develop and demonstrate two landers with an uncrewed and crewed Moon landing each – the original plan. Insultingly, Cantwell tacked that amendment onto an authorization bill, meaning that even if Congress were to pass the bill and the President were to sign it into law, Congress would still have to actually allocate that $10 billion in the form of a more than 10% boost to NASA’s annual budget. Historically, even if Congress were to defy all recent precedent and significantly boost NASA’s 2022 budget, there is no guarantee that that raise would be upheld for four or more years, which it would need to be for the authorization bill to be anything more than a hollow promise.

More recently, a clause was thankfully added clarifying that NASA is not allowed to “modify, terminate, or rescind” SpaceX’s HLS contract to comply with the amendment. Additionally, while still amounting to a legal gun to NASA’s head to force it to into a contract it knows it cant afford, the modification gives NASA 60 days to award a second lander contract. Based on the agency’s own selection statement, Blue Origin’s National Team would almost certainly be the recipient in the event that the bill becomes law, forcing NASA to commit more than $9 billion – instead of $2.9 billion – to the next stage of HLS development with no guarantee that its budget will be raised accordingly.

Advertisement

In the meantime, GAO still has to complete its reviews of Blue Origin and Dynetic’s protests and the White House has to submit its FY2022 budget request and consider adding NASA funding to its proposed jobs and infrastructure package.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla Cybercab stands to gain from new Trump autonomy rules

Published

on

Credit: Teslarati

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.

Continue Reading

News

Tesla plans production boost at Giga Berlin following rebound in Europe

Published

on

Credit: Andre Thierig | X

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’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.

Continue Reading

News

Tesla and driver sued by family of woman killed in Texas crash: what we know

Published

on

Credit: CNBC

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.

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.

Continue Reading