Connect with us

News

SpaceX fires up Starship and Super Heavy booster hours apart

Two rockets; two static fires; three hours. (NASASpaceflight - bocachicagal)

Published

on

SpaceX appears to have successfully fired up a Starship and Super Heavy booster hours apart, testing a total of three new Raptor 2 engines on the two rockets.

SpaceX says it completed a two-engine static fire with Starship 24 less than three hours after the company successfully ignited a Raptor 2 engine installed on a rocket prototype for the first time. That earlier test, performed by Super Heavy Booster 7, was also the first time SpaceX used its new Starbase orbital launch site to support a static fire test and the second-ever static fire of a Starship booster prototype. Had the company called it quits after Booster 7 survived its first intentional trial by fire, it would have still been an exceptionally successful day.

But SpaceX wasn’t done.

Instead, after Booster 7’s seemingly flawless single-Raptor static fire at 5:25 pm CDT, SpaceX loaded Starship 24 with a small amount of liquid oxygen and methane propellant and ignited two of the ship’s six engines around 8:18 pm. It was not initially clear how many engines were involved but a tweet from SpaceX later confirmed it was two. More likely than not, one of those engines was a sea level-optimized Raptor with a smaller bell nozzle and the other was a vacuum-optimized Raptor with a much larger nozzle.

Advertisement

Almost ten months ago, Starship 20 – SpaceX’s first potentially orbital-class Starship prototype – began static fire testing in a somewhat similar way. Its first day of static fires began with a single Raptor Vacuum engine and ended with a simultaneous RVac and sea-level Raptor test in October 2021. In some ways, SpaceX has been a bit less cautious with Starship 24, which is the second potentially orbital-class prototype to begin proof testing. Ship 24 already has all six Raptors installed, whereas Ship 20 only had four of six engines installed during its first static fire tests. SpaceX also took about three weeks to progress from Ship 20’s first static fire test to its first static fire of all six engines, whereas it appears that Ship 24 could potentially attempt its first six-engine test just a few days to a week later.

On the other hand, Ship 24’s path to its first static fire was substantially longer than Ship 20’s. Ship 20 completed its first static fire test(s) just 25 days after its first proof test, referring to the process of verifying that the prototype was in good working order before moving on to riskier testing with flammable propellant and intentional ignitions. Ship 20 also completed its first six-engine static fire 46 days after testing began. Ship 24, meanwhile, took 75 days to go from its first proof test to its first static fire – almost three times slower than Ship 20, a prototype that was essentially the first of its kind.

It’s possible that Ship 24’s upgraded Raptor 2 engines are partially or fully to blame. Instead of jumping straight into ‘hot’ Raptor testing like Ship 20, which began that particular campaign with a partial-ignition preburner test, SpaceX put Ship 24 through seven ‘spin-prime’ tests before its first static fire. For Raptor, spin-primes test the ignition step before preburner ignition, which is itself a step before main combustion chamber ignition (where the engine starts to produce meaningful thrust). Raptor startup procedures likely involve flowing high-pressure gaseous helium, nitrogen, or propellant (oxygen/methane) through the engine to spin up its turbopumps, ‘priming’ them for preburner and main combustion chamber ignition.

On Raptor 1, the preburners would ignite once a high enough flow rate was achieved, producing hot gas that the main combustion chamber would mix and ignite one last time to start the engine. In a recent interview with Tim Dodd (“The Everyday Astronaut”), CEO Elon Musk revealed that SpaceX was able to “remove torch igniters” from Raptor 2’s main combustion chamber (MCC). It’s unclear if that means that Raptor 2 now has zero MCC igniters, but a major change in the overall ignition process could explain why the start of Ship 24 and Booster 7 engine testing was so sluggish. So could the unintended explosion Booster 7 caused when SpaceX attempted to spin-prime all 33 of its Raptor 2 engines at once.

Advertisement

Regardless, SpaceX has finally crossed that particular Rubicon and, with any luck, Raptor 2 testing will begin to speed up on both Starship 24 and Super Heavy Booster 7. SpaceX has test windows scheduled on August 11th, 15th, and 16th. A warning distributed to Boca Chica, Texas residents on August 10th confirmed that the company intends to perform at least one more static fire test on the 11th.

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 owners surpass 8 billion miles driven on FSD Supervised

Tesla shared the milestone as adoption of the system accelerates across several markets.

Published

on

Credit: Tesla

Tesla owners have now driven more than 8 billion miles using Full Self-Driving Supervised, as per a new update from the electric vehicle maker’s official X account. 

Tesla shared the milestone as adoption of the system accelerates across several markets.

“Tesla owners have now driven >8 billion miles on FSD Supervised,” the company wrote in its post on X. Tesla also included a graphic showing FSD Supervised’s miles driven before a collision, which far exceeds that of the United States average. 

The growth curve of FSD Supervised’s cumulative miles over the past five years has been notable. As noted in data shared by Tesla watcher Sawyer Merritt, annual FSD (Supervised) miles have increased from roughly 6 million in 2021 to 80 million in 2022, 670 million in 2023, 2.25 billion in 2024, and 4.25 billion in 2025. In just the first 50 days of 2026, Tesla owners logged another 1 billion miles.

Advertisement

At the current pace, the fleet is trending towards hitting about 10 billion FSD Supervised miles this year. The increase has been driven by Tesla’s growing vehicle fleet, periodic free trials, and expanding Robotaxi operations, among others.

Tesla also recently updated the safety data for FSD Supervised on its website, covering North America across all road types over the latest 12-month period.

As per Tesla’s figures, vehicles operating with FSD Supervised engaged recorded one major collision every 5,300,676 miles. In comparison, Teslas driven manually with Active Safety systems recorded one major collision every 2,175,763 miles, while Teslas driven manually without Active Safety recorded one major collision every 855,132 miles. The U.S. average during the same period was one major collision every 660,164 miles.

During the measured period, Tesla reported 830 total major collisions with FSD (Supervised) engaged, compared to 16,131 collisions for Teslas driven manually with Active Safety and 250 collisions for Teslas driven manually without Active Safety. Total miles logged exceeded 4.39 billion miles for FSD (Supervised) during the same timeframe.

Advertisement
Continue Reading

Elon Musk

The Boring Company’s Music City Loop gains unanimous approval

After eight months of negotiations, MNAA board members voted unanimously on Feb. 18 to move forward with the project.

Published

on

The-boring-company-vegas-loop-chinatown
(Credit: The Boring Company)

The Metro Nashville Airport Authority (MNAA) has approved a 40-year agreement with Elon Musk’s The Boring Company to build the Music City Loop, a tunnel system linking Nashville International Airport to downtown. 

After eight months of negotiations, MNAA board members voted unanimously on Feb. 18 to move forward with the project. Under the terms, The Boring Company will pay the airport authority an annual $300,000 licensing fee for the use of roughly 933,000 square feet of airport property, with a 3% annual increase.

Over 40 years, that totals to approximately $34 million, with two optional five-year extensions that could extend the term to 50 years, as per a report from The Tennesean.

The Boring Company celebrated the Music City Loop’s approval in a post on its official X account. “The Metropolitan Nashville Airport Authority has unanimously (7-0) approved a Music City Loop connection/station. Thanks so much to @Fly_Nashville for the great partnership,” the tunneling startup wrote in its post. 

Advertisement

Once operational, the Music City Loop is expected to generate a $5 fee per airport pickup and drop-off, similar to rideshare charges. Airport officials estimate more than $300 million in operational revenue over the agreement’s duration, though this projection is deemed conservative.

“This is a significant benefit to the airport authority because we’re receiving a new way for our passengers to arrive downtown at zero capital investment from us. We don’t have to fund the operations and maintenance of that. TBC, The Boring Co., will do that for us,” MNAA President and CEO Doug Kreulen said. 

The project has drawn both backing and criticism. Business leaders cited economic benefits and improved mobility between downtown and the airport. “Hospitality isn’t just an amenity. It’s an economic engine,” Strategic Hospitality’s Max Goldberg said.

Opponents, including state lawmakers, raised questions about environmental impacts, worker safety, and long-term risks. Sen. Heidi Campbell said, “Safety depends on rules applied evenly without exception… You’re not just evaluating a tunnel. You’re evaluating a risk, structural risk, legal risk, reputational risk and financial risk.”

Advertisement
Continue Reading

Elon Musk

Tesla announces crazy new Full Self-Driving milestone

The number of miles traveled has contextual significance for two reasons: one being the milestone itself, and another being Tesla’s continuing progress toward 10 billion miles of training data to achieve what CEO Elon Musk says will be the threshold needed to achieve unsupervised self-driving.

Published

on

Credit: Tesla

Tesla has announced a crazy new Full Self-Driving milestone, as it has officially confirmed drivers have surpassed over 8 billion miles traveled using the Full Self-Driving (Supervised) suite for semi-autonomous travel.

The FSD (Supervised) suite is one of the most robust on the market, and is among the safest from a data perspective available to the public.

On Wednesday, Tesla confirmed in a post on X that it has officially surpassed the 8 billion-mile mark, just a few months after reaching 7 billion cumulative miles, which was announced on December 27, 2025.

The number of miles traveled has contextual significance for two reasons: one being the milestone itself, and another being Tesla’s continuing progress toward 10 billion miles of training data to achieve what CEO Elon Musk says will be the threshold needed to achieve unsupervised self-driving.

The milestone itself is significant, especially considering Tesla has continued to gain valuable data from every mile traveled. However, the pace at which it is gathering these miles is getting faster.

Secondly, in January, Musk said the company would need “roughly 10 billion miles of training data” to achieve safe and unsupervised self-driving. “Reality has a super long tail of complexity,” Musk said.

Training data primarily means the fleet’s accumulated real-world miles that Tesla uses to train and improve its end-to-end AI models. This data captures the “long tail” — extremely rare, complex, or unpredictable situations that simulations alone cannot fully replicate at scale.

This is not the same as the total miles driven on Full Self-Driving, which is the 8 billion miles milestone that is being celebrated here.

The FSD-supervised miles contribute heavily to the training data, but the 10 billion figure is an estimate of the cumulative real-world exposure needed overall to push the system to human-level reliability.

Continue Reading