News
SpaceX CEO Elon Musk arrives in Texas for milestone Starship engine test
On Saturday evening, SpaceX CEO Elon Musk landed in Waco, Texas – perhaps along with additional SpaceX propulsion engineers – for the critical static fire debut of the first “radically redesigned” Raptor engine, built to power BFR’s Starship upper stage and Super Heavy booster.
If the first operationalized Raptor’s static fire tests go well, there are several possible routes the test program could take, all of which will end up with this engine and several others being tested and ultimately installed on the Starship hopper (Starhopper) prototype under construction roughly 500 miles (800 km) south of SpaceX’s Raptor test cell.
At @SpaceX Texas with engineering team getting ready to fire new Raptor rocket engine pic.twitter.com/ACFM8AtY8w
— Elon Musk (@elonmusk) February 3, 2019
Shortly after Musk revealed official photos of the first operationalized Raptor preparing for an inaugural static fire test at SpaceX’s McGregor, Texas facilities, the SpaceX and Tesla CEO’s private jet was seen landing at Waco, Texas around sunset. Although all SpaceX technical expertise needed for Raptor’s first ignition was probably already on site several days prior, Musk has been known to offer seats on his private planes to SpaceX and Tesla employees when a critical group is needed away from their normal base of operations. The best examples come from Tesla engineering expertise sometimes traveling between Fremont and Gigafactory 1 when needed, often to solve production holdups.
Regardless of whether he was traveling with members of the SpaceX propulsion team, Musk’s arrival at McGregor yesterday signified that Raptor Block 1’s first integrated hot-fire was imminent. Assuming no attempt was made on Saturday night or Sunday morning, SpaceX technicians and engineers are presumably still working on installing what is effectively a new rocket engine and ensuring that Raptor’s test cells – extensively overhauled and upgraded for the occasion – are working as intended. While the development Raptors SpaceX built hovered around 1000 kN (~100t) of thrust, also roughly the same as Merlin 1D, the Raptor now on stand in Texas is reportedly a 200 ton-class engine or more than double the thrust of any single engine SpaceX engineers and technicians have built or test-fired in 15 years of engine development.
- The only official render of Raptor, published by SpaceX in September 2016. The Raptor departing Hawthorne in Jan ’19 looked reasonably similar. (SpaceX)
- Technically speaking, this Raptor is the smaller (sea-level) version of the engine. (SpaceX)
- SpaceX’s current Texas facilities feature a test stand for Raptor, the engine intended to power BFR and BFS to Mars. (SpaceX)
- A Raptor prototype is seen here during its first-ever ignition test. (SpaceX)
- A 2017 test-firing of the mature development Raptor, roughly 50% less powerful than the full-scale system. (SpaceX)
A fork in the R&D road
Prior to completing Raptor Block 1 (unofficial designation), SpaceX cumulatively test-fired dev Raptors for far more than 1200 seconds over the course of more than 24 months. It’s unclear how extensively the company’s engineers will be able to test the pathfinder hardware built on the back of that extensive test program. Nominally, one would expect hundreds or thousands of seconds of additional testing to properly characterize the design and production of a brand-new, optimized engine like Raptor while primarily ensuring that it performs within engineering specifications.
Knowing CEO Elon Musk’s self-admitted tendency to push for impractical deadlines and schedules that often appeared rushed for the sake of rushing, it’s not impossible that the first Raptors could find themselves installed on the Boca Chica-based Starhopper test article after Merlin-esque acceptance testing and nothing more. For M1D and MVac, acceptance testing usually takes the shape of a full-duration burn with throttle and gimbal activity to closely simulate a true Falcon 9 or Heavy launch. For the 200-ton Raptor now in Texas, comparable acceptance testing could take a variety of forms, ranging from short Starhopper-relevant burns (10-60 seconds for small hops) to simulating conditions during a Super Heavy launch and landing or even a 6 or 7-minute orbital insertion burn indicative of the performance needed for Starship.

Depending on the interplay between the route SpaceX engineers would likely prefer and the Starhopper test schedule executives and managers might want, this first Raptor engine (and two more soon to follow) could be installed on Starhopper anywhere from a few weeks to several months from now. Elon Musk indicated in early January that he expected hop tests would occur 4-8 weeks later, shortly followed by unplanned damage to the craft’s nose cone that pushed the debut back “a few weeks”.
Aiming for 4 weeks, which probably means 8 weeks, due to unforeseen issues
— Elon Musk (@elonmusk) January 5, 2019
I just heard. 50 mph winds broke the mooring blocks late last night & fairing was blown over. Will take a few weeks to repair.
— Elon Musk (@elonmusk) January 23, 2019
Realistically, hop tests should thus be expected to begin no earlier than (NET) 8-12 weeks from the first week of January, translating to NET March or April. This would give SpaceX propulsion engineers a decent amount of time to gain at least a few hundred (or maybe 1000+) seconds of experience operating the newest and most advanced iteration of Raptor.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes!
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.
Elon Musk
Tesla gears up Cybercab with Starlink for public debut, but with notable changes
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.




