News
SpaceX set to launch NASA astronauts first after Boeing narrowly avoids catastrophe in space
SpaceX is set to become the first private company to launch NASA astronauts as few as three months from now, all but guaranteed after Boeing’s competing Starliner spacecraft narrowly avoided a catastrophe in space on its orbital launch debut.
The ultimate purpose of NASA’s Commercial Crew Program (CCP) is to ensure that the US is once again able to launch its own astronauts into orbit and to the International Space Station (ISS) – a capability the country has not possessed since it prematurely canceled the Space Shuttle in 2011. In a logical step, NASA decided to fund two independent companies to ensure that astronaut launch capabilities would be insulated against any single failure, ultimately awarding contracts to Boeing and SpaceX in 2014. Boeing did actually try to have Congress snub SpaceX back in 2014 and solely award the contract to Starliner, but the company thankfully failed.
As a result, SpaceX beating Boeing on the (not-a-) race to launch NASA astronauts to the International Space Station (ISS) would represent an immense and deeply embarrassing upset in the traditional aerospace industry – essentially a case of David and Goliath. For the better part of a decade, Congress, most industry officials, and Boeing itself have argued ad nauseum the Starliner spacecraft was clearly a far safer bet than anything built by SpaceX – Boeing, obviously, has far more experience (“heritage”) in the spaceflight industry. However, multiple “catastrophic” failures during Boeing’s recent Starliner ‘Orbital Flight Test’ (OFT) paint a far uglier picture.
As its PR team and executives will constantly remind anyone within earshot, Boeing helped build the first stage of the Saturn V rocket, while a company it bought years after the fact (Rockwell) did technically buy the company (North American) that built the spacecraft (Apollo CSM) that carried NASA astronauts from the Earth to the Moon (and back). Rockwell (acquired by Boeing) also built all five of NASA’s Space Shuttle orbiters.
In the 1990s, Boeing – set to lose a competition to build an expendable rocket for the US military – acquired McDonnell Douglas at the last second, slapping a Boeing sticker on the Delta IV rocket – designed and built by MD. Boeing then conspired to steal trade secrets from Lockheed Martin (bidding Atlas V) and used that stolen info to mislead the USAF about the real cost of Delta IV, thus securing the more lucrative of two possible contracts. This is all to point out the simple fact that Boeing has far less real experience designing spacecraft than it tends to act like it does.
As such, it’s substantially less surprising than it might otherwise be that Boeing’s Starliner spacecraft has had such a rocky orbital launch debut. Preceded just a matter of weeks by a quality assurance failure that prevented one of Starliner’s four parachutes from deploying after an otherwise-successful pad abort test, a second Starliner spacecraft launched atop an Atlas V rocket on its orbital launch debut (OFT) on December 20th, 2019. Atlas V performed flawlessly but immediately after Starliner separated from the rocket, things went very wrong.
Bad software ultimately caused the spacecraft to perform thousands of uncommanded maneuvering thruster burns, depleting a majority of its propellant before Boeing was able to intervene. Starliner managed to place itself in low Earth orbit (LEO), but by then it had nowhere near enough propellant left to rendezvous and dock with the ISS – one of the most crucial purposes of the uncrewed flight test. Unable to complete that part of the mission, Boeing instead did a few small tests over the course of 48 hours in orbit before commanding the spacecraft’s reentry and landing on December 22nd.
But wait, there’s more!
As it turns out, although both NASA and Boeing inexplicably withheld the information from the public for more than two months, Boeing’s OFT Starliner spacecraft reportedly almost suffered a second major software failure just hours before reentry. According to NASA and Boeing comments in a press conference held only after news of that second failure broke after an advisory panel broached the issue in February 2020, a second Starliner software bug – caught only because the first failure forced Boeing to double-check its code – could have had far more catastrophic consequences.
NASA officials stated that had the second bug not been caught, some of Starliner’s thruster valves would have been frozen, either entirely preventing or severely hampering the spacecraft’s detached trunk from properly maneuvering in orbit. Apparently, that service module (carrying fuel, abort engines, a solar array, and more) could have crashed into the crew module shortly after detaching from it. Unsurprisingly, that ‘recontact’ could have severely damaged the Starliner crew capsule, potentially making reentry impossible (or even fatal) if its relatively fragile heat shield bore the brunt of that impact.
SpaceX has undeniably suffered its own significant failures, most notably when flight-proven Crew Dragon capsule C201 exploded moments before a static fire test, but the company has already proven that it fixed the source of the failure with the spacecraft’s second successful launch on a Falcon 9 rocket. Ultimately, it’s becoming nearly impossible to rationally argue that Boeing’s Starliner will be safer than SpaceX’s Crew Dragon – let alone worth the 40% premium Boeing is charging NASA and the US taxpayer.
According to Ars Technica’s Eric Berger, Crew Dragon’s inaugural astronaut launch is now tentatively scheduled as early as late-April to late-May 2020. Paperwork – not technical hurdles – is currently the source of that uncertainty, and all Demo-2 mission hardware (Falcon 9 and Crew Dragon) is either already in Florida or days away from arriving.
Due to the combination of similar software failures Starliner suffered during its first and only launch, Boeing now has to review the entirety of the spacecraft’s software – more than a million lines of code – before NASA will allow the company to launch again. There’s also a very good chance that Boeing will now have to repeat the Orbital Flight Test, potentially incurring major delays. In short, it would take nothing less than a miracle – or NASA making a public mockery of itself for Boeing’s benefit – for Starliner to launch astronauts before SpaceX.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
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 crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
