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 AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
