Connect with us

News

SpaceX delays Starhopper’s first flight a few days despite Raptor preburner test success

According to NASASpaceflight.com, SpaceX's Starhopper successfully completed a Raptor preburner taste on July 15th. A static fire ignition test should follow on July 16th.(NASASpaceflight - bocachicagal)

Published

on

SpaceX has (partially) ignited Starhopper’s freshly-installed Raptor engine, successfully verifying that the engine is ready for its next major test: a full ignition and static firing. Although successful, SpaceX still has some work to do before the vehicle is ready for its first untethered flight(s).

July 15th’s progress is just the latest in a several day-series of preflight tests designed to reduce the likelihood that Starhopper is destroyed over the coming days and (hopefully) weeks. If all goes planned during the awkward Starship prototype’s first foray into hover tests, SpaceX CEO Elon Musk has stated that he will provide an official presentation updating the public on the status of the company’s ever-changing next-generation rocket.

The past week or so of Starhopper preflight testing began with Raptor serial number 6 (SN06) completing the last of a series of acceptance test fires in McGregor, Texas on June 10th. Even on its own, this was a major milestone for the new SpaceX engine: Raptor SN06 was the first of the new, full-scale engines to pass the acceptance test program with flying colors. According to Musk, for the engine to complete those tests so successfully, SpaceX had to solve a challenging bug in which some sort of mechanical resonance (i.e. vibration) damaged or destroyed Raptors SN01-05.

Hours later, the engine began a short ~450 mi (720 km) journey south to Starhopper, located in Boca Chica, Texas. The engine arrived on July 11th and was fully installed on Starhopper by the following evening (July 12th), at which point SpaceX put Starhopper and Raptor through some mild but valuable thrust vector controller (TVC) tests, wiggling the car-sized engine to ensure it can accurately steer the prototype rocket.

Around two days after the above ‘wiggle’ test was successfully completed, SpaceX moved into the next stage, partially fueling Starhopper with liquid methane and oxygen propellant and helium pressurant in what is known in rocketry as a wet dress rehearsal (WDR). The (implicitly) successful WDR was capped off with a duo of what can now safely be concluded were some sort of Raptor test preceding even pre-ignition operations. Whatever the tests were, they appear to have been completed successfully.

That appears to be the case because less than 24 hours after their completion, on July 15th, SpaceX once again began loading Starhopper with propellant and pressurant for a second round of wet testing. This time around, SpaceX got right into more critical Raptor tests once enough propellant was loaded, igniting the engine’s interwoven oxygen and methane preburners.

Starhopper (technically) came alive for the third time ever on July 15th, albeit only partially. SpaceX ignited the engine’s preburners as a precursor to a full static fire, now NET July 16th. (LabPadre – YouTube livestream)

Previously discussed 24 hours ago in a Teslarati article focused on Raptor wiggles and other miscellaneous tests, Raptor is an extremely advanced rocket engine based on a cycle (i.e. how propellant is turned into thrust) known as full-flow staged combustion.

“In a staged-combustion engine like Raptor, getting from the supercool liquid oxygen and methane propellant to 200+ tons of thrust is quite literally staged, meaning that the ignition doesn’t happen all at once. Rather, the preburners – essentially their own, unique combustion chambers – ignite an oxygen- or methane-rich mixture, the burning of which produces the gas and pressure that powers the turbines that bring fuel into the main combustion chamber. That fuel then ignites, producing thrust as they exit the engine’s bell-shaped nozzle.

Unintuitively, conditions inside the preburner – hidden away from view – are actually far more intense than the iconic blue, purple, and pink flame that visibly exists Raptor’s nozzle. Much like hot water will cool while traveling through pipes, the superheated gaseous propellant that Raptor ignites to produce thrust will also cool (and thus lose pressure) as it travels from Raptor’s preburner to its main combustion chamber. If the pressure produced in the preburners is too low, Raptor’s thrust will be (roughly speaking) proportionally limited at best. At worst, low pressure in the preburners can trigger a “hard start” or shutdown that could destroy the engine. According to Elon Musk, Raptor’s oxygen preburner thus has the worst of it, operating at pressures as high or higher than 800 bar (11,600 psi, 80 megapascals).”

In full-flow staged combustion (FFSC), even more complexity is added as all propellant that touches the engine must necessarily end up traveling through the main combustion chamber to eke every last ounce of thrust out of the finite propellant a rocket lifts off with. As such, FFSC engines can be about as efficient as the laws of physics allow any given chemical rocket engine to be, at the cost of exceptional complexity and brutally difficult development.

Additionally, FFSC physically requires two separate preburners and then makes things even harder by making each separate preburner (methane and oxygen) depend on each other’s operation for the engine to fully ignite. This means that no individual preburner can be used to kickstart Raptor – instead, SpaceX must somehow spin the turbopumps that feed propellant into each preburner with some separate system. This is all just to emphasize the fact that Raptor’s ignition sequence is a spectacularly complex orchestra of valves, spark plugs, sensors, and magic. This is why it’s valuable for Raptor to test its preburner system independently of an actual ignition test, at least as long as the engine is still in the development stages.

A Raptor engine is pictured here during a static fire test in McGregor, Texas. (SpaceX)

According to NASASpaceflight.com managing editor Chris Bergin, what this practically translates to is a minor Starhopper hover test delay of 1-2 days, while the static fire has also been pushed roughly 24 hours from July 15th to July 16th. If that full static fire produces lots of happy data, Starhopper could be cleared for a hover test debut attempt as early as Wednesday or Thursday (July 17/18).

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

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