Connect with us

News

SpaceX already clearing Starship debris, preparing for next rocket rollout

Published

on

Update: Half a day after Starship serial number 10 (SN10) became the first prototype to land in one piece, SpaceX has begun clearing its remains and preparing to roll the next rocket to the launch pad.

Never one to rest on its laurels, SpaceX appears to be wasting no time moving forward from Starship SN10’s successful landing and subsequent explosion. Almost a month ago, SpaceX stacked SN10’s successor – Starship SN11 – to its full height and has spent the last four weeks closing out the virtually identical rocket. As of SN10’s launch debut, Starship SN11 has been more or less finished and ready to roll to the launch pad for at least a week.

At the same time as SpaceX teams have begun the process of recovering SN10’s remains, the company also transported a large crane to the launch site – the same crane used to install Starships SN8, SN9, and SN10 at the launch pad. Stay tuned for updates as SpaceX prepares SN11 for a fourth high-altitude launch and landing attempt – this time with the goal of keeping the rocket intact after landing.

In a classically spectacular fashion, a SpaceX Starship prototype has successfully touched down in one piece for the first time ever, only to explode minutes later after catching itself on fire.

Rolled from SpaceX Boca Chica Starship factory to test and launch facilities just a mile down the road on January 28th, Starship SN10 lifted off just five weeks later – the fastest factory-to-launch flow yet. The speed of that turnaround was mainly made possible thanks to an exceptionally smooth test campaign, passing cryogenic proof and static fire tests after only a few attempts.

Prior to its second launch attempt, Starship SN10 automatically aborted a few seconds prior to its first attempt after the rocket’s flight computer determined that its three Raptor engines were producing more thrust than expected. Within half an hour of the abort, CEO Elon Musk took to Twitter to reveal the cause and stated that SpaceX would be tweaking the flight software’s thrust limits and recycling for another shot at launch around two hours later.

Advertisement
-
Starship SN10 became the first of its kind to touch down in one piece – but not for long. (SpaceX)

Up to the last 20 or so seconds of the 6.5-minute flight test, Starship SN10’s launch debut was virtually identical to Starships SN8 and SN9, both of which made it just one or two dozen seconds away from a soft landing. However, after SN9, SpaceX optimized the landing process to add additional redundancy, meaning that SN10 reignited all three of its Raptor engines – instead of just two – for its flip and landing burn.

Exactly as planned, SN10 fired up those engines, autonomously analyzed their performance, and then shut down two Raptors to leave the best-behaving engine to complete the final landing burn. Unlike SN8 and SN9, that maneuver went about as well as it could have, nearly slowing SN10 to a hover with one (seemingly) healthy engine to take it the rest of the way to the ground.

(NASASpaceflight)
Unfortunately, SN10 only had a bit less than ten minutes to enjoy its incredible accomplishment, exploding around T+14:40 after a small fire spread. (NASASpaceflight)

After all that heroic effort and for the first time ever, Starship SN10 proceeded to touch down in one piece. Through the eyes of a drone hovering far away from the launch complex, the landing couldn’t exactly be considered ‘soft,’ however, and SN10 impacted the landing zone with some substantial momentum – likely far too much for its tiny legs to handle.

However, more importantly, SN10 appeared to ignite one or two of its own gaseous oxygen or methane vents, triggering a fire that remained visible until well after the hard – but intact – landing. From official and unofficial views of the landed vehicle, Starship SN10 had a significant lean and appeared to have no more than a few inches to a foot of clearance between its aft skirt and the concrete pad. Remote-controlled firefighting spigots were able to extinguish any external sign of fire but that lack of clearance may have prevented the water from doing much inside the skirt, ultimately dooming Starship SN10.

Starship SN11, February 7th, 2021. (NASASpaceflight – bocachicagal)

Regardless of where exactly that fire ‘broke through,’ so to speak, the original cause of the fire – accidentally igniting a vent plume – is unlikely to be a hard problem to fix, and it’s safe to say that SN10’s intact landing is an extraordinary success for SpaceX. In its official webcast, SpaceX engineer John Insprucker confirmed that Starship SN11 is all but complete and could roll out to the launch pad to pick up where SN10 left off almost as soon as it’s safe to do so.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla Robotaxi takes over for Uber credits and loaners at Service locations

Published

on

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.

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.

Continue Reading

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.

Published

on

By

Elon Musk and U.S. Transportation Secretary Sean Duffy during Duffy’s visit to Gigafactory Texas in May 2025. (Credit: Elon Musk/X)
Elon Musk and U.S. Transportation Secretary Sean Duffy during Duffy’s visit to Gigafactory Texas in May 2025. (Credit: Elon Musk/X)

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.

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.

Continue Reading

Elon Musk

Tesla gears up Cybercab with Starlink for public debut, but with notable changes

Published

on

Credit: Joe Tegtmeyer | X

Tesla is gearing up Cybercab, its all-electric and fully autonomous ride-hailing vehicle, for a very public debut as it plans to start customer deliveries in December. However, the units that rolled out of Gigafactory Texas this morning seem to differ from what we have seen previously.

Aerial images captured by drone photographer Joe Tegtmeyer at Giga Texas on November 18 reveal a noticeable update to the appearance of Tesla’s Cybercabs equipped with Starlink. Rows of gold production vehicles sit in the outbound lot, each carrying a flush-mounted Starlink V5 terminal on the rear hatch that looks more refined than the version first shown months earlier.

When Tesla first unveiled the integration in July and displayed a physical example in August, the Starlink hardware appeared as a relatively distinct rectangular panel on the hatch. Later September footage of large numbers of Cybercabs leaving the factory still showed a lighter, more obvious rectangular cover that roughly matched the vehicle’s gold paint:

Images via Joe Tegtmeyer

The newest batch stands out for how cleanly the cover blends into the roof’s character lines. Observers and replies to Tegtmeyer’s post describe the result as tighter and more intentional, sitting flush and following the body contours rather than reading as an added panel.

All of the Cybercabs in the latest images also wear prominent “Cybercab” logos on the doors and rear hatch, confirming these are finished production units rather than early prototypes. They are staged near the factory building, end-of-line areas, and covered transport trailers, with some already lined up for shipment.

The scale and consistency of the installation point to factory tooling rather than retrofit work.

A secondary detail noted in related sightings is a darker tone to the Starlink cover compared with earlier lighter panels. Tegtmeyer himself left open whether the darker finish is deliberate. There are a variety of explanations for it: perhaps for thermal performance, signal characteristics, or simple visual identification—or simply a batch variation still being refined.

Either way, the overall effect is a more integrated, production-ready appearance. For a Robotaxi that relies on Starlink for fleet connectivity, passenger services, and backup data links in areas with weak cellular coverage, the cleaner hatch design is more than cosmetic.

It signals that Tesla is polishing the final visual and hardware details as Cybercab volumes continue to climb at Giga Texas ahead of broader Robotaxi deployment. The vehicles now look to be built with Starlink instead of it being added afterward.

Continue Reading