News
SpaceX’s drone ship fleet spied prepping for future rocket recoveries
Just shy of three weeks since SpaceX’s last launch and the better part of half a year since the last successful ocean recovery, both of the company’s drone ships have been spotted in recent weeks being refurbished, refitted, and prepared for a return to the ocean.
The unusual drought of drone ship landings was nearly brought to an end in early March, but that recovery attempt – following the successful launch of Hispasat 30W-6 – was precluded by extreme weather in the landing zone, forcing booster 1044 to soft-land in the Atlantic with a swan call of landing legs and titanium grid fins. Several weeks before 1044’s demise, the inaugural launch of Falcon Heavy also saw the first failed booster recovery attempt since June 2016, ending a successful streak of 17 flawless Falcon 9 recoveries – though both side boosters did manage a spectacular, synchronized landing at LZs 1 and 2.
Before the Falcon Heavy attempt, East coast drone ship Of Course I Still Love You (OCISLY) successfully recovered a Falcon 9 booster for the last time in late October 2017, a handful of weeks after the successful recovery of SES-11 – the source of a small fire that famously destroyed SpaceX’s robotic stage securer, nicknamed Roomba or Octagrabber. Over the several months, since it was damaged, Octagrabber has gradually undergone refurbishment at SpaceX’s Port Canaveral berth, most recently appearing back on OCISLY for post-refurb testing.
With the introduction of Falcon 9 Block 5 presumably a month or less away, the days of expending once flight-proven boosters will almost certainly be over, aside from missions that truly require the booster’s full performance. As discussed yesterday, regardless of whether Block 5 is truly ready for the limelight, SpaceX is no more than two months away from effectively running out of all older boosters: the once-flown B1045 (TESS) will likely be the only flight-worthy heritage booster remaining by early May. In other words, every single SpaceX launch in the second half of 2018 is all but guaranteed to attempt recovery, either by land or sea.
- OCISLY as seen by Tom Cross on March 5, readying for a busy future of rocket recoveries. (Tom Cross)
- Roomba was spied aboard OCISLY for the first time in months earlier this month. (Instagram /u/grimlok77)
OCISLY is effectively prepared to support these upcoming recovery attempts, and its Octagrabber may be as well. However, OCISLY was reportedly damaged by Falcon Heavy’s center core, despite the fact that it quite visibly missed the drone ship. Presumably, the forlorn booster acted as a sort of depth charge, thus damaging beyond repair the drone ship’s sensitive maneuvering and station-keeping thrusters. Before Falcon Heavy, it’s likely that the same fire that burned Octagrabber also damaged the hydraulic systems of one or several of OCISLY’s thrusters. These conclusions are supported by the fact that SpaceX’s West coast drone ship, Just Read The Instructions (JRTI), has visibly been stripped of its functional thrusters, presumably used to keep OCISLY operational in anticipation of Falcon Heavy and later Hispasat 30W-6.
Mr Steven, SpaceX’s only current fairing recovery vessel, has also been spotted conducting some sort of sea trials just off the shore of Port of San Pedro and LA, presumably honing recovery operations and giving its pilots time to practice catching fairings. Following the launch of PAZ and SpaceX’s own prototype Starlink satellites, the company managed its first-ever intact fairing recovery, although it missed Mr Steven’s net by a few hundred feet. As stated by Musk, it should be relatively easy to go from missing by a few hundred feet to successfully catching the fairing, and it’s likely that the imminent launch of Iridium-5 (7:19 am PDT, March 29) will attempt to close that gap and actually catch a fairing halve. On the other hand, the booster – flight-proven during the October 2017 launch of Iridium-3 – will likely soft-land in the Pacific Ocean because JRTI is currently unable to support ocean recoveries, lacking two of its four thrusters.
- Teslarati photographer Pauline Acalin took a trip down to Port of San Pedro to check up on JRTI, March 25. (Pauline Acalin)
- Note one of JRTI’s thrusters here, quite clearly not installed. A second one sits just out of sight on the right. (Pauline Acalin)
- SpaceX’s West coast drone ship Just Read The Instructions getting some much needed fresh paint. (Instagram, anonymous)
Follow us for live updates, behind-the-scenes sneak peeks, and a sea of beautiful photos from our East and West coast photographers.
Teslarati – Instagram – Twitter
Tom Cross – Twitter
Pauline Acalin – Twitter
Eric Ralph – Twitter
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.




