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.
Elon Musk
Tesla Full Self-Driving’s newest behavior is the perfect answer to aggressive cars
According to a recent video, it now appears the suite will automatically pull over if there is a tailgater on your bumper, the most ideal solution for when a driver is riding your bumper.
Tesla Full Self-Driving appears to have a new behavior that is the perfect answer to aggressive drivers.
According to a recent video, it now appears the suite will automatically pull over if there is a tailgater on your bumper, the most ideal solution for when a driver is riding your bumper.
With FSD’s constantly-changing Speed Profiles, it seems as if this solution could help eliminate the need to tinker with driving modes from the person in the driver’s seat. This tends to be one of my biggest complaints from FSD at times.
A video posted on X shows a Tesla on Full Self-Driving pulling over to the shoulder on windy, wet roads after another car seemed to be following it quite aggressively. The car looks to have automatically sensed that the vehicle behind it was in a bit of a hurry, so FSD determined that pulling over and letting it by was the best idea:
Tesla appears to be implementing some sort of feature that will now pull over if someone is tailgating you to let the car by
Really cool feature, definitely get a lot of this from those who think they drive race cars
— TESLARATI (@Teslarati) February 26, 2026
We can see from the clip that there was no human intervention to pull over to the side, as the driver’s hands are stationary and never interfere with the turn signal stalk.
This can be used to override some of the decisions FSD makes, and is a great way to get things back on track if the semi-autonomous functionality tries to do something that is either unneeded or not included in the routing on the in-car Nav.
FSD tends to move over for faster traffic on the interstate when there are multiple lanes. On two-lane highways, it will pass slower cars using the left lane. When faster traffic is behind a Tesla on FSD, the vehicle will move back over to the right lane, the correct behavior in a scenario like this.
Perhaps one of my biggest complaints at times with Full Self-Driving, especially from version to version, is how much tinkering Tesla does with Speed Profiles. One minute, they’re suitable for driving on local roads, the next, they’re either too fast or too slow.
When they are too slow, most of us just shift up into a faster setting, but at times, even that’s not enough, see below:
What has happened to Mad Max?
At one point it was going 32 in a 35. Traffic ahead had pulled away considerably https://t.co/bjKvaMVTNX pic.twitter.com/aaZSWmLu5v
— TESLARATI (@Teslarati) January 24, 2026
There are times when it feels like it would be suitable for the car to just pull over and let the vehicle that is traveling behind pass. This, at least up until this point, it appears, was something that required human intervention.
Now, it looks like Tesla is trying to get FSD to a point where it just knows that it should probably get out of the way.
Elon Musk
Tesla Megapack powers $1.1B AI data center project in Brazil
By integrating Tesla’s Megapack systems, the facility will function not only as a major power consumer but also as a grid-supporting asset.
Tesla’s Megapack battery systems will be deployed as part of a 400MW AI data center campus in Uberlândia, Brazil. The initiative is described as one of Latin America’s largest AI infrastructure projects.
The project is being led by RT-One, which confirmed that the facility will integrate Tesla Megapack battery energy storage systems (BESS) as part of a broader industrial alliance that includes Hitachi Energy, Siemens, ABB, HIMOINSA, and Schneider Electric. The project is backed by more than R$6 billion (approximately $1.1 billion) in private capital.
According to RT-One, the data center is designed to operate on 100% renewable energy while also reinforcing regional grid stability.
“Brazil generates abundant energy, particularly from renewable sources such as solar and wind. However, high renewable penetration can create grid stability challenges,” RT-One President Fernando Palamone noted in a post on LinkedIn. “Managing this imbalance is one of the country’s growing infrastructure priorities.”
By integrating Tesla’s Megapack systems, the facility will function not only as a major power consumer but also as a grid-supporting asset.
“The facility will be capable of absorbing excess electricity when supply is high and providing stabilization services when the grid requires additional support. This approach enhances resilience, improves reliability, and contributes to a more efficient use of renewable generation,” Palamone added.
The model mirrors approaches used in energy-intensive regions such as California and Texas, where large battery systems help manage fluctuations tied to renewable energy generation.
The RT-One President recently visited Tesla’s Megafactory in Lathrop, California, where Megapacks are produced, as part of establishing the partnership. He thanked the Tesla team, including Marcel Dall Pai, Nicholas Reale, and Sean Jones, for supporting the collaboration in his LinkedIn post.
Elon Musk
Starlink powers Europe’s first satellite-to-phone service with O2 partnership
The service initially supports text messaging along with apps such as WhatsApp, Facebook Messenger, Google Maps and weather tools.
Starlink is now powering Europe’s first commercial satellite-to-smartphone service, as Virgin Media O2 launches a space-based mobile data offering across the UK.
The new O2 Satellite service uses Starlink’s low-Earth orbit network to connect regular smartphones in areas without terrestrial coverage, expanding O2’s reach from 89% to 95% of Britain’s landmass.
Under the rollout, compatible Samsung devices automatically connect to Starlink satellites when users move beyond traditional mobile coverage, according to Reuters.
The service initially supports text messaging along with apps such as WhatsApp, Facebook Messenger, Google Maps and weather tools. O2 is pricing the add-on at £3 per month.
By leveraging Starlink’s satellite infrastructure, O2 can deliver connectivity in remote and rural regions without building additional ground towers. The move represents another step in Starlink’s push beyond fixed broadband and into direct-to-device mobile services.
Virgin Media O2 chief executive Lutz Schuler shared his thoughts about the Starlink partnership. “By launching O2 Satellite, we’ve become the first operator in Europe to launch a space-based mobile data service that, overnight, has brought new mobile coverage to an area around two-thirds the size of Wales for the first time,” he said.
Satellite-based mobile connectivity is gaining traction globally. In the U.S., T-Mobile has launched a similar satellite-to-cell offering. Meanwhile, Vodafone has conducted satellite video call tests through its partnership with AST SpaceMobile last year.
For Starlink, the O2 agreement highlights how its network is increasingly being integrated into national telecom systems, enabling standard smartphones to connect directly to satellites without specialized hardware.






