News
SpaceX Falcon Heavy rocket passes static fire test three years in the making
After knocking out some figurative cobwebs, SpaceX has test-fired a Falcon Heavy rocket for the first time since June 2019.
Shortly before the static fire, NASASpaceflight’s Thomas Burghardt reported that Falcon Heavy’s first launch in 40 months – a mission for the US Space Force known as USSF-44 – had slipped from October 28th and October 31st to no earlier than (NET) 9:40 am EDT (13:40 UTC), Tuesday, November 1st. USSF-44 will be Falcon Heavy’s fourth launch since February 2018.
During its 10-second October 27th static fire, Falcon Heavy – the most capable rocket currently operational – appeared to ignite all 27 of its first stage’s Merlin 1D engines, likely producing up to 2350 tons (5.18 million lbf) of thrust. Only three liquid-powered rockets (N1, Saturn V, & Energia) and one rocket augmented by solid rocket boosters (the Space Shuttle) have produced more thrust at sea level, and the most recently active of those four vehicles (NASA’s Space Shuttle) was permanently retired in 2011.
NASA’s Space Launch System (SLS) rocket will retake the crown when it (hopefully) debuts later this year, but Falcon Heavy will remain the most powerful commercially-available rocket until SpaceX’s own Starship debuts. After Starship debuts later this year or early next, Falcon Heavy will continue on as the second most powerful commercial rocket for the indefinite future.
After more than three years of downtime, SpaceX unsurprisingly appeared to run into minor issues while preparing Falcon Heavy for a full wet dress rehearsal and static fire. SpaceX rolled the rocket – sans payload fairing – out to the launch pad late on October 25th, at which point the launch target had already slipped to October 31st. Falcon Heavy then sat horizontally for about 30 hours before SpaceX raised it vertical and fully attached the rocket and transporter/erector to the pad’s ground systems.
Another 12 hours of work later, SpaceX was ready to begin static fire test operations, and Falcon Heavy fired up at 8 pm EDT on October 27th, 50 hours after it rolled out. During Falcon 9’s most recent satellite launch out of Pad 39A, the rocket lifted off about 30 hours after rollout. While preparing for Falcon Heavy Block 5’s first launch (Flight 2 overall) in April 2019, the rocket went vertical 12 hours after rollout – 18 hours faster than Flight 4. Ahead of Flight 3 in June 2019, Falcon Heavy completed a static fire test 25 hours after rolling out – 25 hours faster than Flight 4.
Before it can launch, Falcon Heavy will have to return to LC-39A’s hangar to have its fairing (containing two classified USSF-44 satellites) installed and then return to the pad, repeating the rollout process. Falcon Heavy Flight 3 holds the record (5d 4h) for the shortest gap between a static fire and launch. Falcon Heavy’s updated launch target is 4 days and 14 hours after its static fire, meaning that SpaceX will have to break that record to launch USSF-44 as planned.
Update: The USSF-44 payload fairing – satellites safely encapsulated inside it – headed to Pad 39A less than four hours after Falcon Heavy Flight 4’s static fire.
Regardless, with a successful static fire under its belt, Falcon Heavy’s fourth launch is now all but guaranteed to occur within the next 5-10 days. The rocket’s fifth launch – carrying ViaSat’s first ViaSat-3 communications satellite – could follow as early as December 2022, and another four Falcon Heavy launches are currently scheduled between January and August 2023.
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
