News
SpaceX on track for US Air Force Falcon 9 mission later this year
Reading between the lines, the US Air Force has effectively confirmed that GPS III Space Vehicle 03 (SV03) – the third GPS III satellite built by Lockheed Martin – is ready for launch aboard a SpaceX Falcon 9 rocket, scheduled no earlier than December 2019.
In December 2018, SpaceX successfully launched the first GPS III spacecraft aboard an expendable Falcon 9 Block 5 rocket, kicking off a launch campaign – shared between SpaceX and ULA – that will likely last until 2023 or 2024. Thus far, ULA has won a single GPS III launch contract, scheduled for July 2019, while SpaceX has won three (with options for two more). Thanks to competition forcefully reintroduced by a 2014 SpaceX lawsuit, the USAF – and thus US taxpayers – are likely saving a minimum of $50M per GPS III launch.
In late 2018, SpaceX’s closer followers were surprised to discover that brand new Falcon 9 Block 5 booster B1054 – the first to be officially certified for a critical operational military launch – was to be expended, making no attempt to land. This was confusing for several reasons.
“If Falcon 9 [was to be] expended solely because of mission performance requirements, despite the oddly low payload mass (~3800 kg) and comparatively low-energy orbit (~20,000 km), the only possible explanation for no attempted recovery would be the need for Falcon 9’s upper stage to circularize the orbit after a long coast. However, the mission parameters the USAF shopped around for would have placed the GPS III satellite into an elliptical orbit of 1000 km by 20,181 km, an orbit that would almost without a doubt leave Falcon 9 with enough propellant for a drone ship recovery.”
— Teslarati.com, December 2018
As it turns out, there was, in fact, nothing unique about the elliptical, medium-energy orbit GPS III SV01 was placed in. According to external analysis of the Falcon 9 upper stage’s final deorbit activities, SpaceX had “plenty of extra performance available”, objectively indicating that that excess performance was intentionally removed from booster B1054 at the cost of its ability to land. The (unconfirmed) reason for this is quite simple: the US Air Force chose extreme – perhaps even excessive – caution to account for the minute chance that myriad failures might happen mid-launch.
To sacrifice, or not to sacrifice
According to a USAF statement made in mid-May, GPS III Space Vehicle 03 (SV03) has been officially classed as “available for launch”, jargon that means the satellite is fully assembled and has successfully completed extensive pre-launch testing. For SpaceX’s inaugural GPS III launch (SV01), a pathfinder that carried unique wait and likely took additional processing time, SpaceX and the USAF took roughly five months to go from shipping the satellite to Florida to going vertical atop Falcon 9. More likely than not, GPS III SV03 has already begun to be prepared for transport from California to Florida, meaning that SV03 is roughly 1-2 months ahead of the schedule SV01 followed ahead of its Falcon 9 launch debut.
So: the GPS III satellite is ready for launch. The next critical milestones will be the satellite’s transport to Florida and SpaceX’s completion of the mission’s USAF-grade Falcon 9. B1054’s technically unnecessary sacrifice thus raises a question for SpaceX’s next GPS III launch, currently scheduled no earlier than December 2018: will another fresh Falcon 9 Block 5 booster be sacrificed to the gods of Obsessively Cautious Margins?

The optimist in me wants to say, “Of course!” With GPS III SV01, SpaceX perfectly demonstrated Falcon 9’s performance and permitted the USAF the luxury of expending a brand new Falcon 9 booster to satisfy the customer’s desire for extremely cautious margins. The Falcon 9 upper stage’s luxuriously expensive (in terms of delta V) deorbit burns – performed after a several-hour cost in orbit – served as another definitive demonstration of the rocket’s intentionally underutilized performance. Having demonstrated a flawless launch with margins on margins, it seems reasonable that the US Air Force would permit SpaceX the freedom to recover Falcon 9 B105x after launching GPS III SV03.
On the other hand, the USAF and Department of Defense are not exactly known for their rational, evidence-based strategies of decision-making and procurement. As such, it’s safe to say that – without official info from SpaceX or the USAF – the answer to the question of whether SpaceX will need to continue expending valuable boosters for GPS launches is entirely up in the air – call it a 50-50 split.

In the meantime, GPS III SV03’s Falcon 9 booster is likely several months away from shipping off to SpaceX’s McGregor, Texas facilities for static fire testing. Up next for SpaceX is a critical Falcon Heavy launch that could secure the rocket’s certification for US military launches, become the first USAF mission to utilize flight-proven SpaceX boosters, and pave the way for the USAF to develop a dedicated certification process for launching on commercially-developed reusable rockets.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.


