News
SpaceX aborts Starship launch after Raptors produce too much thrust
Update #3: SpaceX CEO Elon Musk says that Starship prototype SN10 automatically aborted a 2:15 pm CST (UTC-6) launch attempt after the rocket determined that its three Raptor engines were producing too much thrust.
Instead of scrubbing for the day, Musk says that SpaceX will instead increase the flight computer’s thrust limits and try again as early as 4:30 pm CST – still well before today’s window closes at 6:30 pm. SpaceX ended its webcast but will start a second webcast a few minutes prior to the next launch attempt.
Update #2: As of Wednesday morning, SpaceX has officially confirmed that Starship is on track for a third high-altitude launch and ‘bellyflop‘-style landing attempt sometime later today.
As of 11am CST (UTC-6), FAA approval is in hand, weather is encouraging, Starship prototype serial number 10’s (SN10) flaps have been unchained, and SpaceX has cleared the launch site – all signs that the rocket’s launch attempt is imminent. Much like SN8 and SN9 coverage, SpaceX says it will make a public livestream of SN10’s launch available to the public “a few minutes” before liftoff. Stay tuned and follow along with NASASpaceflight’s live coverage in the meantime.
Update: SpaceX has asked Boca Chica Village residents to prepare to evacuate the area as early as Wednesday morning for Starship’s third high-altitude launch and landing attempt.
The odds of things going so wrong that a Starship launch could actually end with a prototype impacting at or near the Village and the handful of non-employee holdouts still residing there are minuscule. However, FAA safety regulations and SpaceX’s contingent launch license mean that evacuations are now a routine part of Starship’s high-altitude flight tests since Starship SN8 took the first step beyond short hops. While undeniably inconvenient for the few remaining residents, today’s evacuation notice – short of an official SpaceX.com confirmation – does serve as the ultimate sign that Starship SN10’s first launch attempt is firmly scheduled on Wednesday, March 3rd.
With FAA approval in hand, weather rapidly improving, and the latest rocket prototype seemingly raring to go, the stars are aligning for SpaceX’s third high-altitude Starship launch and first triple-engine landing attempt.
As of March 1st, publicly-available FAA “temporary flight restrictions” (TFRs) and weather forecasts both agree that SpaceX is currently preparing to launch Starship serial number 10 (SN10) as early as Wednesday afternoon CST (UTC-6), March 3rd. Barring surprises, that gives SpaceX a healthy three-day period to account for any potential technical or weather-related delays.
Originally scheduled as early as the last week of February, unspecified delays pushed Starship SN10’s launch debut schedule into March. In general, the vehicle’s path to flight has been much smoother than Starship SN8 and SN9, both of which ran into hardware bugs and opaque FAA licensing issues. With Starship SN10, the FAA approved SpaceX’s “modified” launch license well before the company was ready for flight – and even before the rocket had attempted its first static fire.
Unlike Starships SN8 and SN9, both of which took anywhere from 6-10 weeks to go from rolling off the factory floor to preparing for their first launch attempts, SN10’s first launch attempt appears likely to occur less than five weeks after the rocket arrived at the launch site. The sequential improvements in efficiency and reliability between those three prototypes is a fundamental part (or goal, at least) of SpaceX’s iterative development process.
Still, Starship SN10’s preflight flow wasn’t completely free of drama and SpaceX ultimately put the rocket through a second triple-Raptor static fire after the first test revealed an issue with one of those engines. SpaceX swapped that faulty engine out in record time and fired up SN10 again less than 48 hours after test #1, seemingly producing more satisfactory results the second time around.
Unlike its predecessors, SN10 will also debut a new triple-engine approach to landing, aiming to increase redundancy and boost the odds of a successful touchdown even if one of the Starship’s three Raptors fail during a last-second flip maneuver. Building on the failures of SN8 and SN9, it’s safe to say that SN10 has the best shot yet at sticking the landing.
TFRs show that two earlier launch windows on Monday and Tuesday (March 1st and 2nd) were canceled, leaving only the Wednesday, March 3rd airspace closure request still open. Wednesday was then backed up with two alternate windows on Thursday and Friday not long after.
Hardware-wise, Starship SN10’s cherry-on-top (an explosives-based flight termination system or FTS) was installed on February 28th. In the event that Starship loses control and strays past a certain point outside of its approved trajectory, that FTS would explode, breaching the rocket’s propellant tank, triggering vehicle breakup, and thus preventing it from harming the local populace. All told, SpaceX confirmation of a Wednesday launch attempt – and another official webcast – should be imminent. Stay tuned!
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.