News
SpaceX’s next Falcon Heavy launch and landing could be more than a year away
According to comments made by US Air Force officials prior to SpaceX’s latest Falcon Heavy launch, the payload assigned to the military’s first fully-certified Falcon Heavy has been swapped with another, although the mission’s late-2020 launch target remains relatively unchanged.
This new information comes on the heels of the June 25th launch of Space Test Program 2 (STP-2), SpaceX’s third successful Falcon Heavy mission and a huge milestone for the rocket’s future as a competitive option for US military launches. Perhaps most importantly, it confirms – barring a surprise launch contract or internal Starlink mission – that Falcon Heavy’s next (and fourth) launch is unlikely to occur until late next year, a gap of at least 15-17 months.
Announced roughly four months after Falcon Heavy’s inaugural February 2018 launch debut, the USAF contracted with SpaceX to launch the ~6350 kg (14,000 lb) AFSPC-52 satellite no earlier than (NET) September 2020. In February 2019, Department of Defense contract announcements revealed that SpaceX had been awarded three military launch contracts, two for the National Reconnaissance Office (NROL-85 & NROL-87) and one for the USAF (AFSPC-44), all tentatively scheduled to launch in 2021.
First reported by Spaceflight Now, Col. Robert Bongiovi – director of the launch enterprise systems directorate at the Air Force’s Space and Missile Systems Center (AFSMC) – recently indicated that AFSPC-44 – not AFSPC-52 – is now scheduled to be the US military’s first post-certification Falcon Heavy launch. 52 and 44 have essentially swapped spots, with AFSPC-44 moving forward to NET Q4 (fall) 2020 while AFSPC-52 has been delayed to NET Q2 (spring) 2021.
The trouble with launch gaps
Although Bongiovi did not explicitly state that AFSPC-44 will be SpaceX’s next Falcon Heavy launch, there are no publicly-disclosed missions set to launch on the rocket in the interim. That could theoretically change, especially if SpaceX has plans to launch the massive rocket in support of an internal Starlink mission or even something more exotic, but the loss of both Block 5 center core B1055 and B1057 means that the company will have to build an entirely new center core.
SpaceX’s Falcon Heavy lead times are far superior to competitor ULA’s Delta IV Heavy production line, but the process of manufacturing new center cores is still quite lengthy. Critically, Falcon Heavy Block 5 center cores require strengthened octawebs, custom interstages, and propellant tanks that are significantly thicker than those used on Falcon 9. For all intents and purposes, a center core is a totally different rocket relative to a Falcon 9 booster, the latter being SpaceX’s primary focus at the company’s assembly line-style Hawthorne factory. It’s theoretically possible for a dedicated Falcon Heavy center core build to be expedited or leapfrogged forward in the production queue, but most long-lead Falcon 9 booster hardware physically cannot be redirected to speed up center core production.
Unless SpaceX was already in the process of building a new center core prior B1057’s unsuccessful landing attempt, it’s safe to assume that the next custom Falcon Heavy booster is unlikely to be completed until early 2020, if not later. In theory, this means that Falcon Heavy could be dormant for no less than 16 months between STP-2 and its next launch. Traditionally, that sort of lengthy gap between launches has been frowned upon by NASA, ULA, and oversight groups like GAO. If a given rocket doesn’t launch for a year or more, it can potentially pose a risk to reliability and raise costs as its production and launch teams have no satisfactory way to fully preserve their technical expertise.
This can be compared to attempting to become an expert at a musical instrument while only having access to said instrument one or two months a year, essentially impossible. In fact, at one point, NASA hoped to require its Space Launch System (SLS) rocket be able to launch no less than once per year, partly motivated by a desire to mitigate some of the deterioration that can follow extremely low launch cadences. Years later, financial constraints and years upon years of delays and budget overruns have made such a cadence effectively impossible for SLS/Orion, but the fact remains that launching a rocket just once every 18-24 months is likely to inflate both costs and risks.
Thankfully, SpaceX’s Falcon Heavy could scarcely be more different than NASA’s SLS and the retired Space Shuttle it derives most of its hardware from. Even if all things are held equal and not flying a Falcon Heavy center core for 16+ months increases risk and cost, center cores are still heavily derived from Falcon 9 booster technology, including plumbing, avionics, attitude control thrusters, Merlin 1D engines, landing legs, and launch facilities.
Furthermore, the center core is just one of five distinct assemblies that make up a given Falcon Heavy. Both side boosters are effectively Falcon 9 Block 5 boosters with nose cones instead of interstages and slight modifications to support booster attachment hardware, while the upper stage and payload fairing are the same for all Falcon launches. In other words, SpaceX’s workforce will continue to build, launch, land, and reuse dozens of Falcon 9 boosters – as well as upper stages payload fairings – between now and Falcon Heavy Flight 4, even if it’s NET Q4 2020. In a worst-case scenario, SpaceX production and launch staff will be unfamiliar and inexperienced with maybe 20% of Falcon Heavy – at least in a very rough sense. Even then, much of that unfamiliarity may still be tempered by the fact that Falcon Heavy center cores share a large amount of commonality with the Falcon 9 first stages SpaceX’s workforce will remain deeply familiar with.
Indeed, Falcon Heavy’s second launch has already demonstrated this to some extent, occurring without issue more than 14 months after the rocket’s inaugural launch. It seems that the only real loss incurred by a ~16-month delay between Flights 3 and 4 will be having to wait another year (or more) to witness Falcon Heavy’s next 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
