Connect with us

News

SpaceX’s Elon Musk hints at “notable” Starship changes, explains static fire anomaly

Starship SN8; humans for scale. (NASASpaceflight - bocachicagal)

Published

on

CEO Elon Musk has offered an explanation for SpaceX’s recent Starship static fire anomaly and says that an overview of the next-generation rocket development program will be delayed to account for some “notable” design changes.

Over the last several months, Musk has promised to do one of his (thus far) usual annual Starship updates, either in the form of a presentation in South Texas, an article published on SpaceX’s website, or both. Originally expected in September or October, the CEO’s tentative schedules have come and gone several times. Simultaneously, however, SpaceX has been preparing Starship serial number 8 (SN8) for a range of crucial tests and Starship program firsts, recently culminating in a successful cryogenic proof test, multiple wet dress rehearsals (WDRs), nosecone installation, the first triple-Raptor static fire test, engine tests using smaller ‘header’ tanks, and more.

Unfortunately for SN8, the most recent Raptor engine header static fire – drawing propellant from two small internal tanks mainly used for landing burns – did not go according to plan, resulting in some kind of high-temperature fire and severing Starship’s hydraulic systems. For SpaceX test controllers, that meant a total loss of control of most vehicle valves and pressurization systems, essentially putting one of Starship SN8’s header tanks through an unplanned pressure and failsafe test. In the days since, what exactly caused that unfortunate failure has been the subject of a great deal of discussion – discussion that can finally be put to rest with new information from Musk himself.

In a surprise, SpaceX had apparently decided to add a failsafe to Starship SN8’s new nose section, installing what is known as a burst disk – effectively an automatic single-use valve. Once the upper (liquid oxygen) header tank reached dangerous pressures, the force of that pressure broke the seal, allowing the rocket to vent excess pressure and avoid what would have otherwise been a potentially catastrophic explosion.

The cause of that near-miss, according to Elon Musk, was as simple as debris kicked up during the Starship SN8 Raptor engine static fire directly prior. Producing up to 200 metric tons (~450,000 lbf) of thrust and an exhaust stream traveling some 3.3 kilometers per second (2 mi/s, Mach ~10), Musk says that Raptor tore apart a special ceramic coating covering the concrete directly beneath Starship SN8. Likely accelerated to extreme velocities in milliseconds, shards of that coating reportedly “severed [an] avionics cable, causing [a] bad [Raptor engine shutdown].”

Raptor engine SN42 took SN32’s place after debris caused damage when the engine attempted to shut down. (NASASpaceflight – bocachicagal)

Prior to Musk’s comments, SpaceX technicians had already removed on of SN8’s three Raptors – SN32 – on November 14th and replaced it with Raptor SN42 on November 16th, effectively confirming that any damage suffered by Starship’s engine section was easily repairable. It’s unclear how exactly a single severed cable could result in a Raptor engine seemingly dripping molten metal but regardless of the cause, the fix appears to have been a quick one.

A second Starship test stand and the beginnings of a Super Heavy-class orbital launch mount are pictured to the left and right of prototype SN8. (NASASpaceflight – bocachicagal)

In response to the anomaly, Musk says that Starship avionics cables will ultimately be routed inside steel pipes to shield them from debris, while “water-cooled steel pipes” will be added to the launch pad to help limit the damage Raptors can cause. Perhaps as a partial result of SN8’s troubles at the launch pad, Musk says that his Starship blog post will have to wait, as SpaceX “[may be] making some notable changes” to the launch vehicle.

Prior to Starship SN8’s failed November 12th Raptor test, SpaceX was expected to attempt three consecutive static fires before clearing the rocket for an ambitious 15 km (9.5 mi) flight test. One of those static fires had already been completed on November 10th and it’s unclear if SpaceX’s SN8 test plan has remained unchanged or if the static fire counter has been effectively reset. Either way, barring more surprises, there’s still a definite possibility that Starship SN8 will be ready for its launch debut by the end of November and an even better chance that it will launch some time between now and 2021. Stay tuned for updates!

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

News

SpaceX completes another secret Pentagon launch, adding to suspected Starshield buildout

SpaceX launched the classified USSF-385 mission from Vandenberg, landing its booster on a tenth flight.

Published

on

By

US Golden Dome space defense system (Concept render by Grok)

SpaceX launched another classified mission for the U.S. Space Force from California early Saturday morning, and the Falcon 9 booster that carried it landed on a drone ship in the Pacific for the tenth time. The USSF-385 mission lifted off from Space Launch Complex 4E at Vandenberg Space Force Base at 7:00 a.m. PT.

Booster B1100 touched down on Of Course I Still Love You roughly eight and a half minutes after liftoff. It was the booster’s tenth flight and tenth successful landing, following the NROL-95 national security mission and eight Starlink launches. Its previous flight, a Starlink Group 15 mission on August 22, came just 35 days earlier. SpaceX ended its livestream shortly after the landing, which is standard for classified payloads, and neither the company nor the Space Force has said what the rocket carried.

USSF-385 is the fourth Space Force launch from the same Vandenberg pad in roughly six weeks, following USSF-366 on August 15, USSF-153 on September 10, and USSF-259 on September 17. When SpaceX flew USSF-366 in August, independent trackers noted that the rocket’s stage drop zones matched SpaceX’s Starlink Group 15 missions, pointing to Starshield, the government version of the Starlink satellite bus. The Space Force later cataloged 23 satellites after both USSF-366 and USSF-153, while USSF-259 placed 17 satellites into a different orbital plane, per KeepTrack. Launch databases describe USSF-385 the same way, though the payload remains officially unidentified.

Starlink’s Starshield wins contract with US Space Force

The cadence lines up with the contracts, because in July, the Space Force awarded SpaceX $1.6 billion in task orders for 18 Falcon 9 missions from Vandenberg through the end of 2027. SpaceX also holds contracts to build pieces of that same network, which pushed its Pentagon contract total for 2026 past $8 billion.

Saturday’s flight was also the sixth and final Falcon 9 launch from Vandenberg in September, according to Spaceflight Now, while only one Falcon 9 flew from the East Coast this month as SpaceX shifts its Florida infrastructure toward Starship. Launch trackers list it as SpaceX’s 112th mission of 2026 and the 108th Falcon 9 flight of the year, with SLC-4E turned around about six and a half days after its previous launch.

The West Coast pad will not stay quiet for long, considering SpaceX has another Starlink mission scheduled from SLC-4E on September 30. Meanwhile, in Texas, the company is two days away from Starship Flight 14, which is targeting Monday at 7:15 a.m. CT for the vehicle’s first attempt to reach orbit.

Continue Reading

News

Tesla hints at new Roadster design in surprise clip

Tesla ended its Semi event with a Roadster teaser revealing a new front light bar.

Published

on

By

Tesla Battery Day event (Credit: Ryan McCaffrey/Twitter)

Tesla closed out its Semi event in Nevada on Thursday night with a nod to its own history, dropping a short Roadster teaser that suggests the production car will look noticeably different from the prototype first shown in 2017.

“We can’t have a Semi event without the Roadster,” Tesla engineering executive Lars Moravy told the crowd before the clip played. The line was a deliberate callback. Tesla first revealed the next generation Roadster in November 2017 by driving it out of the back of a Semi trailer at the truck’s original unveiling in Hawthorne, California.

The new video opens on trailer doors swinging apart in the dark. A thin white light bar glows across what appears to be the nose of the car, Tesla and SpaceX logos flash over the frame, and the Roadster name appears before the clip ends on “See you next week.” Tesla posted the nine second clip on X after the livestream wrapped.

The light bar is the most concrete design detail so far. The 2017 prototype used two separate curved headlamp pods, while a connected front light strip would bring the Roadster in line with the Cybertruck, Cybercab, Semi, and refreshed Model Y. Sawyer Merritt was among the first to point out what looked like part of a SpaceX logo in the video, something Tesla has not addressed.

That logo fits the buildup around the optional SpaceX Package, which Elon Musk has long said would use cold gas thrusters to improve acceleration and possibly allow the car to briefly leave the ground. Tesla’s “Go for launch” post on September 12 set the October 1 date, and invitations sent to reservation holders place the event in Waco, Texas, at 8:30 p.m. Eastern. Waco sits roughly 20 minutes from SpaceX’s McGregor rocket test site, where the FAA has put a temporary flight restriction in place from September 18 through October 2, covering a 1.5 nautical mile radius from the surface up to 10,000 feet.

Tesla is also taking money ahead of the reveal. The company reopened Roadster reservations earlier this week with a $5,000 refundable card payment, followed by a $45,000 wire transfer due within 10 days. That puts buyers at $50,000 committed before Tesla has published a price.

The original pitch set a high bar: 0 to 60 mph in 1.9 seconds before any upgrades, 620 miles of range, a top speed above 250 mph, and production in 2020. That timeline has slipped repeatedly, and Tesla has since pointed to production at Gigafactory Texas no earlier than 2027. The company has said next Thursday’s event will include pricing, specifications, and production targets, the three details original reservation holders have been waiting on for nearly nine years.

Continue Reading

News

Tesla Full Self-Driving release in the EU gets delayed

Published

on

Credit: Grok Imagine

Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.

The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.

Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.

That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.

Elon Musk’s reply to the delay was a single word: “Sigh.”

Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.

Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.

The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.

An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.

Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval

The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.

Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.

Continue Reading