News
SpaceX backup Starship reaches full height after nosecone installation
SpaceX has installed another Starship’s nosecone, all but completing the second full-size prototype a matter of days before the first fully-assembled Starship’s risky launch debut.
Over the last two months, SpaceX has effectively put Starship number 8 (SN8) through an almost nonstop series of tests, completing at least four separate cryogenic proof tests, four Raptor engine static fires, and much more. The company’s South Texas team have also dodged an array of technical bugs; installed, plumbed, and wired what amounts to ~40% of Starship (the nose section) while fully exposed to the coastal elements; and even narrowly avoided a potentially catastrophic failure.
In spite of the many hurdles thrown up and delays resultant, CEO Elon Musk announced earlier this week that Starship SN8 is scheduled to attempt its 15-kilometer (~50,000 ft) launch debut as early as Monday, November 30th. Musk, however, does not see success as the most probable outcome.

Why, then, push to launch Starship SN8 when, in Musk’s own words, the probability of success is as low as “33%”? As previously discussed many times in the history of Teslarati’s BFR and Starship coverage, SpaceX’s attitude towards technology development is (unfortunately) relatively unique in the aerospace industry. While once a backbone of major parts of NASA’s Apollo Program moonshot, modern aerospace companies simply do not take risks, instead choosing a systems engineering methodology and waterfall-style development approach, attempting to understand and design out every single problem to ensure success on the first try.
The result: extremely predictable, conservative solutions that take huge sums of money and time to field but yield excellent reliability and all but guarantee moderate success. SpaceX, on the other hand, borrows from early US and German rocket groups and, more recently, software companies to end up with a development approach that prioritizes efficiency, speed, and extensive testing, forever pushing the envelope and thus continually improving whatever is built.
In the early stages of any program, the results of that approach can look extremely unusual and rudimentary without context (i.e. Starhopper, above), but building and testing a minimum viable product or prototype is a very intentional foundation. Particularly at the start, those minimal prototypes are extremely cheap and almost singularly focused on narrowing a vast range of design options to something more palatable. As those prototypes rapidly teach their builders what the right and wrong questions and design decisions are, more focused and refined prototypes are simultaneously built and tested.
Done well, the agile approach is often quite similar to evolution, where prototype failures inform necessary design changes and killing off dead-end strategies, designs, and assumptions before they can be built upon. In many cases, compared to cautious waterfall-style development, it will even produce results that are both better, cheaper, and faster to realize. SpaceX’s Starship program is perhaps the most visible example in history, made all the more interesting and controversial by the fact that it’s still somewhere in between its early, chaotic development phase and a clear path to a viable product.
On the build side of things, SpaceX has created a truly incredible ad hoc factory from next to nothing, succeeding to the point that the company is now arguably testing and pushing the envelope too slowly. As of November 2020, no fewer than eight full-size Starships and the first Super Heavy booster prototype are visibly under construction. Most recently, Starship SN9 was stacked to its full height, kicking off nosecone installation while still at the build site (unlike SN8). SN10’s completed tank section is likely ready to begin flap installation within the next few days, while Starship SN11 is perhaps a week or two behind that. Additionally, large tank sections of Starships SN12, SN13, SN14, SN15, and (most likely) SN16 are already completed and have all been spotted in the last few weeks.
Some ~90% of the above work was likely started after Starship SN8 first left the factory and rolled to the launch pad on September 26th. In many regards, SN8 has been the first to reach multiple major milestones, largely explaining the relatively plodding pace of its test program compared to SN4, SN5, and SN6.


Ultimately, SN9’s imminent completion – effectively a superior, more refined copy of SN8 – means that Starship SN8’s utility to SpaceX is rapidly deteriorating. The company would almost assuredly never skip an opportunity to learn, meaning that there’s no plausible future in which SN8 testing doesn’t continue, but that doesn’t mean that SpaceX can’t turn its risk tolerance to 11. In essence, accept a 67% (or higher) chance of Starship SN8’s violent destruction but learn as much as possible in the process. As long as good data is gathered, SN8’s launch debut will be a success for Starship whether the rocket lands in one or several pieces.
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.