Connect with us

News

SpaceX Starship prototype charred but intact after catching fire [photos]

SpaceX employees inspect Starship SN4 for the first time some two days after the rocket finished its third Raptor engine test. (NASASpaceflight - bocachicagal)

Published

on

SpaceX teams have finally safed the fourth full-scale Starship prototype nearly two days after a Raptor engine test caught it on fire, an anomaly that left the massive rocket charred and damaged – but still intact.

While SN4’s survival is a welcome and unexpected outcome, the fire that broke out near the base of the rocket caused damage that will have to be repaired, while the fault that allowed that fire to occur in the first place will also need to be rectified. Had the same events transpired during the ship’s inaugural flight test, things could have gone even further south after the rocket lifted off, carrying it away from remotely-controlled water jets used to suppress unplanned fires on the pad.

Thankfully, SpaceX’s focus on testing, testing, and testing some more meant that Starship SN4’s minor self-immolation occurred on the ground when the stakes – while high – were much lower than they would have been with an airborne rocket. The problems uncovered will, of course, need to be fixed, inevitably delaying the ship’s first flight test, but odds are that SN4 now has a better shot at success thanks to those hiccups.

Starship SN4 has thankfully survived a ~48-hour ordeal that may have left the rocket partially uncontrolled. (NASASpaceflight – bocachicagal)

Thanks to the fact that Starships are constructed almost entirely out of steel, a little (or a lot of) fire shouldn’t theoretically be much of a problem. However, SpaceX has taken a rather freeform approach to its early Starship SNx prototypes, opting to bolt, weld, or tape on the vast majority of external hardware with little or no protection from the elements, including fires ignited by the ships themselves.

With SN4, it appears that the pressure jump experiences immediately after Raptor ignition (the ship’s third such test) shook some methane-related plumbing loose. Raptor continued to burn for another five or so seconds after that minor failure, shutting down as planned – but not before it ignited the methane the burst pipe was leaking. Additionally, after that new plume of boiling liquid methane caught fire, the fire it sustained proceeded to ignite insulation wrapped around the rocket’s launch. It burned vigorously, likely helping to damage wiring, ultimately causing SpaceX to partially lose control of the rocket and preventing attempts to inspect and fix the damage for two full days.

A May 8th view of the pipe (bottom right of Starship SN4) that failed on May 19th, starting a fire and damaging the rocket. (NASASpaceflight – bocachicagal)
A large scorch mark and blackened cabling are the only signs on Starship that anything went wrong on May 19th. (NASASpaceflight – bocachicagal)
Around the other side of the rocket, (apparently flammable) insulation haphazardly wrapped around part of the launch mount ~24 hours before testing caught fire and burned aggressively. The leftovers are pictured here on May 21st. (NASASpaceflight – bocachicagal)

It’s safe to say that SpaceX is probably going to prioritize avoiding the series of events that caused May 19th’s anomaly from here on out, considering that things could have easily gone much worse. Thankfully, whatever control SpaceX or the rocket itself retained after wire damage allowed it to safely offload its flammable propellant and vent expanding gases to prevent SN4’s tanks from bursting. Installing highly flammable insulation approximately 10 feet away from an active Raptor engine and giant controlled fire and explosion was also inadvisable and probably won’t be repeated.

(NASASpaceflight – bocachicagal)

Thankfully, the damage is clearly minimal and Starship SN4 survived the ordeal otherwise unscathed. With any luck, inspections and repairs will be quick and easy and SpaceX – as NASASpaceflight reporter Michael Baylor notes – will be able to complete an identical static fire test without starting a fire on Starship SN4. SpaceX has requested a new road closure (signifying planned testing) on May 28th with backup windows on May 29th and June 1st.

Thanks to Starship SN4’s unplanned delays, it now looks quite likely that SpaceX’s next full-scale Starship prototype (SN5) will be completed – or nearly so – by the time that its predecessor is cleared for flight. “Too many Starships” is certainly a welcome problem to have.

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