Connect with us

News

SpaceX scraps Starship SN8 wreckage, clears landing zone for next launch

Although efforts were made to save the historic hardware, Starship SN8's wreckage is no more. (NASASpaceflight - bocachicagal)

Published

on

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.

The beginning and end of Starship SN8’s highly successful but ill-fated launch debut. (Richard Angle)

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.

Advertisement
-->
Thanks to a quick, temporary fix, Starship SN9’s own 12.5 km launch debut remains on track to despite SN8’s failed landing. (NASASpaceflight – bocachicagal)
SN9 appeared to complete a cryogenic proof test on December 29th and could attempt its first static fire as early as January 6th. (NASASpaceflight – bocachicagal)

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.

Although SpaceX couldn’t fully salvage SN8’s nosecone wreckage, it did snag a mostly intact flap before scrapping the rest. (NASASpaceflight – bocachicagal)

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.

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

Tesla CEO Elon Musk sends rivals dire warning about Full Self-Driving

Published

on

Credit: Tesla

Tesla CEO Elon Musk revealed today on the social media platform X that legacy automakers, such as Ford, General Motors, and Stellantis, do not want to license the company’s Full Self-Driving suite, at least not without a long list of their own terms.

“I’ve tried to warn them and even offered to license Tesla FSD, but they don’t want it! Crazy,” Musk said on X. “When legacy auto does occasionally reach out, they tepidly discuss implementing FSD for a tiny program in 5 years with unworkable requirements for Tesla, so pointless.”

Musk made the remark in response to a note we wrote about earlier today from Melius Research, in which analyst Rob Wertheimer said, “Our point is not that Tesla is at risk, it’s that everybody else is,” in terms of autonomy and self-driving development.

Wertheimer believes there are hundreds of billions of dollars in value headed toward Tesla’s way because of its prowess with FSD.

A few years ago, Musk first remarked that Tesla was in early talks with one legacy automaker regarding licensing Full Self-Driving for its vehicles. Tesla never confirmed which company it was, but given Musk’s ongoing talks with Ford CEO Jim Farley at the time, it seemed the Detroit-based automaker was the likely suspect.

Tesla’s Elon Musk reiterates FSD licensing offer for other automakers

Ford has been perhaps the most aggressive legacy automaker in terms of its EV efforts, but it recently scaled back its electric offensive due to profitability issues and weak demand. It simply was not making enough vehicles, nor selling the volume needed to turn a profit.

Musk truly believes that many of the companies that turn their backs on FSD now will suffer in the future, especially considering the increased chance it could be a parallel to what has happened with EV efforts for many of these companies.

Unfortunately, they got started too late and are now playing catch-up with Tesla, XPeng, BYD, and the other dominating forces in EVs across the globe.

Continue Reading

News

Tesla backtracks on strange Nav feature after numerous complaints

Published

on

Credit: Tesla

Tesla is backtracking on a strange adjustment it made to its in-car Navigation feature after numerous complaints from owners convinced the company to make a change.

Tesla’s in-car Navigation is catered to its vehicles, as it routes Supercharging stops and preps your vehicle for charging with preconditioning. It is also very intuitive, and features other things like weather radar and a detailed map outlining points of interest.

However, a recent change to the Navigation by Tesla did not go unnoticed, and owners were really upset about it.

Tesla’s Navigation gets huge improvement with simple update

For trips that required multiple Supercharger stops, Tesla decided to implement a naming change, which did not show the city or state of each charging stop. Instead, it just showed the business where the Supercharger was located, giving many owners an unwelcome surprise.

However, Tesla’s Director of Supercharging, Max de Zegher, admitted the update was a “big mistake on our end,” and made a change that rolled out within 24 hours:

The lack of a name for the city where a Supercharging stop would be made caused some confusion for owners in the short term. Some drivers argued that it was more difficult to make stops at some familiar locations that were special to them. Others were not too keen on not knowing where they were going to be along their trip.

Tesla was quick to scramble to resolve this issue, and it did a great job of rolling it out in an expedited manner, as de Zegher said that most in-car touch screens would notice the fix within one day of the change being rolled out.

Additionally, there will be even more improvements in December, as Tesla plans to show the common name/amenity below the site name as well, which will give people a better idea of what to expect when they arrive at a Supercharger.

Continue Reading

News

Dutch regulator RDW confirms Tesla FSD February 2026 target

The regulator emphasized that safety, not public pressure, will decide whether FSD receives authorization for use in Europe.

Published

on

The Dutch vehicle authority RDW responded to Tesla’s recent updates about its efforts to bring Full Self-Driving (Supervised) in Europe, confirming that February 2026 remains the target month for Tesla to demonstrate regulatory compliance. 

While acknowledging the tentative schedule with Tesla, the regulator emphasized that safety, not public pressure, will decide whether FSD receives authorization for use in Europe.

RDW confirms 2026 target, warns Feb 2026 timeline is not guaranteed

In its response, which was posted on its official website, the RDW clarified that it does not disclose details about ongoing manufacturer applications due to competitive sensitivity. However, the agency confirmed that both parties have agreed on a February 2026 window during which Tesla is expected to show that FSD (Supervised) can meet required safety and compliance standards. Whether Tesla can satisfy those conditions within the timeline “remains to be seen,” RDW added.

RDW also directly addressed Tesla’s social media request encouraging drivers to contact the regulator to express support. While thanking those who already reached out, RDW asked the public to stop contacting them, noting these messages burden customer-service resources and have no influence on the approval process. 

“In the message on X, Tesla calls on Tesla drivers to thank the RDW and to express their enthusiasm about this planning to us by contacting us. We thank everyone who has already done so, and would like to ask everyone not to contact us about this. It takes up unnecessary time for our customer service. Moreover, this will have no influence on whether or not the planning is met,” the RDW wrote. 

Advertisement
-->

The RDW shares insights on EU approval requirements

The RDW further outlined how new technology enters the European market when no existing legislation directly covers it. Under EU Regulation 2018/858, a manufacturer may seek an exemption for unregulated features such as advanced driver assistance systems. The process requires a Member State, in this case the Netherlands, to submit a formal request to the European Commission on the manufacturer’s behalf.

Approval then moves to a committee vote. A majority in favor would grant EU-wide authorization, allowing the technology across all Member States. If the vote fails, the exemption is valid only within the Netherlands, and individual countries must decide whether to accept it independently.

Before any exemption request can be filed, Tesla must complete a comprehensive type-approval process with the RDW, including controlled on-road testing. Provided that FSD Supervised passes these regulatory evaluations, the exemption could be submitted for broader EU consideration.

Continue Reading