News
SpaceX sends “radically redesigned” Starship engine to Texas for hot-fire tests
SpaceX has shipped one of the first of a group of Starship engines known as Raptor, described last month by CEO Elon Musk as “radically redesigned”. A culmination of more than 24 months of prototype testing, the first flight-worthy Raptor could be ignited for the first time as early as February.
According to Musk, three of these redesigned Raptors will power the first full-scale BFR prototype, a Starship (upper stage) test article meant to conduct relatively low-altitude, low-velocity hop tests over the southern tip of Texas. Those tests could also begin next month, although a debut sometime in March or April is increasingly likely.
Engines currently on Starship hopper are a blend of Raptor development & operational parts. First hopper engine to be fired is almost finished assembly in California. Probably fires next month.
— Elon Musk (@elonmusk) January 5, 2019
Effectively designed on a blank slate, Raptor began full-scale component-level tests in 2014 at NASA’s Mississippi-based Stennis Space Center, evolving from main injector development to oxygen preburner hot-fires in 2015. Soon after Raptor’s prototype preburner design was validated at Stennis, SpaceX moved testing to its privately-owned and operated facilities in McGregor, Texas, where Raptor static fire testing has remained since.
Mach diamonds pic.twitter.com/TCX7ZGFnN0
— Elon Musk (@elonmusk) September 26, 2016
Just days before CEO Elon Musk was scheduled to reveal SpaceX’s next-generation rocket (BFR, formerly known as the Interplanetary Transport System or ITS) in September 2016, he announced in a tweet that propulsion engineers and technicians had successful hot-fired an integrated Raptor prototype – albeit subscale – for the first time ever. Just 12 months later, Musk once again took to the stage to announce an update to BFR’s design, while also revealing that prototype Raptor engines had already completed more than 1200 seconds (20 minutes) of cumulative hot-fire tests, an extremely aggressive and encouraging rate of progress for such a new engine.
SpaceX has completed over 1,200 seconds of firing across 42 main Raptor engine tests. pic.twitter.com/EhxbPjd8Cj
— SpaceX (@SpaceX) September 29, 2017
Although Raptor undoubtedly borrows heavily from much of the same expertise that designed Merlin 1 and operated and improved it for years, that is roughly where the similarities between Raptor and M1D end. M1D, powered by refined kerosene (RP-1) and liquid oxygen, uses a combustion cycle (gas-generator) that is relatively simple and reliable at the cost of engine efficiency, although SpaceX propulsion expertise still managed to give M1D the highest thrust-to-weight ratio of any liquid rocket engine ever flown. Still, measured by ISP (instantaneous specific impulse), M1D’s inefficient kerolox gas-generator cycle ultimately means that the engine simply can’t compete with the performance of engines with more efficient propellants and combustion cycles.
While SpaceX’s Falcon 9 and Heavy rockets – powered by Merlin 1D and Merlin Vacuum – are more than adequate in and around Earth orbit, a far more efficient engine was needed for the company to enable the sort of interplanetary colonization Musk had in mind when he created SpaceX. Raptor was the answer. Ultimately settling on liquid methane and oxygen (methalox) as the propellant and a full-flow staged-combustion (FFSC) cycle, Raptor was designed to be extraordinarily reliable and efficient in order to safely power a spacecraft (BFS/Starship) meant to ferry dozens or hundreds of people to and from Mars.
- The only official render of Raptor, published by SpaceX in September 2016. The Raptor departing Hawthorne in Jan ’19 looked reasonably similar. (SpaceX)
- SpaceX technicians wrench on Merlin 1D and Merlin Vacuum engines. Raptor was apparently dramatically larger in person. (SpaceX)
- Starhopper’s Raptors feature a very distinct seam and second curve, indicative of a dual-bell nozzle. (NASASpaceflight /u/bocachicagal)
Raptor enters a new era
For all the extensive and invaluable testing SpaceX has done with a series of prototype Raptor engines, the engines tested were subscale versions with around 30% the thrust of the c. 2016 Raptor and around 40-50% of the updated c. 2017 iteration, producing almost the same amount of thrust as Merlin 1D (914 kN to Raptor’s ~1000 kN). In September 2018, Musk described Raptor as an “approximately…200-ton (~2000 kN) thrust engine” that would eventually operate with a chamber pressure as high as 300 bar (an extraordinary ~4400 psi), requiring at least one of the FFSC engine’s two preburners (used to power separate turbopumps) to operate at a truly terrifying ~810 bar (nearly 12,000 psi).
Conveniently stood beside a Merlin 1D engine also ready for hot-fire acceptance testing, the Raptor engine spotted departing SpaceX’s Hawthorne, CA factory last week was reportedly immense in person, towering over an M1D engine. Raptor also featured a mass of spaghetti-like plumbing (complexity necessary for its advanced combustion cycle), with a significant fraction of the metallic pipes and tubes displaying mirror-like finishes. Most notable was an obvious secondary preburner/turbopump stack and the lack of any exhaust port, whereas M1D relies on a single turbopump and exhausts the gases used to power it. Raptor’s full-flow staged-combustion cycle uses separate oxygen and methane preburners to power separate turbopumps, significantly improving mass flow rate and smoothing out combustion mixing.
- SpaceX’s current Texas facilities feature a test stand for Raptor, the engine intended to power BFR and BFS to Mars. (SpaceX)
- SpaceX’s subscale Raptor engine has completed more than 1200 seconds of testing in less than two years. (SpaceX)
- A gif of Raptor throttling over the course of a 90+ second static-fire test in McGregor, Texas. (SpaceX)
- A September 2018 render of Starship (then BFS) shows one of the vehicle’s two hinged wings/fins/legs. (SpaceX)
Unlike all previous hot-fired Raptors, those shipping now to McGregor, Texas are expected to be the first completed engines with a finalized design, arrived at only after a period of extensive testing and iterative improvement. They also appear to be full-scale, meaning that the test bays dedicated to Raptor will likely need to be upgraded (if they haven’t been already) to support a two- or threefold increase in maximum thrust.
Yes. Radically redesigned Raptor ready to fire next month.
— Elon Musk (@elonmusk) December 22, 2018
SpaceX’s Starship hopper will need three finalized engines, meaning that the Raptor now in McGregor, Texas may not have been the first to arrive. Nevertheless, the shipment of full-scale hardware is always an extremely encouraging milestone for any advanced technology development program, while also foreshadowing the first imminent static-fires of the “radcally redesigned” rocket engine. With hardware now at the test site before January is out, a February test debut – one month behind a January debut teased by Elon Musk last December – is not out of the question.
News
Tesla Full Self-Driving release in the EU gets delayed
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.”
Sigh
— Elon Musk (@elonmusk) September 25, 2026
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.
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.
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.
Launch rehearsal complete ahead of Starship Flight 14 pic.twitter.com/h5LBYyBqi4
— SpaceX (@SpaceX) September 24, 2026
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.”
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.
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.






