Connect with us

SpaceX

SpaceX’s Starship prototype set for first serious test after Raptor engine installed

Starhopper conducts a propellant tank pressure regulation test on March 18th. (NASASpaceflight - bocachicagal)

Published

on

In concert with South Texas’ Cameron County, SpaceX has officially scheduled the first serious test – requiring temporary road closures – of its Starship prototype, unofficially nicknamed ‘Starhopper’ in light of its ultimate goal of performing low-altitude, low-velocity hop tests.

SpaceX technicians have already successfully completed a number of unspecified tanking tests – likely with chemically neutral liquid nitrogen – and completed acceptance and installation of Raptor serial number 02 (SN02), setting the stage for the giant testbed’s first flight-critical tests. Now set to occur between 10am and 4pm local time (8am2pm Pacific, 15:00-21:00 UTC), that test debut will likely see Starhopper topped to the brim with liquid methane and oxygen propellant for the first time, potentially transitioning into the first BFR-integrated Raptor static fire test.

Scarcely seven days after the engine’s arrival in Boca Chica, SpaceX technicians completed the first-ever installation of a flight-ready Raptor – SN02 – on a full-scale BFR prototype known as Starhopper. Aside from marking a major symbolic milestone for the company’s next-generation rocket development program, the installation of a functional rocket engine on the first partial-fidelity vehicle prototype means that SpaceX can now enter into a new and critical stage of development: integrated flight testing.

Assuming (hopefully) that SpaceX has yet to conduct actual fueling tests of the Starship prototype without establishing roadblocks and safety perimeters, something that would be an egregious threat to nearby locals, it’s likely that this first major test – much like SpaceX’s established Falcon 9 and Heavy test regime – will involve a process known as a Wet Dress Rehearsal (WDR). A WDR would see Starhopper loaded with liquid methane and oxygen propellant – potentially anywhere from the bare minimum needed to operate a single Raptor to completely filling its tanks – to verify that the prototype’s complex plumbing system and giant tanks are operating nicely together under flight conditions (i.e. cryogenic temperatures, thermal and mechanical stresses, chemical environments, etc.). Much like routine Falcon 9 static fire tests performed both at SpaceX’s McGregor, TX test site and the launch pad, data indicating that the rocket is behaving nominally during the WDR allows the operations team to transition smoothly from a WDR into a captive static fire test, in which the vehicle’s engine(s) are briefly ignited to simulate the first few seconds prior to liftoff.

It’s relatively rare but not unusual for planned Falcon 9 or Heavy static fire tests to end during the WDR phase in cases where the launch team observes data that appears to be less than nominal. SpaceX generally takes a “better safe than sorry” approach to these sorts of operations, swallowing the costs and risk of raising customers’ ire due to delays in order to ensure the highest probability of complete launch success.

For a vehicle as utterly new and alien as Starhopper is to both SpaceX and the aerospace industry as a whole, it’s safe to say that that tendency towards caution will be readily on display throughout these first several tests, at least until the company’s operations technicians and engineers are considerably more familiar with the prototype rocket’s behavior. On the other hand, given just how shoestring the budget of this beast likely is and how rapidly SpaceX managed to go from an empty dirt lot to a hop-test-ready, 30ft/9m-diameter Starship prototype, it’s equally likely that the company – particularly CEO Elon Musk – will accept the increased risk of catastrophic vehicle failures to keep the development program as agile as possible.

According to CEO Elon Musk, this large metal cylinder is actually one of the barrel sections of the first orbital Starship prototype. Workers are welding the sections together outside, rain or shine. (NASASpaceflight – bocachicagal)
Starhopper makes its own clouds during tanking tests on March 14th. (NASASpaceflight – bocachicagal)

As Musk himself frequently and famously is known to say, it’s far better to push hardware to failure during early testing than it is to hold back and risk largely unplanned failures during nominal operations, a lesson that SpaceX itself has learned the hard way several times. One step further, while they are at best undeniably inconvenient and expensive, major vehicle failures during testing can actually be an invaluable source of data that ultimately improves the system as a whole. For BFR, a launch vehicle meant to safely, routinely, and reliably transport as many as 100+ people both around the Earth and solar system, all possible opportunities to learn and improve the system prior to risking the lives of passengers will be an absolute necessity if SpaceX wants to ensure that customers remain willing to trust the company and its spacecraft with their lives.

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

Elon Musk

SpaceX secures FAA approval for 44 annual Starship launches in Florida

The FAA’s environmental review covers up to 44 launches annually, along with 44 Super Heavy booster landings and 44 upper-stage landings.

Published

on

Credit: SpaceX

SpaceX has received environmental approval from the Federal Aviation Administration (FAA) to conduct up to 44 Starship-Super Heavy launches per year from Kennedy Space Center Launch Complex 39A in Florida. 

The decision allows the company to proceed with plans tied to its next-generation launch system and future satellite deployments.

The FAA’s environmental review covers up to 44 launches annually, along with 44 Super Heavy booster landings and 44 upper-stage landings. The approval concludes the agency’s public comment period and outlines required mitigation measures related to noise, emissions, wildlife, and airspace management.

Construction of Starship infrastructure at Launch Complex 39A is nearing completion. The site, previously used for Apollo and space shuttle missions, is transitioning to support Starship operations, as noted in a Florida Today report.

Advertisement

If fully deployed across Kennedy Space Center and nearby Cape Canaveral Space Force Station, Starship activity on the Space Coast could exceed 120 launches annually, excluding tests. Separately, the U.S. Air Force has authorized repurposing Space Launch Complex 37 for potential additional Starship activity, pending further FAA airspace analysis.

The approval supports SpaceX’s long-term strategy, which includes deploying a large constellation of satellites intended to power space-based artificial intelligence data infrastructure. The company has previously indicated that expanded Starship capacity will be central to that effort.

The FAA review identified likely impacts from increased noise, nitrogen oxide emissions, and temporary airspace closures. Commercial flights may experience periodic delays during launch windows. The agency, however, determined these effects would be intermittent and manageable through scheduling, public notification, and worker safety protocols.

Wildlife protections are required under the approval, Florida Today noted. These include lighting controls to protect sea turtles, seasonal monitoring of scrub jays and beach mice, and restrictions on offshore landings to avoid coral reefs and right whale critical habitat. Recovery vessels must also carry trained observers to prevent collisions with protected marine species.

Advertisement
Continue Reading

Elon Musk

Elon Musk reiterates rapid Starship V3 timeline with next launch in sight

Musk shared the update in a brief post on X, writing, “Starship flies again next month.”

Published

on

Credit: SpaceX/X

Elon Musk has confirmed that Starship will fly again next month, reiterating SpaceX’s aggressive timeline for the first launch of its Starship V3 rocket.

Musk shared the update in a brief post on X, writing, “Starship flies again next month.” The CEO’s post was accompanied by a video of Starship’s Super Heavy booster being successfully caught by a launch tower in Starbase, Texas. 

The timeline is notable. In late January, Musk stated that Starship’s next flight, Flight 12, was expected in about six weeks. This placed the expected mission date sometime in March. That estimate aligned with SpaceX’s earlier statement that Starship’s 12th flight test “remains targeted for the first quarter of 2026.”

If the vehicle does indeed fly next month, it would mark the debut of Starship V3, the upgraded platform expected to feature the rocket’s new Raptor V3 engines.

Advertisement

Raptor V3 is designed to deliver significantly higher thrust than earlier versions while reducing cost and weight. Starship V3 itself is expected to be optimized for manufacturability, a critical step if SpaceX intends to scale production toward frequent launches for Starlink, lunar missions, and eventually Mars.

Starship V3 is widely viewed as the version that transitions the program from experimental testing to true operational scaling. Previous iterations have completed multiple integrated flight tests, with mixed outcomes but steady progress. Expectations are high that SpaceX is now working on Starship’s refinement.

An aggressive launch schedule supports several priorities at once. It advances Starlink’s next-generation satellite deployment, supports NASA’s lunar ambitions under Artemis, and keeps SpaceX on track for its longer-term Moon and Mars objectives.

Continue Reading

Elon Musk

Musk company boycott proposal at City Council meeting gets weird and ironic

The City of Davis in California held a weekly city council meeting on Tuesday, where it voted on a proposal to ban Musk-operated companies. It got weird and ironic.

Published

on

Credit: Grok

A city council meeting in California that proposed banning the entry of new contracts with companies controlled by Elon Musk got weird and ironic on Tuesday night after councilmembers were forced to admit some of the entities would benefit the community.

The City of Davis in California held a weekly city council meeting on Tuesday, where it voted on a proposal called “Resolution Ending Engagement With Elon Musk-Controlled Companies and To Encourage CalPERS To Divest Stock In These Companies.”

The proposal claimed that Musk ” has used his influence and corporate platforms to promote political ideologies and activities that threaten democratic norms and institutions, including campaign finance activities that raise ethical and legal concerns.”

We reported on it on Tuesday before the meeting:

California city weighs banning Elon Musk companies like Tesla and SpaceX

However, the meeting is now published online, and it truly got strange.

While it was supported by various members of the community, you could truly tell who was completely misinformed about the influence of Musk’s companies, their current status from an economic and competitive standpoint, and how much some of Musk’s companies’ projects benefit the community.

City Council Member Admits Starlink is Helpful

One City Council member was forced to admit that Starlink, the satellite internet project established by Musk’s SpaceX, was beneficial to the community because the emergency response system utilized it for EMS, Fire, and Police communications in the event of a power outage.

After public comments were heard, councilmembers amended some of the language in the proposal to not include Starlink because of its benefits to public safety.

One community member even said, “There should be exceptions to the rule.”

Community Members Report Out of Touch Mainstream Media Narratives

Many community members very obviously read big bold headlines about how horribly Tesla is performing in terms of electric vehicles. Many pointed to “labor intimidation” tactics being used at the company’s Fremont Factory, racial discrimination lawsuits, and Musk’s political involvement as clear-cut reasons why Davis should not consider his companies for future contracts.

However, it was interesting to hear some of them speak, very obviously out of touch with reality.

Musk has encouraged unions to propose organizing at the Fremont Factory, stating that many employees would not be on board because they are already treated very well. In 2022, he invited Union leaders to come to Fremont “at their convenience.”

The UAW never took the opportunity.

Some have argued that Tesla prevented pro-union clothing at Fremont, which it did for safety reasons. An appeals court sided with Tesla, stating that the company had a right to enforce work uniforms to ensure employee safety.

Another community member said that Tesla was losing market share in the U.S. due to growing competition from legacy automakers.

“Plus, these existing auto companies have learned a lot from what Tesla has done,” she said. Interestingly, Ford, General Motors, and Stellantis have all pulled back from their EV ambitions significantly. All three took billions in financial hits.

One Resident Crosses a Line

One resident’s time at the podium included this:

He was admonished by City Council member Bapu Vaitla, who said his actions were offensive. The two sparred verbally for a few seconds before their argument ended.

City Council Vote Result

Ultimately, the City of Davis chose to pass the motion, but they also amended it to exclude Starlink because of its emergency system benefits.

Continue Reading