News
SpaceX’s first government Falcon Heavy launch aiming for “early 2019” per USAF
Linked to the rocket and mission through its own LightSail 2 solar sail satellite, The Planetary Society reports that the USAF and SpaceX are now targeting Falcon Heavy’s first launch for a government customer in “early 2019”.
Previously expected to launch around November 30th, just a month from today, it’s clear that SpaceX’s second Falcon Heavy rocket has yet to approach flight readiness, likely marginalized by a more pressing focus on near-term Falcon 9 missions and Crew Dragon’s imminent flight debuts.
LightSail 2 launch pushed to early 2019
An Air Force official says an ‘initial launch capability’ is being reassessed: https://t.co/QYA6NFPP1I pic.twitter.com/RJclLvcbSs
— Planetary Society (@exploreplanets) October 29, 2018
According to Planetary Society, a USAF official provided an update – per the group’s involvement in its STP-2 rideshare launch – stating that its “initial launch capability” was being reassessed, essentially a roundabout way of saying “A new launch date is being determined”. Reasons for the multitude of delays since Falcon Heavy’s successful February 2018 debut are few and far between, with the most likely explanation being some combination of issues with one or several of the ~25 satellites manifested and SpaceX’s ability to build a new Falcon Heavy rocket in time.
However, it’s decidedly ambiguous as to which one of those explanations truly takes precedence, given that SpaceX apparently told the USAF and its customers that it was ready to launch the mission between June and August.
“Officials working on the mission said SpaceX has provided the Air Force and other customers a 60-day window for launch opening on June 13. The Air Force spokesperson confirmed it will be the second Falcon Heavy mission.” – Stephen Clark, SpaceflightNow
Assuming SpaceX’s launch readiness announcement was accurate, the USAF and its customers must have run into some extreme issues while organizing all STP-2 payloads and integrating those satellites onto a custom-built adapter, a task that companies like Spaceflight Industries have shown to often be the long pole of rideshare launches. It’s also possible that SpaceX executives and managers underestimated or undersold the challenge of moving from a Falcon Heavy built solely on old Falcon 9 Block 2 and 3 boosters to an all-Block 5 version of the rocket, featuring a large number of highly-consequential changes like uprated engines and an entirely new approach to assembling each booster’s octaweb.
- Spaceflight’s SSO-A rideshare mission is quite similar to STP-2, albeit with more satellites on the smaller side. (Spaceflight)
- One group of STP-2 passengers, known as DSX, has been awaiting launch for more than eight years. (USAF)
- SpaceX’s second Falcon Heavy launch will either be the USAF’s STP-2, a collection of smaller satellites, or Arabsat 6A, a large communications satellite. (USAF)
Lastly, depending on the nature of the launch contract between them, it’s possible that SpaceX had been planning on reflying Falcon 9 Block 5 boosters as its next Falcon Heavy’s side boosters, a move that would dramatically shorten the lead time required for a new Falcon Heavy to be produced. If the USAF expects or has unconditionally demanded all-new hardware for the launch of STP-2, SpaceX would need at least two (if not three) times the production resources to build and test Falcon Heavy #2, all while paralyzing those resources until well after the rocket’s first flight.
Building three separate Falcon 9/Heavy boosters, acceptance-testing them in Texas, and delivering them to Florida – all under uniquely strict USAF standards – would likely take SpaceX a bare minimum of four months from start to finish. In the guaranteed event that SpaceX had to simultaneously continue regular production, test operations, and preparations for Crew Dragon launches, an all-new Falcon Heavy would likely take more than 6-8 months to make flight-ready while still allowing SpaceX to avoid severe launch delays for its many other customers.
- The communications satellite Arabsat-6A. (Lockheed Martin)
- Falcon Heavy’s side boosters seconds away from near-simultaneous landings at Landing Zones 1 and 2. (SpaceX)
To add additional confusion to the mix, multiple reliable sources have confirmed that STP-2’s actual launch target is closer to March 2019, quite a stretch for “early 2019”. At the same time, Falcon Heavy customer Arabsat has reported that its Arabsat 6A satellite is expected to launch as early as January 2019. Ultimately, clarity can only come from the USAF, Arabsat, or SpaceX itself – for now, we wait.
For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!
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.




