Connect with us

News

Rocket Lab to resume launches following in-flight anomaly investigation

The Rocket Lab Electron takes flight from New Zealand. (Rocket Lab)

Published

on

Less than a month after the complete loss of customer payload due to an in-flight anomaly, Rocket Lab has announced that it is ready to return its small-class Electron rocket to flight. Company CEO, Peter Beck, during a media briefing Friday (July 31) said that the Electron second-stage “re-entered the atmosphere and burned up” resulting in a failed July 4 launch of the Electron and complete loss the customer payload of seven small satellites. Beck went on to state that through a collaborative investigation with the Federal Aviation Administration Rocket Lab was “able to quickly reconstruct what happened and the AIB board (Accident Investigation Board) was able to confidently narrow down the issue to a single electrical connection.”

The thirteenth flight of the Electron carried seven small satellites, all Earth-imaging inspiring the “Pics Or It Didn’t Happen” mission name. The rocket initially experienced a flawless launch from the company’s Launch Complex-1A on New Zealand’s Mahia Penninsula and everything seemed like it was going to plan until the video feed cut out unexpectedly shortly after the nominal ignition of the second-stage which was intended to carry the payloads to orbit.

The launch was completely event free during the first-stage ascent, stage separation, second stage ignition, and payload fairing jettison, then trouble occurred. Beck stated that the electrical connection that went bad during the second-stage of the flight was “incredibly unusual because it was able to evade all of the pre-flight acceptance testing.” Beck went on to explain that “while all of the testing showed no issues, after a period of time one of the joints had high resistance and that high resistance led to heating. That heating then led to thermal expansion of one of the components. That thermal expansion and heating enabled some of the potting components – that are around that joint to keep it secure from vibration – to flow.”

Once the potting compound used to secure electrical connections was able to heat up and essentially melt – or began to flow – the electrical connection become unsecured and led to the interruption in electrical current throughout the second-stage. Beck stated that “when the video stops (in the webcast) is exactly the point (of failure).” Although the video cut out, Rocket Lab ground stations continued to receive telemetry data of the flight’s progress due to the amount of redundancy with the systems aboard Electron “telemetry is the only way you can reconstruct this stuff so we have a very high priority of those (data) channels” Beck said.

https://twitter.com/SpaceflightNow/status/1279536259715813376

With the immense amount of data that was received during the flight and throughout the second-stage shutdown Rocket Lab was able to quickly determine the cause of the error and perform tests to determine exactly what occurred during the failed flight. “The vehicle as it flies every flight has just a huge amount of instrumentation. That coupled with a graceful shutdown coupled with full telemetry stream throughout the whole anomaly, we were really able to quickly reconstruct what happened” Beck said.

The vast amount of data and the ability to sufficiently replicate the incident now means that Rocket Lab has a plan of action in place to mitigate any failures – of this nature – on future missions. “We can actually mitigate (the anomaly) very easily through a slight change in production processes, but more importantly we can screen for it in our current vehicles and stock through more in-depth testing procedures.”

To that end, the Rocket Lab Electron is set to return to flight in August, an impeccable turn around time following an anomaly investigation.”I’m very proud of the way the team has been able to identify this issue and rectify it so quickly” Beck said. He gave high praise to the entire Rocket Lab team for relentlessly working toward determining, not only the cause of the anomaly but working toward a solution for a quick return to flight. “Literally ten minutes after we saw some anomalous behavior during the flight, the team already started to work it and they haven’t stopped. They’ve been relentless” Beck said.

Advertisement
-

The customer payload that will fly aboard the return to flight and fourteenth mission of Electron launch is expected to be announced very soon. Rocket Lab did state that following a successful launch from the LC-1A complex in New Zealand, the following mission would be the first to take place from the brand new Launch Complex 2 located at the Mid-Atlantic Regional Spaceport at NASA Wallops in Virginia. Although an American private company, Rocket Lab predominately launches from New Zealand. The upcoming mission will be the first Electron flight to occur from American soil.

Beck closed the media briefing by stating that Rocket Lab looks forward to returning to operational status and launching Electrons every month, if not bi-weekly. He expressed that Rocket Lab is looking to the future and hopes to achieve a full recovery effort of the first stage booster via a helicopter and a specially designed grappling hook with the seventeenth flight of Electron. He also hinted that “there’ll be a couple of other little surprises as well, as we execute some other programs that have been cooking up in the background.”

Space Reporter.

Advertisement
Comments

Elon Musk

Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash

An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.

Published

on

By

Photorealistic depiction of the Amazon Prime plane crash in Miami on Sep 3, 2026 near a fleet of Tesla Cybercab
Photorealistic depiction of the Amazon Prime plane crash in Miami on Sep 3, 2026 near a fleet of Tesla Cybercab

An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.

Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.

The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.


Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.

The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.

Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.

Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.

Continue Reading

News

Tesla crosses major Unsupervised Self-Driving milestone

Published

on

Credit: Tesla

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.

Continue Reading

News

Tesla Robotaxi will be a 24/7 service: here’s when

Published

on

Credit: @AdanGuajardo/X

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.

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.

Continue Reading