SpaceX made a Strange Turn on Ship 37 back on Pad Re-Test, But No Static Fire?

SpaceX made a Strange Turn on Ship 37 back on Pad Re-Test, But No Static Fire?
===
00:00: Intro
00:30: S37’s movement and its tests
04:16: Ship V3’s progress
06:28: Falcon 9’s Kuiper launching mission
09:21: Vulcan’s movement for launching
===
#greatspacex #elonmusk #spacex #nasa
==
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
Our video content is referenced by video sources at these sites:
https://www.space.com/space-exploration/launches-spacecraft/falcon-9-rocket-launches-amazon-project-kuiper-internet-satellites-spacex-100th-mission-2025
===
SpaceX made a Strange Turn on Ship 37 back on Pad Re-Test, But No Static Fire?
S37 continues its test campaign, though this round may be less extensive than expected.
Elsewhere, SpaceX has completed its Kuiper mission for rival Amazon, a major milestone this year. And Vulcan has finally rolled to the pad for launch after nearly a year of anticipation.
Let’s break it all down in today’s episode of Great SpaceX.
We are now in mid-August, with launch window announcements drawing near. Over the past week, preparations have accelerated for S37’s next phase of testing following its recent engine swap. Once the final checks were complete, SpaceX scheduled a road closure for the afternoon of August 11 to facilitate S37’s relocation.
By the morning of August 11, activity around Mega Bay 2 was in full swing. The Ship lifting jig was brought into the facility, while the transport stand was positioned at the bay entrance. Meanwhile, on the Pad-1 side, the crane departed Pad-1 and moved to Pad-2—likely to clear space for the transfer and upcoming test work. By midday, S37 emerged from Mega Bay 2. At the exact scheduled hour, the vehicle rolled to the launch pad, where it was immediately secured by the Chopsticks system.
SpaceX made a Strange Turn on Ship 37 back on Pad Re-Test, But No Static Fire?
Once in position, a series of crucial steps began. The stabiliser arms were activated, and the Ship testing interface was connected to the QD (quick-disconnect) point on the vehicle. The QD arm itself opened to allow for lifting operations. When all connections and safety checks were completed, S37 was lifted a second time to be mated with the new test platform—a process occurring roughly two weeks after the initial lift.
With this relocation, S37 now stands ready for its next round of testing. A beach closure has been scheduled from 4:00 p.m. on August 12 until 3:00 a.m. on August 13. The key question remains: what type of test is about to unfold?
SpaceX made a Strange Turn on Ship 37 back on Pad Re-Test, But No Static Fire?
Originally, the prevailing assumption was that SpaceX planned a static fire of S37’s newly installed vacuum engine. However, recent developments have cast doubt on that theory. A newly surfaced image shows that the vacuum engines currently installed lack stiffeners—structural supports that help prevent unwanted vibration or collision during high-stress tests. Without these stiffeners, it is unlikely that a static fire will occur.
Another clue lies in the unusual timing of the closures. Typically, a launch pad test involving a static fire would prompt a road closure from 7:00 a.m. to 7:00 p.m., allowing for daylight operations. This not only supports safer execution but also enables clear observation and photography—important for documentation and analysis. In contrast, the current closure window spans late afternoon through the early hours of the next morning. While the night setting might create a dramatic visual effect, it hampers detailed observation and recording, suggesting that the planned test may be less intense than a static fire.
----
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.