Space shuttle contingency functional


Patrick AFB FL 32925-3239 15 February 2003



Download 2.5 Mb.
Page23/31
Date31.03.2018
Size2.5 Mb.
#45357
1   ...   19   20   21   22   23   24   25   26   ...   31

Patrick AFB FL 32925-3239

15 February 2003



APPENDIX 4 TO ANNEX H TO DDMS CONTINGENCY FUNCPLAN 3610-03

UPPER AIR OBSERVING SYSTEM OPERATIONS


1. General. NASA established requirements for balloon soundings in support of landing operations at all sites. To satisfy both meteorological and flight dynamic requirements, NASA purchased upper air observing system systems. Personnel operate TASS equipment at each TAL site and Edwards AFB, CA, to form a balloon sounding network that functions only during Space Shuttle operations.
2. Concept of Operations. DOD weather personnel operate the TASS system at all TAL sites. All DOD personnel operating the RATS receive training prior to certification to operate the TASS equipment. Tasked units document training in their local training records. NASA provides equipment and supplies and reimburses training costs. TASS operators launch balloons at specified times and transmit observed upper air data to NASA by computer-to-computer transfer via satellite relay or commercial telephone.
3. TASS Balloon Schedule. SMG provides TAL site balloon schedules to each TAL site WPOC for each mission. CONUS sites follow range schedules received from SMG. Typical times for balloon launches appear below:


TIME (HOURS)

ALTITUDE

REMARKS

L-48 (approximate time)

80,000 Ft AGL




L-36

80,000 Ft AGL




L-24

80,000 Ft AGL




L-13

80,000 Ft AGL




L-9

80,000 Ft AGL




L-4.5

50,000 Ft AGL

(only per JSC request)

L-2.5

40,000 Ft AGL




L-1

10,000 Ft AGL




Landing

70,000 Ft AGL

(if Shuttle lands)

4. Communication. NASA provides the communications for computer-to-computer transfer of data. Weather personnel normally use the INMARSAT terminal or commercial telephones for data transmission to SMG.


5. Documentation. DDMS-W supplies weather support operating instructions for each TAL site.

(INTENTIONALLY BLANK)

DEPARTMENT OF DEFENSE

MANNED SPACE FLIGHT SUPPORT OFFICE


Patrick AFB FL 32925-3239

15 February 2003




ANNEX J TO DDMS CONTINGENCY FUNCPLAN 3610-03

COMMAND RELATIONSHIPS


REFERENCES:

a. Johnson Space Center, National Space Transportation System Program Directives










b. NASA Space Shuttle Operations Plan (NSTS 07700, Vol. VIII), Revision E, Change 53, September 2000










c. Secretary of Defense Memorandum, 15 October 1996, Subject: Assignment of Responsibilities for the DOD Manager, Manned Space Flight Support Operations










d. Director, Joint Staff Memorandum, DJSM-1226-96, 16 December 1996, Subject: Assignment of Responsibilities for the DOD Manager, Manned Space Flight Support Operations










e. KSC STS Operations Plan Flight and Ground Crew Rescue, K-STSM-09.3.1, Revision E, April 1998

1. General.


a. Purpose. This annex identifies the DOD Manager's Space Shuttle support management and control structure and those NASA management positions which interface with DOD elements when conducting operations in support of the Space Shuttle.
b. Scope. The information contained herein provides an overview of the DOD/NASA Space Shuttle support management and control structure. The DOD management organization is based upon DOD operational concepts and planned response options to NASA's documented support requirements. NASA management identified in this annex is provided for planning and information purposes and is not to be considered an assignment of internal NASA responsibilities. Appendix 1 gives a pictorial representation of the communications interface at each of the NASA/DOD augmented sites.
c. Responsibility. Commanders of tasked organizations will identify appropriate management and control positions within their organizations to interface with those of the DOD Manager and NASA as specified in this plan.
2. DOD Contingency Support Management And Control. Key members of the DOD Space Shuttle contingency support management organization are listed below:
a. DOD Manager. The Commander, United States Strategic Command, is the DOD Manager for Manned Space Flight Support Operations. The DOD Manager exercises tactical control over DOD forces participating in Space Shuttle contingency support operations as defined in this functional plan. For matters related to Space Shuttle contingency support operations, the DOD Manager reports through the Chairman, Joint Chiefs of Staff, to the Secretary of Defense and is the supported commander. The DOD Manager communicates with the DOD Support Operations Center (SOC) through the STRATCOM Command Center at Offutt AFB, NE.
b. Deputy DOD Manager. The 45 SW Commander, Patrick AFB, FL, is the Deputy DOD Manager.
c. DDMS Commander. The DDMS Commander occupies a console position in the Operations Support Room (callsign “DDMS”) in the Launch Control Center (LCC) for each launch. During on-orbit periods and landings, the DDMS Commander is on call.
d. DOD Support Operations Center (SOC) Director. The SOC Director represents the DOD Manager in Space Shuttle contingency support operations during mission periods and reports directly to the DDMS Commander. The SOC Director provides an interface with tasked operational support forces and performs a coordinating and status monitoring function for the DOD Manager. Representatives from Operations, Communications, Public Affairs, Meteorology, Medical, and the Coast Guard assist the SOC Director in the execution of the DOD support mission. The SOC Director will:
(1) Maintain status of search and rescue (SAR) control centers and forces.
(2) Maintain status and coordinate the readiness and response of the DOD landing sites and dedicated resources.
(3) Maintain communications with JSC, KSC, ALSs, ELSs, and DOD contingency response forces.
(4) Initiate the response to locate, render aid, and recover the orbiter flight crew in the event of a downed orbiter or crew bailout.
(5) Serve as the focal point to coordinate real-time support requirements.
(6) Report daily status (SITREPs) of SAR, contingency operations, and/or recovery actions to the DOD Manager through the SPOC, until relieved of that responsibility by JTF-DDMS or the SPOC.
e. Field Management. Tasked organizations will establish management positions as required to accomplish the mission. Commanders of identified landing sites will designate a Space Shuttle support contingency coordinator/airfield support coordination officer (ASCO) and an OSC to direct response to landing operations/contingencies. Procedures will be established to coordinate readiness and response actions with the SOC Director. See Annex C and the appropriate appendix for specific details.
(1) On-Scene Commander (OSC). The OSC directs the employment of all local DOD forces supporting Space Shuttle contingency operations. In discharging these duties, the OSC responds to requests from the NASA GOM (if on site) and with the SOC Director through the Space Shuttle support contingency coordinator or ASCO. Overall responsibility for the protection of life and property rests with the OSC who will direct actions as necessary. Specific responsibilities of the OSC include, but are not limited to:
(a) Assuring only properly trained and prepared personnel are used and all personnel are operationally ready to support as required.
(b) Ensuring the contingency response force (CRF) is formed and prepared to respond to orbiter contingencies.
(c) Providing command and control of all DOD forces and directing their response to landing contingencies.
(d) Responding to the NASA Representative’s (if on site) requests for support until a contingency mode is declared. If a contingency is declared, the OSC assumes responsibility for the orbiter and crew until the situation is resolved.
(e) Responding to requests from the NCC for selective use of fire protection equipment to control leaks, spills, smoke, etc., during landing/post-landing operations.
(f) Securing and controlling access to the orbiter vehicle or contingency site IAW the security requirements defined in Annex L, local DOD directives and as the situation dictates. The OSC will maintain security until released of responsibility by NASA personnel.
(g) Relaying information, when the situation allows, through the Space Shuttle support contingency coordinator/ASCO concerning orbiter landing or contingency actions to the SOC Director.
NOTE 1: At Moron AB, the OSC is the 496 ABS Commander or his designated representative.
NOTE 2: At Zaragoza AB the DOD Senior Fire Official directs operations at the scene if a mode is declared. During other convoy operations he responds to requests from the NASA Convoy Commander (NCC).
NOTE 3: At Ben Guerir TAL site, the deployed SGS Fire Chief directs operations at the scene if a mode is declared.
NOTE 4: At KSC, the NASA Landing Recovery Director (LRD) requests contingency response actions from the SOC.
NOTE 5: During a MODE VIII contingency response, the AIRBOSS will act as OSC and is

responsible for employment of DOD forces on-scene. The AIRBOSS reports directly to the SOC.


(2) Space Shuttle support contingency coordinator/ASCO. The Space Shuttle support contingency coordinator/ASCO is appointed by the installation commander and normally functions as the primary point of contact with DDMS to coordinate shuttle support requirements. Specific responsibilities of the Space Shuttle support contingency coordinator/ASCO are determined by the commander. They include, but are not limited to:
(a) Supporting the OSC as a communication and information link both passing and receiving information from the SOC during an orbiter landing.
(b) Coordinating any requirements for additional base assets when the OSC directs.
(c) Support, as able, the NASA GOM and the DDMS DFC (if on site).
3. NASA Contingency Support Management. Key members of NASA organizations that interface with DOD operational support forces are listed below.
a. NASA Executive Management.
(1) Director, Space Shuttle. NASA management has designated a Director who has overall responsibility for NASA contingency support planning. Both KSC and JSC personnel support contingency operations IAW NASA Space Shuttle Program directives and plans.
(2) Launch Director. The NASA Launch Director, located in the Launch Control Center (LCC) at KSC, is responsible for prelaunch and KSC launch contingency support operations. In this capacity, the Launch Director performs appropriate NASA mission-level contingency support management and control functions. This responsibility is in addition to those assigned for the conduct of Space Shuttle mission launch operations.
(3) Flight Director. The NASA Flight Director, located in the Mission Control Center (MCC) at JSC, is responsible for remote contingencies and, in this capacity, performs mission-level NASA contingency support management and control over remote contingency operations. This responsibility is in addition to those assigned for the conduct of Space Shuttle mission flight operations.
(4) NASA Test Director (NTD). The NTD, located in the LCC, is responsible to the Launch Director for the management and execution of NASA launch operations at KSC. The NTD coordinates the GO/NO GO status from all team elements prior to launch and authorizes initiation of the terminal countdown sequence. In the event of a contingency during the prelaunch or launch sequence, the NTD is responsible for directing appropriate NASA actions and requesting DOD support as required.
(5) Landing Recovery Director (LRD). The LRD, located in the LCC, is responsible for coordinating all KSC activities supporting landing and post-landing operations at either KSC, the designated end-of-mission (EOM) landing site, abort-once-around (AOA) landing site, or with the NASA GOM at the TAL site. In the event of a contingency while landing at KSC, the LRD is the principal interface with the SOC Director.
b. Field Management. The following NASA management positions interface directly with the DOD Manager's contingency support elements in conducting contingency support operations.
(1) NASA Convoy Commander (NCC). At the designated EOM/AOA/TAL sites (see J-1-3) there will be a NCC responsible for managing the overall NASA on-site activities during orbiter landing/contingency operations. In the event of a contingency during landing, the NCC's specific responsibilities are to:
(a) Direct the NASA on-site safing and servicing activities.
(b) Establish a controlled access area surrounding the orbiter.
(c) Control access to/within the controlled area.
(d) Discharge NASA's responsibility for the preservation of life, limb, or property.
(e) Assure collection/preservation of all perishable and nonperishable data/evidence.
(f) Coordinate with the on-scene DOD representative for DOD support, as required.
(g) Provide on-scene expertise and assistance to responding DOD forces.
(h) Provide situation reports to appropriate NASA management elements.
(2) NASA KSC Rescue Operations Commander (ROC). The ROC is the on-scene commander (OSC) for KSC rescue operations in the local area. The ROC is the final authority in committing rescue forces at the mishap scene.
(3) NASA KSC Director of Safety, Reliability and Quality Assurance. The NASA KSC Director of Safety, Reliability and Quality Assurance manages operational safety implementation during Space Shuttle ground operations and integrates the overall development of contingency plans which involve KSC resources.
(4) NASA Representatives at the TAL Sites and CONUS (Continental United States) DOD Landing Sites. NASA deploys personnel, as required, to TAL sites and DOD augmented landings sites (ALSs) to support orbiter landing/post-landing operations.
(a) NASA Ground Operations Manager (GOM). The NASA GOM is the primary representative of the Deputy Program Manager, Space Shuttle and is the single point of contact (on-site) for NASA. He is responsible for the preparation of the landing site to adequately support an orbiter landing, for the orbiter following flight crew exit and for establishing the turn-around operation to return the orbiter to KSC. The GOM also has the authority to approve expenditures of NASA reimbursable funds. Specific responsibilities are to:
1. Coordinate support with the host country civilian and military officials, US Embassy, various NASA contractor organizations, and DDMS for DOD support.
2. Interface with the DDMS DFC to coordinate all DOD support functions.
3. Interface with the DOD OSC/Senior Fire Official (SFO) to keep him apprised of orbiter status during landing/post-landing operations.
4. Communicate with the orbiter flight crew after wheel stop.
5. Advise the orbiter flight crew on appropriate mode of egress.
6. Request contingency mode response from the DOD OSC/SFO.
7. Advise the DOD OSC/SFO on selective use of fire protection equipment to control leaks, spills, fires, etc., during landing/post-landing operations. However, in the event of a major mishap or accident, the OSC/SFO will take such actions as deemed necessary for the preservation of life and property.
8. Close the orbiter side/top hatch.
9. Tow the orbiter from the runway.
10. Ensure minimum security requirements for orbiter protection are met.
11. Request additional support not previously documented in Program Requirement Documents from the DDMS representative.
(b) JSC Representative [TAL Communicator (TALCOM)]. The TALCOM from the Astronaut Office at JSC represents the JSC Flight Director and provides expertise on orbiter landing parameters to NASA/DOD personnel. Additional responsibilities are to:
1. Serve as the Deputy Site Manager with tasks as assigned by the GOM.
2. Advise the Flight Director on landing conditions at the site, including weather and any other phenomenon, which would affect an orbiter landing.
3. Advise the NASA GOM on landing aid status (i.e., Ball/Bar, PAPI, Aim Point lights, TACAN, etc.) following aircraft weather observation flights. This is not

required per the Program Requirements Document but may be accomplished in conjunction with the weather flight.


4. Advise tower controllers and communicate with the orbiter crew when required.
(c) NASA Contractor. Specific responsibilities are to:
1. Accompany the DOD OSC/SFO during landing support activities.
2. Interface with the DOD OSC/SFO to keep him apprised of orbiter status during landing/post-landing operations.
3. Advise the orbiter crew on appropriate mode of egress.
4. Request contingency mode response from the DOD OSC/SFO.
5. Advise the DOD OSC/SFO on selective use of fire protection equipment to control leaks, spills, fires, etc., during landing/post-landing operations. However, in the event of a major mishap or accident, the OSC/SFO will take such actions as deemed necessary for the preservation of life and property.
(5) DOD Houston. The DOD Houston position, located in the JSC Mission Control Center, supports the Flight Director by providing the coordination interface with the NASA Mission Operations Flight Control Team and landing support activities. DOD Houston monitors Space Shuttle mission activities, DOD support capabilities, and real-time support requirements. Should a launch abort or landing contingency occur, DOD Houston coordinates with internal NASA management and external organizations worldwide in determining the preferred course of action. DOD Houston is the primary interface with the SOC in acquiring DOD support for emergency situations after lift-off of the shuttle. The following tasks are included in specific DOD Houston responsibilities:
(a) Maintain status of launch site and contingency support forces.
(b) Coordinate status of DOD augmented and worldwide landing site contingency support capabilities.
(c) Coordinate pre-mission support schedules and landing opportunity schedules for DOD landing site mission support.
(d) Provide pertinent information to the SOC should a contingency occur, i.e., projected orbiter landing/bailout location.



DAVID K. DINGLEY

JAMES O. ELLIS, JR.

Colonel, USAF

Admiral, USN

Commander, DOD Manned Space

DOD Manager,

Flight Support Office

Manned Space Flight Support Operations

Appendix:


1. Command Relationships Diagrams

DEPARTMENT OF DEFENSE



MANNED SPACE FLIGHT SUPPORT OFFICE


Download 2.5 Mb.

Share with your friends:
1   ...   19   20   21   22   23   24   25   26   ...   31




The database is protected by copyright ©ininet.org 2024
send message

    Main page