A small leak was discovered in a propellant line for space shuttle Discovery’s orbital maneuvering system engines. The leak was found at a flange located at the interface where two propellant lines meet in the shuttle’s aft compartment. The line carries a propellant called monomethyl hydrazine, one of two chemicals used to ignite the 6,000-pound thrust engines seen on either side of the shuttle’s tail above the three main engines. <\/p>\n
Engineers and technicians working on Discovery at Launch Pad 39A at NASA’s Kennedy Space Center in Florida will tighten the six bolts around the suspect flange and re-evaluate for leaks. If that doesn’t work, the propellants already inside the tanks will be pumped out and technicians will replace its primary and secondary seals.<\/p>\n
The processing schedule could allow the two seals to be replaced without delaying Discovery’s targeted launch on Nov. 1. Space Shuttle Program managers, however, are careful about making sure any potential fixes are indeed successful before pressing ahead with a countdown.<\/p>\n","protected":false},"excerpt":{"rendered":"
A small leak was discovered in a propellant line for space shuttle Discovery’s orbital maneuvering system engines. The leak was found at a flange located at the interface where two propellant lines meet in the shuttle’s aft compartment. The line carries a propellant called monomethyl hydrazine, one of two chemicals used to ignite the 6,000-pound thrust engines seen on either side of the shuttle’s tail above the three main engines. <\/p>\n
Engineers and technicians working on Discovery at Launch Pad 39A at NASA’s Kennedy Space Center in Florida will tighten the six bolts around the suspect flange and re-evaluate for leaks. If that doesn’t work, the propellants already inside the tanks will be pumped out and technicians will replace its primary and secondary seals.<\/p>\n
The processing schedule could allow the two seals to be replaced without delaying Discovery’s targeted launch on Nov. 1. Space Shuttle Program managers, however, are careful about making sure any potential fixes are indeed successful before pressing ahead with a countdown.<\/p>\n","protected":false},"author":26,"featured_media":612598,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"class_list":["post-58322","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-shuttle-update"],"_links":{"self":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/58322","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=58322"}],"version-history":[{"count":0,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/58322\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/media\/612598"}],"wp:attachment":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=58322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=58322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=58322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}