News
Elon Musk reveals SpaceX Falcon 9 survived a water landing test
Following the picture-perfect launch of GovSat-1 on Wednesday afternoon, SpaceX CEO Elon Musk took to Twitter with an extremely unusual bit of news. After separating from the second stage, events relating to Falcon 9’s first stage recovery operations were heard live in the background of SpaceX’s live coverage, leading to some additional intrigue around an already odd situation.
B1032, a flight-proven (reused) booster tasked with launching GovSat-1 on its second mission, was seen with landing legs and grid fins on its sooty exterior – a confusing appearance due to SpaceX’s statement that the core would be expended into the ocean after launch. Thankfully, Elon Musk’s tweets provide at least the beginning of an answer for the several oddities.
This rocket was meant to test very high retrothrust landing in water so it didn’t hurt the droneship, but amazingly it has survived. We will try to tow it back to shore. pic.twitter.com/hipmgdnq16
— Elon Musk (@elonmusk) January 31, 2018
As stated above, GovSat-1’s Falcon 9 booster (1032) was apparently being used to test an exceptionally aggressive landing burn in lieu of a drone ship beneath it. The lack of drone ship begins to make more sense with the added knowledge that 1032 was testing experimental landing procedures: in the relatively likely eventuality that something went wrong, the massive booster would have likely impacted Of Course I Still Love You at an extremely high velocity. Similar impacts have occurred before as SpaceX gradually perfected the new technologies and operational knowledge necessary to recover orbital-class rockets, but a basic understanding of rocketry implies that 1032’s OCISLY impact would have been uniquely destructive, likely taking the ship out of action for at least several weeks of repairs.
This would pose an inherent problem for the imminent launch of Falcon Heavy, with the center of three first stages currently scheduled to attempt a landing aboard the very same drone ship in less than a week. Under optimum conditions (sans huge explosions and general destruction), OCISLY and its entourage of support vessels simply could not complete the journey back to Port Canaveral and the subsequent return to sea that would have been necessary to recovery both GovSat-1 and Falcon Heavy’s center core. Add in the potential need for repairs and expending GovSat-1 was a no-brainer for the launch company: Falcon Heavy’s center core could easily see at least one additional launch after it is recovered, whereas the twice-used 1032 effectively reached the end of its useful life after it separated from the second stage and GovSat payload earlier today.
Falcon 9 1038 aboard Just Read The Instructions after the launch of Formosat-5. (SpaceX)
As a result, SpaceX appears to have continued a trend of exploiting flight test opportunities to the greatest extent practicable by tasking B1032 with an experimental landing attempt. More specifically, Elon quickly added that the landing burn attempted by 1032 involved the ignition of three of the booster’s nine Merlin 1D engines during landing, whereas all SpaceX landings up to this point have occurred with a single Merlin 1D ignition. While the company already routinely utilizes three engines during some boostback and reentry burns, landing burns have always featured a single engine. However, by using three engines, it is entirely possible that SpaceX hopes to eventually move towards even more aggressive landing burns. While the obvious downsides likely include difficulty maintaining control and increased stresses on the booster, the benefits are also pretty inherent. By using more engines, the length of the landing burn could be drastically shortened, resulting in far more efficient propellant usage by minimizing losses to gravity (every second the rocket is trying to go upwards is a second fighting against Earth’s gravity, which pulls the rocket down at ~9.8 meters/second squared).
Incredibly, the booster somehow managed to pull off that three engine landing burn with some success, made apparent by the fact that it is intact and floating in the Atlantic, with some hope of being towed back to land. This is almost certainly the first time SpaceX has ever successfully landed a booster in the ocean without a subsequent breakup, an incredible achievement for a rocket that likely experienced exceptional stresses during reentry and landing. Time will tell how this impacts SpaceX’s future recovery efforts, but it is certainly promising as a method of extracting just a little extra performance from reusable Falcon 9s. In other words, future Falcon 9 missions might be able to carry heavier payloads into higher orbits while still being able to land at sea or even on land. Exciting times!
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
