News
(Update: scrubbed) SpaceX’s next Starlink launch to break rocket fairing reuse record
Update: SpaceX says that today’s Starlink-12 launch attempt was scrubbed due to a mysterious “recovery issue.” Liftoff from Kennedy Space Center Pad 39A is now scheduled no earlier than (NET) 1:57 pm EDT (17:57 UTC) on Friday, September 18th.
Prior to the announcement, fairing recovery ship GO Ms. Tree was spotted diverting to a North Carolina port for unknown reasons, leaving twin ship Ms. Chief to recover both fairing halves. Based on bouy data, conditions at the Atlantic Ocean fairing and booster recovery zones appeared to be moderately challenging but far from unreasonable and SpaceX has been happy to point to recovery weather for past launch delays.
SpaceX has revealed that its next Starlink launch will mark a new first for Falcon 9 payload fairing reuse, reaching a milestone that took booster reuse 18 months in less than a year.
Scheduled to lift off no earlier than (NET) 2:19 pm EDT (18:19 UTC) on Thursday, September 17th, the Starlink-12 (v1.0 L12) mission will be SpaceX’s 11th in 2020 alone and 13th overall. If things go according to plan, it could leave SpaceX’s nascent constellation just two or so months away from the beginning of the first public beta tests of Starlink internet service.
Meanwhile, Falcon 9 booster B1058 will be attempting its third launch less than four months after its flight debut, an unprecedented cadence of reuse for SpaceX. Aside from likely ensuring that B1058 becomes the proud holder of SpaceX’s first and second place records for booster turnaround (time between launches), the mission also continues an unexpected trend: the near-extinction of Falcon 9 static fire tests.
SpaceX’s first successful Falcon booster landing happened in December 2015, just a few months shy of five years ago. In March 2017, two years later, SpaceX reused a Falcon 9 booster on an orbital-class launch for the first time in history. Some 21 months after that historic milestone, SpaceX launched the same Falcon 9 booster for the third time, kicking off a relentless series of reusability firsts that continue to be made to this day.
Now, SpaceX says it’s about to launch the same Falcon 9 payload fairing half for the third time in a significant and unexpected first for fairing reuse. Constructed primarily out of a carbon fiber-aluminum honeycomb composite material, Falcon fairings are dramatically more fragile – and reaches much higher altitudes and velocities – than the boosters SpaceX has cut its teeth on recovering and reusing.
Compared to booster reuse, it’s quite the achievement. SpaceX first managed to launch the same Falcon 9 booster three times in December 2018, ~33 months after the first booster reuse. Measured from SpaceX’s first fairing reuse, completed in November 2019 as part of the first Starlink v1.0 launch (Starlink-1), the company will have managed to cross the three-flight fairing reuse barrier less than 11 months later – a full three times faster than SpaceX’s booster reuse program took to achieve the same milestone.
Additionally, prior to SpaceX’s September 16th reveal, it was purely up to speculation whether the company would be able to reuse Falcon fairing halves more than once, particularly when a given fairing half is only fished out of the ocean. If successful, Starlink-12 will prove that Falcon fairing halves can be reused at least three times regardless of whether SpaceX was/is able to catch said halve in a recovery ship’s net.
No more static fires?
Meanwhile, SpaceX appears to be turning a major corner on Falcon 9 launch operations. Of all 93 Falcon 9 launches since the rocket’s June 2010 debut, every single one has been preceded by a combined wet dress rehearsal (WDR) and static fire test a few days or weeks prior to liftoff. Effectively simulating a launch 1:1 up to the exact moment before liftoff, SpaceX has used static fires to verify vehicle health and firewall minor quality assurance lapses for as long as it’s been launching rockets.
In a major operational change that has almost flown under the radar, SpaceX appears to have killed the practice of universal prelaunch static fires beginning with Starlink-8 in June 2020. Including Starlink-8, of the seven launches SpaceX has completed in the last three months, just three (GPS III SV03, Starlink-9, and Starlink-10) included Falcon 9 static fire tests prior to liftoff. A step further, two of the four static fire-free launches were for major commercial missions – not retiring risk on SpaceX’s own Starlink launches, in other words.
As of today, Falcon 9 has completed 65 successful launches since the last catastrophic vehicle failure (Amos-6, September 2016) and 74 consecutively-successful launches if Amos-6 (which never lifted off) is excluded. As of 2020, it’s the most reliable US launch vehicle currently in operation, surpassing ULA’s Atlas V several months ago. In fewer words, it’s not actually surprising (in retrospect) that SpaceX has begun to relax its position on static fires – especially considering that there isn’t another launch provider on Earth that static fires rockets before every launch.
More likely than not, SpaceX will continue to static fire Falcon 9 and Heavy boosters at the launch pad before their flight debuts and upon customer request. If launch or post-flight inspection data offer reason(s) for concern, SpaceX may still choose to static fire boosters out of caution. Additionally, SpaceX shows no signs of ending the practice of performing full booster static fires in McGregor, Texas as part of acceptance testing, still leaving it a step beyond traditional rocket manufacturers, which only static fire individual engines.
Regardless, SpaceX’s 13th Starlink launch will be streamed live as usual, with coverage beginning around 15 minutes prior to liftoff.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.
An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.
Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.
The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.
Footage of the plane crash from earlier today | #ONLYinDADE pic.twitter.com/iGoOtnd6cD
— ONLY in DADE (@ONLYinDADE) September 6, 2026
Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.
The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.
Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.
Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
Tesla crosses major Unsupervised Self-Driving milestone
