Connect with us

SpaceX

SpaceX begins static Starhopper tests as Raptor engine arrives on schedule

SpaceX's second completed Raptor engine - serial number 2 (SN02) - arrived in Boca Chica on March 11th, right on time. (SpaceX, NASASpaceflight, bocachicagal)

Published

on

SpaceX has officially begun static ground testing of Starhopper, a full-scale pathfinder Starship prototype meant to support an early series of Raptor-powered hop tests at SpaceX’s South Texas launch site. Simultaneously, the second completed Raptor engine arrived at the site on Monday, March 11th, confirming CEO Elon Musk’s March 8th tweets about the delivery.

While reasonably routine for any rocket test program, the first tanking test of Starhopper effectively marks the first time that SpaceX has begun tests with a more or less fully integrated Starship (previously BFS). Likely performed with liquid nitrogen instead of liquid oxygen/methane, the first few tanking tests will be used to determine the quality of the prototype’s stainless steel tanks – built en plein air in a fairly unorthodox fashion – and test whether they are functional pressure vessels without risking immediate and total destruction. If successful, SpaceX will proceed into Raptor integration and integrated static-fire tests before preparing for tethered hover tests, perhaps as early as later this month.

In November 2016, SpaceX began propellant-loading tests of its first finished full-scale Starship (then Big Falcon Spaceship) hardware, a massive carbon composite liquid oxygen tank stretching 12 m (~40 ft) in diameter. Over the course of 2017, SpaceX transitioned from liquid nitrogen to liquid oxygen and ultimately conducted one final burst-test in which the composite tank was pressurized until it exploded, ending full-scale BFR composite testing with a bang. Within 6-12 months, Musk had come to the conclusion that a stainless steel BFR would ultimately be a superior path forward for the rocket and spaceship and attempted (apparently successfully) to get his team of R&D engineers on board with such a radical change so late in the development phase.

Despite the fact that that radical design departure may have occurred as few as 6-8 months ago, SpaceX engineers and technicians have accomplished an extremely rapid development program that will – in part – culminate in the hopefully successful hop testing of Starhopper, the first Starship prototype. While more of a rough testbed than an actual representation of the hardware and structures that will be required for a reusable orbital-class Starship, Starhopper has at least acted as a crash course (either technically or organizationally) on fabricating and assembling stainless steel aerospace structures, a material largely foreign to SpaceX flight hardware prior to late 2018.

Although the early vehicle was less than encouraging, as was the demise of its nosecone as a consequence of improper planning and/or bad workmanship, Starhopper as it now stands might actually be flightworthy in the context of suborbital, subsonic hop tests. Powered by the same or similar Raptors that would power orbital prototypes, Starhopper’s hop tests would optimally provide a wealth of experience and engineering data for both building 9 meter/30 foot-diameter stainless steel rocket sections and operating full-scale Raptor engine(s) in actual flight configurations. Extensive testing with Raptor will help to ensure that the fit and finish of the new engine’s flight-grade avionics and hardware are up to the challenge of safe, reliable, and gentle operations for a nominally crew-rated launch vehicle and spacecraft.

60 hours later, Musk was clearly not wrong.

Around two days after Starhopper was briskly transported from its build site to SpaceX’s brand new launch facility, local Twitter account @SPadre (short for South Padre Island) posted a video of tanking test that occurred on March 11th, capturing the sound of venting as the liquid involved turned to gas inside its propellant tank(s). The fact alone that the person behind the camera was allowed to be where they were during the test all but guarantees that this first test was performed with an inert liquid, most likely liquid nitrogen given a massive delivery that occurred the day before (March 10th). In no conceivable world would SpaceX or local law enforcement willingly allow for Starhopper to be loaded – for the first time ever – with even a partial load of liquid methane or liquid oxygen with bystanders barely a few hundred feet distant.

SpaceX accepted delivery of multiple truckloads of liquid nitrogen on March 10th, likely to support early tank loading tests to verify structural integrity and check for leaks. (NASASpaceflight – bocachicagal)

When SpaceX gets to the point that they are confident enough in the structural integrity of Starhopper to begin wet dress rehearsals and tests with actual propellant, it’s a safe bet that the company will cooperate with local law enforcement to block off the lone access road to a distance of at least 1-2 miles, if not more. It’s unclear if local homeowners and residents will be forced to vacate the adjacent Boca Chica Village during testing, but chances are good that nobody will be within several thousand feet of Starhopper when those propellant loading tests begin, let alone actual static fire activity once Raptor(s) are installed.

According to an official SpaceX statement on the progress, propellant load tests and static fires could begin “in the days ahead”, although the spokesperson was under the impression that those tests – as well as initial hop tests – “[would] not be visible from offsite”. Unless SpaceX plans to draw a keep-out zone with a radius of multiple miles, interested observers will almost certainly be able to get close enough to at least catch a glimpse of Starhopper, but the statement still offers an idea of just how focused the company will be on safety during these early tests.

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

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

SpaceX tells the FCC that Starship Flight 14 is going to orbit

SpaceX filed with the FCC for Starship Flight 14, its first true orbital launch attempt.

Published

on

By

SpaceX has asked the Federal Communications Commission for permission to fly Starlink terminals during Starship’s fourteenth flight test, and the filing lays out a genuine trip to orbit, something the program has never attempted.

Every Starship flight so far, including Flight 13’s successful splashdown in the Indian Ocean on July 24, has flown a suborbital arc that ends with the ship reentering the atmosphere within the same hour it launches. The FCC paperwork describes a mission profile built around an actual orbital insertion instead.

The payload is the other half of the story. Flight 13 carried 20 production Starlink V3 satellites, but because that mission never reached orbit, the satellites reentered along with the ship rather than joining the constellation, something Teslarati covered in detail after SpaceX released footage shot from one of those satellites as it drifted away from Starship in space. Flight 14 is designed to close that gap. If the orbital insertion holds, the roughly 20 V3 satellites onboard would separate into an operational orbit and could eventually go into service, each one rated for about 1 terabit per second of downlink capacity by SpaceX’s own account.

SpaceX announces new Starbase for ‘thousands of Starship launches annually’

Elon Musk first flagged the orbital attempt during SpaceX’s August 4 earnings call, the company’s first as a public entity following its June IPO under the ticker SPCX. He also floated catching the ship with the Starbase tower on the same flight, an idea he walked back on August 20, saying the catch attempt would more likely come “in a few months,” as Teslarati reported at the time. Flight 14 will instead target a splashdown for the ship in the Indian Ocean, the same recovery method used since Flight 12.

Hardware has been catching up to the ambition. Booster 21 completed a full 33-engine static fire on August 28, and Ship 41 finished its own six-engine test the week before. An airspace briefing circulated to pilots on August 20 listed September 15 as the target date, later than the end of August window Musk mentioned on the earnings call, though SpaceX has not confirmed a launch date publicly and Starship schedules routinely slip while hardware and FAA paperwork line up.

The FCC filing itself does not guarantee a launch date. It covers communications authority, and not flight readiness, considering SpaceX still needs Ship 41 fully stacked and cleared by the FAA before Flight 14 can fly. But the filing is a real marker of intent and it puts a specific regulatory process behind what had so far only been Musk’s word on the earnings call.

Continue Reading

Elon Musk

SpaceX would not exist if this crucial early launch failed, Musk says

Published

on

Credit: SpaceX

Elon Musk recently restated a fact that still defines SpaceX’s origin story: if Falcon 1’s fourth launch had failed, the company would not exist. The comment answered a reminder that after three consecutive losses, SpaceX had money for only one more attempt.

On X, Peter Diamandis said that the present-day acknowledgement of SpaceX’s success does not discount the rough start the company had. “Almost nobody remembers that Elon’s first rocket failed three times, and there was money for exactly only one more attempt.”

Musk said, “If the 4th launch had failed, SpaceX would not exist.”

In late 2008, the firm was nearly out of cash. Another failure would have ended payroll, closed the Hawthorne factory, and left the Falcon 9 and Dragon programs as unfinished drawings.

The first flight lifted off from Omelek Island on 24 March 2006. Thirty-three seconds later, a corroded aluminum fitting on a fuel line leaked. Kerosene ignited around the Merlin engine, control was lost, and the vehicle came apart. The small DARPA payload, FalconSAT-2, survived the short flight only to land on a storage shed near the pad. Investigators later traced the fitting to a materials mix-up that should never have reached the rocket.

Flight 2, on 21 March 2007, looked far better at first. The first stage burned cleanly and handed off to the Kestrel-powered upper stage. The vehicle crossed 100 kilometers and reached a peak of about 289 kilometers. Then propellant slosh in the second-stage tank started a circular coning motion that grew until the engine shut down. Telemetry faded as the stage tumbled, and SpaceX had reached space but not orbit. Over the next year, the team redesigned everything from the ground up, including tanks, baffles, and the new regeneratively cooled Merlin 1C.

That engine flew on Flight 3 on 2 August 2008. The first stage performed almost perfectly and reached 217 kilometers. After main-engine cutoff, leftover fuel in the cooling channels produced a faint residual thrust, roughly 10 pounds per square inch of chamber pressure. On a Texas test stand, the effect was invisible beneath ambient air pressure. In vacuum it was enough to push the spent first stage back into the second stage after separation. The stages collided, the upper stage spun, and the mission was lost. Musk later said a slightly longer delay before staging would have saved the flight.

Six weeks later, the team assembled Flight 4 from remaining parts and flew it on 28 September 2008 at 23:15 UTC. The payload was Ratsat, a 165-kilogram aluminum mass simulator built in-house. Staging was delayed so residual thrust could decay. The Kestrel ignited, the fairing split away, and nine and a half minutes after liftoff the vehicle was in orbit. After a coast, the second stage restarted, settling into a 621-by-643-kilometer path at 9.35 degrees inclination. Falcon 1 became the first privately developed liquid-fueled rocket to reach Earth orbit. Musk called the insertion “middle of the bull’s-eye.”

SpaceX restores a Falcon 1 rocket for 10th anniversary of first launch success

That success unlocked NASA’s Commercial Resupply Services award later that year. Without it, there would have been no Falcon 9, no reusable first stages, and no Dragon cargo or crew flights to the International Space Station. Launch prices would have remained far higher. Starlink’s constellation would not exist; broadband from low Earth orbit would still be a paper concept.

Ride-share markets, high launch cadence, and the current pace of lunar and Mars hardware would be years behind. Communications, Earth observation, and the cost of putting anything into space would look more like the 2000s than the 2020s.

One extra second of residual thrust in August 2008 would have written a different decade.

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