notes, though, a few issues popped up just as the team was finishing up the fueling process on Monday afternoon. They discovered a hydrogen leak and had to find options to seal it after their first solution didn't work. Plus, the flare stack, which burns excess liquid hydrogen from the rocket, caused a small fire in the grassy area around the launch site.
In the end, the launch controllers came up with a plan to mask data associated with the leak so as not trigger a hold by the launch computer. That wouldn't fly in a real launch scenario, but they wanted to get as far into the countdown as possible to gather the data they need. They were successfully able to resume the 10-minute final launch countdown after an extended hold and got to T-29 seconds before they had to end the test completely.
Regardless, they successfully performed several critical operations needed for launch during the test, including handing over control from the ground launch sequencer to the automated launch sequencer controlled by the rocket's flight software.
How is having to stop short and not finish the test as well as also having to implement a work around to ignore an issue you could never launch with a 'success'?
United States Latest News, United States Headlines
Similar News:You can also read news stories similar to this one that we have collected from other news sources.
Source: DigitalTrends - 🏆 95. / 65 Read more »
Source: ksatnews - 🏆 442. / 53 Read more »
Source: IntEngineering - 🏆 287. / 63 Read more »
Source: physorg_com - 🏆 388. / 55 Read more »
Source: IntEngineering - 🏆 287. / 63 Read more »
Source: BGR - 🏆 234. / 63 Read more »