News
SpaceX’s flight-proven Falcon 9 and drone ship fleet ready for duo of launches
SpaceX is gearing up for a duo of flight-proven Falcon 9 launches and drone ship landings on both coasts of the United States, set for liftoff from Cape Canaveral’s Kennedy Space Center and Vandenberg Air Force Base no earlier than (NET) November 15th and 19th, respectively.
#SpaceXArmada: Moments ago, outbound tugboat Hawk with droneship OCISLY in tow in @PortCanaveral. Destination: Booster core landing/recovery LZ of Thursday's #Eshail2 launch, approx 408 mi E of @NASAKennedy. pic.twitter.com/n5FvBdIvpt
— Cowboy Dan (@CowboyDanPaasch) November 12, 2018
East Coast activities
On the East Coast, drone ship Of Course I Still Love You departed from Port Canaveral late last night (Nov 11) as Falcon 9 B1047 rolled onto Pad 39A for a preflight static fire test, where the rocket will be filled with a full complement of fluids (TEA/TEB, helium, nitrogen, oxygen, kerosene) and all nine Merlin 1D engines are ignited in order to replicate the seconds just prior to a real launch. That static fire test was originally expected to occur on November 10 or 11 but has obviously been pushed back a day to Nov. 12, likely meaning that the rocket’s launch – carrying Qatari communications satellite Es’hail-2 – will slip 24 hours to 3:46pm EST (08:46 UTC) on the 16th,
Following the unfortunate loss of Amos-6 during a preflight static fire in September 2016, SpaceX has since made a reasonable move away from performing static fires with payloads integrated atop the rocket, unless the customer specifically requests that it be done that way to save time. As such, Falcon 9 must be brought horizontal, rolled back to the hangar, inspected, and finally have the payload and fairing attached to the rocket, a sensitive process that demands nuance and time. Combined with an analysis of data gathered during the static fire, this process – when all goes as planned – can take at least 48 hours from start to finish, and longer still if any minor off-nominal behavior is observed or the launch customer has additional requirements (typically reserved for NASA and national security-related missions).
- B1047 horizontal at Pad 39A, November 11. (Tom Cross)
- B1047 made an extraordinary ring vortex rainbow as it smashed through Max Q, the point of highest aerodynamic stress on the rocket. (Tom Cross)
- B1046 seen mid-static fire at Pad 39A ahead of Falcon 9 Block 5’s launch debut, May 2018. (Tom Cross)
Because rockets like Falcon 9 are extraordinarily intricate and finely-tuned machines, perfectly nominal launch-related events are few and far between. In reality, the time between static fire rollout and launch readiness is rarely less than three days (72 hours), not including the process of rolling the fully-integrated rocket back out to the pad, aligning and securing the vehicle and transporter-erector (TE) over the flame trench, and finally attaching all umbilical connections and verifying vehicle health. Speaking generally, four to five days is a good rule of thumb for the time it takes to complete Falcon 9’s static fire and return the rocket to the pad after attaching the payload.
Still, it’s always a good sign when a drone ship leaves port, much like OCISLY did on the evening of the 11th. The journey to its destination will take 2-3 days, meaning that the drone ship will be ready to catch Falcon 9 whenever the rocket is ready to launch.

Drone ships and sooty rockets, oh my!
On the West Coast, SpaceX is also getting ready for drone ship Just Read The Instructions (JRTI) to depart Port of San Pedro in anticipation of a presumed sea recovery of Falcon 9 following the NET Nov 19 launch of a multi-satellite rideshare mission known as SSO-A. While SpaceX currently holds two recovery licenses for the booster, one by sea and one at the land-based LZ-4 pad, it’s possible that the company will be forced to use JRTI despite the fact that Falcon 9 will have plenty of propellant left to return itself to the launch site (RTLS). United Launch Alliance’s (ULA) next Delta IV Heavy rocket is currently on-pad with a presumably very expensive National Reconnaissance (NRO) satellite attached roughly 1.5 miles northeast of SpaceX’s LZ-4 – the rest of the gaps are easy enough to fill in.
- Falcon 9 Block 5 booster B1046 seen during both of its post-launch landings. (SpaceX/SpaceX)
- B1047 completed its first successful launch in July 2018. (Tom Cross)
- B1047 seen rolling into 39A’s integration hangar for refurbishment on July 31st. (Reddit – Kent767)
JRTI was spotted by Teslarati photographer Pauline Acalin performing some rare sea trials on November 10 after spending several weeks berthed at port for routine maintenance and deck repairs. Fairing recovery vessel Mr. Steven has also been undergoing some unusual modifications, now proudly sporting what can only be described as a steel horn recently installed on the tip of his bow deck. After sitting out a catch attempt during the launch of SAOCOM 1A to prepare for controlled helicopter drop tests performed over a period of several weeks in October, Mr. Steven will most likely be ready for another stab at operational fairing recovery during SSO-A.
Both rockets – B1047 to the East and (presumed) B1046 to the West – are flight-proven, meaning that they have flown operational orbital missions prior to their upcoming launch attempts, B1047 launched communications satellite Telstar 19V in July 2018, while B1046 has actually performed two successful launches already, Bangabandhu-1 in May and Telkom 4 (Merah Putih) in August.
For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!
Elon Musk
Tesla may test customer-owned Robotaxis as early as next month, Musk says
Elon Musk says that Tesla could test adding customer-owned vehicles to the Robotaxi platform as soon as December.
In a reply on X to an Austin-based Uber driver who uses a Model Y with Full Self-Driving and keeps only 49-63% of fares after the platform’s cut, Musk wrote:
“Coming soon. If things well, may start trials next month. Much better to manage a fleet of cars than have to drive just one car by yourself!”
@apostlejohn @WorldlyReviewer Coming soon. If things well, may start trials next month.
Much better to manage a fleet of cars than have to drive just one car by yourself!
— Elon Musk (@elonmusk) November 16, 2026
The exchange highlights the appeal of passive income from an autonomous vehicle versus actively driving for rideshare platforms.
This potential December start is technically earlier than prior company guidance, but it also aligns with the currently-projected first delivery of the Tesla Cybercab, a vehicle that has no manual controls.
Nevertheless, Tesla planned to bring customer vehicles into the fleet later on. During Tesla’s Q3 earnings call, AI leadership had pointed to roughly the second quarter of 2027 for customer vehicles joining the network. Musk’s comment suggests an accelerated pilot, most likely beginning in Austin, where Tesla’s Robotaxi service has operated longest and where new features typically roll out first.
December is also the target month for the first customer deliveries of the Cybercab. In mid-November, Tesla began inviting select buyers to purchase the purpose-built, two-seat vehicle for personal use at $29,990 plus a required $299 monthly Autonomy Subscription, with estimated deliveries in Austin.
Tesla Cybercab goes on sale for $29,990, slated for December deliveries
Those initial private Cybercabs are restricted to personal use within existing Robotaxi zones and do not automatically include commercial network participation; the large majority of Cybercabs are expected to remain Tesla-owned fleet vehicles.
The coincidence of the two December milestones underscores Tesla’s parallel paths. Customer Model Ys already on the road with FSD hardware could rapidly enlarge the vehicle pool for unsupervised trials, while the Cybercab, which is void of a steering wheel or pedals and equipped with only dedicated Robotaxi hardware, arrives as a purpose-built platform.
Hardware differences, such as additional cameras or cleaning systems on company Robotaxis, may constrain which Model Ys are eligible at the outset. Regulatory approvals, insurance arrangements, and software readiness will also determine whether the “if things go well” condition is met.
For owners, successful trials would fulfill a vision Musk first sketched in Tesla’s 2016 Master Plan: vehicles that earn money while their owners sleep or work.
Combined with the arrival of privately owned Cybercabs in the same month, December could mark the transition from Tesla-controlled Robotaxi operations to a broader ecosystem in which both company fleets and customer vehicles contribute to the company’s autonomous ride-hailing platform, which continues expanding.
Elon Musk
FAA turned down free Starlink offer before nationwide ground stop, Elon Musk says
Elon Musk says the FAA declined free Starlink terminals before last week’s nationwide ground stop.
Elon Musk says the Federal Aviation Administration could have had Starlink backing up its air traffic communications for free, and he is pointing to last week’s nationwide ground stop as proof it was needed. “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,” Musk wrote on X Monday.
Musk was quoting his own post from February 2025, when he wrote that “the ancient system that is rapidly declining in capability was made L3Harris,” while a newer replacement system from Verizon was “not yet operational.” The Department of Transportation has not responded publicly to Musk’s account of the offer.
The outage behind the post began at about 3:30 p.m. ET on Friday, November 13. According to the FAA’s own account, its legacy equipment became unstable when data began flooding its FAA Telecommunications Infrastructure network at a rate of 1,000 connection attempts every four to five seconds. The agency traced the flood to two locations, a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas, where L3Harris had been installing a new router.
Instability spread across 17 of the FAA’s 22 Air Route Traffic Control Centers. The agency grounded departures nationwide while about 3,500 aircraft already in the air landed safely, and lifted the stop at 8:15 p.m. ET. Operators canceled roughly 12,462 flights that day, though the FAA notes not all of those were directly caused by the ground stop. L3Harris blocked the two sites to stabilize the network, and the FAA disabled the same router function on about 60 similar units. Officials found no sign of a cyberattack.
Transportation Secretary Sean Duffy has blamed prior administrations and dated systems, and has called on Congress to fund a $50 billion overhaul of the system.
Musk’s history with the FAA network goes back to early 2025, when he was leading the Department of Government Efficiency. He claimed on X that the system was failing and putting air travelers at risk, initially blaming Verizon before correcting himself to name L3Harris. The FAA confirmed at the time it was testing Starlink terminals, one at its Atlantic City, New Jersey facility and two at “non-safety critical sites” in Alaska. SpaceX said it was providing the kits at no cost and had no intent to take over any existing FAA contract.
Duffy described Starlink then as “part of a solution” rather than a replacement. By July 2025, the FAA told lawmakers it was not considering replacing its L3Harris and Verizon telecommunications contracts with Starlink.
Whether Starlink would have prevented Friday’s disruption is not clear. The FAA described a fault inside its terrestrial network rather than a loss of connectivity, and Musk did not explain how satellite links would have been used. His post does put SpaceX back in the conversation as Washington debates how to pay for the next air traffic control system. SpaceX already supplies Starlink to commercial airlines for inflight connectivity, and United’s rollout required FAA certification for each aircraft type.
News
Tesla makes $3.3 billion Cybercab bet at Giga Berlin
It is no secret Tesla is prioritizing Cybercab production as it plans to launch a fleet of fully autonomous vehicles without steering wheels or pedals across the world. Today, it made a €3 billion bet to do so in Europe.
Tesla announced on November 16, that it will invest €3 billion (approximately $3.3 billion) to expand its Gigafactory in Grünheide near Berlin, its only vehicle manufacturing site in Europe.
🚨 BIG NEWS: Tesla will invest €3 billion (~$3.3B) to expand Giga Berlin.
A new production building could eventually build up to 1 million Cybercabs a year. Construction targeted for H1 2027, production in 2029. Permit filing comes later this year. https://t.co/hsM8kNaJRR
— TESLARATI (@Teslarati) November 16, 2026
The investment will fund a major new production building—roughly twice the size of the existing main hall—and supporting infrastructure, including an additional wastewater treatment plant. The new facility is designed to produce up to one million Cybercabs annually once fully scaled, alongside continued Model Y output.
Tesla plans to file the building permit application before the end of 2026, according to Tagesspiegel, drawing on a broader expansion application submitted in 2023 that targets one million vehicles per year overall. Construction is scheduled to begin in the first half of 2027, with Cybercab production starting in 2029.
The company is already recruiting several hundred workers for construction and production planning. The site currently employs about 12,600 people after recent hiring of roughly 2,000, and it is ramping Model Y production toward 7,500 vehicles per week (around 375,000 annually).
This vehicle expansion comes just days after plant manager André Thierig indicated at the Automobilwoche Congress on November 11 that full battery cell production at Grünheide is on track for mid-2027.
The factory already produces electrodes, which are currently shipped to Texas for cell assembly and returned; the goal is to complete 4680-format cells on site using Tesla’s dry-electrode process, targeting up to 18 GWh annually.
The cumulative investment in the cell operation approaches €1 billion and is expected to create more than 1,500 jobs. Once operational, Giga Berlin would become the first plant in Europe to produce everything from battery cells to finished vehicles under one roof, raising the European content of its Model Ys to roughly 90 percent.
For Tesla’s German operations, the twin moves deepen vertical integration and reduce dependence on transatlantic and Chinese supply chains.
They also contrast sharply with the broader German automotive industry, which faces high costs, weak demand, and job cuts; Brandenburg officials have welcomed the investment as a significant economic boost that creates hundreds of new positions and strengthens the region as a manufacturing hub.
Tesla’s expansion advances its strategic pivot toward autonomy and robotaxis. The Cybercab is intended to become a high-volume product; adding major European capacity diversifies production beyond the United States and supports Elon Musk’s vision of autonomous vehicles comprising the majority of Tesla’s future output.
Combined with localized 4680 cell production, the plans position Giga Berlin as a more self-sufficient, technologically advanced European base, enhancing competitiveness as regulatory and market conditions favor higher local content.






