#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.
=======
SpaceX Booster 7 31 engines Firing instead of 33, Musk’s Reaction….
1)HUGE THANKS TO:
2) 🎵 ABOUT ALL TRACK IN MY VIDEO 🎵
Artist: Infraction – No Copyright Music
The Doctor
3) SOURCES OF IMAGES AND VIDEOS
Kevin Randolph:
LabPadre:
Ezekiel Overstreet:
Emil Romano
StarshipGazer:
Cosmic Perspective:
Ryan Hansen Space:
Robossbomb:
C-bass Productions :
Andrew:
Matthew Cable:
Evan Karen:
iamVisual:
Alexander Svan:
3D_ Daniel:
=====
SpaceX Booster 7 31 engines Firing instead of 33, Musk’s Reaction….
Wow wow, after years of preparatory work, this finally happened!!!
SpaceX just attempted to ignite all 33 engines in a test fire of its gargantuan Super Heavy rocket booster. The trial marks the biggest company “static fire” test for what is expected to be the most powerful launch vehicle ever built.
However, you may know or not, B7 only got 31 engines firing instead of 33.
Why? Will that number of engines be enough for Starship to have an orbital mission?
This is the real reason explained by Elon Musk.
SpaceX’s Starship rocket has survived the most powerful static fire test in the history of rocketry.
Yeah, it’s still standing on the launch pad!!! Congrats to SpaceX’s team.
According to CEO Elon Musk, Super Heavy Booster 7 (B7) ultimately ignited 31 of its 33 Raptor engines. One engine was manually disabled “just before” the static fire, while the other faulty engine automatically shut down while attempting to ignite. The other 31 Raptors, however, completed a “full duration” static fire that lasted about five seconds.
Musk says that even with two engines disabled, those that remained were “still enough…to reach orbit” – an excellent result despite the static fire’s imperfections.
SpaceX Booster 7 31 engines Firing instead of 33, Musk’s Reaction….
—-
We use images and content in accordance with the YouTube Fair Use copyright guidelines:
Any questions about copyright please send us via Gmail: [email protected]
To be resolved, thank you.
