- \n
- STS-135 LIVE Updates<\/li>\n
- L2 STS-135 Section<\/li>\n
- Click here to Join L2<\/li>\n<\/ul>\n
GPC-3 returned to action via the IPL (Initial Program Load) and dump tasks \u2013 an effective reload of software into the computer \u2013 during the early part of Flight Day 4.<\/p>\n
Commander Ferguson spent 45 minutes transferring data from the troublesome computer into GPC-2 \u2013 aided by Ground Control (GG) in the Shuttle Flight Control Room (FCR) bypassing an expected period of Loss Of Signal (LOS) by working with with assets at White Sands in New Mexico \u2013 before being told he could return to his sleep period.<\/p>\n
The crew were then informed they would be awoken 30 minutes later than scheduled on Flight Day 8 due to the interruption.<\/p>\n
Updating the latest status of the investigation into the GPC issue, ISS Orbit 3 Flight Director Courtenay McMillan noted more information will be known when the crew begin trobleshooting during the first half of Flight Day 8.<\/p>\n
Space Shuttle
<\/path>Technology News <\/path>Spaceflight news subscription <\/path>\n (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n
\u201cWe don\u2019t know if there will be any impact (to the mission) yet. First thing in the morning there will be some troubleshooting to gain some data and see if we can recover the computer.\u201d<\/p>\n
Around eight hours of transfer time will be lost during the troubleshooting, according to FD McMillan \u2013 although the crew was already 15 hours ahead of the mission schedule.<\/p>\n
However, the troubleshooting did not take long, wih GPC-4 successfully reloaded within a few hours and appears to be stable, as a root cause is evaluated (documentation on L2).<\/p>\n
STS-135 Specific Articles: http:\/\/www.nasaspaceflight.com\/tag\/sts-135\/<\/p>\n
TPS clearance overview:<\/p>\n
Following an as-always impressive review of launch day imagery, Flight Day 2 (FD-2) TPS inspections of Atlantis via the Orbiter Boom Sensor System (OBSS), FD-2 Hi-Res photography of Atlantis\u2019s OMS pods, and FD-3 R-bar Pitch Maneuver (RPM) photography of Atlantis\u2019s underbelly TPS tiles, the Damage Assessment Team (DAT) have completed their extremely thorough review of Atlantis and cleared her for reentry into Earth\u2019s atmosphere.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A328.jpg\" "\\"A3\\"")
With only 5 \u2013 yes, count them ONLY 5 \u2013 TPS notes, Atlantis\/STS-135 will stand in history as being tied with sister Discovery as the second-cleanest orbiter to ever reach orbit: an honor she reached on STS-132 last year with only 4 areas of TPS damage \u2013 same as STS-131\/Discovery.<\/p>\nThe honor of \u201ccleanest\u201d post-launch orbiter in the history of the Space Shuttle Program goes to Endeavour. She made it to orbit on STS-130 with only 3, yes THREE, TPS notes and absolutely NO lower-surface, underbelly TPS tile scuffs, dings, or scrapes.<\/p>\n
For Atlantis and STS-135, the DAT identified three (3) FI insulating blanket frays on the port OMS pod, one FI blanket fray on the forward -Y star tracker, and ONLY one underbelly TPS tile damage location.<\/p>\n
Launch pad cameras also captured the liberation of one AMES Gap Filler ~3seconds after liftoff from LC-39A last Friday.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A173.jpg\" "\\"A17\\"")
On orbit RPM photography of Atlantis by the ISS crew also confirmed mechanical and sensor evidence that both of Atlantis\u2019s ET umbilical doors are properly closed and a good thermal seal present.<\/p>\nVerification of closure of the two ET doors gives this system a PERFECT record throughout the 135 flight history of the Space Shuttle Program.<\/p>\n
Even more impressive here is that not only has the ET door closure system worked exactly as designed every single time, but that each and every Shuttle flight crew has undergone training for a contingency EVA to manually close the doors via a spacewalk underneath the Shuttle orbiter in the event that these doors ever failed to close properly.<\/p>\n
Atlantis DAT review:<\/p>\n
To begin their superb TPS clearance review, the DAT reviewed their characterization of the one TPS tile damage (more of a scuff) location.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A412.jpg\" "\\"A4\\"")
As noted by the FD-5 TPS DAT Review presentation, available for download on L2\u2019s dedicated STS-135 documentation database, \u201cAnalysis Dimensions: 2.49\u2033 L x 0.40\u2033 W.\u201d<\/p>\nFurther analysis showed the cavity more than acceptable for reentry \u2013 with a total damage area assessed at 2.5\u2033L x 0.5\u2033W x 0.84\u2033D. Total tile thickness on the affected tile is 1.16\u2033.<\/p>\n
Nominal heating on this tile and its underlying structure is expected during reentry, and all aligned and cross-flow case evaluations will remain strongly positive.<\/p>\n
Cross-flow case evaluations revealed a conservatively estimated max 263-degree F temperature in the area. The max temp allowed is 350-degrees F.<\/p>\n
Thus, this area will not be any concern during reentry next Thursday (July 21).<\/p>\n
The remaining four areas of interest for the DAT team were all thermal insulation blankets on the upper surfaces of Atlantis.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A610.jpg\" "\\"A6\\"")
The only one of these blanket areas not located on the left OMS pod was on the nose of Atlantis near her -Y star tracker.<\/p>\n\u201cFrayed C\/P Blanket Forward of -Y Star Tracker,\u201d notes the DAT presentation.<\/p>\n
The damage dimensions are 2.59\u2033L and ~1.13\u2033H. Total blanket thickness is 0.75\u2033 thick, and the blanket is an original build blanket making its first flight.<\/p>\n
The damage itself is between two previous stitch and coat repairs. Furthermore, the blanket was built to withstand the spreading of fray damage with quality stitches every inch.<\/p>\n
The fray has caused no loss of thermal protection characteristics, and ascent heat loads are significantly higher than entry loads on this area of the vehicle.<\/p>\n
No material liberation is expected during reentry, and the area is cleared for entry.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A79.jpg\" "\\"A7\\"")
The final three locations of interest were all on the port OMS pod, the first of which being the V070-396377-103 blanket.<\/p>\nInstalled on December 19, 2006 during OPF flow processing for STS-117, the blanket is making its 6th flight on Atlantis. The blanket itself is 0.92\u2033 thick.<\/p>\n
The blanket edges in this area are stitched together to account for loose OML fabric, and \u2013 like the star tracker blanket \u2013 the blanket is designed to prevent the spread of a blanket tear.<\/p>\n
Ascent heating loads in this area are \u201csignificantly higher\u201d than entry loads. There are no thermal protection loses because of the blanket deformation.<\/p>\n
No material loss is expected during reentry.<\/p>\n
For background on the FI blankets, \u201csleeving stitching is used for reinforcing blanket attachment to vehicle. Sleeving securely attached and will not liberate,\u201d notes the STS-135 TPS clearance presentation.<\/p>\n
Thus, there is no loss of thermal protection from \u201cloose\u201d stitching.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A87.jpg\" "\\"A8\\"")
The fourth TPS area examined by DAT was a \u201csmall fray\/protrusion\u201d on the V070-396377-029 blanket.<\/p>\nTotal blanket thickness is 1.26\u2033, and the damaged area is approximately 1.3\u2033L x 0.9\u2033H.<\/p>\n
The blanket was installed on September 16, 2010 and is making its first flight on Atlantis.<\/p>\n
The presentation notes for this blanket include a reference to \u201c1 MR to accept chart recorder data for 4 hours \u2013 s\/b 8hours. Hands on evaluation verified no bond anomalies.\u201d<\/p>\n
Again, the design of the blanket prevents the propagation of the fray, and all thermal limits are well maintained.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A94.jpg\" "\\"A9\\"")
The fifth and final TPS area looked at by the DAT was located right next to an APU exhaust vent on the port-side of Atlantis near her Vertical Stabilizer.<\/p>\nThe blanket here was observed to be protruding and frayed near the \u201caft hole reinforcement sleeving \u2018donut.’\u201d<\/p>\n
The blanket, which is 0.75\u2033 thick, was installed on July 23, 1999 and is making its 21st flight with Atlantis.<\/p>\n
Based on turnaround flow documentation from STS-129 to STS-132, the DAT found that the blanket had damage to its \u201cdesign stitches and perimeter fabric,\u201d and that this damage was \u201crepaired with additional stitching and C-9 coating.\u201d<\/p>\n
The sleeving stitching is \u201cused for reinforcing blanket cutout for penetration hole.\u201d<\/p>\n
The blanket is still firmly attached to Atlantis and will not liberate during entry and landing ops next week.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A102.jpg\" "\\"A10\\"")
The final TPS item reviewed by the DAT, but not included in the five TPS damage location number, was an AMES Gap Filler liberation event at approximately 3 seconds after liftoff from LC-39A last Friday.<\/p>\n\u201cIdentified as protruding ~3 seconds post launch (V070-191011-131 \/ -132),\u201d notes the TPS DAT presentation.<\/p>\n
The gap filler was making its 12th flight on Atlantis and was installed for \u201cout of tolerance gap of 0.085 inches.\u201d<\/p>\n
Assessments show that there is no risk of increased heating in this area during reentry.<\/p>\n
Thus, all six TPS areas were reviewed by the DAT, and all areas were unanimously recommended for clearance for entry. The Orbiter Project Office reviewed this information and concurred with the assessment to clear the TPS for entry.<\/p>\n
The MMT reviewed this data as well and formally cleared the TPS for entry.<\/p>\n
Atlantis Trivia:\n<\/p>\n
Three of Atlantis\u2019s four STS-135 crew members made their rookie flights aboard Atlantis: Chris Ferguson (STS-115), Sandy Magnus (STS-112), and Rex Walheim (STS-110).<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A1110.jpg\" "\\"A11\\"")
All three of Rex Walheim\u2019s flights have been aboard the Atlantis: STS-110, STS-122, and STS-135. With this, Rex Walhiem has actually been a member of two of Atlantis\u2019s three \u201cfinal\u201d trips to the ISS: STS-122 and STS-135.<\/p>\nSandy Magnus, with her flight on Atlantis\/STS-135, is only the third astronaut to fly on all three orbiters (Discovery, Atlantis, and Endeavour) in the post-Columbia timeframe: STS-126\/Endeavour (up to ISS), STS-119 (down from ISS), STS-135 (Atlantis).<\/p>\n
Steven Bowen (STS-126\/Endeavour, STS-132\/Atlantis, and STS-133\/Discovery) and Garret Reisman (STS-123\/Endeavour up to Station, STS-124\/Discovery down from Station, and STS-132\/Atlantis) are the other two astronauts to have flown aboard all three orbiters in the post-Columbia era.<\/p>\n
Atlantis is the only Shuttle orbiter to have had more than one \u201cpenultimate\u201d and \u201cfinal\u201d flight.<\/p>\n
Her \u201cpenultimate\u201d flights \u2013 at the time they were flown and with the addition of STS-135 \u2013 are STS-122, STS-129, and STS-132.<\/p>\n
Her first-last flight was STS-132. Her final-last flight is STS-135.<\/p>\n
Atlantis is the ONLY Space Shuttle orbiter to have never suffered a post-SSME (Space Shuttle Main Engine) start RSLS (redundant Set Launch Sequence) pad abort.<\/p>\n
The five post-SSME start RSLS aborts in the Space Shuttle Program were: STS-41D (maiden voyage of Discovery in June 1984 at T-6.4secs), STS-51F (Challenger in July 1985 at T-3secs), STS-55 (Columbia in March 1993 at T-3secs), STS-51 (Discovery in August 1993 at T-3secs), and STS-68 (Endeavour in August 1994 at T-1.9secs).<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A143.jpg\" "\\"A14\\"")
Finishing her career tied with Discovery as the second-cleanest TPS orbiter ever, it is also notable that Atlantis is also the most TPS damaged orbiter to safely return to Earth.<\/p>\nDuring her STS-27 mission in December 1988, standard post-launch imagery review revealed that portions of ablative insulation on the right hand Solid Rocket Booster (SRB) nose cone had liberated 85 seconds after liftoff and impacted the right hand side of the Atlantis, causing significant TPS damage.<\/p>\n
From the images transmitted during the mission, it was determined that the damage was no more severe than on previous missions.<\/p>\n
Upon landing on December 6, 1988, over 700 TPS tiles were found to be damage, and one tile was completely missing.<\/p>\n
Luckily, and perhaps the only thing that prevented a burn through at the area of the missing TPS tile and the loss of Atlantis and her flight crew was the fact that the missing tile was located over a dense aluminum mounting plate for the L-band antenna \u2013 which provided some degree of \u201cadded\u201d protection against a burn through.<\/p>\n
Additionally, on the occasion of Atlantis\u2019s real final flight, she has become the only Space Shuttle orbiter to carry an iPhone (smart phone) into orbit \u2013 thus linking the most complex machine ever built (the Shuttle orbiter) with a new generation of hand-held computing technology.<\/p>\n
To read about Atlantis and her sisters \u2013 from birth, processing, every single mission, through to retirement, click here for the links:
\nhttp:\/\/forum.nasaspaceflight.com\/index.php?topic=25837.0<\/p>\n(Images: Via L2 content, L2\u2019s 600mb STS-135 400mm, 800mm, and 1000mm hi res photo collection \u2013 and NASA.gov. Further articles on STS-135 will be produced during and after her mission, driven by L2\u2032s STS-135 Special Section which is following the mission at MMT\/MER level, surrounded by a wealth of FRR\/PRCB\/MER\/MMT and SSP documentation\/pressentations, videos, images and more.<\/p>\n
(As with all recent missions, L2 is providing full exclusive level mission coverage, available no where else on the internet. To join L2, click here: http:\/\/www.nasaspaceflight.com\/l2\/)<\/p>\n","protected":false},"excerpt":{"rendered":"
A master alarm onboard Atlantis woke the crew from their sleep, after a General Purpose Computer (GPC-4) suffered a problem. The issue follows the failure \u2013 and subsequent recovery \u2013 of GPC-3 earlier in the mission. Meanwhile, the Damage Assessment Team (DAT) provided their full review of the orbiter\u2019s Thermal Protection System (TPS), which has […]<\/p>\n","protected":false},"author":1,"featured_media":29576,"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":[9171,3659,7935],"class_list":["post-40384","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-dat","tag-sts-135","tag-tps"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40384"}],"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=40384"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40384\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/29576"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=40384"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=40384"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=40384"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}