News
SpaceX sends Falcon 9’s West Coast drone ship to the Panama Canal in surprise move
In a surprise turn of events, SpaceX has decided to send Just Read The Instructions (JRTI) – one of the company’s two autonomous spaceport drone ships (ASDS) – from Port of Los Angeles to either the Gulf or East Coast.
The likely destination: either Port Canaveral, Florida or Port of Brownsville, Texas. This move comes as the company enters a major lull in launch activities from its West Coast SLC-4 pad, situated in California’s Vandenberg Air Force Base (VAFB). Lacking manifested launches, SpaceX has gone as far as redistributing almost all of its VAFB-based launch team and laying off those that could not move to Texas or Florida. As early as the first half of 2020, this major move east could easily culminate in the end of all West Coast SpaceX fleet activity, aside from a rare fairing retrieval or two.
On June 12th, SpaceX successfully launched what is expected to be its last West Coast mission for at least 6-9 months, while drone ship JRTI was most recently used to recover a VAFB-launched Falcon 9 booster during the January 11th launch of Iridium NEXT-8. Unexpectedly, it appears that Falcon 9 B1049.2’s landing aboard JRTI will be the drone ship’s last West Coast recovery for quite some time.
On August 1st, the approximately 300 foot by 170 foot converted barge departed its well-worn Port of Los Angeles berth behind tugboat “Alice C”. In fact, the drone ship’s departure went unknown for a solid 12-24 hours before a member of the unofficial SpaceX subreddit (/r/SpaceX) discovered paperwork filed with the Panama Canal Authority for an August 15th passage.
Back in January 2019, SpaceX fairing recovery vessel Mr. Steven (now GO Ms. Tree) – in a bit of what now is obvious foreshadowing – began a very similar ~5000 mi (8000 km) journey, traveling from Port of LA to Port Canaveral via the Panama Canal. Mr. Steven, however, is a far faster ship and sustained a solid 15-20 knots (17-22 mph) over the entire voyage, while drone ship JRTI – towed the entire way – will have to suffice with an average speed less than half that.
Where to?
Assuming a day-long canal passage, JRTI’s journey to Port Canaveral or Brownsville would take no less than three weeks (~22 days) from start to finish, indicating a likely arrival at the unknown final destination in the third week of August. The two probable destinations, Texas and Florida, would both arguably make sense.
In Florida, SpaceX drone ship Of Course I Still Love You (OCISLY) is now tasked with handling the vast majority of SpaceX’s non-LZ booster recoveries, including Falcon Heavy center cores. In February 2018, CEO Elon Musk noted that a third drone ship (aside from JRTI & OCISLY) was “under construction” with the intention of allowing SpaceX to conduct Falcon Heavy launches where the center core is expended and both side boosters land at sea.
Perhaps SpaceX analyzed its fairly short West Coast manifest and decided that it would be even faster (and cheaper) to simply send JRTI East. Falcon Heavy’s next (public) launch is scheduled no earlier than late 2020, ruling out that as a primary motivation, but SpaceX is also about to begin operational Starlink launches that will demand an unprecedented cadence. Starlink’s cadence requirements could be so high that a second dedicated drone ship is necessary to prevent SpaceX’s internal manifest from delaying and generally disrupting its customers’ launches, thus explaining JRTI’s move.
At the same time, the spectacular pace of SpaceX’s orbital Starship prototype construction could very well demand the use of a large ocean-based landing platform in the near-term, at least according to Elon Musk’s recent comments on the subject of the first Starship test flights. Per Musk, either or both of SpaceX’s two Starship Mk1 (technically Mk1 & Mk2) prototypes could be ready for their first significant flights as early as September 2019, initially targeting altitudes of at least 20 km (12 mi).
Somewhat coincidentally, Starship’s tripod fin-legs – circa. a September 2018 design update – would actually almost fit inside the span of a Falcon 9 booster’s deployed landing legs (~18m diameter). This is to say that SpaceX’s two drone ships may already be large enough (give or take) to support Starship and Super Heavy booster landings. Given that the SpaceX plans to eventually put one or both of the in-work orbital Starship prototypes through an increasingly intensive series of high-speed, high-altitude (but still suborbital) tests before the first orbital flights, a drone ship may be necessary for the same reasons that not all Falcon 9 boosters can conveniently return to land during recovery.
Regardless of the ultimate purpose of drone ship JRTI’s move, it is undoubtedly a sign that things are about to get even more interesting and exciting in the world of SpaceX.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
