Connect with us

News

Musk blames SpaceX’s latest Starship explosion on Raptor engine leak

CEO Elon Musk says that a "small" leak on one of Starship SN11's Raptor engines led to the rocket's failed landing attempt. (SpaceX)

Published

on

CEO Elon Musk says that SpaceX’s latest Starship test flight ended with a midair explosion because a “small” leak started on one of the rocket’s three Raptor engines.

As promised, the new information offers some insight into the cause of Starship SN11’s premature demise and the challenges of iteratively developing systems as complex as a fully-reusable Saturn V-class launch vehicle. On March 30th, after about a week of delays, Starship SN11 lifted off on SpaceX’s fourth high-altitude launch and landing test while all but completely obscured by a thick bank of fog.

Despite the unfortunate weather conditions, which prevented almost any kind of view of the launch outside of Starship’s own cameras, the rocket performed about as well as its three predecessors, reaching a planned apogee of 10 km (6.2 mi) before free-falling belly-first back to earth. At T+5:49, however, things went wrong.

At that point, Starship tried to ignite its three Raptor engines to flip into a tail-down landing configuration, at which point two of those engines would be shut down, leaving the healthiest of the three to attempt a soft landing. Something immediately went wrong and both telemetry, live video, and the countdown clock froze with a view of one partially ignited Raptor engine.

The engine on the left here appears to have been the leaky culprit. (SpaceX)

Notably, as pictured in the image at the top of this article, it’s possible that the “small [methane] leak” Musk has blamed for SN11’s failure was visible on Raptor engine SN52 less than 30 seconds after Starship lifted off, leaving plenty of time for a high-pressure fire to severely damage the faulty engine and its adjacent partners. The SpaceX CEO says that the resultant fire “fried part of [the] avionics” controlling one or all three Raptors, “causing [a] hard start” that damaged or destroyed one or all of the engines when they attempted to begin their landing burns.

Based on analysis of unofficial videos taken by cameras near the Starship launch site, it’s been deemed likely that SN11 exploded not because its flight termination system (FTS) triggered – but because of Raptor’s violent, explosive “hard start.” Ultimately, it’s not clear if ever SpaceX itself will ever be able to paint a truly clear picture of what exactly happened to SN11, but Musk says that the suspect Raptor leak “is getting fixed [six] ways to Sunday.” It’s possible that an upgraded Raptor engine Musk has hinted will debut on Starship SN15 has already fully or partially dealt with whatever is at the root of SN11’s engine leak and hard start(s).

Advertisement

Either way, SN15 is already expected to roll to the launch pad as early as this week – mere days after SN11’s explosion – and SpaceX wont have to wait long to test whatever fixes it implements as the upgraded vehicle works towards static fire tests and its own launch debut.

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

Elon Musk

Tesla Semi finally has an FSD timeline and it’s waiting on the Cybercab

Elon Musk told investors Semi self-driving should start working by early 2027, per today’s earnings.

Published

on

By

During Wednesday’s’ Tesla Q2 earnings call, an analyst asked Elon Musk when Tesla would look at autonomy for the Semi. His answer set a real timeline for the first time, noting that self-driving on the Tesla Semi is expected to start working “around the end of this year or early next year”.

Musk framed the delay as a matter of priority, not capability. Tesla’s self-driving team is currently focused on Model 3, Model Y, and Cybercab, the vehicles that make up the overwhelming majority of Tesla’s fleet. Since Semi trucks on the road remain a small fraction of that total even after the recent Nevada factory ramp, Musk said it made more sense to keep the software team’s attention on what he called “the march of nines of safety” for the higher volume vehicles first. Autonomous Semi development is “taking a bit of a backseat for the next six months or so,” he said, before adding that it “will definitely be working next year and in time for the scale-up to high production of the Tesla Semi.”

Tesla Semi’s official battery capacity leaked by California regulators

The timeline lines up with what’s already been showing up on public roads. In June, a Tesla Semi was spotted in Sunnyvale wearing a full validation rig, the same rooftop sensor array Tesla mounts on vehicles ahead of an FSD milestone.

A second unit was seen near Fremont days later with a matching camera suite and lens washers. Separately, Tesla analyst Nic Cruz Patane posted video this month of the production Semi’s exterior camera array, ten AI4 based units built directly into the truck rather than added later.


Musk also gave the reason autonomy on the Semi matters in the first place, a persistent shortage of qualified truck drivers. “There is a really serious shortage of truckers,” he said on the call, framing a self-driving Semi as important both for addressing that shortage and for improving safety and comfort for the drivers running the truck today.

The timing also tracks with the Semi’s production reality. Tesla’s Q2 shareholder letter, dropped language promising the Semi would reach volume production this year. Musk pointed to 4680 battery cell output as the near-term constraint on Semi and Cybercab production. A software timeline landing in early 2027 gives Tesla’s autonomy team room to work while the hardware ramp catches up behind it.

It’s worth nothing that this isn’t necessarily a promise the Semi ships driverless next year. Musk’s own language, self-driving “working” by early 2027, describes internal validation catching up to hardware already riding on every production truck, not a public unsupervised rollout.

Continue Reading

Investor's Corner

Tesla (TSLA) Q2 2026 earnings results: miss on EPS, beat on revenue

Published

on

Credit: Tesla

Tesla (NASDAQ: TSLA) reported its earnings for the first quarter of 2026 on Wednesday afternoon. Here’s what the company reported compared to what Wall Street analysts expected.

The earnings results come after Tesla reported a massive beat on vehicle deliveries for the second quarter, delivering 489,126 vehicles and building 451,758 cars during the three-month span.

This was a major shock for those on Wall Street as they anticipated somewhere around 400,000 deliveries for the quarter, and showed Tesla still has plenty of demand for its vehicles around the world and in the U.S. despite losing the $7,500 EV Tax Credit last year.

Tesla Q2 2026 Earnings Results

  • Non-GAAP EPS – $0.33 reported vs. $0.53 expected
  • Revenues – $28.236 billion reported vs. $26.4 billion expected
  • Free Cash Flow- -$1.092B
  • Profit -$ 4.751B

Tesla (beat/missed) analyst expectations, so the market response to the company’s quarter is what we will look for next.

Tesla shares closed today down just over 1 percent, trading at $374.01.

In the past, it has been anyone’s guess with what Tesla shares will do after they report earnings. Strong quarters have resulted in sharp drops, while lackluster quarters have seen the stock shoot up considerably.

Tesla will hold its Q2 2026 Earnings Call in about 90 minutes at 5:30 p.m. on the East Coast. Remarks will be made by CEO Elon Musk and other executives, who will shed some light on the investor questions that we covered earlier this week.

You can stream it below. Additionally, we will be doing our Live Blog on X and Facebook.

Continue Reading

Elon Musk

Tesla is about to make parking in busy lots less stressful than ever

Published

on

Tesla FSD 14.3 [Credit: TESLARATI)
Tesla FSD 14.3 [Credit: TESLARATI)

Tesla is about to make parking in busy parking lots at businesses and other points of interest less stressful than ever by allowing drivers more control over where they park and how, CEO Elon Musk confirmed on X.

Tesla has been working to improve the parking performance of vehicles utilizing the Full Self-Driving suite, but now it is looking to add more customization, allowing drivers to choose the specific space they park in, but also potentially the orientation the car pulls into the spot:

Musk has reiterated on X twice over the past several weeks that Tesla is working to make things with the FSD suite based more on the driver’s specific preferences and behaviors that were seen in past drives.

Essentially, it sounds like if you tend to park away from a business to avoid other vehicles, Tesla FSD will soon recognize that preference of yours and start parking further away as well. Additionally, the prospect of assigned parking spaces has been something many owners have voiced concerns about.

Living in a community with assigned parking spaces makes using FSD incredibly difficult as it will rarely park in the correct spot when there are so many to choose from. This is also pertinent in work settings where there are sometimes assigned parking spaces.

The updates to Tesla’s Full Self-Driving suite in terms of listening to driver preferences with parking are also extending to routing. Tesla announced yesterday that with the release of its 2026 Summer Update, it was adding Automatic Navigation and Preferred Routes:

Tesla reveals 2026 Summer Update with crazy fixes to Nav and more

Tesla has always maintained the idea that any human input is bad input, and that, ideally, Tesla Full Self-Driving will always make the right decision. Of course, this is all in theory, but the issue is that so many of Tesla’s interventions have come because it does something that is not necessarily wrong, but perhaps not what the driver would prefer.

Taking these preferences into account will help Tesla alleviate some of the potentially unnecessary interventions that drivers perform.

Continue Reading