Connect with us

News

Starhopper update: SpaceX’s ungainly Starship testbed survives night of fireballs, Raptor testing

Despite what looked like several decidedly off-nominal fires after an apparently successful Raptor static fire, Starhopper looks unscathed in the morning light. (NASASpaceflight - bocachicagal, 07/17/2019)

Published

on

SpaceX’s Starhopper appears to have come out the other end of an eventful night of fires, fireballs, and Raptor testing completely unscathed, although – as with all things rocketry – there is vastly more than meets the eye.

However, signs point towards Starhopper being almost entirely unharmed by its brief voyage inside a fireball – even if Boca Chica’s fire suppression system got a thorough workout and many a SpaceX onlooker likely suffered a partial heart attack. For the time being, it’s safe to assume that Starhopper’s planned flight activities have been indefinitely delayed as SpaceX technicians analyze the vehicle and engineers work to mitigate or completely prevent major fires from recurring.

According to NASASpaceflight.com’s well-informed sources, despite the spectacular fireworks that followed Raptor’s own impressive display, the engine’s static fire test was a full success – at least in terms of data produced by the engine. The large fireball was attributed to the ignition of a large methane vent that followed soon after Raptor’s shutdown.

For now, this means that Starhopper’s untethered flight test and hover test debut should not be expected to occur for several days, even in the event that the rocket, pad, and Raptor engine all made it through their July 16th ordeal completely undamaged. If there is zero damage, this accident will serve as an unfortunate but useful demonstration of a true stainless steel rocket’s theoretically exceptional sturdiness and heat resistance.

It may seem more than a little ironic, but it’s likely less than a coincidence. If it comes to fruition as a truly functional, orbit-capable steel rocket, spaceship, and upper stage, Starship/Super Heavy will exist in their shiny, steel forms almost entirely because of the unintuitive tradeoffs that could theoretically make heat-resistant-but-dense steel more efficient than a ship built out of ultra-light carbon composites. If Starhopper’s newly demonstrated resilience is anything to go by, a very happy side-effect of that efficient, heat-resistant steel could be an almost unprecedented resilience in the face of serious fires, fireballs, and other fire-related anomalies.

https://www.youtube.com/watch?v=heguSQRla-Q

For almost any other rocket, exposure – at least outside of the engine section – to large fireballs and quite literally having parts burning while motionless on the ground are deeply, deeply worrisome things and risk a major vehicle malfunction – potentially up to and including a catastrophic failure (i.e. explosion). ULA’s Delta IV rocket family is famous for self-immolating during ignition and liftoff, a minimal concern to the rockets’ thin, aluminum tankage thanks to several inches of thick, fire-retardant foam insulation.

For a rocket like Falcon 9, almost entirely (by surface area) composed of thin, aluminum propellant tanks and carbon composite structures, there is a constant struggle to balance the vehicle’s extreme performance with the low melting point of its primary structures (~720 degrees C). The 301-series stainless steel Starhopper and Starship(s) are built out of has a melting point of ~1400 degrees C, nearly double aluminum-lithium alloys.

~12 hours later, Starhopper and Raptor SN06 bare no visible scars after pushing through multiple fires and a large fireball on July 16th. (NASASpaceflight – bocachicagal, 07/17/2019)

In short, while it boggles the mind and is decidedly unintuitive to anyone who watched July 16th’s live coverage of the static fire, it’s actually not a huge surprise that Starhopper has suffered serious fire-related anomalies with essentially zero visible damage. In fact, it’s almost impossible to tell that anything at all happened, let alone discerning some subtle sign(s) of damage incurred by fires. It may sound ironic to say so, but rockets and fire just do not tend to like each other much at all.

Time will tell if Starhopper and Raptor are in as good a condition as they appear to be.

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

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