News
SpaceX’s Starhopper readies for more ambitious Raptor-powered flight tests
For the second time in two months, SpaceX technicians have begun to install a Raptor engine on Starhopper, a full-scale Starship testbed theoretically capable of low-velocity, moderate-altitude ‘hops’.
Back in late March, Raptor and Starhopper were joined for the first time, enabling a lengthy series of attempted tests that were followed by two engine ignitions and tethered hops before Raptor was removed for inspection. In the two months since that first round of integrated testing, SpaceX has significantly upgraded Starhopper and its spartan launch facilities, all focused on transforming the odd vehicle from a largely fixed test stand into a giant, mobile Grasshopper.
All the way back in 2012, SpaceX began testing Falcon 9 recovery and reusability concepts with a low-fidelity prototype known as Grasshopper – essentially a minimalist Falcon 9 first stage with ad hoc legs and a single Merlin engine. It supported a series of 8 major test flights – all successful and a source of valuable data – before the vehicle’s 2013 retirement. An upgraded Grasshopper – known instead as Falcon 9 Reusable Development Vehicle (F9R Dev1) – began testing around the same time and continued even higher altitude vertical takeoff/vertical landing (VTVL) tests until its untimely demise in August 2014.
Starhopper is quite similar, although it is also serving as a testbed for a far more varied range of technologies due to the fact that it has been developed before the inaugural launch of its namesake (Starship/Super Heavy). By the time SpaceX started Grasshopper/F9R tests, Falcon 9 had already completed several successful launches. With Starhopper, SpaceX is building and testing its first 9m-diameter ‘flight’ hardware, its first propellant tanks built out of steel, its first flight-capable rocket fueled by methane and oxygen, and its first mobile Raptor testbed, among numerous other things. The challenges are inherently much greater, but SpaceX has the luxury of taking the opposite approach it took towards Falcon 9 and building a launch vehicle entirely around its intended reusability, rather than trying to squeeze a method of reusability around an already-flying rocket.
Saurid Oddities
As noted by NASASpaceflight.com in a June 2nd article, SpaceX seems to be juggling its growing selection of newly-produced and tested Raptor engines in pursuit of Starhopper’s return to flight. According to the publication’s reliable sources,
“Up until recently, [SpaceX] was planning to utilize Raptor SN4 for [Starhopper’s first] untethered hops. However, the company has now decided to utilize this engine only for fit checks, and will instead perform the hops with SN5 – the latest Raptor to come out of SpaceX’s factory in Hawthorne, California.” – NASASpaceflight.com, June 2nd, 2019
This indicates that the Raptor engine delivered to Boca Chica on June 1st and currently in the process of being installed on Starhopper is actually more of a stand-in* for a future Raptor, SN05. The reasons behind this Raptor shuffle elude detection, but it’s possible that the simplest explanation – also posed by NASASpaceflight – is the correct one. By shipping a Raptor that may not be ready for flight tests, SpaceX could likely save anywhere from a few days up to a few weeks by doing everything short of lifting off under the powered of Raptor SN04.
*By all appearances, SN04 is a flight-grade Raptor that has completed assembly and likely been test-fired in McGregor, Texas. Why it may currently be resigned to a “stand-in” role is unknown.
It appears that the Raptor engine is not centered, could it be that they are going straight with the 3 engine test. (Idk honestly, I wonder why this is?) @elonmusk are things about to get epic?? pic.twitter.com/sne5v7SMhy— Austin Barnard? (@austinbarnard45) June 1, 2019
Very curiously, upon Raptor SN04’s South Texas arrival, it appears that SpaceX technicians have indeed rapidly installed the engine on Starhopper, but in a position that is decidedly off-center. Pictured above, the photo could have simply caught the engine while technicians were moving it to its actual installation spot, but it could also indicate that SpaceX is speeding towards Starhopper’s first triple-Raptor test flights.
Starhopper delays?
In line with the last-second switch from Raptor SN04 to Raptor SN05 as the engine-to-be for untethered hops, SpaceX has pushed the start of that test series from approximately May 31st to June 11th. More likely than not, the ~11-day delay is meant to allow time for Raptor SN05’s McGregor, Texas acceptance testing, given that – per CEO Elon Musk – the engine wasn’t even finished as of May 22nd.
On the other hand, with Raptor SN05 now scheduled to support Starhopper hop tests as early as mid-June, it begs the question of whether SpaceX is instead working towards expedited triple-Raptor testing. For unknown reasons, neither Raptor SN03 or SN04 are apparently ready to support flight operations, although both have been thoroughly hot-fired in McGregor. Perhaps each engine is a distinct prototype with a different level of experimental readiness, or perhaps SpaceX is just testing certain engines (like SN03) more extensively than others (SN05).
Regardless, SpaceX now seems to have 3-4 intact, functional Raptor engines (excluding SN01; destroyed during stress testing), 2-3 of which are actively testing or being worked on a day’s drive north of Boca Chica. SN02 – having successfully supported a brief duo of ignition tests with Starhopper – could still be intact and test-ready. SN03 is an unknown quantity, but SN04 is clearly in excellent shape and is probably close to flight-readiness if it isn’t already. This is to say that SpaceX likely already has three Raptors on hand that are capable of supporting multi-engine Starhopper testing, whether or not such a test regime would actually be valuable.
Musk has noted that both orbit-capable Starship prototypes will be far closer to finished products and will thus fly with “at least 3 engines” (3 sea level engines, as it would turn out) or even “all 6” (3 sea level, 3 vacuum-optimized). In the meantime, Starhopper stands with an off-centered Raptor, awaiting the arrival of a different Raptor to kick off a second hop test program. If nothing else, SpaceX’s Starship/Super Heavy development program is operating in a spectacularly hardware-rich fashion, lending itself to the breakneck-pace of iteration and improvement SpaceX is famous for.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
