News
SpaceX team spotted removing Block 5 landing legs prior to teardown analysis
Teslarati photographer Tom Cross has captured SpaceX technicians removing the landing legs from the first Falcon 9 Block 5 booster, signaling that the end of recovery operations are near.
Of note, it appears that SpaceX chose to conduct this recovery much like previous ones by removing the rocket’s legs instead of retracting them, a feature of the Block 5 upgrade prominently noted by CEO Elon Musk and other company officials. A brief time-lapse shows workers carefully removing the legs in a well-worn ballet of heavy machinery, skirting around the massive rocket with expertise developed over the better part of two years of sea and land recoveries of Falcon 9 and Falcon Heavy boosters.
There are a number of possible reasons for SpaceX choosing to remove B1046’s landing legs the ‘old-fashioned’ way, most relating to the fact that this particular booster is a critical pathfinder for the entire future of Falcon 9 Block 5. Musk described this attitude in a lengthy and detailed prelaunch briefing:
We are going to be very rigorous in taking this rocket apart and confirming our design assumptions to be confident that it is indeed able to be reused without being taken apart. Ironically, we need to take it apart to confirm that it does not need to be taken apart.
Both COO Shotwell and Musk have briefly discussed the new functionality of the upgraded legs in the past few weeks, indicating that they are capable of being rapidly and repeatedly stowed without being removed from the rocket, whereas all past booster reuse has required the slow removable and equally slow reattachment of landing legs, assuming Block 3 and 4 boosters even reuse their same landing legs. At a minimum, Musk’s above comment already makes it clear that SpaceX has no plans to reuse this booster immediately, instead conducting an extremely thorough teardown analysis to verify that wear and tear from high-speed atmospheric reentry is within an acceptable range.
SpaceX technicians busy themselves removing Falcon 9 Block 5’s massive recovery hardware. (Tom Cross)
Equally plausible, choosing to remove B1046’s landing legs instead of testing the new retraction mechanisms may better preserve the leg hardware in its post-landing state, providing engineers and technicians cleaner and more representative data. One final obvious possibility is that the process of flight-testing new Block 5 leg hardware caused damage or led to some off-nominal telemetry and other visible faults, thus preventing them from retracting.
Because the next Block 5 booster (B1047) is likely nearing its own debut after a thorough round of testing in Texas, captured by an aerial photographer, SpaceX may be pushing hard to complete its post-landing analysis of B1046 as quickly as possible to make way for the imminent launches of several new boosters. If the company hopes to maintain its impressive 2018 flight rate of one launch every two weeks throughout the rest of the year, they will need to refly Block 5 boosters at least 10 times – the last flight-proven commercial Block 4 launch (CRS-15) is currently scheduled for early July, leaving roughly half of all 2018’s upcoming launches manifested on Block 5 Falcon 9/Heavy rockets. Falcon Heavy’s second launch has in fact been pushed back by several months per The Planetary Society, indicating that the construction of the first Block 5 center booster has taken a back seat to the more pressing concerns of Falcon 9 Block 5 boosters, upper stages, and fairings needed to avoid additional customer launch delays.
B1046’s final landing leg is removed and carried off with a forklift, presumably for teardown analysis at a SpaceX facility. (Tom Cross)
Regardless, the first successful and nearly-complete recovery of a Falcon 9 Block 5 booster marks a huge milestone for SpaceX. So long as the imminent teardown analysis does not reveal anything especially unexpected, the rocket company is quickly closing in on true rapid reuse with Octagrabber/Roomba’s steady routinization of robotic rocket saving, yet another intact fairing half recovery, and the good condition of B1046 after a relatively hot reentry and landing.
-
- Just boopin’ an orbital-class rocket with a huge metal component, NBD. (Tom Cross)
-
- (Tom Cross)
-
- A toasty Block 5 landing leg shows off a new patina for SpaceX’s upgraded thermal protection material.
-
- (Tom Cross)
Follow us for live updates, behind-the-scenes sneak peeks, and a sea of beautiful photos from our East and West coast photographers.
Teslarati – Instagram – Twitter
Tom Cross – Twitter
Pauline Acalin – Twitter
Eric Ralph – Twitter
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 is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
