| Revision as of 03:40, 12 April 2006 edit4.171.51.243 (talk) →Range Safety Officer (formerly RSO, currently flight contol officer FCO)← Previous edit | Revision as of 23:55, 13 April 2006 edit undoRich Farmbrough (talk | contribs)Edit filter managers, Autopatrolled, Extended confirmed users, File movers, Pending changes reviewers, Rollbackers, Template editors1,725,419 editsm clean up using AWBNext edit → | ||
| Line 3: | Line 3: | ||
| The room where the flight controllers work was called the Mission Operations Control Room (MOCR), and now is called the Flight Control Room (FCR). The "back room" was called the Staff Support Room (SSR), and is now called the Multi-Purpose Support Room (MPSR). The front room/back room split is a critical concept and unique to JSC. The front room controllers, named below, are experts in their system, but even more so, they are experts in integrating their systems into the activities of the vehicle. The back room positions are far more specialied on the operation of their systems, almost to the exclusion of other activities. | The room where the flight controllers work was called the Mission Operations Control Room (MOCR), and now is called the Flight Control Room (FCR). The "back room" was called the Staff Support Room (SSR), and is now called the Multi-Purpose Support Room (MPSR). The front room/back room split is a critical concept and unique to JSC. The front room controllers, named below, are experts in their system, but even more so, they are experts in integrating their systems into the activities of the vehicle. The back room positions are far more specialied on the operation of their systems, almost to the exclusion of other activities. | ||
| ] also have flight controllers but are managed from separate organizations, either the ] for deep-space missions or ] for near-earth missions. | ] also have flight controllers but are managed from separate organizations, either the ] for deep-space missions or ] for near-earth missions. | ||
| Each flight controller has a unique ], which describes the position responsibilities. The call sign and responsibility refer to the particular ''console'', not just the person, since missions are managed around the clock and with each shift change a different person takes over the console. | Each flight controller has a unique ], which describes the position responsibilities. The call sign and responsibility refer to the particular ''console'', not just the person, since missions are managed around the clock and with each shift change a different person takes over the console. | ||
| Flight controller responsibilities have changed over time, and continue to evolve. New controllers are added, and tasks are reassigned to other controllers to keep up with changing technical systems. For example the EECOM handled ] communication systems though ], which was afterward assigned to a new position called INCO. | Flight controller responsibilities have changed over time, and continue to evolve. New controllers are added, and tasks are reassigned to other controllers to keep up with changing technical systems. For example the EECOM handled ] communication systems though ], which was afterward assigned to a new position called INCO. | ||
| == Shuttle and space station flight controllers == | == Shuttle and space station flight controllers == | ||
| Line 16: | Line 16: | ||
| In contrast, the ISS flight controllers work 24 hours a day, 365 days a year. This allows the ISS flight controllers time to discuss off-] telemetry. The ] flight controllers have the opportunity to interface with many groups and engineering experts. The mentality behind an ] flight controller is to preempt a failure. Telemetry is closely monitored for any signatures that may begin to indicate future catastrophic failures. Generally, ] flight controllers take a ] approach to space vehicle operations. There are command capabilities that ] flight controllers use to preclude a potential failure. | In contrast, the ISS flight controllers work 24 hours a day, 365 days a year. This allows the ISS flight controllers time to discuss off-] telemetry. The ] flight controllers have the opportunity to interface with many groups and engineering experts. The mentality behind an ] flight controller is to preempt a failure. Telemetry is closely monitored for any signatures that may begin to indicate future catastrophic failures. Generally, ] flight controllers take a ] approach to space vehicle operations. There are command capabilities that ] flight controllers use to preclude a potential failure. | ||
| The ] flight controllers have the capability of sending commands to the ] , causing system reconfigurations. Also, systems like thermal controls and life support are a single console position (known as ]) for Space Shuttle flight controllers. The ISS is a much larger vehicle, and therefore its subsystems are much more extensive in size and capability. The ISS console position that monitors the life support system is known as Environmental Controls and Life Support System (ECLSS, prounounced Ecliss). The ] console position that monitors thermal controls is known as |
The ] flight controllers have the capability of sending commands to the ] , causing system reconfigurations. Also, systems like thermal controls and life support are a single console position (known as ]) for Space Shuttle flight controllers. The ISS is a much larger vehicle, and therefore its subsystems are much more extensive in size and capability. The ISS console position that monitors the life support system is known as Environmental Controls and Life Support System (ECLSS, prounounced Ecliss). The ] console position that monitors thermal controls is known as Thermal Operations and Resources (THOR). The THOR and ECLSS console positions require exhaustive amounts of system knowledge and therefore are two separate console positions. | ||
| == Responsibility == | == Responsibility == | ||
| Line 26: | Line 25: | ||
| * During the launch of ], the ] was struck by lightning which knocked out all ] and the Apollo guidance unit. This would probably have aborted the mission, except EECOM controller ] quickly determined that an obscure cockpit switch could fix the problem. | * During the launch of ], the ] was struck by lightning which knocked out all ] and the Apollo guidance unit. This would probably have aborted the mission, except EECOM controller ] quickly determined that an obscure cockpit switch could fix the problem. | ||
| * During space shuttle mission ], a ] failed during ascent to orbit. A second engine began showing signs of failing. If it failed it would cause an ], or possibly could cause the shuttle to ditch in the ocean. Booster officer Jenny Howard Stein determined within seconds it was an incorrect sensor and not an engine problem. At her direction the crew inhibited the sensor, which saved the mission and possibly the crew. | * During space shuttle mission ], a ] failed during ascent to orbit. A second engine began showing signs of failing. If it failed it would cause an ], or possibly could cause the shuttle to ditch in the ocean. Booster officer Jenny Howard Stein determined within seconds it was an incorrect sensor and not an engine problem. At her direction the crew inhibited the sensor, which saved the mission and possibly the crew. | ||
| ====Other flight controller definitions==== | ====Other flight controller definitions==== | ||
| Line 59: | Line 58: | ||
| == Space Shuttle flight control positions == | == Space Shuttle flight control positions == | ||
| ===Electrical, Environmental and Consumables Manager (EECOM)=== | ===Electrical, Environmental and Consumables Manager (EECOM)=== | ||
| (Call sign: EECOM) is a space flight control room position at ]'s ]. The EECOM controller monitors ] levels for ]s, ] and cabin cooling systems, electrical distribution systems, cabin pressure control systems and vehicle lighting systems. | (Call sign: EECOM) is a space flight control room position at ]'s ]. The EECOM controller monitors ] levels for ]s, ] and cabin cooling systems, electrical distribution systems, cabin pressure control systems and vehicle lighting systems. | ||
| Historically, the EECOM controller is responsible for monitoring and maintaining the spacecraft electrical and life-support systems. For the ] Program, the EECOM is responsible for the life support and thermal systems, a breathable atmosphere and vehicle cooling. The complexity of the ] created two new flight control positions, ] and ] which oversee the electrical and mechanical systems respectively, of which EECOM used to run. While many new flight controller positions have been created throughout the years, EECOM has been around since the beginning of manned spaceflight. | Historically, the EECOM controller is responsible for monitoring and maintaining the spacecraft electrical and life-support systems. For the ] Program, the EECOM is responsible for the life support and thermal systems, a breathable atmosphere and vehicle cooling. The complexity of the ] created two new flight control positions, ] and ] which oversee the electrical and mechanical systems respectively, of which EECOM used to run. While many new flight controller positions have been created throughout the years, EECOM has been around since the beginning of manned spaceflight. | ||
| EECOM originally stood for Electrical, Environmental and COMmunication systems. The ] EECOM was responsible for the ]s of the ], and also CSM communications through ]. Afterward the communication task was moved to a new console named INCO. | EECOM originally stood for Electrical, Environmental and COMmunication systems. The ] EECOM was responsible for the ]s of the ], and also CSM communications through ]. Afterward the communication task was moved to a new console named INCO. | ||
| Perhaps the most famous NASA EECOMs are ], the EECOM on duty at the time of the oxygen tank explosion on ] who was responsible for isolating the explosion's damage and for creating life-support solutions to bring the crew back to Earth alive, and ] who is credited with discovering the fact that ] capsule was struck by lightning shortly after liftoff and for giving the crew onboard a solution to their mechanical errors. | Perhaps the most famous NASA EECOMs are ], the EECOM on duty at the time of the oxygen tank explosion on ] who was responsible for isolating the explosion's damage and for creating life-support solutions to bring the crew back to Earth alive, and ] who is credited with discovering the fact that ] capsule was struck by lightning shortly after liftoff and for giving the crew onboard a solution to their mechanical errors. | ||
| * Apollo EECOM : Journey of a Lifetime: Apogee Books Space Series 31 (2003) ISBN 1896522963 | * Apollo EECOM : Journey of a Lifetime: Apogee Books Space Series 31 (2003) ISBN 1896522963 | ||
| ===Guidance, Navigation, and Controls Systems Engineer (GNC)=== | ===Guidance, Navigation, and Controls Systems Engineer (GNC)=== | ||
| (]: GNC) monitors all vehicle guidance, navigation and control systems, notifies the ] and crew of impending ], and advises crew regarding guidance hardware malfunctions. Also responsible for all inertial navigational systems hardware such as star trackers, radar altimeters and the inertial measurement units; monitors radio navigation and digital autopilot hardware systems. | (]: GNC) monitors all vehicle guidance, navigation and control systems, notifies the ] and crew of impending ], and advises crew regarding guidance hardware malfunctions. Also responsible for all inertial navigational systems hardware such as star trackers, radar altimeters and the inertial measurement units; monitors radio navigation and digital autopilot hardware systems. | ||
| ===Guidance Procedures Officer/Rendezvous Officer (GUIDANCE)=== | ===Guidance Procedures Officer/Rendezvous Officer (GUIDANCE)=== | ||
| Line 78: | Line 76: | ||
| ===Flight Dynamics Officer (FIDO)=== | ===Flight Dynamics Officer (FIDO)=== | ||
| (]: FDO, pronounced "fido") responsible for the flight path of the space vehicle, both atmospheric and ]. During lunar missions the FDO is also responsible for lunar ]. The FDO monitors vehicle performance during the powered flight phase and assesses ], calculates orbital maneuvers and resulting trajectories, and monitors vehicle flight profile and energy levels during ]. | (]: FDO, pronounced "fido") responsible for the flight path of the space vehicle, both atmospheric and ]. During lunar missions the FDO is also responsible for lunar ]. The FDO monitors vehicle performance during the powered flight phase and assesses ], calculates orbital maneuvers and resulting trajectories, and monitors vehicle flight profile and energy levels during ]. | ||
| '''External links''' | '''External links''' | ||
| Line 88: | Line 86: | ||
| (]: BOOSTER) monitors and evaluates performance of propulsion-related aspects of the launch vehicle during prelaunch and ascent, regardless of whether strap-on ]s are used. | (]: BOOSTER) monitors and evaluates performance of propulsion-related aspects of the launch vehicle during prelaunch and ascent, regardless of whether strap-on ]s are used. | ||
| In the U.S. ], the Booster Systems Engineer monitors the ], ] and ] during prelaunch and ascent phases of missions. | In the U.S. ], the Booster Systems Engineer monitors the ], ] and ] during prelaunch and ascent phases of missions. | ||
| In a space flight context, a ] can refer either to strap on ]s, or to the entire vehicle as it ascends under powered flight. | In a space flight context, a ] can refer either to strap on ]s, or to the entire vehicle as it ascends under powered flight. | ||
| ===Propulsion Engineer (PROP)=== | ===Propulsion Engineer (PROP)=== | ||
| (]: PROP) manages the ] thrusters and ] engines during all phases of flight, monitors fuel usage and propellant tank status, and calculates optimal sequences for thruster firings. | (]: PROP) manages the ] thrusters and ] engines during all phases of flight, monitors fuel usage and propellant tank status, and calculates optimal sequences for thruster firings. | ||
| ===Data Processing System Engineer (DPS)=== | ===Data Processing System Engineer (DPS)=== | ||
| (]: DPS) responsible for data processing systems in a space flight, including the onboard ]. This includes determining the data processing system status, flight-critical and launch data lines, the malfunction display system, mass memories and system-level software. | (]: DPS) responsible for data processing systems in a space flight, including the onboard ]. This includes determining the data processing system status, flight-critical and launch data lines, the malfunction display system, mass memories and system-level software. | ||
| The ] are a critical subsystem, and the vehicle cannot fly without them. | The ] are a critical subsystem, and the vehicle cannot fly without them. | ||
| '''External links''' | '''External links''' | ||
| Line 104: | Line 102: | ||
| ===Maintenance, Mechanical, Arm And Crew Systems (MMACS)=== | ===Maintenance, Mechanical, Arm And Crew Systems (MMACS)=== | ||
| (]: MMACS, pronounced "max", formerly known as RMU) responsible for ] structural and mechanical systems, including the ], monitoring ]s and ] systems, and managing payload bay and vent door operations. MMACS also follows use of onboard crew hardware and in-flight equipment maintenance. | (]: MMACS, pronounced "max", formerly known as RMU) responsible for ] structural and mechanical systems, including the ], monitoring ]s and ] systems, and managing payload bay and vent door operations. MMACS also follows use of onboard crew hardware and in-flight equipment maintenance. | ||
| ===Instrumentation and Communications Officer (INCO)=== | ===Instrumentation and Communications Officer (INCO)=== | ||
| (]: INCO), responsible for all ] data, voice and video communications systems, including monitoring the configuration of in-flight communications and ] systems. Duties also include monitoring the ] link between the vehicle and the ground, and overseeing the ] command and control processes. | (]: INCO), responsible for all ] data, voice and video communications systems, including monitoring the configuration of in-flight communications and ] systems. Duties also include monitoring the ] link between the vehicle and the ground, and overseeing the ] command and control processes. | ||
| ===Range Safety Officer (formerly RSO, currently flight contol officer FCO)=== | ===Range Safety Officer (formerly RSO, currently flight contol officer FCO)=== | ||
| (]: FCO) is responsible for public safety during flight of the launch vehicle. For Cape Canaveral, Kennedy Space Center, and Vandenberg launches, the FCO is an Air Force operative acting on the authority of the commander of the appropriate missile range. For example, for launches from Kennedy Space Center or Cape Canaveral Air Station, the FCO acts on behalf of the commander of the Eastern Range. Even for U.S. manned space missions, the FCO has authority to order the remote destruction of the launch vehicle if it shows signs of endangering the public. The U.S. ] does not have remote destruct devices, but the ] (SRBs) do. During the ], the FCO ordered the SRBs destroyed after the vehicle broke up in flight and the SRBs began flying back toward populated areas of Florida. | (]: FCO) is responsible for public safety during flight of the launch vehicle. For Cape Canaveral, Kennedy Space Center, and Vandenberg launches, the FCO is an Air Force operative acting on the authority of the commander of the appropriate missile range. For example, for launches from Kennedy Space Center or Cape Canaveral Air Station, the FCO acts on behalf of the commander of the Eastern Range. Even for U.S. manned space missions, the FCO has authority to order the remote destruction of the launch vehicle if it shows signs of endangering the public. The U.S. ] does not have remote destruct devices, but the ] (SRBs) do. During the ], the FCO ordered the SRBs destroyed after the vehicle broke up in flight and the SRBs began flying back toward populated areas of Florida. | ||
| ===Retrofire Officer (RETRO)=== | ===Retrofire Officer (RETRO)=== | ||
| (]: RETRO) monitors impact prediction displays and is responsible for determination of ] times. On Apollo planned and monitors Trans Earth Injection (TEI) manoeuvres, where the ] fired its engine to return to earth from the moon. | (]: RETRO) monitors impact prediction displays and is responsible for determination of ] times. On Apollo planned and monitors Trans Earth Injection (TEI) manoeuvres, where the ] fired its engine to return to earth from the moon. | ||
| ===Guidance Officer (GUIDO)=== | ===Guidance Officer (GUIDO)=== | ||
| Line 126: | Line 124: | ||
| ===Flight Activities Officer (FAO)=== | ===Flight Activities Officer (FAO)=== | ||
| (]: FAO) plans and supports crew activities, checklists, procedures and schedules | (]: FAO) plans and supports crew activities, checklists, procedures and schedules | ||
| == ISS flight control positions == | == ISS flight control positions == | ||
| ===Assembly and Checkout Officer (ACO)=== | ===Assembly and Checkout Officer (ACO)=== | ||
| (]: ACO) is responsible for integration of assembly and activation tasks for all ISS systems and elements and coordinating with station and shuttle flight controllers on the execution of these operations. | (]: ACO) is responsible for integration of assembly and activation tasks for all ISS systems and elements and coordinating with station and shuttle flight controllers on the execution of these operations. | ||
| Line 180: | Line 176: | ||
| * | * | ||
| * | * | ||
| ] | ] | ||
Revision as of 23:55, 13 April 2006
Flight controller: a space flight control room position at NASA's Mission Control Center. Flight controllers sit at computer consoles and use telemetry to monitor in real time various technical aspects of a manned space mission. Each controller is an expert in a specific area, and is in constant communication with additional experts in the "back room". The Flight Director is the lead flight controller, monitors the activities of others and has overall responsibility for the mission success and safety.
The room where the flight controllers work was called the Mission Operations Control Room (MOCR), and now is called the Flight Control Room (FCR). The "back room" was called the Staff Support Room (SSR), and is now called the Multi-Purpose Support Room (MPSR). The front room/back room split is a critical concept and unique to JSC. The front room controllers, named below, are experts in their system, but even more so, they are experts in integrating their systems into the activities of the vehicle. The back room positions are far more specialied on the operation of their systems, almost to the exclusion of other activities.
Unmanned U.S. space missions also have flight controllers but are managed from separate organizations, either the Jet Propulsion Laboratory for deep-space missions or Goddard Space Flight Center for near-earth missions.
Each flight controller has a unique call sign, which describes the position responsibilities. The call sign and responsibility refer to the particular console, not just the person, since missions are managed around the clock and with each shift change a different person takes over the console.
Flight controller responsibilities have changed over time, and continue to evolve. New controllers are added, and tasks are reassigned to other controllers to keep up with changing technical systems. For example the EECOM handled Command and Service Module communication systems though Apollo 10, which was afterward assigned to a new position called INCO.
Shuttle and space station flight controllers
There are two groups of flight controllers at JSC; the ISS flight controllers and the Space Shuttle flight controllers. The Space Shuttle flight controllers generally do not have the capability of sending commands to the space vehicle for any type of system reconfigurations.
The Space Shuttle flight controllers work relatively brief periods: The several minutes of ascent, the few days the vehicle is in orbit, and reentry. The duration of operations for Space Shuttle flight controllers is short and time-critical. A failure on the Shuttle leaves flight controllers little time for talking, and causes more pressure towards responding to a failure.
In contrast, the ISS flight controllers work 24 hours a day, 365 days a year. This allows the ISS flight controllers time to discuss off-nominal telemetry. The ISS flight controllers have the opportunity to interface with many groups and engineering experts. The mentality behind an ISS flight controller is to preempt a failure. Telemetry is closely monitored for any signatures that may begin to indicate future catastrophic failures. Generally, ISS flight controllers take a prophylactic approach to space vehicle operations. There are command capabilities that ISS flight controllers use to preclude a potential failure.
The ISS flight controllers have the capability of sending commands to the ISS , causing system reconfigurations. Also, systems like thermal controls and life support are a single console position (known as EECOM) for Space Shuttle flight controllers. The ISS is a much larger vehicle, and therefore its subsystems are much more extensive in size and capability. The ISS console position that monitors the life support system is known as Environmental Controls and Life Support System (ECLSS, prounounced Ecliss). The ISS console position that monitors thermal controls is known as Thermal Operations and Resources (THOR). The THOR and ECLSS console positions require exhaustive amounts of system knowledge and therefore are two separate console positions.
Responsibility
Space Shuttle flight controllers are responsible for ascent/descent operations that may lead to life-or-death decisions. Examples of life-or-death decisions:
- During the Apollo 11 moon landing, the Lunar Module guidance computer began giving errors which threatened to abort the landing. Guidance officer Steve Bales had only a few seconds to determine it was safe to proceed, which saved the mission. Bales was later awarded the Presidential Medal of Freedom for his role.
- During the launch of Apollo 12, the Saturn V was struck by lightning which knocked out all telemetry and the Apollo guidance unit. This would probably have aborted the mission, except EECOM controller John Aaron quickly determined that an obscure cockpit switch could fix the problem.
- During space shuttle mission STS-51-F, a main engine failed during ascent to orbit. A second engine began showing signs of failing. If it failed it would cause an emergency landing in Spain, or possibly could cause the shuttle to ditch in the ocean. Booster officer Jenny Howard Stein determined within seconds it was an incorrect sensor and not an engine problem. At her direction the crew inhibited the sensor, which saved the mission and possibly the crew.
Other flight controller definitions
- An FAA person who directs air traffic
- A computer joystick used for aircraft simuation games
- A joystick used to control an aircraft
"Common" flight control positions
There are some positions that have and will serve the same function in every vehicle's Flight Control team. The group of individuals serving in those positions may be different, but they will be called the same thing and serve the same function.
Flight Director (FLIGHT)
(Call sign: FLIGHT), is leads the flight control team. "Flight" has overall operational responsiblity for missions and payload operations and for all decisions regarding safe, expedient flight. He monitors the other flight controllers, who are in constant verbal communication with him through intercom channels called "loops".
Mission Operations Directorate (MOD)
(Call sign: MOD), is a representative of the senior management chain at JSC, and is there to help the FD make those decisions that have no safety-of-flight consequences, but may have cost or public perception consequences. In NO cases can the MOD rep overrule the FD (though like the captain of a warship, the FD is subject to later consequences.)
Capsule Communicator (CAPCOM)
(Call sign: CAPCOM) generally the only person who communicates directly with a manned space crew. During much of the U.S. manned space program, NASA felt it was important for all communication with the astronauts in space to pass through a single individual in the Mission Control Center. That role was designated the capsule communicator or capcom and was typically filled by another astronaut, often one of the backup crew members. For long duration missions, there would be more than one capcom, each assigned to a different shift team. After control of U.S. spaceflights moved to the Lyndon B. Johnson Space Center in the early 1960s, capcoms used the radio call sign Houston.
External links
Ground Controller (GC)
(Call sign: GC), directs maintenance and operation activities affecting Mission Control hardware, software and support facilities; coordinates space flight tracking and data network, and Tracking and Data Relay Satellite system with Goddard Space Flight Center.
Flight Surgeon (SURGEON)
(Call sign: SURGEON) directs all operational medical activities concerned with the mission, including the status of the flight crew. Monitors crew health, provides crew consultation, and advises flight director of the crew's health status.
Public Affairs Officer (PAO)
(Call sign: PAO) provides mission commentary to supplement and explain air-to-ground transmissions and flight control operations to the news media and the public.
Space Shuttle flight control positions
Electrical, Environmental and Consumables Manager (EECOM)
(Call sign: EECOM) is a space flight control room position at NASA's Mission Control Center. The EECOM controller monitors cryogenic levels for fuel cells, avionics and cabin cooling systems, electrical distribution systems, cabin pressure control systems and vehicle lighting systems.
Historically, the EECOM controller is responsible for monitoring and maintaining the spacecraft electrical and life-support systems. For the Space Shuttle Program, the EECOM is responsible for the life support and thermal systems, a breathable atmosphere and vehicle cooling. The complexity of the Space Shuttle created two new flight control positions, EGIL and MMACS which oversee the electrical and mechanical systems respectively, of which EECOM used to run. While many new flight controller positions have been created throughout the years, EECOM has been around since the beginning of manned spaceflight.
EECOM originally stood for Electrical, Environmental and COMmunication systems. The Apollo EECOM was responsible for the life support systems of the Command and Service Module (CSM), and also CSM communications through Apollo 10. Afterward the communication task was moved to a new console named INCO.
Perhaps the most famous NASA EECOMs are Seymour "Sy" Liebergot, the EECOM on duty at the time of the oxygen tank explosion on Apollo 13 who was responsible for isolating the explosion's damage and for creating life-support solutions to bring the crew back to Earth alive, and John Aaron who is credited with discovering the fact that Apollo 12 capsule was struck by lightning shortly after liftoff and for giving the crew onboard a solution to their mechanical errors.
- Apollo EECOM : Journey of a Lifetime: Apogee Books Space Series 31 (2003) ISBN 1896522963
Guidance, Navigation, and Controls Systems Engineer (GNC)
(Call sign: GNC) monitors all vehicle guidance, navigation and control systems, notifies the flight director and crew of impending abort situations, and advises crew regarding guidance hardware malfunctions. Also responsible for all inertial navigational systems hardware such as star trackers, radar altimeters and the inertial measurement units; monitors radio navigation and digital autopilot hardware systems.
Guidance Procedures Officer/Rendezvous Officer (GUIDANCE)
(Call sign: GUIDANCE) operational responsibility for crew procedures assistance during critical phases of ascent, entry, and rendezvous. Monitors onboard navigation and onboard guidance computer software.
Flight Dynamics Officer (FIDO)
(Call sign: FDO, pronounced "fido") responsible for the flight path of the space vehicle, both atmospheric and orbital. During lunar missions the FDO is also responsible for lunar trajectory. The FDO monitors vehicle performance during the powered flight phase and assesses abort modes, calculates orbital maneuvers and resulting trajectories, and monitors vehicle flight profile and energy levels during re-entry.
External links
Booster Systems Engineer (BOOSTER)
(Call sign: BOOSTER) monitors and evaluates performance of propulsion-related aspects of the launch vehicle during prelaunch and ascent, regardless of whether strap-on booster rockets are used.
In the U.S. Space Shuttle program, the Booster Systems Engineer monitors the space shuttle main engines, solid rocket boosters and external tank during prelaunch and ascent phases of missions.
In a space flight context, a booster can refer either to strap on booster rockets, or to the entire vehicle as it ascends under powered flight.
Propulsion Engineer (PROP)
(Call sign: PROP) manages the reaction control thrusters and orbital maneuvering engines during all phases of flight, monitors fuel usage and propellant tank status, and calculates optimal sequences for thruster firings.
Data Processing System Engineer (DPS)
(Call sign: DPS) responsible for data processing systems in a space flight, including the onboard general purpose computers. This includes determining the data processing system status, flight-critical and launch data lines, the malfunction display system, mass memories and system-level software.
The space shuttle general purpose computers are a critical subsystem, and the vehicle cannot fly without them.
External links
Maintenance, Mechanical, Arm And Crew Systems (MMACS)
(Call sign: MMACS, pronounced "max", formerly known as RMU) responsible for space shuttle structural and mechanical systems, including the remote manipulator system, monitoring auxiliary power units and hydraulic systems, and managing payload bay and vent door operations. MMACS also follows use of onboard crew hardware and in-flight equipment maintenance.
Instrumentation and Communications Officer (INCO)
(Call sign: INCO), responsible for all space shuttle data, voice and video communications systems, including monitoring the configuration of in-flight communications and instrumentation systems. Duties also include monitoring the telemetry link between the vehicle and the ground, and overseeing the uplink command and control processes.
Range Safety Officer (formerly RSO, currently flight contol officer FCO)
(Call sign: FCO) is responsible for public safety during flight of the launch vehicle. For Cape Canaveral, Kennedy Space Center, and Vandenberg launches, the FCO is an Air Force operative acting on the authority of the commander of the appropriate missile range. For example, for launches from Kennedy Space Center or Cape Canaveral Air Station, the FCO acts on behalf of the commander of the Eastern Range. Even for U.S. manned space missions, the FCO has authority to order the remote destruction of the launch vehicle if it shows signs of endangering the public. The U.S. space shuttle orbiter does not have remote destruct devices, but the solid rocket boosters (SRBs) do. During the Challenger disaster, the FCO ordered the SRBs destroyed after the vehicle broke up in flight and the SRBs began flying back toward populated areas of Florida.
Retrofire Officer (RETRO)
(Call sign: RETRO) monitors impact prediction displays and is responsible for determination of retrofire times. On Apollo planned and monitors Trans Earth Injection (TEI) manoeuvres, where the Apollo Service Module fired its engine to return to earth from the moon.
Guidance Officer (GUIDO)
(Call sign: GUIDO, pronounced "guy dough") verifies performance of inertial navigation system and onboard guidance system software.
Electrical Generation and Integrated Lighting Systems Engineer (EGIL)
(Call sign: EGIL) monitors cryogenic levels for the fuel cells, electrical generation and distribution systems on he spacecraft, and vehicle lighting.
Telemetry, electrical, EVA Mobility Unit Officer (TELMU)
(Call sign: TELMU) on Apollo lunar missions monitored the Lunar Module electrical and environmental systems, plus lunar astronaut spacesuits. Essentially the equivalent of the EECOM for the lunar module.
Flight Activities Officer (FAO)
(Call sign: FAO) plans and supports crew activities, checklists, procedures and schedules
ISS flight control positions
Assembly and Checkout Officer (ACO)
(Call sign: ACO) is responsible for integration of assembly and activation tasks for all ISS systems and elements and coordinating with station and shuttle flight controllers on the execution of these operations.
Attitude Determination and Control Officer (ADCO)
(Call sign: ADCO) works in partnership with Russian controllers to determine and manage the station’s orientation, controlled by the onboard Motion Control Systems. This position also plans and calculates future orientations and maneuvers for the station.
Communication and Tracking Officer (CATO)
(Call sign: CATO) is responsible for management and operations of the U.S. communication systems, including audio, video, telemetry and commanding systems.
Environmental Control and Life Support System (ECLSS)
(Call sign: ECLSS, pronounced "eekliss") is responsible for the assembly and operation of systems related to atmosphere control and supply, atmosphere revitalization, cabin air temperature and humidity control, circulation, fire detection and suppression, water collection and processing and crew hygiene equipment, among other areas.
Extravehicular Activity Officer (EVA)
(Call sign: EVA) is responsible for all spacesuit and spacewalking-related tasks, equipment and plans.
Onboard, Data, Interfaces and Networks (ODIN)
(Call sign: ODIN) is responsible for the U.S. Command and Data Handling System, including hardware, software, networks, and interfaces with International Partner avionics systems.
Operations Support Officer (OSO)
(Call sign: OSO) is the console operator that is charged with those logistics support funtions that address on-orbit maintenance, support data and documentation, logistics information systems, maintenance data collection and maintenance analysis. Also responsible for mechanical systems -- such as those used to attach new modules or truss sections to the vehicle during assembly.
Power, Heating, Articulation, Lighting Control Officer (PHALCON)
(Call sign: Phalcon) manages the power generation, storage, and power distribution capabilities.
Robotics Operations Systems Officer (ROBO)
(Call sign: ROBO) is responsible for the operations of the Canadian Mobile Servicing System, which includes a mobile base system, station robotic arm, station robotic hand or special purpose dexterous manipulator. (Call sign: ROBO) represents a joint Canadian Space Agency-NASA team of specialists to plan and execute robotic operations.
Thermal Operations and Resources (THOR)
(Call sign: THOR) is responsible for the assembly and operation of multiple station subsystems which collect, distribute, and reject waste heat from critical equipment and payloads.
Trajectory Operations Officer (TOPO)
(Call sign: TOPO) is responsible for the station trajectory. The TOPO works in partnership with Russian controllers, ADCO, and the U.S. Space Command to maintain data regarding the station's orbital position. TOPO plans all station orbital maneuvers.
Operations Planner (OPSPLAN)
(Call sign: OPSPLAN) leads the coordination, development and maintenance of the station's short-term plan, including crew and ground activities. The plan includes the production and uplink of the onboard station plan and the coordination and maintenance of the onboard inventory and stowage listings.
See also
- Mission Control Center
- Johnson Space Center
- Kennedy Space Center
- Space Shuttle program
- Apollo program
- Eugene Kranz
- Christopher C. Kraft, Jr.
- John Aaron