Connect with us

News

SpaceX still an option for future Amazon internet satellite launches, says Senior VP

Published

on

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.

Advertisement

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.

Advertisement

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.

Three batches and two generations of SpaceX Starlink satellites. (SpaceX)

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.

Advertisement

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.

Advertisement

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla faces Full Self-Driving pushback in EU over ‘speeding’

Published

on

Credit: Tesla

A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.

The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.

TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.

Tesla Full Self-Driving gets first-ever European approval

Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.

Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.

TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of ​vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.

This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.

This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.

However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.

Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.

Continue Reading

Elon Musk

Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’

Published

on

Credit: Tesla

Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.

The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.

A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”

Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.

Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.

This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.

The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.

Musk teased that a similar feature was “coming” back in February:

Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says

It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.

Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.

Here’s an example of that from December:

Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.

We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.

Continue Reading

News

Tesla Cybercab has one important piece that AI4 cars might need for FSD

Published

on

Credit: @tpgoebel | X

A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.

This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.

The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.

Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:

Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.

But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:

This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.

For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.

Without it, even the most advanced neural nets struggle when their “eyes” are compromised.

What Does This Mean for AI4 Cars?

This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:

Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys

As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.

As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.

Continue Reading