News
SpaceX Starship aborts Raptor engine test, briefly catches fire
Update: On March 15th, SpaceX got within milliseconds of Starship serial number 11’s (SN11) first Raptor engine test but suffered an abort just before full ignition, briefly leaving the rocket on fire.
Around 12:26 pm CDT, after an otherwise nominal static fire flow, Starship SN11 momentarily ignited one or two of its three Raptor engines’ preburners, referring to a central component that burns cryogenic liquid propellant into gas that’s ready for combustion. As with all preburner tests, intentional or otherwise, the end result looked a bit like a weak static fire and produced a small but visible amount of flame and thrust. Unlike intentional preburner tests, the static fire abort seemingly ignited something hidden inside Starship SN11’s and appeared to burn for at least another 30-40 seconds.
Raptor has proven itself to be an extremely durable engine, up to and including surviving visible onboard fires during actual Starship flight tests. Nevertheless, depending on the source of SN11’s post-abort fire and what it may or may not have burned or damaged, it’s no surprise that SpaceX ended testing for the day instead of quickly trying again, which it’s done several times prior. If the fire was largely harmless, SpaceX has already distributed notices suggesting a second attempt could happen as early as 6am to 12pm CDT (UTC-5) on Tuesday, March 16th. If more time is needed, SpaceX has the rest of the week to conduct any necessary repairs or swap out SN11’s Raptor engines.
Public documents show that SpaceX has plans to static fire and launch its latest Starship prototype within a two-day period that could begin later today.
SpaceX shipped Starship SN11 from its Boca Chica, Texas rocket factory to test and launch facilities a mile down the road on March 8th, less than five days after Starship SN10 exploded minutes after touchdown. The very next day, SpaceX completed ambient-temperature proof testing, filling Starship with benign nitrogen gas to check for leaks and verify system health. Two days after that, Starship SN11 appeared to complete a several-hour cryogenic proof test – swapping nitrogen gas for its supercool liquid form – without issue.
Despite the seemingly successful ‘cryo proof,’ something prevented a subsequent static fire test planned on March 12th before any attempt could be made, delaying the next attempt until after the approaching weekend. An agreement between SpaceX, Cameron County, and the state of Texas currently prevents road closures (and thus rocket testing) on weekends falling between Labor Day and Memorial Day, rules meant to preserve some level of public access to Boca Chica Beach.
As a result, unless SpaceX is already ready to launch (it has waivers for three such weekend closures for launch attempts), the company has to wait until Monday even if a minor issue fixable in hours or a day or so scrubs Friday test plans. While inconvenient, it’s worth noting that the existence of that public beach and the strong regulations that protect its public domain is likely one of the only reasons the general public can still get as close as they can to SpaceX’s Boca Chica ‘Starbase’.
For whatever reason, that road closure agreement does still mean that SpaceX will (in theory) be able to test and launch any day of the week from May 31st to September 6th, save for a few holidays, effectively boosting the number of opportunities by 40% for those 14 weeks. Until then, SpaceX is doing everything it can to take full advantage of the five days a week it is allowed to test Starship prototypes. N
Notably, although Starships SN8 and SN9 both hit a few weeks of technical and regulatory snags while preparing for their high-altitude launch attempts, SpaceX has been gradually speeding up that process over time. Starship SN10, the first prototype of its kind to land in one piece, took just 33 days to go from pad arrival to liftoff and spent just 8 days between its first static fire and launch attempts. The same feats took Starship SN8 77 and 50 days, respectively, with SN9 splitting the difference at 43 days from transport to liftoff and 28 days between its first static fire and launch attempts.
Road closure requests, a safety warning for residents, and a Temporary Flight Restriction (TFR) filed with the FAA all suggest that SpaceX’s current plan is to attempt Starship SN11’s first triple-Raptor static fire between 6am and 12pm CDT on Monday, March 15th. If that test goes almost perfectly, SpaceX wants to turn the rocket around for a 10 km (6.2 mi) launch attempt on Tuesday, March 16th – the very next day. Given the past performance of high-altitude Starship prototypes, that target is decidedly ambitious and likely to incur delays, but it still reveals the true scope of SpaceX’s goals even at this early stage of development.
If Starship SN11 does manage to launch within a few days of its first static fire attempt, SpaceX would still crush SN10’s 33-day record by a factor of three. Stay tuned for updates on Monday’s possible Starship static fire and rapid Tuesday turnaround attempt
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.
Now targeting to launch Starship’s thirteenth flight test as early as Thursday, July 23 → https://t.co/Rp7VwBzpWx pic.twitter.com/Y0YNzfc5zk
— SpaceX (@SpaceX) July 19, 2026
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.
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.
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:
This is fake news
— Elon Musk (@elonmusk) July 20, 2026
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.
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.
The car will start to remember your specific interventions and match each person’s individual preferences
— Elon Musk (@elonmusk) July 18, 2026
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:
Yeah it seems like FSD v14.3.5 is having some issues with parking early on https://t.co/Bw5ULfVmDq pic.twitter.com/RHdpjOEpIo
— TESLARATI (@Teslarati) July 13, 2026
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:
Yes
— Elon Musk (@elonmusk) July 20, 2026
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.
SpaceX adjusts Starship Flight 13 test launch target date once again
Elon Musk debunks $52 billion SpaceX-NVIDIA GPU deal
