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.
News
Tesla Cybercab stands to gain from new Trump autonomy rules
Tesla Cybercab stands to gain from new rules that the Trump Administration is aiming to enforce on autonomous vehicles. On Thursday, NHTSA, under the Trump Administration’s U.S. Department of Transportation, commenced rulemaking on the Federal Motor Vehicle Safety Standards (FMVSS).
This effort aims to eliminate the mandate for manual brake pedals in vehicles that are designed to be driven exclusively by automated driving systems. This would impact the Tesla Cybercab, which the company has stated would operate without a steering wheel or pedals.
Tesla Cybercab launch is imminent after latest sighting at Giga Texas
The Trump Administration is looking to revise FMVSS No. 135, which requires standard braking systems on light-duty vehicles.
Currently, the regulation requires light-duty cars to use traditional manual braking systems that allow operators to slow the vehicle. With the advent of self-driving in the U.S., these regulations need updating, and these are the changes that could come to FMVSS No. 135:
- Removes requirements for hand- or foot-operated brake controls for vehicles designed never to be operated by a human. Existing rules still apply to AVs that retain manual controls.
- All subject vehicles must still meet the same stopping distance performance criteria via alternative testing procedures.
- While this update ensures AVs can physically stop when commanded, NHTSA is separately developing safety performance requirements for AVs in real-world driving scenarios.
- NHTSA will continue to use its broad defect enforcement authority to investigate unsafe ADS behavior and oversee recalls.
As autonomy becomes a greater part of passenger travel, these types of rule adjustments will be more than reasonable. It will give manufacturers the ability to self-certify their vehicles and avoid any red tape that could ultimately delay the deployment of these vehicles.
Administrators are also incredibly excited about the opportunity to play a role in the advancement of self-driving vehicles.
“We are at the cusp of the greatest technological revolution in vehicle technology since the innovation of the Model T,” NHTSA Administrator Jonathan Morrison said. “If we want America to lead the way, we have to reimagine our regulatory framework. That’s why under Secretary Sean Duffy’s AV Framework, NHTSA is tearing down pointless barriers to innovative designs while strengthening the fundamental safety requirements that matter and holding AV developers accountable for safe performance.”
The Cybercab entered mass production at Gigafactory Texas in April. Tesla ultimately plans to push the vehicle into its Robotaxi fleet, potentially when frameworks like these are established.
News
Tesla plans production boost at Giga Berlin following rebound in Europe
Tesla plans to boost production at its Gigafactory Berlin plant in Germany following a sharp rebound in sales and demand in Europe after a softer 2025.
The plans put Tesla in a better position to compete with strengthening companies in Europe and potentially other markets; demand indicators show Tesla is much better off than in 2025.
Last year was a tough year for Tesla in terms of overall demand in Europe. The company produced over 200,000 vehicles at the German plant last year, a soft figure compared to the 375,000 vehicles Tesla lists as its current capacity at the factory.
🚨 Tesla said this morning it will ramp up production at Gigafactory Berlin to a volume of 7,500 vehicles per week.
This is a 20 percent boost in production. Tesla will hire 1,000 new employees to help with the increase.$TSLA pic.twitter.com/kravKfRO5n
— TESLARATI (@Teslarati) June 25, 2026
Tesla’s overall European sales dropped significantly last year due to a variety of factors. However, sales are rebounding, and demand is strong once again, and only getting stronger. Tesla is now planning to bump production of Model Y vehicles at Giga Berlin upward by about 20 percent. It will also bring 1,000 new jobs to the plant.
Tesla confirmed the details of its planned production expansion in Germany this morning. It is a strategy to keep up with strengthening demand.
In Q1, Tesla saw a record 61,000 vehicles produced at Giga Berlin. European registrations rebounded sharply, with Model Y seeing 117 percent increases in March 2026 compared to last year. Germany alone saw stark increases, with a quadrupling in registrations to 9,252 units.
This trend continued in other key European markets, including France, Denmark and Sweden. Tesla registrations were up over 46 percent in some of these markets, and Model Y continued its trend as a top BEV in the market.
Demand has been recovering strongly in 2026, giving Tesla a reason to expand production efforts at the factory. These increases signal management’s confidence in sustained or growing European pull for Berlin-built vehicles.
News
Tesla and driver sued by family of woman killed in Texas crash: what we know
Tesla is being sued by the family of the woman who was killed in a Texas crash involving a Model 3. The driver, who is also being sued, claimed the vehicle was operating on Autopilot mode, but Tesla executives have come out challenging that claim, stating that the driver of the vehicle overrode the system.
The lawsuit was filed by 76-year-old Martha Avila’s daughter and her husband, who allege a “design defect” involving a Tesla and a failure to warn. The suit alleges negligence against Tesla and the driver, Michael Butler.
Butler “stated he was operating with an automated driving assistance system engaged at the time of the crash,” the Harris County Sheriff’s Office said in a statement. He showed no signs of intoxication and was cooperative, the Sheriff’s Office said, according to NBC News.
Just after reports of the crash and numerous headlines that immediately blamed Tesla’s Autopilot suite, both Tesla CEO Elon Musk and Head of AI Ashok Elluswamy challenged that. Musk said the crash made “no sense” given that Tesla Autopilot and Full Self-Driving do not travel at the speeds the door cameras captured the car traveling at, which Tesla says was 73 MPH.
Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration
Elluswamy also revealed that Tesla data showed Butler overrode the system by pressing the accelerator to 100%, and that the pedal was compressed fully even after the car had crashed. Tesla has not released this data to the public, likely because it is communicating with agencies like the NHTSA on an investigation.
The suit uses a Washington Post analysis of government data that “identified at least 17 fatal incidents linked to Tesla Autopilot.”
This is far from the first time an accident has been blamed on Autopilot. A fatal crash in Texas was blamed on Autopilot several years ago, but when Tesla released data to the NTSB, which was investigating the crash, Autopilot was not available where the crash occurred, and Autosteer was never enabled, meaning the car was manually controlled at the time of the accident.
“Application of the accelerator pedal was found to be as high as 98.8 percent,” the NTSB said in their findings. The highest recorded speed in the five seconds leading up to the impact was 67 miles per hour. The area where the crash occurred is residential, and Texas State laws… pic.twitter.com/XGD97NHVZ2
— TESLARATI (@Teslarati) March 18, 2026
More information on the accident will be released as Tesla works with agencies to find the cause of the crash. From personal experience, it is hard to imagine Tesla Autopilot or FSD operating in this manner. It drives sometimes too cautiously in residential areas in parking lots, at least in my experience. Speeding happens, but at this rate in this type of area, it is hard to believe.
We look forward to more details being released with time.