Connect with us

News

SpaceX wiggles Starhopper’s Raptor engine, tests parts ahead of hover test debut

Repeating a test conducted in June with Raptor SN04, SpaceX tested Starhopper and Raptor SN06's thrust vectoring capabilities on July 12th. (NASASpaceflight - bocachicagal)

Published

on

On the evening of July 12th, SpaceX technicians put Starhopper’s freshly-installed Raptor – serial number 06 (SN06) – through a simple but decidedly entertaining test, effectively wiggling the engine in circles.

Designed to verify that Raptor’s thrust vectoring capabilities are in order and ensure that Starhopper and the engine are properly communicating, the wiggle test is a small but critical part of pre-flight acceptance and a good indicator that the low-fidelity Starship prototype is nearing its first hover test(s). Roughly 48 hours after a successful series of wiggles, Starhopper and Raptor proceeded into the next stage of pre-flight acceptance, likely the final more step before a tethered static fire.

Routine for all Falcon rockets, SpaceX’s exceptionally rigorous practice of static firing all hardware at least once (and often several times) before launch has unsurprisingly held firm as the company proceeds towards integrated Starhopper and Starship flight tests. Despite the fact that Raptor SN06 completed a static fire as recently July 10th, SpaceX will very likely put Starhopper and its newly-installed Raptor through yet another pre-flight static fire, perhaps its fourth or fifth test this month.

Although it would undoubtedly be easier, cheaper, and faster to skip that post-delivery static fire, it will simultaneously lower the risk of Raptor failing mid-flight and verify that Starhopper itself is healthy and ready for untethered hovering. Although SpaceX could likely live without Starhopper in the event that it’s lost during flight-testing, any failure capable of destroying the vehicle itself is at least as capable of severely damaging or completely destroying the spartan but still expansive test and launch facilities the company built over the course of several months.

SpaceX has been hard at work gradually building, expanding, and upgrading its South Texas launch facilities since December 2018. (NASASpaceflight – bocachicagal, 04/27/2019)

Would you like some testing with your testing?

Follow July 12th’s nighttime Raptor wiggle test, July 13th was mainly quiet and filled with inspections of Starhopper, Raptor, and other various work. The day after, however, SpaceX proceeded through several hours of propellant loading, ending with what looked like less energetic versions of the Raptor preburner ignition tests Starhopper previously performed with Raptor SN02.

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.

The first obvious test occurred around 7:30pm CT, July 14th. (LabPadre)
The second obvious test followed around 8:50 pm CT. (LabPadre)

Although the fireworks are so subtle that they are easily missed, the conditions inside the preburner – hidden away from view – are actually far more intense than the iconic blue, purple, and pink flame that exists Raptor’s nozzle. This is because the preburners have to nurture the conditions necessary for the pumps they power to fuel the main combustion chamber. 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 the main combustion chamber.

Thus, if the head 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 completely prevent Raptor from starting and running stably and can even trigger a “hard start” or shutdown that could damage or destroy the engine. As such, to preburners fundamentally have to operate at higher chamber pressures (and thus higher temperatures) than the main combustion chamber (the big firey bit at the end). According to Elon Musk, Raptor’s oxygen preburner has the worst of it, operating at pressures as high or higher than 800 bar (11,600 psi, 80 megapascals).

Coincidentally, this is roughly equivalent to the pressure at the bottom of the Pacific Ocean.

Starhopper and Raptor seen on the afternoon of July 14th, preparing for an evening of testing. (NASASpaceflight – bocachicagal)

In short, preburner testing is no less critical than full-on static fire testing with an engine like Raptor. July 14th’s test was also made doubly efficient due to the fact that preburner testing requires liquid propellant, which effectively makes the whole test a wet dress rehearsal (WDR) even before any engine ignition or partial ignition is involved. Per SpaceX moving from propellant loading to preburner/turbine testing, Starhopper is almost certainly healthy and operating as expected, an excellent sign that the ungainly vessel may be ready for a static fire of Raptor as early as 2pm CT, July 15th.

The memes, oh, the memes.

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

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

on

Credit: Tesla

Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.

The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:

“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”

We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.

Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.

Tesla Roadster is available for order once again following brief hold

The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.

The Tesla Roadster will be unveiled in Waco, Texas.

Continue Reading

Elon Musk

SpaceX turned a heralding moment for Starship into its greatest

Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.

Published

on

By

SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.

The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.

Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.

That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.

The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.

SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.

Continue Reading