Connect with us

News

SpaceX delays Starhopper’s first flight a few days despite Raptor preburner test success

According to NASASpaceflight.com, SpaceX's Starhopper successfully completed a Raptor preburner taste on July 15th. A static fire ignition test should follow on July 16th.(NASASpaceflight - bocachicagal)

Published

on

SpaceX has (partially) ignited Starhopper’s freshly-installed Raptor engine, successfully verifying that the engine is ready for its next major test: a full ignition and static firing. Although successful, SpaceX still has some work to do before the vehicle is ready for its first untethered flight(s).

July 15th’s progress is just the latest in a several day-series of preflight tests designed to reduce the likelihood that Starhopper is destroyed over the coming days and (hopefully) weeks. If all goes planned during the awkward Starship prototype’s first foray into hover tests, SpaceX CEO Elon Musk has stated that he will provide an official presentation updating the public on the status of the company’s ever-changing next-generation rocket.

The past week or so of Starhopper preflight testing began with Raptor serial number 6 (SN06) completing the last of a series of acceptance test fires in McGregor, Texas on June 10th. Even on its own, this was a major milestone for the new SpaceX engine: Raptor SN06 was the first of the new, full-scale engines to pass the acceptance test program with flying colors. According to Musk, for the engine to complete those tests so successfully, SpaceX had to solve a challenging bug in which some sort of mechanical resonance (i.e. vibration) damaged or destroyed Raptors SN01-05.

Hours later, the engine began a short ~450 mi (720 km) journey south to Starhopper, located in Boca Chica, Texas. The engine arrived on July 11th and was fully installed on Starhopper by the following evening (July 12th), at which point SpaceX put Starhopper and Raptor through some mild but valuable thrust vector controller (TVC) tests, wiggling the car-sized engine to ensure it can accurately steer the prototype rocket.

Around two days after the above ‘wiggle’ test was successfully completed, SpaceX moved into the next stage, partially fueling Starhopper with liquid methane and oxygen propellant and helium pressurant in what is known in rocketry as a wet dress rehearsal (WDR). The (implicitly) successful WDR was capped off with a duo of what can now safely be concluded were some sort of Raptor test preceding even pre-ignition operations. Whatever the tests were, they appear to have been completed successfully.

That appears to be the case because less than 24 hours after their completion, on July 15th, SpaceX once again began loading Starhopper with propellant and pressurant for a second round of wet testing. This time around, SpaceX got right into more critical Raptor tests once enough propellant was loaded, igniting the engine’s interwoven oxygen and methane preburners.

Starhopper (technically) came alive for the third time ever on July 15th, albeit only partially. SpaceX ignited the engine’s preburners as a precursor to a full static fire, now NET July 16th. (LabPadre – YouTube livestream)

Previously discussed 24 hours ago in a Teslarati article focused on Raptor wiggles and other miscellaneous tests, Raptor is an extremely advanced rocket engine based on a cycle (i.e. how propellant is turned into thrust) known as full-flow staged combustion.

In a staged-combustion engine like Raptor, getting from the supercool liquid oxygen and methane propellant to 200+ tons of thrust is quite literally staged, meaning that the ignition doesn’t happen all at once. Rather, the preburners – essentially their own, unique combustion chambers – ignite an oxygen- or methane-rich mixture, the burning of which produces the gas and pressure that powers the turbines that bring fuel into the main combustion chamber. That fuel then ignites, producing thrust as they exit the engine’s bell-shaped nozzle.

Unintuitively, conditions inside the preburner – hidden away from view – are actually far more intense than the iconic blue, purple, and pink flame that visibly exists Raptor’s nozzle. Much like hot water will cool while traveling through pipes, the superheated gaseous propellant that Raptor ignites to produce thrust will also cool (and thus lose pressure) as it travels from Raptor’s preburner to its main combustion chamber. If the pressure produced in the preburners is too low, Raptor’s thrust will be (roughly speaking) proportionally limited at best. At worst, low pressure in the preburners can trigger a “hard start” or shutdown that could destroy the engine. According to Elon Musk, Raptor’s oxygen preburner thus has the worst of it, operating at pressures as high or higher than 800 bar (11,600 psi, 80 megapascals).”

In full-flow staged combustion (FFSC), even more complexity is added as all propellant that touches the engine must necessarily end up traveling through the main combustion chamber to eke every last ounce of thrust out of the finite propellant a rocket lifts off with. As such, FFSC engines can be about as efficient as the laws of physics allow any given chemical rocket engine to be, at the cost of exceptional complexity and brutally difficult development.

Additionally, FFSC physically requires two separate preburners and then makes things even harder by making each separate preburner (methane and oxygen) depend on each other’s operation for the engine to fully ignite. This means that no individual preburner can be used to kickstart Raptor – instead, SpaceX must somehow spin the turbopumps that feed propellant into each preburner with some separate system. This is all just to emphasize the fact that Raptor’s ignition sequence is a spectacularly complex orchestra of valves, spark plugs, sensors, and magic. This is why it’s valuable for Raptor to test its preburner system independently of an actual ignition test, at least as long as the engine is still in the development stages.

A Raptor engine is pictured here during a static fire test in McGregor, Texas. (SpaceX)

According to NASASpaceflight.com managing editor Chris Bergin, what this practically translates to is a minor Starhopper hover test delay of 1-2 days, while the static fire has also been pushed roughly 24 hours from July 15th to July 16th. If that full static fire produces lots of happy data, Starhopper could be cleared for a hover test debut attempt as early as Wednesday or Thursday (July 17/18).

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

Musk’s massive Terafab project will get final location soon

Published

on

Credit: SpaceX

Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.

“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.

Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry

Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.

The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.

In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.

However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.

Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.

Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.

“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”

He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”

Continue Reading

News

Elon Musk reveals SpaceX performed secret Starship test on Flight 13

Published

on

Credit: SpaceX

SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.

Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.

All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.

However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.

Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:

SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.

Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.

The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.

Continue Reading

Elon Musk

Tesla FSD takes owner on a 20,000+ mile joy ride

Tesla owner David Moss just pushed his intervention free FSD streak past 20,000 miles total.

Published

on

By

Tesla FSD 14.3 [Credit: TESLARATI)

Tesla Model 3 owner David Moss has spent the better part of eight months turning his vehicle into a rolling stress test for Full Self-Driving, and this week he pushed his single, continuous FSD streak past 20,000 miles without a human intervening.

Moss, a Tacoma, Washington resident who sells LiDAR scanning equipment for a living, first drew wide attention in December 2025 when he logged 10,000 consecutive miles on FSD v14.2. Days later he drove from the Tesla Diner in Los Angeles to Myrtle Beach, South Carolina, covering 2,732 miles in two days and 20 hours with zero disengagements, the first verified coast to coast autonomous drive in Tesla’s history. Tesla even featured the trip as an official customer story in March. That original streak eventually reached 12,961 miles across 30 states before ending in rural Wisconsin in January, when snow and single digit temperatures forced Moss to take over.

Tesla FSD successfully completes full coast-to-coast drive with zero interventions

He started over, and this run has gone further. In late May, Moss drove 3,760 miles across Canada with two companions, from Horseshoe Bay in Vancouver to a Tesla showroom in Halifax, again without a single intervention, a trip Tesla AI software VP Ashok Elluswamy publicly congratulated him for on X. In June, he pushed the same unbroken streak south, aiming to link the Canadian border to the Mexican border, and crossed 10,000 miles on Tesla’s newly added in car streak counter along the way, the first driver to do so since Tesla began showing confetti animations for the feature.


It’s worth noting that every mile is logged through the FSD Database, a community run tracker built by Tesla influencer Omar Qazi, well known as @WholeMars on X, that pulls telemetry straight from the car and records disengagements down to a tenth of a mile. That verification is what separates Moss’s numbers from casual claims on social media.

The streak itself is a fairly recent addition to Tesla’s software. FSD v14.2 introduced a Self Driving Stats panel tracking the ratio of autonomous to manual miles, and v14.3.4 added the live streak counter in June, which resets the moment a driver brakes, wrenches the wheel or cancels navigation. Reaching 20,000 miles on that counter means a single Tesla drove itself through countless highways, city grids, construction zones and Supercharger stalls without a single reset.

Moss has said the goal was never to set a record for its own sake, but to show, mile by verified mile, what the software can already do.

Continue Reading