SpaceX Ready for Starship flight 13 Launch in Weeks after 6 Engine test fire x100 Faster Than Ever! === #alphatech #techalpha #spacex #elonmusk === 0:00 Milestone Cleared 0:30 Engine Sequence 3:12 Booster Bottleneck 6:11 Pad Prep 9:12 Catch Readiness 11:00 Tile Test === Thanks to: Starship Gazer: https://twitter.com/StarshipGazer Avid Space: https://www.youtube.com/c/LabPadre Daniel's 3D Station: https://twitter.com/T3DSS38 C-bass Productions: https://www.youtube.com/c/CbassProductions WAI: https://www.youtube.com/@Whataboutit Project Road to Mars: https://www.youtube.com/channel/UCBIumwk1oar1CEbgUybw1tA Evan Karen: https://www.youtube.com/channel/UCDN1X8Fz1oAXX-rBcOWjzmg Vooper3D: https://twitter.com/Vooper3D SLS: https://x.com/ScottLikedSLS ThreeDeDaniel: https://x.com/ThreeDeDaniel Ezekiel Overstreet: https://twitter.com/EzekielOverstr1 Starbase Surfer: https://twitter.com/cnunezimages iamVisual: https://www.youtube.com/@iamVisualVFX/videos Lewis Knaggs: https://twitter.com/lewisknaggs42 RyanHansenSpace: https://twitter.com/RyanHansenSpace/ IGW: https://x.com/interstellargw Everyday Astronaut: https://www.youtube.com/c/EverydayAstronaut Truthful_ast: https://x.com/Truthful_ast AshleyKillip: https://x.com/AshleyKillip === SpaceX Ready for Starship flight 13 Launch in Weeks after 6 Engine test fire x100 Faster Than Ever! SpaceX just did something extraordinary with Ship 40. All six Raptor engines roared to life together — a full 60 seconds of sustained fire at Massey's test site. And that means they've just cleared one of the most critical milestones before rolling the ship to the launch pad 2. And that’s not all. Some very deliberate activity has been happening around the area lately. Everything is pointing toward one thing: Starship Flight 13 is getting dangerously close. But the real question is… when? To answer that, we need to look at what Ship 40 actually went through at Massey’s. SpaceX Ready for Starship flight 13 Launch in Weeks after 6 Engine test fire x100 Faster Than Ever! The ship first rolled out to Massey's on June 23rd, and by June 24th propellant loading had already begun — matching the exact levels used during Ship 39's test campaign before Flight 12. Everything pointed toward a routine six-engine static fire. Then something changed. Fueling stopped early. The oxygen tank only filled to about two-thirds, and barely any methane was loaded. That's not how you prepare a full-stack ignition. On June 25th, only one engine fired. Engine 142 — a central Raptor 3 sea-level engine — burned for about 15 seconds while the other five stayed completely silent. Ship 40 rolled back to Mega Bay 2 the following day. SpaceX Ready for Starship flight 13 Launch in Weeks after 6 Engine test fire x100 Faster Than Ever! Now here's the thing. If the problem had been structural — a tank fault, an airframe issue — SpaceX wouldn't have fired anything at all. Engine 142 running clean was its own kind of data. It told engineers the core vehicle was healthy. Whatever the issue was, it was narrow. Contained. Fixable. And even in that constrained test, the partial tank fill and header tank ignition sequence closely mirrored an in-space burn — the exact reignition profile Starship needs to execute during re-entry. SpaceX found a way to collect meaningful data even from an incomplete attempt. === Subcribe Alpha Tech: https://www.youtube.com/@alphatech4966/?sub_confirmation=1 ===
AI Generated·May contain errors
Video Summary
AI Generated
SpaceX has achieved a major milestone with Ship 40, successfully completing a 60-second full-engine static fire. This test validates the Raptor 3 engines and the ship's structural integrity, signaling that Flight 13 is imminent. Parallel preparations are underway for Booster 20 and Pad 2 to ensure reliability for future catch attempts and orbital missions.
SpaceX just did something extraordinary with Ship 40.
All six Raptor engines roared to life together.
A full 60 seconds of sustained fire at Massey's test site.
And that means they've just cleared one of the most critical milestones
before rolling the ship to the launch pad too.
And that's not all.
Some very deliberate activity has been happening around the area lately.
Everything is pointing toward one thing.
Starship Flight 13 is getting dangerously close.
But the real question is, when?
To answer that, we need to look at what Ship 40 actually went through at Massey's.
The ship first rolled out to Massey's on June 23rd.
And by June 24th, propellant loading had already begun.
Matching the exact levels used during Ship 39's test campaign before Flight 12.
Everything pointed toward a routine six-engine static fire.
Then something changed.
Fueling stopped early.
The oxygen tank only filled to about two-thirds.
And barely any methane was loaded.
That's not how you prepare a full stack ignition.
On June 25th, only one engine fired.
Engine 142, a Central Raptor 3 sea-level engine,
burned for about 15 seconds while the other five stayed completely silent.
Ship 40 rolled back to Megabay 2 the following day.
Now, here's the thing.
If the problem had been structural, a tank fault, an airframe issue,
SpaceX wouldn't have fired anything at all.
Engine 142 running clean was its own kind of data.
It told engineers the core vehicle was healthy.
Whatever the issue was, it was narrow, contained, fixable.
And even in that constrained test,
the partial tank fill and header tank ignition sequence closely mirrored an in-space burn.
The exact re-ignition profile Starship needs to execute during re-entry.
SpaceX found a way to collect meaningful data even from an incomplete attempt.
And then, just only six days later, ship 40 rolled back out to Massey's.
This time, there was no partial attempt.
The ignition sequence was notably different from previous tests.
The two Raptor vacuum engines appeared to light first,
followed moments later by the three sea-level Raptors.
All six engines then burned together cleanly for a full 60 seconds,
delivering a powerful, stable flame that lit up the South Texas sky.
No anomalies were reported publicly.
Exactly what SpaceX needed.
Why did they sequence the vacuum engines first?
My theory is that SpaceX is being extra deliberate with the RVACs.
These engines have much larger nozzles optimized for vacuum.
So on the ground, they experience more stress from back pressure and potential flow separation.
Lighting them first allows the team to closely monitor their startup transients,
chamber pressures, and how their plumes interact with the test stand and the sea-level engines.
It's also excellent practice for in-space engine relight scenarios,
where the vacuum engines will play a critical role during orbital burns or landing burns.
And SpaceX didn't waste a second before posting it on X,
Starship's 60-second static fire ahead of the 13th flight test.
Are you already feeling the heat?
Because Flight 13 is getting very, very close.
If you are, drop a Go 13 in the comments.
And if you haven't subscribed yet, now's a great time.
That 60-second number isn't arbitrary.
SpaceX commissioned its first Starship flame trench at Massey Outpost in 2024,
specifically to allow these long static fires — the kind of sustained,
full-duration test that simply wasn't possible before.
One engine firing for 15 seconds is a health check.
Six engines burning for a full minute is something else entirely.
It's a stress test of the complete propulsion system, validating engine performance,
vibration loads, thermal behavior, propellant flow rates,
and the ship's structural ability to hold together under maximum thrust.
This is the closest you can get to a real flight without actually leaving the ground.
And critically, this test validates the Raptor 3 engines,
the newest generation of SpaceX's most important hardware.
Flight 13 will be another suborbital flight, mirroring much of Flight 12's profile.
With particular focus on the ship's vacuum engine relight in space,
something Flight 12 attempted, but Flight 13 needs to nail cleanly.
Every data point from that 60-second fire feeds directly into reducing that risk.
So, where does Ship 40 stand now?
It rolled back to Megabay 2 on July 2 and was lifted onto a work stand for post-fire inspection.
Engineers will go through the engines, the TPS tiles, the structure,
check for leaks, and review telemetry data from the test.
Given how clean the fire was, major fixes are unlikely.
After that, the checklist is short.
Final integrations, payload installation,
and then transport to Pad B to stack with Booster 20.
And that's the other half of this story.
While Ship 40 was wrapping up its engine campaign,
Booster 20 was back in Megabay 1, getting its full complement of 33 Raptor engines installed.
Unlike Booster 19, which had a longer static fire campaign,
Booster 20 should move through quickly,
likely a tanking test to verify pad changes,
then a straight 33-engine static fire before rolling back for flight preparations.
That 33-engine static fire is the next major milestone,
and it's the one that will set the clock for Flight 13.
Based on current vehicle timelines, late July is possible,
but this window could easily slip into August.
Ship 40 is expected within the next month or so.
The ship's side is essentially done.
The bottleneck now sits entirely with Booster 20.
But zoom out, and the bigger picture is just as striking.
Meanwhile, Ship 41 was already rolling out to Massey's on June 28
to begin its own cryo test campaign, running in parallel.
Two Block 3 ships in active test campaigns at the same time.
That's not an accident.
That's a program that has learned to move.
Flight 13 has one job above all others.
Show that Starship is reliable.
That the Raptor 3 engines can be trusted.
That the lessons from Flight 12 have been absorbed, acted on,
and proven on the ground before being proven in the sky.
The 60 seconds at Massey's suggest they're on track.
But while Ship 40 was wrapping up its engine campaign at Massey's,
something equally significant was happening a few miles down the road at Pad 2.
Water deluge activations.
Chopstick movements.
BQD and SQD cycling.
Clamp arm checks, one by one, in rapid succession.
Taken individually, each of these looks like routine pad maintenance.
Taken together, they paint a very clear picture.
Start with the water deluge system.
Pad 2's deluge is not a simple fire hose.
It floods the launch mount and flame trench with roughly 350,000 gallons of water
in a precisely timed sequence, absorbing the thermal energy
and dampening the acoustic shock waves that would otherwise tear the pad apart
when 33 Raptors light simultaneously.
SpaceX learned that lesson the hard way at Pad 1.
Pad 2 was designed from day one,
with a water-cooled steel deck on the orbital launch mount
to handle repeat high-cadence launches.
But what observers noticed recently wasn't just a standard deluge check.
There were two distinct firing profiles.
One matching the familiar launch sequence
and a second that was noticeably different.
Stronger water pressure, pulsing intervals, and a heavy purge phase at the end.
That second profile doesn't match a launch.
It matches a landing.
When a super-heavy booster returns for a catch attempt,
13 of its Raptor engines are firing at close range directly above the pad structure.
The heat and acoustic load are different, more concentrated, more directional.
SpaceX appears to be tuning the deluge system
to handle both scenarios within a single flight cycle.
Then there's the mechanical side.
The chopsticks, Pad 2's catch arms,
were raised to full height and cycled through stabilizer movements.
The BQDs, the quick-disconnect arms that supplies propellant and power to the booster,
were extended and retracted repeatedly,
with engineers clearly evaluating both speed and precision.
SpaceX has been relocating the BQD alignment sensors into protective hoods
to ensure they survive repeated operations.
A design choice that only makes sense
if you're planning to use those disconnects over and over again,
flight after flight.
And critically,
the 20 hold-down clamps on the launch mount were tested individually,
retracted at normal speed,
then deployed one by one at slow speed
so engineers could observe each clamp independently.
That level of granular testing suggests SpaceX wants to be certain
or release it cleanly on command.
Both matter enormously when you're planning to catch that same booster on the way back down.
The chopstick actuators have also been upgraded from hydraulic to electric,
a change expected to improve responsiveness and reliability during booster and ship catches.
Faster, more precise arm movement is not a requirement for a launch.
It is absolutely a requirement for snagging a 70-meter booster
out of the sky at low speed.
And that brings us to something that deserves its own moment of reflection.
When does a V3 Super Heavy booster finally get caught?
Three catches.
All Block 1 or Block 2.
Booster 12 on Flight 5.
The first ever.
Snagged by Mechazilla's arms on the very first attempt.
Booster 14 on Flight 7.
Booster 15 on Flight 8.
Three for three when SpaceX actually committed to the attempt.
And then it stopped.
Flight 6's catch was aborted mid-flight.
Not all criteria were met, so the flight director never gave the command.
Flights 9, 10, and 11 didn't attempt to catch at all,
with the boosters directed to splashdowns or used for experimental data.
And on Flight 12, Booster 19 never even made it to the catch window.
The boostback burn failed, and it crashed into the Gulf of Mexico at over 1,400 kmh.
Now enter Booster 20, the first V3 Super Heavy to ever attempt a catch.
Block 3 is a fundamentally different vehicle.
Taller, heavier, running 33 Raptor 3 engines that have never been through a catch cycle before.
Everything validated on the previous boosters needs to be proven again from scratch.
Flight 13 won't attempt the catch.
That's Flight 14's job.
But it needs to prove the boostback is reliable,
and the descent is controlled enough to set up that attempt.
That's exactly what all the activity at Pad 2 is building toward.
The dual deluge profiles tuned for a booster return.
The BQD sensors relocated into protective hoods to survive repeated operations.
The chopstick actuators upgraded from hydraulic to electric for faster, more precise response.
Do you think SpaceX might actually go for the catch on Flight 13?
Let me know in the comments.
Outside of Ship 40 and Pad 2, there's something else worth noting.
And it's happening inside Star Factory.
Do you remember back in March,
when we covered that Starship nose cone spotted with white heat shield tiles?
Well, they're back.
Those mysterious white heat shield tiles have made a comeback.
This time, prominently placed on the nose tip.
They're half-sized to better fit the tight curvature of the nose.
Noticeably thicker than the standard black tiles,
with no insulation layer or protective felt underneath.
Just the tile itself.
A visible gap between it and the hull,
and the same attachment pins as everything else.
The obvious question is, why white?
And why exactly at the nose tip?
Here's what I think.
That gap isn't a mistake or a temporary placeholder.
SpaceX may have intentionally stripped away the underlayers
to expose these tiles to the absolute harshest conditions
during re-entry with almost no thermal buffering.
Think about it.
The normal tile stack, pins, felt, mesh, ablative material,
then the tile on top,
is designed to spread and absorb heat gradually.
By removing those protective layers,
the white tile essentially faces re-entry almost naked.
Whatever happens to it will give engineers extremely clear,
real-world data on how the new tile material or coating
performs entirely on its own.
And the nose tip is the most brutal place to run this test.
It's the single most thermally stressed point
on the entire vehicle during re-entry.
Highest heat flux, highest pressure,
and the most aggressive plasma interaction.
If you want to know exactly what a new tile formulation
can handle at its absolute limit,
you don't test it somewhere safe.
You put it right where the heat hits hardest.