News
Rocket Lab secretly launches revolutionary satellite and readies for US launch debut
Rocket Lab’s recent flawless return to flight mission nicknamed “I Can’t Believe It’s Not Optical,” set the company up for loftier goals in the latter half of 2020 in a big way. Returning to operation after an in-flight anomaly and subsequent investigation is a massive accomplishment for any launcher. Returning to flight and debuting a pathfinder satellite developed and built in-house, however, solidified Rocket Lab as a full end-to-end space systems company.
For good measure, company founder and chief executive officer, Peter Beck, hopes to round out the year by activating two more Electron launchpads – one of which will be the launcher’s first US-based launch location dedicated to supporting missions for the United States government. Furthermore, following Electron’s seventeenth flight, Rocket Lab hopes to recover the expended first-stage booster – and perhaps more importantly, a mountain of data – as a stepping stone to launch vehicle reuse, a practice pioneered and solely dominated by SpaceX.
A return to flight and an introduction to space systems
Just eight weeks after Electron’s ill-fated thirteenth flight resulting in the loss of a second stage and all customer payloads due to an in-flight electrical anomaly, the next Electron was raised at Launch Complex 1 in Mahia, New Zealand. The fourteenth flight of Electron was a dedicated mission for San Francisco-based information services company, Capella Space. Initially announced, the mission deployed a single microsatellite called “Sequoia” to an approximate 500km circular orbit. Peter Beck later confirmed the mission also secretly featured the successful deployment of Rocket Lab’s first in-house designed and built satellite called “First Light.”
“First Light” is a pathfinder spacecraft based on Rocket Lab’s configurable Photon satellite platform. According to Rocket Lab, it exploits Electron’s Kick Stage, “a nimble but powerful extra stage on Electron designed to circularize payload orbits.” The Kick Stage is designed as a satellite bus with extended capabilities to transition into a satellite – Photon – and performing an independent standalone mission. This is exactly what occurred with “First Light.”
Following the deployment of the “Sequoia” microsatellite, Rocket Lab teams signaled the Kick Stage to enable the standalone Photon capabilities. The command transitioned the spacecraft from a delivery vehicle to a fully functional satellite for the very first time. “First Light” serves as the testbed of many upgraded components including improved management systems for power, thermal, and attitude control.
in a statement provided by Rocket Lab Beck said, “Launching the first Photon mission marks a major turning point for space users – it’s now easier to launch and operate a space mission than it has ever been. When our customers choose a launch-plus-spacecraft mission with Electron and Photon, they immediately eliminate the complexity, risk, and delays associated with having to build their own satellite hardware and procure a separate launch.”
Eventually, the extended Photon capabilities of the Kick Stage will be used to support lunar and interplanetary missions. Beck has gone on record many times stating that Rocket Lab is working toward funding a private mission to Venus with a more robust version of the Photon platform which will deploy a probe to collect information about the Venusian atmosphere.
Counting down to Electron’s first launch from Virginia
On September 17, just two weeks after introducing the world to “First Light,” Rocket Lab announced the final successful Electron wet dress rehearsal at its new Launch Complex 2 (LC-2) at the Mid-Atlantic Regional Spaceport in Wallops Island, Virginia.
-
The wet dress rehearsal is a standard preparatory practice of raising the rocket vertical on the launchpad, fueling the rocket, and conducting a practice run of all countdown systems and procedures ahead of a launch attempt. This gives launch teams the opportunity to ensure that the rocket is prepared for flight and work out any kinks that may arise ahead of sending the vehicle to space. The countdown is carried down to T-0 and then the vehicle is emptied and safed.
Recently, Rocket Lab was granted a five-year Launch Operator License by the Federal Aviation Administration for the LC-2 site enabling the space systems company to support up to ten Electron missions a year from U.S. soil. The new operator license combined with the one previously procured for Launch Complex 1 in New Zealand allows Rocket Lab to support up to 130 flights of the Electron rocket globally per year.
It was speculated that Electron’s next flight – and the first launch from LC-2 in Virginia – would be the dedicated STP-27RM mission coordinated by the U.S. Space Force’s Space and Missile Systems Center. The first from Virginia will launch a single microsatellite for the Air Force Research Laboratory’s Monolith program. However, the first mission from Virginia is still waiting on a debut date to be identified.
In order for Electron to fly from Virginia, NASA must first certify Electron’s Autonomous Flight Termination System (AFTS) – a protective measure that will automatically destroy the rocket in a safe manner should anything anomalous occur during first stage flight. Electron’s AFTS has already previously flown numerous times from New Zealand. The first flight from Virginia, however, will be the first time a vehicle will launch from the Mid-Atlantic Regional Spaceport with an AFTS.
15 launches, 3 launch pads, and a booster recovery
Until then, Rocket Lab is busy preparing for flight fifteen from New Zealand. The recently announced mission, nicknamed “In Focus,” is a rideshare mission featuring nine SuperDove satellites for Planet Labs and one payload for Spaceflight Inc. customer Canon Electronics Inc.
While preparing for the next flight, nearby Rocket Lab is simultaneously wrapping up construction on yet another launch pad. Launch Complex 1B is very much near completion and is expected to be brought online by year’s end. And that’s not the last goal Rocket Lab looks to achieve by the new year.
Beck has time and time again confirmed that the seventeenth flight of Electron will be the first attempt at recovering an expended first stage booster. Eventually, the company will attempt to catch the booster as it is falling back to Earth under the canopy of a parachute by utilizing a helicopter equipped with a specialized grappling hook. The first attempt at recovering a booster is not expected to be quite as elaborate.
Rocket Lab has strengthened the first-stage booster enough to survive the return trip. Until now, the booster has slammed into the ocean water and broken up into small bits. With the assistance of improved software and a deployable parachute, the booster of flight seventeen is expected to softly float back for a gentle water landing with the assistance of “recovery pontoons” as described in a Twitter post by Beck.
As of now, Rocket Lab has not identified any target dates for the upcoming milestones. The company has previously stated that the first mission from Virginia is expected to launch in the third quarter of 2020. Electron’s next flight – “In Focus” – from New Zealand is expected in the first half of October. Rocket Lab will provide future launch and development updates on their social media accounts.
-
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.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
