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.

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.

Advertisement
-

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.

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

News

Why SpaceX is finishing another space-internet system that isn’t Starlink

SpaceX launched three final O3b mPower satellites Sunday, finishing a lesser known SES satellite network.

Published

on

By

SpaceX had an 87 minute window opening at 2:49 p.m. Eastern on Sunday to fly a Falcon 9 out of Cape Canaveral carrying the final three satellites for SES’s O3b mPower constellation, a project that has taken more than a decade to finish since Boeing and SES first signed SpaceX on for the work.

Unlike the thousands of Starlink satellites SpaceX has stacked into orbit over the years, O3b mPower flies in a different neighborhood entirely. The three new satellites, tagged F11, F12 and F13, are headed for medium Earth orbit at roughly 5,000 miles up, more than ten times higher than Starlink’s shell around 340 miles but still a small fraction of the 22,000 miles where old school geostationary satellites sit. That middle position is the whole point, because a satellite that far out needs far fewer siblings to blanket the globe than a low orbit constellation does. Essentially, SES only needed 13 satellites total to build a network offering quick, steady service that used to require thousands of spacecraft.

With most people having heard plenty about Starlink and almost nothing about O3b mPower, SES and SpaceX already blend the two networks for some customers. Both SpaceX and SES sell satellite broadband, but they’re aimed at different buyers. Starlink is built for volume, direct to consumers, RVs, homes, small businesses, plus a growing aviation and maritime business. O3b mPower skips consumers entirely and sells enterprise grade connectivity to airlines, cruise lines, offshore energy operators, telecoms needing backhaul, and governments, priced and provisioned more like a dedicated circuit.

A 2023 partnership lets cruise ships combine Starlink’s speed with O3b mPower’s steady capacity depending on what a ship needs at a given moment. Sunday’s completed 13 satellite constellation effectively finishes the medium orbit half of that pairing, years after.

Sunday’s mission was already a something on SpaceX’s manifest well before O3b mPower entered the picture. This flight marked its 29th trip to orbit, a history that includes two crewed Axiom missions, the European Space Agency’s Euclid telescope and 22 separate Starlink batches. SpaceX has landed boosters on the droneship A Shortfall of Gravitas so often that Sunday’s touchdown attempt, if it went as planned, was set to be the 661st successful Falcon booster landing to date.

For a company that pushed the Starlink constellation past 11,000 satellites back in August, almost entirely through bulk launches from California, Sunday’s flight was a reminder that SpaceX’s schedule still has room for someone else’s satellites too. SES gets a finished network built for a narrower set of customers, and Falcon 9 gets one more line on an already long resume.

Continue Reading

Elon Musk

Tesla gives the Roadster an official “Go for launch” demonstration date

Tesla teased an October 1 Roadster reveal, reviving years of delayed SpaceX thruster hover promises.

Published

on

By

Concept rendering of a Tesla Roadster with SpaceX Package via Grok
Concept rendering of a Tesla Roadster with SpaceX Package via Grok

Tesla teased an October 1 event date for its next generation Roadster, posting an image on X Saturday that shows the car lit up like it is sitting on a launch pad, with the date “10.01” stamped across the bottom and the caption “Go for launch.” A countdown clock on Tesla’s Roadster order page now points to the same date, which falls on a Thursday. The company has not said where the event will happen or whether it will be streamed at the moment. Stay with us @Teslarati for live updates.


Tesla has since sent formal invitations to reservation holders confirming the event will take place in Waco, Texas, about 90 minutes north of its Austin headquarters, based on a digital ticket shared on X by Sawyer Merritt. Tesla did not name the exact venue, though Waco sits close to SpaceX’s McGregor, Texas, rocket test site, previously reported as the planned location for a Roadster thruster demonstration. The invite sets the reveal for 8:30 p.m. Eastern on October 1, requires RSVPs by midnight on September 16, and limits entry to guests 21 and older. Invitations are non-transferable.

The tease follows nine years of a project defined by unimaginable specs along with slipped dates. Musk first showed the second generation Roadster in November 2017 as a surprise reveal at the end of the Tesla Semi event, promising a 0 to 60 mph time under two seconds, a top speed above 250 mph, 620 miles of range from a 200 kWh battery, and production starting in 2020. At last November’s shareholder meeting, Musk set an April 1 demo date and joked the choice gave him “deniability” if it slipped again, which it did, moving first to late April, then to “a month or so,” then to August.

Tesla Roadster SpaceX Package’s 1.1-second 0-60 mph launch visualized in concept video

Whatever Tesla shows on October 1 is expected to center on the SpaceX developed thruster package Musk has described since 2018. Internally code named A71, a nod to the Lockheed SR-71 Blackbird, the system reportedly uses cold gas thrusters fed by a composite overwrapped pressure vessel, the same tank design SpaceX uses on Falcon 9. Musk has said a thruster equipped Roadster could hit 60 mph in about 1.1 seconds under roughly 2.75 g of launch force, well past the 1.9 second figure quoted for the standard car. That version reportedly will not be street legal and has reportedly been discussed as a limited run sold through a track only program.

The standard Roadster is still expected to carry the original $200,000 base price and $250,000 Founders Series tier, both set when Tesla opened $50,000 and $250,000 reservations in 2017. Tesla VP of Vehicle Engineering Lars Moravy has confirmed production will happen at Gigafactory Texas, with Musk targeting 2027 or 2028, 12 to 18 months after whatever the company demonstrates next month.

Continue Reading

News

Tesla plans big safety improvements for Full Self-Driving v15

Published

on

Credit: Tesla

Tesla is planning to roll out some pretty significant safety and accident avoidance features with Full Self-Driving version 15, which will be the next major FSD deployment from the company.

Tesla AI lead Ashok Elluswamy used a near-miss this week to preview what the company says is the next leap in Full Self-Driving.

In response to a driver whose car had swerved away from another vehicle pulling out of a parking lot, Elluswamy wrote that he was glad the owner was safe and that “even earlier prediction of hazards, even faster reaction time and overall significantly better safety and collision avoidance” would arrive with FSD v15.

The comment landed as Tesla continues to treat software as the primary safety upgrade path. v15 is described internally as a larger architectural step, with a much bigger neural network and tighter coupling between prediction and control.

The company has already begun using early v15 software in some robotaxi operations while rolling out safety features such as Automatic Collision Evasion into current customer cars, allowing the driving stack to intervene even when the driver is in manual control.

Tesla is rolling out a new FSD version with a massive safety addition

Tesla’s published telemetry is the backbone of its safety argument. In recent North American Vehicle Safety Report data, vehicles with FSD (Supervised) engaged traveled roughly 5.1 million to 5.7 million miles between major collisions, defined as airbag-deployment events.

Tesla’s estimate of the U.S. average over the same period is about 699,000 miles per comparable crash. That is the comparison Tesla often frames as roughly seven times fewer major collisions.

A tighter comparison uses the same Tesla fleet. Cars driven manually with active safety features such as automatic emergency braking still recorded a major collision about every 2.1 million miles. Against that baseline, FSD’s advantage shrinks to roughly 2.4 to 2.7 times fewer severe crashes, which independent researchers argue is the more apples-to-apples figure.

European data released in 2026 pointed in the same direction: Tesla reported FSD as 3.5 times safer than manual driving in the Netherlands and 4.1 times fewer collisions than manually driven Teslas with active safety across more than 100 million kilometers in five approved countries.

Those numbers do not settle every debate. NHTSA’s Standing General Order still shows Tesla accounting for the large majority of U.S. Level 2 driver-assist crash reports, in part because the fleet logs far more assisted miles than rivals. Critics also note that Tesla’s “U.S. average” mixes crash definitions and driving mix.

Even so, Tesla’s own same-car comparisons, plus lower rates of automatic emergency braking and harsh maneuvers when FSD is engaged, are the evidence Elluswamy is pointing to when he says v15 will push prediction and collision avoidance further. The claim is not that software already eliminates risk. It is that each major version is meant to widen the gap between the system and an unaided human driver.

Continue Reading