- \n
- STS-132 Live Coverage<\/li>\n
- L2 STS-132 Section<\/li>\n
- Click here to Join L2<\/li>\n<\/ul>\n
\u201cNew IPR 0036 to APU (Auxiliary Power Unit). During Auxiliary Power Unit (APU)1 GN2 pressurization, QD (Quick Disconnect) MD12 Airborne Half Coupler (AHC) failed leak check and the GN2 tank pressure increased. The QD was cycled 3 times, and leak rate improved enough that APU pressurization was able to continue.<\/p>\n
\u201cNew IPR 132V-0037 to OMS\/RCS. During post Forward Reaction Control System (FRCS) fuel load, QD MD121 was leaking internally. An extended decay check on the QD was performed which verified the AHC leak rate was acceptable. FRCS fuel load was continued.\u201d<\/p>\n
A previous IPR (0029) \u2013 related to troubleshooting on a Partial Pressure Oxygen (PPO2) sensor C \u2013 ruled out the amplifier and sensor as culprits for the failure to calibrate. As such, troubleshooting results remain under evaluation.<\/p>\n
Space tourism guides
<\/path>SpaceX launch tickets <\/path>Space Shuttle <\/path>\n (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n
The main aim of the flow this week is to prepare for Launch Countdown operations, known as S0007. Despite only one contingency day available in the flow, engineers remain on track to hit their target, allowing for the first launch attempt to take place on May 14.<\/p>\n
STS-132 Specific Articles: http:\/\/www.nasaspaceflight.com\/tag\/sts-132\/<\/p>\n
\u201cS5009 Ordnance Installation completed. The vehicle is powered up and personnel are being cleared from the pad for post ordnance installation testing. Orbiter Aft closeout continues. Door installation for flight is planned for Friday,\u201d added NTD processing information.<\/p>\n
\u201cPayload Bay Doors were re-opened to support bulb seal repair which is complete less 72 hour cure. Latch guide installation started today and will be finished after ordnance installation. Remote Manipulator System (RMS) elbow camera installation has been rescheduled.<\/p>\n
\u201cS0007 Launch countdown preps are in work and will continue through the week.\u201d<\/p>\n
Agency FRR:<\/p>\n
STS-132\u2019s Agency (SOMD) FRR is not expected to have any major talking points, thanks for the smooth flow of what is currently Atlantis\u2019 final mission on the schedule. With all departmental FRRs now complete, the Agency FRR will set the launch date, ahead of follow-on reviews by the Mission Management Team (MMT).<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/05\/A3.jpg\" "\\"A3\\"")
\u201cAgency FRR charts are due for the FRR on Wednesday that starts at 8:00 a.m. ET. The MMT pre-brief and STS-131 debrief (were conducted on Tuesday),\u201d noted the KSC Integration manager on the latest Shuttle Standup\/Integration report (L2), which included a late note on Atlantis\u2019 Californian landing option.<\/p>\n\u201cAt Edwards (Dryden Flight Research Center), the main runways are back up. The Air Force will transition Ops over next weekend. Have both the Microwave Scanning Beam Landing Systems (MSBLSs) on 22 left and 04 right up and certified to support STS-132.\u201d<\/p>\n
As with all FRRs, the previous mission\u2019s IFAs (In Flight Anomalies) make up a large part of the discussions, resulting in Discovery\u2019s Ku-Band failure \u2013 and plans for any re-occurrence with Atlantis \u2013 being added to the meeting.<\/p>\n
\u201cOn the Ku-band failure, the robotics instructors have tagged up with future crews to offer additional training for the docked inspection,\u201d noted Flight Operations on the Standup report. \u201cFeedback from the crews is that they feel they have been adequately trained and are in good shape should there be another failure.\u201d<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/05\/A54.jpg\" "\\"A54\\"")
Charged as Discovery\u2019s fourth IPR for her STS-133 flow, troubleshooting on her Ku-band hardware began shortly after she arrived back into the Orbiter Processing Facility (OPF-3), following the conclusion of STS-131.<\/p>\n\u201cIPR-0004 Ku Band troubleshooting is Complete to Date. Ku band is still not functioning properly. Engineering is evaluating. More troubleshooting will follow,\u201d noted the opening set of processing notes on the evaluations.<\/p>\n
\u201cKu Band troubleshooting is complete to date. Verified that the 156 MHz reference signal was good going into the Deployed Assembly (DA). Signal was steady and had a good level. Tentative plan is to replace the DA.\u201d<\/p>\n
Over the weekend, engineers were planning to replace the DA on Discovery\u2019s Ku-Band system, although this operation is currently on hold pending a decision on which spare DA will be installed on the veteran orbiter.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/05\/A45.jpg\" "\\"A45\\"")
\u201cThe Ku-Band removed from OV-103 (Discovery) was received at the (Lab) Saturday morning. The team worked through the weekend troubleshooting. Isolated the failure to a Q6 transistor on harmonic phase comparator on the same exciter with the DEA. It was isolated to the DEA,\u201d added KSC Logistics on the Standup report.<\/p>\n\u201cThat data will be turned over to the Engineering team for additional troubleshooting.\u201d<\/p>\n
\u201cThe last Ku failure was STS-92, and was a Q5 transistor. Was a different location, but the same transistor,\u201d added the Orbiter Project Office (OPO) on the Standup report, who also referred to another ongoing topic for FRR discussion \u2013 the small ceramic inserts that have become a liberation issue during recent flights.<\/p>\n
\u201cThe team working the SICB (Safety Integration Control Board) and ceramic inserts are working long hours and putting in a lot of overtime. Pulling a story together this quickly is impressive. Kudos to that team; they are doing an amazing job.\u201d<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/05\/A422.jpg\" "\\"A422\\"")
Given previous discussions ahead of STS-131, this topic is very unlikely to be a problem for the FRR. However, further actions have been noted via the inspection and replacement procedures, while flight history continues to play a positive role in easing concerns relating to potential liberations from the Payload Bay Door hinges.<\/p>\nWith all areas of liberation, potential impacts to downstream hardware is a concern that remains under constant evaluation.<\/p>\n
\u201cMore discussion to come on window fasteners since STS-131 post-flight inspections determined one missing plug on window 6 and two protruding plugs on windows 5 and 6,\u201d added pre-FRR notes (L2) from MOD\u2019s 8th Floor (L2).<\/p>\n
\u201cPlan is to inspect and reinstall all plugs that have potential to come loose. As discussed prior to STS-131, the payload bay hinge line locations are not accessible at the pad. Only one plug has been liberated in our flight history \u2013 occurred on base of vertical tail (two other occurrences of loss of the insert\/plug which is different failure mode).\u201d<\/p>\n
With the Rudder Speed Brake (RSB) tile liberation during STS-131\u2019s launch also cleared via reviews, Space Shuttle Program (SSP) manager John Shannon noted his pride for his teams, referencing Associate Administrator for Space Operations) Bill Gerstenmaier\u2019s acceptance speech at a recent award ceremony.<\/p>\n
\u201cThe National Space Trophy was won by Bill Gerstenmaier. In his acceptance speech, he thanked the Space Shuttle team effusively for how much this team has done over the last several years to keep the Program on track and operating as safely as we have been. He really meant that,\u201d noted Mr Shannon on the Standup report.<\/p>\n
\u201cThe team is doing an amazing job of getting all of the issues turned around and all of the proper discussions. We are rolling into next week in good shape (Mr Shannon) agreed with the kudos. There was lots of good feedback on how great this team is doing. Keep it up, and we will see most of you down in Florida (for the FRR).\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"
NASA and contractor managers will set STS-132\u2019s launch date during the Agency level Flight Readiness Review (FRR) on Wednesday. No major issues have been noted, while Atlantis continues to behave on Pad 39A, raising the likelihood May 14 will be set as the launch date. Meanwhile, engineers have pinpointed the cause of Discovery\u2019s Ku-band system […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[3610,3485],"class_list":["post-40788","post","type-post","status-publish","format-standard","hentry","category-news","tag-frr","tag-sts-132"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40788"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=40788"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40788\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=40788"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=40788"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=40788"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}