STS-3xx
From Wikipedia, the free encyclopedia
| Mission statistics | |
|---|---|
| Mission name: | STS-3xx
<tr><th>Launch pad:</th><td>LC-39A/B, Kennedy Space Center</td></tr> |
| Launch: | STS-1xx Flight Day #45 |
| Landing: | STS-1xx Flight Day #49 |
| Duration: | 4 days |
Space shuttle missions designated STS-3xx (officially called Launch On Need missions) are rescue missions which would be mounted to rescue the crew of a Space Shuttle if their vehicle was damaged and deemed unable to make a successful reentry. Such a mission would be flown if Mission Control determined that the heat shielding tiles and reinforced carbon-carbon (RCC) panels of a currently flying orbiter were damaged beyond the normal repair methods. This mission was also referred to as a Launch on Need (LON) or Launch on Demand (LOD) mission.
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 it being called up. During that time the damaged (or disabled) shuttle's crew would have to take refuge on the International Space Station. The ISS is able to support both crews for around 80 days, with oxygen supply being the limiting factor<ref Name=FRRBriefingTranscript>Flight Readyness Review Briefing, Transcript of press briefing carried on NASA TV, 17 June 2006</ref>. This plan for maintaining the shuttle crew at the ISS is known as Contingency Shuttle Crew Support (CSCS) operations within NASA.<ref Name=CSCSResourceBook>Contingency Shuttle Crew Support (CSCS)/Rescue Flight Resource Book. 12 July, 2005</ref> Up to STS-121 all rescue missions were to be designated STS-300.
In the case of an abort to orbit, where the shuttle doesn't reach the ISS orbit and the thermal protection system inspections suggest the shuttle could not return to earth safely, the ISS could be brought down to meet the shuttle. Such a procedure is known as joint underspeed recovery <ref name=jointunderspeed>Engineering for Complex Systems Knowledge Engineering for Safety and Success Project</ref>.
| Flight | Rescue Flight |
|---|---|
| STS-114 (Discovery) | STS-300 <ref Name=CSCSResourceBook>Contingency Shuttle Crew Support (CSCS)/Rescue Flight Resource Book. 12 July, 2005 p.101</ref> (Atlantis) |
| STS-121 (Discovery) | STS-300 <ref Name=PressKit>"STS-121 Nasa Press Kit"NASA Press Kit - STS-121, May 2006.</ref> (Atlantis) |
| STS-115 (Atlantis) | STS-301 <ref Name=PressKit>"STS-121 Nasa Press Kit"NASA Press Kit - STS-121, May 2006.</ref> <ref Name=CSCSResourceBook>Contingency Shuttle Crew Support (CSCS)/Rescue Flight Resource Book. 12 July, 2005 p.101</ref> (Discovery) |
| STS-116 (Discovery) | STS-317 <ref name=atcnews>Nasa Assurance Technology Center News Article</ref> <ref Name=launchschedule>NASA Launch Schedule (Via Hipstersunite.com)</ref> (Atlantis) |
| STS-117 (Atlantis) | STS-318 <ref Name=launchschedule>NASA Launch Schedule (Via Hipstersunite.com</ref> (Endeavour[citation needed]) |
| STS-118 (Endeavour) | STS-320 <ref Name=launchschedule>NASA Launch Schedule (Via Hipstersunite.com</ref> (Atlantis) |
| STS-120 (Atlantis) | STS-322 <ref Name=launchschedule>NASA Launch Schedule (Via Hipstersunite.com</ref> (Discovery) |
| STS-122 (Discovery) | STS-323 <ref Name=launchschedule>NASA Launch Schedule (Via Hipstersunite.com</ref> (Endeavour) |
Prior to STS-121 the plan was for the damaged shuttle to be abandoned and allowed to burn up upon reentry. STS-121 was the first shuttle mission to carry an 8.5-meter cable designed to connect the flight deck manual controls used during landing to an avionics bay in the middeck allowing mission controllers to land the shuttle unmanned if required. Such an unmanned landing may have been considered if the vehicle suffered damage that is too severe to risk a manned reentry, but might have enabled the shuttle to land intact. The landing site for an unmanned landing would have probably been Edwards Air Force Base, in California,<ref name="NASA spaceflight"> http://www.nasaspaceflight.com/content/?id=4582</ref> where the expanse of dry lake bed gives a large margin for error, unlike KSC where canals border the landing facility. White Sands Missile Range in New Mexico was another possible site.[1] The flight resource book, and flight rules in force during STS-121 suggest that the damaged Orbiter would reenter on a trajectory such that if it should break up, it would do so with debris landing in the South Pacific.<ref Name=CSCSResourceBook>Contingency Shuttle Crew Support (CSCS)/Rescue Flight Resource Book. 12 July, 2005</ref>
To save weight, and to allow the combined crews of both shuttles to return to Earth safely, many shortcuts would have had to be made, and the risks of launching another orbiter, without resolving the failure which caused the previous orbiter to become disabled would have had to be faced.
If implemented, it is highly likely such a mission would be the last flight of a Space Shuttle and mark the end of the Shuttle program.<ref>Watson, Traci. "The mission NASA hopes won't happen", USA Today, 2005-03-22. Retrieved on 2006-09-13.</ref>
Contents |
[edit] Crew
[edit] STS-114 Rescue (STS-300)
Subset of STS-121 Crew
- Steve Lindsey, Commander and backup Remote Manipulator System operator
- Mark Kelly, Pilot and prime Remote Manipulator System operator
- Michael E. Fossum, Mission Specialist 1 and Extravehicular 2
- Piers Sellers, Mission Specialist 2 and Extravehicular 1
[edit] STS-121 Rescue (STS-300)<ref Name=PressKit>"STS-121 Nasa Press Kit"NASA Press Kit - STS-121, May 2006.</ref>
Subset of STS-115 Crew
- Brent Jett, commander
- Christopher Ferguson, pilot and backup Remote Manipulator System operator
- Joseph Tanner, mission specialist 1, Extravehicular 1 and prime Remote Manipulator System operator
- Daniel Burbank, mission specialist 2 and Extravehicular 2
[edit] STS-115 Rescue (STS-301)
Subset of STS-116 Crew
- Mark Polansky - Commander
- William Oefelein - Pilot
- Christer Fuglesang - Mission specialist 1
- Robert Curbeam - Mission specialist 2
[edit] Flight hardware
A number of pieces of Launch on Need flight hardware have been 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
- Sky genie mounting provisions for four additional sky genies
- Escape Pole mounting provisions for three additional lanyards <ref name="STS114FRR">STS-114 Flight Readyness Review Presentation</ref>
[edit] Remote Control Orbiter
The Remote Control Orbiter (RCO) is a term used by NASA to describe a Shuttle that could perform entry and landing without a human crew onboard. To this end, NASA developed the RCO in-flight maintenance (IFM) cable. The cable is approximately 28 feet long, weighs over 5 lbs, and has 16 connectors.<ref>Kestenbaum, David. "Emergency Rescue Plans in Place for Astronauts", NPR, 2006-06-29. Retrieved on 2006-09-19.</ref>
The purpose of the RCO IFM cable is to provide an electrical signal connection between the Ground Command Interface Logic (GCIL) and the flight deck panel switches. 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 stowage during the mission. The cable will remain aboard the ISS until the end of the Shuttle program at which time it will be brought back to Earth on the final Shuttle flight.
[edit] Shuttle backup plan
Even following Endeavour's (OV-105) Orbiter Major Modification period, which began in December 2003 and lasted through October 2005, NASA's remaining two operational vehicles, Discovery (OV-103) and Atlantis (OV-104), still have to back each other up for the time being, should the need for an STS-3xx mission arise. Only after Endeavour returns to active operations in mid-2007 will it too carry its share of Launch-on-Need duty.
[edit] Pre-ISS era
Before the ISS was launched, shuttle crews would have had to transfer directly between shuttles, should a rescue have been needed. The orbiters would have been unable to dock, so whilst they used their RMS arms to grapple each other, the crew would have made an EVA between the shuttles. This would have been carried out using the two EVA-designated mission specialists wearing the Shuttle/ISS Extravehicular Mobility Unit (EMU) spacesuits, while the remaining crew would have been sealed up in pressurized "rescue balls" and carried over either by hand, or using a pulley system (akin to that of a clothesline pulley found on most Amish farms) like that employed in the Apollo program for lifting samples from the surface into the Lunar Module.
[edit] Timeline
- 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 transfered between the shuttle and ISS.
- FD-21 Hatch closure will be conducted from the ISS side
- FD-21 Deorbit Burn - Burn occurs four hours after separation. 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 after 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.<ref Name=CSCSResourceBook>Contingency Shuttle Crew Support (CSCS)/Rescue Flight Resource Book. 12 July, 2005 p.101</ref>
- FD-45->47 The rescue flight catches up with the ISS, conducting heat shield inspections en-route.
- FD-47 The rescue flight will dock 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 O2 exhaustion in event Progress unable to perform resupply function.
The above timeline is presented with respect to the flight day (FD) of the mission to be rescued.
[edit] STS-125 Rescue
STS-125 is a Hubble Servicing Mission; as such there is no option for a shuttle crew to use the ISS as a safe haven, and planning for a rescue mission will have to be very different. A rescue flight would have to be ready to launch only ten days after call up as the maximum time the crew could remain on the shuttle is 23 days. The mission would probably follow a similar procedure to the pre-ISS era plan, as outlined above.
[edit] References
<references />
