News
NASA snubbed SpaceX, common sense to overpay Boeing for astronaut launches, says audit
A detailed government audit has revealed that NASA went out of its way to overpay Boeing for its Commercial Crew Program (CCP) astronaut launch services, making a mockery of its fixed-price contract with the company and blatantly snubbing SpaceX throughout the process.
Over the last several years, the NASA inspector general has published a number of increasingly discouraging reports about Boeing’s behavior and track-record as a NASA contractor, and November 14th’s report is possibly the most concerning yet. On November 14th, NASA’s Office of the Inspector General (OIG) published a damning audit titled “NASA’s Management of Crew Transportation to the International Space Station [ISS]” (PDF).
Offering more than 50 pages of detailed analysis of behavior that was at best inept and at worst deeply corrupt, OIG’s analysis uncovered some uncomfortable revelations about NASA’s relationship with Boeing in a different realm than usual: NASA’s Commercial Crew Program (CCP). Begun in the 2010s in an effort to develop multiple redundant commercial alternatives to the Space Shuttle, prematurely canceled before a US alternative was even on the horizon, the CCP ultimately awarded SpaceX and Boeing major development contracts in September 2014.


NASA awarded fixed-cost contracts worth $4.2 billion and $2.6 billion to Boeing and SpaceX, respectively, to essentially accomplish the same goals: design, build, test, and fly new spacecraft capable of transporting NASA astronauts to and from the International Space Station (ISS). The intention behind fixed-price contracts was to hold contractors responsible for any delays they might incur over the development of human-rated spacecraft, a task NASA acknowledged as challenging but far from unprecedented.
Off the rails
The most likely trigger of the bizarre events that would unfold a few years down the road began in part on June 28th, 2015 and culminated on September 1st, 2016, the dates of the two catastrophic failures SpaceX’s Falcon 9 rocket has suffered since its 2010 debut. In the most generous possible interpretation of the OIG’s findings, NASA headquarters and CCP managers may have been shaken and not thinking on an even keel after SpaceX’s second major failure in a little over a year.
Under this stress, the agency may have ignored common sense and basic contracting due-diligence, leading “numerous officials” to sign off on a plan that would subvert Boeing’s fixed-price contract, paying the company an additional $287 million (~7%) to prevent a perceived gap in NASA astronaut access to the ISS. This likely arose because NASA briefly believed that SpaceX’s failures could cause multiple years of delays, making Boeing the only available crew transport provider for a significant period of time. Starliner was already delayed by more than a year, making it increasingly unlikely that Boeing alone would be able to ensure continuous NASA access to the ISS.
As NASA attempted to argue in its response to the audit, “the final price [increase] was agreed to by NASA and Boeing and was reviewed and approved by numerous NASA officials at the Kennedy Space Center and Headquarters”. In the heat of the moment, perhaps those officials forgot that Boeing had already purchased several Russian Soyuz seats to sell to NASA or tourists, and perhaps those officials missed the simple fact that those seats and some elementary schedule tweaks could have almost entirely alleviated the perceived “access gap” with minimal cost and effort.
The OIG audit further implied that the timing of a Boeing proposal – submitted just days after NASA agreed to pay the company extra to prevent that access gap – was suspect.
“Five days after NASA committed to pay $287.2 million in price increases for four commercial crew missions, Boeing submitted an official proposal to sell NASA up to five Soyuz seats for $373.5 million for missions during the same time period. In total, Boeing received $660.7 million above the fixed prices set in the CCtCap pricing tables to pay for an accelerated production timetable for four crew missions and five Soyuz seats.”
NASA OIG — November 14th, 2019 [PDF]
In other words, NASA officials somehow failed to realize or remember that Boeing owned multiple Soyuz seats during “prolonged negotiations” (p. 24) with Boeing and subsequently awarded Boeing an additional $287M to expedite Starliner production and preparations, thus averting an access gap. The very next week, Boeing asked NASA if it wanted to buy five Soyuz seats it had already acquired to send NASA astronauts to the ISS.
Bluntly speaking, this series of events has three obvious explanations, none of them particularly reassuring.
- Boeing intentionally withheld an obvious (partial) solution to a perceived gap in astronaut access to the ISS, exploiting NASA’s panic to extract a ~7% premium from its otherwise fixed-price Starliner development contract.
- Through gross negligence and a lack of basic contracting due-diligence, NASA ignored obvious (and cheaper) possible solutions at hand, taking Boeing’s word for granted and opening up the piggy bank.
- A farcical ‘crew access analysis’ study ignored multiple obvious and preferable solutions to give “numerous NASA officials” an excuse to violate fixed-price contracting principles and pay Boeing a substantial premium.
Extortion with a friendly smile
The latter explanation, while possibly the worst and most corruption-laden, is arguably the likeliest choice based on the history of NASA’s relationship with Boeing. In fact, a July 2019 report from the US Government Accountability Office (GAO) revealed that NASA was consistently paying Boeing hundreds of millions of dollars worth of “award fees” as part of the company’s SLS booster (core stage) production contract, which is no less than four years behind schedule and $1.8 billion over budget. From 2014 to 2018, NASA awarded Boeing a total of $271M in award fees, a practice meant to award a given contractor’s excellent performance.
In several of those years, NASA reviews reportedly described Boeing’s performance as “good”, “very good”, and “excellent”, all while Boeing repeatedly fumbled SLS core stage production, adding years of delays to the SLS rocket’s launch debut. This is to say that “numerous NASA officials” were also presumably more than happy to give Boeing hundreds of millions of dollars in awards even as the company was and is clearly a big reason why the SLS program continues to fail to deliver.
Ultimately, although NASA’s concern about SpaceX’s back-to-back Falcon 9 failures and some combination of ineptitude, ignorance, and corruption all clearly played a role, the fact remains that NASA – according to the inspector general – never approached SpaceX as part of their 2016/2017 efforts to prevent a ‘crew access gap’. Given that the CCP has two partners, that decision was highly improper regardless of the circumstances and is made even more inexplicable by the fact that NASA was apparently well aware that SpaceX’s Crew Dragon had significantly shorter lead times and far lower costs compared to Starliner.
This would have meant that had NASA approached SpaceX to attempt to mitigate the access gap, SpaceX could have almost certainly done it significantly cheaper and faster, or at minimum injected a bit of good-faith competition into the endeavor.
Finally and perhaps most disturbingly of all, NASA OIG investigators were told by “several NASA officials” that – in spite of several preferable alternatives – they ultimately chose to sign off Boeing’s demanded price increases because they were worried that Boeing would quit the Commercial Crew Program entirely without it. Boeing and NASA unsurprisingly denied this in their official responses to the OIG audit, but a US government inspector generally would never publish such a claim without substantial confidence and plenty of evidence to support it.
According to OIG sources, “senior CCP officials believed that due to financial considerations, Boeing could not continue as a commercial crew provider unless the contractor received the higher prices.” A lot remains unsaid, like why those officials believed that Boeing’s full withdrawal from CCP was a serious possibility and how they came to that conclusion, enough to make it impossible to conclude that Boeing legitimately threatened to quit in lieu of NASA payments.

All things considered, these fairly damning revelations should by no means take away from the excellent work Boeing engineers and technicians are trying to do to design, build, and launch Starliner. However, they do serve to draw a fine line between the mindsets and motivations of Boeing and SpaceX. One puts profit, shareholders, and itself above all else, while the other is trying hard to lower the cost of spaceflight and enable a sustainable human presence on the Moon, Mars, and beyond.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
News
Tesla Robotaxi will be a 24/7 service: here’s when
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.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
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.
News
Tesla Cybercab launch catches NHTSA’s attention who wants to know more
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.