SpaceX has completed its 60th operational Starlink satellite launch after a rare string of scrubs.
Flying for the 6th time just 66 days after its 5th launch, Falcon 9 booster B1067 lifted off with 54 Starlink satellites on SpaceX’s Starlink 4-34 mission at 8:18 pm EDT, Sunday, September 18th. Five days prior, after unknown issues triggered a delay from a planned September 11th launch attempt, SpaceX attempted to launch the mission for the first time on September 13th.
About an hour before liftoff, lightning conditions forced the company to call off the attempt. On September 14th, also about an hour before liftoff, weather forced SpaceX to call off the second attempt. On September 15th, the third attempt was aborted (by weather) just 29 seconds before liftoff, followed by a fourth weather-related scrub about a minute before liftoff on September 16th. Only after a fifth attempt on September 17th was preempted by a delay to September 18th did SpaceX finally find a gap between Florida’s summer weather.
With dozens of Starlink launches beginning to blur together and SpaceX’s Falcon 9 continuing a relentless and potentially record-breaking streak of successes at a pace that could soon make it the fastest launching rocket in history, it’s hard to be surprised that Starlink 4-34 was completed without issue. Falcon 9 B1067 ascended under power for about three minutes, sent the rest of the rocket on the way to orbit, coasted into space, and returned to Earth with SpaceX’s 68th consecutively successful booster landing.
Falcon 9’s underappreciated upper stage continued into an orbit around 300 kilometers (~190 mi) up, spun itself up end over end, and deployed a 16.7-ton (~36,900 lb) stack of 54 Starlink V1.5 satellites all at once. Following the quick deployment, the rocket’s pair of reusable fairing halves were likely still 10 or 20 minutes away from touching down on the Atlantic Ocean under their GPS-guided parafoils, where they will eventually be scooped out of the water for future flights.
Starlink 4-34 was SpaceX’s 42nd launch of 2022, maintaining an average of one launch every 6.2 days since the year began. It leaves more than 3000 working Starlink satellites in Earth orbit, likely meaning that a majority of all working satellites are owned and operated by SpaceX less than three full years after the company began operational launches.
Up next, Next Spaceflight and Spaceflight Now report that SpaceX has two more Starlink launches (4-35 and 4-36) tentatively scheduled before the end of September. As of September 15th, both reported that those missions were working towards launches on September 19th and September 26th – nothing unusual for SpaceX in 2022.
What was unusual, however, was both unofficial manifests’ agreement that SpaceX intended to use the same pad – Cape Canaveral Space Force Station’s LC-40 – to launch Starlink 4-34, 4-35, and 4-36. Even assuming that those schedules were predicated upon Starlink 4-34 launching on September 13th, before all of its weather delays, SpaceX would have had to break LC-40’s 7.7-day turnaround record by around ~25% and complete a second launch just seven days after that.
Starlink 4-34’s delays have thrown that plan into question, but the fact that SpaceX thought it was possible in the first place suggests that the company has plans to squeeze even more performance out of LC-40 – already its most important pad from the perspective of launch cadence. Launch photographer Ben Cooper now reports that Starlink 4-36 could launch in late September or October. If it slips into October, SpaceX has a rapid-fire pair of customer satellite launches scheduled on October 5th and 13th that will probably take precedent over any internal Starlink mission.
With only 16 days left before LC-40’s next commercial launch and NASA’s Crew-5 launch taking over SpaceX’s other East Coast pad until October 3rd, SpaceX would have to launch Starlink 4-35 and 4-36 just four or five days apart (and one just 4-5 days after Starlink 4-34) to avoid delaying one of the Starlink missions well into October, avoid unnecessarily delaying commercial launches for paying customers, and ensure that those customers don’t have abruptly agree to be commercial guinea pigs for extra quick LC-40 turnarounds.
Starlink 4-35 is now tentatively scheduled for September 23rd, making a Starlink 4-36 delay more likely but not fully ruling out a launch attempt before the end of the month.
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
