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 released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla claims supplier is holding Cybertruck production hostage
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
