Connect with us

News

SpaceX sends Starship prototype to launch pad after engine installation

Published

4 years ago

on

After several weeks of work back at SpaceX’s Starbase rocket factory, the company has transported a new and improved Starship prototype to nearby test and launch facilities, where it joined a similarly upgraded Super Heavy booster.

That Starship prototype – Ship 24 or S24 – is closely following in the footsteps of Super Heavy Booster 7 (B7), which kicked off a similar phase of preflight testing about two weeks ago. The purposes of their latest trips from the factory to the launch pad are also largely the same and could potentially open the door for Starship’s inaugural orbital launch attempt sometime later this year if the process goes smoothly. Both protypes have a ways to go, however.

Booster 7 and Ship 24 got off to fairly rocky starts when they began a less risky phase of proof testing in May and June. Apparently caused by improper sequencing or a small design flaw, a large steel tube meant to carry liquid methane fuel through Booster 7’s liquid oxygen tank and double as a storage vessel for landing propellant violently imploded when a vacuum formed inside it. It took SpaceX several weeks to repair the damage but, defying the odds, the tube was eventually repaired and Booster 7 completed another two proof tests soon after.

A few weeks later, during one of Ship 24’s first tests, a much smaller internal pipe – likely carrying high-pressure gas – also failed, damaging heat shield tiles and other adjacent plumbing. S24’s troubles were less dramatic and only took a few days to fix, but both were still new failure modes for the Starship program and served as a reminder that Starship hardware remains relatively immature and that SpaceX is still learning. Nonetheless, they also demonstrated SpaceX’s ability to respond quickly to new problems, as both B7 and S24 sailed through additional testing without apparent issue after quick repairs.

Advertisement
Ship 24’s first cryoproof. (NASASpaceflight – Starbase Live)
Both of Booster 7’s successful post-repair cryoproof tests. (NASASpaceflight Starbase Live)

After completing cryogenic proof and thrust simulation testing, B7 and S24 returned to SpaceX’s factory facilities for Raptor installation and finishing touches. SpaceX took about six weeks to install 33 Raptor engines and associated heat shielding on Booster 7, while installing six Raptors and wrapping up a few other aspects of Ship 24 took about four weeks.

Collectively, Booster 7 and Ship 24 have 39 Raptor engines installed. (SpaceX)

Aside from the installation of most of the Starship’s missing heat shield tiles, Ship 24’s preparations did include one particularly unique step involving its payload bay prototype. SpaceX’s first stab at a Starship payload bay has been likened to a giant Pez dispenser, which is not entirely inaccurate. Exclusive to Starlink, satellites will be stored on a rectangular rack that’s assumed to operate like an elevator. As an unknown mechanism pushes two satellites at a time through Starship’s slot-like bay door, the stack of satellites will feed downwards like bullets in a magazine until the full set is fully deployed.

A render of Starship’s Starlink bay in action. (SpaceX)

In late June, SpaceX attached a giant white box to a crane and positioned the box to interface with Ship 24’s bay door, where it hung for the better part of a day. The test confirmed speculation that the box was meant to solve perhaps the most obvious problem SpaceX’s unique payload bay design posed: payload installation. SpaceX’s solution appears to involve using the deployment mechanism in reverse, with the white box conveying Starlink Gen2 satellites through the ‘slot’ and the dispenser grabbing and lifting each pair up into the bay.

It’s possible that Ship 24 will have a handful of Starlink V2/Gen2 satellites loaded into its bay if it passes its next tests. Before being cleared for flight, Ship 24 will need to complete at least one nominal wet dress rehearsal (simulating every aspect of a launch short of engine ignition) and one six-engine static fire, though several tests are far more likely. Starship S24’s test campaign will benefit significantly from Starship S20, which survived extensive testing (and multiple six-Raptor static fires) in 2021. In comparison, Super Heavy B7’s similar wet dress rehearsal and static fire test campaign will be almost entirely new to SpaceX, save for a single three-engine static fire completed by an outdated booster prototype last year.

SpaceX could attempt to static fire Booster 7 for the first time as early as Wednesday, July 6th. It’s unclear if the company will attempt to kick off Ship 24’s next round of testing in the gaps between Super Heavy B7’s static fire testing. While unlikely, SpaceX is technically capable of testing Ship 24 and Booster 7 simultaneously.

Related Topics:

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 confirms Cybercab with no steering wheel enters production

Published

3 hours ago

on

April 25, 2026

By

Tesla has confirmed today that its steering wheel-less and pedal-less Cybercab, the vehicle geared toward launching the company’s autonomous ride-hailing hopes, has officially entered production at its Giga Texas production facility outside of Austin.

The Cybercab is a sleek two-door, two-passenger coupe engineered from the ground up as an electric self-driving vehicle. It features no steering wheel or pedals, relying instead on Tesla’s advanced vision-only Full Self-Driving system powered by multiple cameras and artificial intelligence.

The minimalist cabin centers on a large display screen that serves as the primary interface for passengers, creating an open, futuristic space optimized for comfort during unsupervised rides. A compact 35-kilowatt-hour battery pack delivers exceptional efficiency at 5.5 miles per kilowatt-hour, providing an estimated 200-mile range.

Additional innovations include inductive charging compatibility and a lightweight design that enhances aerodynamics and performance.

Production at Giga Texas builds on earlier prototypes and initial units completed earlier in 2026. The facility, already a hub for Model Y and Cybertruck assembly, now ramps up dedicated lines for the Cybercab.

This shift to volume manufacturing reflects Tesla’s strategy to scale affordable autonomous vehicles rapidly.

By focusing on a dedicated platform rather than adapting existing models, the company aims to keep costs low while prioritizing safety and reliability through continuous AI improvements.

The Cybercab’s debut in production carries broad implications for urban mobility. As the cornerstone of Tesla’s Robotaxi network, it promises on-demand, driverless rides that could slash transportation expenses, reduce traffic accidents caused by human error, and lower emissions through its all-electric powertrain.

Accessibility features, such as space for service animals or assistive devices, further broaden its appeal. Regulators and cities worldwide will soon evaluate its deployment, but the vehicle’s design already addresses key hurdles in scaling unsupervised autonomy.

Challenges persist, including full regulatory clearance and building charging infrastructure. Yet this production launch signals momentum. With Cybercabs poised to roll out in increasing numbers, Tesla edges closer to a future where personal ownership meets shared fleets of intelligent vehicles.

The start of Cybercab production is more than just a new vehicle entering mass manufacturing for Tesla, as it’s a signal autonomy is near. Being developed without manual controls is such a massive sign by Tesla that it trusts its progress on Full Self-Driving.

While the development of that suite continues, Tesla is making a clear cut statement that it is prepared to get its fully autonomous vehicle out in public roads as it prepares to revolutionize passenger travel once and for all.

Continue Reading

News

Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much

There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.

Published

23 hours ago

on

April 24, 2026

By

(Photo: Hector Perez/YouTube)

Tesla Full Self-Driving v14.3.2 began rolling out to some owners earlier this week, and there are some notable improvements that came with this update.

There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.

Overall operation saw a handful of slight improvements, especially with parking performance, which has been the most notable difference with the arrival of FSD v14.3. However, there are still some very notable shortcomings, most notably with region-specific signage and navigation.

Tesla Assisted Smart Summon (ASS) improvements

There are noticeable improvements to ASS operation, which has definitely been inconsistent in terms of performance. Tesla wrote in the release notes for v14.3.2:

“Unified the model between Actually Smart Summon, FSD, and Robotaxi for more capable and reliable behavior.”
As recently as this month, I used Summon with no success. It had pulled around the parking lot I was in incorrectly, leaving the range at which Summon can be operated and losing a signal while moving in the middle of the lot.

This caused me to sprint across the lot to retrieve the vehicle:

Unfortunately, Summon was not dependable or accurate enough to use regularly. It appears Tesla might have bridged the gap needed to make it an effective feature, as two tests in parking lots proved that Summon was more responsive and faster to navigate to the location chosen.

It also did so without hesitation, confidently, and at a comfortable speed. I was able to test it twice at different distances:

I plan to test this more thoroughly and regularly through the next few weeks, and I avoided using it in a congested parking lot initially because I have not had overwhelming success with Summon in the past. I wanted to set a low baseline for it to see if it could simply pull up to the place I pinned in the Tesla app.

It was two for two, which is a big improvement because I don’t think I ever had successful Summon attempts back-to-back. It just seems more confident than ever before.

New Disengagement Categories

This is a really good idea from Tesla, but there are some issues with it. The categories you can select are Critical, Comfort, Preference, and Other.

I think the reasons why people choose to take over would be a better way to prompt drivers, like, “Traveling Too Fast,” “Incorrect Maneuver,” “Navigation Error,” would be more beneficial.

I say this because it seems that how we each categorize things might be different. For example, I shared a video of an intervention because the car had navigated to an exit to a parking lot and put its left blinker on, despite left turns not being allowed there.

I disengaged and chose Critical as the reason; it’s not a comfort issue, it’s not a preference, it’s quite literally an illegal turn, and it’s also dangerous because it cuts across several lanes of traffic and is 180 degrees.

Some said I should not have labeled this as Critical, but that’s the description I best characterized the disengagement as.

Categorizing interventions is a good thing, but it’s kind of hard to determine how to label them correctly.

Inconsistency with Regional Traffic Patterns

Tesla Full Self-Driving is pretty inconsistent with how it handles regional or local traffic patterns and road rules. The most frequent example I like to use is that of the “Except Right Turn” stop sign, which has become a notorious sighting on our social media platforms.

In the initial rollout of v14.3, my Model Y successfully navigated through one of these stop signs with no issues. However, testing at two of these stop signs yesterday proved it is still not sure how to read signs and navigate through them properly.

Off camera, I approached another one of these signs and felt the car coming to a stop, so I nudged it forward with the accelerator pedal pressed.

This helped the car go through the sign without stopping, but I could feel the bucking of the vehicle as the car really wanted to stop.

Musk said on the earnings call earlier this week that unsupervised FSD would probably be available in some regions before others, including a state-to-state basis in the U.S.

“It’s difficult to release this like to everyone everywhere all at once because we do want to make sure that they’re not unique situations in a city that particularly complex intersection or — actually, they tend to be places where people get into accidents a lot because they’re just — perhaps there’s — and like I said, an unsafe intersection or bad road markings or a lot of weather challenges. So I think we would release unsupervised gradually to the customer fleet as we feel like a particular geography is confirmed to be safe.”
This could be one of those examples that Tesla just has to figure out.

Highway Operation

Full Self-Driving is already pretty good at routine roadway navigation, so I don’t have too much to report here.

However, I was happy with FSD’s decision-making at several points, including its choice not to pass a slightly slower car and remain in the right lane as we approached the off-ramp:

Better Maneuvering at Stop Signs

Many FSD users report some strange operations at stop signs, especially four-way intersections where there is a stop sign and a line on the road, and they’re not even with one another.

I experienced this quite frequently and found that FSD would actually double stop: once at the stop sign and again at the line.

This created some interesting scenarios for me and I had many cars honk at me when the second stop would happen. Other vehicles that had waved me on to proceed through the intersection would become frustrated at the second stop.

FSD seems to have worked through this particular maneuver:

FSD should know to go to the more appropriate location (whichever provides better visibility), and proceed when it is the car’s turn to move. The double stop really ruined the flow of traffic at times and generally caused some frustration from other drivers.

Continue Reading

News

Tesla plans to resolve its angriest bunch of owners: here’s how

Since the rollout of the AI4 chip in Tesla vehicles, owners with the last generation self-driving chip, known as Hardware 3, have been persistent in their quest for a solution to their issue: they were told their cars were capable of unsupervised Full Self-Driving. It turns out the cars are not.

Published

1 day ago

on

April 24, 2026

By

tesla-asia-model-3
Credit: Tesla Asia/Twitter

Tesla has a plan to make Hardware 3 owners whole after CEO Elon Musk admitted that those with that self-driving chip in their cars will not have access to unsupervised Full Self-Driving.

The company’s strategy is so crazy that it is sort of hard to believe.

Since the rollout of the AI4 chip in Tesla vehicles, owners with the last generation self-driving chip, known as Hardware 3, have been persistent in their quest for a solution to their issue: they were told their cars were capable of unsupervised Full Self-Driving. It turns out the cars are not.

During the Tesla Q1 earnings call on Wednesday, Musk finally clarified what the company’s plans are for Hardware 3 owners, what they will be offered, and what Tesla will have to do internally to prepare for it.

The answer was somewhat mind-boggling.

Musk said:

“Unfortunately, Hardware 3 — I wish it were otherwise, but Hardware 3 simply does not have the capability to achieve unsupervised FSD. We did think at one point it would have that, but relative to Hardware 4, it has only 1/8 of the memory bandwidth of Hardware 4. And memory bandwidth is one of the key elements needed for unsupervised FSD.”
He continued, stating that HW3 owners would have the opportunity to trade their cars in at a discounted rate in order to get the AI4 chip:

“So for customers that have bought FSD, what we’re offering is essentially a trade-in — like a discounted trade-in for cars that have AI4 hardware, and we’ll also be offering the ability to upgrade the car, to replace the computer. And you also need to replace the cameras, unfortunately, to go to Hardware 4.”
Obviously, Tesla has a lot of people to work with and make this whole thing right. Musk was adamant that HW3 would be capable of FSD, and now that the company has finally admitted that it is not, there are some things that could come of this.

There has been open talk about some sort of class action lawsuit against Tesla. The promises that Tesla made previously could be considered a breach of contract or even false advertising, and that’s according to Grok, Musk’s own AI program.

Musk went on to say that Tesla would likely have to establish new microfactories to effectively and efficiently replace HW3 computers and cameras:

…So to do this efficiently, we’re going to have to set up, like kind of micro factories or small factories in major metropolitan areas in order to do it efficiently. Because if it’s done just at the service center, it is extremely slow to do so and inefficient. So we basically need like many production lines to make the change.”
This is going to be an extremely costly process, especially if Tesla has to buy real estate, properties, and equipment to complete this work. Additionally, there was no wording on pricing, but Musk never said it would be free. It will likely come with some kind of price tag, and HW3 owners, after being left hanging for so long, will have something to say about that.

Advertisement



Continue Reading