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.
A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.
The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.
TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.
Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.
Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.
TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.
This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.
This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.
However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.
Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.
Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.
The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.
A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”
Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.
This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.
The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.
Musk teased that a similar feature was “coming” back in February:
Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says
It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.
Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.
Here’s an example of that from December:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.
We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
