Connect with us

News

SpaceX’s Starhopper readies for more ambitious Raptor-powered flight tests

On June 1st, SpaceX technicians began installing a new Raptor - this time SN04 - on Starhopper. (NASASpaceflight - bocachicagal)

Published

on

For the second time in two months, SpaceX technicians have begun to install a Raptor engine on Starhopper, a full-scale Starship testbed theoretically capable of low-velocity, moderate-altitude ‘hops’.

Back in late March, Raptor and Starhopper were joined for the first time, enabling a lengthy series of attempted tests that were followed by two engine ignitions and tethered hops before Raptor was removed for inspection. In the two months since that first round of integrated testing, SpaceX has significantly upgraded Starhopper and its spartan launch facilities, all focused on transforming the odd vehicle from a largely fixed test stand into a giant, mobile Grasshopper.

All the way back in 2012, SpaceX began testing Falcon 9 recovery and reusability concepts with a low-fidelity prototype known as Grasshopper – essentially a minimalist Falcon 9 first stage with ad hoc legs and a single Merlin engine. It supported a series of 8 major test flights – all successful and a source of valuable data – before the vehicle’s 2013 retirement. An upgraded Grasshopper – known instead as Falcon 9 Reusable Development Vehicle (F9R Dev1) – began testing around the same time and continued even higher altitude vertical takeoff/vertical landing (VTVL) tests until its untimely demise in August 2014.

Starhopper is quite similar, although it is also serving as a testbed for a far more varied range of technologies due to the fact that it has been developed before the inaugural launch of its namesake (Starship/Super Heavy). By the time SpaceX started Grasshopper/F9R tests, Falcon 9 had already completed several successful launches. With Starhopper, SpaceX is building and testing its first 9m-diameter ‘flight’ hardware, its first propellant tanks built out of steel, its first flight-capable rocket fueled by methane and oxygen, and its first mobile Raptor testbed, among numerous other things. The challenges are inherently much greater, but SpaceX has the luxury of taking the opposite approach it took towards Falcon 9 and building a launch vehicle entirely around its intended reusability, rather than trying to squeeze a method of reusability around an already-flying rocket.

Saurid Oddities

As noted by NASASpaceflight.com in a June 2nd article, SpaceX seems to be juggling its growing selection of newly-produced and tested Raptor engines in pursuit of Starhopper’s return to flight. According to the publication’s reliable sources,

“Up until recently, [SpaceX] was planning to utilize Raptor SN4 for [Starhopper’s first] untethered hops. However, the company has now decided to utilize this engine only for fit checks, and will instead perform the hops with SN5 – the latest Raptor to come out of SpaceX’s factory in Hawthorne, California.” – NASASpaceflight.com, June 2nd, 2019

This indicates that the Raptor engine delivered to Boca Chica on June 1st and currently in the process of being installed on Starhopper is actually more of a stand-in* for a future Raptor, SN05. The reasons behind this Raptor shuffle elude detection, but it’s possible that the simplest explanation – also posed by NASASpaceflight – is the correct one. By shipping a Raptor that may not be ready for flight tests, SpaceX could likely save anywhere from a few days up to a few weeks by doing everything short of lifting off under the powered of Raptor SN04.

*By all appearances, SN04 is a flight-grade Raptor that has completed assembly and likely been test-fired in McGregor, Texas. Why it may currently be resigned to a “stand-in” role is unknown.

Very curiously, upon Raptor SN04’s South Texas arrival, it appears that SpaceX technicians have indeed rapidly installed the engine on Starhopper, but in a position that is decidedly off-center. Pictured above, the photo could have simply caught the engine while technicians were moving it to its actual installation spot, but it could also indicate that SpaceX is speeding towards Starhopper’s first triple-Raptor test flights.

Advertisement
-

Starhopper delays?

In line with the last-second switch from Raptor SN04 to Raptor SN05 as the engine-to-be for untethered hops, SpaceX has pushed the start of that test series from approximately May 31st to June 11th. More likely than not, the ~11-day delay is meant to allow time for Raptor SN05’s McGregor, Texas acceptance testing, given that – per CEO Elon Musk – the engine wasn’t even finished as of May 22nd.

On the other hand, with Raptor SN05 now scheduled to support Starhopper hop tests as early as mid-June, it begs the question of whether SpaceX is instead working towards expedited triple-Raptor testing. For unknown reasons, neither Raptor SN03 or SN04 are apparently ready to support flight operations, although both have been thoroughly hot-fired in McGregor. Perhaps each engine is a distinct prototype with a different level of experimental readiness, or perhaps SpaceX is just testing certain engines (like SN03) more extensively than others (SN05).

Regardless, SpaceX now seems to have 3-4 intact, functional Raptor engines (excluding SN01; destroyed during stress testing), 2-3 of which are actively testing or being worked on a day’s drive north of Boca Chica. SN02 – having successfully supported a brief duo of ignition tests with Starhopper – could still be intact and test-ready. SN03 is an unknown quantity, but SN04 is clearly in excellent shape and is probably close to flight-readiness if it isn’t already. This is to say that SpaceX likely already has three Raptors on hand that are capable of supporting multi-engine Starhopper testing, whether or not such a test regime would actually be valuable.

Musk has noted that both orbit-capable Starship prototypes will be far closer to finished products and will thus fly with “at least 3 engines” (3 sea level engines, as it would turn out) or even “all 6” (3 sea level, 3 vacuum-optimized). In the meantime, Starhopper stands with an off-centered Raptor, awaiting the arrival of a different Raptor to kick off a second hop test program. If nothing else, SpaceX’s Starship/Super Heavy development program is operating in a spectacularly hardware-rich fashion, lending itself to the breakneck-pace of iteration and improvement SpaceX is famous for.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

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