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.
In a move echoing its earlier commitment to open innovation, Tesla CEO Elon Musk announced recently that the company plans to make the design and software of its Model S and Model X fully open source.
This follows the same approach Tesla took with its original Roadster, releasing all available design, engineering, and diagnostic materials in November 2023 so that “whatever we have, you now have.”
Just as Tesla made the original Roadster design & software open source, we plan to do the same with Model S & X
— Elon Musk (@elonmusk) July 24, 2026
The Model S, introduced in 2012, was Tesla’s first mass-produced vehicle and a groundbreaking luxury electric sedan. It offered impressive range, rapid acceleration, and over-the-air software updates that redefined expectations for electric cars.
The Model X, launched in 2015, built on that foundation as a high-performance electric SUV notable for its distinctive falcon-wing doors, spacious interior, and advanced safety features. Both models served as flagships that helped establish Tesla as a leader in the EV industry and popularized long-range battery-electric vehicles.
Production of the Model S and Model X was wound down earlier in 2026, with manufacturing ending in the second quarter. Tesla redirected the Fremont factory space previously used for these vehicles toward higher-priority projects, including Optimus humanoid robots and the Cybercab autonomous vehicle.
By the time of Musk’s open-source announcement, custom orders had closed and only remaining inventory was available.
Open-sourcing the designs and software offers several clear advantages. Owners of these aging but still capable vehicles gain better access to technical documentation, diagnostic tools, and software resources, making independent repairs and modifications easier and more affordable.
Independent repair shops and third-party specialists can support the large existing fleet without relying solely on Tesla’s service network. Enthusiasts and engineers can study real-world implementations of Tesla’s battery, powertrain, and software systems, potentially accelerating broader industry progress in electric mobility.
The step aligns with Tesla’s 2014 patent pledge and its overall mission to advance sustainable transport by sharing hard-won knowledge rather than locking it behind proprietary walls.
By releasing these materials now that the models have left production, Tesla ensures continued support for its early adopters while freeing internal resources for future technologies. The open-source release of the original Roadster already enabled simulations, community projects, and deeper technical understanding.
Extending that practice to the Model S and Model X should deliver similar benefits on a larger scale, helping keep these influential vehicles relevant and repairable for years to come
Tesla flexed one incredible Robotaxi metric during the Q2 Earnings Call that skeptics have to hate to hear. The company’s platform has already driven more than 380,000 miles of unsupervised ride-hailing across several states with no notable incidents.
During the company’s Q2 Earnings Call on Wednesday, Vice President of AI, Ashok Elluswamy, said:
“First of all, I’d like to state that the Robotaxi program has been operating extremely well. Especially in terms of safety, the program has had an impeccable safety record. We have driven more than 380,000 miles of unsupervised Robotaxi, now across six cities in two different states. We have had zero notable incidents. Any reports have been of other actors impacting us when we were stationary. I like to emphasize how safe the operation has been so far. Zero notable incidents over 380,000 miles.”
Elluswamy’s claim over Robotaxi miles is a significant milestone for Tesla in the grand scheme, especially considering this is a sizeable number of miles without any incident.
0 notable incidents across over 380,000 miles traveled by Robotaxi
— Tesla (@Tesla) July 22, 2026
Tesla’s self-driving approach is much different than that of other companies. Tesla has maintained that vision is the only thing needed to have a solid and effective self-driving suite. Many self-driving companies utilize things like LiDAR, sensors, and other elements to improve performance, but Elluswamy sent a jab at those who believe it’s needed.
“Historically, the so-called experts have always claimed that you need LiDARs, radars, HD maps, and the entire kitchen sink to drive safely. Here we show that such is not true. You can have safe, comfortable, and affordable autonomy with just cameras. This record should be a huge validation of Tesla’s entire AI approach.”
The feat of accumulating this many miles without any driver behind the wheel is impressive. The thing is, Tesla is also doing this across several different locations, with varying traffic rules, pedestrian levels, weather patterns, and other important factors.
While Tesla is not ready to roll out an unsupervised platform completely, it is a slow but steady indication that the company is well on its way to figuring things out.
The company’s attitude toward expansion is slow, safe, and controlled, and despite this huge milestone, it will still be some time until we see Tesla truly unleash unsupervised rides more aggressively.
Elon Musk
SpaceX Starship just nailed something it’s never done before
SpaceX’s Starship flew successfully Friday, landing both stages and deploying its first Starlink V3 satellites.
Starship’s thirteenth test flight delivered exactly what SpaceX needed with a clean liftoff, two successful stage recoveries, and the first real payload the vehicle has ever carried to space. Booster 20 and Ship 40 lifted off at 5:51 p.m. CT from Starbase, and by the time the mission wrapped roughly an hour later, both halves of the rocket had done exactly what they were supposed to do.
Booster 20 separated from Ship 40 a few minutes into the flight and stuck a controlled splashdown in the Gulf of Mexico about six minutes after liftoff. That is a meaningful turnaround from Flight 12 in May, when the booster lost several engines during its boostback burn before a hard water landing attempt.
Starship as seen from Starlink satellites pic.twitter.com/e2hvfmnewh
— Elon Musk (@elonmusk) July 25, 2026
Starship 40’s performance was arguably the bigger win. The vehicle deployed the first 20 operational Starlink V3 satellites Starship has ever carried, then flew a suborbital arc to a landing in the Indian Ocean that SpaceX commentator Dan Huot called the company’s softest splashdown yet. “This is a dream scenario for this team that’s trying to get this heat shield data,” Huot said on the live broadcast, according to Space.com’s live coverage. “I’m a little over the moon right now. Wow. Lucky number 13.”
Unlike the mass simulators SpaceX flew on Flight 12, these were production Starlink V3 satellites, meant to extend solar arrays and antennas and attempt to link with the broader constellation before reentering minutes later. Getting real hardware through a full deploy sequence on only the second flight of the V3 generation keeps Starship on schedule for the payload work NASA is counting on for future Artemis lunar landings.
What an awesome launch, really seems like everything went super well and it was all incredibly smooth.
SpaceX is awesome. Very interested to see how the market will respond on Monday pic.twitter.com/KSHmyBfV55
— TESLARATI (@Teslarati) July 25, 2026
— TESLARATI (@Teslarati) July 25, 2026
The flight also arrives at a moment when SpaceX needed a win. SPCX has traded below its $135 IPO price since mid-July, as Teslarati reported when the mission slipped to Friday, and short interest has climbed to roughly a third of the tradable float. A clean flight will not fix a balance sheet, but it does answer the one question SpaceX absolutely needed answered this week: whether the fixes made after the July 16 abort would hold up under real flight conditions. They did, on both stages, on the first try after the redesign.
SpaceX has not set a target date for Flight 14, though the company has said it wants to push toward an orbital attempt on the next mission. After Friday, that goal looks a lot more within reach.
Tesla to open source Model S and Model X designs and software
Tesla flexes incredible Robotaxi metric that skeptics will hate
