News
SpaceX’s West Coast drone ship begins Panama Canal transit on journey to Florida (or Texas)
After traveling more than 3500 miles (5600 km), SpaceX autonomous spaceport drone ship (ASDS) Just Read The Instructions (JRTI) began its eastbound transit of the Panama Canal on August 18th, placing the vessel roughly two-thirds of the way to its unknown destination.
As previously discussed on Teslarati, JRTI’s move came as a bit of a surprise and it’s still anyone’s bet if the SpaceX recovery vessel heads for Texas or Florida immediately after exiting the Panama Canal. Nevertheless, JRTI’s presence at either (or, more likely, both) possible destinations arguably centers around the imminent demands of a planned ramp of SpaceX’s Starlink satellite constellation launch cadence, as well as an equally imminent need for recovery assets to support the first suborbital Starship test flights.
On July 31st, JRTI departed Port of Los Angeles – its home for the last four years – under tow behind tugboat Alice C. The duo arrived at the Canal on August 15th and, after a several-day wait in a large passage queue, the drone ship and its paired tugboat are finally on their way through the canal, although traffic still remains high and another day (or several) of waiting is likely in order.
After successfully making it through the first half of the transit, JRTI and Alice C are currently waiting in line while westbound traffic is routed through. That wait will likely last hours, not days, (hopefully) allowing JRTI to exit the canal on Tuesday or Wednesday, leaving drone ship free to head towards its final destination.
JRTI has two possible destinations: Port of Brownsville, Texas or Port Canaveral, Florida. Both options are roughly 1800 mi (3000 km) from the Panama Canal’s western mouth and, extrapolating from the first major leg of the journey, should take Alice C around 8 days to tow JRTI across the finish line. Barring mishaps, the drone ship should thus be able to arrive at its new home sometime in the final week of August – roughly August 27th to the 31st.
To the East, to the Gulf
As previously discussed on Teslarati, there are good cases to make for both potential drone ship destinations. On the East Coast, SpaceX’s plans to ramp up its internal Starlink launch cadence could require multiple drone ship to prevent those ambitions from seriously impacting the company’s commercial launch manifest. The readiness of one or two of the payloads is uncertain, but SpaceX has anywhere from seven to nine Falcon 9 launches scheduled in Q4 2019, requiring a cadence significantly higher than SpaceX’s activity in the first half of 2019.
At the same time, extrapolating from SpaceX’s H1 2019 cadence (1.33 launches per month), more than doubling that average cadence to 3 launches per month in the final quarter seems ambitious, at a minimum. SpaceX has achieved six-launch quarters several times in the last few years, likely a reasonable expectation for Q4 2019. In short, this is all to say that SpaceX has made do with one drone ship in the past while hitting similar launch cadences, meaning that the need for JRTI at Port Canaveral is probably not urgent.
On the Gulf Coast, SpaceX has established a Starship development facility in Boca Chica, Texas, just a handful of miles north of the southernmost tip of Texas. A full-scale, low-fidelity prototype known as Starhopper completed its first test flight on July 25th and is likely just days away from a second test flight. Meanwhile, SpaceX Boca Chica is simultaneously assembling what CEO Elon Musk has described as the “Mk1” orbital Starship prototype and is making spectacularly rapid progress.
Musk recently tweeted that SpaceX’s Mk1 Starship and a second parallel build – Starship Mk2 – could be ready for their first (suborbital) flights as early as late-September or October, followed by one of the spacecraft’s first orbital launch attempt an incredibly ambitious “2-3 months after” the first test flight. Per additional statements from Musk in 2018 and 2019, SpaceX plans to subject either or both of its Mk1 and Mk1 Starships to a high-altitude, high-velocity test program before proceeding to orbital launch attempts.
Said extreme testing could easily involve Starship traveling on high suborbital trajectories dozens or even hundreds of miles above Earth’s surface, potentially demanding an ocean-going landing platform far downrange. Given that Starship is in its very early stages of integrated development, any downrange assets (i.e. JRTI) needed for test flights will need to be very flexible, as Starship launch attempts could easily slip days or weeks with little to no notice.
Best of both worlds
Although pitting options against each other is entertaining and has its uses, the fact remains that once drone ship JRTI has passed through the Panama Canal, traveling from, say, Florida to Texas or vice versa is far less arduous a journey than the trip from Port of LA. In other words, moving JRTI between Port of Brownsville and Port Canaveral every few months should be very little trouble, easily allowing the drone ship to service both Gulf and East Coast recovery needs.
Given that SpaceX’s next Falcon 9 launch is believed to be no earlier than late-October, it’s not even out of the question that JRTI will stop in Brownsville for one month or several before heading to Port Canaveral as SpaceX attempts to complete a very busy Q4 2019 launch manifest. Stay tuned…
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
