News
SpaceX “intends” to start launching next-generation Starlink satellites in March
In a new Q&A with the Federal Communications Commission (FCC), SpaceX says it still “plans” and “intends” to begin launching the next generation of Starlink satellites as early as March 2022.
In August 2021, SpaceX filed an application modification request with the FCC in a bid to change its plans for the next-generation “Gen2” Starlink constellation, which still aims to drastically improve and expand upon its first few phases. SpaceX filed the first unmodified Gen2 Starlink application with the FCC in May 2020, requesting permission to launch an unprecedented 30,000 satellites. While the size of the proposed constellation is extraordinary, the FCC has also been exceptionally slow to process it. Only five months after SpaceX submitted its Starlink Gen2 modification request and nineteen months after its original Gen2 application did the FCC finally accept it for filing, which means that it has taken more than a year and a half to merely start the official review process.
That extremely slow pace of work could pose problems for SpaceX’s characteristically ambitious deployment schedule.
In a January 7th, 2022 electronic filing in which SpaceX answered a dozen questions from the FCC, the company didn’t outright criticize the extreme sluggishness with which it was reviewing the application but the sentiment was still just below the surface throughout it. After noting that the FCC continues to ask for far more information from SpaceX than it does from other constellation applications, some of which have recently received licenses in spite of that, SpaceX states that it while it “filed its Gen2 Application more than nineteen months ago…and its Amendment nearly five months ago, they were accepted for filing only two weeks ago.”
It’s perhaps no coincidence that that inexplicable delay only came to an end two weeks after FCC Chairwoman Jessica Rosenworcel – who SpaceX notes recently acknowledged a “need to speed the processing of applications to keep pace with…innovation” – was finally confirmed by the US Senate.
Most importantly, though, SpaceX used its extensive Q&A to reveal that it downselected to one of the two similar constellation configurations proposed in its Gen2 application modification. Specifically, SpaceX says it will continue to develop Configuration 1 only, which is designed and organized to take full advantage of the company’s next-generation Starship launch vehicle. That should simplify the licensing process for many Starlink competitors, which have sought to hobble SpaceX’s application with bizarre requests to the FCC and complained ad nauseam about how much of a burden analyzing two potential constellation layouts was for them. Now they will only have to consider one constellation layout, making SpaceX’s Gen2 constellation a more traditional – if still massive – proposal.
Clearly lacking a great deal of self-awareness about the irony of such of a question, the FCC also saw fit to ask SpaceX for “any updates regarding the expected timing of launches for the Gen2 system.” The timing of Starlink Gen2 launches is obviously unequivocally contingent upon FCC approval more than 19 months after SpaceX first submitted an application for said approval. Nonetheless, SpaceX politely answered the question, revealing that it had “informed Commission staff before filing its Amendment” in August 2021 that it “plans to have Gen2 satellites prepared for launch as soon as March 2022” and “still intends to begin launching [Starlink Gen2 satellites] as early as March 2022.”
Many readers and industry followers interpreted this as an implicit claim that Starship will be ready to launch Starlink Gen2 satellites as early as March 2022 – just another of the company’s detached-from-reality schedule estimates, in other words. That’s simply not the case, though. While SpaceX does confirm that it’s settling on a Starlink Gen2 configuration that will explicitly depend upon Starship for the full 29,988-satellite constellation’s timely, cost-effective deployment, FCC deployment and operations licensing are almost inherently unconcerned with how the constellation gets into space. For example, the original Gen2 application SpaceX modified last August never mentioned which launch vehicle would be responsible for launching tens of thousands of satellites. So long as the rocket is compliant with FCC regulations and has an active permit for any given launch, which is also the responsibility of a different bureau, the FCC is effectively indifferent about which rockets launch a given constellation.
In other words, while SpaceX has made it clear that Starlink Gen2 Configuration 1 is optimized for Starship, SpaceX will be free to launch Gen2 satellites on any rocket it wants if or when the FCC approves the constellation. Assuming that Starlink Gen2 satellites will still be able to fit inside a 5.2m (17 ft) wide payload fairing, that includes Falcon 9. Further, in early 2018, the FCC allowed SpaceX to launch the first two Starlink satellite prototypes before it had issued the company a license for the full constellation, making it clear that with the right paperwork, prospective constellation operators can launch and test prototype satellites before their full constellations are approved.
This is to say that there is nothing theoretically preventing SpaceX from again pursuing permission to launch a few prototype Starlink satellites (this time Gen2) before the FCC has finished reviewing and approving the whole constellation. In fact, anything less would actually be surprising and unusual for the company. When SpaceX says in January 2022 that it plans to have Gen2 satellites ready for launch by March 2022, it’s thus not hard to believe that that’s the truth. Perhaps it will take a month or two longer than planned to complete the prototypes, secure temporary FCC approval, and build and license a new E-band ground station, but it’s still believable that SpaceX will be ready and able to launch the first few Starlink Gen2 satellites on Falcon 9 within the next several months. Above all else, unless SpaceX has explicitly designed Starlink Gen2 satellites such that they no longer fit inside a Falcon fairing, nothing is forcing SpaceX to wait for Starship if Gen2 prototypes are ready to launch before the next-gen rocket.
Given that Starship will have to wait until at least March 2022 for its first orbital test flight after FAA review delays, it’s obviously implausible that the rocket will be ready to launch Starlink prototypes by then. Starship S20 – currently said by CEO Elon Musk to be the first space-bound prototype – doesn’t even have a payload bay. Unless SpaceX wants to wait several more months after that to kick off the flight-testing phase of Starlink Gen2 development, it’s likely that the first few satellites will launch on Falcon 9 – either alongside routine Starlink V1.5 launches or on their own.
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
