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 CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
