News
SpaceX reinstalling 29 Raptor engines on first orbital-class Starship booster
For the second time this month, SpaceX has begun installing 29 Raptor engines on Starship’s first orbital-class Super Heavy booster, potentially paving the way for several crucial milestones.
On August 1st, around the same time as SpaceX finished installing car-sized grid fins on a Super Heavy for the first time, the company began the process of installing multiple Raptor engines on the booster (#4) that might one day support Starship’s first orbital launch attempt. Not long after it began, it became clear that SpaceX was installing a full 29 Raptor engines on Booster 4 (B4) at a breakneck pace, and less than 24 hours later, all had been attached to Super Heavy’s thrust structure.
Barely a day later, Super Heavy Booster 4 was rolled to the orbital launch pad and installed on a massive ‘launch table’ that was itself installed just a few days prior after months of assembly. Four days after engine installation, Starship S20 and Booster 4 were briefly mated together, forming a full Starship stack – the tallest and most powerful rocket ever built – for about an hour. However, while it did serve as a useful learning experience and pathfinder operation, both stages were demated and returned to the factory soon after.
Since Booster 4’s later August 11th build site return, SpaceX teams have been hard at work fitting the massive 69m (225 ft) tall rocket booster with thousands of feet (if not miles) of secondary plumbing and power and avionics cables. That process effectively began with removing the Super Heavy’s 29 Raptor engines, which finished just a few days after its return to the high bay.


Now, just 12 days after Super Heavy Booster 4 arrived back at the high bay and 11 days after workers briskly removed its Raptors, SpaceX has begun the process of reinstalling those engines – albeit with several new entrants this time around. When SpaceX first fitted B4 with Raptors, it became clear that five or more of had never been tested, making the removal of some of the Super Heavy’s 29 engines more or less inevitable. Indeed, as expected, several new Raptors (engines that weren’t clearly installed the first time around) have joined around two dozen engines that were installed earlier this month.
Given that Booster 4 has already completed a range of fit checks, the implication is that SpaceX is now installing the 29 Raptor engines that will support the first static fire test campaign of a flightworthy Super Heavy. Of course, that testing (likely involving several different static fires of an increasing number of Raptors) could unearth issues or even damage some of those 29 Raptors, so it isn’t quite accurate to say that Booster 4 is being fitted with the engines that will help it carry Starship to orbit. Depending on the outcome of those tests, though, most could easily find themselves lifting off on Super Heavy B4 later this year.
For now, though, Super Heavy Booster 4’s next milestone will be its second trip from the build site to the launch pad. That could occur at any point in the next week or two and could find Booster 4 installed beside Ship 20 on the second of two suborbital test stands, though the Super Heavy may instead return to the orbital launch site.
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.
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.
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.
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.
Go for launch pic.twitter.com/Khu03eiZ04
— Tesla (@Tesla) September 12, 2026
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.
News
Tesla plans big safety improvements for Full Self-Driving v15
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.
Glad you are safe. Even earlier prediction of hazards, even faster reaction time and overall significantly better safety and collision avoidance coming as part of the next big upgrade (v15).
— Ashok Elluswamy (@aelluswamy) September 11, 2026
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.