Everyday Astronaut
@everydayastronaut.bsky.social
Hi it’s me Dim Todd the occasional cosmonaut.
FTS was not triggered (safed). The likely RUD cause, based on what is available, is an engine bay fire in the skirt attic tied to top-left RVAC failure. This fire may have spread, leading to the explosion and loss of control.
March 7, 2025 at 1:35 AM
FTS was not triggered (safed). The likely RUD cause, based on what is available, is an engine bay fire in the skirt attic tied to top-left RVAC failure. This fire may have spread, leading to the explosion and loss of control.
Launch control video suggests the top-left RVAC exploded, taking out the 3 center engines. A hot spot was seen at T+ 3:33 post-stage separation, hinting at early RVAC issues. Ship 34 yawed right at T+7:55, suggesting underperformance.
March 7, 2025 at 1:35 AM
Launch control video suggests the top-left RVAC exploded, taking out the 3 center engines. A hot spot was seen at T+ 3:33 post-stage separation, hinting at early RVAC issues. Ship 34 yawed right at T+7:55, suggesting underperformance.
Starship Ship 34 faced a RUD on Flight 8. Here whats known:
At T+8:04, a RVAC shut down prematurely, followed by all 3 Sea-Level Raptors, 1 sec later than last flight. Ship 34 then lost attitude control due to no gimbaling engines.
At T+8:04, a RVAC shut down prematurely, followed by all 3 Sea-Level Raptors, 1 sec later than last flight. Ship 34 then lost attitude control due to no gimbaling engines.
March 7, 2025 at 1:35 AM
Starship Ship 34 faced a RUD on Flight 8. Here whats known:
At T+8:04, a RVAC shut down prematurely, followed by all 3 Sea-Level Raptors, 1 sec later than last flight. Ship 34 then lost attitude control due to no gimbaling engines.
At T+8:04, a RVAC shut down prematurely, followed by all 3 Sea-Level Raptors, 1 sec later than last flight. Ship 34 then lost attitude control due to no gimbaling engines.