News
SpaceX Falcon 9 booster fires up ahead of NASA launch and surprise drone ship landing
SpaceX has successfully fired up a new rocket ahead of what is now believed to be a surprise Falcon 9 booster drone ship landing, to follow shortly after the company’s upcoming CRS-19 Cargo Dragon resupply mission for NASA.
Around 5:30 pm EST (22:30 UTC) on November 26th, a Falcon 9 rocket – featuring a rare unflown booster – successfully performed a wet dress rehearsal (WDR) and ignited all nine of its first age Merlin 1D engines, verifying the rocket’s health and perfectly simulating a launch right up to the point of liftoff. With that routine static fire complete, SpaceX now has a luxurious seven days to bring the rocket horizontal, roll it back into LC-40’s integration and processing hangar, install Cargo Dragon atop the second stage, and roll the fully-integrated rocket back out to the launch mount.
According to NASASpaceflight.com reporter Michael Baylor, SpaceX decided to swap boosters, moving Falcon 9 B1056.3 to a commercial satellite mission and assigning B1059.1 to Cargo Dragon’s NASA CRS-19 resupply mission. Prior to visual confirmation of this shift, NASA and SpaceX had indicated interest in flying Block 5 booster B1056 for a third time after it successfully completed its second launch and landing for NASA on July 25th, 2019. That would have been the first time NASA certified a twice-flown SpaceX booster to launch a NASA mission, a critical step along the path to making booster reuse routine – even for SpaceX’s highest-profile customers.
Instead, B1056.3 is now scheduled to launch the Kacific-1/JCSAT-18 commsat no earlier than December 15th, while CRS-19 is scheduled to lift off at 12:51 pm EST (17:51 UTC) on December 4th. As with most other missions designed to quickly rendezvous with the International Space Station (ISS), CRS-19’s launch window is effectively instantaneous, meaning that any issue during the countdown or day-of preparations will force a ~24-hour recycle.
Aside from it being unclear why exactly NASA, SpaceX, or both parties decided against launching B1056 for the third time on CRS-19, the mission features another minor mystery. Instead of using the performance left over from such a light launch to low Earth orbit (LEO) to return the booster to launch site (RTLS) and land at SpaceX’s LZ-1/2 landing pads, it appears that Falcon 9 B1059 will attempt to land aboard drone ship Of Course I Still Love You (OCISLY).
Since April 2016, SpaceX has only once intentionally recovered Falcon 9 by sea after a Cargo Dragon launch. That particularly recovery occurred during CRS-17 in May 2019, just a few weeks after Crew Dragon capsule DM-1 catastrophically exploded just prior to an attempted static fire test located adjacent to LZ-1/2. That explosion littered the area with evidence, precluding Falcon 9’s planned LZ-1 recovery in the same way that a police helicopter would likely try to avoid landing directly on top of an active crime scene. In that case, extraordinary attenuating circumstances were required before SpaceX redirected a CRS launch’s booster recovery to a drone ship.
Seemingly lacking similarly extraordinary circumstances, it remains to be seen whether SpaceX or NASA will offer an explanation for the unexpected change in plans. On the plus side, an unexpected Falcon 9 drone ship landing also means an unexpected Port Canaveral return, which should offer increasingly rare views of a once-flown Falcon 9 booster.
Routinely reusable spacecraft
As expected, CRS-19 will become the second orbital launch of a twice-flown Cargo Dragon capsule, flexing SpaceX’s reusability muscles in the much less forgiving realm of orbital spacecraft. On July 25th, CRS-18 became the first such mission to reuse a twice-flown spacecraft, leaving SpaceX with several additional twice-flown Cargo Dragon capsules as the only plausible options for its remaining three CRS1 missions.
SpaceX says that CRS-19’s Cargo Dragon capsule previously flew CRS-4 (Sept 2014) and CRS-11 (June 2017), identifying it as capsule C106. As it turns out, C106 supported SpaceX’s first Cargo Dragon capsule reuse, making it a fairly historic vehicle – the first commercial orbital spacecraft reused in history. Beginning with CRS-3, Dragon 1 vehicles were designed to support up to three orbital missions each, leaving SpaceX with four possible capsules (C110-C113) capable of supporting CRS-20, Dragon 1’s last planned launch.
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
