News
SpaceX Falcon 9 launch and landing imminent as drone ship heads to sea
SpaceX’s next Falcon 9 launch and landing is well into the late stages of preparation, leaving the company approximately 24-48 hours away from its next mission to orbit. To support the surprise ocean landing, a drone ship has already been dispatched and recently departed Port Canaveral.
After a frenetic week of preparation, tugboat Hawk departed with drone ship Of Course I Still Love You (OCISLY) on December 1st, preparing for its second recovery attempt in roughly three weeks and SpaceX’s second drone ship landing after a rare, six-month rocket landing lull. In the days leading up to the anticipated departure, workers could be seen performing a routine procedure often nicknamed a “FOD-walk” in which a given surface is scoured for Foreign Object Debris (FOD). This is most commonly performed on runways (including aircraft carriers) and attempts to mitigate or fully prevent damage from rocks and other small debris.
In the case of Falcon booster landings, the rocket’s Merlin 1D engine exhaust velocity is just shy of 3000 m/s (6700 mph), meaning that a tiny rock or leftover rocket piece could almost immediately become a high-subsonic or supersonic projectile in the seconds before touchdown. The drone ship itself is most at risk, but those theoretical projectiles could potentially bank off the platform’s exhaust shields and hit the booster itself, causing far costlier damage.
And hence the FOD-walk pictured above. Once complete, OCISLY was cleared for departure and has since made it about 75% of the way to its planned landing zone coordinates. SpaceX is currently scheduled to launch Cargo Dragon resupply mission CRS-19 on a Falcon 9 rocket no earlier than 12:51 pm EST (16:51 UTC) on December 4th, although a specific weather condition may delay the instantaneous window by 24 hours. Hawk and OCISLY should thus arrive on station one or two days before launch.
As it turns out, this Falcon 9 landing is a bit of mystery: it’s unclear why exactly SpaceX has decided to land the booster at sea instead of the usual Landing Zone recoveries that have followed most recent Cargo Dragon launches. Typically, the low insertion orbit (~200 km x ~390 km) and relatively low mass of Cargo Dragon (less than 10 tons or 22,000 lb) means that Falcon 9 has (literally) tons of propellant left over, giving it the margins needed to flip around, cancel out a huge amount of horizontal velocity, and boost 100+ km (62+ mi) back to shore.
Instead, new Falcon 9 booster B1058 is scheduled to land aboard drone ship OCISLY some 350 km (220 mi) downrange, an unusual distance. For reference, SpaceX’s May 2019 CRS-17 mission is the only time Falcon 9 has landed at sea after a CRS launch since CRS-8, the rocket’s first successful drone ship recovery. That scenario was forced because LZ-1/2 had coincidently been showered in Crew Dragon debris after C201 exploded during testing. Even then, OCISLY was stationed just 20 or so kilometers offshore, meaning that Falcon 9 B1056 still performed a routine Return To Launch Site (RTLS) landing in spirit.
In short, the ~350-km-downrange landing plan suggests that this Cargo Dragon launch may have a much smaller propellant margin than essentially every similar mission preceding it. This could be explained in a few ways. Maybe after Falcon 9 B1050’s surprise landing failure, SpaceX decided that all new Falcon 9 boosters will attempt drone ship landings after their first flight, minimizing the risk to Cape Canaveral in the event of a CRS-16 repeat. Another possibility, Crew Dragon capsule C205 – scheduled to support the spacecraft’s In-Flight Abort (IFA) test late this month or early next – may still be close to the Cape’s Landing Zones, another reason to avoid even the slightest chance of a catastrophic Falcon landing failure.
Finally, it’s also possible that CRS-19 will follow in the footsteps of CRS-18, which sported a prototype Falcon 9 upper stage designed to push the enveloped of its orbital longevity. Falcon 9 B1056 still managed to land at LZ-1 after CRS-18, but a more ambitious follow-on test could potentially require much more propellant, accounting for the drone ship’s position further downrange. With any luck, we’ll find out more later today during SpaceX, NASA, and the US Air Force’s routine pre-launch press conference – 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
