News
SpaceX still an option for future Amazon internet satellite launches, says Senior VP
An Amazon executive says that the company could still call on SpaceX to launch some of its Project Kuiper internet satellites after two of the three unproven rockets it purchased announced launch delays days apart.
Amazon began work on Project Kuiper in 2018. When SpaceX CEO Elon Musk fired several senior employees overseeing the company’s Starlink satellite internet program for being overly cautious, at least two of those employees immediately landed in senior positions at Project Kuiper. Four years later and more than two years after Amazon received an FCC license to deploy its 3,236-satellite Project Kuiper constellation, which aims to compete directly with SpaceX’s Starlink, the company’s first prototype satellite launch has changed rockets and slipped from late 2022 to early 2023.
Of the 77 firm launch contracts Amazon has signed since April 2021, only nine are for a rocket – United Launch Alliance’s (ULA) Atlas V – that has already successfully flown. The remaining 68 (and another 15 exercisable options) are spread among ULA’s Vulcan Centaur, Arianespace’s Ariane 6, and Blue Origin’s New Glenn, all of which are months away from their first launch attempts.
On October 10th, ULA CEO Tory Bruno told reporters that Vulcan Centaur’s launch debut had slipped from its latest late-2022 target to no earlier than (NET) “early 2023.” Garnering 38 of 77 firm contracts, Vulcan is the single most important rocket for Amazon’s Project Kuiper plans and is likely expected to launch close to half of all Kuiper satellites.
Nine days later, Ariane Group and the European Space Agency (ESA) announced that Ariane 6’s launch debut had also slipped from a late-2022 target. Unlike Vulcan’s gentle early-2023 slip, Ariane 6’s debut was pushed to late 2023 at the earliest, and ESA and Ariane officials frankly admitted that that could easily become 2024. Excluding options, Ariane 6 won 18 Project Kuiper launch contracts and is the constellation’s second most important rocket.
Because Amazon applied for its Project Kuiper license so early, a six-year countdown started when the FCC approved its license in July 2020. If Amazon fails to launch half of its 3,236 satellites within six years of that receipt, the FCC could revoke Kuiper’s constellation license. While it’s unlikely that the FCC would actually revoke the license of a constellation that’s close to achieving its deployment milestones, the deadline still emphasizes just how far Amazon and its suppliers are falling behind.
Vulcan, Ariane 6, and Project Kuiper prototype launch delays have only worsened an already challenging situation. In addition to the rocket’s long-awaited debut, ULA has major obligations to NASA and the US military, who expect Vulcan to complete up to four more launches in 2023. Unless ULA pulls off a minor miracle, it’s unlikely that Vulcan will be able to launch five times in its first year of service. Respectively, ULA’s Atlas V and Delta IV rockets took 2.5 and 3.5 years to reach that milestone. If ULA’s past record serves as a reasonable guide for its future, it’s possible that Vulcan Centaur won’t have the spare capacity to begin Project Kuiper launches until 2025.
The same is arguably true for Ariane 6, which has an even busier manifest – all of which may be delayed to 2024. Of Arianespace’s two most recent rockets, Ariane 4 took 14 months and Ariane 5 took 53 months to complete their first five fully successful launches. Ariane 6 borrows heavily from Ariane 5’s design. Unless Arianespace gets off to a record-breaking start or prioritizes Amazon over ESA and other European operators, an almost unthinkable scenario, it’s difficult to imagine that Ariane 6 will have the spare capacity to begin Project Kuiper launches before 2025 or 2026.
Blue Origin’s New Glenn rocket, which is years behind schedule and unlikely to debut before late 2023 or 2024, might ironically be Amazon’s best bet for the first dedicated Project Kuiper launch, but only if its debut is near-flawless and doesn’t slip any further. Given that New Glenn will be Blue Origin’s first orbital rocket of any kind, more delays and issues (if not an outright failure) on the first launch are likely. New Glenn is thus also unlikely to be ready to launch large batches of Project Kuiper satellites until 2024 or 2025. Given the record of its suborbital New Shepard rocket, the odds are also against Blue Origin quickly ramping up the cadence of a far more complex orbital launch vehicle.
Only Atlas V appears to have any significant chance of beginning large-scale Project Kuiper launches before 2025. But ULA is shutting down Atlas V production to transition to Vulcan, so it’s impossible for Amazon to order more than nine of the rockets, as ULA.
Unfortunately for Amazon, in addition to the many rocket-side issues facing Project Kuiper, its satellite prototype delays will make it even harder for the company to begin large-scale launches sooner than later. SpaceX, now the proud owner of a majority of all working satellites in orbit, took around 21 months to go from launching its first two prototypes to its first batch of 60 operational Starlink satellites. The satellite design it settled on was almost nothing like the first two prototypes.
If Amazon’s first prototypes launch on Vulcan’s early-2023 debut, perform excellently, meet or exceed expectations after just a few months of testing, and are close to the final satellite design, Project Kuiper may still have a shot at manufacturing enough satellites to fill one or more launches in 2024. But if its first satellites run into major issues, Amazon’s decision to “[bring] up manufacturing of…production satellites [in parallel with prototype development]” could set it back months if it’s forced to redesign its satellites, find new suppliers, or significantly change the factory it’s already building.
Combined, Project Kuiper finds itself in an unenviable position. It’s thus unsurprising that as of October 2022, an Amazon executive appears to have changed their tune about using SpaceX rockets. Over the last ~13 months, SpaceX has become the single most productive launch provider in the world, besting the entire nation of China. On a quarterly basis, SpaceX now launches more useful mass to orbit than the rest of the world combined. It’s also the only launch provider on Earth that can create spare capacity for last-minute customers by shuffling its own internal launch demands.
According to Dave Limp, senior vice president of devices and services at Amazon, Project Kuiper is willing to consider taking advantage of some of SpaceX’s unprecedented capabilities after it shunned the company entirely in earlier contracts and statements. Speaking in a Washington Post Live interview, Limp says that Amazon is “open to contracting with anyone” and understands “that heavy launch capacity is [and will likely remain] pretty constrained” for years to come.
Unfortunately, Limp began by falsely asserting that Falcon 9 was too small to have warranted earlier launch contracts, stating that it’s “probably at the low end of…the capacity that we need.” In an expendable configuration, Falcon 9 can launch more than 22 tons (~48,500 lb) to low Earth orbit (LEO), while Ariane 6 is quoted at [PDF] 21.7 tons (~47,800 lb). While it hasn’t flown, SpaceX also offers an extended payload fairing that should more or less match Vulcan and Ariane 6’s largest fairings.
But Limp expressed interest in SpaceX’s Falcon Heavy rocket, which could likely match or come close to the payload volume of Ariane 6 and Vulcan and far exceed either rocket’s performance to LEO. In a configuration that would allow SpaceX to recover all three of Falcon Heavy’s boosters, almost guaranteeing that it would cost less than Vulcan or Ariane 6, the rocket would likely be able to launch around 40-50 tons (90,000-110,000 lb) to LEO. The Amazon executive even brought up SpaceX’s next-generation Starship rocket as a more desirable option for future Project Kuiper launches. Starship is designed to launch anywhere from 100 to 150 tons to LEO, should cost even less than Falcon 9 or Falcon Heavy, and will eventually feature a payload bay that dwarfs even New Glenn’s massive fairing.
Nonetheless, despite the promise of SpaceX, Amazon appears to be in no rush to hedge its bets on Vulcan, Ariane 6, and New Glenn. Only time will tell if its multi-billion-dollar gamble pays off.
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
