News
SpaceX Starship nails ‘flip’ maneuver in explosive landing video
Update: SpaceX has published a video taken near the launch pad of Starship nailing an exotic ‘flip’ maneuver shortly before a hard landing destroyed the rocket.
Both the company, test directors, and CEO Elon Musk have all made it abundantly clear that despite the explosive end, Starship SN8’s maiden flight was a spectacular success, proving that the rocket is capable of performing several previously-unproven maneuvers and surviving the associated stresses. Notably, according to tweets posted by Musk not long after, Starship SN8 performed almost perfectly, failing a soft landing (already proven by SN5 and SN6) solely because of low pressure in the rocket’s secondary ‘header’ fuel tank.
For unknown reasons, that tank or its associated plumbing were unable to maintain the pressure needed to feed Raptor with enough propellant, resulting in fuel starvation mid-burn. A lack of fuel and surplus of oxygen effectively turned the landing engine into a giant oxygen torch, melting the copper walls of its combustion chamber (hence the green plume). Had the header tank maintained the correct pressure, SN8 would have very likely landed intact (or at least had a much softer landing).
In simpler terms, it seems that Raptor isn’t to blame for Starship SN8’s failed landing and fixing a pressurization problem will be dramatically faster and easier than rectifying a rocket engine design flaw.
In perhaps the most spectacular aerospace demonstration since Falcon Heavy’s 2018 debut, SpaceX’s first full-size Starship prototype came within a hair’s breadth of sticking the landing after an otherwise successful ~12.5 km (7.8 mi) launch debut.
To quote SpaceX’s test director, heard live on the company’s official webcast moments after Starship serial number 8 (SN8) exploded on impact, “Incredible work, team!” For most, praise shortly after a rocket explosion could easily feel nonsensical, but in the context of SpaceX’s iterative approach to development, a Starship prototype failing just moments before the end of a multi-minute test can be considered a spectacular success.
Chock full of surprises, Starship SN8 ignited its three Raptor engines for the third time and lifted off at 4:45 pm CST (UTC-6) on the program’s high-altitude launch debut.
About 100 seconds after liftoff, already representing the longest-known ignition of one – let alone three – Raptor engines, one of those three engines appeared to shut down, causing the two remaining engines to gimbal wildly in an effort to retain control. Another two minutes after that, one of those Raptors also shut down, leaving one engine active. That one engine continued to burn for another minute and a half, producing just enough thrust to more or less maintain Starship SN8’s altitude at apogee while performing a bizarre horizontal slide maneuver.
Finally, at a bit less than five minutes after liftoff, Starship cut off all Raptor engines and began falling back to earth. Looking spectacularly similar to fan-made renders and CGI videos of the highly-anticipated ‘skydiver’ or ‘belly-flop’ maneuver, Starship – belly down – spent around two minutes in a rock-solid freefall, using four large flaps to maintain stability.
Around 4:52 pm, Starship SN8 performed exactly as expected, igniting one – and then two – Raptor engines while fully parallel to the ground to complete an aggressive 90-degree flip, transitioning into vertical flight for an attempted landing. Unfortunately, although it’s difficult to judge what was intentional and what was not, things began to go wrong after that point -visible in the form of one of the two reignited Raptors flashing green before shutting down.
At the same time, the plume of the lone remaining engine flashed an electric green, quite literally consuming its copper-rich internals in an unsuccessful attempt to slow Starship down. According to SpaceX CEO Elon Musk, Raptor performed “great” throughout the launch and landing attempt, with the bright-green plume likely explained by extremely oxygen-rich combustion caused by low “fuel header tank pressure.”
Regardless of the specific cause, Starship SN8 smashed into the ground around 10-20 seconds early, traveling about 30 m/s (~70 mph) too fast. To be clear, in SpaceX’s eyes, the test – primarily focused on demonstrating multi-engine ascent, freefall stability, header tank handover, engine reignition, and a flip-over maneuver – was a spectacular success, completing almost every single objective and seemingly doing so without any major issues.
Clocking in at an incredible (and unexpected) ~400 seconds (~6.5 minutes) from liftoff to explosion, it’s difficult to exaggerate the sheer quantity of invaluable data SpaceX has likely gathered from SN8’s sacrifice. Thanks to SN8’s primarily successful debut, SpaceX’s Starship test and launch facilities (minus the rocket’s remains on the landing zone) appear to be almost completely unharmed, likely requiring only minor repairs and refurbishment. Further, Starship SN9 is effectively complete and patiently waiting a few miles down the road, ready to roll to the launch pad almost as soon as SpaceX has understood the cause of SN8’s hard landing.
Stay tuned for more analysis, photos, and videos as the dust settles.
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
