Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Flight controller
open-in-new
<h2 id="nasas-flight-controllers">NASA's flight controllers</h2> <p class="note">For a more comprehensive list, see <a href="/facts/List_of_NASA%2527s_flight_control_positions/E999csCG">List of NASA's flight control positions</a>.</p> <p>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 <a href="/facts/Abort_(computing)/Q9hCm8EM">abort</a> 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 <a href="/facts/Launch_status_check/l1d3c2AK">launch status check</a>. 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. </p><p>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 <a href="/facts/Apollo_11/BdUKVnQP">Apollo 11</a> <a href="/facts/Apollo_Lunar_Module/XtvQS5K5">Lunar Module</a> <a href="/facts/Apollo_11/BdUKVnQP"><i>Eagle</i></a>, when "1202" and "1201" program alarms came from the LM. GUIDO <a href="/facts/Steve_Bales/mDvAKtuz">Steve Bales</a>, not sure whether to call for an abort, trusted the experts in the guidance backroom, especially <a href="/facts/Jack_Garman/kgdeb2PI">Jack Garman</a>, who told him that the problem was a computer overload, but could be ignored if it was intermittent. Bales called "Go!", Flight Director <a href="/facts/Gene_Kranz/6Ku2jm40">Gene Kranz</a> 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. </p><p>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. </p><p><a href="/facts/Unmanned_space_mission/Frlbbkvu">Uncrewed U.S. space missions</a> also have flight controllers but are managed from separate organizations, either the <a href="/facts/Jet_Propulsion_Laboratory/zPXnxRBf">Jet Propulsion Laboratory</a> or the Johns Hopkins University <a href="/facts/Applied_Physics_Laboratory/PN4H87V9">Applied Physics Laboratory</a> for deep-space missions or <a href="/facts/Goddard_Space_Flight_Center/WfoEKknM">Goddard Space Flight Center</a> for near-Earth missions. </p><p>Each flight controller has a unique <a href="/facts/Call_sign/k3Y1upDl">call sign</a>, which describes the position's responsibilities. The call sign and responsibility refer to the particular <i>console</i>, not just the person, since missions are managed around the clock and with each shift change a different person takes over the console. </p><p>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 <a href="/facts/Command_and_service_module/rfoTgzFx">command and service module</a> communication systems through <a href="/facts/Apollo_10/SYbSPPHM">Apollo 10</a>, which was afterward assigned to a new position called INCO. </p> <h3>Responsibility</h3> <p>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 we may find ourselves in a role where our performance has ultimate consequences." Well-known actions taken by flight controllers include: </p> <ul><li>The <a href="/facts/Apollo_11/BdUKVnQP">Apollo 11</a> <a href="/facts/Lunar_Module/XtvQS5K5">Lunar Module</a> computer was overloaded because the astronauts forgot to switch off their upper-stage radar before switching on the downward-pointing radar. Guidance officer <a href="/facts/Steve_Bales/mDvAKtuz">Steve Bales</a> had only a few seconds to determine whether it was safe to land anyway or 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 <a href="/facts/NASA_Group_Achievement_Award/yDTfhE0W">NASA Group Achievement Award</a> from President <a href="/facts/Richard_Nixon/HS8uXAoC">Richard Nixon</a> on behalf of the <a href="/facts/Apollo_11/BdUKVnQP">Apollo 11</a> mission operations team.</li> <li>During the launch of <a href="/facts/Apollo_12/TyLvYjhw">Apollo 12</a>, the <a href="/facts/Saturn_V/WhpUEFJM">Saturn V</a> was struck by lightning which knocked out all <a href="/facts/Telemetry/Mz9czXTl">telemetry</a> and multiple command module systems. Seconds before mission abort, EECOM controller <a href="/facts/John_Aaron/mzEVpbNA">John Aaron</a> determined that switching to the backup electrical power distribution telemetry conditioning would reveal the true nature of the issue.</li> <li>During Space Shuttle mission <a href="/facts/STS-51-F/znwAzdNu">STS-51-F</a>, a <a href="/facts/Space_Shuttle_Main_Engine/vGkj6Vxm">main engine</a> failed during ascent to orbit. Subsequently, indications were received of a second engine beginning to fail, which would have caused a <a href="/facts/Space_Shuttle_abort_modes/AAwsIPm9">mission abort</a>, 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.</li></ul> <h2 id="common-flight-control-positions">Common flight control positions</h2> <p>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.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> </p> <h3>Flight director</h3> <p>Leads the flight control team. <i>Flight</i> 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". </p> <h3>Flight operations directorate (FOD)</h3> <p>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. </p> <h3> Spacecraft communicator (CAPCOM)</h3> <p class="note">For the video game company, see <a href="/facts/Capcom/XBPVAyhV">Capcom</a>.</p> <p>Generally, only the spacecraft communicator communicates directly with the crew of a crewed space flight. The acronym dates back to <a href="/facts/Project_Mercury/H8zqFzbC">Project Mercury</a> when the spacecraft was originally termed a "capsule." <a href="/facts/NASA/TIMCV0yV">NASA</a> felt it important for all communication with the <a href="/facts/Astronaut/HB1bd6Lz">astronauts</a> in space to pass through a single individual in the <a href="/facts/Mission_Control_Center/RvXSH1AI">Mission Control Center</a>. That role was first designated the <i>capsule communicator</i> 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. </p><p>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 <a href="/facts/Call_sign/k3Y1upDl">call-sign</a> <i>Houston</i>. When non-astronauts are communicating directly with the spacecraft, CAPCOM acts as the communications controller. </p><p>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. </p><p>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.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p> <h3>Other common flight control positions</h3> Flight surgeon The flight surgeon directs all medical activities during the mission – monitors crew health via telemetry, provides crew consultation, and advises the flight director. A private communication channel can be established between astronauts and the flight surgeon, to provide doctor–patient confidentiality. Public affairs officer (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 <i>The Voice of Mission Control</i>. <h2 id="see-also">See also</h2> Space centers and mission control center <p class="note">Main article: <a href="/facts/Mission_control_center/RvXSH1AI">Mission control center</a></p> <ul><li><a href="/facts/Baikonur_Cosmodrome/sk16LwcH">Baikonur Cosmodrome</a> (launch control center for <a href="/facts/Roscosmos/GzWfae7U">Roscosmos</a> in <a href="/facts/Baikonur/Axz7dYJq">Baikonur</a>, Kazakhstan)</li> <li><a href="/facts/Beijing_Aerospace_Command_and_Control_Center/KwwkNNXd">Beijing Aerospace Command and Control Center</a> (mission control center for the <a href="/facts/China_National_Space_Administration/q3s4bGYt">China National Space Administration</a> in <a href="/facts/Beijing/Bg4puFBv">Beijing</a>)</li> <li><a href="/facts/Christopher_C._Kraft_Jr._Mission_Control_Center/8DxahkB2">Christopher C. Kraft Jr. Mission Control Center</a> (mission control center for <a href="/facts/NASA/TIMCV0yV">NASA</a> in <a href="/facts/Houston/1v8AwQUN">Houston</a>)</li> <li><a href="/facts/John_H._Chapman_Space_Centre/6K9qoURR">John H. Chapman Space Centre</a> (robotics mission control center for the <a href="/facts/Canadian_Space_Agency/zL2njRvS">Canadian Space Agency</a> in <a href="/facts/Longueuil%2c_Quebec/eGXbjVFu">Longueuil, Quebec</a>)</li> <li><a href="/facts/European_Space_Operations_Centre/RQ0ASFvU">European Space Operations Centre</a> (mission control center for the <a href="/facts/European_Space_Agency/L8YRNV0C">European Space Agency</a> in <a href="/facts/Darmstadt/UzVdfNVQ">Darmstadt</a>, Germany)</li> <li><a href="/facts/German_Space_Operations_Center/7INgPwXD">German Space Operations Center</a> (mission control center for the <a href="/facts/German_Aerospace_Center/nIeKtKqd">German Aerospace Center</a>, including <a href="/facts/Columbus_Control_Centre/bx5TH8JF">Columbus Control Centre</a> for the European Space Agency in <a href="/facts/Oberpfaffenhofen/MImqPVUT">Oberpfaffenhofen</a>, Germany)</li> <li><a href="/facts/Guiana_Space_Centre/hp6TSJ6W">Guiana Space Centre</a> (launch control center for the <a href="/facts/European_Space_Agency/L8YRNV0C">European Space Agency</a> in <a href="/facts/Kourou/wvDVpjpJ">Kourou</a>, French Guiana)</li> <li><a href="/facts/Johnson_Space_Center/rN6Jvhqe">Johnson Space Center</a> (mission control center for NASA in <a href="/facts/Houston/1v8AwQUN">Houston</a>, Texas)</li> <li><a href="/facts/Kennedy_Space_Center/zmwszuPr">Kennedy Space Center</a> (launch control center for NASA in <a href="/facts/Cape_Canaveral/DsFRGqWm">Cape Canaveral</a>, Florida)</li> <li><a href="/facts/Payload_Operations_and_Integration_Center/vUB1P2Hg">Payload Operations and Integration Center</a> (located at the <a href="/facts/Marshall_Space_Flight_Center/Q5XqseqT">Marshall Space Flight Center</a> in Huntsville, Alabama)</li> <li><a href="/facts/RKA_Mission_Control_Center/4NzcqzG3">RKA Mission Control Center</a> (mission control center for Roscomos near Moscow Russia)</li> <li><a href="/facts/Tanegashima_Space_Center/PKLppwl8">Tanegashima Space Center</a> (launch control center for <a href="/facts/JAXA/ofUpflgf">JAXA</a>, <a href="/facts/Tanegashima_Island/NKd6EV6K">Tanegashima Island</a>, <a href="/facts/Japan/U5mz0SRT">Japan</a>)</li> <li><a href="/facts/Tsukuba_Space_Center/DeUVrM5f">Tsukuba Space Center</a> (mission control center for <a href="/facts/JAXA/ofUpflgf">JAXA</a>, <a href="/facts/Tsukuba/0Juuaxe7">Tsukuba</a>, <a href="/facts/Japan/U5mz0SRT">Japan</a>)</li></ul> <h3>Sources</h3> <ul><li>Liebergot, Sy (2003). <i>Apollo EECOM : Journey of a Lifetime</i>. Apogee Books Space Series. Vol. 31. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 1-896522-96-3.</li> <li>Murray, Charles; Cox, Catherine Bly (1989). <i>Apollo: The Race to the Moon</i>. New York, NY: <a href="/facts/Simon_and_Schuster/pESq8Dxl">Simon and Schuster</a>. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 0-671-61101-1.</li></ul> <h2 id="external-links">External links</h2> <ul><li><a href="https://web.archive.org/web/20111208175016/http://spacestationlive.jsc.nasa.gov/operations.html">Space Station Live!</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"HSF". spaceflight.nasa.gov. Archived from the original on 7 January 2000. Retrieved 2 October 2017. <a href="https://web.archive.org/web/20000107041437/http://www.spaceflight.nasa.gov/shuttle/reference/mcc/index.html" target="_blank">https://web.archive.org/web/20000107041437/http://www.spaceflight.nasa.gov/shuttle/reference/mcc/index.html</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>William Clancey, Maarten Sierhuis, Richard Alena, John Dowding, Jeffrey Graham, Shannon Rupert, Daniel Berrios, Kim Tyree, Robert Hirsh, W. Brent Garry, Abigail Semple, Simon Buckingham Shum, and Nigel Shadbolt (2005). "Automating CapCom Using Mobile Agents and Robotic Assistants", 1st Space Exploration Conference: Continuing the Voyage of Discovery. Space Exploration Conferences. Accessed online Nov 26, 2018: https://arc.aiaa.org/doi/abs/10.2514/6.2005-2659 <a href="https://arc.aiaa.org/doi/abs/10.2514/6.2005-2659" target="_blank">https://arc.aiaa.org/doi/abs/10.2514/6.2005-2659</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> </ol>