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.

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 Robotaxi gets a massive upgrade in Nevada

Nevada regulators just approved a massive expansion of Tesla’s robotaxi fleet across the entire county.

Published

on

By

Concept art of a Tesla Cybercab in Las Vegas Strip as rendered via Grok

Tesla’s robotaxi footprint in Nevada just grew by roughly 500 times in a single regulatory vote.

The Nevada Transportation Authority approved Tesla’s full Autonomous Vehicle Network Company permit on Thursday, clearing the way for the company to deploy up to 5,000 driverless vehicles across Clark County over the next 12 months. The decision came during a four hour general session meeting that Tesla investor Sawyer Merritt watched live and reported on X, noting the vote replaces the interim order that had limited Tesla to just 10 robotaxis on a narrow stretch of the Las Vegas Strip.

That earlier cap, covered here after it surfaced on August 13, came with restrictions that looked stricter than what Tesla runs in Austin: a 45 mph speed ceiling, no airport pickups, and a geofence confined to the Strip corridor. The new approval extends Tesla’s operating authority to all of Clark County, with room to request an even wider geofence across the state.

Tesla representatives at the meeting said they have no intention of putting 5,000 cars on the road right away. Commercial rides are expected to start within 30 days, pending vehicle inspections, insurance filings, and fare approval, the standard steps every robotaxi operator in Nevada has had to clear.

Tesla’s own Robotaxi account replied to the news with a short line, The golden future is upon us.

The timing lines up with Tesla’s broader robotaxi push this month. The company is preparing to open Cybercab rides to the public in Austin as soon as this month, and it opened a sweepstakes for riders to win a seat at the launch event. Tesla filed its original application for a 5,000 vehicle Nevada fleet back in June, a request regulators trimmed to 10 vehicles when they issued the interim order in July. Thursday’s vote effectively grants the number Tesla asked for from the start.

Zoox, the Amazon owned robotaxi operator, has run in Nevada since 2025 and was capped at 100 vehicles before Thursday’s decision. Tesla’s new ceiling puts it well ahead of that comparison on paper, though the company has said its actual fleet size will depend on how quickly FSD v15 rolls out, the software update executives have called the gateway to scaling unsupervised robotaxi operations nationwide.

Continue Reading

News

Tesla admits to slow Model Y Robotaxi integration, but for a good reason

Published

on

Credit: Tesla

Tesla welcomed JPMorgan analysts to one of its factories earlier this month, with the Wall Street firm highlighting its findings in a new note to investors. One of the more pertinent pieces of information is that Tesla admitted to slowly integrating Model Y vehicles into its Robotaxi fleet, but it has a good reason.

JPMorgan analysts recently toured Tesla’s Fremont Factory and met with the company’s investor relations team, emerging with a clearer picture of the automaker’s Robotaxi strategy. According to the bank’s note, Tesla is intentionally limiting the addition of Model Y vehicles to its existing Robotaxi fleet.

The firm’s analysts said:

“Tesla indicated it is intentionally holding back on adding Model Y units to the robotaxi fleet, expressing confidence in its ability to scale Cybercab in the near-term. On FSD V15, Tesla views this release as a step-change in performance, comparable to the leap from V13 to V14. The V15 upgrade encompasses seven core technologies, with ~40% of those currently being tested in the robotaxi fleet, where initial feedback has been encouraging.”

Far from signaling delays or doubts about autonomy, the move reflects strong management confidence in the near-term scalability of the purpose-built Cybercab.

Tesla has operated its Robotaxi service primarily with modified Model Ys since launching in Austin and expanding to other markets. Yet the company is now deliberately holding back further Model Y conversions. The rationale is straightforward: leadership believes the Cybercab, a two-seat, steering-wheel- and pedal-free vehicle optimized for high utilization, can ramp production and deployment more efficiently in the coming months.

This dedicated form factor promises better unit economics for the majority of rides, which typically involve one or two passengers, while freeing consumer Model Y inventory for retail sales.

Supporting this pivot is Full Self-Driving (FSD) software version 15, which Tesla describes as a genuine step-change in performance, comparable to the leap from V13 to V14. The update incorporates seven core technologies; roughly 40 percent are already undergoing real-world testing in the current Robotaxi fleet, with early feedback described as encouraging.

Tesla is carefully managing software development to minimize regressions in core driving functions as new capabilities are added. Management positions V15 as the primary gateway to scaling unsupervised FSD. Importantly, the existing AI and Hardware 4 stack is already capable of running V15 and supporting unsupervised operation.

Cybercab itself is only the first vehicle on the platform. Tesla reiterated that additional form factors will follow, pointing to concepts such as the earlier “Robovan” demonstration as examples of how the architecture can evolve.

Tesla’s mysterious Robovan makes a sneak peek with Optimus in Terafab video

Parallel progress continues on the Optimus humanoid robot, which remains on track for start of production in the coming months, with commercial sales possible as early as the second half of 2027. Generation 3 details will be revealed closer to production to preserve competitive advantages, while Generation 4 scope will draw on real-world Gen 3 experience.

JPMorgan left the meeting with a deeper appreciation for Tesla’s manufacturing automation and maintained its $475 price target. The decision to slow Model Y Robotaxi integration is therefore not a setback but a calculated prioritization of a more efficient, purpose-built solution that management believes is ready to scale.

Continue Reading

Elon Musk

Elon Musk gives a timeline for SpaceX’s first Starship catch attempt

Published

on

SpaceX Starship V3 from Starbase, Texas on April 14, 2026

SpaceX CEO Elon Musk announced today that the company will likely attempt to catch the Starship upper stage with its launch tower arms “in a few months.”

In a post on X, Musk wrote, “Looks like we will probably catch the ship with the tower in a few months. If there had been a tower out to sea where we practiced landing the ship, it would have been caught.” He added that the first reflight of a Starship vehicle is expected by the end of 2026 or early 2027, describing it as “a fork in the road of history for consciousness reaching the stars.”

Musk’s prediction comes amid ongoing progress toward full reusability of the Starship system, a two-stage rocket designed for rapid turnaround and dramatically lower launch costs. Catching the upper stage, known simply as “ship,” with the Mechazilla tower’s mechanical arms would mark a major milestone. It would allow both stages to return directly to the launch site for quick refurbishment and reuse, eliminating the need for ocean recovery.

Musk has previously signaled plans for a ship catch. In July, shortly after SpaceX’s wildly successful Starship 13 mission, he stated that the company would attempt to catch the ship with the tower on the next flight unless problems emerged in the mission data review. Earlier comments also outline conditions such as successful soft ocean landings before attempting a land recovery to minimize risk.

SpaceX has solved Starship’s biggest challenge, Elon Musk says

The latest update from Musk adjusts this timeline to a few months, reflecting the iterative nature of the test campaign.

SpaceX has already demonstrated the tower catch technique successfully with the Super Heavy booster on a couple of occasions. The first successful booster catch occurred during Flight 5 in October 2024, when the massive first stage returned to the Starbase pad in Texas and was plucked from the air by the tower arms.

Additional catches followed on later flights, including Flight 7, proving the concept for the booster and building confidence in the system as a whole.

Achieving a similar catch for the upper stage would represent a significant step forward. The ship returns from much higher speeds and greater heat loads after orbital or near-orbital flight. Success would advance SpaceX’s goal of full and rapid reusability, potentially reducing the cost of access to orbit by a factor of 100 or more and supporting ambitions for frequent satellite deployments, lunar missions, and eventual Mars flights.

Musk has long emphasized that true reusability, refueling rather than discarding hardware, is essential for making humanity a multi-planetary species.

As SpaceX continues refining Starship through successive test flights, the coming months will test whether the ambitious catch timeline can be met. The combination of prior booster successes and improving ship landing precision suggests the company is steadily closing in on this historic capability.

Continue Reading