Connect with us

News

SpaceX’s next West Coast Falcon 9 landing could be decided by baby seals

Falcon 9 B1051 lands aboard drone ship OCISLY after its March 3rd launch debut. The same booster will launch RCM on June 11th. (SpaceX)

Published

on

SpaceX and the Canadian Space Agency (CSA) have – at long last – officially announced a launch date for the Radarsat Constellation Mission (RCM), a ~$1B trio of Earth observation satellites.

Delayed from November, February, March, and May, RCM is now scheduled to launch on a flight-proven Falcon 9 booster from California’s Vandenberg Air Force Base (VAFB) no earlier than June 11th. The three flight-ready spacecraft were shipped from Canada in September 2018 and have now been awaiting launch in a Southern California storage facility for more than half a year. The blame for such an egregious delay can be largely placed on SpaceX, but CSA and launch customer Maxar Technologies are also partially responsible. On a lighter note, the location of RCM’s subsequent Falcon 9 landing might end up being decided by seal pupping – baby harbor seals, in other words.

Although RCM’s slip from 2018 to 2019 remains unexplained, the mission’s journey from mid-February to mid-June is a different story. Still, next to nothing is publicly known about the process SpaceX launch customers go through after contracts have been signed, particularly with respect to how Falcon boosters are assigned to missions. This is further stymied by the fact that – to date – the ~$1 billion RCM is probably the most valuable payload SpaceX has ever attempted to launch, making it a clear outlier. But, as they say, “damn the epistemological torpedoes!”

Rocket logistics hell

RCM’s logistical hell and ~6 months of delays began on December 5th, 2018 when Falcon 9 Block 5 booster B1050 – having just completed its inaugural launch debut – experienced a hydraulic pump failure. The first of its kind, B1050’s pump failure killed grid fin control authority and forced the booster to abort into the Atlantic Ocean, where it somehow pulled off a landing soft enough to leave the rocket almost entirely intact. Even more surprisingly, B1050 was safely towed back to port, lifted onto dry land, and shipped off to one of SpaceX’s many Florida hangars for inspection.

Despite its near-miraculous survival, B1050 was immediately removed from SpaceX’s fleet of flightworthy boosters. Set to become the least flight-proven flight-proven Block 5 booster yet after supporting a low-energy Cargo Dragon mission, SpaceX and CSA/Maxar had apparently reached an agreement to launch RCM on B1050.2. Despite the availability of other boosters at the time, all available cores had completed two launches (B1046, 47, and 48) or were assigned to a second launch in the near-term (B1049). This is the only rational explanation for the delays that followed.

B1049 completed its second launch in mid-January 2019 and has since floated around various SpaceX facilities while waiting for its third mission. Had CSA/Maxar been okay with a twice-flown Falcon 9, B1049 could have likely supported RCM’s launch as early as March or April. Instead, the customer – as was apparently their right – concluded that being a booster’s third launch would be an unacceptable risk, whereas launching on a once-flown booster was acceptable. The only possible solution to those demands was to manifest RCM on Falcon 9 B1051, assigned to Crew Dragon’s launch debut.

Quite possibly the worst booster one could pick for schedule preservation, Crew Dragon’s launch debut slipped – to the surprise of very few – from January to February and finally to March 3rd. B1051 launched, landed without issue, and returned to Port Canaveral a few days later, where it was transported to Pad 39A for refurbishment. The relatively gently-used booster required a bit less than 8 weeks of inspection and refurbishment before being packaged and shipped to California near the end of April (see above). By now, B1051 is likely safely inside SpaceX’s SLC-4E integration hangar, preparing for upper stage integration and a routine pre-launch static fire test.

Advertisement
B1051 landed aboard drone ship OCISLY around 8 minutes after launch. (SpaceX)
Falcon 9 B1051 was refurbished inside Pad 39A’s main hangar. (SpaceX – April 2019)
B1051 was shipped west on April 26th. (Facebook – Joshuah Murrah)

In short, an untimely Falcon 9 anomaly and customer preferences conspired to delay the launch of Canada’s Radarsat Constellation Mission by nearly four months, from February 18th to June 11th. With any luck, the mission’s flow will be issue-free and suffer no additional delays.

FCC launch communications licenses currently show that SpaceX plans to return Falcon 9 B1051 to the launch site (RTLS) after launch, rather than landing aboard drone ship Just Read The Instructions (JRTI). With a total launch mass likely around 5000 kg (11,000 lb), Falcon 9 should easily be able to manage a RTLS recovery. However, SpaceX’s West Coast LZ-4 use permit prevents the company from landing rockets at the pad during harbor seal pupping season, typically March thru June. The sonic booms and noise generated during Falcon 9’s spectacular landings might end up stressing endangered harbor seals, potentially causing parents to abandon their seal pups in confusion. As such, JRTI may be forced to get some exercise after spending almost five months in port. Anything for the baby seals!

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

SpaceX adjusts Starship Flight 13 test launch target date once again

Published

on

Credit: SpaceX

SpaceX has updated its target for the thirteenth integrated flight test of Starship, aiming for as early as Thursday, July 23. The 90-minute launch window opens at 5:45 p.m. CT from the company’s Starbase facility in South Texas.

The target flight was initially rescheduled for today, but SpaceX pushed it back again.

This latest adjustment follows an aborted attempt earlier in the week and reflects the iterative, rapid-development approach that has defined the Starship program. With the vehicle already stacked and ground teams making final preparations, the mission represents another step toward proving the full reusability of the world’s most powerful rocket system.

The original launch attempt on July 16 was scrubbed at T-0 when several Raptor engines on the Super Heavy booster failed to ignite properly. The automatic abort system triggered just as the engines began their startup sequence, preventing liftoff.

SpaceX CEO Elon Musk confirmed that some engines did not start as expected, prompting the decision to replace two Raptors on Booster 20 to ensure reliability. The issue occurred despite a successful full-duration static fire earlier, highlighting the complexities of coordinating 33 engines under flight conditions.

This cautious approach underscores SpaceX’s commitment to safety amid an aggressive test cadence.

SpaceX comes with a slew of changes for Starship Flight 13

Flight 13 builds directly on the lessons from Flight 12 in May 2026. The Super Heavy booster’s primary goals include a successful liftoff, ascent, stage separation, boostback burn, and controlled splashdown in the Gulf of America.

Hardware and software modifications address the off-nominal flip and boostback burn problems from the prior flight, where propellant slosh and engine relight issues led to an uncontrolled impact.

For the Starship upper stage, objectives include deploying 20 operational Starlink V3 satellites, the first real payload of this type, performing a single Raptor engine relight in space, and executing a controlled entry, descent, and splashdown in the Indian Ocean. Propulsion upgrades aim to improve engine-out capability after one vacuum Raptor was lost on Flight 12.

Additional test elements focus on heat shield performance. Six satellites carry cameras to image the tiles during flight, while white-painted tiles and upgraded attachments on flaps and the aft skirt will gather data for future reusability.

The FAA completed its mishap investigation into Flight 12 earlier this month, clearing the regulatory path.

This suborbital mission, the second with V3 vehicles, advances Starship toward operational missions, including potential crewed flights and support for NASA’s Artemis program. Success would mark significant progress in rapid reusability and satellite deployment from the massive system.

Continue Reading

News

Elon Musk debunks $52 billion SpaceX-NVIDIA GPU deal

Published

on

Credit: SpaceX

Elon Musk dismissed reports claiming SpaceX had placed a massive order for NVIDIA GPUs worth $52 billion. The denial came hours after Taiwanese media, citing unnamed industry sources, reported that SpaceX planned to acquire approximately 13,000 AI server racks, equating to roughly 1 million GB300 GPUs, from Foxconn.

Each rack was estimated at around $4 million, with deliveries potentially starting in late 2025.

The story suggested this would mark SpaceX’s first major foray into Foxconn-manufactured NVIDIA hardware, breaking from suppliers like Supermicro and Dell. Musk responded bluntly on X:

Despite the denial, the rumored scale aligns with SpaceX’s explosive growth in AI infrastructure. NVIDIA’s GB300 (successor to the GB200 NVL) racks deliver unprecedented performance for large-scale training and inference. A $52 billion commitment would dwarf most corporate AI budgets and provide the compute muscle needed for frontier models.

SpaceX already operates gigawatt-scale terrestrial clusters like Colossus in Memphis, Tennessee, and has monetized them aggressively through leasing deals.

SpaceX’s newest Starmind will make earth data centers obsolete

Major customers include Anthropic (paying ~$1.25 billion monthly for 220,000+ GPUs), Google (~$920 million monthly for 110,000 GPUs), and Reflection AI. These arrangements are projected to generate tens of billions in annual revenue, far outpacing traditional SpaceX businesses.

Such an investment would fuel internal AI efforts, particularly Grok models under the integrated SpaceXAI division, while supporting ambitious orbital data center plans. SpaceX envisions launching thousands of AI-optimized satellites powered by solar energy and cooled in space, bypassing terrestrial power and land constraints.

This “Starmind” constellation could position the company as a leader in space-based computing.

SpaceX as an Emerging AI Powerhouse

Once primarily known for reusable rockets and Starlink satellite internet, SpaceX has transformed into a multifaceted AI player.

The 2026 acquisition of xAI integrated Grok development directly into the company. Starlink’s low-latency global network complements massive compute clusters, enabling efficient data flow for training and serving AI models.

Musk has long argued that AI scaling demands solutions beyond Earth, citing things like real estate and electricity limits on the ground.

While the Foxconn deal may not be in the cards, SpaceX’s trajectory is continuing on the path of blending aerospace engineering with hyperscale AI to dominate both launches and intelligence infrastructure.

Continue Reading

Elon Musk

Elon Musk sheds details on Tesla FSD’s upcoming improvements

Published

on

Credit: Tesla

Elon Musk shed more details on the upcoming improvements to Tesla’s Full Self-Driving suite, specifically one that the CEO mentioned last week, which should help owners see fewer interventions.

Last week, Musk hinted that one major improvement that Tesla planned to roll out to Full Self-Driving users was the car’s ability “to remember your specific interventions and match each person’s individual preferences.”

Elon Musk says your Tesla will start to learn your individual preferences

This small bit of detail was linked to a post from Tesla community member Whole Mars, who said that FSD’s tendency to exit the carpool lane, a feature that owners can turn on but at times the car will disregard.

It sounds like, based on Musk’s two responses since that original post, it is safe to say the things FSD will start to remember are wide-ranging. However, it seems the biggest differences will be noticed with parking performance, which Musk continues to mention.

Highway Lane Preferences

The initial post Musk mentioned, with these new remembered preferences soon to arrive for Tesla owners everywhere, was the Carpool/Express Lane.

Tesla has a setting in the FSD menu that lets drivers enable HOV Lane travel. However, the car won’t always stay in that suggested or preferred lane.

Some owners have also complained of left lane camping, an illegal maneuver in at least some states. Cruising in the passing lane has resulted in tickets for some, as it is illegal in over 30 states in the U.S.

Tesla did not confirm if these preferences would also be included in new FSD behaviors, but it would certainly help move the company toward fewer interventions.

Parking Preferences

This seems to be the real focus of the entire operation, as Musk stated several weeks ago that parking was overwhelmingly the most frequent reason for interventions.

The major issue with parking is not necessarily the parking “performance,” as FSD is generally good at parking. It definitely has its issues; we’ve recorded plenty of them, including this one as recent as last week:

However, the changes coming are more about preferences, meaning where you park and how your car enters the spot, either pulling in or backing in. Owners have also reported that pulling into the correct driveway is a relatively rare thing for FSD, something else that needs to be confronted.

Musk basically confirmed that all of these things would be part of Tesla’s plan to address driver preferences with FSD:

It’s obvious there is something big coming with FSD, and the company’s focus seems to be eliminating any intervention that would be related to preferences. This is probably the biggest bottleneck between Tesla and being fully autonomous. Critical interventions do occur, but they are much less frequent.

The only time a driver should be taking over is because of a critical intervention; this seems to be the goal of Tesla right now.

This all seems to be a priority as Tesla continues to move closer to the prospect of unsupervised driving.

Continue Reading