News
Boeing Starliner abort test (mostly) a success as SpaceX nears Crew Dragon static fire
On November 4th, Boeing completed a crucial pad abort test of its reusable Starliner spacecraft, successful in spite of an unintentional partial failure of its parachute recovery system. Three days later, Boeing revealed what it believed to be the cause of that anomaly in a November 7th press conference.
Meanwhile, SpaceX – having completed Crew Dragon’s pad abort test in 2015 – is preparing for an equally important In-Flight Abort (IFA) test and is perhaps just a day or two away from static firing the Crew Dragon capsule assigned to the test flight.
According to a NASA press release after the test, it “was designed to verify [that] each of Starliner’s systems will function not only separately, but in concert, to protect astronauts by carrying them safely away from the launch pad in the unlikely event of an emergency prior to liftoff.” Although the test wasn’t without flaws, the pad abort test successfully demonstrated the ability of the four launch abort engines and control thrusters to safely extricate astronauts from a failing rocket.
Those theoretical astronauts would have almost certainly survived the ordeal unharmed despite the failed deployment of one of Starliner’s three main parachutes, testing the spacecraft’s abort capabilities and redundancy quite a bit more thoroughly than Boeing intended. To put it bluntly, Boeing’s above tweet and PR claim that the failed deployment of 1/3 parachutes is “acceptable for the test parameters and crew safety” is an aggressive spin on a partial failure that NASA undoubtedly did not sign off on.
Boeing and SpaceX have both suffered failures while testing parachutes, leading NASA to require significantly more testing. However, in a November 7th press conference, Boeing revealed that Starliner’s parachute anomaly wasn’t the result of hardware failing unexpectedly under planned circumstances, but rather a consequence of a lack of quality assurance that failed to catch a major human error. Boeing says that a critical mechanical linkage (a pin) was improperly installed by a technician and then not verified prior to launch, causing one of Starliner’s three drogue chutes to simply detach from the spacecraft instead of deploying its respective main parachute.
Space is Parachutes are hard
Parachutes have been a major area of concern for the Commercial Crew Program. Both SpaceX and Boeing have now suffered failures during testing and have since been required to perform a range of additional tests to verify that upgraded and improved parachutes are ready to reliably return NASA astronauts to Earth. Although the Starliner pad abort test did indeed demonstrate the ability to land the capsule safely under two main chutes, an inadvertent test of redundancy, the series of Boeing actions that lead to the failure will almost certainly be scrutinized by NASA to avoid reoccurrences.
Boeing believes that the parachute failure won’t delay the launch of Starliner’s Orbital Flight Test (OFT), currently targeting a launch no earlier than (NET) December 17th. However, it can be said with some certainty that it will delay Starliner’s crewed launch debut (CFT), at least until Boeing can prove to NASA that it has corrected the fault(s) that allowed it to happen. SpaceX is similarly working to qualify upgraded Crew Dragon parachutes for astronaut launches, although the company has thus far only suffered anomalies related to the structural failure of parachute rigging/seams/fabric.
Abort tests galore
Boeing’s Starliner pad abort test occurred just days prior to a different major abort test milestone – this time for SpaceX. SpaceX Crew Dragon capsule C205 will perform a static fire test of its upgraded SuperDraco abort system, as well as its Draco maneuvering thrusters.
SpaceX has made alterations to the SuperDraco engines to prevent a failure mode that abruptly reared its head in April 2019, when a leaky valve and faulty design resulted in a catastrophic explosion milliseconds before a SuperDraco static fire test. Prior to its near-total destruction, Crew Dragon capsule C201 was assigned to SpaceX’s In-Flight Abort test, and its loss (and the subsequent failure investigation) delayed the test’s launch by at least six months. Crew Dragon’s design has since been fixed by replacing reusable check valves with single-use burst discs, nominally preventing propellant or oxidizer leaks.
If capsule C205’s static fire testing – scheduled no earlier than November 9th – goes as planned, SpaceX may be able to launch Crew Dragon’s in-flight abort (IFA) test before the end of 2019e. Likely to be a bit of a spectacle, Crew Dragon will launch atop a flight-proven Falcon 9 booster and a second stage with a mass simulator in place of its Merlin Vacuum engine, both of which will almost certainly be destroyed when Dragon departs the rocket during peak aerodynamic pressure.
NASA made in-flight abort tests an optional step for its Commercial Crew providers and Boeing decided to perform a pad abort only and rely on modeling and simulations to verify that Starliner’s in-flight abort safety. Assuming that NASA is happy with the results of Starliner’s pad abort and Boeing can alleviate concerns about the parachute anomaly suffered during the test, Starliner’s uncrewed orbital flight test (OFT) could launch as early as December 17th. Starliner’s crewed flight test (CFT) could occur some 3-6 months after that if all goes as planned during the OFT.
If SpaceX’s In-Flight Abort (IFA) also goes as planned and NASA is content with the results, Crew Dragon could be ready for its crewed launch debut (Demo-2) as early as February or March 2020.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
Elon Musk
Tesla’s Elon Musk: 10 billion miles needed for safe Unsupervised FSD
As per the CEO, roughly 10 billion miles of training data are required due to reality’s “super long tail of complexity.”
Tesla CEO Elon Musk has provided an updated estimate for the training data needed to achieve truly safe unsupervised Full Self-Driving (FSD).
As per the CEO, roughly 10 billion miles of training data are required due to reality’s “super long tail of complexity.”
10 billion miles of training data
Musk comment came as a reply to Apple and Rivian alum Paul Beisel, who posted an analysis on X about the gap between tech demonstrations and real-world products. In his post, Beisel highlighted Tesla’s data-driven lead in autonomy, and he also argued that it would not be easy for rivals to become a legitimate competitor to FSD quickly.
“The notion that someone can ‘catch up’ to this problem primarily through simulation and limited on-road exposure strikes me as deeply naive. This is not a demo problem. It is a scale, data, and iteration problem— and Tesla is already far, far down that road while others are just getting started,” Beisel wrote.
Musk responded to Beisel’s post, stating that “Roughly 10 billion miles of training data is needed to achieve safe unsupervised self-driving. Reality has a super long tail of complexity.” This is quite interesting considering that in his Master Plan Part Deux, Elon Musk estimated that worldwide regulatory approval for autonomous driving would require around 6 billion miles.
FSD’s total training miles
As 2025 came to a close, Tesla community members observed that FSD was already nearing 7 billion miles driven, with over 2.5 billion miles being from inner city roads. The 7-billion-mile mark was passed just a few days later. This suggests that Tesla is likely the company today with the most training data for its autonomous driving program.
The difficulties of achieving autonomy were referenced by Elon Musk recently, when he commented on Nvidia’s Alpamayo program. As per Musk, “they will find that it’s easy to get to 99% and then super hard to solve the long tail of the distribution.” These sentiments were echoed by Tesla VP for AI software Ashok Elluswamy, who also noted on X that “the long tail is sooo long, that most people can’t grasp it.”
News
Tesla earns top honors at MotorTrend’s SDV Innovator Awards
MotorTrend’s SDV Awards were presented during CES 2026 in Las Vegas.
Tesla emerged as one of the most recognized automakers at MotorTrend’s 2026 Software-Defined Vehicle (SDV) Innovator Awards.
As could be seen in a press release from the publication, two key Tesla employees were honored for their work on AI, autonomy, and vehicle software. MotorTrend’s SDV Awards were presented during CES 2026 in Las Vegas.
Tesla leaders and engineers recognized
The fourth annual SDV Innovator Awards celebrate pioneers and experts who are pushing the automotive industry deeper into software-driven development. Among the most notable honorees for this year was Ashok Elluswamy, Tesla’s Vice President of AI Software, who received a Pioneer Award for his role in advancing artificial intelligence and autonomy across the company’s vehicle lineup.
Tesla also secured recognition in the Expert category, with Lawson Fulton, a staff Autopilot machine learning engineer, honored for his contributions to Tesla’s driver-assistance and autonomous systems.
Tesla’s software-first strategy
While automakers like General Motors, Ford, and Rivian also received recognition, Tesla’s multiple awards stood out given the company’s outsized role in popularizing software-defined vehicles over the past decade. From frequent OTA updates to its data-driven approach to autonomy, Tesla has consistently treated vehicles as evolving software platforms rather than static products.
This has made Tesla’s vehicles very unique in their respective sectors, as they are arguably the only cars that objectively get better over time. This is especially true for vehicles that are loaded with the company’s Full Self-Driving system, which are getting progressively more intelligent and autonomous over time. The majority of Tesla’s updates to its vehicles are free as well, which is very much appreciated by customers worldwide.
Elon Musk
Judge clears path for Elon Musk’s OpenAI lawsuit to go before a jury
The decision maintains Musk’s claims that OpenAI’s shift toward a for-profit structure violated early assurances made to him as a co-founder.
A U.S. judge has ruled that Elon Musk’s lawsuit accusing OpenAI of abandoning its founding nonprofit mission can proceed to a jury trial.
The decision maintains Musk’s claims that OpenAI’s shift toward a for-profit structure violated early assurances made to him as a co-founder. These claims are directly opposed by OpenAI.
Judge says disputed facts warrant a trial
At a hearing in Oakland, U.S. District Judge Yvonne Gonzalez Rogers stated that there was “plenty of evidence” suggesting that OpenAI leaders had promised that the organization’s original nonprofit structure would be maintained. She ruled that those disputed facts should be evaluated by a jury at a trial in March rather than decided by the court at this stage, as noted in a Reuters report.
Musk helped co-found OpenAI in 2015 but left the organization in 2018. In his lawsuit, he argued that he contributed roughly $38 million, or about 60% of OpenAI’s early funding, based on assurances that the company would remain a nonprofit dedicated to the public benefit. He is seeking unspecified monetary damages tied to what he describes as “ill-gotten gains.”
OpenAI, however, has repeatedly rejected Musk’s allegations. The company has stated that Musk’s claims were baseless and part of a pattern of harassment.
Rivalries and Microsoft ties
The case unfolds against the backdrop of intensifying competition in generative artificial intelligence. Musk now runs xAI, whose Grok chatbot competes directly with OpenAI’s flagship ChatGPT. OpenAI has argued that Musk is a frustrated commercial rival who is simply attempting to slow down a market leader.
The lawsuit also names Microsoft as a defendant, citing its multibillion-dollar partnerships with OpenAI. Microsoft has urged the court to dismiss the claims against it, arguing there is no evidence it aided or abetted any alleged misconduct. Lawyers for OpenAI have also pushed for the case to be thrown out, claiming that Musk failed to show sufficient factual basis for claims such as fraud and breach of contract.
Judge Gonzalez Rogers, however, declined to end the case at this stage, noting that a jury would also need to consider whether Musk filed the lawsuit within the applicable statute of limitations. Still, the dispute between Elon Musk and OpenAI is now headed for a high-profile jury trial in the coming months.
Tesla’s Elon Musk: 10 billion miles needed for safe Unsupervised FSD
Tesla earns top honors at MotorTrend’s SDV Innovator Awards
