Connect with us

News

SpaceX’s Starhopper readies for more ambitious Raptor-powered flight tests

On June 1st, SpaceX technicians began installing a new Raptor - this time SN04 - on Starhopper. (NASASpaceflight - bocachicagal)

Published

on

For the second time in two months, SpaceX technicians have begun to install a Raptor engine on Starhopper, a full-scale Starship testbed theoretically capable of low-velocity, moderate-altitude ‘hops’.

Back in late March, Raptor and Starhopper were joined for the first time, enabling a lengthy series of attempted tests that were followed by two engine ignitions and tethered hops before Raptor was removed for inspection. In the two months since that first round of integrated testing, SpaceX has significantly upgraded Starhopper and its spartan launch facilities, all focused on transforming the odd vehicle from a largely fixed test stand into a giant, mobile Grasshopper.

All the way back in 2012, SpaceX began testing Falcon 9 recovery and reusability concepts with a low-fidelity prototype known as Grasshopper – essentially a minimalist Falcon 9 first stage with ad hoc legs and a single Merlin engine. It supported a series of 8 major test flights – all successful and a source of valuable data – before the vehicle’s 2013 retirement. An upgraded Grasshopper – known instead as Falcon 9 Reusable Development Vehicle (F9R Dev1) – began testing around the same time and continued even higher altitude vertical takeoff/vertical landing (VTVL) tests until its untimely demise in August 2014.

Starhopper is quite similar, although it is also serving as a testbed for a far more varied range of technologies due to the fact that it has been developed before the inaugural launch of its namesake (Starship/Super Heavy). By the time SpaceX started Grasshopper/F9R tests, Falcon 9 had already completed several successful launches. With Starhopper, SpaceX is building and testing its first 9m-diameter ‘flight’ hardware, its first propellant tanks built out of steel, its first flight-capable rocket fueled by methane and oxygen, and its first mobile Raptor testbed, among numerous other things. The challenges are inherently much greater, but SpaceX has the luxury of taking the opposite approach it took towards Falcon 9 and building a launch vehicle entirely around its intended reusability, rather than trying to squeeze a method of reusability around an already-flying rocket.

Saurid Oddities

As noted by NASASpaceflight.com in a June 2nd article, SpaceX seems to be juggling its growing selection of newly-produced and tested Raptor engines in pursuit of Starhopper’s return to flight. According to the publication’s reliable sources,

“Up until recently, [SpaceX] was planning to utilize Raptor SN4 for [Starhopper’s first] untethered hops. However, the company has now decided to utilize this engine only for fit checks, and will instead perform the hops with SN5 – the latest Raptor to come out of SpaceX’s factory in Hawthorne, California.” – NASASpaceflight.com, June 2nd, 2019

This indicates that the Raptor engine delivered to Boca Chica on June 1st and currently in the process of being installed on Starhopper is actually more of a stand-in* for a future Raptor, SN05. The reasons behind this Raptor shuffle elude detection, but it’s possible that the simplest explanation – also posed by NASASpaceflight – is the correct one. By shipping a Raptor that may not be ready for flight tests, SpaceX could likely save anywhere from a few days up to a few weeks by doing everything short of lifting off under the powered of Raptor SN04.

*By all appearances, SN04 is a flight-grade Raptor that has completed assembly and likely been test-fired in McGregor, Texas. Why it may currently be resigned to a “stand-in” role is unknown.

Very curiously, upon Raptor SN04’s South Texas arrival, it appears that SpaceX technicians have indeed rapidly installed the engine on Starhopper, but in a position that is decidedly off-center. Pictured above, the photo could have simply caught the engine while technicians were moving it to its actual installation spot, but it could also indicate that SpaceX is speeding towards Starhopper’s first triple-Raptor test flights.

Advertisement
-

Starhopper delays?

In line with the last-second switch from Raptor SN04 to Raptor SN05 as the engine-to-be for untethered hops, SpaceX has pushed the start of that test series from approximately May 31st to June 11th. More likely than not, the ~11-day delay is meant to allow time for Raptor SN05’s McGregor, Texas acceptance testing, given that – per CEO Elon Musk – the engine wasn’t even finished as of May 22nd.

On the other hand, with Raptor SN05 now scheduled to support Starhopper hop tests as early as mid-June, it begs the question of whether SpaceX is instead working towards expedited triple-Raptor testing. For unknown reasons, neither Raptor SN03 or SN04 are apparently ready to support flight operations, although both have been thoroughly hot-fired in McGregor. Perhaps each engine is a distinct prototype with a different level of experimental readiness, or perhaps SpaceX is just testing certain engines (like SN03) more extensively than others (SN05).

Regardless, SpaceX now seems to have 3-4 intact, functional Raptor engines (excluding SN01; destroyed during stress testing), 2-3 of which are actively testing or being worked on a day’s drive north of Boca Chica. SN02 – having successfully supported a brief duo of ignition tests with Starhopper – could still be intact and test-ready. SN03 is an unknown quantity, but SN04 is clearly in excellent shape and is probably close to flight-readiness if it isn’t already. This is to say that SpaceX likely already has three Raptors on hand that are capable of supporting multi-engine Starhopper testing, whether or not such a test regime would actually be valuable.

Musk has noted that both orbit-capable Starship prototypes will be far closer to finished products and will thus fly with “at least 3 engines” (3 sea level engines, as it would turn out) or even “all 6” (3 sea level, 3 vacuum-optimized). In the meantime, Starhopper stands with an off-centered Raptor, awaiting the arrival of a different Raptor to kick off a second hop test program. If nothing else, SpaceX’s Starship/Super Heavy development program is operating in a spectacularly hardware-rich fashion, lending itself to the breakneck-pace of iteration and improvement SpaceX is famous for.

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

Elon Musk

Tesla is fixing Full Self-Driving’s pothole problem

Published

on

Tesla Model Y L in a field
Credit: Tesla

Tesla Full Self-Driving is set to get a major fix with pothole avoidance, a feature that CEO Elon Musk said recently was “coming soon.” The feature has been included within the FSD v14 release notes for some time as an upcoming improvement.

Potholes come in all shapes and sizes, but one thing is universal about them, and that is the fact that every driver wants to avoid them. Driving into or over a pothole can cause tire and wheel damage, alignment issues, and even, in some more severe instances, injury to occupants or major damage to a vehicle in despair.

Tesla Cybercab uses a unique strategy for picking up the right rider

Musk said late last night in a post that pothole avoidance while utilizing the Full Self-Driving suite is “coming soon.”

Full Self-Driving, even in its most recent and robust forms, still has its shortcomings. While the suite has performed exceptionally well with avoiding on-road obstacles like cardboard boxes, horse droppings, car parts, and other debris, it still seems to struggle with recognizing certain things.

Potholes and other abrupt changes in a road’s layout are things that FSD still tends to struggle with. Perhaps the suite’s 3D modeling is still in need of some additional data or some sort of script that will help it to avoid a potentially destructive pothole or bump in the road that would be easily recognizable by the human eye.

Musk has mentioned pothole avoidance for some time, with the initial idea coming in April 2019 when an owner first requested the feature. Musk said that Tesla would “definitely” develop pothole avoidance.

In August 2020, Musk said Tesla was in the process of labeling bumps and potholes so cars can either slow down or steer around them altogether.

Tesla to utilize micro maps for pothole-detection in future update

Avoiding major disturbances in the road is a necessary feature for Full Self-Driving to have, especially as Tesla is working toward a fully autonomous program that will eventually allow every occupant in the vehicle to sleep, work, or enjoy leisure time while traveling.

That truly begins this week with the launch of Cybercab on Thursday.

Continue Reading

Elon Musk

Elon Musk says he knows how to save Earth for a billion years

Elon Musk says sentient AI satellites launched from the Moon could keep Earth livable forever.

Published

on

By

Elon Musk spent part of his weekend describing a plan to keep the planet livable for roughly a billion years, and it starts with satellites that can think for themselves.

In a post on X, Musk argued that swapping fossil fuels for solar and wind power will not be enough to protect humanity from what he called extremely severe extinction events, the kind that occur roughly every 100 million years. His fix is what he called sentient satellites, or solar-powered satellites, controlled by AI, that would sit in a fixed spot between Earth and the Sun after being launched off the Moon using a giant electromagnetic catapult instead of rockets.

The satellites’ onboard AI would make continuous, small adjustments rather than waiting on human instructions. The mass driver is Musk’s proposed way of getting the raw material there cheaply by using an electromagnetic launch track built on the Moon, where lower gravity and no atmosphere make it far easier to fling cargo into space than it is from Earth.

Musk shared a Grok generated estimate suggesting roughly 5 percent of Florida’s land, or about 1.68 million acres, could face regular flooding by 2070 under a high sea level rise scenario, and said humanity has about 50 years to act before coastal living looks very different than it does today.

This is not the first time Musk has floated the idea. He raised a similar concept in November, describing a solar powered AI satellite constellation that could make tiny adjustments to incoming sunlight to fine tune Earth’s temperature. Musk has also tied planetary risk to his broader vision at SpaceX, where his compensation package is explicitly linked to establishing a self-sustaining Mars colony, one he has described as an insurance policy against the kind of extinction event he referenced this weekend, and where he has said humans could set foot within five to seven years.

Continue Reading

Elon Musk

OpenAI cites distrust of SpaceX in decision to drop Cursor partnership

OpenAI will cut SpaceX-owned Cursor’s model access in November, citing Musk’s history of broken contracts.

Published

on

By

OpenAI, the company behind ChatGPT, announced late Friday that it is ending its partnership with Cursor, cutting off the coding tool’s access to its models on November 12. The move comes two weeks after SpaceX completed its $60 billion acquisition of Cursor’s parent company, Anysphere, folding the popular AI coding assistant into Elon Musk’s growing SpaceXAI division.

In a post on its website, OpenAI said the decision came down to trust, not technology. “We cannot be confident that SpaceX will use our technology within our terms of service, based on our experience with Elon Musk’s companies violating contracts,” the company wrote. OpenAI pointed to two specific incidents: X, now part of SpaceX, allegedly breaking the terms of an existing OpenAI contract after Musk bought Twitter.

That lawsuit is the backdrop for all of this. Musk cofounded OpenAI in 2015, left the board in 2018, and sued Sam Altman and Greg Brockman in 2024, arguing they abandoned the company’s nonprofit mission for profit. A federal jury sided with OpenAI in May, finding Musk waited too long to sue rather than ruling on the merits of his claims. Musk said at the time he would appeal to the Ninth Circuit, calling the outcome a “calendar technicality” rather than a real judgment.

Elon Musk breaks silence on OpenAI trial decision

SpaceX’s interest in Cursor predates that verdict by weeks. The company first struck a deal with Cursor in April, securing an option to acquire it for $60 billion or pay $10 billion for joint development work instead. As Teslarati reported at the time, the logic was straightforward: Cursor was paying retail prices to Anthropic and OpenAI, two of its most direct competitors, every time a developer used its product, while SpaceX had idle capacity on its Colossus supercomputer, roughly the equivalent of a million Nvidia H100 GPUs, that Cursor could use to train its own models instead. SpaceX exercised the option in June, days after its own IPO, and the deal closed in mid-August.

Once it closed, Musk moved fast. On an all-hands call with more than 1,000 Cursor employees, he reportedly told staff that SpaceXAI’s Grok was playing catchup in the AI race, unlike Tesla and SpaceX in their own markets, and singled out Anthropic as the company to catch. Cursor CEO Michael Truell now reports directly to Musk inside SpaceXAI.

Elon Musk admits he was ‘clearly wrong’ about Anthropic

Losing OpenAI’s models leaves Cursor leaning harder on Anthropic’s Claude, which has its own compute agreement with SpaceX, and on Cursor’s in-house Composer model, the one SpaceX’s compute was supposed to accelerate in the first place. OpenAI framed the November deadline as maximum notice under its contract, and said it wants to “go above and beyond” to help developers through the transition. Whether Anthropic makes the same call is now the open question in AI coding.

Continue Reading