News
SpaceX grapples with failed Falcon 9 landing as Starlink launches slip
The follow-on effects of SpaceX’s failed February 15th booster landing have begun to roll in, triggering at least one to two weeks of delays for several upcoming Starlink launches.
Already delayed a few days and leapfrogging an even more beleaguered Starlink-17 launch originally scheduled as far back as late January, SpaceX Falcon 9 booster B1059 lifted off for the sixth time without issue last Monday. The rocket seemed to perform fine, separating as planned around 150 seconds after launch and leaving Falcon 9’s expendable upper stage to continue on its way to orbit with a ~16-ton (~35,000 lb) batch of 60 Starlink satellites.
During B1059’s “reentry burn,” a period where Falcon boosters reignite three of their Merlin 1D engines to both slow down and create a sort of shield with the rocket exhaust that burn produces, something went wrong. Unusual sparks quite literally flew during and after the last few seconds of the burn and the bright flare produced by Falcon 9’s engines dissipated far slower than usual. Eventually, when B1059 was expected to fire up for one final landing burn, all that was visible from a live camera on SpaceX’s drone ship was two flashes of warm light.
It’s hard to say for sure without an official comment from SpaceX but those flashes may have been the drone ship camera capturing the mid-air breakup and fast-fire (or explosion) of the Falcon 9 booster some 20-30 seconds before a planned soft landing. The odd behavior observed during and after the reentry burn could have also indicated a partial loss of thrust in one or more of B1059’s three reentry engines.
Unofficial analysis of the telemetry data included in SpaceX’s public webcasts more or less aligns with that theory, suggesting that Falcon 9 B1059 reentry burn lasted a nominal duration but didn’t slow the rocket down as much as it should have. As a result, B1059 would have been traveling faster and at a lower altitude relative to a nominal Starlink mission, which is exactly what’s observed in a comparison between Starlink-18 and Starlink-19, virtually identical launches completed 11 days apart.
That same telemetry also suggests that Falcon 9 B1059 may have lost thrust before its first burn completed, possibly explaining why the timing of launch events on SpaceX’s webcast and an official SpaceX.com launch timeline began to drastically diverge after MECO. MECO itself occurred about five seconds behind that schedule, gradually ballooning to a difference of more than half a minute for Starlink satellite deployment an hour after launch.
That observation increases the similarity between Starlink-5 and Starlink-19, both of which seemingly suffered a boost phase anomaly, off-nominal reentry burn performance, and booster loss well before landing. SpaceX’s Starlink-5 engine-out anomaly and failed booster landing grounded the company for about five weeks before it eventually returned to flight on April 22nd, 2020.
SpaceX appears to be working to mitigate the impact from Starlink-19 but a delay of at least 1-2 weeks is in order based on current schedules. Perhaps the most chronically delayed SpaceX launch of all time, Starlink-17 – originally scheduled to fly as early as “Jan. 29, Jan. 30, Jan. 31, Feb. 1, Feb. 2, Feb. 4, Feb. 5, Feb. 7, Feb. 17,” and Feb. 25 – is now on the calendar for no earlier than (NET) February 28th. Starlink-20, planned to launch in the last week of February, has been tentatively pushed to no earlier than March 7th. Both dates are assuredly subject – and likely – to change as SpaceX works to close out its Starlink-19 anomaly investigation and implement any necessary changes.
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
