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.
A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.
The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.
TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.
Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.
Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.
TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.
This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.
This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.
However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.
Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.
Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.
The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.
A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”
Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.
This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.
The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.
Musk teased that a similar feature was “coming” back in February:
Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says
It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.
Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.
Here’s an example of that from December:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.
We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
