News
SpaceX completes Falcon 9 test fire, space station supply mission up next
After almost exactly 15 months of dormancy, SpaceX’s Launch Complex 40 (LC-40) came to life with the roar of nine Merlin 1D rocket engines as Falcon 9 1035 conducted its second pre-launch static fire in preparation for the company’s 13th Commercial Resupply Services mission, CRS-13. Previously tasked with the launch of the CRS-11 Cargo Dragon, the booster completed its mission and returned safely to Landing Zone-1 (LZ-1) on June 3 2017. The path towards LC-40’s reactivation has delayed the launch approximately one week, but December 6th’s successful static fire bodes well for the current launch date, 11:46 AM on December 12.
Static fire test of Falcon 9 complete—targeting launch of CRS-13 on December 12 from Pad 40, followed by launch of Zuma from Pad 40 in early January.
— SpaceX (@SpaceX) December 6, 2017
On September 6 2016, LC-40 was effectively destroyed over the course of the Amos-6 failure. In months that followed, SpaceX reactivated LC-39A in order to continue chipping away at the company’s launch manifest, but also began the slow process of damage assessment and reconstruction of LC-40. It is safe to assume that almost every single component of the ground support equipment (GSE) was completely replaced, and interviews with Cape Canaveral’s 45th Space Wing commander suggest that SpaceX went further still, transforming the painful situation into an opportunity.
In an exclusive and frank conversation between Brig. Gen. Wayne Monteith and Florida Today’s Emre Kelly, the commander suggested that extensive design changes and additional hardening measures implemented during reconstruction are expected to make LC-40 exceptionally resilient to the rigors of rocket launches. Most tellingly, if perhaps overly optimistic, Monteith estimated that a second vehicle failure on the order of Amos-6 might only take two months to recover from, compared to the 15 months that followed Amos-6. He attributed this claim to GSE that is now largely buried underground, theoretically protecting the vast apparatus of hand-welded piping necessary to fuel the Falcon 9 launch vehicle. The replacement Transporter/Erector/Launcher (TEL) tasked with supporting Falcon 9 during integration and launch also appears to have been modernized, and will likely end up looking quite similar to the monolithic white TEL that resides at LC-39A.
Rocket and spacecraft for CRS-13 are flight-proven. Falcon 9’s first stage previously launched SpaceX’s eleventh resupply mission for @NASA, and Dragon flew to the @Space_Station in support of our sixth cargo resupply mission. pic.twitter.com/RY4F2TrWO2
— SpaceX (@SpaceX) December 6, 2017
With CRS-13’s static fire now complete, the mission is set to become the fifth operational reuse of a flight-proven Falcon 9 booster in 2017, thanks to NASA’s unusually rapid acceptance of the new practice. Further still, if Iridium-4’s December 22 launch date holds, and it does look to be stable for the moment, SpaceX will rather incredibly have conducted five commercial reuses of a Falcon 9 in its first year of operations, meaning that one third of SpaceX’s 2017 missions will have launched aboard flight-proven boosters. Also impressive is SpaceX’s full-stop move towards the reuse of Cargo Dragon capsules, and the company stated over the summer that it was hoping to almost completely redirect Cargo Dragon’s manufacturing facilities towards Dragon 2, also known as Crew Dragon. This was most recently reiterated several months ago and is presumed to still be the company’s goal moving forward, and CRS-12 is believed to have been the last “new” Cargo Dragon that will fly. CRS-13’s Dragon previously flew the CRS-6 mission in April 2015.

Photos shared privately with the author show CRS-13’s Falcon 9 to be covered in a graceful layer of soot from its previous recovery, similar in appearance to Falcon 9 1021 seen above. (Instagram/bambi_mydear)
In a December 6 tweet, SpaceX further confirmed that the deeply secretive Zuma mission, previously delayed from an early-November launch as a result of concerns about fairing defects, has now been moved from LC-39A to LC-40 and is understood to be targeting January 4 2018. This will give SpaceX approximately three weeks after the launch of CRS-13 to verify that everything is functioning nominally in what is essentially a new pad.
Meanwhile, with Zuma now officially moved to 40, LC-39A is completely free from routine operations, meaning that SpaceX’s ground crew can now work at will to ready the pad for the inaugural launch of Falcon Heavy, now aiming for early 2018. Aside from Falcon Heavy, recent FCC filings point to two additional SpaceX launches aiming for January, although slips are probable in light of CRS-13’s minor delays. Regardless, December and January are likely to be thrilling months for followers of the intrepid space exploration outfit.
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.