News
SpaceX Falcon 9 doubleheader still on track after fiery ULA launch abort
As previously reported by Teslarati, SpaceX announced intentions to launch two Falcon 9 missions from two Florida launchpads on Sunday, August 30th. However, the ambitious goal was left in limbo.
The record-breaking doubleheader was believed to hinge upon the Saturday morning launch of a United Launch Alliance (ULA) Delta IV Heavy rocket with a classified spy satellite. However, that is apparently no longer the case.
Instead of launching on time, ULA’s infrequently-flown heavy-lift rocket was hit by 72 hours of delays to rectify minor pad hardware bugs. Around 2 am EDT (UTC-4) on August 29th, Delta IV Heavy made it just seconds away from liftoff before the rocket’s autonomous flight computer detected an anomaly with pad hardware and aborted the launch. As a result, the three cores’ three Aerojet Rocketdyne RS-68A engines were forced to shut down after ignition – an uncommon Delta IV launch abort scenario that has historically required at least a week of work to recycle for another launch attempt.

ULA ultimately determined that it was not possible to recycle the countdown for another attempt although enough time remained in the launch window to do so. The launch vehicle was safed and a scrub was announced.
In a statement provided by ULA confirmed that the early shutdown was “due to an unexpected condition during the terminal count at approximately three seconds before liftoff.” ULA also confirmed that “the required recycle time prior to the next launch attempt is seven days minimum.”
ULA has to fly before SpaceX, right?
With a minimum of seven days required to recycle the ULA Delta IV Heavy for another launch attempt, it was unclear what that meant for the fate of the SpaceX SAOCOM-1B mission.

It was previously understood that in order for SpaceX to launch the SAOCOM-1B mission from nearby Space Launch Complex-40 (SLC-40), the ULA Delta IV Heavy would have to successfully launch first. The southern polar launch trajectory of the SAOCOM-1B’s mission is one that hasn’t been flown from Cape Canaveral, FL in nearly six decades. This particular flightpath includes launch hazard zones that inch ever so close to the launchpad of the Delta IV Heavy, which is currently still on its launchpad stacked with a classified payload for the U.S. government.
It was assumed that the Falcon 9 would suffer the same minimum delay of seven days, if not longer. However, on Saturday afternoon, August 29 a SpaceX media representative confirmed that the company was still targeting the historic double header launches on Sunday, August 30.
Double the launches, double the recoveries
If SpaceX can pull it off, Sunday is set to be a stellar day for Falcon 9 launches and landings. The SAOCOM-1B mission will feature a Return To Launch Site (RTLS) landing attempt of the expended Falcon 9 booster while the Starlink Falcon 9 booster is expected to land aboard the autonomous droneship “Of Course I Still Love You” currently stationed off the coast of South Carolina.
In an unusual move, SpaceX split up the fairing catching vessels. Initially, both vessels left Port Canaveral and headed south to a catch zone located between The Bahamas and Cuba in an attempt to catch both fairing halves of the SAOCOM-1B mission. Then, GO Ms.Tree did an about-turn and met up with the booster recovery vessels off the coast of South Carolina.
At the time of publishing, the two Sunday Falcon 9 launches are expected to occur just nine hours apart. The Starlink V1.0-L11 mission is slated to occur at 10:12am ET (1412 UTC) from Launch Complex 39-A at Kennedy Space Center while the SAOCOM-1B mission is set to launch at 7:18pm ET (2318 UTC) from SLC-40 at Cape Canaveral Air Force Station. As usual, SpaceX will host official launch webcasts live, typically beginning around 15 minutes before liftoff.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
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.
News
Tesla Cybercab launch catches NHTSA’s attention who wants to know more
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.

Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.