Connect with us

News

SpaceX's workhorse Falcon 9 rocket expected to reach major launch milestone in 2020

Published

on

Hours after SpaceX launched its 240th new Starlink satellite into orbit, Elon Musk took to Twitter to cryptically reveal that the company’s workhorse Falcon 9 rocket could “reach triple digits this year” if everything goes according to plan.

Designed and built by SpaceX in the late 2000s, the Falcon 9 rocket launched for the first time in June 2010. Developed for the unfathomably low price of $300 million from clean-sheet design to first orbital launch, the original single-core Falcon 9 rocket – known as V1.0 – was about 48m (160 ft) tall, weighed 333 metric tons (735,000 lb) fully fueled, and was capable of launching almost 10.5 metric tons (23,000 lb) into low Earth orbit (LEO). Famously, when provided with Falcon 9’s basic specifications and characteristics, an independent NASA study estimated that the rocket’s development would have cost the agency anywhere from $1.7 billion to $4 billion to design and build.

NASA came to this conclusion in 2011, less than a year after Falcon 9’s first launch, and that the disconnect between the status quo held by NASA and the broader US spaceflight industry and what SpaceX tangibly achieved came to almost perfectly symbolize the rocket’s first six or so years of operations. Although SpaceX stumbled hard with two catastrophic rocket failures in June 2015 and September 2016, the company ultimately picked itself up, learned from those still-agonizing lessons, and has since shaped Falcon 9 into one of the most capable, reliable, reusable, and prolific launch vehicles ever flown. That latter characteristic – the sheer volume of launches Falcon 9 has come to represent – is what CEO Elon Musk was referring to earlier this week.

Specifically, after Wednesday’s flawless launch, Falcon 9 has now launched 80 times in its 9.5-year career, while Starlink V1 L3 marked the workhorse rocket’s 52nd consecutive success of 79 total. Impressively, while those 52 launches represent almost 65% of all of Falcon 9’s missions, SpaceX has dramatically improved the rocket’s reliability and availability over the last few years. In short, Falcon 9 has completed 52 consecutively successful launches in exactly 36 months (January 2017 to January 2020), meaning that nearly two-thirds of its lifetime launches have occurred in less than a third of the time Falcon 9 has been operational.

SpaceX's three surviving thrice-flown Block 5 boosters - B1048, B1049, and B1046 - are pictured here in various stages of recovery. (Teslarati, Pauline Acalin)
Falcon 9 B1048, B1049, and B1046 pictured in various stages of their most recent launches. Together, the three have supported twelve successful orbital-class launches. (Tom Cross & Pauline Acalin)

Put a different way, since the start of 2017, SpaceX has – on average – launched Falcon 9 more than four times (1.4 launches/month) as often as the rocket managed in its first 6.5 years of operations (1 launch every 2.7 months). Tweeting on January 29th, 2020 in response to an overview of the number of launches performed by each operational US rocket, CEO Elon Musk hinted that he believes “Falcon 9 will achieve triple digits” in 2020.

In other words, Musk thinks that SpaceX’s workhorse Falcon 9 rocket will be able to reach more than 100 lifetime launches by the end of 2020 — a feat that will require at least 20 additional Falcon 9 launches over the next 11 months. Speaking hours after SpaceX completed its third launch in January 2020 alone, it’s not hard to imagine – assuming, as Musk did, that “all goes well – that Falcon 9 will manage another 20 launches this year.

Falcon 9 B1049 lifted off for the fourth time with a batch of 60 Starlink satellites on January 7th. (Richard Angle)
Albeit suborbital, Falcon 9 B1046 supported SpaceX’s second launch of 2020 – Crew Dragon’s In-Flight Abort test – on January 19th. (Richard Angle)
Finally, B1051 launched another batch of 60 Starlink satellites on January 29th, likely SpaceX’s last launch of the month. (Richard Angle)

Averaged out, SpaceX has performed a launch every 9.7 days in January. Extrapolated to the rest of the year and assuming no improvement, SpaceX could theoretically perform as many as 37 launches in 2020. It’s worth noting, however, that SpaceX’s third launch of the month was ready for flight as early as January 21st but was delayed more than a week by bad weather – obviously out of the company’s control. Had weather permitted, SpaceX even had a fourth launch planned this month – a Starlink mission that is now expected sometime in early February.

In simple terms, it would take one or several major upsets to prevent Falcon 9 from reaching >100 lifetime launches later this year. Even if every single customer launch abruptly slips into 2021, SpaceX has still said that it has plans for 20-24 dedicated Starlink launches in 2020 alone, potentially singlehandedly carrying Falcon 9 over the 100-launch crest.

Falcon 9’s next launch – the fourth Starlink v1.0 mission – is currently scheduled no earlier than (NET) early February, followed by another Starlink mission later that month and Cargo Dragon’s final space station resupply mission NET March 2nd.

Advertisement
-
-

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

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 briefly offered this Robotaxi part for your personal car

Published

on

Credit: @tpgoebel | X

Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.

Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.

First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.

This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.

However, this part has since been removed and is no longer visible on the EPC.

Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?

While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.

AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.

This could be the first hint of that’s where we are headed.

Continue Reading

News

Tesla Robotaxi gets sweeping but polarizing change

Published

on

Credit: Tesla

Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.

Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.

But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:

However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.

Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.

Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.

The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.

Continue Reading

News

Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

on

Credit: Tesla

Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.

Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.

However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.

With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.

Turning Hesitancy, Inaccuracy

I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.

Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.

I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.

FSD Disregards Manual Turn Signals

This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.

If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.

FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.

This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.

This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.

Bird Braking is a Thing of the Past

The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.

There have been zero issues with this so far in v14.3.6, which is an excellent improvement.

FSD Might Already Be Taking Note of Driver Preferences

Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.

This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.

Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.

Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.

It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.

As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

Continue Reading