News
SpaceX wants to attempt Starship booster catch during first orbital launch
An updated document submitted by SpaceX to the US Federal Communications Commission (FCC) has revealed details about the company’s plan for the first Starship booster ‘catch’ attempt.
The document follows a different batch submitted by SpaceX in June 2021, when the company detailed its plans for Starship’s orbital launch debut as background while requesting permission from the FCC to use Starlink dishes for in-flight telemetry. A month earlier, a different request focused on more standard telemetry antennas had already revealed that even if the mission went perfectly, Starship would not fully reach orbit on its first attempted spaceflight. It also confirmed that SpaceX had no intention of recovering the upper stage or Super Heavy booster assigned to Starship’s launch debut – a sort of implicit acknowledgment that success was (then) not expected on the first try.
Twelve months later, SpaceX has submitted an updated overview of Starship’s orbital launch debut in a new request for permission to use multiple Starlink dishes on both stages. While most of the document is the same, a few particular details have changed about Super Heavy’s role in the mission.
This time around, SpaceX says that the Super Heavy booster will “will separate[,] perform a partial return[,] and land in the Gulf of Mexico or return to Starbase and be caught by the launch tower.” Prior to this document, SpaceX’s best-case plans for the first Super Heavy booster to launch never strayed from a controlled splashdown in the Gulf of Mexico – potentially demonstrating that it would be safe to attempt booster recovery on the next launch but all but guaranteeing that the first booster would be lost at sea.
A year later, SpaceX appears to be a bit more confident and wants to leave itself the option to attempt to recover the first Super Heavy booster that launches. However, the company has dramatically complicated the process of testing early Super Heavy and Starship recovery (and thus reuse) by fully removing traditional and predictable landing legs and designing its latest prototypes such that the only way they can be recovered in one piece is with a giant mechanized ‘launch tower’ nicknamed Mechazilla.
The launch tower and its three mobile arms will play a crucial role in all aspects of orbital Starship launches. The first arm swings out to brace Super Heavy for Starship installation and connect the upper stage to power, propellant supplies, and other launch pad utilities. A more exotic pair of arms nicknamed ‘chopsticks’ has a more complex job. On top of using the chopsticks to lift, stack, and demate Starships and Super Heavy boosters and almost any weather and wind conditions, SpaceX wants to use the arms as an incredibly complex and precarious rocket recovery system.
For a booster or Starship “catch,” the rocket will approach the tower, enter the gap between the splayed arms, hover in place while the arms close around it, and eventually come to rest on hardpoints that appear to offer about as much surface area as a coffee table. Based on a simulation of the process shown by Elon Musk, calling it a “catch” is a misnomer, as the arms will mainly move in one dimension (open/close) and can’t actually ‘grab’ the rocket in any real sense. As built and shown, they are closer to a tiny fixed landing platform capable of minor last-second positional adjustments.
Eventually, the chopsticks could shave a small amount of time off of post-recovery processing, removing the need for a crane (or the same arms) to attach to a landed booster or ship. They could also shave off the dry mass required for landing legs, though all interplanetary ships will still need legs. However, they will also inherently make proving their own efficacy a nightmare. By all appearances, the current recovery mechanisms on the arms and the landing hardpoints on ships and boosters mean that a ‘catch’ could fail if either stage is more than a foot or two from a perfect bullseye or rotated a few degrees in the wrong direction. With the method SpaceX has devised, even the tiniest error could easily end with a massive, pressurized, partially-fueled rocket destroying the chopsticks and plummeting a few hundred feet to the ground, guaranteeing an explosion that could damage surrounding infrastructure or start fires that might.
In the event of larger anomalies during a landing attempt, Starship or Super Heavy could accidentally impact the launch tower, damaging or even outright destroying the skyscraper-sized structure. Ultimately, the immense risk posed by any catch attempt means that unless SpaceX has miraculously gotten the design of everything involved nearly perfect on its first try, the company will have to be extraordinarily cautious and expend a large number of ships and boosters to avoid rendering its only Starship launch tower unusable.
At least to some extent, SpaceX likely knows this and Super Heavy would likely need to be in excellent health and perform perfectly during the ascent and boostback portions of its launch debut to be cleared for a catch attempt. Ultimately, Starship’s first orbital launch could end up being even more of a spectacle than it’s already guaranteed to be.
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
