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

5 years ago

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.

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 removes Safety Monitors, begins fully autonomous Robotaxi testing

This development, in terms of the Robotaxi program, is massive. Tesla has been working incredibly hard to expand its fleet of Robotaxi vehicles to accommodate the considerable demand it has experienced for the platform.

Published

8 hours ago

on

December 14, 2025

By

Credit: @Mandablorian | X

Tesla has started Robotaxi testing in Austin, Texas, without any vehicle occupants, the company’s CEO Elon Musk confirmed on Sunday. Two Tesla Model Y Robotaxi units were spotted in Austin traveling on public roads with nobody in the car.

The testing phase begins just a week after Musk confirmed that Tesla would be removing Safety Monitors from its vehicles “within the next three weeks.” Tesla has been working to initiate driverless rides by the end of the year since the Robotaxi fleet was launched back in June.

Two units were spotted, with the first being seen from the side and clearly showing no human beings inside the cabin of the Model Y Robotaxi:

Another unit, which is the same color but was confirmed as a different vehicle, was spotted just a few moments later:

The two units are traveling in the general vicinity of the South Congress and Dawson neighborhoods of downtown Austin. These are located on the southside of the city.

This development, in terms of the Robotaxi program, is massive. Tesla has been working incredibly hard to expand its fleet of Robotaxi vehicles to accommodate the considerable demand it has experienced for the platform.

However, the main focus of the Robotaxi program since its launch in the Summer was to remove Safety Monitors and initiate completely driverless rides. This effort is close to becoming a reality, and the efforts of the company are coming to fruition.

It is a drastic step in the company’s trek for self-driving technology, as it plans to expand it to passenger vehicles in the coming years. Tesla owners have plenty of experience with the Full Self-Driving suite, which is not fully autonomous, but is consistently ranked among the best-performing platforms in the world.

Continue Reading

News

Tesla refines Full Self-Driving, latest update impresses where it last came up short

We were able to go out and test it pretty extensively on Saturday, and the changes Tesla made from the previous version were incredibly impressive, especially considering it seemed to excel where it last came up short.

Published

19 hours ago

on

December 14, 2025

By

Credit: TESLARATI

Tesla released Full Self-Driving v14.2.1.25 on Friday night to Early Access Program (EAP) members. It came as a surprise, as it was paired with the release of the Holiday Update.

We were able to go out and test it pretty extensively on Saturday, and the changes Tesla made from the previous version were incredibly impressive, especially considering it seemed to excel where it last came up short.

Tesla supplements Holiday Update by sneaking in new Full Self-Driving version

With Tesla Full Self-Driving v14.2.1, there were some serious regressions. Speed Profiles were overtinkered with, causing some modes to behave in a strange manner. Hurry Mode was the most evident, as it refused to go more than 10 MPH over the speed limit on freeways.

It would routinely hold up traffic at this speed, and flipping it into Mad Max mode was sort of over the top. Hurry is what I use most frequently, and it had become somewhat unusable with v14.2.1.

It seemed as if Speed Profiles should be more associated with both passing and lane-changing frequency. Capping speeds does not help as it can impede the flow of traffic. When FSD travels at the speed of other traffic, it is much more effective and less disruptive.

With v14.2.1.25, there were three noticeable changes that improved its performance significantly: Speed Profile refinements, lane change confidence, and Speed Limit recognition.

Speed Profile Refinement

Speed Profiles have been significantly improved. Hurry Mode is no longer capped at 10 MPH over the speed limit and now travels with the flow of traffic. This is much more comfortable during highway operation, and I was not required to intervene at any point.

With v14.2.1, I was sometimes assisting it with lane changes, and felt it was in the wrong place at the wrong time more frequently than ever before.

However, this was one of the best-performing FSD versions in recent memory, and I really did not have any complaints on the highway. Speed, maneuvering, lane switching, routing, and aggressiveness were all perfect.

Lane Changes

v14.2.1 had a tendency to be a little more timid when changing lanes, which was sort of frustrating at times. When the car decides to change lanes and turn on its signal, it needs to pull the trigger and change lanes.

It also changed lanes at extremely unnecessary times, which was a real frustration.

There were no issues today on v14.2.1.25; lane changes were super confident, executed at the correct time, and in the correct fashion. It made good decisions on when to get into the right lane when proceeding toward its exit.

It was one of the first times in a while that I did not feel as if I needed to nudge it to change lanes. I was very impressed.

Speed Limit Recognition

So, this is a complex issue. With v14.2.1, there were many times when it would see a Speed Limit sign that was not meant for the car (one catered for tractor trailers, for example) or even a route sign, and it would incorrectly adjust the speed. It did this on the highway several times, mistaking a Route 30 sign for a 30 MPH sign, then beginning to decelerate from 55 MPH to 30 MPH on the highway.

This required an intervention. I also had an issue leaving a drive-thru Christmas lights display, where the owners of the private property had a 15 MPH sign posted nearly every 200 yards for about a mile and a half.

The car identified it as a 55 MPH sign and sped up significantly. This caused an intervention, and I had to drive manually.

It seems like FSD v14.2.1.25 is now less reliant on the signage (maybe because it was incorrectly labeling it) and more reliant on map data or the behavior of nearby traffic.

A good example was on the highway today: despite the car reading that Route 30 sign and the Speed Limit sign on the center screen reading 30 MPH, the car did not decelerate. It continued at the same speed, but I’m not sure if that’s because of traffic or map data:

A Lone Complaint

Tesla has said future updates will include parking improvements, and I’m really anxious for them, because parking is not great. I’ve had some real issues with it over the past couple of months.

Today was no different:

Full Self-Driving v14.2.1.25 is really a massive improvement over past versions, and it seems apparent that Tesla took its time with fixing the bugs, especially with highway operation on v14.2.1.

Continue Reading

News

Tesla hints at Starlink integration with recent patent

“By employing polymer blends, some examples enable RF transmission from all the modules to satellites and other communication devices both inside and outside the vehicle.”

Published

2 days ago

on

December 13, 2025

By

Credit: Grok

Tesla hinted at a potential Starlink internet terminal integration within its vehicles in a recent patent, which describes a vehicle roof assembly with integrated radio frequency (RF) transparency.

The patent, which is Pub. No U.S. 2025/0368267 describes a new vehicle roof that is made of RF-transparent polymer materials, allowing and “facilitating clear communication with external devices and satellites.”

Tesla believes that a new vehicle roof design, comprised of different materials than the standard metallic or glass elements used in cars today, would allow the company to integrate modern vehicular technologies, “particularly those requiring radio frequency transmission and reception.

Instead of glass or metallic materials, Tesla says vehicles may benefit from high-strength polymer blends, such as Polycarbonate, Acrylonitrile Butadiene Styrene, or Acrylonitrile Styrene Acrylate.

These materials still provide ideal strength metrics for crashworthiness, stiffness for noise, vibration, and harshness control, and are compliant with head impact regulations.

They would also enable better performance with modern technologies, like internet terminals, which need an uninterrupted signal to satellites for maximum reception. Tesla writes in the patent:

“By employing polymer blends, some examples enable RF transmission from all the modules to satellites and other communication devices both inside and outside the vehicle.”

One of the challenges Tesla seems to be aware of with this type of roof design is the fact that it will still have to enable safety and keep that at the forefront of the design. As you can see in the illustration above, Tesla plans to use four layers to increase safety and rigidity, while also combating noise and vibration.

It notes in the patent that disclosed examples still meet the safety requirements outlined in the Federal Motor Vehicle Safety Standards (FMVSS).

Starlink integrated directly into Tesla vehicles would be a considerable advantage for owners. It would come with a handful of distinct advantages.

Initially, the inclusion of Starlink would completely eliminate cellular dead zones, something that is an issue, especially in rural areas. Starlink would provide connectivity in these remote regions and would ensure uninterrupted service during road trips and off-grid adventures.

It could also be a critical addition for Robotaxi, as it is crucial to have solid and reliable connectivity for remote monitoring and fleet management.

Starlink’s growing constellation, thanks to SpaceX’s routine and frequent launch schedule, will provide secure, stable, and reliable internet connectivity for Tesla vehicles.

SpaceX reaches incredible milestone with Starlink program

Although many owners have already mounted Starlink Mini dishes under their glass roofs for a similar experience, it may be integrated directly into Teslas in the coming years, either as an upgrade or a standard feature.

Continue Reading