STS-3xx

The orbiter and four of the crew which were due to fly the next planned mission would be retasked to the rescue mission. The planning and training processes for a rescue flight would allow NASA to launch the mission within a period of 40 days of its being called up. During that time the damaged (or disabled) shuttle's crew would have to take refuge on the International Space Station (ISS). The ISS is able to support both crews for around 80 days, with oxygen supply being the limiting factor.^[1] Within NASA, this plan for maintaining the shuttle crew at the ISS is known as Contingency Shuttle Crew Support (CSCS) operations.^[2] Up to STS-121 all rescue missions were to be designated STS-300.

In the case of an abort to orbit, where the shuttle could have been unable to reach the ISS orbit and the thermal protection system inspections suggested that the shuttle could not have returned to Earth safely, the ISS may have been capable of descending to meet the shuttle. Such a procedure was known as a joint underspeed recovery.^[3]

* – originally scheduled to be Endeavour, changed to Discovery for contamination issues.^[7]

To save weight, and to allow the combined crews of both shuttles to return to Earth safely, many shortcuts would have to be made, and the risks of launching another orbiter without resolving the failure which caused the previous orbiter to become disabled would have to be faced.

A number of pieces of Launch on Need flight hardware were built in preparation for a rescue mission including:

• An extra three recumbent seats to be located in the aft middeck (ditch area)
• Two handholds located on the starboard wall of the ditch area
• Individual Cooling Units mounting provisions
• Seat 5 modification to properly secure in a recumbent position
• Mounting provisions for four additional Sky Genie egress devices (see picture)

   

• Escape Pole mounting provisions for three additional lanyards^[8]

The Remote Control Orbiter (RCO), also known as the Autonomous Orbiter Rapid Prototype (AORP), was a term used by NASA to describe a shuttle that could perform entry and landing without a human crew on board via remote control. NASA developed the RCO in-flight maintenance (IFM) cable to extend existing auto-land capabilities of the shuttle to allow remaining tasks to be completed from the ground. The purpose of the RCO IFM cable was to provide an electrical signal connection between the Ground Command Interface Logic (GCIL) and the flight deck panel switches. The cable is approximately 28 feet (8.5 m) long, weighs over 5 lb (2.3 kg), and has 16 connectors.^[9][10] With this system, signals could be sent from the Mission Control Center to the unmanned shuttle to control the following systems:

• Auxiliary Power Unit (APU) start and run
• Air Data Probe (ADP) deployment
• Main Landing Gear (MLG) arming and deployment
• Drag chute arming and deployment
• Fuel cell reactant valve closure

The RCO IFM cable first flew aboard STS-121 and was transferred to the ISS for storage during the mission. The cable remained aboard the ISS until the end of the Shuttle program. Prior to STS-121 the plan was for the damaged shuttle to be abandoned and allowed to burn up on reentry. The prime landing site for an RCO orbiter would be Vandenberg Air Force Base in California.^[11] Edwards Air Force Base, a site already used to support shuttle landings, was the prime RCO landing site for the first missions carrying the equipment; however Vandenberg was later selected as the prime site as it is nearer the coast, and the shuttle can be ditched in the Pacific should a problem develop that would make landing dangerous. White Sands Missile Range in New Mexico is a likely alternate site.^[12] A major consideration in determining the landing site would be the desire to perform a high-risk re-entry far away from populated areas. The flight resource book, and flight rules in force during STS-121 suggest that the damaged shuttle would reenter on a trajectory such that if it should break up, it would do so with debris landing in the South Pacific Ocean.^[2]

The Soviet Buran shuttle was also remotely controlled during its entire maiden flight without a crew aboard. Landing was carried out by an onboard, automatic system.^[13]

As of March 2011 the Boeing X-37 extended duration robotic spaceplane has demonstrated autonomous orbital flight, reentry and landing.^[14][15] The X-37 was originally intended for launch from the Shuttle payload bay, but following the Columbia disaster, it was launched in a shrouded configuration on an Atlas V.

Had a LON mission been required, a timeline would have been developed similar to the following:

• FD-10 A decision on the requirement for Contingency Shuttle Crew Support (CSCS) is expected by flight day 10 of a nominal mission.
• FD-10 Shortly after the need for CSCS operations a group C powerdown of the shuttle will take place.
• FD-11→21 During flight days 11–21 of the mission the shuttle will remain docked to the international space station (ISS) with the hatch open. Various items will be transferred between the shuttle and ISS.
• FD-21 Hatch closure will be conducted from the ISS side. The shuttle crew remains on the ISS, leaving the shuttle unmanned
• FD-21 Deorbit burn – burn occurs four hours after separation. Orbiter lands at Vandenberg Air Force Base under remote control from Houston. (Prior to STS-121, the payload bay doors would have been left open to promote vehicle breakup.)
• FD-45 Launch of rescue flight. 35 days from call-up to launch for the rescue flight is a best estimate of the minimum time it will take before a rescue flight is launched.^[16]
• FD-45→47 The rescue flight catches up with the ISS, conducting heat shield inspections en route.
• FD-47 The rescue flight docks with the station, on day three of its mission.
• FD-48 Shuttle crew enters the rescue orbiter. Vehicle with a crew complement of 11 undocks from ISS.
• FD-49 Rescue orbiter re-enters atmosphere over Indian or Pacific Ocean for landing at either Kennedy Space Center or Edwards Air Force Base. A Russian Progress resupply spacecraft is launched at later date to resupply ISS crew. ISS precautionary de-crew preparations begin.
• FD-58 De-crew ISS due to ECLSS O₂ exhaustion in event Progress unable to perform resupply function.

 

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).^{[17][18][19][20]}

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.^[19] Instead, NASA developed a plan to conduct a shuttle-to-shuttle rescue mission, similar to proposed rescue missions for pre-ISS flights.^[19][21][22] 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.^[18]

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.^[19] 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.^[20] 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.^[20] 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.^[20] 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.^[18][19]

The crew assigned to this mission was a subset of the STS-126 crew:^[18][23]

 

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.^[22] 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.^[23] 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.^[22]

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.^[17][24]

 

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.^[20]

The Mission would not have included the extended heatshield inspection normally performed on flight day two.^[17][19] Instead, an inspection would have been performed after the crew was rescued.^[17][19] On flight day two, Endeavour would have performed the rendezvous and grapple with Atlantis.^[17][23] On flight day three, the first EVA would have been performed.^[17][19][23] During the first EVA, Megan McArthur, Andrew Feustel and John Grunsfeld would have set up a tether between the airlocks.^[18][19] 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.^[17]

The final two EVA were planned for flight day three.^[17][19] 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.^[17] 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.^[24] 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.^[18][19] On flight day five, Endeavour would have had a full heat shield inspection, and land on flight day eight.^[17][18][19]

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.^[25]

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.^[26][27]

STS-134 was the last scheduled flight of the Shuttle program. Because no more were planned after this, a special mission was developed as STS-335 to act as the LON mission for this flight. This would have paired Atlantis with ET-122, which had been refurbished following damage by Hurricane Katrina.^[28] Since there would be no next mission, STS-335 would also carry a Multi-Purpose Logistics Module filled with supplies to replenish the station.^[29]

The Senate authorized STS-135 as a regular flight on 5 August 2010,^[30] followed by the House on 29 September 2010,^[31] and later signed by President Obama on 11 October 2010.^[32] However funding for the mission remained dependent on a subsequent appropriations bill.

Nonetheless NASA converted STS-335, the final Launch On Need mission, into an operational mission (STS-135) on 20 January 2011.^[33] On 13 February 2011, program managers told their workforce that STS-135 would fly "regardless" of the funding situation via a continuing resolution.^[34] Finally the U.S. government budget approved in mid-April 2011 called for $5.5 billion for NASA's space operations division, including the Space Shuttle and space station programs. According to NASA, the budget running through 30 September 2011 ended all concerns about funding the STS-135 mission.^[35]

With the successful completion of STS-134, STS-335 was rendered unnecessary and launch preparations for STS-135 continued as Atlantis neared LC-39A during its rollout as STS-134 landed at the nearby Shuttle Landing Facility.^[36]

For the STS-135, no shuttle was available for a rescue mission. A different rescue plan was devised, involving the four crew members remaining aboard the International Space Station, and returning aboard Soyuz spacecraft one at a time over the next year. That contingency was not required.

• "CSCS Flight Rules" (PDF). (34.2 KiB)