Connect with us

News

SpaceX aborts several Starship static fire attempts, rolls test tank to the pad

Still plagued by aborts and delays, Starship SN9 sits to the right of test tank SN7.2 on January 20th. (NASASpaceflight - bocachicagal)

Published

on

Accidentally producing the polar opposite of Starship serial number 9 (SN9) completing a trio of Raptor ignition tests in four hours last week, SpaceX has now suffered three back-to-back static fire aborts on January 20th.

On January 13th, Starship SN9 somewhat successfully ignited its Raptor engines three separate times with zero hands-on human intervention or inspection. While an impressive feat, SpaceX CEO Elon Musk soon revealed that two of the rocket’s three engines were damaged during the test campaign. NASASpaceflight.com later reported that the company had detected an issue with one Raptor after the first three-engine static fire, ultimately firewalling it and performing the next two static fires with only two engines.

SpaceX initially allotted five days to replace the two damaged Raptors (SN44 & SN46), scheduling road closures (a telltale sign of test plans) on January 18th, 19th, and 20th. Windows on the 18th and 19th went by with zero attempts. Finally, on the 20th, SpaceX kicked off Starship SN9’s first real test attempt since the engine swap around 2pm but it was aborted by 3pm.

After an extremely brisk recycle, Starship likely made it less than a minute away from ignition but the second attempt was ultimately aborted around 3:40 pm.

Two hours later, after SpaceX extended the end of its road closure from 5pm to 8pm, Starship SN9’s third Raptor static fire attempt was also aborted – once again just a minute or less away from ignition.

Advertisement
-->

SpaceX held Starship SN9 for another hour or so after the third abort but ultimately began final detanking and depressurization around 6:50 pm, marking the end of the day’s attempts.

It’s impossible to say what caused Wednesday’s back-to-back-to-back aborts or if the three instances were connected. While potentially frustrating to watch from the sidelines, it’s crucial to remember that the public is getting a truly unprecedented continuous view of SpaceX’s process of developing and refining a world-class launch vehicle. Additionally, every abort Starship suffers should theoretically produce volumes of valuable data that both Starship and Raptor teams can use to better understand how to design, build, test, and operate the cutting-edge vehicle and its engines.

More likely than not, SpaceX is leaning towards caution (and thus cautious hardware and software limits) while attempting to prepare Starship SN9 for its true data-gathering purpose – an SN8-style high-altitude launch and landing attempt.

Starship SN8’s launch and (explosive) landing debut. SN9’s goal is to replicate the feat without the last-second explosion. (Richard Angle)

SpaceX is currently scheduled to try again with another series of Starship SN9 static fire attempts between 8am and 5pm CST (UTC-6) on Thursday, January 21st.

Meanwhile, prior to SN9’s multiple Wednesday aborts, SpaceX rolled the latest in a series of Starship ‘test tanks’ from the factory to the launch pad. A team rapidly strapped the tank to the concrete pad and connected it to ground support equipment in preparation for a series of tests that will likely end with SpaceX intentionally pressurizing the tank until its bursts. If successful, it will open the door for future Starships to save weight by cutting steel skin thickness from 4mm to 3mm.

Stay tuned for updates on both active test campaigns.

Advertisement
-->

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 FSD and Robotaxis are making people aware how bad human drivers are

These observations really show that Tesla’s focus on autonomy would result in safer roads for everyone.

Published

on

Credit: Tesla

Tesla FSD and the Robotaxi network are becoming so good in their self-driving performance, they are starting to highlight just how bad humans really are at driving. 

This could be seen in several observations from the electric vehicle community.

Robotaxis are better than Uber, actually

Tesla’s Robotaxi service is only available in Austin and the Bay Area for now, but those who have used the service have generally been appreciative of its capabilities and performance. Some Robotaxi customers have observed that the service is simply so much more affordable than Uber, and its driving is actually really good.

One veteran Tesla owner, @BLKMDL3, recently noted that the Robotaxi service has become better than Uber simply because FSD now drives better than some human drivers.  Apart from the fact that Robotaxis allow riders to easily sync their phones to the rear display, the vehicles generally provide a significantly more comfortable ride than their manually-driven counterparts from Uber.

FSD is changing the narrative, one ride at a time

It appears that FSD V14 really is something special. The update has received wide acclaim from users since it was released, and the positive reactions are still coming. This was highlighted in a recent post from Tesla owner Travis Nicolette, who shared a recent experience with FSD. As per the Tesla owner, he was quite surprised as his car was able to accomplish a U-turn in a way that exceeded human drivers.

Advertisement
-->

Yet another example of FSD’s smooth and safe driving was showcased in a recent video, which showed a safety monitor of a Bay Area Robotaxi falling asleep in the driver’s seat. In any other car, a driver falling asleep at the wheel could easily result in a grave accident, but thanks to FSD, both the safety monitor and the passengers remained safe.

These observations, if any, really show that Tesla’s focus on autonomy would result in safer roads for everyone. As per the IIHS, there were 40,901 deaths from motor vehicle crashes in the United States in 2023. The NHTSA also estimated that in 2017, 91,000 police-reported crashes involved drowsy drivers. These crashes led to an estimated 50,000 people injured and 800 deaths. FSD could lower all these tragic statistics by a notable margin.

Continue Reading

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