Connect with us

News

SpaceX’s partial Falcon 9 landing failure could delay next West Coast launch

Wait, that's not supposed to be there... (Tom Cross)

Published

8 years ago

on

According to statements made by the Canadian Space Agency (CSA) and media outlet CBC, the launch of the agency’s next-generation Radarsat Constellation Mission (RCM) – a trio of Earth observation satellites weighing >4200 kg (9300 lbs) – has been “postponed … indefinitely” as a consequence of SpaceX’s first failed Falcon 9 booster landing since 2016.

Offering a rare glimpse into some of the extensive planning that goes on behind the scenes to make commercial rocket launches happen, CSA has indicated that the booster it planned to launch on – Falcon 9 B1050 – suffered an untimely (partial) demise during a recovery attempt shortly after successfully launching the CRS-16 Cargo Dragon mission on December 5th, 2018. While the booster shockingly was returned to dry land mostly intact after landing in the Atlantic, SpaceX and CSA must now settle on a different Falcon 9 to launch the mission.

Goldilocks and the Falcon boosters

While it doesn’t look like there are only three possible rocket options for the Radarsat constellation and SpaceX to choose from, the situation of picking a new booster this late in the launch flow is far less simple than it might initially seem. First and foremost, SpaceX likely needs to do its best to accommodate the preferences of customers CSA and MDA (MacDonald, Dettwiler and Associates Ltd.) regardless of how disruptive they may be. Originally targeted for sometime in November 2018, RCM’s launch slipped several months to the second half of February 2019 due to what CSA described as “higher priority missions [for]the US Government and a backlog of launches from…Vandenberg” late last year.

While that alone does not point directly towards any obvious explanations, CBC reporter Dean Beeby’s implication that the mission’s launch is now “postponed…indefinitely” offers a hint of an answer, although it could also be manufactured hyperbole where there actually is none. If CSA actually indicated that the launch is now postponed indefinitely, the only clear explanation for a launch delay greater than a month or so as a result of Falcon 9 B1050’s unplanned unavailability would lie in some unique aspect of that particular Falcon 9 booster.

Advertisement
-
-

Although each rocket SpaceX builds can be quite different from each other in terms of general quirks and bugs, the only obvious difference between B1050 and any other flight-proven Falcon 9 booster in SpaceX’s fleet was its low-energy CRS-16 trajectory, something that would have enabled a uniquely gentle reentry and landing shortly after launch. In other words, likely out of heaps of caution and conservatism if it is the case, customers CSA and MDA may have requested (or contractually demanded) that SpaceX launch the Radarsat constellation on a flight-proven Falcon 9 with as little wear and tear as possible, in which case B1050 would have been hard to beat.

“Unfortunately, the landing of [Falcon 9 B1050] was unsuccessful, preventing SpaceX from recuperating the reusable components for the launch of RCM. We continue to work closely with MDA and SpaceX to confirm a launch date for RCM.” – Spokesperson Audrey Barbier, Canadian Space Agency (CSA), 01/15/2019

If the customers remained steadfast in their (speculated) request for a gently-used flight-proven Falcon 9 even after B1050’s partial landing failure, the next most comparable booster would be Falcon 9 B1051 after launching the first orbital Crew Dragon mission sometime no earlier than (NET) February 2019. Aside from B1051, there will be no obvious booster alternative available for at least several months after Crew Dragon’s launch debut, unless NASA requests that its next contracted Cargo Dragon mission (CRS-17) launch on a new Falcon 9 rocket in March 2019.

Warmer…

If a less lightly-used booster becomes an option for CSA/MDA, there are immediately multiple clear options available as long as SpaceX is will to accept possible delays to subsequent launches to quickly reassign a flight-proven Falcon 9. Falcon 9 B1046 – the first SpaceX rocket ever to launch three orbital-class missions – is being refurbished at SpaceX’s Hawthorne, California facilities a few hundred miles south of Vandenberg. B1047 completed its second successful launch in November 2018 and is being refurbished – along with the twice-flown B1048 – in Cape Canaveral, Florida. Finally, Falcon 9 B1049 completed its second successful launch just days ago (January 11th) and is being processed off of drone ship Just Read The Instructions (JRTI) at this very moment.

B1047 or B1048 have likely been assigned to the imminent NET February 18th launch of Indonesian commsat PSN-6 and SpaceIL’s Beresheet Moon lander, meaning that the best possible option for Radarsat – short of swallowing months of additional delays – is a decision between B1047/B1048 or B1046, with B1049 also a candidate if a slip into March or April is an option. Still, all of those options would require Canada and MDA to fly on a Falcon 9’s third (or fourth) launch, perhaps an unacceptable compromise or perceived risk for certain customers.

 

Advertisement
-
-

Meanwhile, schedule pressures have meant that SpaceX is pushing as hard as possible to prepare three new Block 5 Falcon Heavy boosters for the giant rocket’s second and third launches, scheduled as early as March and April 2019. While unconfirmed, it appears that SpaceX may have chosen to manufacture all three of those boosters one after the other, meaning that the company’s Hawthorne factory would have been primarily focused on delivering those rockets for at least 2-3 months start to finish. In short, it does not appear that there is or will be an unflown Falcon 9 booster available for Radarsat anytime soon.

Whether the customers wait for a new booster to be produced, wait for Crew Dragon’s first launch to wrap up, or accept being the third or fourth launch of a well-scorched Falcon 9, RCM’s next published launch target should offer a hint as to how CSA, MDA, and SpaceX ultimately decided to respond to Falcon 9 B1050’s dip in the Atlantic OCean.

Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes!

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

News

Tesla briefly offered this Robotaxi part for your personal car

Published

36 minutes ago

on

July 28, 2026

By

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.

Advertisement
-
-

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

3 hours ago

on

July 28, 2026

By

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.

Advertisement
-
-

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

23 hours ago

on

July 27, 2026

By

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.

Advertisement
-
-

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.

Advertisement
-
-
Continue Reading