News
Rocket Lab briefly catches Electron booster with a helicopter on first try
In a significant achievement, public launch provider Rocket Lab has – with a few caveats – successfully used a helicopter to catch the booster of its Electron rocket out of mid-air on the very first attempt.
The company began working on ways to recover and reuse the booster of its tiny Electron rocket in 2019, going back on a promise repeatedly made by founder and CEO Peter Beck in the years prior. Due to just how small the Electron rocket is, it was generally assumed that Beck wasn’t wrong to avoid attempting to recover or reuse its parts of it. However, that attitude quickly changed when the need to ramp up launch cadence became a leading priority. Soon after, Beck revealed that Rocket Lab engineers had looked more carefully at the problem and concluded that Electron booster recovery was more feasible than assumed.
Once the problem was no longer deemed insurmountable, the allure of reuse – intrinsically multiplying the effectiveness of any given production line if done right – was irresistible.
While the change in attitude made Rocket Lab the second company after SpaceX to begin seriously developing the ability to recover and reuse orbital-class liquid rocket boosters, the approach it would need to take for a rocket as small as Electron was almost nothing like that used by Falcon boosters. Instead of multiple in-flight engine ignitions, supersonic retropropulsion, steerable fins, and a propulsive landing, Electron would rely on several parachutes to slow itself down, use small thrusters (not unlike Falcon) for attitude control, and be actively captured out of mid-air by a crewed helicopter.
Ironically, demonstrating the sheer size gap between Electron and Falcon 9, Electron booster recovery more closely resembles Falcon 9 fairing recovery. Weighing in at around one ton (~2200 lb) per half, or about as heavy as an entire Electron rocket booster, each fairing half mainly just controls its attitude with cold-gas thrusters while passively reentering Earth’s atmosphere. Fairing halves then deploy a GPS-guided parafoil and gently splash down on the ocean surface before being fished out of the water by a waiting ship.
That is exactly how Rocket Lab trialed Electron recovery on several prior attempts, fishing intact boosters out of the Pacific Ocean after gentle ocean landings. For a while, SpaceX even attempted to catch fairings out of mid-air – albeit with a highly-modified ship and net instead of a helicopter and hook. However, when the company realized it could easily reuse fairing halves that landed in the ocean, it fully abandoned catch attempts.
In Electron’s case, it’s no surprise that Rocket Lab still pursued catch-based recovery while SpaceX was simultaneously giving up on the practice. Put simply, it would be incredibly difficult to reliably and affordably reuse a liquid rocket booster – and liquid rocket engines especially – after dunking them in saltwater.
That’s also why the success of Rocket Lab’s first operational catch attempt has caveats. While the company did successfully catch the booster out of mid-air, the pilot – who holds final authority for the sake of safety – observed unusual behavior not seen during testing after hooking Electron and chose to release the booster early. Thankfully, it still managed a soft landing in the ocean and was recovered by ship, but despite statements from Beck to the contrary, that seawater exposure will almost certainly make it impossible to fully reuse. To call the attempt a total success, the helicopter would have needed to drop the booster off on the recovery ship’s deck, fully avoiding a bath.
Above all else, even if the catch didn’t last, Rocket Lab successfully launched 34 small satellites and payloads into orbit for several paying customers and briefly caught the booster that launched them with a helicopter. The attempt was arguably far more successful than not and likely leaves Rocket Lab just a little more practice and a few small optimizations away from a perfect recovery. Then the company can shift its focus to the next goal: the first Electron booster reuse.
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
