Engineering:STS-400

From HandWiki
STS-400
Endeavour at LC-39B for STS-400.jpg
Endeavour on standby at LC-39B, ready to rescue the crew of STS-125 if needed
Mission typeCrew rescue
Mission duration7 days
Spacecraft properties
SpacecraftSpace Shuttle Endeavour
Crew
Crew size4 up
11 down
MembersChristopher Ferguson
Eric A. Boe
Robert S. Kimbrough
Stephen G. Bowen
LandingScott D. Altman
Gregory C. Johnson
Michael T. Good
Megan McArthur
John M. Grunsfeld
Michael J. Massimino
Andrew J. Feustel
Orbital parameters
Reference systemGeocentric
RegimeLow Earth
Inclination28.5 degrees
Insignia STS-400.png
"Unofficial" Mission Emblem  
Comparison of International Space Station and Hubble Space Telescope orbits

STS-400 was the Space Shuttle contingency support (Launch On Need) flight that would have been launched using Space Shuttle Endeavour if a major problem occurred on Space Shuttle Atlantis during STS-125, the final Hubble Space Telescope servicing mission (HST SM-4).[1][2][3][4]

Due to the much lower orbital inclination of the HST compared to the ISS, the shuttle crew would have been unable to use the International Space Station as a "safe haven", and NASA would not have been able to follow the usual plan of recovering the crew with another shuttle at a later date.[3] Instead, NASA developed a plan to conduct a shuttle-to-shuttle rescue mission, similar to proposed rescue missions for pre-ISS flights.[3][5][6] The rescue mission would have been launched only three days after call-up and as early as seven days after the launch of STS-125, since the crew of Atlantis would only have about three weeks of consumables after launch.[2]

The mission was first rolled out in September 2008 to Launch Complex 39B two weeks after the STS-125 shuttle was rolled out to Launch Complex 39A, creating a rare scenario in which two shuttles were on launch pads at the same time.[3] In October 2008, however, STS-125 was delayed and rolled back to the VAB.

Initially, STS-125 was retargeted for no earlier than February 2009. This changed the STS-400 vehicle from Endeavour to Discovery. The mission was redesignated STS-401 due to the swap from Endeavour to Discovery. STS-125 was then delayed further, allowing Discovery mission STS-119 to fly beforehand. This resulted in the rescue mission reverting to Endeavour, and the STS-400 designation being reinstated.[4] In January, 2009, it was announced that NASA was evaluating conducting both launches from Complex 39A in order to avoid further delays to Ares I-X, which, at the time, was scheduled for launch from LC-39B in the September 2009 timeframe.[4] It was planned that after the STS-125 mission in October 2008, Launch Complex 39B would undergo the conversion for use in Project Constellation for the Ares I-X rocket.[4] Several of the members on the NASA mission management team said at the time (2009) that single-pad operations were possible, but the decision was made to use both pads.[2][3]

Crew

The crew assigned to this mission was a subset of the STS-126 crew:[2][7]

Position Launching Astronaut Landing Astronaut
Commander Christopher Ferguson
Pilot Eric A. Boe
Mission Specialist 1 Robert S. Kimbrough
Mission Specialist 2 Stephen G. Bowen
STS-125 Commander None Scott D. Altman
STS-125 Pilot None Gregory C. Johnson
STS-125
Mission Specialist 1
None Michael T. Good
STS-125
Mission Specialist 2
None Megan McArthur
STS-125
Mission Specialist 3
None John M. Grunsfeld
STS-125
Mission Specialist 4
None Michael J. Massimino
STS-125
Mission Specialist 5
None Andrew J. Feustel

Early mission plans

Atlantis (foreground) and Endeavour on LC-39A and LC-39B in 2008.

Three different concept mission plans were evaluated: The first would be to use a shuttle-to-shuttle docking, where the rescue shuttle docks with the damaged shuttle, by flying upside down and backwards, relative to the damaged shuttle.[6] It was unclear whether this would be practical, as the forward structure of either orbiter could collide with the payload bay of the other, resulting in damage to both orbiters. The second option that was evaluated, would be for the rescue orbiter to rendezvous with the damaged orbiter, and perform station-keeping while using its Remote Manipulator System (RMS) to transfer crew from the damaged orbiter. This mission plan would result in heavy fuel consumption. The third concept would be for the damaged orbiter to grapple the rescue orbiter using its RMS, eliminating the need for station-keeping.[7] The rescue orbiter would then transfer crew using its RMS, as in the second option, and would be more fuel efficient than the station-keeping option.[6]

The concept that was eventually decided upon was a modified version of the third concept. The rescue orbiter would use its RMS to grapple the end of the damaged orbiter's RMS.[1][8]

Preparations

Diagram showing one of the proposals for crew and equipment transfers during STS-400.

After its most recent mission (STS-123), Endeavour was taken to the Orbiter Processing Facility for routine maintenance. Following the maintenance, Endeavour was on stand-by for STS-326 which would have been flown in the case that STS-124 would not have been able to return to Earth safely. Stacking of the solid rocket boosters (SRB) began on 11 July 2008. One month later, the external tank arrived at KSC and was mated with the SRBs on 29 August 2008. Endeavour joined the stack on 12 September 2008 and was rolled out to Pad 39B one week later.

Since STS-126 launched before STS-125, Atlantis was rolled back to the VAB on 20 October, and Endeavour rolled around to Launch Pad 39A on 23 October. When it was time to launch STS-125, Atlantis rolled out to pad 39A.[4]

Mission plan

The Mission would not have included the extended heatshield inspection normally performed on flight day two.[1][3] Instead, an inspection would have been performed after the crew was rescued.[1][3] On flight day two, Endeavour would have performed the rendezvous and grapple with Atlantis.[1][7] On flight day three, the first EVA would have been performed.[1][3][7] During the first EVA, Megan McArthur, Andrew Feustel and John Grunsfeld would have set up a tether between the airlocks.[2][3] They would have also transferred a large size Extravehicular Mobility Unit (EMU) and, after McArthur had repressurized, transferred McArthur's EMU back to Atlantis. Afterwards they would have repressurized on Endeavour, ending flight day two activities.[1]

The final two EVA were planned for flight day three.[1][3] During the first, Grunsfeld would have depressurized on Endeavour in order to assist Gregory Johnson and Michael Massimino in transferring an EMU to Atlantis. He and Johnson would then repressurize on Endeavour, and Massimino would have gone back to Atlantis.[1] He, along with Scott Altman and Michael Good would have taken the rest of the equipment and themselves to Endeavour during the final EVA. They would have been standing by in case the RMS system should malfunction.[8] The damaged orbiter would have been commanded by the ground to deorbit and go through landing procedures over the Pacific, with the impact area being north of Hawaii.[2][3] On flight day five, Endeavour would have had a full heat shield inspection, and land on flight day eight.[1][2][3]

This mission could have marked the end of the Space Shuttle program, as it is considered unlikely that the program would have been able to continue with just two remaining orbiters, Discovery and Endeavour.[9]

On Thursday, 21 May 2009, NASA officially released Endeavour from the rescue mission, freeing the orbiter to begin processing for STS-127. This also allowed NASA to continue processing LC-39B for the upcoming Ares I-X launch, as during the stand-down period, NASA installed a new lightning protection system, similar to those found on the Atlas V and Delta IV pads, to protect the newer, taller Ares I rocket from lightning strikes.[10][11]

Emblem and Crew Patches

As a contingency mission, STS-400 was not given official support by NASA for the production of a crew patch or emblem. However artwork was created for use by the mission team as an unofficial emblem by Mike Okuda, who also illustrated the official patch of STS-125.[12]

As described by Paul F. Dye, Lead Flight Director of the mission, the emblem "adopts many of the elements seen in a rescue organization's patch - the square cross, bold letterers and border, and simple design. The idea is that the emblem instantly identifies the rescue organization in a crowd of others. In this case, the Shuttle outlines identify the purpose of our organization."[13] In addition, the emblem contains 11 stars, symbolizing the combined 11 crew-members who would return to earth onboard STS-400.

The first flight crew assigned to the mission created another, more humorous design depicting a St. Bernard with its traditional barrel of brandy replaced by the Hubble Space Telescope. The final flight crew though were unsatisfied with this as a crew patch, and contacted longtime NASA artist Tim Gagnon about creating a new one, but never formally approved a design before the mission was scrubbed.[14]

The first STS-400 flight crew's unofficial patch

See also

References

  1. 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 NASA Mission Operations Directorate (2 June 2008). "STS-400 Flight Plan". NASA. http://www.nasa.gov/centers/johnson/pdf/345918main_FLT_PLN_400_B.pdf. 
  2. 2.0 2.1 2.2 2.3 2.4 2.5 2.6 NASA (5 May 2009). "STS-400: Ready and Waiting". NASA. http://www.nasa.gov/audience/foreducators/sts400-ready-and-waiting.html. 
  3. 3.00 3.01 3.02 3.03 3.04 3.05 3.06 3.07 3.08 3.09 3.10 3.11 Atkinson, Nancy (17 April 2009). "The STS-400 Shuttle Rescue Mission Scenario". Universe Today. http://www.universetoday.com/2009/04/17/the-sts-400-shuttle-rescue-mission-scenario/. 
  4. 4.0 4.1 4.2 4.3 4.4 Bergin, Chris (19 January 2009). "STS-125/400 Single Pad option progress – aim to protect Ares I-X". NASASpaceflight.com. http://www.nasaspaceflight.com/2009/01/sts-125400-single-pad-option-progress-protect-ares-i-x/. 
  5. Bergin, Chris (9 May 2006). "Hubble Servicing Mission moves up". NASASpaceflight.com. http://www.nasaspaceflight.com/2006/05/hubble-servicing-mission-moves-up/. 
  6. 6.0 6.1 6.2 Copella, John (31 July 2007). "NASA Evaluates Rescue Options for Hubble Mission". NASASpaceflight.com. http://www.nasaspaceflight.com/2006/07/nasa-evaluates-rescue-options-for-hubble-mission/. 
  7. 7.0 7.1 7.2 7.3 NASA (9 September 2008). "STS-125 Mission Overview Briefing Materials". NASA. http://www.nasa.gov/mission_pages/shuttle/shuttlemissions/sts125/news/125_mission_overview.html. 
  8. 8.0 8.1 Bergin, Chris (11 October 2007). "STS-400 – NASA draws up their Hubble rescue plans". NASASpaceflight.com. http://www.nasaspaceflight.com/2007/10/sts-400-nasa-draws-up-their-hubble-rescue-plans/. 
  9. Watson, Traci (22 March 2005). "The mission NASA hopes won't happen". USA Today. https://www.usatoday.com/tech/science/space/2005-03-22-shuttle-cover_x.htm. 
  10. Harwood, William (21 May 2009). "Iffy weather forecast for Friday's shuttle landing". CBS News, Spaceflightnow.com. http://www.spaceflightnow.com/shuttle/sts125/090521fd11/index2.html. 
  11. Bergin, Chris (22 May 2009). "Endeavour in STS-127 flow". NASA Spaceflight.com. http://www.nasaspaceflight.com/2009/05/atlantis-sets-sights-saturday-endeavour-sts-127-flow/. 
  12. "Graphic artist on the final frontier: an interview with Mike Okuda". The Space Review. https://www.thespacereview.com/article/1215/2. 
  13. "STS-400 patches". NASAspaceflight. https://forum.nasaspaceflight.com/index.php?topic=14162.0. 
  14. "STS-400 (STS-125 LON) mission patches". collectspace. http://www.collectspace.com/ubb/Forum18/HTML/000593.html. 

External links

sv:STS-125#STS-400