Connect with us

News

SpaceX’s Crew Dragon abort test gets closer to launch with SuperDraco static fires

A pair of Crew Dragon's upgraded SuperDraco abort engines perform a static fire test. (SpaceX)

Published

on

SpaceX has posted a video showing the static fire test of a pod of Crew Dragon SuperDraco abort thrusters, indicating that the complex system has been successfully redesigned (“upgraded”) to fix the faults that caused a Dragon capsule to explode in April 2019.

This progress keeps SpaceX on track for two critical Crew Dragon milestones, both of which are now expected to occur sooner than later.

Published just a few hours prior, CNBC journalist Michael Sheetz reported that SpaceX is planning to static fire the Super Draco abort thrusters of Crew Dragon capsule C205 as early as November 2nd.

Capsule C205 – along with an expendable trunk – were reassigned to support Crew Dragon’s crucial In-Flight Abort (IFA) test after flight-proven capsule C201 was destroyed just prior to a SuperDraco static fire test on April 20th. Having just successfully completed Crew Dragon’s first uncrewed orbital launch, space station docking, and ocean recovery (Demo-1), the plan was to reuse C201 to perform the IFA test.

Crew Dragon C205 would support Demo-2 – the spacecraft’s first NASA astronaut launch – and C206 would support Post-Certification Mission 1 (PCM-1), meaning Dragon’s first operational delivery of astronauts to the ISS.

Crew Dragon capsule C205 and Falcon 9 booster B1046 arrived in Florida around October 3rd ahead of SpaceX’s critical In-Flight Abort (IFA) test. (SpaceX)
Excluding Falcon 9, all pieces of SpaceX’s first astronaut-rated Crew Dragon spacecraft are visible in this one frame: capsule C206, a heat shield, and what looks like a nearly finished trunk. (Teslarati – Pauline Acalin)

Instead, Crew Dragon C201 suffered a catastrophic explosion just prior to a SuperDraco static fire test at SpaceX’s Cape Canaveral Air Force Station (CCAFS) Landing Zone (LZ) facilities. Capsule C205 was diverted to support the In-Flight Abort, while C206 was moved up to support Demo-2. Had C201’s static fire been successful, SpaceX could have been ready to launch Crew Dragon’s IFA mission as early as May or June.

As Michael Sheetz reported, SpaceX now plans to perform a similar static fire test of the IFA Crew Dragon capsule as early as November 2nd. It’s unclear if this static fire would have been performed had C201 not exploded, but CNBC suggests that NASA and a number of other parties will be watching the results of this test closely.

SpaceX’s first spaceworthy Crew Dragon capsule prepares for its first Falcon 9-integrated static fire and a post-recovery test fire three months later. (SpaceX)

Whether that’s true or not, it’s unclear just how relevant a SuperDraco static fire of a factory-fresh Crew Dragon spacecraft (C205) is to C201’s failure. The latter spacecraft had completed months of testing (much of it fueled), spent a week in orbit, reentered Earth’s atmosphere, and splashed down in saltwater barely a month and a half prior to the fated test.

Regardless, it looks like SpaceX and NASA understandably want to perform a (relatively) similar static fire test to verify that – at a minimum – the Dragon capsule’s abort thrusters are in working order. As SpaceX’s static fire video illustrates, SuperDraco thrusters – as well as each integrated pair of engines – are all static fired in McGregor, Texas as part of routine acceptance testing. If all goes as planned during the November 2nd static fire, as well as the Falcon 9 rocket’s own static fire, Crew Dragon’s In-Flight Abort mission could launch as early as late-November.

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

News

Tesla’s switch-up on selling Full Self-Driving has paid off big time

Published

on

In early 2026, Tesla made a bold strategic pivot: it largely eliminated the option to purchase Full Self-Driving (FSD) software outright and shifted to a subscription-only model. The change, effective around mid-February, ended the one-time fee that had previously ranged as high as $15,000 and later dropped to $8,000. Instead, customers would access FSD (Supervised) for $99 per month in the U.S.

At the time, skeptics questioned whether locking customers into recurring payments would hurt adoption or alienate buyers who preferred ownership of the feature. Tesla bet that a lower barrier to entry, seamless integration at purchase, and the ability to cancel at any time would drive higher uptake.

The results from Q2 2026 speak for themselves: the decision has been a resounding success, delivering the largest quarterly growth in FSD subscriptions in the company’s history.

According to Tesla’s Q2 shareholder update, active FSD subscriptions reached 1.48 million globally by the end of June 2026. That represents a 56 percent increase year-over-year and a 15.6 percent jump from the prior quarter. Tesla added roughly 200,000 new subscriptions in the period alone—the biggest single-quarter gain on record.

North America led the charge, with more than 55 percent of new vehicle deliveries including an FSD subscription at the time of purchase, a record attach rate for the region.

Tesla explicitly noted that “more customers [are] opting for subscription at the time of vehicle purchase,” crediting the model shift and prominent placement of the option in the ordering process. Subscriptions now contribute meaningfully to ancillary revenue, helping offset pressure elsewhere in the business.

The financial upside is substantial: At $99 per month, 1.48 million active subscriptions generate approximately $146.5 million in monthly recurring revenue. Over a full year, that equates to roughly $1.76 billion in annualized recurring revenue (ARR) from FSD subscriptions alone, assuming steady retention and no major pricing changes.

These figures represent pure, high-margin software revenue. Unlike vehicle sales, which carry production costs, warranty obligations, and supply-chain risks, FSD subscriptions flow largely to the bottom line once the software is developed and deployed over-the-air.

Tesla does not break out exact FSD subscription revenue in its filings (it sits within “Services and Other”), but the category grew 50 percent year-over-year in Q2, with executives highlighting subscriptions as a key driver.

The subscription model offers several structural advantages. It lowers the upfront cost of a new Tesla, potentially broadening the buyer pool and supporting vehicle demand, especially important amid fluctuating EV market conditions. It creates a predictable revenue stream that compounds as the fleet grows and more owners try (and stick with) the software.

Legacy one-time purchasers still exist, but new growth is overwhelmingly subscription-based following the February cutoff.

Early data also suggests improving retention and satisfaction, as well. Tesla has rolled out iterative FSD updates, including v14 features, and expanded availability to additional markets. Recent regulatory approvals in parts of Europe have further boosted interest, with owners in newly enabled countries eager to activate the software they had been waiting for.

FSD is still supervised; regulatory hurdles for true unsupervised autonomy persist in many regions, including the United States, and competition in advanced driver-assistance systems is intensifying. Yet the Q2 numbers validate Tesla’s bet: by removing the large upfront commitment and making FSD accessible via subscription, the company has accelerated adoption faster than many anticipated.

What began as a controversial switch-up has become a clear win. With nearly 1.5 million subscribers, record attach rates, and nearly $1.8 billion in potential annual recurring revenue already in view, Tesla’s FSD business is transitioning from a promised future to a tangible, fast-growing profit engine.

If the momentum continues, and especially if unsupervised capabilities unlock robotaxi opportunities, the subscription flywheel could become one of the most valuable assets in Tesla’s portfolio.

Continue Reading

News

Tesla Robotaxi’s slow rollout gets explanation from Elon Musk

Published

on

Credit: Tesla

Tesla Robotaxi is among its biggest projects currently, but many have been quick to point out the fact that the company has definitely been slow to expand its fleet.

However, there is definitely a method to that madness. CEO Elon Musk answered several concerns during last night’s quarterly earnings call that some might have about that slow rollout of the Robotaxi suite, maintaining the company’s narrative on prioritizing safety and wanting to avoid injuries to anyone, including animals.

Musk said:

“With Robotaxi, our goals are very ambitious for Robotaxi, but we do need to be cautious about causing any accidents or causing any harm to anyone. Although there are, I think, 30,000 to 40,000 automotive deaths per year in the U.S. alone, most of those do not generate any press or maybe, you never really read about almost any of those. If we injure even one person, it’ll be worldwide headline news, and regulators will immediately clamp down on our activities.

We don’t want to injure anyone. We’re going as fast as humanly possible in scaling Robotaxi, but while trying to ensure that we do not harm anyone at all, and ideally do not even run over a pet. That’s really the constraint is we want to grow as fast as possible with Robotaxi without harm to anyone.”

Tesla has maintained an exemplary safety record with its Robotaxi suite, according to internal data. VP of AI, Ashok Elluswamy, said that the Robotaxi suite has driven more than 380,000 miles unsupervised without any incidents.

Analyst Colin Langan of Bank of America also pushed Tesla executives for answers regarding the company’s decision to add cities across several states with dozens of vehicles “as opposed to hundreds.”

Elluswamy said there’s a bigger advantage to do it the way Tesla has been because it ensures that its software stack “is a very general one:”

“The reason we have been expanding across different cities instead of just doubling down on a single city, is that we want to make sure that our stack is a very general one. It is a general one. We just want to both prove to ourselves and to other folks that it is working across a lot of different cities without too much effort per city. That’s what we see internally.”

In the past, we have written about Tesla’s decision to be incredibly conservative with its Robotaxi rollout, especially with the incredibly small fleet size compared to competitors. However, there really is not a price anyone can put on safety for those utilizing the platform or pedestrians, so what Tesla is doing is justified.

A year into the Robotaxi program being active, Tesla has made major strides, but many investors and fans would like to see the fleet expand as quickly as the program has to other cities and states.

Continue Reading

Elon Musk

Tesla Semi finally has an FSD timeline and it’s waiting on the Cybercab

Elon Musk told investors Semi self-driving should start working by early 2027, per today’s earnings.

Published

on

By

During Wednesday’s’ Tesla Q2 earnings call, an analyst asked Elon Musk when Tesla would look at autonomy for the Semi. His answer set a real timeline for the first time, noting that self-driving on the Tesla Semi is expected to start working “around the end of this year or early next year”.

Musk framed the delay as a matter of priority, not capability. Tesla’s self-driving team is currently focused on Model 3, Model Y, and Cybercab, the vehicles that make up the overwhelming majority of Tesla’s fleet. Since Semi trucks on the road remain a small fraction of that total even after the recent Nevada factory ramp, Musk said it made more sense to keep the software team’s attention on what he called “the march of nines of safety” for the higher volume vehicles first. Autonomous Semi development is “taking a bit of a backseat for the next six months or so,” he said, before adding that it “will definitely be working next year and in time for the scale-up to high production of the Tesla Semi.”

Tesla Semi’s official battery capacity leaked by California regulators

The timeline lines up with what’s already been showing up on public roads. In June, a Tesla Semi was spotted in Sunnyvale wearing a full validation rig, the same rooftop sensor array Tesla mounts on vehicles ahead of an FSD milestone.

A second unit was seen near Fremont days later with a matching camera suite and lens washers. Separately, Tesla analyst Nic Cruz Patane posted video this month of the production Semi’s exterior camera array, ten AI4 based units built directly into the truck rather than added later.


Musk also gave the reason autonomy on the Semi matters in the first place, a persistent shortage of qualified truck drivers. “There is a really serious shortage of truckers,” he said on the call, framing a self-driving Semi as important both for addressing that shortage and for improving safety and comfort for the drivers running the truck today.

The timing also tracks with the Semi’s production reality. Tesla’s Q2 shareholder letter, dropped language promising the Semi would reach volume production this year. Musk pointed to 4680 battery cell output as the near-term constraint on Semi and Cybercab production. A software timeline landing in early 2027 gives Tesla’s autonomy team room to work while the hardware ramp catches up behind it.

It’s worth nothing that this isn’t necessarily a promise the Semi ships driverless next year. Musk’s own language, self-driving “working” by early 2027, describes internal validation catching up to hardware already riding on every production truck, not a public unsupervised rollout.

Continue Reading