Connect with us

News

SpaceX Starship engine test aborted twice in one day by hurricane damage and bugs

Starship SN5 was forced to abort a planned Raptor engine test twice in one day. (NASASpaceflight - bocachicagal)

Published

on

SpaceX has been unable to catch a break in the last few weeks and CEO Elon Musk says that a Starship Raptor engine test was delayed twice in one day by minor hardware bugs and damage caused by Hurricane Hanna.

Although it quickly devolved into a tropical storm and largely missed the southernmost tip of Texas, where SpaceX has built its Starship factory and test facilities, Hanna caused significant damage just a few dozen miles to the north. Above all else, the flooding caused by Hanna has by far been the worst part of the storm. Boca Chica managed to dodge the bulk of that element but was still hit by heavy rain that lasted for a day or two, drenching everything that wasn’t covered and nearly flooding the only access road.

According to Musk, an unspecified “connector” related to Starship SN5 or the pad supporting it was damaged by Hanna’s glancing encounter with SpaceX’s facilities. The connector was ultimately fixed around 7-8 pm CDT per unofficial webcasts showing technicians working around the rocket after they returned to the pad, but SpaceX’s test window technically closed at 8 pm CDT (01:00 UTC).

Nevertheless, SpaceX must have been able to work with local sheriffs to extend that road closure into the night, and – as promised by CEO Elon Musk – testing restarted around 9:30 pm CDT. About an hour and a half later, Starship SN5 appeared to make it all the way through a partial wet dress rehearsal before its Raptor engine test fire was aborted a second time. Based on four static fires completed by Starship SN4 in May 2020, the rocket could have been just a few minutes away from ignition.

Advertisement

According to Musk, Starship SN5’s fuel (methane) “spin valve” – presumably a valve that opens to allow methane gas to spin up Raptor’s fuel turbopump – failed to open when it was supposed to. To ensure Raptor’s health after three inactive weeks spent installed on Starship out in the elements, SpaceX likely planned what is known as a “spin prime” test directly prior to the static fire. If Raptor successfully spun up its turbopumps, SpaceX would proceed directly into static fire operations without having to detank Starship.

During SN5’s second July 27th static fire attempt, Raptor was unable to start that spin prime test, forcing SpaceX to stand down to diagnose and fix the problem. Musk says that SpaceX will attempt to static fire Starship SN5 again tomorrow (July 28th) – assuming the issue can be quickly rectified.

Raptor SN27 was installed on Starship SN5 around July 3rd or 4th. (NASASpaceflight – bocachicagal)
Starship SN5 was forced to wait several weeks after its first cryogenic proof test to begin more challenging tests with a Raptor engine and real methane/oxygen propellant. (NASASpaceflight – bocachicagal)

Musk further noted that some “odd…behavior” was observed in the hydraulic pump powering Raptor SN27’s thrust vector control (TVC). Used to steer a rocket engine, Raptor doesn’t technically need functioning TVC to perform a static fire test on the ground, but it’s an issue that will have to be completely fixed before Starship SN5 is allowed to attempt its first flight test. If July 28th finally sees SN5 successfully ignite its Raptor engine, there’s a chance – however slim – that SpaceX will be able to turn the Starship around for its first hop just a few days later.

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

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

SpaceX adjusts Starship Flight 13 test launch target date once again

Published

on

Credit: SpaceX

SpaceX has updated its target for the thirteenth integrated flight test of Starship, aiming for as early as Thursday, July 23. The 90-minute launch window opens at 5:45 p.m. CT from the company’s Starbase facility in South Texas.

The target flight was initially rescheduled for today, but SpaceX pushed it back again.

This latest adjustment follows an aborted attempt earlier in the week and reflects the iterative, rapid-development approach that has defined the Starship program. With the vehicle already stacked and ground teams making final preparations, the mission represents another step toward proving the full reusability of the world’s most powerful rocket system.

The original launch attempt on July 16 was scrubbed at T-0 when several Raptor engines on the Super Heavy booster failed to ignite properly. The automatic abort system triggered just as the engines began their startup sequence, preventing liftoff.

SpaceX CEO Elon Musk confirmed that some engines did not start as expected, prompting the decision to replace two Raptors on Booster 20 to ensure reliability. The issue occurred despite a successful full-duration static fire earlier, highlighting the complexities of coordinating 33 engines under flight conditions.

This cautious approach underscores SpaceX’s commitment to safety amid an aggressive test cadence.

SpaceX comes with a slew of changes for Starship Flight 13

Flight 13 builds directly on the lessons from Flight 12 in May 2026. The Super Heavy booster’s primary goals include a successful liftoff, ascent, stage separation, boostback burn, and controlled splashdown in the Gulf of America.

Hardware and software modifications address the off-nominal flip and boostback burn problems from the prior flight, where propellant slosh and engine relight issues led to an uncontrolled impact.

For the Starship upper stage, objectives include deploying 20 operational Starlink V3 satellites, the first real payload of this type, performing a single Raptor engine relight in space, and executing a controlled entry, descent, and splashdown in the Indian Ocean. Propulsion upgrades aim to improve engine-out capability after one vacuum Raptor was lost on Flight 12.

Additional test elements focus on heat shield performance. Six satellites carry cameras to image the tiles during flight, while white-painted tiles and upgraded attachments on flaps and the aft skirt will gather data for future reusability.

The FAA completed its mishap investigation into Flight 12 earlier this month, clearing the regulatory path.

This suborbital mission, the second with V3 vehicles, advances Starship toward operational missions, including potential crewed flights and support for NASA’s Artemis program. Success would mark significant progress in rapid reusability and satellite deployment from the massive system.

Continue Reading

News

Elon Musk debunks $52 billion SpaceX-NVIDIA GPU deal

Published

on

Credit: SpaceX

Elon Musk dismissed reports claiming SpaceX had placed a massive order for NVIDIA GPUs worth $52 billion. The denial came hours after Taiwanese media, citing unnamed industry sources, reported that SpaceX planned to acquire approximately 13,000 AI server racks, equating to roughly 1 million GB300 GPUs, from Foxconn.

Each rack was estimated at around $4 million, with deliveries potentially starting in late 2025.

The story suggested this would mark SpaceX’s first major foray into Foxconn-manufactured NVIDIA hardware, breaking from suppliers like Supermicro and Dell. Musk responded bluntly on X:

Despite the denial, the rumored scale aligns with SpaceX’s explosive growth in AI infrastructure. NVIDIA’s GB300 (successor to the GB200 NVL) racks deliver unprecedented performance for large-scale training and inference. A $52 billion commitment would dwarf most corporate AI budgets and provide the compute muscle needed for frontier models.

SpaceX already operates gigawatt-scale terrestrial clusters like Colossus in Memphis, Tennessee, and has monetized them aggressively through leasing deals.

SpaceX’s newest Starmind will make earth data centers obsolete

Major customers include Anthropic (paying ~$1.25 billion monthly for 220,000+ GPUs), Google (~$920 million monthly for 110,000 GPUs), and Reflection AI. These arrangements are projected to generate tens of billions in annual revenue, far outpacing traditional SpaceX businesses.

Such an investment would fuel internal AI efforts, particularly Grok models under the integrated SpaceXAI division, while supporting ambitious orbital data center plans. SpaceX envisions launching thousands of AI-optimized satellites powered by solar energy and cooled in space, bypassing terrestrial power and land constraints.

This “Starmind” constellation could position the company as a leader in space-based computing.

SpaceX as an Emerging AI Powerhouse

Once primarily known for reusable rockets and Starlink satellite internet, SpaceX has transformed into a multifaceted AI player.

The 2026 acquisition of xAI integrated Grok development directly into the company. Starlink’s low-latency global network complements massive compute clusters, enabling efficient data flow for training and serving AI models.

Musk has long argued that AI scaling demands solutions beyond Earth, citing things like real estate and electricity limits on the ground.

While the Foxconn deal may not be in the cards, SpaceX’s trajectory is continuing on the path of blending aerospace engineering with hyperscale AI to dominate both launches and intelligence infrastructure.

Continue Reading

Elon Musk

Elon Musk sheds details on Tesla FSD’s upcoming improvements

Published

on

Credit: Tesla

Elon Musk shed more details on the upcoming improvements to Tesla’s Full Self-Driving suite, specifically one that the CEO mentioned last week, which should help owners see fewer interventions.

Last week, Musk hinted that one major improvement that Tesla planned to roll out to Full Self-Driving users was the car’s ability “to remember your specific interventions and match each person’s individual preferences.”

Elon Musk says your Tesla will start to learn your individual preferences

This small bit of detail was linked to a post from Tesla community member Whole Mars, who said that FSD’s tendency to exit the carpool lane, a feature that owners can turn on but at times the car will disregard.

It sounds like, based on Musk’s two responses since that original post, it is safe to say the things FSD will start to remember are wide-ranging. However, it seems the biggest differences will be noticed with parking performance, which Musk continues to mention.

Highway Lane Preferences

The initial post Musk mentioned, with these new remembered preferences soon to arrive for Tesla owners everywhere, was the Carpool/Express Lane.

Tesla has a setting in the FSD menu that lets drivers enable HOV Lane travel. However, the car won’t always stay in that suggested or preferred lane.

Some owners have also complained of left lane camping, an illegal maneuver in at least some states. Cruising in the passing lane has resulted in tickets for some, as it is illegal in over 30 states in the U.S.

Tesla did not confirm if these preferences would also be included in new FSD behaviors, but it would certainly help move the company toward fewer interventions.

Parking Preferences

This seems to be the real focus of the entire operation, as Musk stated several weeks ago that parking was overwhelmingly the most frequent reason for interventions.

The major issue with parking is not necessarily the parking “performance,” as FSD is generally good at parking. It definitely has its issues; we’ve recorded plenty of them, including this one as recent as last week:

However, the changes coming are more about preferences, meaning where you park and how your car enters the spot, either pulling in or backing in. Owners have also reported that pulling into the correct driveway is a relatively rare thing for FSD, something else that needs to be confronted.

Musk basically confirmed that all of these things would be part of Tesla’s plan to address driver preferences with FSD:

It’s obvious there is something big coming with FSD, and the company’s focus seems to be eliminating any intervention that would be related to preferences. This is probably the biggest bottleneck between Tesla and being fully autonomous. Critical interventions do occur, but they are much less frequent.

The only time a driver should be taking over is because of a critical intervention; this seems to be the goal of Tesla right now.

This all seems to be a priority as Tesla continues to move closer to the prospect of unsupervised driving.

Continue Reading