News
SpaceX scrubs Starhopper’s final Raptor-powered flight as Elon Musk talks “finicky” igniters
For unknown reasons, SpaceX’s Starhopper prototype suffered a hold just 0.8 seconds prior to its second planned flight test, a hold that was eventually followed by a decision to scrub the August 26th attempt and try again tomorrow, August 27th.
Starhopper is a full-scale, partial-height testbed for SpaceX’s next-generation Starship launch vehicle, serving more as a semi-mobile test stand for steel rockets and Raptor engines than an actual Starship prototype. The unusual vehicle took flight for the first time ever on July 25th, reaching an altitude of roughly 20m (65 ft) under the power of a single Raptor engine, capable of producing up to 200 tons (450,000 lbf) of thrust. That test also suffered a minor scrub on the 24th, followed by a successful flight one day later, a chapter that Starhopper may now mirror on its second attempted flight, a 150m (500 ft) hop.
Notably, SpaceX CEO Elon Musk took to Twitter just seconds after the rocket’s scheduled liftoff suffered a last-second hold to indicate that Raptor’s torch igniters were proving somewhat finicky relative to the chemical alternative used by SpaceX’s proven Merlin engines.
The CEO later confirmed that that comment was directly related to the 26th’s scrub, indicating that Raptor serial number 06 (SN06) needed to have its igniters inspected prior to a second hop test attempt, now scheduled to occur no earlier than 6pm EDT (22:00 UTC) on August 27th. The gist of the difficulties with Raptor’s igniter starts with the reason that SpaceX is attempting to integrate an entirely new form of ignition into the engine, replacing the methods successfully used over tens or even hundreds of thousands of seconds of firing with the company’s Merlin 1 and Merlin Vacuum engines.
Merlin 1D and MVacD both rely on a relatively simple, reliable, cheap, and easy method of chemical ignition, using a duo of pyrophoric materials known as triethylaluminum-triethylborane (TEA-TEB). When mixed, these materials immediately combust, generating an iconic green flash visible during Falcon 9 and Heavy launches, and thus producing the ‘spark’ needed to start Merlin engines.
Generally speaking, TEA-TEB is an excellent method of igniting rockets, even if it is more of a brute-force, inelegant solution than alternatives. It does, however, bring limitations: every single ignition requires a new ‘cartridge’ be expended, fundamentally limiting the number of times Merlin 1D (and Merlin Vacuum) engines can be ignited before and after liftoff.
This doesn’t even consider the fact that TEA-TEB are extremely complex chemical products that would be next to impossible to produce off of Earth, at least for the indefinite future.
To combat these downsides, SpaceX has designed Raptor with an entirely different method of ignition, known as torch ignition. Technically speaking, Raptor’s power, design, and methalox propellant combine to demand more than a relatively common solution, in which spark plugs are used to ignite an engine. Instead, Raptor uses those spark plugs to ignite its ignition sources, what CEO Elon Musk has described as full-up blow torches. Once ignited, those blow torches – likely miniature rocket engines using the same methane and oxygen fuel as Raptor – then ignite the engine’s methane and oxygen preburners before finally igniting those mixed, high-pressure gases in the combustion chamber.
In simple terms, the fact that Raptor is a full-flow staged-combustion (FFSC) engine means that the pressures it must operate under are extreme, verging on unprecedented in large-scale rocketry. Extremely high-pressure gases (on the order of 3,000-10,000+ psi or 200-700+ bar) are just as difficult to reliably ignite, especially if hypergolic solutions (i.e. TEA-TEB) are off the table.
To get an even ignition – critical to avoid burn-through, minor explosions, and even catastrophic engine failures – Raptor’s torch ignition may actually involve a 360-degree ring of spark plug-lit torches around the point of ignition, an undeniably complex solution.
However, as Musk notes, these significant, “finicky” challenges brought on by Raptor’s exotic ignition method are motivated by the potential benefits such a solution might bring. Relative to Merlin 1D’s TEA-TEB ignition, torch ignition – once optimized and matured into a reliable solution – will permit an almost unlimited number of Raptor ignitions before, during, and after flight.
Avoiding TEA-TEB and other complex chemical igniters also means that Starship will technically be able to launch to Mars or the Moon, perform injection and landing burns, maybe even hop around the surface, and still be able to return to Earth – all without resupply. Such a return voyage would still be predicated on the ability to generate the methane and oxygen propellant needed to fuel Starships, but – assuming that challenge can be solved – torch-lit Raptors would be ready for such a mission. In the event that, say, something like August 26th’s scrub happens to a Starship on Mars, the crew would also be able to get out, inspect Starship’s Raptors, and even replace faulty spark plugs if necessary.
Technically, one could bring lots of spare TEA-TEB cartridges and install those in space or after landing, but those cartridges are quite literally firebombs waiting to ignite, whereas spare spark plugs are entirely inert.
For now, we’ll have to wait for SpaceX technicians to get their eyes and hands-on Starhopper’s lone Raptor engine to verify that its ignition hardware is in good health. If all goes well, Starhopper will attempt its final flight test as early as August 27th.
Update (August 27th): Starhopper is reportedly set for a second attempted 150m (500 ft) flight test today, scheduled to occur no earlier than 5pm EDT (21:00 UTC) on August 27th. Stay tuned for SpaceX’s official Livestream!
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
