Connect with us

News

SpaceX schedules Starship’s first triple-Raptor static fire test

SpaceX has successfully installed three Raptors on Starship SN8 and is scheduled to attempt the first triple-engine static fire as early as October 14th. (Elon Musk)

Published

on

A photo posted by CEO Elon Musk confirms that SpaceX has successfully installed three functional Raptors on Starship SN8 just hours before road closure notices revealed the company’s first triple-engine static fire schedule.

Technically, it’s incorrect to say that Starship serial number 8 (SN8) is the first prototype to receive three Raptor engines. Back in late-September 2019, in the lead-up to Musk’s promised Starship update event, the company installed three Raptors on the first full-scale prototype, known as Starship Mk1. The engines were only installed as an apparent fit test or even a photo opportunity, however – evidenced by the fact that they weren’t actually plumbed to the Starship’s propellant tanks.

Even then, in September 2019, Starship Mk1 was far from ready to make use of Raptor engines and was more than a month away from attempting its first pressure and cryogenic proof tests – tests it quickly failed. As such, Starship SN8 – having more or less successfully passed its ‘cryo proof’ by October 9th – is undoubtedly the first ship to have a shot at igniting multiple Raptor engines at once.

Almost exactly one year after Starship Mk1, SpaceX has successfully installed three Raptors on Starship SN8. (SpaceX)

Curiously, SpaceX remained quiet for several days after Starship SN8 passed its first big test. Whereas with past Starship prototypes SpaceX has often filed test plans (appearing in the form of road closures) even before the current phase of testing is complete, the company waited until Tuesday, October 14th to file closure notices for “SN8 static fire” testing.

Same as Starships SN4, SN5, and SN6, all of which successfully graduated from cryo proof to static fire testing (and even flight tests for the latter two), SpaceX began Starship SN8’s test campaign with a cryo proof. It took three days and at least as many attempts but SN8 ultimately “passed cryo proof” according to Elon Musk, likely meaning that the ship reached sustained pressures of 7.5 bar (~110 psi) or more.

Elon Musk says that SpaceX’s first high-altitude Starship prototype has passed its first major test. (NASASpaceflight – bocachicagal)

Cryo proof complete, SpaceX installed Starship SN8’s engines – the first time multiple Raptors have been fully integrated with a rocket or test stand – in preparation for another Raptor first: multi-engine static fires. While modern computation fluid dynamics (CFD) and modeling mean that the great unknowns of rocket propulsion are rarely as opaque as they used to be, the first test of multiple powerful engines in close proximity is still a guaranteed recipe for surprises.

Thanks to expertise hard-won from nearly 100 Falcon 9 and Falcon Heavy launches, SpaceX is likely the world’s foremost expert in the challenges and dynamics of the proximity operation of more than two rocket engines. At the same time, though, Raptor is a dramatically different engine than Merlin 1D and while Starship will only have six engines at most, those six engines will produce thrust equivalent to almost two entire Falcon 9 boosters.

Starship SN5 prepares to land under the thrust of one Raptor engine – more than twice as powerful as Falcon 9’s Merlin 1D. (SpaceX)

In other words, even with a (relatively) simple three-Raptor static fire, SpaceX will be treading new ground and will almost certainly end up learning one or several things about Raptor’s design and operation. More likely than not, SpaceX will begin Starship SN8’s static fire test campaign with a wet dress rehearsal (like a cryo proof but with real liquid methane and oxygen propellant) and transition into a Raptor spin prime (turbopump spin-up) or preburner test (a turbopump spin-up but with partial combustion) if the WDR goes smoothly. If all three Raptor engines appear healthy, SpaceX may recycle and attempt the first static fire just an hour or two later.

Starship SN8’s triple-Raptor static fire test window opened at 9pm CDT on October 14th and closes at 6am on the 15th, with an identical 9pm-6am backup on the 15th and another window from 8am to 4:30pm on the 16th. LabPadre (below) will continue to offer 24/7 views of Starship, including any static fire testing, while NASASpaceflight.com will likely provide live coverage once testing begins in earnest.

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

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

News

SpaceX readies Starship Flight 14 for a historic journey into uncharted territory

SpaceX finished Starship’s Flight 14 rehearsal, clearing the way for its first orbital flight Monday.

Published

on

By

Sunrise at Starbase. Starship is stacked for opportunistic full-stack testing ahead of Flight 14 via SpaceX
Sunrise at Starbase. Starship is stacked for opportunistic full-stack testing ahead of Flight 14 via SpaceX

SpaceX has cleared one of the last hurdles before Starship’s first trip to orbit. The company posted on X Thursday afternoon that its launch rehearsal for Flight 14 was complete, keeping the mission on track for Monday, September 28. The launch window opens at 7:15 a.m. CT at Starbase, Texas, and runs for 75 minutes.

A wet dress rehearsal is essentially launch day without the launch. Crews fill Booster 21 and Ship 41 with thousands of tons of extremely cold propellant, run the countdown nearly to ignition, then drain everything back out. It lets engineers catch leaks or equipment problems before anything leaves the pad. SpaceX still needs a launch license from the FAA before the stack, which stands 407 feet tall, can fly.

Flight 14 matters because of where it is going. All 13 previous Starship flights followed a suborbital path, which works like throwing a ball extremely high and far: the vehicle reaches space, but it is always on a course that brings it back down within about an hour. This time, Ship 41 will perform a short engine firing called an orbital insertion burn roughly 25 minutes after liftoff, giving it enough speed to keep falling around Earth instead of back into it. SpaceX plans about six laps at an altitude near 275 kilometers (171 miles) over nearly 10 hours, as Teslarati detailed when the mission was first announced.


Getting into orbit also means Starship has to prove it can get back out. The ship must relight a single Raptor engine in space to slow down for reentry. SpaceX says it will only attempt the orbital insertion burn after flight controllers confirm the hardware needed for that return burn has enough backup, and its flight plan includes health checks that could shorten the mission to two or five orbits.

Flight 14 is also the first to put working satellites into service. Flight 13 carried 20 Starlink V3 satellites in July, but they came back down with the ship because that mission never reached orbit. This time, 26 V3 satellites are meant to stay up and join the constellation within a few weeks. Together they add about 26 terabits per second of network capacity, which SpaceX says is roughly 10 times what a single Falcon 9 launch of older V2 Mini satellites adds. Three of them carry cameras that will photograph Starship’s heat shield in orbit to check for tile damage before reentry.

The hardware has changed too. Ship 41 flies with extra fasteners on tiles in the most vulnerable areas, fixes for gaps where superheated plasma slipped behind tiles, and curved tiles designed to reduce heating between them. Two tiles recovered from Ship 40 will fly again, the first reuse of any part of a Starship heat shield. Booster 21 carries better engine filtering and new relight software after ice clogged three center engines on the previous booster, leaving only eight of 13 engines to restart for its landing burn.

Ship 41 is targeting a splashdown in the Pacific Ocean west of Chile, a new recovery zone after several Indian Ocean landings, while Booster 21 aims for the Gulf. Neither will be caught by the tower on this flight. Elon Musk said in August that a ship catch was likely “in a few months.”

Continue Reading

Elon Musk

Google just picked SpaceX for its first step into orbital AI

Google will launch its first Project Suncatcher AI satellite on SpaceX’s Transporter-18 rideshare next week.

Published

on

By

Google is about to put its own AI chips into orbit for the first time, and it is paying SpaceX to get them there.

The company said Thursday that the first in-orbit test of Project Suncatcher, its research effort to find out whether space can host large-scale AI computing, will fly next week on SpaceX’s Transporter-18 rideshare mission.

The satellite, called MVP, is about the size of a refrigerator and carries four of Google’s Tensor Processing Units, the same chips Google runs in its ground data centers. Google originally planned to launch two custom satellites in 2027, but chose to move faster by integrating its chips into a satellite.

MVP’s solar panels supply about one kilowatt of power, and Google will run Gemini models on the TPUs only in bursts of roughly 15 minutes before the chips shut down so the radiators can shed heat. In a blog post, Google said its Trillium TPUs survived vibration testing that mimicked sustained launch loads of up to 10g, with individual components seeing 50 to 100g, and handled a radiation dose greater than a five year mission would deliver.

SpaceX and Google mull massive partnership on Musk’s orbital data dream: report

Next week’s flight, slated for October 1, follows a relationship that became public in May, when Teslarati reported that Google was in talks with SpaceX for a launch deal tied to orbital data centers. Google also holds a stake of roughly 6% in SpaceX.

The two companies are chasing the same idea from very different starting points. SpaceX’s own orbital compute program is built around the AI1 satellite, a roughly 70 meter structure derived from Starlink V3 hardware that is designed for 150 kW of peak compute, about 150 times the power MVP will draw. Elon Musk has brushed off concerns about crowding orbit with those satellites, and SpaceX is building its Gigasat factory in Bastrop, Texas, to produce them, targeting an annualized rate of about 1 GW of space compute by the end of 2027.

Musk also posted on X on Thursday that “the amount of compute in space will obviously round up to 100% of all compute.”

Google has been more cautious in public. Its research estimates that launch prices need to fall below about $200 per kilogram before an orbital data center can compete with a ground facility on energy cost, a threshold the company believes could be reached around the mid 2030s. The Suncatcher team has said it expects the effort to remain a project rather than a product for years, which leaves the first real test of its hardware riding on a rocket from the company with the most aggressive timeline in the field.

Continue Reading