- \n
- STS-134 LIVE UPDATES<\/li>\n
- L2 STS-134 Special Section<\/li>\n
- Click here to Join L2<\/li>\n<\/ul>\n
Only two items of interest \u2013 both minor \u2013 were charged against Endeavour\u2019s ascent, both of which resolved by the time the MER had a chance to report them.<\/p>\n
\u201cAt 6 min 11 sec MET, the Space Shuttle Main Engine (SSME) -1 Low Pressure Fuel Turbopump (LPFTP) pressure Channel B instrumentation experienced a data drop-out for 0.1 sec. This caused the SSME controller to post a Failure Identifier (FID) and disqualify that measurement,\u201d added the Ascent summary report (a specific article, based on the expansive MER ascent report will follow later in the mission).<\/p>\n
\u201cThe SSME uses this transducer for the Liquid Hydrogen (LH2) flow-rate calculation on the center engine. It continued to use the Channel A pressure for that calculation. The FID did not affect any other SSME operation. This transducer is not used after Main Engine Cutoff (MECO). MECO occurred at 136\/13:04:49 GMT (00\/00:08:21MET).\u201d<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/05\/A76.jpg\" "\\"A7\\"")
The other issue \u2013 the Vernier R5D Chamber Pressure Tube Slow Pressure Decay \u2013 was observed when the R5D chamber pressure failed to drop to vacuum as expected during ascent, indicating a possible blockage in thruster or PC sense tube. However, upon first firing of R5D, the response was nominal with normal Pc response.<\/p>\nAt time of publishing, the MER had only listed five issues, ranging from a data transmission issue on the Right Nose Landing Gear (NLG) transducer to the Forward Event Timer error, which has since been resolved. MER presentations on the issues \u2013 available in L2\u2019s expansive STS-134 mission coverage sections \u2013 show all the issues are very minor and hold no mission impact.<\/p>\n
NASA mission updates
<\/path>Space Shuttle models <\/path>Spaceflight <\/path>\n (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n
STS-134 Specific Articles: http:\/\/www.nasaspaceflight.com\/tag\/sts-134\/<\/p>\n
Endeavour\u2019s TPS:<\/p>\n
Following the separation of Endeavour\u2019s External Tank (ET-122) \u2013 listed at 136\/13:05:10 GMT (00\/00:08:42 MET) \u2013 photography from the orbiter\u2019s umbilical well, along with handheld photography, was downlinked to the Damage Assessment Team (DAT) in Houston.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/05\/A313.jpg\" "\\"A3\\"")
The high quality imagery (bulk dump in L2) provided post-ascent data on the state of what is known as the \u201cKatrina Tank\u201d \u2013 due to its return to the launch manifest after damage sustained during the hurricane of 2005 was repaired. The imagery shows the tank performed like a champ.<\/p>\nOnly five minor foam liberations have been tracked back to observations on the separated tank, with small mass foam losses seen in areas such as the Ice Frost Ramps (IFRs), a remarkable achievement given ET-122 did not receive the full set of Return To Flight (RTF) modifications during its fabrication at the Michoud Assembly Facility (MAF) in New Orleans.<\/p>\n
As noted by Mission Management Team (MMT) chair LeRoy Cain, the tank \u201cexceeded expectations by quite a bit,\u201d based on the routine pre-launch risk assessments.<\/p>\n
With the payload bay doors opened at 136\/14:26:29 GMT (00\/01:30:01 MET), and the Ku-Band antenna deployed, along with a self-test being completed with satisfactory results, the crew also carried out a survey of the exposed cargo bay and OMS Pods.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/05\/A411.jpg\" "\\"A4\\"")
The checks on the Pods allow for early observations of protruding gap fillers, cracked tiles or torn stitching on the blankets. The latter issue required a special EVA repair during Atlantis\u2019 STS-117 mission, which resulted in ground processing mitigation procedures being put into place.<\/p>\nAs with all recent flights, the imagery shows the OMS Pods are in excellent condition, with no items of interest being noted by the DAT engineers at this time.<\/p>\n
It\u2019ll be a few more days before the DAT can inform the MMT Endeavour is cleared from any further inspections, via what is known as a Focused Inspection (FI), as ascent data, crew photography and the imagery gathered from the main focus of Flight Day 2 \u2013 the inspections using the Orbiter Boom Sensor System (OBSS) \u2013 are fully reviewed on the ground.<\/p>\n
So far, FD2\u2019s scans have raised no flags with the DAT engineers, as they reported their latest findings to the MMT late in the flight day.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/05\/A66.jpg\" "\\"A6\\"")
\u201cReview of FD2 scans is continuing \u2013 no reportable damage,\u201d noted the DAT status on the MMT presentation for Flight Day 2 (L2). \u201cPort and Starboard T0 Inspection complete. OMS Pods complete \u2013 both LE and acreage with no blanket\/gap filler protrusions or reportable tile damages.\u201d<\/p>\nOnly one mark on one RCC panel was noted, which was a \u201cnature related\u201d observation, pre-launch.<\/p>\n
With the OBSS scans focusing on the Port and Starboard Reinforced Carbon Carbon (RCC), Nose cap and Thermal Protection System (TPS) in the path of the pre-defined map of Endeavour\u2019s Heatshield, the only DAT note of interest related to the partial coverage of Starboard regions 2-4.<\/p>\n
However, that data will be refined via the Flight Day 3, as Endeavour was put through a series of burns, highlighted by the Terminal Initiation burn (TI) at 2:37am Central, to begin final approach to the ISS. The TI burn, which makes final course adjustments to the orbiter\u2019s approach to the ISS, placed Endeavour and her crew on the proper heading to reach a point 600-feet \u201cbelow\u201d the Space Station along the R-bar.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/05\/A3241.jpg\" "\\"A324\\"")
Once on the R-bar, Mission Control gave Endeavour\u2019s crew the go ahead to perform the 360-degree R-bar Pitch Maneuver, or RPM, at 4:14am Central \u2013 to allow the flight crew aboard the International Space Station to conduct a photographic survey of the orbiter\u2019s TPS, including her belly.<\/p>\nWhen the always-stunning maneuver was completed, Endeavour was commanded to perform the TORVO (Twice Orbital Rate V-bar Approach) maneuver to take her from the R-bar to the V-bar (Velocity bar) directly in front of the Space Station\u2019s line of travel.<\/p>\n
Once properly aligned within the docking cone, Endeavour\u2019s thrusters were pulsed to reduce the orbiter\u2019s speed by two-tenths of a foot per second, effectively slowing the vehicle and allowing the ISS to \u201ccatch up\u201d with the visiting spacecraft.<\/p>\n
Following docking, timed at 5:14am Central, hard seal was confirmed and air leak checks performed between Endeavour\u2019s Orbiter Docking System (ODS) and the Pressurized Mating Adaptor (PMA). This was followed by the crew of Endeavour ingressing the ISS for the traditional crew greeting.<\/p>\n
A safety briefing with the newly arrived crew was conducted, as Flight Day 3 movedtowards the next milestone, involving robotics and Endeavour\u2019s ELC-3 payload. This operation was successfully completed.<\/p>\n
Further updates will follow, with this article being updated during the key events.<\/p>\n
(All images via L2. Extensive coverage is being provided on the news site, forum and L2 special sections \u2013 the latter of which is the world\u2019s best front row seat to Shuttle missions. With specific and extensive flight day coverage, from interactive \u201cone stop\u201d FD live coverage in the open forum, to internal documentation, photos, videos and content in the specific L2 FD areas).<\/p>\n","protected":false},"excerpt":{"rendered":"
In another historic milestone for Endeavour\u2019s final flight, the fleet\u2019s youngest orbiter chased down the International Space Station (ISS) to kick start the docked phase of the STS-134 mission. Endeavour arrived in superb shape, with the Mission Management Team (MMT) only having to review a handful of very minor issues, following an extremely clean ascent to […]<\/p>\n","protected":false},"author":1,"featured_media":29542,"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":[233,3366],"class_list":["post-40451","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-iss","tag-sts-134"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40451"}],"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=40451"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40451\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/29542"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=40451"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=40451"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=40451"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}