News
SpaceX Starlink launch suffers third weather scrub, next attempt Tuesday
Update: Multiple weather constraint violations forced SpaceX to scrub today’s Starlink-12 launch attempt less than half an hour before liftoff, marking the mission’s third weather-related scrub and fourth abort overall since mid-September. As of October 4th, the US Air Force 45th Space Wing predicted a 40% chance of weather violation.
SpaceX’s fifth Starlink-12 launch attempt is scheduled no earlier than 7:29 am EDT (11:29 UTC) on Tuesday, October 6th. The mission-specific T-1 weather forecast predicts a 70% chance of favorable conditions.
On the heels of a rare last-second Falcon 9 launch abort, SpaceX is closing in on its third attempt to launch the 12th batch of operational Starlink satellites.
Scheduled to lift off from Kennedy Space Center (KSC) Launch Complex 39A (Pad 39A) no earlier than (NET) 7:51 am EDT (11:51 UTC) on Monday, October 5th, Starlink-12 was originally scheduled to launch in mid-September. Bad weather at the Atlantic Ocean landing zone caused a ten-day delay from September 17th to the 27th, followed by a pad weather delay on the 28th.
After a ULA Delta IV Heavy mission with range priority was scrubbed for the seventh time on September 30th, SpaceX tried to launch Starlink-12 again but suffered an abort – later blamed on a pad sensor – seven seconds before liftoff. Finally, a new Falcon 9 launch with an upgraded GPS III satellite aboard was aborted just two seconds before liftoff on October 2nd. Moved from NET October 3rd to the 5th just prior to GPS III SV04’s separate launch delay, Starlink-12 is now up next.
Interrupting what has otherwise been a much-improved level of launch readiness and schedule reliability for Falcon 9 and Falcon Heavy’s Block 5 upgrade, this recent string of delays – while mostly the result of weather and ULA’s own NROL-44 launch delays – has even become a concern for CEO Elon Musk. Currently focused on building out SpaceX’s new Starship factory and pushing towards the rocket’s first high-altitude and orbital test flights in Boca Chica, Texas, Musk stated that he would be flying to Cape Canaveral “to review hardware in person” on the week of October 5th.
Musk also says that SpaceX is “doing a broad review of launch site, propulsion, structures, avionics, range, & regulatory constraints” to determine if an apparent goal of “48 launches” in 2021 is feasible.
To be fair to SpaceX, most of the plague of delays suffered by the company in the last month has been caused by a mixture of weather and the range’s preferential treatment of ULA’s “national security” NROL-44 launch. Additionally, of an impressive seven ULA NROL-44 launch attempts between August 26th and September 30th, just a single one was caused by weather – the remaining six a result of a wide variety of technical software and hardware bugs. SpaceX’s Starlink-12 and GPS III SV04 missions have only suffered one technical launch abort each on September 30th and October 2nd.
In other words, short of upgrading Falcon rockets to launch and land in worse weather conditions, most of SpaceX’s delays have been largely out of the company’s control, while ULA’s NROL-44 struggles demonstrate just how much worse things could be. According to an unofficial analysis of 44 Falcon Block 5 launches since May 2018, only four technical launch aborts have been triggered by a booster fault. Pad-caused aborts have been roughly as common, meaning that 1 in roughly 6 to 8 SpaceX launches suffers some kind of abort shortly before liftoff, on average.
Altogether, Falcon Block 5 rockets have been relatively dependable for on-time, on-schedule launches even if SpaceX has struggled with more repeated delays than usual in the last few months. To achieve anywhere close to 48 launches annually, however, major improvements will need to be made, likely including upgrades to whatever is responsible for Falcon 9’s weather constraints. As of October 2020, SpaceX has never launched four times in one month (or four times in the same ~30-day period). To launch 48 times in one year, SpaceX will need to average four launches per month. That, of course, in no way accounts for the possibility that 2020-esque summer weather could functionally cut 4-8+ weeks off of Falcon 9’s annual availability.
Regardless, SpaceX will begin live coverage of the third Starlink-12 launch attempt around 7:35 am EDT (11:35 UTC). Tune in to (hopefully) catch the company’s 17th launch this year.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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 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.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
