News
SpaceX readies for astronaut capsule recovery backup plan as rocket drone ship deploys to landing zone
Mission objectives of the SpaceX Crew Dragon Demo-2 test flight, have already commenced days ahead of the scheduled launch attempt. On Wednesday, May 27th at 4:33 pm EDT, Elon Musk’s rocket launching – and landing – company, SpaceX, will set out to achieve more firsts than it has ever attempted in one launch. The final Crew Dragon test flight will shuttle NASA astronauts Bob Behnken and Doug Hurley to the International Space Station for the very first time. Along with the primary mission objective to deliver the astronauts safely, many secondary objectives are built into the mission profile. One of which is autonomously turning the Falcon 9 booster around shortly after launch to land on a floating barge in the middle of the Atlantic Ocean.
During the late hours of Saturday, May 23rd, a trusted veteran member of the SpaceX fleet of recovery vessels, Tug Hawk, returned to Port Canaveral to transport SpaceX’s autonomous spaceport drone ship, Of Course I Still Love You (OCISLY) to the designated booster recovery zone some 510km downrange. It seems that Tug Hawk and its crew returned specifically to assist with the recovery efforts of SpaceX’s highest-profile launch to date as there was already another tug at Port Canaveral available to assist that was not used. The arrival was captured by long-time port activity documenter, Julia Bergeron, and reported by the unofficial Twitter SpaceX recovery vessel tracking account, SpaceXFleet.
The SpaceX recovery fleet portion of the Demo-2 mission got underway on the morning of Sunday (May 24th). Space Coast local Greg Scott was at Port Canaveral to capture Tug Hawk’s departure with OCISLY in tow just twelve hours after arriving. About an hour later, the OCISLY support vessel that carries cargo and crew essential for booster recovery efforts, GO Quest, departed. It will take Tug Hawk and OCISLY approximately two days to travel to the recovery zone, arriving about 24 hours before the launch attempt.
The propulsive landing of a booster at sea is not a new concept for SpaceX. However, it is a practice that can be somewhat tricky to get right every time due to a multitude of factors. Recently, SpaceX suffered the loss of the Falcon 9 boosters B1056 and B1048 following recent Starlink satellite launches. Both boosters suffered unrelated issues with high winds and software glitches resulting in failed attempts to stick the landing on OCISLY. However, SpaceX successfully demonstrated the reliability of the Falcon 9 landing capability with the flawless launch and landing of the April 22nd Starlink Falcon 9 B1051 booster.

A special circumstance of the Demo-2 mission is the added recovery requirements of the Crew Dragon capsule. With Crew Dragon launching from LC-39A at the Kennedy Space Center in Florida and splashdown designated for the Atlantic Ocean, various recovery zones span almost the entire length of the United States’ eastern seaboard and across the Atlantic Ocean to Ireland. Special recovery zones also are located throughout the Gulf of Mexico.
Typically, the recovery of a crew capsule would only be thought to occur upon mission end when it is on approach for splashdown after re-entry. However, the specially equipped SpaceX Crew Dragon recovery vessels, GO Searcher and GO Navigator, are required to be able to respond to a number of locations during launch and through the entire duration of Crew Dragon’s time on orbit chasing down the International Space Station prior to docking – for Demo-2 that will be nineteen hours. This is to ensure that in the unlikely event of Crew Dragon experiencing an emergency pad or launch abort scenario, the crew aboard can be safely rescued.
To this end, GO Searcher departed Port Canaveral days ago destined for the Naval Air Station in Pensacola on Florida’s west coast. GO Navigator will remain at Port Canaveral until Crew Dragon returns for a splashdown following the conclusion of Demo-2. Dual Dragon recovery vessels stationed on either side of Florida ensures that Hurley and Behnken can be rescued should they require emergency recovery.
Should Demo-2 pass SpaceX’s upcoming final Launch Readiness Review scheduled for Monday, May 25th, all will proceed toward the launch attempt on Wednesday, May 27th at 4:33 pm EDT.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
News
Tesla crosses major Unsupervised Self-Driving milestone
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.
News
Tesla Robotaxi will be a 24/7 service: here’s when
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.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
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.