Connect with us

News

SpaceX fires up redesigned Crew Dragon as NASA reveals SuperDraco thruster “flaps”

On November 13th, SpaceX successfully static fired Crew Dragon capsule C205's Draco and SuperDraco thrusters. (SpaceX)

Published

on

On November 13th, SpaceX revealed that a planned static fire test of a Crew Dragon’s powerful abort thrusters was completed without issue, a strong sign that the company has successfully redesigned the spacecraft to prevent a catastrophic April 2019 explosion from reoccurring.

Pending a far more extensive analysis, Wednesday’s static fire should leave SpaceX on track to perform Crew Dragon’s next major flight test before the end of 2019.

In an unexpected flourish of transparency, SpaceX and NASA published photos of the Crew Dragon capsule’s static fire test just a few hours after it was completed, an excellent sign that the ‘quick-look’ data analysis immediately following the test was extremely positive. Spaceflight Now was first to visually confirm that the test had occurred, publishing a photo that revealed a whitish cloud of smoke produced by the static fire around 3:15 pm EST (20:15 UTC).

Had a failure similar to the April 2019 explosion occurred, that cloud would have likely been tinged red by unburnt dinitrogen tetroxide (NTO) oxidizer, and the different appearance of November 13th’s exhaust cloud was seen as the first tentative sign that this static fire had gone more successfully.

Alongside photos of the SuperDraco thruster test published by NASA and SpaceX shortly after its conclusion, SpaceX confirmed that the test was completed without issue. Regardless of whether everything performed exactly as intended, this means that factory-fresh Crew Dragon capsule C205 made it through the test unscathed, likely securing SpaceX and NASA a large volume of uninterrupted telemetry data, as well as the hardware itself.

Just hours after C205’s static fire was completed, NASA published a detailed update, confirming that the tests were finished without any immediately apparent issues.

NASA described the test in much more detail than SpaceX, noting that it began with the ignition of two of Crew Dragon’s 16 Draco maneuvering thrusters, each performing two one-second burns. C205’s eight SuperDraco abort thrusters subsequently ignited and burned for a total of ~9 seconds to simulate required abort performance, followed by the reignition of two Draco thrusters immediately after SuperDraco cutoff.

Advertisement
-
-

Each capable of producing several dozen pounds of thrust, both Crew and Cargo Dragon use Draco thrusters to orient themselves in orbit, rendezvous with the International Space Station, and lower their orbits to reenter Earth’s atmosphere. Crew Dragon’s Draco thrusters are also designed to control its attitude during abort scenarios, stabilizing and flipping the spacecraft to prevent a loss of control and ensure proper orientation during emergency parachute deployment. The Draco firings during Crew Dragon’s November 13th static fire were meant to simulate that additional use-case.

Aside from verifying that SpaceX has successfully redesigned Crew Dragon to mitigate the failure mode that caused capsule C201’s catastrophic explosion in April 2019, the Draco static fires specifically mirrored the burns Crew Dragon C205 will need to perform to successfully complete its In-Flight Abort (IFA) test. As noted by NASA and SpaceX, with the static fire complete, both teams will now comb through the data produced, inspect Crew Dragon to verify its health and the performance of its redesigned high-flow pressurization system, and perform any necessary refurbishment.

A pod of SuperDraco thrusters is pictured here shortly after installation on Crew Dragon C206, the spacecraft set to launch astronauts for the first time ever. (SpaceX)

SuperDraco’s mystery “flaps”

NASA’s post on Crew Dragon’s static fire revealed another thoroughly intriguing detail: the SpaceX spacecraft’s SuperDraco thrusters apparently have flaps! A bit of retroactive speculation suggests that SuperDracos are closed out with plugs of some sort to create a seal against the environment before Crew Dragon is rolled out to the launch pad. Perhaps, in the event of a SuperDraco ignition, SpaceX included actuating flaps as a method of resealing those thrusters prior to splashdown in the Atlantic Ocean.

“Immediately after the SuperDracos shut down, two Dracos thrusters fired and all eight SuperDraco flaps closed, mimicking the sequence required to reorient the spacecraft in-flight to a parachute deploy attitude and close the flaps prior to reentry. The full sequence, from SuperDraco startup to flap closure, spanned approximately 70 seconds.”

NASA, November 13th, 2019

In retrospect, flaps (actuating covers) are an obvious explanation for the cutouts visible directly underneath each SuperDraco pod. (SpaceX)

Given that the obvious utility of those flaps appears to be extremely limited and their associated actuators have to survive the 9+ consecutive seconds of hellish conditions in the event of an actual abort, it seems like an excessively complicated system to include on Crew Dragon. Nevertheless, the ability to guarantee that SuperDracos are water-sealed before splashdown would almost without a doubt make Crew Dragon far easier to refurbish and reuse.

The SuperDraco flaps may also be a holdover from before propulsive Crew Dragon landings were canceled, although the use-cases for such a system still remain unclear. The flaps’ raison d’etre could even be as simple as preventing water intrusion that might otherwise cause Dragon to sink after splashdown.

The fact that Crew Dragon C201’s flaps appeared to be unchanged after launch and recovery suggests that they are more of a backup in the event that the abort thrusters have to be used. (NASA)

Regardless of why they exist, NASA indicates that SpaceX’s November 13th static fire proved that they worked exactly as expected, closing soon after the simulated abort burn to seal Crew Dragon against water intrusion. If NASA and SpaceX’s deep-dive inspections and data analysis uncover no red flags, it’s extremely likely that SpaceX will able to launch C205 for its In-Flight Abort test some 4-8 weeks from now.

If the IFA also goes as planned, Crew Dragon could be ready for its inaugural NASA astronaut launch as early as February or March 2020.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Advertisement
-
-

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

Musk’s massive Terafab project will get final location soon

Published

on

Credit: SpaceX

Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.

“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.

Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry

Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.

The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.

In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.

However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.

Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.

Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.

“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”

He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”

Continue Reading

News

Elon Musk reveals SpaceX performed secret Starship test on Flight 13

Published

on

Credit: SpaceX

SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.

Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.

All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.

However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.

Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:

SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.

Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.

The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.

Continue Reading

Elon Musk

Tesla FSD takes owner on a 20,000+ mile joy ride

Tesla owner David Moss just pushed his intervention free FSD streak past 20,000 miles total.

Published

on

By

Tesla FSD 14.3 [Credit: TESLARATI)

Tesla Model 3 owner David Moss has spent the better part of eight months turning his vehicle into a rolling stress test for Full Self-Driving, and this week he pushed his single, continuous FSD streak past 20,000 miles without a human intervening.

Moss, a Tacoma, Washington resident who sells LiDAR scanning equipment for a living, first drew wide attention in December 2025 when he logged 10,000 consecutive miles on FSD v14.2. Days later he drove from the Tesla Diner in Los Angeles to Myrtle Beach, South Carolina, covering 2,732 miles in two days and 20 hours with zero disengagements, the first verified coast to coast autonomous drive in Tesla’s history. Tesla even featured the trip as an official customer story in March. That original streak eventually reached 12,961 miles across 30 states before ending in rural Wisconsin in January, when snow and single digit temperatures forced Moss to take over.

Tesla FSD successfully completes full coast-to-coast drive with zero interventions

He started over, and this run has gone further. In late May, Moss drove 3,760 miles across Canada with two companions, from Horseshoe Bay in Vancouver to a Tesla showroom in Halifax, again without a single intervention, a trip Tesla AI software VP Ashok Elluswamy publicly congratulated him for on X. In June, he pushed the same unbroken streak south, aiming to link the Canadian border to the Mexican border, and crossed 10,000 miles on Tesla’s newly added in car streak counter along the way, the first driver to do so since Tesla began showing confetti animations for the feature.


It’s worth noting that every mile is logged through the FSD Database, a community run tracker built by Tesla influencer Omar Qazi, well known as @WholeMars on X, that pulls telemetry straight from the car and records disengagements down to a tenth of a mile. That verification is what separates Moss’s numbers from casual claims on social media.

The streak itself is a fairly recent addition to Tesla’s software. FSD v14.2 introduced a Self Driving Stats panel tracking the ratio of autonomous to manual miles, and v14.3.4 added the live streak counter in June, which resets the moment a driver brakes, wrenches the wheel or cancels navigation. Reaching 20,000 miles on that counter means a single Tesla drove itself through countless highways, city grids, construction zones and Supercharger stalls without a single reset.

Moss has said the goal was never to set a record for its own sake, but to show, mile by verified mile, what the software can already do.

Continue Reading