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

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.

Advertisement
-

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.

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.

Advertisement
-

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.

 

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!

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 Full Self-Driving release in the EU gets delayed

Published

on

Credit: Grok Imagine

Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.

The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.

Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.

That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.

Elon Musk’s reply to the delay was a single word: “Sigh.”

Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.

Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.

The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.

An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.

Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval

Advertisement
-

The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.

Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.

Continue Reading

News

SpaceX readies Starship Flight 14 for a historic journey into uncharted territory

SpaceX finished Starship’s Flight 14 rehearsal, clearing the way for its first orbital flight Monday.

Published

on

By

Sunrise at Starbase. Starship is stacked for opportunistic full-stack testing ahead of Flight 14 via SpaceX
Sunrise at Starbase. Starship is stacked for opportunistic full-stack testing ahead of Flight 14 via SpaceX

SpaceX has cleared one of the last hurdles before Starship’s first trip to orbit. The company posted on X Thursday afternoon that its launch rehearsal for Flight 14 was complete, keeping the mission on track for Monday, September 28. The launch window opens at 7:15 a.m. CT at Starbase, Texas, and runs for 75 minutes.

A wet dress rehearsal is essentially launch day without the launch. Crews fill Booster 21 and Ship 41 with thousands of tons of extremely cold propellant, run the countdown nearly to ignition, then drain everything back out. It lets engineers catch leaks or equipment problems before anything leaves the pad. SpaceX still needs a launch license from the FAA before the stack, which stands 407 feet tall, can fly.

Flight 14 matters because of where it is going. All 13 previous Starship flights followed a suborbital path, which works like throwing a ball extremely high and far: the vehicle reaches space, but it is always on a course that brings it back down within about an hour. This time, Ship 41 will perform a short engine firing called an orbital insertion burn roughly 25 minutes after liftoff, giving it enough speed to keep falling around Earth instead of back into it. SpaceX plans about six laps at an altitude near 275 kilometers (171 miles) over nearly 10 hours, as Teslarati detailed when the mission was first announced.


Getting into orbit also means Starship has to prove it can get back out. The ship must relight a single Raptor engine in space to slow down for reentry. SpaceX says it will only attempt the orbital insertion burn after flight controllers confirm the hardware needed for that return burn has enough backup, and its flight plan includes health checks that could shorten the mission to two or five orbits.

Flight 14 is also the first to put working satellites into service. Flight 13 carried 20 Starlink V3 satellites in July, but they came back down with the ship because that mission never reached orbit. This time, 26 V3 satellites are meant to stay up and join the constellation within a few weeks. Together they add about 26 terabits per second of network capacity, which SpaceX says is roughly 10 times what a single Falcon 9 launch of older V2 Mini satellites adds. Three of them carry cameras that will photograph Starship’s heat shield in orbit to check for tile damage before reentry.

Advertisement
-

The hardware has changed too. Ship 41 flies with extra fasteners on tiles in the most vulnerable areas, fixes for gaps where superheated plasma slipped behind tiles, and curved tiles designed to reduce heating between them. Two tiles recovered from Ship 40 will fly again, the first reuse of any part of a Starship heat shield. Booster 21 carries better engine filtering and new relight software after ice clogged three center engines on the previous booster, leaving only eight of 13 engines to restart for its landing burn.

Ship 41 is targeting a splashdown in the Pacific Ocean west of Chile, a new recovery zone after several Indian Ocean landings, while Booster 21 aims for the Gulf. Neither will be caught by the tower on this flight. Elon Musk said in August that a ship catch was likely “in a few months.”

Continue Reading

Elon Musk

Google just picked SpaceX for its first step into orbital AI

Google will launch its first Project Suncatcher AI satellite on SpaceX’s Transporter-18 rideshare next week.

Published

on

By

Google is about to put its own AI chips into orbit for the first time, and it is paying SpaceX to get them there.

The company said Thursday that the first in-orbit test of Project Suncatcher, its research effort to find out whether space can host large-scale AI computing, will fly next week on SpaceX’s Transporter-18 rideshare mission.

The satellite, called MVP, is about the size of a refrigerator and carries four of Google’s Tensor Processing Units, the same chips Google runs in its ground data centers. Google originally planned to launch two custom satellites in 2027, but chose to move faster by integrating its chips into a satellite.

MVP’s solar panels supply about one kilowatt of power, and Google will run Gemini models on the TPUs only in bursts of roughly 15 minutes before the chips shut down so the radiators can shed heat. In a blog post, Google said its Trillium TPUs survived vibration testing that mimicked sustained launch loads of up to 10g, with individual components seeing 50 to 100g, and handled a radiation dose greater than a five year mission would deliver.

SpaceX and Google mull massive partnership on Musk’s orbital data dream: report

Next week’s flight, slated for October 1, follows a relationship that became public in May, when Teslarati reported that Google was in talks with SpaceX for a launch deal tied to orbital data centers. Google also holds a stake of roughly 6% in SpaceX.

Advertisement
-

The two companies are chasing the same idea from very different starting points. SpaceX’s own orbital compute program is built around the AI1 satellite, a roughly 70 meter structure derived from Starlink V3 hardware that is designed for 150 kW of peak compute, about 150 times the power MVP will draw. Elon Musk has brushed off concerns about crowding orbit with those satellites, and SpaceX is building its Gigasat factory in Bastrop, Texas, to produce them, targeting an annualized rate of about 1 GW of space compute by the end of 2027.

Musk also posted on X on Thursday that “the amount of compute in space will obviously round up to 100% of all compute.”

Google has been more cautious in public. Its research estimates that launch prices need to fall below about $200 per kilogram before an orbital data center can compete with a ground facility on energy cost, a threshold the company believes could be reached around the mid 2030s. The Suncatcher team has said it expects the effort to remain a project rather than a product for years, which leaves the first real test of its hardware riding on a rocket from the company with the most aggressive timeline in the field.

Continue Reading