- \n
- STS-131 LIVE UPDATES<\/li>\n
- L2 STS-131 Special Section<\/li>\n
- Click here to Join L2<\/li>\n<\/ul>\n
\u201cHPU (Hydraulic Power Unit) carts were transferred from the Hyper Fuel Farm and lifted to the zero-level of the MLP (Mobile Launch Platform) on 3rd shift Friday morning. Due to conflicting resources, the Pad-A GH2 recharge is now rescheduled for next Wednesday, March 10th.<\/p>\n
\u201cWeekend Work: SSME Frequency Response Test and Helium Signature Test. S0024 Hypergolic servicing preps.\u201d<\/p>\n
With departmental FRRs already concluding, the results will make up what is usually a two day SSP FRR at the Johnson Space Center (JSC) in Houston \u2013 although STS-130\u2019s SSP FRR only took up a day, thanks to a lack of issues from the previous flight, STS-129.<\/p>\n
A similar situation for STS-131\u2019s SSP FRR appears likely, with STS-130\u2019s IFA (In Flight Anomaly) review at the PRCB (Program Requirements Control Board) on Thursday showing only three IFAs for the entire mission \u2013 with no issues of note for Endeavour herself.<\/p>\n
Space Shuttle models
<\/path>SpaceX launch tickets <\/path>Space Shuttle <\/path>\n (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n
STS-131 Specific Articles: http:\/\/www.nasaspaceflight.com\/tag\/sts-131\/<\/p>\n
\u201cThe STS-131 SSP FRR is March 10 and 11. Charts are due Monday. Special topics are due by (Friday). The STS-130 MMT (Mission Management Team) Debrief will be scheduled toward the end of the month,\u201d noted the latest Shuttle Standup\/Integration report on L2.<\/p>\n
\u201cInputs for the debrief are due by Friday to see if a stand alone debrief is needed; otherwise it will be combined with a pre-brief for STS-131. Had a successful pre-FRR. Had three integrated IFAs that will be bringing forward to be dispositioned.\u201d<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/03\/A35.jpg\" "\\"A3\\"")
The large Orbiter Project Office (OPO) only found one item of interest during their departmental FRR for STS-131, relating to inspections that are to be carried out on Discovery at the pad \u2013 following the STS-130 observation of Endeavour\u2019s left hand outboard elevon flipper door sliding seal protrusion, and the protruding window insert.<\/p>\n\u201cHad FRR with OPO. Have a little bit of open work left on OV-103 (Discovery) out at the Pad,\u201d added OPO via the Standup report. \u201cStill a little more to do with flipper door inspection with regards to the seal that came up during the last flight, and also a little more ceramic insert inspection to be done. Will have Chits in the system to do both of these.\u201d<\/p>\n
Other items that will highlight the FRR will be the External Tank, specific to the foam liberations from the intertank region.<\/p>\n
STS-132 Processing Latest:<\/p>\n
Atlantis\u2019 final \u201cscheduled\u2019 mission \u2013 STS-132 \u2013 continues to work towards a May 14 launch date, with evaluations on ET-136\u2019s intertank foam also set to take place shortly in the Vehicle Assembly Building (VAB) High Bay 2 (HB-2) via plug\/pull tests.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/03\/A45.jpg\" "\\"A4\\"")
\u201cIn the VAB, got ET-136 offloaded and put into the HB-2 checkout cell. Will pick up with test and checkout activities,\u201d noted processing information. \u201cET-136 (VAB HB-2 East) Shakedown\/Receiving inspections continue. GUCP (Ground Umbilical Carrier Plate) and LO2\/LH2 checkout preps continue.<\/p>\n\u201cWill talk the ET-136 intertank foam bond adhesion testing (plug\/pull tests) that needs to be done. Will discuss options. SSP (Space Shuttle Program Manager) Mr. (John) Shannon added that since going away from platforms to a cherry picker cleaning, it must be decided whether the same plug pattern is appropriate.\u201d<\/p>\n
The change from platforms to mechanical lifters relates to the process of cleaning the intertank structure during processing towards foam application at the Michoud Assembly Facility (MAF). It is believed that the root cause for the liberations during ascent is caused by dust contamination, with the old platforms obstructing the proper removal of the offending dust.<\/p>\n
A lack of intertank foam loss during ET-136\u2019s ascent will confirm the root cause and the aforementioned solution.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/03\/A54.jpg\" "\\"A5\\"")
The primary payload for STS-132 is the Russian Mini-Research Module 1 (MRM-1) and Integrated Cargo Carrier \u2013 Vertical Lightweight Deployable (ICC-VLD) pallet, with baseline evaluations continuing as per normal. Already noted is a Change Request (CR) relating to the mission duration.<\/p>\n\u201cProcessed the STS-132 CR for mission duration to 12+0 (days); went outside the board,\u201d noted Flight Operations and Integration on the Standup report.<\/p>\n
Processing of Atlantis continues to go well, following the installation of her three SSMEs and the start of booster stacking operations inside the VAB.<\/p>\n
\u201cOV-104 (STS-132) Got the clearance to start engine leak checks. Working base heat shield installation. Continuing installation of lower LESS carrier panels above the right and left wings,\u201d noted Ground Operations. \u201cIn HB-1, will be picking up with SRB stacking, with the left aft booster going up.<\/p>\n
\u201cOrbiter: OV-104 (OPF Bay 1): Orbiter closeouts for rollout to VAB will be started Friday. Weekend Work: ECLSS (Environmental Control and Life Support System) GN2 servicing, SSME and TPS (Thermal Protection System) work.<\/p>\n
\u201cBI-143 \/ RSRM 111 (VAB HB-1): Left Aft Booster stacking is complete. Right Aft Booster stacking is scheduled for Friday.\u201d<\/p>\n
STS-134 Processing Latest:<\/p>\n
From a processing standpoint, all is proceeding to plan with Endeavour, following her return from STS-130. Preparations for STS-134 are taking place, as engineers work towards the removal of her three SSMEs \u2013 which will begin on Monday.<\/p>\n
\u201cThermography on the WLE (Wing Leading Edge) has been completed, and is in data review. Working engine removal preps. Picked up with checkout of the FRCS (Forward Reaction Control System). Continuing with post-flight window inspections,\u201d outlined an overview from Ground Operations.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/03\/A62.jpg\" "\\"A6\\"")
\u201cWorking on OV-105 (Endeavour) post-flight STS-130,\u201d added SSME contractor Pratt & Whitney Rocketdyne, via the Standup report. \u201cWill be working Saturday on engine removal preps, so that engine removal can start first thing Monday morning.<\/p>\n\u201cIt takes around three shifts to get those engines back in the Engine Shop. The first activity in the Engine Shop will be running the normal nozzle tube leak checks.\u201d<\/p>\n
One issue \u2013 or Interim Problem Report (IPR) \u2013 is continuing to be worked during nominal flow operations, relating to a payload bay door centerline latch limit switch noted as off when should be on.<\/p>\n
\u201cIPR-03 troubleshooting continues; the team performed bore scope inspection on the LH and RH (Left and Right Hand) PLBD (Payload Bay Door) shear pins,\u201d the NTD reported. \u201cTroubleshooting results are under engineering evaluation.<\/p>\n
\u201cRCC (Reinforced Carbon Carbon) Thermography completed Friday. FRCS functional checkout is complete. OBSS (Orbiter Boom Sensor System) removal Friday. Weekend Work: SSME removal preps. Fuel cells 1, 2 & 3 work.\u201d<\/p>\n
Potentially Large STS-134 Delay:<\/p>\n
STS-134 currently has a launch date of July 29. However, memos started to circulate earlier this week requesting inputs from team leaders on the potential impacts of swapping the mission order, by allowing STS-133 to launch ahead of Endeavour\u2019s mission.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2010\/03\/A72.jpg\" "\\"A7\\"")
Further memos on Friday informed managers to attend a program level meeting next Monday, due to the potential of a \u201csignificant\u201d delay to STS-134, relating to problems during the testing of Endeavour\u2019s payload \u2013 the Alpha Magnetic Spectrometer (AMS).<\/p>\n\u201cConducting a quick look assessment of the impacts of flying STS-133\/ULF5 prior to 134\/ULF6. This option is being looked at due to problems that have been encountered with the AMS payload during testing (planned to fly on ULF6),\u201d noted one of several memos that are being collated in L2 ahead of Monday\u2019s meeting.<\/p>\n
\u201cIt is not clear at this point how significant a delay will result from these AMS problems, but the Program wants to look at our options before too much time passes and it becomes too late to consider a swap.\u201d<\/p>\n
A full review of the situation will be published after Monday\u2019s meeting in order to gain full details of the problem, and the potential length of the delay \u2013 although one memo intimated a slip of several months, while some sources claim it could be as serious as slipping well into 2011. NASA managers do hold flexibility in the schedule to move a flight into the first quarter of 2011 \u2013 if required.<\/p>\n
Ironically, the potential slip to STS-134 comes at a time when lawmakers are pushing for a large extension to the shuttle\u2019s operational lifetime, a drive which was acknowledged \u2013 at least by way of asking his teams to remained focus on the job in hand \u2013 by Mr Shannon.<\/p>\n
\u201cThere are many stories in the news, as there always are. This time it seems they are more focused on our team (SSP). The best thing we can do is to continue to operate excellently as we have been, keep putting together outstanding vehicles with no problems in flight, and keep hitting our launch windows,\u201d Mr Shannon added to the Standup report.<\/p>\n
\u201cThe team has been doing a wonderful job of that. We just need to keep it up, and keep our heads down, and we will see where the country wants this team to go.\u201d<\/p>\n
L2 members<\/em> <\/em>: Documentation \u2013 from which the above article has quoted snippets \u2013 is available in full in the related L2 sections, now over 4500 gbs in size<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
No major topics are expected at next week\u2019s Space Shuttle Program (SSP) Flight Readiness Review (FRR), as Discovery continues to push towards her April 5 launch date. Processing is also proceeding well for May\u2019s STS-132 flight with Atlantis, although Endeavour\u2019s STS-134 mission is subject to program level meetings \u2013 starting next Monday \u2013 due a […]<\/p>\n","protected":false},"author":1,"featured_media":29523,"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":[9184,3485,3366],"class_list":["post-40850","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-sts-131","tag-sts-132","tag-sts-134"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40850"}],"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=40850"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40850\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/29523"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=40850"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=40850"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=40850"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}