Connect with us
Boeing's Starliner and SpaceX's Crew Dragon spacecraft stand vertical at their respective launch pads in December 2019 and January 2020. Crew Dragon has now performed two successful full-up launches to Starliner's lone partial failure. (Richard Angle) Boeing's Starliner and SpaceX's Crew Dragon spacecraft stand vertical at their respective launch pads in December 2019 and January 2020. Crew Dragon has now performed two successful full-up launches to Starliner's lone partial failure. (Richard Angle)

News

Report: SpaceX to launch at least five back-to-back Crew Dragon missions for NASA

Crew Dragon looks set to continue picking up the slack left behind Boeing's Starliner spacecraft. (Richard Angle)

Published

4 years ago

on

Update: Wasting no time at all, NASA has confirmed the Ars Technica report one day later, announcing that rookie astronauts Nicole Mann and Josh Cassada have been reassigned from Boeing Starliner missions to SpaceX’s Crew-5 Crew Dragon launch – currently no earlier than August 2022.

Ars Technica’s Eric Berger reports that NASA has begun the process of moving a number of astronauts assigned to Boeing’s ailing Starliner spacecraft to a SpaceX Crew Dragon mission scheduled no earlier than August 2022.

Per sources close to Berger, NASA has chosen to reassign two rookie astronauts to Crew Dragon as hopes of a crewed Starliner launch – and thus an opportunity for them to gain hands-on spaceflight experience – in the next 6-12 months continue to wither. Barring surprises, the implied change of plans behind those actions means that SpaceX now appears to be scheduled to fly five operational NASA Crew Dragon missions back to back before Boeing’s Starliner flies a single astronaut – let alone its first operational mission with four crew aboard.

In December 2019, nine months after Crew Dragon’s own uncrewed March 2019 debut, Starliner lifted off for the first time on a ULA Atlas V rocket. However, whereas Crew Dragon performed a practically flawless orbital launch, space station rendezvous, docking, departure, reentry, and splashdown on its first try, Starliner’s Orbital Flight Test (OFT) went horribly wrong as soon as it separated from Atlas V.

Due to shoddy prelaunch testing that failed to detect several gaping holes in Starliner’s software, the spacecraft effectively lost control as soon as it was under its own power. Aside from making ground communication and control far harder, Starliner burned through most of its propellant and pushed most of its maneuvering thrusters past their design limits in the first hour or two after launch. Due to the catastrophic software failure and lack of propellant margins, NASA unsurprisingly called off a planned space station rendezvous and docking attempt and Boeing ultimately ordered Starliner to reenter a few days after launch.

Advertisement

Mere hours before reentry, Boeing apparently detected and fixed another major software error at the last second, potentially preventing Starliner’s propulsion and service module from smashing into the capsule’s fragile heat shield and dooming the spacecraft to burn up during reentry. Ultimately, it’s likely that the only reason Boeing didn’t suffer a total loss of vehicle (LOV) during Starliner’s OFT debut spacecraft was dumb luck. Had the initial clock error been worse, Starliner could have failed to reach orbit entirely or burned through all of its propellant, resulting in an uncontrolled reentry. Had there been no clock issue, it’s hard to imagine that Boeing’s software team would have attempted the panicked, impromptu bug hunt that detected and fixed the service module recontact issue.

Now, 22 months after Starliner’s catastrophic OFT, Boeing has been forced to stand down from a second self-funded orbital flight test (OFT-2) due to the last-second discovery of more than a dozen malfunctioning valves on the second spacecraft’s service module. Aside from raising the question of how Boeing and NASA yet again failed to detect a glaring Starliner issue until the day of launch, Starliner’s valve issues appear likely to cause another multi-month delay as Boeing is forced to investigate the problem, find the root cause, and implement a fix on all impacted service modules.

NASA reassigning some of the astronauts scheduled to helm Starliner on its Crewed Flight Test (CFT) and first operational mission to Crew Dragon’s August 2022 Crew-5 launch seemingly implies that the space agency is not confident that Boeing will have completed Starliner OFT-2, passed extensive post-flight reviews, and readied another Starliner for CFT by Q3 2022. Given that NASA took some 14 months to OK Crew Dragon’s Demo-2 crewed flight test after Demo-1’s March 2019 success and a catastrophic April 2019 failure during a ground test of the recovered capsule, it’s not unreasonable to assume that NASA will take about a year after OFT-2 to approve Starliner’s first crewed flight test.

If significant issues arise during OFT-2, which is now unlikely to occur before early 2022, a year-long gap is even more likely. Ultimately, that means that there is now a significant chance that SpaceX’s Crew Dragon spacecraft will complete not just five – but six – back-to-back operational NASA astronaut launches before Starliner is ready for its first operational ferry mission. SpaceX, in other words, is now expected to singlehandedly hold the line and ensure biannual NASA access to and from the International Space Station (ISS) for more than two years despite charging NASA $2 billion less than Boeing (~$5B vs ~$3B) to develop Crew Dragon.

Advertisement
Related Topics:

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

‘I don’t understand TSLAQ:’ notable investor backs Tesla, Elon Musk

Published

10 hours ago

on

October 8, 2025

By

tesla showroom
(Credit: Tesla)

One notable investor that many people will recognize said today on X that he does not understand Tesla shorts, otherwise known as $TSLAQ, and he’s giving some interesting reasons.

Martin Shkreli was long known as “Pharmabro.” For years, he was known as the guy who bought the rights to a drug called Daraprim, hiked the prices, and spent a few years in Federal prison for securities fraud and conspiracy.

Shkreli is now an investor who co-founded several hedge funds, including Elea Capital, MSMB Capital Management, and MSMB Healthcare. He is also known for his frank, blunt, and straightforward responses on X.

His LinkedIn currently shows he is the Co-Founder of DL Software Inc.

One of his most recent posts on X criticized those who choose to short Tesla stock, stating he does not understand their perspective. He gave a list of reasons, which I’ll link here, as they’re not necessarily PG. I’ll list a few:

  • Fundamentals always have and will always matter
  • TSLAQ was beaten by Tesla because it’s “a great company with great management,” and they made a mistake “by betting against Elon.”
  • When Shkreli shorts stocks, he is “shorting FRAUDS and pipe dreams”

After Shkreli continued to question the idea behind shorting Tesla, he continued as he pondered the mentality behind those who choose to bet against the stock:

“I don’t understand ‘TSLAQ.’ Guy is the richest man in the world. He won. It’s over. He’s more successful with his 2nd, 3rd, and 4th largest companies than you will ever be, x100.

You can admit you are wrong, it’s just a feeling which will dissipate with time, trust me.”

According to reports from both Fortune and Business Insider, Tesla short sellers have lost a cumulative $64.5 billion since Tesla’s IPO in 2010.

Elon Musk issues dire warning to Tesla (TSLA) shorts

Shorts did accumulate a temporary profit of $16.2 billion earlier this year.

Continue Reading

News

Tesla will let you bring back this removed Model 3 part for a price

It will cost $595 and is available on Tesla’s website. You will have to have a Model 3 on your Tesla account to purchase the stalk retrofit kit.

Published

13 hours ago

on

October 8, 2025

By

Credit: Tesla Asia/X

Tesla is now letting Model 3 owners in the United States bring back one part that the company decided to remove after it refreshed the all-electric sedan last year. Of course, you can do it for a price.

With the Model 3 “Highland” refresh that Tesla launched last year, one of the most monumental changes the company made was to ditch the turn signal stalk altogether. Instead, Tesla opted for turn signal buttons, which have been met with mixed reviews.

I drove the new Tesla Model 3, here’s what got better

The change was widely regarded as Tesla preparing for more autonomous driving in its vehicles, especially as its interiors have gotten even more minimalistic.

The lack of a stalk in the new Model 3 was just another move the company made to adjust drivers and passengers to seeing less at the steering wheel column.

However, many drivers did not prefer the use of buttons and wanted the stalk reinstalled. Tesla allowed it in several regions, launching a retrofit kit. It has now made its way to the United States:

It will cost $595 and is available on Tesla’s website. You will have to have a Model 3 on your Tesla account to purchase the stalk retrofit kit.

It is interesting to note that despite Tesla’s strategy to remove the stalk with the new Model 3, which was released in early 2024, the company did not choose to make the same move with the new Model Y.

The new Model Y launched in the United States in early 2025, and Tesla chose to install a stalk in this vehicle.

It seemed as if the turn signal buttons were too much of a polarizing feature, and although the company technically could have given orderers an option, it would not have been the most efficient thing for manufacturing.

Continue Reading

News

Tesla Full Self-Driving v14.1 first impressions: Robotaxi-like features arrive

Tesla Full Self-Driving v14.1 is here, and we got to experience it for ourselves.

Published

14 hours ago

on

October 8, 2025

By

Tesla rolled out its Full Self-Driving v14.1 yesterday, its first public launch of its most robust and accurate FSD iteration yet. Luckily, I was able to get my hands on it through the Early Access Program.

The major changes in FSD v14.1 were revealed in the release notes, which outline several notable improvements in areas such as driving styles, parking, and overall navigation. Here’s what Tesla outlined fully in its release notes:

  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
  • Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances).
  • Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
  • Added additional Speed Profile to further customize driving style preference.
  • Improved handling for static and dynamic gates.
  • Improved offsetting for road debris (e.g. tires, tree branches, boxes).
  • Improve handling of several scenarios including: unprotected turns, lane changes, vehicle cut-ins, and school busses.
  • Improved FSD’s ability to manage system faults and recover smoothly from degraded operation for enhanced reliability.
  • Added alerting for residue build-up on interior windshield that may impact front camera visibility. If affected, visit Service for cleaning!

I wanted to try it for myself. My big must-dos were my complaints with v13.2.9, which included parking when arriving at a destination, Navigation when leaving a destination, and definitely a general improvement in the car traveling at an acceptable rate of speed, even when using the “Hurry” driving style.

Here’s what I noticed with the new Full Self-Driving v14.1:

Speed Profiles are More Realistic

I am driving on “Hurry” about 95% of the time when utilizing Full Self-Driving. In past versions, most notably v13.2.9, my Tesla would slowly reach the speed limit, and it would tend to hang out at about 1-2 MPH either above or below it.

My first observation with v14.1 was the vehicle’s tendency to get right up to speed and, since I was still on Hurry, drive slightly above the speed limit. It never got out of line; it traveled at speeds I would typically drive at manually.

I think this is a big improvement on its own, because I felt that I was pressing the accelerator too frequently in past FSD versions. Oftentimes, it just wasn’t going fast enough to justify the “Hurry” label; it felt more conservative and more like a student driver than anything.

Check it out:

This was among my favorite improvements, and it was the first thing I noticed as the car navigated me to the Supercharger, where my next positive is.

Navigating into parking lots, self-parking at Supercharger

One of the changes noted in the Release Notes was the addition of Arrival Options, which allows the car to select the appropriate parking situation. Since I was going to charge, the car had already chosen “Charger” as the parking option.

Pulling into a gas station or convenience store, especially during work days, can be stressful, as they are usually congested and full of foot and vehicle traffic. In past FSD versions, I have noticed the car being slightly “jumpy” and even hesitant to proceed through the lot.

Driving through parking lots was a noticeable improvement. It seems as if the car is much more confident in making its way through, while still being aware and cautious enough to safely navigate to the Supercharger.

It then backed straight into a Supercharger stall, which was recently repaired and is once again active. I was actually upset it chose this specific stall because it had been inactive for a while. However, Tesla got this stall back up and running, the car chose it, and backed into the spot flawlessly:

This was super cool to experience, and I think it is a testament to how hard the Tesla AI team has worked. CEO Elon Musk recently stated that FSD would enable automatic parking at Superchargers, which was really awesome to experience firsthand.

I decided to leave the Supercharger and go to an auto parts store to pick up some interior cleaner and some microfiber towels. I love keeping my Tesla clean!

I also thought it would be a great opportunity to see how it would react to another parking lot, how it would navigate it, and let it choose a parking spot. It did it all flawlessly:

I had zero complaints about everything here. All of it was done really well.

Making a choice after being caught in the middle of an intersection

I arrived at a tight intersection in Dallastown, PA, and what my car did next has catalyzed quite a conversation on X.

It proceeded out into the middle of the intersection as the light was green. It had to yield to oncoming traffic, and while waiting, the light turned yellow, then red.

Most people, including myself, would have turned right and proceeded through the intersection since the car was already past the line. However, FSD chose to back up and wait for the next light cycle, which I felt was also a more than acceptable option:

There are some conflicting perspectives on what it chose to do here. Some said they would have proceeded and would want FSD to also proceed. I can agree with that perspective, but I also think it is not the worst thing in the world to back up. In Pennsylvania, I couldn’t find the exact law that says what is right or wrong. Instead, I did see that a left turn on red is only feasible when you’re going from a One-Way street to another One-Way.

I’m not totally sure what is “correct” here, but I think either option is fine. I have personally done both, and I’ve seen other drivers do both. I was more than fine with the car doing this, and I was honestly impressed that it did.

Navigated a busy grocery store lot, found suitable parking

This is not the busiest my local grocery store gets, but it was still congested enough for me to be impressed.

FSD decided to do one loop in the parking lot before it found a spot that it felt was good enough for me. I was perfectly fine with where it chose to park, and I thought it did a really great job. I was impressed with how stress-free I felt, as I have noted in the past that parking lots are definitely an area where Tesla needs to improve.

I was happy with its performance:

Strange right turn signal as if it saw an emergency vehicle

This was the first bug I noticed with FSD v14.1. While traveling on a local road, it put the right turn signal on and approached the curb as if it was pulling over for an emergency vehicle or as if it was going to park on the street.

It then realized its mistake and proceeded:

I’m not super sure what caused this, but I was a tad bit confused. There were no police cars, ambulances, or anyone with flashing lights to my rear. There was a dump truck on the other side of the road, and I almost felt like the way it navigated “around” that was probably what triggered it.

Navigation is still making strange decisions

I’ve written about navigation and my discontent with some of its decisions. It seems v14.1 didn’t resolve much of anything with navigation, and it did a couple of things wrong.

The first was that it tried to take the illogical and pointless path out of the Supercharger. I wrote about this a few days ago, as FSD tried to take my car the wrong way.

It did it again, but I overrode the decision, and it was all okay:

This is a minor issue, but it is still pretty frustrating. Hopefully, the navigation will learn after performing this adjustment after enough times.

The next navigation issue was more frustrating than the Supercharger one, especially considering it completely ignored the route. The navigation had the vehicle very clearly heading straight, but out of nowhere, the right turn signal went on. I overrode it, but the car still turned right, ignoring the navigation completely:

I ended up taking over here and driving until I could get to a stop sign.

Final Thoughts

I am really impressed with all of the changes Tesla made with FSD v14.1, and while there were a handful of bugs, things were tremendously better than v13.2.9.

Continue Reading

Trending