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!
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
