News
Rocket Lab’s first step towards SpaceX-style rocket reuse set for next Electron launch
Just over a year ago, Rocket Lab announced intentions to recover the first-stage of its small Electron launch vehicle, potentially making it the second private company on Earth – after SpaceX – to attempt to recover and reuse an orbital-class rocket.
In a media call earlier this week, Rocket Lab founder and CEO, Peter Beck, revealed that the first recovery attempt has been expedited to mid-November and will occur following the next flight of Rocket Lab’s Electron rocket.
Like competitor SpaceX, Rocket Lab aims to recover its first stage Electron booster to decrease production time and increase launch cadence. Rocket Lab now has three launchpads to launch from and is licensed by the Federal Aviation Administration to carry out up to 130 launches per calendar year. In order to increase the launch cadence of the Electron, production times need to decrease. This can effectively be accomplished with the recovery, refurbishment, and reuse of the small, carbon composite rocket booster.
Recovery Doesn’t Happen Overnight
Initially, the first step of recovering an expended first stage – a guided and controlled soft water landing under a parachute and retrieval by sea-vessel – was intended for the seventeenth launch of the Electron prior to the end of this calendar year. However, Rocket Lab is now targeting the sixteenth launch for the first recovery attempt, a mission appropriately nicknamed “Return to Sender.” When asked what prompted the move to an earlier launch, Beck stated to reporters, “the guys got it done in time. With a new development like this, it’s always very dependent on how the program runs and the program ran very successfully.”
Rocket Lab has been working toward this recovery attempt for quite some time. In late 2018, Rocket Lab began collecting data during launches to inform future recovery efforts and determine whether or not it would even be feasible with a small-class rocket. The first major block upgrade of the Electron booster debuted on the tenth flight, “Running Out of Fingers,” in December 2019.
The first recovery milestone, a task Beck called getting through “the wall,” was achieved following the tenth flight. And again in January 2020 following a successful eleventh flight of Electron. The “wall” Beck refers to is the Earth’s atmosphere. Returning a booster through the atmosphere intact requires extreme precision in terms of re-entry orientation and how efficient the heat shield is.
Because the Electron is a small-class rocket, Rocket Lab was able to collect enough data from previous flights to determine that the carbon composite frame could withstand a fall through the atmosphere given a precise enough angle of attack to sufficiently distribute thermal loads. According to Beck, the process is referred to as an “aero thermal decelerator.”
Small Rocket Following in Big Footsteps
SpaceX, Elon Musk’s space exploration company pioneered booster landing, recovery, and reuse efforts when the first Falcon 9 booster to successfully land returned to Landing Zone 1 at Cape Canaveral Air Force Station in Florida on December 21, 2015. SpaceX approaches the process of booster re-entry in a different way than what Rocket Lab has decided to attempt with Electron.
The Falcon 9 boosters perform a re-orientation flip and use the engines to perform what is known as a boost-back burn to set the rocket on the path to return to the Earth’s surface. The rocket then autonomously deploys titanium grid-fins that essentially steer, and slow the booster down as it falls through the atmosphere. Finally, the engines are re-ignited during a series of burns, and landing legs are deployed to propulsively land either at sea aboard an autonomous spaceport droneship or back on land at a landing zone.
The booster of Rocket Lab’s tenth mission in 2019 was outfitted with guidance and navigation hardware and cold gas attitude control thrusters used to flip and orient the booster to withstand the stresses of re-entry. Otherwise, no other hardware was incorporated to reduce the stresses of re-entry or slow the vehicle as it fell through the atmosphere. The booster made it through “the wall” intact and eventually slowed to a rate less than 900km per hour by the time it reached sea-level for an expected impact.
-
Eventually, Rocket Lab imagines its small Electron booster to be caught during a controlled descent under parachute canopy with a specially equipped helicopter and grappling hook. Beck and his team spent weeks outfitting a test article with prototype parachutes that were manufactured in-house.
A low-altitude drop test of a test article to simulate an Electron first stage was performed and a helicopter was able to snag the test article mid-air and deliver it one piece. Essentially, this proved that the concept was at least feasible and the small-class rocket could in fact be fully recovered to eventually be refurbished and reused. Since the completion of this drop test in April of 2020, the parachute design has been reevaluated and many more drop tests have been conducted. The final drop test with a more traditional system of a drogue parachute and an 18m ringsail type main parachute occurred in August of 2020 with a first stage simulator.
Next up, Rocket Lab plans to use the finalized design of the parachute system to bring Electron home safely for a soft landing in the Pacific Ocean. After which the booster will be collected by a recovery vessel, similar to the process that SpaceX uses to scoop its payload fairings from the water.
“Bringing a whole first stage back intact is the ultimate goal, but success for this mission is really about gaining more data, particularly on the drogue and parachute deployment system,” said Beck. With the parachute system verified the teams should be able to make any further iterations for a full capture and recovery effort on a future mission relatively quickly.
Rocket Lab will try to fully recover the “Return to Sender” expended first-stage booster once it separates approximately two and a half minutes after liftoff from Launch Complex 1 on the Mahia Penninsula of New Zealand. Electron will support a rideshare payload of thirty smallsats. The window to launch the sixteenth Electron mission opens on November 16 UTC (November 15 PT / ET). A hosted live webcast of the launch and recovery attempt will be provided on the company website approximately fifteen minutes prior to liftoff.
Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.
Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.
🚨 Tesla looks to have installed Camera Washers on the side repeater cameras on Robotaxis in Austin
pic.twitter.com/xemRtDtlRR— TESLARATI (@Teslarati) January 23, 2026
First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.
This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.
However, this part has since been removed and is no longer visible on the EPC.
Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?
While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.
AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.
This could be the first hint of that’s where we are headed.
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Tesla briefly offered this Robotaxi part for your personal car
Tesla Robotaxi gets sweeping but polarizing change
