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
Elon Musk reveals date of Tesla Full Self-Driving’s next massive release
Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.
Tesla CEO Elon Musk revealed the date of Full Self-Driving’s next massive release: v14.3.
For months, Tesla owners with Hardware 4 have been utilizing Full Self-Driving v14.2 and subsequent releases. Currently, the most up-to-date FSD version is v14.2.2.5, which has definitely brought out mixed reviews. With releases, some things get better, and other things might regress slightly.
For the most part, things are better in terms of overall behavior.
However, many owners have been looking forward to the next release, which is v14.3, about which Musk has said many great things. Back in November, Musk said that v14.3 “is where the last big piece of the puzzle lands.”
He added:
“We’re gonna add a lot of reasoning and RL (reinforcement learning). To get to serious scale, Tesla will probably need to build a giant chip fab. To have a few hundred gigawatts of AI chips per year, I don’t see that capability coming online fast enough, so we will probably have to build a fab.”
Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.
Tesla Full Self-Driving v14.2 is a considerable improvement from early versions of the suite, but we have written about the somewhat confusing updates that have come with recent versions.
Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever
They’ve been incredibly difficult to gauge in terms of progress because some things have gotten better, but there seems to be some real regression on a handful of things, especially with confidence and assertiveness.
Musk confirmed today on X that Tesla is already testing v14.3 internally right now. It will hit a wide release “in a few weeks,” so we should probably expect it by late April.
It’s in testing right now. Wide release in a few weeks.
— Elon Musk (@elonmusk) March 19, 2026
Overall, there are high hopes that v14.3 could be a true game changer for Tesla Full Self-Driving, as many believe it could be the version that Robotaxis in Austin, Texas, some of which are driverless and unsupervised, are running.
It could also include some major additions, including “Banish,” also referred to as “Reverse Summon,” which would go find a parking spot after dropping occupants off at their destination.
What Tesla will roll out, and when exactly it arrives, all remain to be seen, but fans have been ready for a new version as v14.2.2.5 has definitely run its course. We have had a lot of readers tell us their biggest request is to fix Navigation errors, which seem to be one of the most universal complaints among daily FSD users.
Cybertruck
Chattanooga Charge: Tesla and EV fans ready for the Southeast’s wildest Tesla party
From Cybertruck Convoys to Kid-Friendly Fun Zones: The Chattanooga Charge Has Something for Everyone
Hundreds of like-minded Tesla and EV enthusiasts are descending on Chattanooga Charge this weekend for the largest Tesla meet in the Southeast. Taking place on March 20–22, 2026 at the stunning Tennessee Riverpark.
If you were there last year, you’ll know that it’s the ultimate experience to see the wildest Teslas in action, see the best in EV tech, and arguably the most fun – finally put a name to the face and connect with those social media buddies IRL! Oh, and that epic night time Tesla light show is a once-in-a-lifetime experience that will transform the Riverpark into something out of a sci-fi film that’s remarkably unforgettable and must be seen in person.
This year’s event takes everything up a notch, with over 100 Cybertrucks expected to be on display, many sporting jaw-dropping modifications and custom wraps that push the boundaries of what these stainless steel beasts can look like.
Whether you’re a diehard Tesla fan, EV supporter, or just EV-mod-curious, the sheer spectacle is worth the drive.
The Chattanooga Charge doesn’t wait until Saturday morning to get started. The weekend technically kicks off Friday, March 20th, and the venue sets the tone immediately. Come share roadtrip stories over drinks at the W-XYZ Rooftop Bar on the top floor of the Aloft Chattanooga Hamilton Place Hotel, with sunset views over the city.
Come morning, nurse your hangover with a some good coffee, and convoy with hundreds of other Tesla and EV drivers through Chattanooga to the event for some morning meet and greets before the speaker panel starts and the food trucks fire up.
Tesla owner clubs travel from across the country to be here, not just to show off their vehicles,, but to connect, share, and celebrate a shared passion for the future of driving.
Sounds like a plan to me. See you there, guys. Don’t miss it. Get your tickets at ChattanoogaCharge.com and join the charge. 🔋⚡
Chattanooga Charge is a premier Tesla and EV gathering inspired by the X Takeover, known as one of the largest Tesla event gatherings. What began as a bold idea from the team at DIY Wraps/TESBROS, hosted in their hometown of Chattanooga, Tennessee, the event quickly became a movement across social media. The first annual Chattanooga Charge united over 16 Tesla clubs from 16 states, proof that the EV community was hungry for something big in the South. Year after year, the event has grown in scale, ambition, and heart.
News
Tesla Full Self-Driving gets latest bit of scrutiny from NHTSA
The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.
The National Highway Traffic Safety Administration (NHTSA) has elevated its probe into Tesla’s Full Self-Driving (Supervised) suite to an Engineering Analysis.
The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.
The step up into an Engineering Analysis is often required before the NHTSA will tell an automaker to issue a recall. However, this is not a guarantee that a recall will be issued.
🚨 The NHTSA said it was upgrading a probe into Tesla’s Full Self-Driving (Supervised) platform to an “engineering analysis”
It will examine 3.2 million vehicles and aims to determine its effectiveness in evaluating degraded road conditions pic.twitter.com/2dkrv1mR8o
— TESLARATI (@Teslarati) March 19, 2026
The NTHSA wants to examine Tesla FSD’s ability to assess road conditions that have reduced visibility, as well as detect degradation to alert the driver with sufficient time to respond.
The Office of Defects Investigation (ODI) will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications Tesla makes to the degradation detection system, including the timing, purpose, and capabilities of the updates.
Tesla routinely ships software updates to improve the capabilities of the FSD suite, so it will be interesting to see if various versions of FSD are tested. Interestingly, you can find many examples from real-world users of FSD handling snow-covered roads, heavy rain, and single-lane backroads.
However, there are incidents that the NHTSA has used to determine the need for this probe, at least for now. The agency said:
“Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred.”
It continues to say in its report that a review of Tesla’s responses revealed additional crashes that occurred in similar environments showed FSD “did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path.”
The next steps of the NHTSA Engineering Analysis require the agency to gather further information on Tesla’s attempts to upgrade the degradation detection system. It will also analyze six recent potentially related incidents.
The investigation is listed as EA26002.