SpaceX Engineer revealed Ship 35 ''REGAIN CONTROL'' before RUD BUT...Here's Solution === #greatspacex#elonmusk#spacex#nasa#starship == Advertisers who want to place ads on our channel, please contact the email manager: [email protected] === SpaceX Starship SN Be the first to sponsor us Thank you. https://www.patreon.com/GreatspaceX?fan_landing=true ==== SpaceX Engineer revealed Ship 35 ''REGAIN CONTROL'' before RUD BUT...Here's Solution Good news, everyone! SpaceX has just announced a positive update on S35’s “Regain Control” stage, clearing the path for upcoming flights. Meanwhile, Blue Origin continues to push into the suborbital tourism market with its New Shepard program. And halfway around the globe, Japan is making strides in preparing its Mars sample-return mission. Let’s dive into all of today’s stories on Great SpaceX. Flight 9 ended with a mix of triumphs and unanswered questions, and though everyone had been expecting S35 to steal the show, the upper stage instead delivered a sobering reminder of how many hurdles remain. From the outset, S35 carried enormous expectations. We counted on it to reach orbit, deploy its payload, reignite in space, survive re-entry, and splash down gently. Instead, it never managed to open its payload bay, then began to tumble uncontrollably. At T+00:46:40—just as the cameras caught the aft flap burning—the live feed cut out and, for a moment, it felt like that was truly the end of S35’s journey. SpaceX Engineer revealed Ship 35 ''REGAIN CONTROL'' before RUD BUT...Here's Solution But SpaceX engineers weren’t ready to give up. Behind the scenes, they kept pinging S35 with commands, trying to reestablish guidance and telemetry. Their persistence paid off. A few days later, an internal screenshot—purportedly a chat from a SpaceX team member—revealed the key message: “We did regain some control at the end.” That small revelation changed how we should view the flight’s conclusion. Why does regaining control matter so much? By the time S35 regained stability, the stage had endured severe structural and thermal stress. Its aft flap was badly scorched, critical plumbing was likely compromised, and internal avionics might have suffered damage from violent vibrations. No one expected a gentle touchdown at that point. Yet, regaining enough attitude authority to fly into the designated splashdown corridor proved that the vehicle’s guidance and control systems still functioned under dire conditions. SpaceX Engineer revealed Ship 35 ''REGAIN CONTROL'' before RUD BUT...Here's Solution Every Starship flight must operate within a narrow warning area set by the FAA. For S35, that zone stretches across the Indian Ocean, southeast of Madagascar. Landing within that corridor safeguards shipping lanes and coastal regions, and it demonstrates to regulators—both federal and international—that SpaceX can contain any unexpected debris. By reorienting S35 away from a random spin and guiding it back over water, SpaceX fulfilled its safety obligations, ensuring no harm came to people or property. This achievement should smooth the path for quick flight licensing, as regulators will see that SpaceX can still satisfy stringent safety requirements even after mission anomalies. ---- We use images and content in accordance with the YouTube Fair Use copyright guidelines: https://www.youtube.com/intl/en/about/copyright/fair-use/ Any questions about copyright please send us via Gmail: [email protected] To be resolved, thank you.
Good news everyone, SpaceX has just announced a positive update on S35's regain control
stage clearing the path for upcoming flights.
Meanwhile, Blue Origin continues to push into the suborbital tourism market with its new
Shepard program.
And halfway around the globe, Japan is making strides in preparing its Mars sample return
mission.
Flight 9 ended with a mix of triumphs and unanswered questions, and though everyone
had been expecting S35 to steal the show, the upper stage instead delivered a sobering
reminder of how many hurdles remain.
From the outset, S35 carried enormous expectations.
We counted on it to reach orbit, deploy its payload, reignite in space, survive reentry,
and splash down gently.
Instead, it never managed to open its payload bay, then began to tumble uncontrollably.
At T-plus 46 minutes and 40 seconds, just as the cameras caught the aft flap burning,
the live feed cut out and for a moment it felt like that was truly the end of S35's
journey.
But SpaceX engineers weren't ready to give up.
Behind the scenes, they kept pinging S35 with commands, trying to reestablish guidance
and telemetry.
Their persistence paid off.
A few days later, an internal screenshot, purportedly a chat from a SpaceX team member,
revealed the key message, we did regain some control at the end.
That small revelation changed how we should view the flight's conclusion.
Why does regaining control matter so much?
By the time S35 regained stability, the stage had endured severe structural and thermal
stress.
Its aft flap was badly scorched, critical plumbing was likely compromised, and internal
avionics might have suffered damage from violent vibrations.
No one expected a gentle touchdown at that point, yet regaining enough attitude authority
to fly into the designated splashdown corridor proved that the vehicle's guidance and control
systems still functioned under dire conditions.
Every Starship flight must operate within a narrow warning area set by the FAA.
For S35, that zone stretches across the Indian Ocean southeast of Madagascar.
Landing within that corridor safeguards shipping lanes and coastal regions and demonstrates
to regulators, both federal and international, that SpaceX can contain any unexpected debris.
By reorienting S35 away from a random spin and guiding it back over water, SpaceX fulfilled
its safety obligations, ensuring no harm came to people or property.
This achievement should smooth the path for quick flight licensing as regulators see that
SpaceX can still satisfy stringent safety requirements even after mission anomalies.
Indeed, the FAA has already spoken publicly.
A few days after Flight 9, the agency issued a statement acknowledging an anomaly and confirming
there were no injuries or property damage in Texas or in airspace and maritime zones.
That declaration, combined with SpaceX's own reminder that, as is standard for every test,
the area in the gulf containing the booster's flight path was cleared to prior launch, suggests
the regulatory response will be limited to routine debris surveys and any necessary environmental
assessments.
Beyond safety and regulation, Flight 9 also showcased significant technical strides.
Super Heavy's boostback burn was flawless, proving the team has mastered that complex
maneuver after two earlier hiccups.
All engines ignited and throttled as command, and the hot staging separation was captured
in breathtaking detail.
Elon Musk himself called it a great achievement by the SpaceX team.
Ship 35 overcame its ascent phase engine out tolerance for the first time and demonstrated
that its upgraded heat shield tiles can handle peak re-entry heating.
Each of these successes validates the incremental upgrades rolled out since Flight 7.
Yet, as so often in aerospace, every victory highlights the next set of challenges.
Flight 10 must carry forward the wins while eliminating the failures.
Musk's promise of a launch cadence of one flight every three to four weeks implies Flight
10 could lift off as soon as mid-June.
Already, B-16 and S-36 have passed multiple cryogenic tests and await static fire runs.
If their installations, checkouts, and pad transports proceed without delay, that timeline
is within reach.
But only if SpaceX resists the temptation to rush.
The work ahead is extensive.
Super Heavy must avoid a repeat of its landing burn explosion either by restoring the gentler
catch method on the tower or by refining steep angle water landings until the booster's
structure can reliably survive higher lateral loads.
Igniter systems will need extra insulation and perhaps redundant spark plug arrays to
guarantee re-ignitions.
Two engine final burns, tank pressure tests, and vibration dampening enhancements must
be validated before the next descent profile is attempted.
For Shift 36, the upper stage, the list is even longer.
Leaks in the main propellant tanks must be quelled by reinforced welds and secondary
containment shells.
Upgraded leak detection sensors have to be baked into every tank.
The aft flap needs both aerodynamic and thermal redesign, perhaps a smaller pivoting surface
with a metallic heat sink overlay, and more robust hinge protection.
The payload bay door mechanism must be simplified and stress-tested in cryogenic vacuum chambers
until its latches and actuators trigger flawlessly every time.
In space, engine relights must be demonstrated again and guidance software must be hardened
to respond adaptively to off-nominal conditions.
Yet even as SpaceX tackles these tasks, it must preserve the gains it has already achieved.
The flight readiness process around pad infrastructure, launch abort safety nuts, and real-time telemetry
pipelines are all critical to sustaining this rapid iteration.
Each test, each anomaly, each fix contributes to a growing knowledge base that will one
day make Starship's routine two-way reuse a reality.
As Flight 10 approaches, the question is not whether SpaceX can learn from Flight 9, because
it already has, but whether it can apply those lessons fast enough to maintain its
ambitious launch cadence without compromising safety or core mission objectives.
Each flight test isn't just a demonstration of raw power, it's a critical checkpoint
in SpaceX's long-term roadmap for reusability, deep space missions, and ultimately, human
settlement on other planets.
If Flight 10 lifts off in June as anticipated, it'll be a milestone in more ways than one.
Not only would it mark the first time since 2023 that Starship launches have occurred
in consecutive months, but it could also break the current record for fastest turnaround
between flights, currently 37 days, set between Flight 5 and 6.
This faster rhythm would showcase just how the program has matured in terms of vehicle
production, launch readiness, and post-flight data integration.
It's a bold indicator that SpaceX isn't just aiming for occasional success, but consistent
iterative progress.
But the stakes are higher than just a quicker tempo.
Every new test moves SpaceX closer to two highly anticipated milestones.
A super-heavy booster that returns safely to the launch tower under Mechazilla's mechanical
arms, and a Starship upper stage capable of controlled landings, whether on solid ground
or in the ocean for quick recovery.
Achieving these would be proof that full reusability is not just a concept, but a reality that's
within reach.
So as we look ahead, ask yourself, are you ready for Flight 10?
If you are, drop a comment saying, ready for 10!
Hit that like button as well and subscribe to our channel.
We're not just witnessing the future, we're living it!
Continuous improvement is our guiding star and with Flight 10 on the horizon, SpaceX
is about to take another exhilarating leap toward a multi-planetary future.
Now let's talk about Blue Origin's upcoming new Shepard flight.
On the 27th of May, the same day SpaceX launched Flight 9, Blue Origin announced that its next
crewed suborbital mission, NS32, will lift off on the 31st of May.
NS32 marks New Shepard's 32nd flight overall and its 12th mission carrying people.
The vehicle will launch from Blue Origin's West Texas site at 8.30am Central or 9.30am
Eastern, carrying six passengers on a roughly 10-12 minute journey that crosses the Karman
Line before returning under parachutes.
While each New Shepard flight brings excitement for the crewed tourism experience, these short
hops don't yet move the needle on Blue Origin's broader ambitions.
Their real test lies with New Glenn, the company's much larger two-stage rocket designed for
orbital missions.
After a successful maiden flight in January, Blue Origin's first orbital launch in its
nearly 25-year history, we've heard little about New Glenn's next launch.
If New Glenn remains grounded for months more, Blue Origin risks falling behind the rapid
cadence of other providers.
Orbital launchers are where the industry's future growth and revenue will be won.
New Shepard flights keep the brand in the headlines, but investors and observers alike
will be watching to see when New Glenn returns to the pad.
As NS32 prepares for liftoff, we'll be paying close attention not just to the smiling faces
aboard its capsule, but also to any clues Blue Origin offers about the timing of New
Glenn's second mission.
Until then, the clock is ticking.
Success comes from what we learn.
SpaceX lives by this after every flight, and it's exactly why they lead the industry.
Flight 9 just wrapped up, revealing fresh challenges and opportunities.
What fixes will SpaceX deploy to turn these lessons into future victories?
I trust you enjoyed the spectacle of Flight 9 on 27th.
Its successes gave us cause for celebration, even as its near-misses reminded us of the
work still ahead.
With Flight 9 behind us and Elon Musk vowing a launch cadence for the next three flights
– roughly one every three to four weeks – all eyes turn to Flight 10.
To prepare for that rapid rhythm, SpaceX must tackle the lingering issues revealed on Flight
9, ensuring each step forward stands on solid engineering foundations.
First, we return to Super Heavy.
B-14's dramatic end came during its landing burn, when an in-air explosion cut short its
ocean touchdown mere moments before success.
The culprit?
Flight data and post-mission analysis point squarely to the aggressive, high angle of
attack-descent profile that was being tested – an approach intended to conserve fuel,
but one that generated intense lateral loads on the booster's skin.
Those forces appear to have exceeded structural limits, allowing a fracture or separation
in the vehicle's primary structure, followed by rapid burn-through and detonation of residual
propellant.
Faced with this outcome, SpaceX leadership must decide how to balance performance gains
with hardware longevity and safety.
One path is to dial back the steep descent maneuvers in the near-term and return to the
proven catch approach using the tower's mechanical arms.
That method proved reliable in Flight 7, yielding an intact booster ready for rapid refurbishment.
By resuming tower captures for Flight 10, SpaceX safeguards ground infrastructure and
keeps the turnaround schedule on track, albeit without immediate fuel savings from steep
descents.
Alternatively, SpaceX could continue refining high angle profiles, but do so over water
to protect pad assets.
Conducting ocean landings for these tests would enable incremental increases in descent
aggressiveness while containing risk.
In that scenario, SpaceX might assign Flight 10's steep angle test to a reused booster,
most logically B-15, which flew once, or even a fresh booster to preserve flight-proven
hardware.
With each ocean trial, engineers would accumulate data to optimize descent guidance, control
algorithms, and structural reinforcements until the booster can reliably survive more
demanding approaches.
Both options offer merits.
Returning to tower catches ensures continuity and speed, while water-based steep descent
tests advance fuel efficiency research.
The decision will hinge on SpaceX's tolerance for risk, the status of ground refurbishment
workflows, and pad availability under a tightening launch cadence.
Whatever the choice, a clear plan must emerge weeks before Flight 10 so teams can modify
flight software, update procedural checklists, and schedule any required hardware upgrades.
Beyond the descent profile itself, Flight 9 exposed weaknesses in the engine ignition
system.
One sensor ring Raptor failed to relight during the landing burn just before the explosion.
Reigniting Raptor engines under cold fuel conditions after multiple engine cycles in
flight is one of Starship's more complex technical challenges.
Temperature extremes in the igniter lines, repeated thermal cycling, and mechanical stresses
from engine gimballing can degrade igniter performance.
To remedy this, SpaceX must build on the insulation and flow path enhancements introduced after
Flight 8, adding thicker thermal barriers around igniter assemblies and rerouting plumbing
away from hotspots.
A redundant ignition igniter, perhaps a small auxiliary spark plug system that can activate
if the primary mechanism falters, would provide a vital backup.
In the weeks before Flight 10, ground test teams should subject identical Raptors to
dozens of rapid-fire ignition cycles, replicating the exact temperature, vibration, and pressure
conditions of a full mission profile.
Automated test stands that cycle cold fuel through a stationary Raptor while capturing
every millisecond of pressure, temperature, and spark plug behavior will highlight the
circumstances under which reliability degrades.
Armed with that data, SpaceX can refine igniter recipes, select more heat-resistant materials,
and rewrite flight hardware to adapt ignition commands if sensors detect incipient failures.
In the longer term, the arrival of Raptor 3, a simplified refractory metal-rich design
promised to withstand harsher conditions, may prove the ultimate fix.
But in the immediate term, zeroing in on the current igniter will be paramount.
A further booster challenge is proving fault tolerance in landing scenarios.
SpaceX intends to test a two-engine final burn, cutting one of the three inner ring
engines to prove the booster can land safely even with an engine out.
That maneuver demands all three engines be scrupulously reliable.
Only by eliminating ignition uncertainty can the team risk shutting down one engine mid-descent.
For Flight 10, SpaceX may choose water landings to refine the two-engine burn first, then
graduate to a tower catch once confidence levels are high.
Each of these trials will push the booster closer to the day when a successful catch
for a fully-reused booster becomes routine.
While Super Heavy's fixes draw on data-rich booster tests, Ship 35's challenges are more
intricate.
On Flight 9, observers noted small fires on the vacuum engine fairing and the lower skirt,
areas already flagged during Flight 8.
Possible sources include exhaust impingement from raptor plumes, micro-leaks in pressurization
or hydraulic lines, or ignition of aerodynamic heater elements.
Though these flare-ups didn't immediately compromise flight safety, they highlight Starship's
vulnerability to stray flames and the need for improved thermal protection.
In the run-up to Flight 10, the team should install additional ablative or insulated cladding
around the skirt-to-engine junctions and consider channeling flame-resistant coatings
across the outer skin.
More ambitiously, embedded fire detection sensors linked to localized carbon dioxide
or water mist suppression nozzles could snuff out any spot fires before they widen.
The mass penalty will be minimal compared to the benefit of near-zero fire risk during
rapid reuse cycles.
Flight 9's most catastrophic failure for Ship 35 came after SECO during the unpowered
coast toward re-entry.
The vehicle's loss of orientation, followed by an uncontrolled spin, turned re-entry into
its harshest test yet.
Instead of presenting its designed windward heat shield, Ship 35 tumbled, exposing every
flank, especially the shield's latches, aft flaps, and structural joints, to searing plasma.
When communications briefly returned, cameras revealed an aft flap that had partially burned
away, a stark testament to the damage inflicted.
The violent spin induced massive vibrations that threatened plumbing, avionics racks,
and welding seams alike.
Diagnosing this, Musk pointed to a loss of main tank pressure.
A propellant leak had bled away ULICH gas or cryogenic fuel, dropping tank pressure
below the level required to feed engines and control thrusters.
Without those thrusters, Ship could not maintain attitude, and the tumble began.
Leaks in Starship's stainless steel tanks are notoriously tricky.
Welds must handle wide thermal swings from cryogenic chill to re-entry heat, and a single
pinhole can trigger a catastrophic spiral.
To close this vulnerability, SpaceX will need to enhance tank fabrication protocols.
That might involve double-seaming all major welds, coating external surfaces with a welded-on
metallic film to seal micro-fractures, or installing a secondary internal bladder designed
to spring into action if primary tank containment fails.
In parallel, a high-fidelity leak detection network combining pressure transducers, ultrasonic
leak sensors, and hull effect-based flow meters must report the smallest pressure loss instantly.
Onboard, autopilot logic can then trigger an emergency-safing sequence.
Reorient the ship, throttle back engines gently, or use attitude-control thrusters to maintain
heat shield forward orientation until a planned splashdown.
Beyond tank integrity, Ship 35's re-entry dynamics demand improved control authority.
Flight 9 highlighted that Starship's flaps, only its aerodynamic surfaces for hypersonic
guidance, can't counter uncontrolled spin once thrusters vanish.
Ship 35's failure to deploy its payload bay doors during Flight 9 adds another layer of
complexity.
Whether the root cause was a frozen actuator or a misaligned hinge, or perhaps even a flimsy
latch, payload deployment must be rock-solid for Starship to fulfill a promise as a multi-utility
vehicle, launching satellites, ferrying space station modules, or delivering lunar landers.
A redesign should aim for simplicity, fewer moving parts, redundant actuators, and fail-safe
latches that can be triggered by alternate commands or even manual pyrotechnic relief.
Ground rigs should cycle these doors hundreds or thousands of times in a thermal vacuum
environment, simulating the exact conditions they will face in orbit.
Beyond hardware fixes, the overarching theme for Flight 10 preparation is integrated testing.
SpaceX must mesh data from booster and ship flight telemetry with ground-based replicas,
running holistic simulations of the entire mission, from ignition through splashdown,
so that no system lives in isolation.
Flight software updates must incorporate new failure detection heuristics, enabling the
onboard computers to adapt real-time to developing anomalies, whether a tank leak or engine misfire
or an errant plasma strike.
Finally, all of these painstaking technical improvements must be matched by robust ground
operations.
A launch pace of one flight every 3-4 weeks leaves scant room for protracted investigations.
Post-flight inspection routines must be streamlined, using automated non-destructive evaluation
tools such as ultrasound scanners, thermographic cameras, and laser profilometers to certify
structural readiness within days.
Component swaps should happen via plug-and-play modules rather than labor-intensive rebuilds.
And the data from each flight must feed directly into AI-driven anomaly detection systems that
spot trends invisible to human eyes.
If SpaceX can nail these fixes – reinforcing tanks, perfecting igniters, optimizing flaps,
safeguarding against fires, ensuring payload deployment, and refining ground workflows
– then Flight 10 will stand not only as another star on Starship's record, but as
the moment when iterative learning propelled the program into an era of true rapid reusability.
So what do you think?
Which improvements matter most, and in what order should SpaceX tackle them?
Let us know in the comments section down below.
This has been Kevin with GreatSpaceX.
Thank you so much for watching and always remember, curiosity, imagination, and inspiration
will follow you so long as you keep looking up.