News
Rocket Lab “In Focus” mission ready to launch after scrubbed first attempt
On Wednesday, October 21, Rocket Lab held a launch countdown ahead of the fifteenth mission of its small rocket, Electron. The mission nicknamed “In Focus,” was slated to take off from the company’s primary launch pad at Launch Complex 1 on the Mahia Peninsula in New Zealand. Ultimately, the launch attempt was scrubbed due to an off-nominal oxygen sensor.
Rocket Lab did not immediately disclose a new targeted launch date, but did state that the launch window for the “In Focus” mission extended for nearly two-weeks. Rocket Lab founder and chief executive officer, Peter Beck, said in a Twitter post that, “the team’s taking the time to make sure it’s just the sensor and nothing else.” Beck also stated that weather moving into the area could pose a challenge for finding a new acceptable launch date.
Just two days later, Rocket Lab announced that a second launch attempt of the rideshare mission supporting ten Earth-observation satellites would occur at 5:14pm EDT (21:14 UTC) Wednesday, October 28. Should the second attempt be thwarted by uncooperative weather, daily opportunities to launch Electron are available until November 3.
What’s on board:
The fifteenth overall flight of Electron and fifth mission of 2020, is a rideshare mission that supports payloads for Canon Electronics Inc. and Earth-imaging services provider Planet. The payload, carefully mounted on the Rocket Lab Electron Kick Stage, consists of one nine SuperDove Flock 4e Planet microsatellites inside of Rocket Lab’s protective Maxwell payload dispensers. The entire stack is topped by Canon Electronics Inc.’s CE-SAT-IIB satellite procured by mission management provider Spaceflight Inc. All ten payloads are securely fixed atop the Electron Kick Stage.
The Electron Kick Stage – a capable extra stage on Electron – is designed to circularize orbits and deploy multiple payloads to independent and precise destinations. The Kick Stage is powered by a small, but powerful Curie engine. All ten of the satellite payloads aboard the “In Focus” mission are expected to be delivered to a 500km morning-crossing Sun Synchronous Orbit.
Prior to flight, the payload was encapsulated inside of the Electron’s protective payload fairing. In traditional fashion, Rocket Lab outfitted the fairing with the mission patch artwork created specifically for Electron’s fifteenth “In Focus” mission.
After encapsulation inside the fairing, the payload was integrated with the Electron first-stage booster. After a short trip from the assembly facility, Electron was raised vertically at Launch Complex 1 to complete a successful wet dress rehearsal – a standard pre-flight run-through of all launch procedures. The purpose of the wet dress rehearsal is to run through all of the launch day procedures including filling the rocket with RP-1 – a rocket grade kerosene – and liquid oxygen.
Launch teams conducted the practice launch on Thursday, October 8 proceeding through all countdown milestones right up until T-0 and engine ignition. This process ensures that the vehicle and launch teams are ready for flight. It also provides an opportunity to catch and address any anomalies that may arise prior to launch day.
What to expect on launch day:
Approximately four hours ahead of the launch attempt Rocket Lab will once again return Electron to vertical launching position at Launch Complex 1 in New Zealand. In the time prior to the fueling of the rocket, safety checks of the launch complex will be conducted and marine hazard zones and airspace will be closed and secured to all traffic. Fueling of the rocket will begin just two hours ahead of the launch attempt.
At T-0 Electron will be propelled to space by nine 3D-printed Rutherford electro-turbopump engines. Approximately 2 minutes and 34 seconds after liftoff Electron’s first stage will separate while the second stage engine ignites. Unique to the Electron, a “hot swap” of the batteries powering the electro-turbopump of the second stage will be performed – swapping out the power source of expelled batteries with new ones – at 6 minutes and 32 seconds after liftoff. The second stage is expected to arrive at an initial parking orbit approximately 8 minutes and 54 seconds after liftoff.
A brief ten seconds later the Kick Stage will separate from the second stage. Approximately 51 minutes and 06 seconds after liftoff the Kick Stage’s Curie engine will ignite to propel the payloads to their final circular Sun-Synchronous Orbits. Payload deployment is expected at the 60-minute mark after liftoff.
Rocket Lab will provide a live hosted webcast of the second launch attempt of the “In Focus” mission on Wednesday, October 28 on the company’s YouTube channel approximately fifteen minutes before liftoff. Should a scrub occur, Rocket Lab will announce a new targeted launch date on the company’s social media channels.
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.
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.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
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.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
