Connect with us

News

SpaceX scrubs Starhopper’s final Raptor-powered flight as Elon Musk talks “finicky” igniters

SpaceX scrubbed Starhopper's second flight test on August 26th. Another attempt will follow on the 27th. (SpaceX)

Published

7 years ago

on

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.

Falcon 9 and Heavy use chemical means – TEA-TEB – to ignite all of their main and upper stage Merlin engines. (SpaceX)

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.

The first finalized Raptor engine (SN01) completed a successful static fire debut on the evening of February 3rd. (SpaceX)

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.

For Starship to remain readily reusable in either of these situations, Raptor’s use of torch ignition will be absolutely critical. (SpaceX)

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.

Advertisement
-
-
Related Topics:

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla Full Self-Driving insurance program with heavy discount expands

Published

4 hours ago

on

August 3, 2026

By

Lemonade has expanded its innovative Autonomous Car insurance program to Tennessee, giving Tesla owners in the state a substantial discount on Full Self-Driving (FSD) miles. Announced on August 3, the product offers 50 percent off every mile driven with FSD activated, positioning the digital insurer as a leader in pricing insurance around autonomous technology.

The program, marketed as Lemonade Autonomous Car insurance, uses a direct connection via Tesla’s Fleet API (with customer permission) to automatically distinguish FSD-engaged miles from manual driving. Policyholders pay a low base rate when the vehicle is stationary and a few cents per mile when moving, with the 50 percent reduction applied specifically to FSD miles.

Coverage includes standard protections such as liability, collision, comprehensive, roadside assistance, and Tesla-specific benefits like access to certified repair shops and emergency crash services. Eligible vehicles require Hardware 4, as well as recent firmware.

Lemonade first unveiled the product on January 21 of this year, describing it as a first-of-its-kind offering designed for self-driving cars, starting with Tesla FSD. It began rolling out in Arizona on January 26, followed by Oregon about a month later. Subsequent expansions brought it to Indiana in early June 2026 and Colorado later that month.

Tennessee marks the fifth state.

Tesla Full Self-Driving gets outrageous insurance offer with insanely cheap rates

The discount rests on Lemonade’s strong belief in the safety of Tesla’s FSD system. The company cites Tesla’s data showing that FSD-driven miles are twice as safe as those driven manually, or associated with roughly a 50 percent crash reduction.

Lemonade Co-founder and President Shai Wininger has emphasized this distinction: “Traditional insurers treat a Tesla like any other car, and AI like any other driver. But a car that sees 360 degrees, never gets drowsy, and reacts in milliseconds can’t be compared to a human.”

He added that “Teslas driven with FSD are involved in far fewer accidents” and committed that as FSD software improves and becomes safer, Lemonade’s prices will drop further.

Tesla Full Self-Driving gets an offer to be insured for ‘almost free’

This approach leverages Lemonade’s existing pay-per-mile technology and AI-driven risk models, which analyze nuanced vehicle data including software version and sensor performance. The company expects the model to reward higher FSD usage with greater savings while supporting mixed households that include both Tesla and non-Tesla vehicles under one policy. Bundling with home, renters, or pet insurance can yield additional discounts.

As autonomous driving technology advances, Lemonade’s state-by-state expansion of usage-based pricing that directly reflects real-world safety data represents a notable shift in how insurers evaluate risk.

Tesla owners in the five available states – Arizona, Oregon, Indiana, Colorado, and now Tennessee – can obtain quotes quickly through the Lemonade app or website, potentially lowering the overall cost of ownership for vehicles equipped with advanced driver-assistance systems. Further states are expected as regulatory approvals progress.

Continue Reading

Cybertruck

Tesla quietly made the Cybertruck even stronger

Published

8 hours ago

on

August 3, 2026

By

Credit: Tesla

Tesla has continued to flex the strength, rigidity, and robustness of its all-electric pickup, the Cybertruck. In fact, since 2019, Cybertruck’s ability to avoid dents, dings, and even gunfire has been one of the main selling points Tesla has used to attract buyers who are looking for a vehicle that can handle the most intense challenges.

But that does not mean Tesla is not still actively trying to make it even better.

In a new hardware update, Tesla has decided to change the material of the Cybertruck’s underbody panels from aluminum to carbon fiber, a move that aims to not only increase pricing efficiency but also improve strength.

RELATED:

Tesla Cybertruck is officially the safest pickup, IIHS says

Cybertruck Lead Engineer Wes Morrill confirmed the change was made to the Cybertruck recently after it was spotted by Coleton Guerin of Out of Spec. This particular trim level was a Cyberbeast, but it is being applied to all trims to keep supply chain efficiency high and have less variance across trim levels.

Morrill said that Tesla tested different materials for the underbody panel protection, and carbon fiber performed better than aluminum, which is what the company was using since its first deliveries in 2023.

Additionally, there are some efficiency improvements because Tesla can better form the areas around the bolts to keep underbody airflow cleaner than previously.

Carbon fiber is traditionally lighter and more durable than aluminum, which is why it is such a popular material among luxury automakers, and EV makers will utilize some of the materials around battery packs to save weight.

This is the first instance of Tesla utilizing carbon fiber on the Cybertruck’s exterior to help with overall performance and strength. As previously mentioned, Tesla used aluminum to protect the underside of the body, but it is pretty typical for the company to continue making engineering changes that will improve the car in the future.

Continue Reading

News

Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Published

23 hours ago

on

August 2, 2026

By

Credit: Teslarati

Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.

Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.

For now, here’s everything I noticed with v14.3.7:

Overall Improvement

Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.

The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.

However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.

I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.

The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.

Manual Signal Override is More Responsive

On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.

The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.

Parking Lot Performance

Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.

The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:

 

I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.

Full Self-Driving Averts Disaster

A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:

There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.

However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.

Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.

It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.

What Needs to Improve

Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps

On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.

However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.

I even tried scrolling down into Sloth quickly, but I ended up just taking over:

A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.

Navigation

Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.

Auto Wipers

Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.

You can watch our full review of Tesla Full Self-Driving v14.3.7 below:

Continue Reading