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

News

Tesla lands approval for Robotaxi operation in third U.S. state

On Tuesday, Tesla officially received regulatory approval from the State of Arizona, making it the third state for the company to receive approval in.

Published

on

Tesla has officially landed approval to operate its Robotaxi ride-hailing service in its third U.S. state, as it has landed a regulatory green light from the State of Arizona’s Department of Transportation.

Tesla has been working to expand to new U.S. states after launching in Texas and California earlier this year. Recently, it said it was hoping to land in Nevada, Arizona, and Florida, expanding to five new cities in those three states.

On Tuesday, Tesla officially received regulatory approval from the State of Arizona, making it the third state for the company to receive approval in:

Tesla has also been working on approvals in Nevada and Florida, and it has also had Robotaxi test mules spotted in Pennsylvania.

The interesting thing about the Arizona approval is the fact that Tesla has not received an approval for any specific city; it appears that it can operate statewide. However, early on, Tesla will likely confine its operation to just one or two cities to keep things safe and controlled.

Over the past few months, Robotaxi mules have been spotted in portions of Phoenix and surrounding cities, such as Scottsdale, as the company has been attempting to cross off all the regulatory Ts that it is confronted with as it attempts to expand the ride-hailing service.

It appears the company will be operating it similarly to how it does in Texas, which differs from its California program. In Austin, there is no Safety Monitor in the driver’s seat, unless the route requires freeway travel. In California, there is always a Safety Monitor in the driver’s seat. However, this is unconfirmed.

Earlier today, Tesla enabled its Robotaxi app to be utilized for ride-hailing for anyone using the iOS platform.

Continue Reading

News

Tesla ride-hailing Safety Monitor dozes off during Bay Area ride

We won’t try to blame the camera person for the incident, because it clearly is not their fault. But it seems somewhat interesting that they did not try to wake the driver up and potentially contact Tesla immediately to alert them of the situation.

Published

on

Credit: u/ohmichael on Reddit

A Tesla Robotaxi Safety Monitor appeared to doze off during a ride in the California Bay Area, almost ironically proving the need for autonomous vehicles.

The instance was captured on camera and posted to Reddit in the r/sanfrancisco subreddit by u/ohmichael. They wrote that they have used Tesla’s ride-hailing service in the Bay Area in the past and had pleasant experiences.

However, this one was slightly different. They wrote:

“I took a Tesla Robotaxi in SF just over a week ago. I have used the service a few times before and it has always been great. I actually felt safer than in a regular rideshare.

This time was different. The safety driver literally fell asleep at least three times during the ride. Each time the car’s pay attention safety alert went off and the beeping is what woke him back up.

I reported it through the app to the Robotaxi support team and told them I had videos, but I never got a response.

I held off on posting anything because I wanted to give Tesla a chance to respond privately. It has been more than a week now and this feels like a serious issue for other riders too.

Has anyone else seen this happen?”

Advertisement

-->

My Tesla Robotaxi “safety” driver fell asleep
byu/ohmichael insanfrancisco

The driver eventually woke up after prompts from the vehicle, but it is pretty alarming to see someone like this while they’re ultimately responsible for what happens with the ride.

We won’t try to blame the camera person for the incident, because it clearly is not their fault. But it seems somewhat interesting that they did not try to wake the driver up and potentially contact Tesla immediately to alert them of the situation.

They should have probably left the vehicle immediately.

Tesla’s ride-hailing service in the Bay Area differs from the one that is currently active in Austin, Texas, due to local regulations. In Austin, there is no Safety Monitor in the driver’s seat unless the route requires the highway.

Tesla plans to remove the Safety Monitors in Austin by the end of the year.

Continue Reading

News

Tesla opens Robotaxi access to everyone — but there’s one catch

Published

on

Credit: Tesla

Tesla has officially opened Robotaxi access to everyone and everyone, but there is one catch: you have to have an iPhone.

Tesla’s Robotaxi service in Austin and its ride-hailing service in the Bay Area were both officially launched to the public today, giving anyone using the iOS platform the ability to simply download the app and utilize it for a ride in either of those locations.

It has been in operation for several months: it launched in Austin in late June and in the Bay Area about a month later. In Austin, there is nobody in the driver’s seat unless the route takes you on the freeway.

In the Bay Area, there is someone in the driver’s seat at all times.

The platform was initially launched to those who were specifically invited to Austin to try it out.

Tesla confirms Robotaxi is heading to five new cities in the U.S.

Slowly, Tesla launched the platform to more people, hoping to expand the number of rides and get more valuable data on its performance in both regions to help local regulatory agencies relax some of the constraints that were placed on it.

Additionally, Tesla had its own in-house restrictions, like the presence of Safety Monitors in the vehicles. However, CEO Elon Musk has maintained that these monitors were present for safety reasons specifically, but revealed the plan was to remove them by the end of the year.

Now, Tesla is opening up Robotaxi to anyone who wants to try it, as many people reported today that they were able to access the app and immediately fetch a ride if they were in the area.

We also confirmed it ourselves, as it was shown that we could grab a ride in the Bay Area if we wanted to:

The launch of a more public Robotaxi network that allows anyone to access it seems to be a serious move of confidence by Tesla, as it is no longer confining the service to influencers who are handpicked by the company.

In the coming weeks, we expect Tesla to then rid these vehicles of the Safety Monitors as Musk predicted. If it can come through on that by the end of the year, the six-month period where Tesla went from launching Robotaxi to enabling driverless rides is incredibly impressive.

Continue Reading