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 released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla claims supplier is holding Cybertruck production hostage
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
