News
SpaceX delays Starhopper’s first flight a few days despite Raptor preburner test success
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.
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.
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.
Tesla Full Self-Driving has officially landed in a new country today, its seventh overall after it launched in both Australia and New Zealand earlier this year.
On Sunday, Tesla owners in South Korea reported that the company’s Full Self-Driving (Supervised) had started arriving in their vehicles. Owners reported that it was v14.1.4, which is not the latest version available in other countries, but is one of the most recent releases Tesla has deployed to drivers:
From 6 to 7
Tesla Full Self-Driving has launched in South Korea; the 7th country to have FSD https://t.co/X6gm1SyoxV
— TESLARATI (@Teslarati) November 23, 2025
This marks the seventh country in which Tesla has enabled its Full Self-Driving suite, following the United States and Puerto Rico, Canada, China, Mexico, Australia, and New Zealand.
Tesla launched Full Self-Driving most recently in Australia and New Zealand about three months ago. The expansion is a major breakthrough for the company as it aims to launch Full Self-Driving on a global scale.
However, the company’s biggest challenge thus far has been getting European regulatory agencies to handle the red tape that has inhibited Tesla from launching its semi-autonomous driving suite on the continent. Recently, it admitted that it sees a pathway through Dutch regulatory bodies, which seem to be the most willing to work with Tesla to get FSD in Europe.
Tesla Full Self-Driving appears to be heading to Europe soon
The company said that it has driven over 1 million kilometers safely on European roads across 17 different countries in internal testing. But its path to success will be by “partnering with the Dutch approval authority RDW to gain exemption for the feature. This involves proving compliance with existing regulations (UN-R-171 DCAS) + filing an exemption (EU Article 39) for yet-to-be-regulated behaviors like Level 2 systems off-highway, system-initiated lane changes with hands-off the wheel, etc.”
Perhaps the expansion into Europe will be the biggest challenge for Tesla, but it could also yield major results and advantages for the company moving forward. Tesla said it hopes to have FSD available in Europe sometime early next year.
For now, the expansion in South Korea is the latest win for Tesla and its self-driving efforts. In the U.S., it now turns its focus toward fully autonomous operation, as it works with state agencies to launch Robotaxi outside of Texas, California, and most recently, Arizona.
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:
Tesla Full Self-Driving lands in a new country, its 7th
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
