News
Rocket Lab to resume launches following in-flight anomaly investigation
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.
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.
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.”
Tesla’s reason for Starlink integration on Cybercab might surprise you, as the company’s Head of AI, Ashok Elluswamy, finally shed some light on the reason they are putting a satellite internet terminal on its ride-hailing-geared vehicle.
On Monday, Tesla officially confirmed that it would integrate Starlink V5 terminals into Cybercab vehicles, something many Tesla fans had figured the company would do, as the vehicle is primarily geared toward giving rides without any passenger intervention.
Starlink V5 directly integrated in Cybercab pic.twitter.com/FxzTtzjB6I
— Tesla (@Tesla) July 20, 2026
The ability to access the internet would allow riders to work or play in the car with their devices. It seemed like a more-than-reasonable feature to add to the Cybercab, which made its way off the production lines for the first time earlier this year.
Tesla reveals first vehicle model to receive Starlink integration
However, the move is not for the rider, as Elluswamy confirmed on Monday night. Instead, it’s actually for Tesla to be able to have a constant connection to the cars in the Robotaxi fleet so it can troubleshoot issues, contact riders, or resolve other issues.
Elluswamy said:
“It is still not required for safe operation of the vehicle. Connectivity is primarily meant for navigation, customer service and, in general, fleet management.”
It is still not required for safe operation of the vehicle. Connectivity is primarily meant for navigation, customer service and, in general, fleet management.
— Ashok Elluswamy (@aelluswamy) July 20, 2026
Many initially assumed the option of constant connectivity would be enabled on the Cybercab for passenger entertainment or work. With the Cybercab, passengers won’t be doing anything but enjoying the ride, so it seemed more than logical that they would be hanging out with Starlink internet access as an amenity.
However, Tesla’s primary concern with Robotaxi is safety, and nailing these first unsupervised rides is a crucial step to setting a good narrative on how effective driverless transportation can be.
Being able to get in touch with passengers or a vehicle if something is wrong is a crucial part of the overall experience, and preventative measures are being taken by Tesla to ensure a smooth process, even in the worst-case.
Tesla has expanded its Robotaxi program in Florida to include two new cities: Tampa and Orlando.
This marks the second and third cities to be added to the company’s available locations for autonomous ride-hailing in the Sunshine State, joining Miami, which was the first Florida city to offer Robotaxi rides.
Tesla announced the addition of Orlando and Tampa to the Robotaxi program on Tuesday morning. The cities now join Austin, Dallas, Houston, Miami, and the San Francisco Bay Area as locations where Tesla can operate its Robotaxi platform:
Robotaxi now in Tampa & Orlando! pic.twitter.com/fYtmXgJq3O
— Tesla Robotaxi (@robotaxi) July 21, 2026
These rides are unsupervised, as AI Head Ashok Elluswamy confirmed the suite in Florida is operating without safety drivers or anyone within the cabin to assist with operation.
Orlando Tesla Robotaxi Operation
The geofence in Orlando covers a prominent irregular shaded zone on the map, roughly 4-6 miles across in key dimensions, so it likely measures somewhere between 25 and 45 square miles, which is comparable to other early Tesla launches in other cities.
It encompasses central and southern areas bounded by major highways including SR-417 and SR-528, including parts of the Orlando metro core, tourism-adjacent zones, and residential/commercial districts. This represents an initial targeted rollout in a tourist-heavy region, positioned for quick expansion via Tesla’s software updates.
Tampa Tesla Robotaxi Operation
In Tampa, the shape of the geofence is a shaded polygon covering key neighborhoods, explicitly including West Tampa, Tampa Heights, Hyde Park, and downtown Tampa proper, with boundaries along major roads and the Hillsborough River area.
This focuses on high-demand central zones and will offer tourists and citygoers rides without drivers.
Robotaxi Progress
Tesla has been operating Robotaxi since last June, when it launched in Austin. The geofences in most regions have already expanded several times since their launch last year, but the bigger complaint is vehicle availability. Tesla has been working to add more Robotaxi-enabled vehicles to its fleet.
The company still plans to utilize its Cybercab, a new vehicle that is being produced at Gigafactory Texas, for the Robotaxi suite alongside the Model Y, which has been the vehicle of choice for Tesla with early operations.
News
Tesla’s AI Chief just hinted at something big for FSD v14 lite owners
Tesla’s AI chief suggests the newest FSD v14 Lite build may finally go wide release.
Tesla’s head of AI, Ashok Elluswamy, noted on Sunday that the newest FSD v14 Lite build rolling out to Hardware 3 cars is likely the version that goes to wide release, the strongest signal yet that Tesla is near to closing out an early access phase that Hardware 3 owners have waited more than a year for.
Elluswamy made the comment in response to an extensive review from Tesla owner Zack, known on X as @BLKMDL3, who tested software version 2026.20.6.10 and detailed the changes in a lengthy post. “FSD v14 Lite (for Tesla AI3 hardware vehicles) review.
The update restarts a rollout that had stalled after its initial release. Tesla began pushing FSD v14 Lite to Hardware 3 early access drivers on June 29, bringing driving behavior learned on the newer Hardware 4 computer down to the more limited chip that has powered Tesla vehicles built between 2019 and early 2023. That release, as we covered in detail, gave roughly 4 million HW3 vehicles their first meaningful update since being frozen on version 12.6 in early 2025.
Tesla Full Self-Driving v14 ‘Lite’ Release Notes: new capabilities and features
The latest build adds features that bring Hardware 3 closer in line with what Hardware 4 owners already have. FSD can now start directly from park without a brake pedal confirmation, a change Zack called a small but meaningful quality of life improvement. The interface also picks up the blue “P” park icon, approaching destination alerts, and a dedicated Self-Driving app with streak tracking, all details previously exclusive to the AI4 branch of v14, as outlined in Tesla’s original release notes.
The stakes around Hardware 3 go beyond software polish. Tesla sold the Full Self-Driving package for years on the promise that every vehicle equipped with it had the hardware needed to eventually drive itself without supervision. That promise broke down during Tesla’s Q1 2026 earnings call, when Musk acknowledged HW3 cars could not run unsupervised FSD, prompting Tesla to offer trade-in discounts and hardware retrofits alongside the Lite software track.
Tesla confirmed HW3 can’t do Unsupervised FSD but there’s more to the story
Tesla has continued to frame v14 Lite as the primary path forward for the HW3 fleet, telling owners in April that international markets would follow the U.S. rollout once regulatory approvals came through. For now, HW3 owners in the early access group are the only ones running the new build. A broader rollout would mark the second major software delivery to the legacy fleet since Tesla first released FSD v14 to Hardware 4 vehicles, and the first sign since June that the Lite program is still moving rather than stuck in early access limbo.
Tesla’s reason for Starlink integration on Cybercab might surprise you
Tesla Robotaxi program expands in Florida to two new cities
