Connect with us

News

SpaceX’s second Starship hop imminent after Raptor static fire test

This photo of Starship SN5's August 4th hop debut is effectively exactly what SN6 went through - short of actually lifting off - on August 23rd. (SpaceX)

Published

on

SpaceX has successfully fired up a new Starship prototype’s Raptor engine, putting the company on track for its second Starship hop test as soon as this week.

The milestone comes not long after SpaceX Starship serial number 6 (SN6) completed its first cryogenic proof, a pressure test with liquid nitrogen (LN2) used to safely verify the structural integrity of tanks (and rockets, in particular). Measuring 9m (30 ft) wide and some 30m (~100 ft) tall, SpaceX rolled Starship SN6 from its Boca Chica, Texas factory to a nearby test and launch facility on August 11th and wrapped up its first acceptance test on August 16th.

Now, just seven days after its cryo proof, SpaceX has installed a new Raptor engine (SN29), prepared SN6 for a much riskier round of tests, and completed a static fire with said engine, leaving just one major step between the Starship and its hop debut. Of course, the process still had its fair share of hiccups.

SpaceX’s first SN6 static fire test window – published by Cameron County in the form of road closure notices – was set for 8 am to 8 pm CDT (UTC-5), August 23rd a few days after the Starship’s cryo proof. The first test attempt began around 9:30 am but was aborted soon after as SpaceX employees returned to the launch pad to (presumably) troubleshoot. The second attempt began around 2:30 pm, leaving a little less than half the test window available.

Attempt #2 very nearly managed to extract a static fire, aborting possibly a second or less before Raptor ignition around 3:41 pm. Once again, SpaceX teams returned to the pad after Starship was detanked and safed, briefly inspecting the general location of the rocket’s Raptor engine before once again clearing the pad around 6:30 pm. At long last, Starship SN6 began a smooth and fast flow that culminated in the ignition of Raptor SN29 around 7:45 pm, just 15 minutes before the end of SpaceX’s test window.

SpaceX installed Raptor SN29 on Starship SN6 on August 18th. (NASASpaceflight – bocachicagal)
Five days later, that engine came to life as part of a Starship prototype for the first time. (LabPadre)

As with all SpaceX static fires, engineers must still analyze the data produced – and possibly inspect pad or rocket hardware – to verify vehicle health before proceeding into launch operations. Unlike all other SpaceX static fires, the company doesn’t announce the results of those tests – nor the solidified launch window – during prototype development programs. In the context of iterative aerospace development, while there may be such a thing as a “good” or “bad” test, all tests – as long as they’re performed safely and produce a large quantity of usable data – are essentially successful.

As such, it’s likely for the best that SpaceX doesn’t put the public focus on the “success” of any given test. Still, it means that unofficial educated guesses are typically the only way to determine the results of any given test and how those results impact the next steps. For SN6, the very broad-strokes conclusions one can draw from unofficial livestreams suggest that the Starship’s first Raptor static fire was a success. Assuming that the unknown cause(s) of the day’s two prior aborts were minor and easily rectified, SpaceX is likely exactly on schedule for Starship SN6’s first hop attempt.

Advertisement
-

SN6’s first flight is expected to be an almost identical copy of Starship SN5’s highly successful August 4th debut, following the same 150m (~500 ft) parabolic trajectory. Filed before SN6’s August 23rd static fire, SpaceX has penciled in Friday, August 28th for Starship SN6’s own hop debut. Thanks to the fact that SpaceX was able to complete both SN6’s cryo proof and static fire on the first day of their respective test windows, August 28th is likely well within reach. Stay tuned for updates as Starship SN6’s hop debut schedule solidifies.

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