News
SpaceX Starship booster heads to launch pad for the fifth time
For the fifth time in five months, SpaceX has transported its most advanced Starship booster prototype from the Starbase factory to the launch pad, setting the stage for another round of testing.
Super Heavy Booster 7 (B7) returned to the factory for the fourth time on August 12th after becoming the first prototype of any kind to perform a static fire engine test while installed on SpaceX’s orbital Starship launch mount. In the days prior, the booster completed two back-to-back static fire tests with one of the 20 Raptor engines installed on the rocket, both of which apparently gave SpaceX enough confidence to prepare for the next phase of testing.
That relatively cautious progress only came after SpaceX attempted to test all 33 of the prototype’s Raptors at once during its first engine test. Whether it was the fault of overzealous managers or executives or a genuine oversight is not clear, but the combined behavior of Super Heavy and the orbital launch pad was not properly characterized before testing began. As a result, the cloud of flammable gas the rocket released during its attempted 33-engine ‘spin-prime’ test found an ignition source and violently exploded on July 11th, causing damage throughout Booster 7’s aft engine section that required several weeks of repairs between July 15th and August 6th.
When the Super Heavy rolled to the pad for the fourth time on August 6th, it was missing all 13 center Raptors, leaving only the outer ring of 20 Raptor Boost engines partially installed for the tests that followed. Thankfully, things went much better on the second try and Booster 7 completed two spin-prime tests with a single Raptor engine, followed by two successful static fire tests on August 9th and 11th. The latter test was the longest Starbase static fire ever (by a factor of ~3) and lasted about 20 seconds, allowing SpaceX to test Booster 7’s autogenous pressurization. That system pressurizes Super Heavy’s tanks by turning small quantities of cryogenic liquid propellant into gas, ensuring that its tanks remain stable as they’re rapidly drained of thousands of tons of propellant.
On August 12th, Booster 7 returned to the factory, where workers installed the rocket’s 13 center engines for the second time. Booster 7 headed back to the orbital launch site (OLS) on August 23rd and the pad’s robotic launch tower used a pair of arms to lift the rocket off its transport stand and place it on the launch mount by the end of the day.
In addition to readying Booster 7 for its next phase of static fire testing, teams of SpaceX workers took advantage of the unplanned lull in testing to modify the orbital launch mount. It’s impossible to know what exactly was done without official confirmation, but it’s likely that SpaceX was attempting to quickly fix the shortcoming(s) that allowed the July 11th explosion to happen. Without a fix, it’s unlikely that SpaceX would want to proceed with plans to ignite large numbers of Raptor engines simultaneously – a series of tests that must be completed before Starship can safely attempt its first orbital launch.


It’s unclear what exactly that fix entails, but it could involve a system to constantly flood the engine section with fire-stopping nitrogen gas or potentially take the shape of a system of vents that will connect to every Raptor engine and remove methane gas before it can turn into flammable clouds.
It’s possible that Booster 7 has returned to the launch pad solely for fit checks or some other basic proof-of-concept testing. It’s also possible that the returns signifies that SpaceX is confident in its quick launch mount fix and ready to restart static fire testing.
As Booster 7 prepares for that next phase of testing, SpaceX may also be ready to restart static fire testing with Starship S24, which paused shortly before Super Heavy returned to the factory. SpaceX appears to be modifying the suborbital launch mount and test stand Ship 24 is installed on, which could explain the lack of ship testing since August 11th. SpaceX has 12-hour test windows tentatively scheduled on August 24th and 25th, either of which could be used to test either or both prototypes.
If all goes to plan, Ship 24 and Booster 7 will eventually complete all the qualification testing SpaceX can throw at them and be ready to support Starship’s first orbital launch attempt sometime before the end of 2022.
News
Tesla Robotaxi’s slow rollout gets explanation from Elon Musk
Tesla Robotaxi is among its biggest projects currently, but many have been quick to point out the fact that the company has definitely been slow to expand its fleet.
However, there is definitely a method to that madness. CEO Elon Musk answered several concerns during last night’s quarterly earnings call that some might have about that slow rollout of the Robotaxi suite, maintaining the company’s narrative on prioritizing safety and wanting to avoid injuries to anyone, including animals.
Musk said:
“With Robotaxi, our goals are very ambitious for Robotaxi, but we do need to be cautious about causing any accidents or causing any harm to anyone. Although there are, I think, 30,000 to 40,000 automotive deaths per year in the U.S. alone, most of those do not generate any press or maybe, you never really read about almost any of those. If we injure even one person, it’ll be worldwide headline news, and regulators will immediately clamp down on our activities.
We don’t want to injure anyone. We’re going as fast as humanly possible in scaling Robotaxi, but while trying to ensure that we do not harm anyone at all, and ideally do not even run over a pet. That’s really the constraint is we want to grow as fast as possible with Robotaxi without harm to anyone.”
Tesla has maintained an exemplary safety record with its Robotaxi suite, according to internal data. VP of AI, Ashok Elluswamy, said that the Robotaxi suite has driven more than 380,000 miles unsupervised without any incidents.
0 notable incidents across over 380,000 miles traveled by Robotaxi
— Tesla (@Tesla) July 22, 2026
Analyst Colin Langan of Bank of America also pushed Tesla executives for answers regarding the company’s decision to add cities across several states with dozens of vehicles “as opposed to hundreds.”
Elluswamy said there’s a bigger advantage to do it the way Tesla has been because it ensures that its software stack “is a very general one:”
“The reason we have been expanding across different cities instead of just doubling down on a single city, is that we want to make sure that our stack is a very general one. It is a general one. We just want to both prove to ourselves and to other folks that it is working across a lot of different cities without too much effort per city. That’s what we see internally.”
In the past, we have written about Tesla’s decision to be incredibly conservative with its Robotaxi rollout, especially with the incredibly small fleet size compared to competitors. However, there really is not a price anyone can put on safety for those utilizing the platform or pedestrians, so what Tesla is doing is justified.
A year into the Robotaxi program being active, Tesla has made major strides, but many investors and fans would like to see the fleet expand as quickly as the program has to other cities and states.
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.
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.
Tesla Semi AI4 cameras. The production version has 10 cameras on its exterior.
These trucks are designed to be autonomous. pic.twitter.com/GH3BamxIBQ
— Nic Cruz Patane (@niccruzpatane) April 14, 2026
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.
Investor's Corner
Tesla (TSLA) Q2 2026 earnings results: miss on EPS, beat on revenue
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.
Q2 2026 Earnings Call https://t.co/zZS6ii2TWK
— Tesla (@Tesla) July 22, 2026
