News
SpaceX’s first “next-gen” Starlink satellites are suspiciously familiar
In a strange twist, SpaceX says that its next Starlink mission will launch 54 satellites into low Earth orbit (LEO), implying that they’re roughly the same size as the V1.5 satellites it’s already launching – not the larger V2 or V2 Mini satellites discussed in recent FCC filings.
However, the data SpaceX provided also shows that those 54 satellites are headed to an orbit that only matches the company’s next-generation Starlink Gen2 (V2) constellation. While SpaceX quietly indicated that a V1.5-sized satellite was an option for early Gen2 launches in a supplemental October 2022 filing [PDF] with the FCC, it’s still unclear why SpaceX would prioritize launching V1.5-sized V2 satellites while its V1 constellation remains unfinished.
Adding to the confusion, in November 2021, CEO Elon Musk strongly implied that the inefficiencies of smaller Starlink V1.x satellites were so significant that they could risk bankrupting SpaceX if the company couldn’t start launching larger V2 satellites on its next-generation Starship rocket by the end of 2022. What, then, is the purpose of SpaceX’s imminent “Starlink G5-1” launch?
The update that's rolling out to the fleet makes full use of the front and rear steering travel to minimize turning circle. In this case a reduction of 1.6 feet just over the air— Wes (@wmorrill3) April 16, 2024
The name alone is confusing. Using the same shorthand as past Starlink V1 launches, “G5-1” refers to the first launch of “Group 5” of a constellation. “Group” here is synonymous with “shell,” which describes a set of satellites that share the same orbital inclination (the angle at which the orbit crosses the equator) and a similar orbital altitude. Of SpaceX’s three approved constellations, only one has five shells, and that shell can only exist at 97.6 degrees, not 43 degrees. SpaceX’s Gen2 constellation technically has nine planned shells, but the FCC has only partially approved three of those shells, one of which is at 43 degrees.
Ignoring the obtuse name, one possibility is that aspects of Starlink V2 satellite upgrades are not explicitly tied to the much larger size of those satellites and can be applied to SpaceX’s first-generation Starlink constellation without requiring a modified FCC license. If SpaceX wanted to add larger satellites to its V1 constellation or change the frequency bands they use, it would almost certainly have to seek a modified license from the FCC, which could take months.
There is no evidence SpaceX has done so, and any attempt would produce public documentation. The 43-degree inclination SpaceX’s mysterious “Starlink G5-1” launch is targeting also rules out any involvement in its V1 constellation, which only has approval for satellites between 53 and 97.6 degrees.
Aside from the unlikely possibility that details about the Starlink 5-1 mission are somehow incorrect or an artifact of a messy launch licensing process, there is at least one other unlikely explanation. In October 2018, the FCC granted SpaceX permission to launch a very low earth orbit (VLEO) constellation of 7518 Starlink satellites with dimensions similar to satellites that make up the 4408-satellite constellation the company is currently launching. More than four years later, SpaceX has yet to begin launching its approved VLEO constellation.
In November 2022, SpaceX told the FCC it intended to combine its Starlink VLEO and Starlink Gen2 constellations by adding V-band antennas to some of the almost 33,000 Gen2 satellites it hoped to launch – a move that would reduce the total number of Starlink satellites SpaceX needs to launch. Around the turn of the month, the FCC partially granted SpaceX’s Starlink Gen2 license, adding unprecedentedly strict requirements and only permitting the launch of 7500 of 33,000 planned Gen2 satellites to a limited set of inclinations (33, 43, and 53 degrees).
Perhaps, then, the uncertainty created by the FCC’s strange partial Gen2 grant made SpaceX change its mind about a dedicated Starlink VLEO constellation. However, without a license modification, SpaceX’s VLEO constellation is stuck with the same smaller (and potentially bankruptcy-inducing) satellites that its CEO believes make the first Starlink V1 constellation unsustainable. SpaceX also has less than two years until its VLEO constellation crosses its first deployment milestone, at which point the company will need to have launched half of it (3759 satellites) to avoid penalties from the FCC – up to and including the revocation of its license.
Despite the numerous reasons it wouldn’t make sense for Starlink 5-1 to be SpaceX’s first Starlink VLEO launch, almost 2500 of SpaceX’s approved VLEO satellites were intended to operate in a 336-kilometer (~209 mi) orbit inclined by 42 degrees – oddly similar to the 338-kilometer (~210 mi), 43-degree orbit SpaceX appears to be targeting with Starlink 5-1.
A surprise VLEO launch is a very unlikely explanation, but it’s only marginally stranger than the alternatives: that Starlink 5-1 is a V1-sized V2 launch with no prior mention or warning, a V1 launch to an orbit that would explicitly violate SpaceX’s Starlink V1 FCC license, or a paperwork error that has propagated so far that SpaceX distributed incorrect orbit information (which could threaten other satellites and rockets) less than two days before liftoff.
Thankfully, there is one last explanation – raised after this article was published – that appears to be much more likely. In response to a tweet summarizing these claims, astrophysicist Jonathan McDowell noted that SpaceX had, in fact, mentioned a third smaller Starlink V2 satellite variant in an October 2022 FCC filing that fell mostly under the radar. In that filing, SpaceX told that FCC it was developing three variants, not two. The smallest variant was said to weigh 303 kilograms and featured dimensions seemingly identical to SpaceX’s existing V1.5 satellites, which are estimated to weigh around 307 kilograms. SpaceX also stated that initial Falcon 9 launches will carry “approximately twenty to sixty satellites,” again confirming that V2 satellites could be about the same size and shape as V1.5 satellites.
SpaceX’s decision to develop a V1.5-sized version of V2 satellites makes little sense in the context of Musk’s implicit claims that problems inherent to its smaller V1 satellites threaten the company’s solvency. It’s clearer than ever that the SpaceX CEO may have been stretching the truth of the matter to craft an existential threat that might encourage employees to work longer hours. Still, developing and launching a V1.5-sized V2 satellite variant and beginning to launch those satellites while SpaceX’s Starlink Gen1 is more than 25% incomplete is confusing at best.
Regardless of what it’s carrying or why, a SpaceX Falcon 9 rocket is scheduled to launch Starlink 5-1 out of Florida’s Cape Canaveral Space Force Station (CCSFS) no earlier than 4:40 am EST (09:40 UTC) on Wednesday, December 28th.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
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 crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
