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.
News
Tesla’s Cybercab fleet just had its biggest day ever
Tesla registered a record 200 Cybercabs in one day, and Dallas could be next up.
Tesla added a record 200 Cybercabs to its Texas Robotaxi fleet in a single day, pushing the purpose-built two-seater past 750 registered units in the state. The batch landed on the Texas Department of Motor Vehicles automated vehicle register at 3:45 p.m. CT on November 17 and included 200 Cybercabs and one Model Y. Tesla’s Cybercab count had sat at 573 since late October before the jump.
The additions also put Tesla back ahead of Waymo on the register. Tesla now has 1,507 vehicles registered for driverless operation in Texas against Waymo’s 1,321, a lead of 186. Waymo had been ahead by 15 vehicles before the batch arrived. Tesla first passed Waymo on November 10, as Teslarati reported, before Waymo briefly moved back in front.
🚨 There are more CYBERCABS in the Tesla Robotaxi fleet in Texas than Model Y! https://t.co/BdRK2LnnAP — TESLARATI (@Teslarati) November 18, 2026
Cybercabs now make up 51.3 percent of Tesla’s registered Texas fleet, at 773 units against 734 Model Ys. Waymo’s fleet in the state is split between 874 Jaguar I-PACEs and 447 Ojai vehicles.
The register does not say where vehicles will operate, and registration does not mean a car is carrying riders. Still, the timing lines up with Tesla’s plans for Dallas. On the company’s third quarter earnings call in October, AI chief Ashok Elluswamy said, “next month, we’ll be launching in Dallas,” and a video posted over the weekend showed more than 50 Cybercabs parked in rows at a Dallas lot, with more on a car carrier nearby. Tesla has not announced a start date.
Dallas is already one of Tesla’s busiest Robotaxi markets. Model Y Robotaxis there have run without anyone in the driver’s seat around the clock since November 11, and the city logged 608,130 miles with no safety monitor between January 22 and October 18, second only to Austin, according to Tesla’s first Robotaxi Safety Report. Public Cybercab rides have been limited to Austin since the vehicle joined the service in September.
The fleet growth comes as Tesla shifts more of its factory capacity toward the Cybercab. The company is winding down Cybertruck production at Giga Texas by the end of summer 2027 to make room, and announced this week a €3 billion expansion of Giga Berlin with a new building designed to produce up to 1 million Cybercabs a year starting in 2029, as Teslarati covered.
Some Cybercabs will soon go to private owners too. Tesla began inviting select customers to buy the vehicle for personal use last week at $29,990 with a required $299 monthly Autonomy Subscription, with deliveries targeted for December in the same five Texas cities where Robotaxi operates.
News
Tesla Robotaxi takes over for Uber credits and loaners at Service locations
Tesla is now utilizing its in-house Robotaxi platform to give those waiting for their vehicles during Service visits rides instead of offering Uber credits or Loaner vehicles.
Tesla owners in Austin who bring vehicles in for service are receiving in-app prompts to use the company’s Robotaxi network while their cars are being worked on.
One recent notification, sent during a frunk repair, carried the heading “Try Robotaxi During Your Service Visit” and stated that while the vehicle is being serviced, the customer can take an autonomous Robotaxi ride to the next destination in Austin and download the Robotaxi app to get started.
Interesting. While my frunk gets fixed Tesla suggests taking a Robotaxi 😇 https://t.co/QiUbAmrp4a
— Wadesmith (@LanceWade) November 17, 2026
The suggestion arrives as Tesla has long relied on two main ways to keep customers mobile during longer service visits. Service centers have typically offered loaner vehicles drawn from a limited fleet; when those vehicles were unavailable, centers have issued Uber or Lyft credits. Uber credits were widely eliminated years ago, but some locations will still give them out.
Both approaches carry costs: loaner cars occupy inventory that could otherwise be sold, and third-party credits generate recurring expense.
Code discovered in Tesla app version 4.60.5 in September 2026 already listed “sv_transport_robotaxi” among the transportation options available for service appointments, alongside paid loaners and other alternatives, indicating the company had been preparing to route customers through its own autonomous fleet.
Your Tesla could be in the Robotaxi fleet next month, Elon Musk claims
Austin provides the clearest early example. The city remains Tesla’s primary Robotaxi market, with unsupervised Model Y and Cybercab vehicles operating across an expanded zone of roughly 400–440 square miles and running 24/7 since November 11. Public driverless service is also live in Dallas, Fort Worth, Houston, San Antonio, Miami, Orlando, and Tampa.
Directing service customers into this network keeps the vehicles utilized and reduces reliance on external rideshare credits, while giving owners practical experience with the Robotaxi app and vehicles during the repair window. Once service is complete, the same network can be used for the return trip without a staffed loaner handoff.
The Austin notification is the first public instance of the capability the September app code previewed. As Robotaxi expands into additional U.S. markets and the fleet grows, service centers in those cities are positioned to follow the same pattern, presenting autonomous rides as a primary transportation option during the service appointment rather than defaulting to loaner vehicles or third-party credits.
For customers, the change preserves mobility without the logistics of arranging a temporary car; for Tesla, it links the service operation more tightly to the expanding Robotaxi business.
Elon Musk
Sean Duffy fires back at Elon Musk over free Starlink
Sean Duffy says the FAA picked a ground network over Starlink, and Musk isn’t impressed.
Transportation Secretary Sean Duffy has responded to Elon Musk’s claim that the Federal Aviation Administration turned down free Starlink terminals before last week’s nationwide ground stop, saying the department chose a ground-based network after running into problems with an earlier version of the satellite service. Musk’s reply was a single emoji: “🤦♂️.”
Speaking at a press conference, Duffy said Starlink had been useful in some parts of the system. “I’ve worked well with Elon, and he, Starlink was a great solution for some of our assets in Alaska, but we sent Starlink, in one of its prior iterations, to our tech lab, and, there was some issues that we had to navigate, and we thought that the best method is to have a network that’s based on the ground,” Duffy said, according to a transcript published by ZeroHedge. “Now, I think what he’s doing with Starlink and the speed is remarkable, but, our airspace is very big. We have assets everywhere. And so, again, we used him for different parts of the airspace.”
Duffy did not dispute that the offer was made. He also did not say what problems the FAA found during testing.
The exchange started Monday, when Musk wrote on X, “Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” as Teslarati reported. That post came three days after the FAA grounded departures nationwide on November 13, when its legacy equipment became unstable as data flooded its telecommunications network at 1,000 connection attempts every four to five seconds. The FAA traced the flood to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where L3Harris had been installing a new router. Roughly 12,462 flights were canceled that day.
As I was saying …
Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were.
— Elon Musk (@elonmusk) November 16, 2026
Duffy has also signaled frustration with L3Harris, which runs the FAA’s current network. “I want to get away from L3Harris and get to a new one, but they own the network,” he said. “I can’t cancel the network that they own.” He has asked Congress for $50 billion to modernize air traffic control, arguing against “a patchwork, a fix to a system that’s critical for every single family.”
The FAA’s position on satellite links predates this week. In a July 2025 letter to lawmakers, FAA Administrator Bryan Bedford said the agency “would not use Starlink (or any satellite service) as the sole communications technology” for safety-critical air traffic services. Reuters reported at the time that the FAA was not considering replacing its L3Harris and Verizon contracts with Starlink. Verizon’s FAA Enterprise Network Services contract, awarded in 2023, is valued at up to $2.4 billion over 15 years.
Musk first pressed the issue in February 2025, while he was leading the Department of Government Efficiency, writing that “the Verizon system is not working and so is putting air travelers at serious risk” before correcting himself days later to blame L3Harris. SpaceX said at the time it was supplying Starlink kits to the FAA at no cost and had no intent to take over any existing contract.