News
SpaceX’s NASA Starship contract safe for now as Blue Origin looks to Congress
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.
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.
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.
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
