News
SpaceX's next launch ready to go just weeks after in-flight engine failure
Just weeks after SpaceX suffered its first in-flight rocket engine failure since 2012, the company has scheduled its next launch on April 16th.
Set to lift off no earlier than (NET) 5:31 pm EDT (21:31 UTC) from NASA Kennedy Space Center (KSC) Launch Complex 39A (Pad 39A), the mission will be SpaceX’s seventh dedicated launch of 60 Starlink satellites. Known as Starlink-6 in reference to the sixth launch of finalized Starlink v1.0 spacecraft, a successful mission could leave SpaceX with some ~410 operational satellites in orbit – significantly more than twice as big as the next largest constellation.
More importantly, Starlink-6 will mark a sort of return-to-flight for Falcon 9 after booster B1048 suffered an in-flight engine failure and missed its landing attempt on March 18th. While the booster was able to sacrifice itself to ensure that the overall Starlink-5 mission was a success, any in-flight failure is still a significant event in aerospace. To that end, very little is known about the Starlink-5 anomaly, aside from announcements that both NASA and the US Air Force will be paying close attention to the results of SpaceX’s internal investigation. Starlink-6’s imminent launch is now the latest piece of that puzzle, shedding some welcome light on the situation.
Unsurprisingly, an in-flight Falcon 9 engine failure more than piqued the curiosities of high-profile SpaceX customers like NASA and the US Air Force (and Space Force), both of which have some of the company’s most important launches ever scheduled within the next few months. Most notably, NASA noted on March 25th that the space agency and SpaceX “are holding the current mid-to-late May [target for Crew Dragon’s inaugural astronaut launch] and [will] adjust the date based on review of the [engine failure] data, if appropriate.”
At time of comment, a few aspects of the unfortunate Starlink-5 engine failure were already positioned in SpaceX’s favor. Critically, it was the first time that a flight-proven Falcon 9 booster launched on its fifth orbital-class mission, meaning that the very same booster – B1048 – had already launched four times prior. In aerospace parlance, the mission thus served as a pathfinder for SpaceX’s reusable rocketry technology, venturing into new territory. Since it began internal Starlink launches, SpaceX has used those opportunities to take its most recent reusability leaps without risking customer payloads in the process.
At least for now, neither NASA or the USAF have plans to fly their most valuable payloads on flight-proven Falcon boosters. While that may change over the next several years, it means that SpaceX’s Starlink-5 anomaly and missions like Crew Dragon Demo-2 and GPS III SV03 – both set to fly on new boosters – share much less commonality. Of course, this assumes that B1048’s March 18th engine failure is directly related to the booster’s exceptionally flight-proven nature. Were SpaceX’s investigation to conclude that the fault had nothing to do with multi-launch wear and tear, it would likely ground Falcon 9 and Falcon Heavy indefinitely.
Instead, SpaceX – knowing full-well the potential consequences of two consecutive in-flight failures – has decided to attempt another orbital-class Starlink launch and booster landing less than a month after Starlink-5. To be clear, while SpaceX could choose to throw caution to the wind on an internal launch, it’s doubtful that it would haphazardly take such a substantial risk. Instead, Starlink-6’s April 16th launch date strongly suggests that SpaceX is already reasonably confident that it’s both determined the likely culprit of last month’s engine failure and identified ways to prevent its reoccurrence.
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
