News
SpaceX scraps Starship SN8 wreckage, clears landing zone for next launch
In spite of tentative plans for preservation, SpaceX has fully scrapped the wreckage of the first high-altitude Starship prototype, clearing the landing zone it impacted for its successor’s imminent launch debut.
Known as serial number 8 or SN8, the Starship prototype was the first of any kind to fly beyond 150 meters (~500 ft), reaching an altitude of 12.5 km (~7.8 mi) on December 9th during its breathtaking launch debut. In an unexpected twist, SpaceX kept Starship SN8’s thrust to weight ratio as low as possible, stretching what could have been a two or three-minute test into an almost seven-minute ordeal with three consecutive Raptor engine cutoffs during the ascent.
At apogee, SN8 used cold gas thrusters to flip into a belly-down orientation and free-fell ~95% of the way back to Earth before igniting two of its three Raptor engines, performing a wild powered flip back into a vertical landing position and nearly securing a soft landing. Unfortunately, around 10-20 seconds before that planned landing, what Musk later described as low methane header tank pressure starved the Starship’s engines of fuel and more or less cut all appreciable thrust, causing SN8 to reach its landing zone traveling about 40 m/s (~90 mph) too fast. The rocket impacted the concrete pad, crumpled, and exploded.
By all accounts, success was one of the less likely outcomes SpaceX expected from SN8’s high-altitude debut, with Musk himself estimating the odds of total success to be just 33%. Additionally, Starship SN8 effectively made it all the way to a low-speed landing regime that Starships SN5 and SN6 all but flawlessly demonstrated with back-to-back 150m hops and landings in August and September 2020.

In other words, despite the explosive end, SN8’s high-altitude launch debut was a spectacular success for SpaceX’s Starship program – possibly even preferable to a perfect landing given that it uncovered an unexpected issue with fuel tank pressurization. Beyond the landing failure, the Starship checked every single box on SpaceX’s test flight list, successfully debuting multiple Raptors, demonstrating multiple in-flight engine shutdowns and engine relights; proving that an unprecedented ‘skydiver-style’ landing maneuver is possible and viable; and successfully testing Starship’s ability to control itself in that bellyflop orientation with thrusters and four massive flaps.
Speaking in a recent interview with Ars Technica, in the words of pragmatic SpaceX COO and President Gwynne Shotwell, SN8’s launch debut “de-risked [the Starship] program pretty massively.” According to Musk, SpaceX engineers were quickly able to determine why Starship SN8’s methane header tank was unable to maintain the fuel flow (pressure) needed for Raptor’s landing burn(s) and quickly implemented a solution.


Instead of pressurizing autogenously with methane gas, Starship SN9 will use helium to pressurize its fuel header tank, serving as a temporary fix while SpaceX determines what changes need to be made to get rid of that helium crutch. Landing pad now cleared of Starship remains and SN8’s impact crater more or less repaired, the only thing standing between Starship SN9 and its own 12.5 km launch debut is a triple-Raptor static fire test. Originally expected as early as January 4th, SpaceX never made it more than a few minutes into the attempt, while a backup window on January 5th was canceled later that evening. The test could now occur no earlier than (NET) Wednesday, January 6th.


Thankfully, although SpaceX was unable to save the entirety of Starship SN8’s wrecked nose section, the company did manage to extract a largely intact nose flap. The rest of the remains were scrapped on site and trucked away but it’s possible that certain significant components of SN8 – particularly the recovered flap – will eventually find themselves on display at one or more SpaceX facilities.
Lifestyle
Watch Tesla’s “guardian angel” FSD feature take over for collision evasion
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 new Automatic Collision Evasion feature worked flawlessly! FSD reengaged itself just as I was about to hit a curb.
Kudos @Tesla_AI team! 👏 pic.twitter.com/Fbp15HhpL2
— Spencer (@scotsrule08) September 28, 2026
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.
News
Tesla Roadster event gets delayed due to unfavorable weather
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.”
Roadster event update
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…
— Tesla (@Tesla) September 28, 2026
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.
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.
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.
Splashdown confirmed. Congratulations to the entire SpaceX team on the first orbital flight of Starship! pic.twitter.com/urjmiwnvNl
— SpaceX (@SpaceX) September 28, 2026
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.
Starship’s 14th flight is set to launch on Monday, Sept 28. The 75-minute launch window opens at 7:15 a.m. CT. Live coverage of the mission starts ~35 minutes before launch → https://t.co/uQKQvgaTmJ
— SpaceX (@SpaceX) September 27, 2026