Connect with us

News

SpaceX Starship hop debut aborted at the last second by Raptor engine

A SpaceX Starship prototype was forced to automatically abort a hop debut milliseconds before liftoff. (SpaceX)

Published

on

SpaceX’s full-scale Starship hop debut was aborted at the last second after an otherwise successful lead-up to the milestone, forcing the company to try again tomorrow.

Following a minor delay from August 2nd to August 3rd, SpaceX kicked off Starship SN5’s hop debut preparations relatively late into the 12-hour window, closing the highway and clearing the pad around 5pm CDT (22:00 UTC). The Starship SN5 tank section prototype was pressurized with ambient-temperature gas around the same time, while cryogenic liquid methane and oxygen propellant loading appeared to begin at roughly 6:20pm CDT (23:20 UTC).

Soon after, SpaceX CEO Elon Musk revealed that Starship was just 33 minutes away from launch, marching towards the first hop of a full-scale prototype at 6:56pm CDT. Unfortunately, possibly much less than a second before ignition, Starship SN5’s Raptor engine had different plans.

Musk says that one of Raptor engine SN27’s “spin start valves” failed to open moments before ignition, causing Starship to automatically abort the attempt. With more than an hour left in the window, SpaceX had time to briefly troubleshoot the bug and potentially turn the rocket around for a second attempt, but Musk announced some 50 minutes later that the company would stand down and try again tomorrow.

Musk’s description of the hop test abort sounds suspiciously similar to his description of the last abort of Starship SN5’s Raptor engine static fire test, in which a “fuel spin valve didn’t open.” If the root cause of both aborts is the same, there’s a good chance that SpaceX may need more time to properly investigate and fix the problem. A recurring issue is immediately much more concerning compared to a one-off bug, so there’s also a chance that SpaceX will go as far as replacing the Raptor engine currently installed on Starship SN5.

Advertisement
Raptor SN27 was installed on Starship SN5 around July 3rd or 4th. (NASASpaceflight – bocachicagal)

If things look more severe than SpaceX initially thought they were after the static fire abort and a replacement engine is necessary, Starship SN5 will have to complete another static fire test with the new Raptor before it can proceed to a second hop attempt.

Based on live views of the launch attempt from NASASpaceflight and LabPadre, Starship SN5 likely aborted a matter of milliseconds before Raptor SN27 ignition and perhaps just a second or two before liftoff. Just like SpaceX’s workhorse Falcon 9 and Heavy rockets, the vehicle’s flight computer is fully in control of the countdown a minute or two before liftoff and can automatically abort far faster than any human could possibly react. Held to the launch mount by hold-down clamps, Starship could have technically analyzed the engine’s performance after ignition and aborted the launch even later into the count.

Once hold-down clamp release is commanded, Starship SN5 will attempt to fly a roughly 150m-tall (500 ft) arc heading southeast of the launch mount. Perhaps 10 seconds prior to touchdown, Starship will attempt to deploy an array of six odd legs and gently land a few hundred feet from the pad. As of now, assuming Raptor’s finicky valve can be easily rectified, SpaceX will work towards a second Starship SN5 hop attempt sometime between 8am and 8pm CDT on Tuesday, August 4th.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

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

Investor's Corner

Tesla (TSLA) Q2 2026 earnings results: miss on EPS, beat on revenue

Published

on

Credit: Tesla

Tesla (NASDAQ: TSLA) reported its earnings for the first quarter of 2026 on Wednesday afternoon. Here’s what the company reported compared to what Wall Street analysts expected.

The earnings results come after Tesla reported a massive beat on vehicle deliveries for the second quarter, delivering 489,126 vehicles and building 451,758 cars during the three-month span.

This was a major shock for those on Wall Street as they anticipated somewhere around 400,000 deliveries for the quarter, and showed Tesla still has plenty of demand for its vehicles around the world and in the U.S. despite losing the $7,500 EV Tax Credit last year.

Tesla Q2 2026 Earnings Results

  • Non-GAAP EPS – $0.33 reported vs. $0.53 expected
  • Revenues – $28.236 billion reported vs. $26.4 billion expected
  • Free Cash Flow- -$1.092B
  • Profit -$ 4.751B

Tesla (beat/missed) analyst expectations, so the market response to the company’s quarter is what we will look for next.

Tesla shares closed today down just over 1 percent, trading at $374.01.

In the past, it has been anyone’s guess with what Tesla shares will do after they report earnings. Strong quarters have resulted in sharp drops, while lackluster quarters have seen the stock shoot up considerably.

Tesla will hold its Q2 2026 Earnings Call in about 90 minutes at 5:30 p.m. on the East Coast. Remarks will be made by CEO Elon Musk and other executives, who will shed some light on the investor questions that we covered earlier this week.

You can stream it below. Additionally, we will be doing our Live Blog on X and Facebook.

Continue Reading

Elon Musk

Tesla is about to make parking in busy lots less stressful than ever

Published

on

Tesla FSD 14.3 [Credit: TESLARATI)
Tesla FSD 14.3 [Credit: TESLARATI)

Tesla is about to make parking in busy parking lots at businesses and other points of interest less stressful than ever by allowing drivers more control over where they park and how, CEO Elon Musk confirmed on X.

Tesla has been working to improve the parking performance of vehicles utilizing the Full Self-Driving suite, but now it is looking to add more customization, allowing drivers to choose the specific space they park in, but also potentially the orientation the car pulls into the spot:

Musk has reiterated on X twice over the past several weeks that Tesla is working to make things with the FSD suite based more on the driver’s specific preferences and behaviors that were seen in past drives.

Essentially, it sounds like if you tend to park away from a business to avoid other vehicles, Tesla FSD will soon recognize that preference of yours and start parking further away as well. Additionally, the prospect of assigned parking spaces has been something many owners have voiced concerns about.

Living in a community with assigned parking spaces makes using FSD incredibly difficult as it will rarely park in the correct spot when there are so many to choose from. This is also pertinent in work settings where there are sometimes assigned parking spaces.

The updates to Tesla’s Full Self-Driving suite in terms of listening to driver preferences with parking are also extending to routing. Tesla announced yesterday that with the release of its 2026 Summer Update, it was adding Automatic Navigation and Preferred Routes:

Tesla reveals 2026 Summer Update with crazy fixes to Nav and more

Tesla has always maintained the idea that any human input is bad input, and that, ideally, Tesla Full Self-Driving will always make the right decision. Of course, this is all in theory, but the issue is that so many of Tesla’s interventions have come because it does something that is not necessarily wrong, but perhaps not what the driver would prefer.

Taking these preferences into account will help Tesla alleviate some of the potentially unnecessary interventions that drivers perform.

Continue Reading

News

Tesla starts preparing for Optimus in its smartphone app

Published

on

Tesla is starting to prepare for the launch of the Optimus robot in its smartphone app, new coding strings show. Elon Musk has referred to Optimus as what will be the greatest-selling product of any kind of all time, and now, Tesla is getting ready for its launch.

Tesla’s smartphone app had several first-time mentions of the Optimus program, according to Tesla App Updates, who intially reported on the appearance. Here’s what they found:

A Dedicated “Robot” Phone Key Authentication

Tesla is working on a Bluetooth Low Energy, or BLE, authentication that is specifically for robots. This does not only apply to Optimus, though, as Robotaxi, which is Tesla’s autonomous ride-hailing platform, might also identify vehicles within the fleet as robots as well.

Tesla shows rapid teardown of Model S and X lines, paving the way for Optimus at Fremont

Essentially, pairing your phone as a key to anything Tesla identifies as a robot to a “whitelist” of authorized devices. Optimus, Robotaxi, or other products that fall into this category will only respond if the device trying to communicate with it is authorized.

This is a great security feature that will eliminate at least face-value and low-level threats.

Home Data Collection and System Alerts

This appears to be somewhat of a neural network for Optimus within your house. There will be a dedicated screen that asks for consent to collect both video and spatial data while Optimus performs in-home tasks. Everything from vacuuming, washing dishes, dusting, and other activities will be tracked.

There will also be a comprehensive alert system that will track everything from low battery to mechanical issues.

Other Changes

Most of the changes tracked in this particular app update are related to Tesla’s 2026 Summer Update, and include things such as image assets for new features, a preview of the new custom wraps feature, and other unique features.

You can check out our coverage on what is included with the 2026 Summer Update here:

Tesla reveals 2026 Summer Update with crazy fixes to Nav and more

Continue Reading