News
SpaceX adds mystery Falcon 9 launch to packed October manifest
SpaceX FCC paperwork has revealed the addition of an unidentified Falcon 9 launch to the company’s packed October manifest, ranging from several Starlink missions to Crew Dragon’s first operational astronaut launch.
Under the US Federal Communications Commission (FCC), companies must submit an application for permission to communicate with their rocket for every single launch. While a major annoyance for those companies and an undeniably clunky process, those applications for “special temporary authority” (STAs) to communicate are one of the only ways members of the public can independently monitor and forecast US launch activities. For SpaceX, the company typically applies for multiple STAs for every single launch, including specific applications for booster launches, landings, and preflight ground tests.
The separate STAs can be connected with a “Mission Number” SpaceX associates each one with, while coordinates included to designate the area of landing communications (i.e. the drone ship recovery zone) often reveals a mission’s trajectory. Combined, STAs can often be used to identify the exact mission (i.e. a Starlink launch, Crew Dragon, etc.). STAs for SpaceX’s upcoming Crew Dragon Crew-1 and Cargo Dragon CRS-21 missions, as well as several Starlink launches, have already been identified.

Thanks to bad weather and a flurry of ULA delays, SpaceX’s October manifest is currently packed with three Starlink missions, a GPS III satellite launch for the US military, and Crew Dragon’s first operational astronaut mission to the International Space Station (ISS). Barring a miracle, ULA’s latest Delta IV Heavy launch delay has pushed SpaceX’s GPS III SV04 mission to October 1st.

Starlink-12 – SpaceX’s 11th Starlink mission this year and 13th overall – is tentatively set to follow GPS III SV04 at 9:17 am EDT (13:17 UTC) on October 1st. Starlink-13 and Starlink-14 are then scheduled to launch no earlier than mid-to-late-October. Finally, SpaceX and NASA are in the final stages of preparing for Crew Dragon’s Crew-1 mission – the spacecraft’s first operational delivery of astronauts to the ISS – as soon as October 31st (Halloween).
A new Sirius XM radio satellite (SXM-7) could launch on a Falcon 9 rocket on November 6th. On the West Coast, SpaceX’s first California mission since June 2019 could launch on November 10th. SpaceX and NASA are also targeting the launch debut of an upgraded Cargo Dragon 2 resupply spacecraft on a mission known as CRS-21, scheduled to lift off NET November 15th. Last but assuredly not least, Turkey’s Turksat 5A communications satellite could launch as early as November 31st. No Starlink missions are currently scheduled in November but it’s safe to assume that there will be at least one or two. Altogether, SpaceX already has five launches scheduled in October and four set for November. While undeniably prolific, SpaceX has never launched more than three times in one month.

Now, on top of that swath of firm launches, mysterious “SpaceX Mission 1512” has joined the fray. Based on the FCC STA request, the mission is scheduled to launch no earlier than (NET) October 3rd (with a six-month window) and will include a return-to-launch-site (RTLS) Falcon 9 booster landing. The RTLS landing in particular substantially constrains the mission and means – right off the bat – that it can’t be for Starlink, while also ruling out Cargo Dragon CRS-21 (an RTLS landing STA already exists) and Crew Dragon Crew-1 (drone ship landing). Simply put, an RTLS rules out every other launch on SpaceX’s 2020 manifest beyond a rideshare mission tentatively scheduled in December, and SpaceX almost never files for STAs months in advance.
That leaves some kind of unannounced, mystery mission. Only once in SpaceX’s history has the company conducted an unannounced launch – unsurprisingly for some unknown branch of the US military or espionage apparatus. Known as Zuma and still shrouded in secrecy, it followed an almost identical pattern, revealed only through FCC launch and landing communications requests and rumors in 2017 before a January 2018 launch. Although Northrop Grumman was thrown under the bus for a failed payload adapter that may or may not have doomed the satellite, no federal agency has taken credit for the mission – unspeakably odd as far as spaceflight goes.
At the time, unofficial rumors published on Reddit implied that Zuma would only be the first of many similar missions. The claimed failure of a spring-like deployment mechanism and loss of spacecraft – believed to be worth one or several billion dollars – just hours after launch would have unsurprisingly thrown a wrench into those gears. Now, almost three years later and in the midst of an exceptionally busy period of several important launches, could SpaceX be preparing for Zuma-2?
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.