Wow! SpaceX Loaded S40 onto the Forte vessel & Began Return to Starbase! B21’s Test Scrub due to… === #greatspacex#elonmusk#spacex#nasa == 00:00 Hot menu for you 01:00 S40 was loaded onto the recovery vessel 04:23 B21’s test abort & reason 06:49 Chang’e 7’s delay 09:05 ULA’s new CEO === 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 === Wow! SpaceX Loaded S40 onto the Forte vessel & Began Return to Starbase! B21’s Test Scrub due to… SpaceX has finally made a major breakthrough in S40’s recovery, but at Starbase, the road to Starship Flight 14 has hit another unexpected obstacle. After spending 32 days in the Indian Ocean, S40 has been lifted from the water and loaded onto the Forte, officially beginning its long journey back to Starbase. Meanwhile, B21’s static-fire test was scrubbed, raising new questions about SpaceX’s preparations for Flight 14. In this video, we will: Wow! SpaceX Loaded S40 onto the Forte vessel & Began Return to Starbase! B21’s Test Scrub due to… How did SpaceX successfully load S40 onto the Forte after more than a month at sea? What happened during the S40 recovery operation, and how will the vehicle return to Starbase? Why was the B21 static-fire test scrubbed, and could the LOX system be responsible? How could the B21 delay affect the schedule and final preparations for Starship Flight 14? Why has China delayed the Chang’e 7 lunar mission, and what does it mean for China’s lunar ambitions? Who is Mark Peller, ULA’s new CEO, and can he help restore Vulcan after its extended grounding? Wow! SpaceX Loaded S40 onto the Forte vessel & Began Return to Starbase! B21’s Test Scrub due to… S40’s return is an extraordinary chapter in the Starship program, while B21’s testing could become a critical milestone before Flight 14. At the same time, developments surrounding Chang’e 7 and United Launch Alliance show just how quickly the global space industry is changing. For the latest SpaceX Starship Flight 14 updates, S40 recovery news, B21 testing, NASA developments, and major aerospace stories, stay tuned to Great SpaceX. Do you think SpaceX can complete B21’s static fire in time for Flight 14? Share your thoughts and comment “Success first” to show your support to SpaceX team.
SpaceX has successfully recovered the S-40 Starship from the Indian Ocean using the heavy-lift vessel Forte. Meanwhile, preparations for Flight 14 face a setback with the scrubbing of B-21's static fire. Additionally, China's Chang'e 7 lunar mission is delayed due to weather, and United Launch Alliance has appointed Mark Peller as its new CEO.
Good news, everyone. After more than a month at sea, S-40 has finally been lifted from the water and secured above the Forte.
Officially beginning its long journey back to Starbase, and the way SpaceX pulled off this recovery is nothing short of impressive.
But while S-40 is finally on its way, things at Starbase haven't been nearly as smooth.
B-21's static fire attempt has been scrubbed, adding another complication to the already tight preparations for Flight 14.
So, what went wrong? And how could this setback affect the next Starship launch?
We'll break it all down, but that's not all.
We also have two major stories from across the space industry. A significant delay to China's Chang'e 7 lunar mission, and
a major leadership change at United Launch Alliance.
So, let's dive into all the latest developments on today's episode of Great SpaceX.
You know, I read the comments on our S-40 update the other day,
and I'm really glad to see that you're still following its journey and supporting its return.
So, if you haven't already, make sure you subscribe to the channel to receive the latest updates on SpaceX and the aerospace industry.
And, if you missed a notification because you were busy or because of a notification issue, just head directly to our channel.
We publish new videos daily, so there's always something new to discover.
And now, here's a gift for you. In the latest update, S-40 has officially left the water and been loaded onto the recovery vessel
Forte at Pescalis. The operation took place during the day on August 26th, local time,
which would have been the night of August 25th in our time zone. And honestly,
it's an impressive sight. The recovery method was almost exactly what ChromeKiwi predicted in the 3D simulation
we discussed in the previous video. As mentioned, Forte is a semi-submersible
heavy lift vessel, capable of lowering its cargo deck approximately 13 meters below the water's surface.
And that's exactly what happened. Nearby footage shows Forte submerging its cargo deck while approaching S-40.
The vessel then connected to S-40 using two lines. One line was attached between S-40's nosecone and the vessel's control room,
while the other connected the aft section of S-40 to one of Forte's two buoyancy casings. With those connections secured,
S-40 could be towed toward the submerged cargo deck. Before the operation,
several yellow retaining pins had been installed on the deck to help keep S-40 from rolling during the loading process.
The vehicle was then carefully aligned on the water's surface until it was positioned directly above the cargo deck.
And once everything was in place, Forte began to rise. As the vessel resurfaced,
S-40 was lifted out of the water and settled onto the deck, where it could be secured to the anchors.
It was a remarkably clever recovery method. Rather than requiring enormous cranes to lift a massive starship directly out of the ocean,
Forte essentially positioned itself underneath the vehicle and lifted it by raising its own deck.
And that marks a major milestone in S-40's extraordinary journey. After 32 days, or approximately
774 hours since splashing down in the Indian Ocean,
S-40 has finally left the water. Its journey has been almost as dramatic as the flight itself. For more than a month,
the vehicle was exposed to salt water, rough waves, storms, and the harsh marine environment.
The conditions were severe enough that even one of S-40's forward flaps was lost.
But now, S-40 has entered a completely new phase.
It's still far from home,
but at least it's no longer sitting in the ocean. On the recovery vessel, S-40 is better protected and much easier for engineers to inspect.
They can now directly examine the vehicle and potentially learn how it survived splashdown in more than a month at sea.
That data could be incredibly valuable for future starships.
Meanwhile, Forte will prepare for the next and much longer leg of the journey.
The big question now is which route S-40 will take back to Starbase. The two most practical
options appear to be around the Cape of Good Hope or through the Panama Canal.
We'll have to wait and see which route SpaceX chooses.
But for now, there's one thing worth celebrating.
After 32 days in the ocean, S-40 is finally out of the water.
Its journey home has officially entered a new chapter.
Now, let's head back to Starbase where the road to Flight 14 continues. At this point,
all eyes are on B-21 and its static fire test.
After being transported to the launch site on the morning of August 25th,
B-21 was immediately lifted onto the OLM.
At the time, the beach closure schedule indicated a two day testing window on August 26th
and the 27th, with August 26th listed as the primary date.
And when that time arrived, it looked like the test preparations were finally underway.
The tank farm activated produced strong venting as SpaceX began what appeared to be the vehicle
and ground system conditioning needed before propellant loading.
At the same time, the booster transport stand departed the launch site, which was another
sign that SpaceX was preparing for an intensive test.
But then nothing happened and things became even more interesting when the liquid oxygen
BQD was disconnected from the vehicle while the rest of the setup remained intact.
Then came the abort.
A new beach closure schedule was subsequently announced, moving the primary testing dates
to August 27th and the 28th.
So the B-21 static fire had officially been scrubbed.
The booster transport stand also returned to its base.
But the biggest question is, why was the test scrubbed?
The biggest clue is the disconnected liquid oxygen BQD, suggesting the issue may have
involved the liquid oxygen plumbing, BQD interface or tank farm equipment.
Whatever the cause, SpaceX couldn't proceed with propellant loading as planned.
And without a fully loaded vehicle, there can be no static fire.
The return of the booster transport stand to the launch site is also interesting.
SpaceX could use it to lift B-21 off the OLM, giving workers better access to the BQD and
surrounding hardware for repairs.
If that's the plan, it could take a day or more, which may explain why August 27th and
the 28th are now primary test dates.
We still don't know the exact cause, but hopefully it's a straightforward issue that
can be resolved quickly.
The sooner B-21 completes its static fire, the more time SpaceX will have for inspections
and Final Flight 14 preparations, especially if September 15th remains the target.
So yes, the scrub is disappointing.
But with Starship, success has to come before speed.
Let's hope B-21 gets back on track quickly.
If you agree, comment success first down below.
Next, let's turn to a major delay affecting Chang'e 7, China's flagship lunar mission.
Chang'e 7 is part of China's highly ambitious lunar exploration program, and if it had been
launched as planned, it would have been one of the year's most significant lunar missions.
But now, weather has thrown the entire schedule into uncertainty.
Chang'e 7 was originally scheduled to launch on the 23rd from the Wanchang Space Launch
Site on Hainan Island.
Then Tropical Depression Nangka began developing in the Gulf of Tonkin, just west of Hainan.
With the weather deteriorating, Chinese officials were forced to delay the launch.
Initially, the target was simply moved back by one day to August 24th.
But that window also became impossible.
Eventually, the launch was postponed indefinitely and the rocket was returned to its factory.
The state-run Xinhua News Agency reported on the 23rd, citing the China Manned Space
Agency, China's Chang'e 7 lunar probe does not meet launch conditions and its launch
therefore cannot take place during the planned window this year.
And that's where things become complicated.
Chang'e 7 can't simply launch whenever the weather improves.
The mission depends on a precise Earth-Moon alignment, creating a limited launch window.
Some reports suggest a September launch is still possible, while others point to 2027.
For now, China hasn't provided a definitive timeline.
Whenever it launches, though, Chang'e 7 will be worth watching.
The mission includes an orbiter and lander, with the lander targeting the moon's south
polar region.
A possible destination is near Shackleton Crater, although the final site hasn't been
confirmed.
That's an extremely important region because permanently shadowed craters may contain
significant deposits of water ice.
Chang'e 7 will investigate those resources using a rover and a hopping robot designed
to explore the difficult terrain.
And lunar water could eventually become far more than a scientific discovery.
It could support life support systems and potentially be converted into hydrogen and
oxygen for rocket fuel.
That's why Chang'e 7 matters beyond a single robotic mission.
It's another step toward China's long-term lunar ambitions and another challenge for
the United States, NASA, and SpaceX to keep pace.
And now let's turn to the latest update on ULA's leadership.
It's safe to say that after Torrey Bruno's departure, the company gradually lost some
of the attention it once commanded within the aerospace community.
ULA needed a new leader capable of guiding the company into its next phase.
And now that person has emerged.
The United Launch Alliance has named Mark Peller, a longtime ULA manager and executive,
as its new president and chief executive officer.
ULA announced on the 17th that Peller had been promoted to the position effective
immediately. He had previously served as the company's chief operating officer and
succeeds John Elbin, who had been serving as interim CEO since December.
Elbin had already planned to retire from ULA after eight years as chief operating
officer, with Peller originally expected to succeed him.
However, when longtime CEO Torrey Bruno unexpectedly left the company, Elbin stepped
in as interim chief executive.
According to ULA board members Kay Sears, the company selected Peller after a months
long process that considered both internal and external candidates.
She said Mark's background, coupled with his extensive knowledge of both ULA's business
and technical offerings, make him the best candidate to fill the CEO position.
And Peller certainly has the experience.
He has spent more than 35 years working at ULA and its predecessor companies.
His career began in 1990 when he joined Rockwell International as a propulsion
engineer working on the space shuttle program.
After Boeing acquired Rockwell's space business in 1996, Peller moved into Boeing's
Delta launch vehicle programs the following year.
Then in 2006, Boeing and Lockheed Martin combined their launch vehicle operations to
create ULA.
Peller went on to become chief engineer for the Delta two and four programs.
Later, he served as ULA's senior vice president for Vulcan and advanced programs before
becoming chief operating officer last December.
Now he has inherited a company facing some serious challenges.
Peller said, I am honored to take on this role, leading a truly amazing team of people
and appreciate the confidence the board has in me.
He also emphasized ULA's long history of national security and exploration missions
while expressing confidence in Vulcan's future.
But Vulcan is currently one of ULA's biggest challenges.
ULA had targeted 16 to 18 Vulcan launches in 2026, but its first launch suffered a
performance anomaly involving one of its four solid rocket boosters.
Although the mission succeeded, Vulcan hasn't flown since.
The prolonged grounding has also created financial pressure, with Lockheed Martin and
Boeing providing loan guarantees totaling hundreds of millions of dollars.
And even after the booster issue is resolved, another concern remains.
Vulcan uses Blue Origin's BE-4 engines, which also power New Glenn.
Blue Origin recently traced an explosion during a New Glenn static fire test to a liquid
oxygen valve in the BE-4 and said it was making modifications to the component.
So, Peller takes over ULA at a difficult moment, facing a grounded Vulcan, financial
pressure, engine concerns, and increasingly aggressive competition.
Now, we'll see whether his experience can help ULA overcome these challenges and
finally unlock Vulcan's full potential.
In any case, folks, if you enjoyed today's episode, don't forget to leave a like,
subscribe to GreatSpaceX, and ring the notification bell so you never miss the
latest updates on Starship, SpaceX, and humanity's exciting journey into the
future of space exploration.
Thanks for watching and we'll see you in the next one.