Flight controller: Difference between revisions

Revision as of 02:53, 12 November 2007

Latest revision as of 06:02, 14 July 2025

(375 intermediate revisions by more than 100 users not shown)

Line 1:

{{short description|Person who aids in spaceflight activities}}

'''Flight controllers''' are personnel who aid in the operations of a space flight, working in Mission Control Centers such as [[NASA]]'s [[Mission Control Center]], or [[ESA]]'s [[European Space Operations Centre|Operations 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. A Flight Director leads a team, designated by a color (e.g., [[Eugene F. Kranz]] led the White Team, and was known as "White Flight").

{{about|the spaceflight occupation|the aviation occupation|Air traffic controller}}

{{other uses}}

{{multiple image

| align = right

| image1 = Russian ISS Flight Control Room.jpg

| width1 = 260

| alt1 =

| caption1 =

| image2 = ISS Flight Control Room 2006.jpg

| width2 = 250

| alt2 =

| caption2 =

| footer = [[International Space Station]] control rooms in Russia and in the United States.

}}

'''Flight controllers''' are personnel who aid [[space flight]] by working in [[mission control center]]s such as [[NASA]]'s [[Christopher C. Kraft Jr. Mission Control Center]] or [[ESA]]'s [[European Space Operations Centre]]. Flight controllers work at computer consoles and use [[telemetry]] to monitor various technical aspects of a [[space mission]] in [[Real-time computing|real-time]]. Each controller is an expert in a specific area and constantly communicates with additional experts in the "back room". The flight director, who leads the flight controllers, monitors the activities of a team of flight controllers, and has overall responsibility for success and safety.

== NASA's Flight Controllers ==

The room where the flight controllers work was called the Mission Operations Control Room (MOCR, pronounced "moh-ker"), and now is called the Flight Control Room (FCR, pronounced "ficker"). The controllers are experts in individual systems, and make recommendations to the Flight Director involving their areas of responsibility. Any controller may call for an [[Abort (computing)|abort]] if the circumstances require it. Before (and at various stages during) an activity, the Flight Director will "go around the room," polling each controller for a GO / NO GO decision. If all factors are good, each controller calls for a GO, but if there is a problem requiring a hold or an abort, the call is NO GO. Another form of this is STAY / NO STAY, when the spacecraft has completed a maneuver and has now "parked" in relation to another body, including spacecraft (or space stations), orbiting the Earth or the Moon, or the Lunar landings.

== NASA's flight controllers ==

Controllers in MOCR/FCR are supported by the "backrooms," teams of specialists located in other parts of the building or even at other facilities across the country. These teams are able to find information and make recommendations to "their" controller. One example of the usefulness of this system occurred during the descent of the [[Apollo 11|Eagle]] [[Lunar Module]], when "1202" and "1201" "program alarms" came from the LM. GUIDO [[Steve Bales]], not sure whether to call for an abort, trusted the experts in the Guidance backroom, especially [[Jack Garman]], who told him that the problem was a computer overload, but could be ignored if it was intermittent. Bales called "GO!," Flight Director Kranz accepted the call and the mission continued to success. Without the support of the backroom, a controller might make a "bad call" based on faulty memory or information not readily available to the person on the console.

{{main list|List of NASA's flight control positions}}

The room where the flight controllers work was called the mission operations control room (MOCR, pronounced "moh-ker"), and now is called the flight control room (FCR, pronounced "ficker"). The controllers are experts in individual systems, and make recommendations to the flight director involving their areas of responsibility. Any controller may call for an [[Abort (computing)|abort]] if the circumstances require it. Before significant events, the flight director will "go around the room", polling each controller for a go/no go decision, a procedure also known as a [[launch status check]]. If all factors are good, each controller calls for a "go" but if there is a problem requiring a hold or an abort, the call is "no go". Another form of this is stay/no stay, when the spacecraft has completed a maneuver and has now "parked" in relation to another body, including spacecraft, orbiting the Earth or the Moon, or the lunar landings.

The backroom was formally called the Staff Support Room (SSR), and is now called the Multi-Purpose Support Room (MPSR, pronounced "mipser").

Controllers in MOCR/FCR are supported by the "backrooms", teams of flight controllers located in other parts of the building or even at remote facilities. The backroom was formerly called the staff support room (SSR), and is now called the multi-purpose support room (MPSR, pronounced "mipser"). Backroom flight controllers are responsible for the details of their assigned system and for making recommendations for actions needed for that system. "Frontroom" flight controllers are responsible for integrating the needs of their system into the larger needs of the vehicle and working with the rest of the flight control team (FCT) to develop a cohesive plan of action, even if that plan is not necessarily in the best interests of the system they are responsible for. Within the chain of command of the MCC, information and recommendations flow from the backroom to the frontroom to Flight, and then, potentially, to the on board crew. Generally, a MOCR/FCR flight control team is made up of the more seasoned flight controllers than the SSR/MPSR, though senior flight controllers cycle back to support in the backroom periodically. One example of the usefulness of this system occurred during the descent of the [[Apollo 11]] [[Apollo Lunar Module|Lunar Module]] [[Apollo 11|''Eagle'']], when "1202" and "1201" program alarms came from the LM. GUIDO [[Steve Bales]], not sure whether to call for an abort, trusted the experts in the guidance backroom, especially [[Jack Garman]], who told him that the problem was a computer overload, but could be ignored if it was intermittent. Bales called "Go!", Flight Director [[Gene Kranz]] accepted the call and the mission continued to success. Without the support of the backroom, a controller might make a bad call based on faulty memory or information not readily available to the person on the console. The nature of quiescent operations aboard the International Space Station (ISS) today is such that the full team is not required for 24/7/365 support. FCR flight controllers accept responsibility for operations without MPSR support most of the time, and the MPSR is only staffed for high-intensity periods of activity, such as joint Shuttle/ISS missions.

[[Unmanned space mission|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.

The flight controllers in the FCR and MPSR are further supported by hardware and software designers, analysts and engineering specialists in other parts of the building or remote facilities. These extended support teams have more detailed analysis tools and access to development and test data that is not readily accessible to the flight control team. These support teams were referred to by the name of their room in Mission Control, the mission operations integration room (MOIR), and are now collectively referred to by the name of their current ___location, the mission evaluation room (MER). While the flight controllers and their backrooms are responsible for real-time decision making, the MOIR/MER provides the detailed data and history needed to solve longer-term issues.

Each flight controller has a unique [[call sign]], which describes the position's 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.

[[Unmanned space mission|Uncrewed U.S. space missions]] also have flight controllers but are managed from separate organizations, either the [[Jet Propulsion Laboratory]] or the Johns Hopkins University [[Applied Physics Laboratory]] for deep-space missions or [[Goddard Space Flight Center]] for near-Earth missions.

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 [[Apollo Command/Service Module|Command and Service Module]] communication systems through [[Apollo 10]], which was afterward assigned to a new position called INCO.

Each flight controller has a unique [[call sign]], which describes the position's 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.

=== Shuttle and space station flight controllers ===

There are currently two groups of flight controllers at [[Johnson Space Center]]: the [[International Space Station]] (ISS) flight controllers and the [[Space Shuttle]] flight controllers.

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 through [[Apollo 10]], which was afterward assigned to a new position called INCO.

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 could leave flight controllers little time for talking, putting pressure on them to respond quickly to potential failures. The Space Shuttle flight controllers generally have limited capability to send commands to the shuttle for system reconfigurations.

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 of 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.

=== Responsibility ===

Flight controllers are responsible for the success of the mission and for the lives of the astronauts under their watch. The Flight Controllers' Creed states that they must "always be aware that suddenly and unexpectedly [they]we may find ourselves in a role where [their]our performance has ultimate consequences"." Well-known actions taken by flight controllers include the following:

* During theThe [[Apollo 11]] moon landing, the [[Lunar Module]] guidance computer beganwas givingoverloaded errorsbecause whichthe threatenedastronauts forgot to abortswitch off their upper-stage radar before switching on the landingdownward-pointing radar. Guidance officer [[Steve Bales]] had only a few seconds to determine whether it was safe to proceed,land whichanyway savedor to abort the mission mere feet above the Moon. Bales was later honored for his role in the mission, when he was selected to accept the [[NASA Group Achievement Award]] from President [[Richard Nixon]] on behalf of the [[Apollo 11]] mission operations team.

* During the launch of [[Apollo 12]], the [[Saturn V]] was struck by lightning which knocked out all [[telemetry]] and multiple command module systems. Seconds before mission abort, EECOM controller [[John Aaron]] determined that switching to the backup electrical power distribution telemetry conditioning would reveal the true nature of the issue.

* During Space Shuttle mission [[STS-51-F]], a [[Space Shuttle Main Engine|main engine]] failed during ascent to orbit. Subsequently, indications were received of a second engine beginning to fail, which would have caused a [[Space Shuttle abort modes|mission abort]], possibly including loss of the shuttle. Booster officer Jenny Howard Stein determined that the anomalous readings on the second engine were a sensor error and not an engine problem. At her direction the crew inhibited the sensor, which saved the mission and possibly the crew.

== Common flight control positions ==

* 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 if EECOM controller [[John Aaron]] had not quickly determined that an obscure cockpit switch could fix the problem.

[[Image:Flight Director insignia.png|thumb|Flight Director's insignia at JSC]]

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.<ref>{{cite web|url=http://spaceflight.nasa.gov/shuttle/reference/mcc/index.html|archive-url=https://web.archive.org/web/20000107041437/http://www.spaceflight.nasa.gov/shuttle/reference/mcc/index.html|url-status=dead|archive-date=7 January 2000|title=HSF|website=spaceflight.nasa.gov|access-date=2 October 2017}}</ref>

===Flight director ===

* During space shuttle mission [[STS-51-F]], a [[Space shuttle main engine|main engine]] failed during ascent to orbit. A second engine began showing signs of failing. If it failed it would cause an [[Space Shuttle abort modes|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.

{{anchor|flight director}}

[[File:Eugene F. Kranz at his console at the NASA Mission Control Center.jpg|thumbnail|right|NASA chief flight director [[Gene Kranz]] at his console on May 30, 1965, in the Mission Operations Control Room, [[Christopher C. Kraft Jr. Mission Control Center|Mission Control Center]], [[Houston]].]]

Leads the flight control team. ''Flight'' has overall operational responsibility for missions and payload operations and for all decisions regarding safe, expedient flight. This person monitors the other flight controllers, remaining in constant verbal communication with them via intercom channels called "loops".

===Flight operations directorate (FOD) ===

=== Common flight control positions ===

Is a representative of the senior management chain at JSC, and is there to help the flight director make those decisions that have no safety-of-flight consequences, but may have cost or public perception consequences. The FOD cannot overrule the flight director during a mission. The former mission operations directorate (MOD) position was renamed FOD when the flight crew operations directorate (FCOD) was merged back with MOD beginning in August 2014.

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.

==={{anchor|CAPCOM}} Spacecraft communicator (CAPCOM)===

====Flight Director (FLIGHT) ====

<!-- This section is linked from [[STS-51-L Mission timeline]] -->

Leads the flight control team. "Flight" has overall operational responsibility for missions and payload operations and for all decisions regarding safe, expedient flight. This person monitors the other flight controllers, remaining in constant verbal communication with them via intercom channels called "loops".

{{for|the video game company|Capcom}}

Generally, only the '''spacecraft communicator''' communicates directly with the crew of a crewed space flight. The acronym dates back to [[Project Mercury]] when the spacecraft was originally termed a "capsule." [[NASA]] felt it important for all communication with the [[astronaut]]s in space to pass through a single individual in the [[Mission Control Center]]. That role was first designated the ''capsule communicator'' or '''CAPCOM''' and was filled by another astronaut, often one of the backup- or support-crew members. NASA believes that an astronaut is most able to understand the situation in the spacecraft and pass information in the clearest way.

For long-duration missions there is more than one CAPCOM, each assigned to a different shift team. After control of U.S. spaceflights moved to the Johnson Space Center in the early 1960s, each CAPCOM used the radio [[call sign|call-sign]] ''Houston''. When non-astronauts are communicating directly with the spacecraft, CAPCOM acts as the communications controller.

====Mission Operations Directorate (MOD) ====

Is a representative of the senior management chain at JSC, and is there to help the flight director 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 Flight Director during a mission.

{{As of | 2011}}, due to the shrinking size of the astronaut corps at the end of the Shuttle program, fewer astronauts are available to perform CAPCOM duties, so non-astronauts from the space flight training and flight controller branches also function as CAPCOM during ISS missions, while the role was filled solely by astronauts for the Apollo and Shuttle missions. Astronauts still take the CAPCOM position during critical events such as docking and EVA.

====Capsule Communicator (CAPCOM)====<!-- This section is linked from [[STS-51-L Mission timeline]] -->

Generally the only person who communicates directly with a manned space crew. During much of the U.S. [[Human spaceflight|manned space program]], [[NASA]] felt it was important for all communication with the [[astronaut]]s in space to pass through a single individual in the [[Mission Control Center]]. That role was designated the ''Capsule Communicator'' or '''CAPCOM''' and was filled by another astronaut, often one of the backup crew members. It is believed that an astronaut is most able to understand the situation in the spacecraft and pass information in the clearest and most efficient way.

In the context of potential crewed missions to Mars, NASA Ames Research Center has conducted field trials of advanced computer-support for astronaut and remote science teams, to test the possibilities for automating CAPCOM.<ref>{{Citation |last=Clancey |first=William |title=Automating CapCom Using Mobile Agents and Robotic Assistants |work=1st Space Exploration Conference: Continuing the Voyage of Discovery |url=https://arc.aiaa.org/doi/abs/10.2514/6.2005-2659 |access-date=November 26, 2018 |publisher=American Institute of Aeronautics and Astronautics |doi=10.2514/6.2005-2659 |last2=Sierhuis |first2=Maarten |last3=Alena |first3=Richard |last4=Dowding |first4=John |last5=Graham |first5=Jeffrey |last6=Rupert |first6=Shannon |last7=Berrios |first7=Daniel |last8=Tyree |first8=Kim |last9=Hirsh |first9=Robert|hdl=2060/20050157849 |hdl-access=free }}</ref>

For long duration missions, there are 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, each CAPCOM uses the radio [[call sign]] ''Houston.'' When non-astronauts are communicating directly with the spacecraft, CAPCOM acts as the communications controller. CAPCOMs have sometimes been jokingly addressed as ''[[Uhura]]'', a reference to the communications expert in the TV show ''[[Star Trek]]''.

=== Other common flight control positions ===

Today, non-astronauts from the Space Flight Training branch also function as CAPCOM during ISS missions, while the role is filled solely by astronauts for shuttle missions.

; Flight surgeon

====Flight Surgeon (SURGEON)====

Directs: allThe operationalflight surgeon directs all medical activities concerned withduring the mission, including– the status of the flightmonitors crew. Monitorshealth crewvia healthtelemetry, provides crew consultation, and advises the flight director of the crew's health status. A directprivate communicationscommunication loopchannel can be established between the mission astronauts and the flight surgeon, in accordanceto withprovide doctor-patientdoctor–patient confidentiality.

====; Public Affairsaffairs Officerofficer (PAO)====

: Provides mission commentary to supplement and explain air-to-ground transmissions and flight control operations to the news media and the public. The individual filling this role is often referred to colloquially as ''The Voice of Mission Control''.

== See also ==

=== Apollo flight control positions ===

; Space centers and mission control center

The flight control positions used during the Apollo era predominantly were identical to the positions used for the Mercury and Gemini vehicles. This was because of the similarity of the vehicle design of the capsules used for the three programs.

{{main|Mission control center}}

* [[Baikonur Cosmodrome]] (launch control center for [[Roscosmos]] in [[Baikonur]], Kazakhstan)

* [[Beijing Aerospace Command and Control Center]] (mission control center for the [[China National Space Administration]] in [[Beijing]])

* [[Christopher C. Kraft Jr. Mission Control Center]] (mission control center for [[NASA]] in [[Houston]])

* [[John H. Chapman Space Centre]] (robotics mission control center for the [[Canadian Space Agency]] in [[Longueuil, Quebec]])

* [[European Space Operations Centre]] (mission control center for the [[European Space Agency]] in [[Darmstadt]], Germany)

* [[German Space Operations Center]] (mission control center for the [[German Aerospace Center]], including [[Columbus Control Centre]] for the European Space Agency in [[Oberpfaffenhofen]], Germany)

* [[Guiana Space Centre]] (launch control center for the [[European Space Agency]] in [[Kourou]], French Guiana)

* [[Johnson Space Center]] (mission control center for NASA in [[Houston]], Texas)

* [[Kennedy Space Center]] (launch control center for NASA in [[Cape Canaveral]], Florida)

* [[Payload Operations and Integration Center]] (located at the [[Marshall Space Flight Center]] in Huntsville, Alabama)

* [[RKA Mission Control Center]] (mission control center for Roscomos near Moscow Russia)

* [[Tanegashima Space Center]] (launch control center for [[JAXA]], [[Tanegashima Island]], [[Japan]])

* [[Tsukuba Space Center]] (mission control center for [[JAXA]], [[Tsukuba]], [[Japan]])

== References ==

====Booster Systems Engineer (BOOSTER)====

{{Reflist}}

Monitored and evaluated performance of propulsion-related aspects of the launch vehicle during prelaunch and ascent. During the Apollo program there were three Booster positions, who worked only until [[Trans Lunar Injection|Trans Lunar Injection (TLI)]]; after that, their consoles were vacated. Booster had the power to send an abort command to the spacecraft. All Booster technicians were employed at the [[Marshall Space Flight Center]] and reported to JSC for the launches.

====Control Officer (CONTROL)====

Responsible for the [[Lunar Module]] guidance, navigation and control systems. Essentially the equivalent of the GNC for the Lunar Module.

====Electrical, Environmental and Consumables Manager (EECOM)====

Monitored [[cryogenic]] levels for [[fuel cell]]s, and cabin cooling systems; electrical distribution systems; cabin pressure control systems; and vehicle lighting systems. EECOM originally stood for Electrical, Environmental and COMmunication systems. The [[Project Apollo|Apollo]] EECOM was responsible for 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 Liebergot|Seymour "Sy" Liebergot]], the EECOM on duty at the time of the oxygen tank explosion on [[Apollo 13]] and [[John Aaron]], who is credited with saving the [[Apollo 12]] mission after the spacecraft was struck by lightning during launch.

* Apollo EECOM : Journey of a Lifetime: Apogee Books Space Series 31 (2003) ISBN 1-896522-96-3

====Flight Activities Officer (FAO)====

Planned and supported crew activities, checklists, procedures and schedules.

====Flight Dynamics Officer (FDO or FIDO)====

Responsible for the flight path of the space vehicle, both atmospheric and [[Orbital spaceflight|orbital]]. During lunar missions the FDO was also responsible for the lunar [[trajectory]]. The FDO monitored vehicle performance during the powered flight phase and assessed abort modes, calculated orbital maneuvers and resulting trajectories, and monitored vehicle flight profile and energy levels during [[re-entry]].

====Guidance Officer (GUIDANCE or GUIDO)====

Monitored onboard [[Apollo PGNCS|navigational systems]] and onboard [[Apollo Guidance Computer|guidance computer]] software. Responsible for determining the position of the spacecraft in space. One well-known Guidance officer was [[Steve Bales]], who gave the "go" call when the [[Apollo 11]] [[Apollo guidance computer|guidance computer]] came close to overloading during the first lunar descent.

====Guidance, Navigation, and Controls Systems Engineer (GNC)====

Monitored all vehicle guidance, navigation and control systems. Also responsible for propulsion systems such as the Reaction and Control System (RCS) and the CSM main engine.

MPSR positions

* ''H-Bar'' - A [[Skylab]]-only mpsr position, provided expert support monitoring of the [[Control moment gyroscope| Control Moment Gyroscopes]].

====Integrated Communications Officer (INCO)====

Responsible for all data, voice and video communications systems, including monitoring the configuration of in-flight communications and [[instrumentation]] systems. Duties also included monitoring the [[telemetry]] link between the vehicle and the ground, and overseeing the [[uplink]] command and control processes. The position was formed from the combination of LEM and CSM Communicator positions.

====Network (NETWORK)====

Supervised the network of ground stations that relayed telemetry and communications from the spacecraft.

====Organization and Procedures Officer (O&P)====

Supervised the application of mission rules and established techniques to the conduct of the flight.

====Retrofire Officer (RETRO)====

Drew up abort plans and was responsible for determination of [[retrorocket|retrofire ]] times. During lunar missions the RETRO planned and monitored Trans Earth Injection (TEI) maneuvers, where the [[Apollo Command/Service Module|Apollo Service Module]] fired its engine to return to earth from the moon.

====Telemetry, Electrical, EVA Mobility Unit Officer (TELMU)====

Monitored the [[Lunar Module]] electrical and environmental systems, plus lunar astronaut spacesuits. Essentially the equivalent of the EECOM for the Lunar Module.

===Shuttle flight control positions===

Many Apollo program mission control positions were carried forward to the space shuttle program. However, other positions were eliminated or redefined, and new positions were added.

Positions remaining generally the same:

* Booster

* FAO

* FDO

* Guidance (became Guidance and Procedures Officer, or GPO)

* GNC

* INCO (became ''Instrumentation'' and Communications Officer)

Positions eliminated or modified:

* RETRO

* EECOM (duties split up)

* TELMU

* CONTROL

====Assembly and Checkout Officer (ACO)====

Responsible for all shuttle-based activities related to construction and operation of the Space Station, including logistics and transfer items stored in a Multi-Purpose Logistics Module (MPLM) or [[Spacehab]]. Also responsible for all shuttle payloads, from Spacehab to the [[Hubble Space Telescope]] to deployable satellites. ACO was formerly known as PAYLOADS.

====Booster Systems Engineer (BOOSTER)====

Monitors and evaluated performance of propulsion-related aspects of the launch vehicle during prelaunch and ascent, including the main engines and solid rocket boosters.

====Data Processing System Engineer (DPS)====

Responsible for data processing systems in a space flight. This includes monitoring the onboard [[Space Shuttle program#Computerized fly-by-wire digital flight control|General Purpose Computers (GPCs)]], flight-critical, launch and payload data buses, the Multi-function Electronic Display System (MEDS), Solid-State Mass Memory (SSMM) units, flight critical and payload Multiplexer/De-multiplexer (MDM) units, Master Timing Unit (MTU), Backup Flight Control (BFC) units and system-level software.

The [[Space Shuttle program#Computerized fly-by-wire digital flight control|space shuttle general purpose computers]] are a critical subsystem, and the vehicle cannot fly without them.

====Emergency, Environmental, and Consumables Management (EECOM)====

EECOM's revamped shuttle responsibilities include the atmospheric pressure control and revitalization systems, the cooling systems (air, water, and freon), and the supply/waste water system.

'''MPSR positions'''

* ''Life Support'' - monitors atmospheric pressure control systems, O2/N2/CO2 maintenance and management, air cooling equipment, waste water systems,

* ''Thermal'' - monitors water and freon coolant loop systems, supply water maintenance

====Electrical Generation and Integrated Lighting Systems Engineer (EGIL)====

Monitors [[cryogenic]] levels for the [[fuel cells]], electrical generation and distribution systems on the spacecraft, and vehicle lighting. This is a portion of the job formerly done by EECOM.

'''MPSR positions'''

* ''EPS'' - provides expert support monitoring of the fuel cells, cryo system, and electrical bus system

====Extravehicular Activity Officer (EVA)====

Responsible for all spacesuit and spacewalking-related tasks, equipment and plans when the EVA takes place from the shuttle.

====Flight Activities Officer (FAO)====

Plans and supports crew activities, checklists, procedures, schedules, and timelines.

====Flight Dynamics Officer (FDO or FIDO)====

Responsible for the flight path of the space shuttle, both atmospheric and [[Orbital spaceflight|orbital]]. 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]].

'''MPSR positions'''

* ''Abort Support'' (ascent only) - provides expert support during the powered flight portion of an RTLS or TAL

* ''ARD Support'' (ascent only) - maintains the Abort Region Determinator processor which is used to predict trajectory capabilities during powered flight

* ''Ascent Support'' team (ascent only) - monitor the winds and weather at the launch site, help compute day-of-launch updates

* ''Dynamics'' - maintains the inputs to the Mission Operation Computer for all processors

* ''Entry Console'' - provides expert support for entry, approach, and landing

* ''Entry Support'' team (ascent and entry) - monitor the winds and weather at the various potential landing sites, prepare trajectory adjustments

* ''Landing Support Officer'' (LSO) team - maintain the airspace at any landing site, dispatch Search and Rescue teams if needed, act as first liaison in case of a landing outside the US

* ''Nav Support'' team - responsible for maintaining the on-board navigation (telemetry) and the ground navigation (tracking)

* ''Profile Support'' (rendezvous only) - assists the FDO with rendezvous profile evaluation and determination

* ''Range Safety'' team (ascent only) - track the falling External Tank and Solid Rocket Boosters

* ''Targeting'' (ascent only) - provides expert support for Abort to Orbit (ATO) or Abort Once Around (AOA) trajectories

* ''Track'' - coordinates tracking site data flow and data requests

* ''Weather'' - a member of the Spaceflight Meteorology Group who provides world-wide weather data

'''External links'''

* [http://space.balettie.com/ Former FDO Roger Balettie]

* [http://space.balettie.com/FDO.html Orbit/Rendezvous FDO Operational Overview]

* [http://home.houston.rr.com/edelen/me.html Current FDO Chris Edelen]

* [http://www.geocities.com/spaceshot2000/mcc.htm Former Targeting Michael Grabois], behind the scenes at a launch from the MPSR

====Ground Controller (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]].

====Guidance, Navigation, and Controls Systems Engineer (GNC)====

Monitors all shuttle guidance, navigation and control systems.

====Instrumentation and Communications Officer (INCO)====

Responsible for all data, voice and video communications systems, including monitoring the configuration of in-flight communications and instrumentation systems. Duties also included monitoring the telemetry link between the vehicle and the ground, and overseeing the uplink command and control processes. This position is a direct evolution of the Integrated Communications Officer from the Apollo program.

====Maintenance, Mechanical, And Crew Systems (MMACS)====

Responsible for [[Space Shuttle program|space shuttle]] structural and mechanical systems, monitoring [[auxiliary power unit]]s and [[hydraulic]] systems, managing payload bay and vent door operations, landing gear/deceleration systems, and monitoring the orbiter docking system. MMACS also follows use of onboard crew hardware and in-flight equipment maintenance. This represents another portion of the job formerly done by EECOM, with additional responsibilities added by the specific requirements of space shuttle operations.

'''MPSR positions'''

* ''MECH'' - provides expert support monitoring of mechanical, hydraulic, and landing gear systems

* ''MECH 2'' - provides extra support during the dynamic ascent and entry phases of flight

* ''IFM'' - In-Flight Maintenance support

* ''Crew Systems'' - responsible for operations of onboard crew hardware and the crew's Launch and Entry Suits

* ''Photo/TV'' - responsible for the "loose" camera operation and maintenance, such as still cameras and camcorders, and the integration of video into and out of the orbiter's TV monitors

====Payload Deployment and Retrieval System (PDRS)====

Responsible for [[Space Shuttle program|space shuttle]] [[Remote Manipulator System|remote manipulator system]], also known as the Remote Manipulator System (RMS) or "robot arm".

====Propulsion Engineer (PROP)====

Manages the [[Reaction control system|reaction control]] thrusters and [[Orbital Maneuvering System|orbital maneuvering]] engines during all phases of flight, monitors fuel usage and propellant tank status, and calculates optimal sequences for thruster firings.

====Rendezvous (RNDZ)====

Responsible for activities such as trajectory operations related to the rendezvous and docking/capture with another spacecraft, including [[Mir]], the ISS, and satellites such as the Hubble Space Telescope.

====Trajectory Officer (TRAJ)====

Assists the FDO during time-critical operations, responsible for maintaining the various processors that help determine the shuttle's current and potential trajectories. A FDO is certified as a TRAJ first. Shares the FCR with FDO.

=== ISS flight control positions ===

The International Space Station flight control positions used by NASA in Houston are different than those used by previous NASA programs. This is due primarily to reduce confusion from having the same name used in two different rooms during the same operations, such as when the space shuttle is conducting mated operations with the space station. There are also differences in the control positions because of the different nature in the way the space station operates compared to the space shuttle. The following is a list of those flight controllers located in Mission Control Center - Houston. There are several other control centers which house dozens of other flight controllers that support the vastly complex vehicle.

====Assembly and Checkout Officer (ACO)====

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)====

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 and is responsible for docking the ISS with other vehicles.

'''MPSR positions'''

* ''HawkI'' - Pronounced (Hawk-eye) - provides expert support monitoring of all US GNC systems, leaving the ADCO to coordinate with other flight controllers and MCC-M. Hawki is actually a strung-together set of common engineering abbreviations for quantities that affect or reflect ISS attitude, primarily chosen because they fit well enough to make a name:

** H - Momentum. The ISS attitude control algorithm uses momentum exchange through each orbit to minimize propellant usage.

** a - attitude.

** ω - angular velocity.

** k - kinetic energy.

** I - moment of inertia.

====Communication and Tracking Officer (CATO)====

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)====

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)====

Responsible for all spacesuit and spacewalking-related tasks, equipment and plans when the EVA takes place from the ISS.

====Onboard, Data, Interfaces and Networks (ODIN)====

Responsible for the U.S. Command and Data Handling System, including hardware, software, networks, and interfaces with International Partner avionics systems.

====Operations Planner (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.

====Operations Support Officer (OSO)====

Charged with those logistics support functions that address on-orbit maintenance, support data and documentation, logistics information systems, maintenance data collection and maintenance analysis. The OSO is 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)====

Manages the power generation, storage, and power distribution capabilities.

====Robotics Operations Systems Officer (ROBO)====

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)====

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)====

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.

====Visiting Vehicle Officer (VVO)====

A specialist position, the VVO is the liaison between the ISS and "visiting vehicles" such as Progress or Soyuz.

== See also ==

* [[Baikonur Cosmodrome]]

* [[European Space Operations Centre|ESOC]]

* [[Centre Spatial Guyanais|Guiana Space Center]]

* [[Tanegashima Space Center]]

* [[Mission Control Center]]

* [[Johnson Space Center]]

* [[Kennedy Space Center]]

* [[Space Shuttle program]]

* [[Apollo program]]

* [[John Hodge (engineer)]]

* [[Eugene Kranz]]

* [[Christopher C. Kraft, Jr.]]

* [[Glynn Lunney]]

* [[John Aaron]]

* [[Jay Greene]]

* [[Steve Bales]]

==References= Sources ===

{{refbegin}}

* {{cite book| first = Charles | last = Murray | coauthors = Cox, Catherine Bly | title = Apollo: The Race to the Moon | ___location = New York | publisher = Simon and Schuster | year = 1989 | id = ISBN 0-671-61101-1}}

* {{cite book |first = Sy |last = Liebergot |title = Apollo EECOM : Journey of a Lifetime |series = Apogee Books Space Series |volume = 31 |year = 2003 |isbn = 1-896522-96-3 }}

* {{cite book |first1 = Charles |last1 = Murray |last2 = Cox |first2 = Catherine Bly |title = Apollo: The Race to the Moon |___location = New York, NY |publisher = [[Simon and Schuster]] |year = 1989 |isbn = 0-671-61101-1 }}

{{refend}}

== External links ==

* [https://web.archive.org/web/20111208175016/http://spacestationlive.jsc.nasa.gov/operations.html Space Station Live!]

* [http://www.cr.nps.gov/nr/twhp/wwwlps/lessons/101space/101visual2.htm National Park Service mission control page]

* [http://www.space-technology.com/projects/johnsoon/ Space-Technology.com mission control page]

{{DEFAULTSORT:Flight Controller}}

[[Category:NASA flight controllers| ]]

[[Category:NASA flight controllers|*]]

[[Category:NASA people|*]]