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.

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.

Advertisement
-
-
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 Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Published

14 hours ago

on

August 2, 2026

By

Credit: Teslarati

Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.

Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.

For now, here’s everything I noticed with v14.3.7:

Overall Improvement

Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.

The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.

However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.

I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.

The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.

Manual Signal Override is More Responsive

On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.

The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.

Parking Lot Performance

Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.

The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:

 

I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.

Full Self-Driving Averts Disaster

A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:

There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.

However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.

Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.

It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.

What Needs to Improve

Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps

On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.

However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.

I even tried scrolling down into Sloth quickly, but I ended up just taking over:

A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.

Navigation

Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.

Auto Wipers

Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.

You can watch our full review of Tesla Full Self-Driving v14.3.7 below:

Continue Reading

Elon Musk

SpaceX’s biggest test yet arrives this week and it’s not a rocket launch

Published

1 day ago

on

August 1, 2026

By

SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.

The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.

Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.

SpaceX scores another massive Pentagon deal to support military satellites

Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.

The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.

As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.

Continue Reading

Elon Musk

SpaceX’s Starship just got filmed by its own cargo

SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.

Published

1 day ago

on

August 1, 2026

By

SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.

The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.

The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.

Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.

Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.

Continue Reading