Search NASA⌕ Search

SEARCH · Search NASA

Results for “Johnson Space Center”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 343 records · Page 19

Autonomous Agents and Intelligent Assistants for Exploration Operations

Human exploration of space will involve remote autonomous crew and systems in long missions. Data to earth will be delayed and limited. Earth control centers will not receive continuous real-time telemetry data, and there will be communication round trips of up to one hour. There will be reduced human monitoring on the planet and earth. When crews are present on the planet, they will be occupied with other activities, and system management will be a low priority task. Earth control centers will use multi-tasking "night shift" and on-call specialists. A new project at Johnson Space Center is developing software to support teamwork between distributed human and software agents in future interplanetary work environments. The Engineering and Mission Operations Directorates at Johnson Space Center (JSC) are combining laboratories and expertise to carry out this project, by establishing a testbed for hWl1an centered design, development and evaluation of intelligent autonomous and assistant systems. Intelligent autonomous systems for managing systems on planetary bases will commuicate their knowledge to support distributed multi-agent mixed-initiative operations. Intelligent assistant agents will respond to events by developing briefings and responses according to instructions from human agents on earth and in space.

Malin, Jane T.↗

Enhancing International Space Station (ISS) Mission Control Center (MCC) Operations Using Tcl/Tk

This paper will discuss the use of Tcl/Tk to enhance the abilities of flight controllers to control the International Space Station (ISS) from the Mission Control Center (MCC) at the Johnson Space Center. We will discuss why existing tools where not able to meet these needs as easily as Tcl/Tk. In addition, we will also discuss how we interfaced with the existing MCC infrastructure to receive ISS telemetry, find servers, register services, and send commands to ISS.

OHagan, Brian↗

Addressing Human Error in International Space Station Flight Control Teams: Advances in Ground Training for Science Operators

In flight control, as with any human in the loop system, operator error is an inevitable reality. On the International Space Station (ISS) where crew time and physical resources are precious and often irreplaceable, operator errors can result in significant, irreversible consequences. Flight controllers at the Payload Operations Integration Center (POIC) located at NASA's Marshall Space Flight Center (MSFC) in Huntsville, Alabama know this reality well. At the POIC, operator errors can be caused by a variety of factors, from poor hardware or software design to environmental factors such as time pressure or fatigue. The most difficult errors to address, however, are those which result from ineffective teamwork. To address these teamwork errors, trainers at the POIC have drawn best practices from high reliability industries as well as from our sister ISS control center at the Johnson Space Center (JSC) in Houston, Texas, to develop and implement a new training program focused specifically on teamwork skills. This training program, called Team Skills Training, is inspired by modern and historical training programs developed by NASA and is specifically tailored to the needs of the payload operations flight control team at the POIC. The program consists of training for both certified and trainee flight controllers, and covers team skills topics such as situational awareness, leadership, and communication skills. To maximize effectiveness, the program uses novel instructional techniques which extend beyond the classroom to encourage students to apply what they have learned to their day to day work. Minimizing operator errors in flight control is an endeavor which requires constant vigilance and continuous improvement. At the POIC, Team Skills Training is an important step in this journey.

Harris, Samantha S.↗

NASA Medical Response to Human Spacecraft Accidents

Manned space flight is risky business. Accidents have occurred and may occur in the future. NASA's manned space flight programs, with all their successes, have had three fatal accidents, one at the launch pad and two in flight. The Apollo fire and the Challenger and Columbia accidents resulted in a loss of seventeen crewmembers. Russia's manned space flight programs have had three fatal accidents, one ground-based and two in flight. These accidents resulted in the loss of five crewmembers. Additionally, manned spacecraft have encountered numerous close calls with potential for disaster. The NASA Johnson Space Center Flight Safety Office has documented more than 70 spacecraft incidents, many of which could have become serious accidents. At the Johnson Space Center (JSC), medical contingency personnel are assigned to a Mishap Investigation Team. The team deploys to the accident site to gather and preserve evidence for the Accident Investigation Board. The JSC Medical Operations Branch has developed a flight surgeon accident response training class to capture the lessons learned from the Columbia accident. This presentation will address the NASA Mishap Investigation Team's medical objectives, planned response, and potential issues that could arise subsequent to a manned spacecraft accident. Educational Objectives are to understand the medical objectives and issues confronting the Mishap Investigation Team medical personnel subsequent to a human space flight accident.

Patlach, Robert↗

Liquid Oxygen/Liquid Methane Component Technology Development at MSFC

The National Aeronautics & Space Administration (NASA) has identified Liquid Oxygen (LOX)/Liquid Methane (LCH4) as a potential propellant combination for future space vehicles based upon exploration studies. The technology is estimated to have higher performance and lower overall systems mass compared to existing hypergolic propulsion systems. Besides existing in-house risk reduction activities, NASA has solicited from industry their participation on component technologies based on the potential application to the lunar ascent main engine (AME). Contracted and NASA efforts have ranged from valve technologies to engine system testbeds. The application for the AME is anticipated to be an expendable, pressure-fed engine for ascent from the moon at completion of its lunar stay. Additionally, the hardware is expected to provide an abort capability prior to landing, in the event that descent systems malfunction. For the past 4 years, MSFC has been working with the Glenn Research Center and the Johnson Space Center on methane technology development. This paper will focus on efforts specific to MSFC in pursuing ignition, injector performance, chamber material assessments and cryogenic valve technologies. Ignition studies have examined characteristics for torch, spark and microwave systems. Injector testing has yielded insight into combustion performance for shear, swirl and impinging type injectors. The majority of chamber testing has been conducted with ablative and radiatively cooled chambers with planned activities for regenerative and transpiration cooled chambers. Lastly, an effort is underway to examine the long duration exposure issues of cryogenic valve internal components. The paper will summarize the status of these efforts.

Robinson, Joel W.↗

One Giant Leap to Protect All Mankind: An Overview of the Lunar Receiving Laboratory

Motivation. In 1961, President John F. Kennedy charged the nation "to land a man on the moon and return him safely to Earth." Eight years later, the Apollo 11 astronauts splashed down in the Pacific Ocean after this first 8-day journey to the moon. As humans had never ventured to another extraterrestrial body, the U.S. government noted the great uncertainty associated with the unknown exposures related to this historic mission. Overview. With this uncertainty in mind, a newly formed Interagency Committee on Back Contamination (ICBC) was established to review the potential for lunar contaminants and establish the prevention of their escape into the biosphere during crew and sample recovery operations from the floating command module to the mobile quarantine facility on the recovery ship and return to the Johnson Space Center. Significance. As a result of the ICBC recommendations, in 1966 NASA planned and built the Lunar Receiving Laboratory (LRL) at the Johnson Space Center in Houston, Texas. The LRL served a great role in service of human space exploration to quarantine Apollo crewmembers, their space vehicles, and the lunar samples collected. Almost an afterthought in the space race to the Moon, the 83,000-square-foot LRL was designed and completed in 1967 for $7.8 million. The core purpose of the LRL was "to protect the public's health, agriculture, and other living resources; to provide lunar sample distribution to approved scientific investigators; and to preserve the scientific integrity of the lunar samples at all times." Its layout was comprised of three major zones: a quarantined Crew Area, a separate but also quarantined Sample Operations Area, and a Support and Administration Area outside the controlled biological barrier. This facility required trained personnel to live and perform within it for several weeks post-flight, to include astronaut crewmembers, flight surgeons, scientists, and vehicle recovery engineers. The LRL holds memories of these historic events but has since been repurposed for NASA's medical and environmental sciences activities, in what is now known as Building 37. As we approach its 50th anniversary, the LRL story will end in demolition as NASA advances its facilities for the next steps in human exploration of space. Learning Objectives: 1. To capture the historical relevance of the NASA Lunar Receiving Laboratory 2. To understand the requirements of receiving crew and samples from the moon for the first time 3. To describe the facility capabilities in protection of public health.

Hayes, Judith↗

LITE data processing

The Lidar In-space Technology Experiment (LITE) was a payload onboard the Space Shuttle Discovery as part of the September 1994 STS-64 mission. LITE successfully made both atmospheric and surface measurements at the 355 nm, 532 nm, and 1064 nm wavelengths [Winker et al., 1996]. At mission completion, nearly 45 Gbytes of data had been obtained. As the data were collected they were organized into three data sets. The largest of these data sets contained the single-shot full resolution digitized lidar signals for all three wavelengths. The other two data sets contained the instrument status data block (ISDB) and the quick look science data (QLSD). ISDB information was generated once per second and contained timing parameters and engineering data related to the health, status, and configuration of the instrument. The QLSD are 100shot averages of the 355 nm and 532 nm lidar signals and were generated at ten second intervals. As the LITE data were generated, they were output to low-rate and high-rate telemetry streams. The low-rate data contained the ISDB and QLSD. The lowrate data were transmitted to the ground by the Shuttle S-band system through the Tracking and Data Relay Satellite System (TDRSS). The high-rate data contained the full resolution digitized lidar signals for all three wavelengths, the ISDB, and QLSD. The high-rate data were transmitted in real time by the Ku-band system through TDRSS downlink to the LITE operations center at the Johnson Space Center (JSC). High-rate data were only obtained when the orbiter and TDRSS telemetry link coincided with the real-time operations of LITE. The low-rate data were backed up by a Shuttle recorder during periods when the telemetry link was unavailable, and the entire lowrate data stream was transferred to the ground over the course of the mission. A total of 53 hours of lowrate data and 45.5 hours of high-rate data were acquired. All of the LITE raw telemetry data have been archived at the NASA Langley Research Center (LaRC), and the LITE high-rate data have been processed to the level 1 data product. This paper describes the data processing steps required to convert the LITE raw, high-rate telemetry data to the LITE level 1 data product.

Powell, Kathleen A.↗

STS-37 Mission Overview: Lead Flight Director Briefing

This NASA Kennedy Space Center (KSC) video release presents a Johnson Space Center (JSC) press conference featuring Chuck Shaw, Lead Flight Director discussing the STS-37 Atlantis shuttle mission. Topics presented include overall mission objectives, flight crew, flight directors, primary payload (Gamma Ray Observatory (GRO)), Extravehicular Activities (EVA) Development Flight Experiment (EDFE), secondary payloads, Development Test Objectives (DTO's), Detailed Supplementary Objectives (DSO's), and flight day activities. Certain flight day activities including the Gamma Ray Observatory deployment and EVA movements and translations are presented as computerized simulations. The video ends with a summary of the key points of STS-37 and a question and answer period with questions posed from Johnson as well as other NASA centers. Questions include topics involving EVA safety, emergency EVA's, and what determines the day of primary payload deployment.

Source record↗

Atmospheric environment for Space Shuttle (STS-4) launch

Selected atmospheric conditions observed near space shuttle STS-4 launch time on June 27, 1982, at Kennedy Space Center, Florida are summarized. Values of ambient pressure, temperature, moisture, ground winds, visual observations (cloud), and winds aloft are included. The sequence of prelaunch Jimsphere measured vertical wind profiles is given as well as the wind and thermodynamic parameters measured at the surface and aloft in the SRB descent/impact ocean area. Final meteorological tapes, which consist of wind descent were constructed. The STS-4 ascent meteorological data tape was constructed by Marshall Space Flight Center in response to shuttle task agreement No. 989-13-22-368 with Johnson Space Center.

Johnson, D. L.↗

Atmospheric environment for Space Shuttle (STS-5) launch

This report presents a summary of selected atmospheric conditions observed near Space Shuttle STS-5 launch time on November 11, 1982, at Kennedy Space Center, Florida. Values of ambient pressure, temperature, moisture, ground winds, visual observations (cloud), and winds aloft are included. The sequence of prelaunch Jimsphere measured vertical wind profiles is given in this report. Also presented are the wind and thermodynamic parameters measured at the surface and aloft in he SRB descent/impact ocean area. Final meteorological tapes, which consist of wind and thermodynamic parameters versus altitude, for STS-5 vehicle ascent and SRB descent have been constructed. The STS-5 ascent meteorological data tape has been constructed by Marshall Space Flight Center in response to Shuttle task agreement No. 936-53-22-368 with Johnson Space Center.

Johnson, D. L.↗

Atmospheric environment for Space Shuttle (STS-6) launch

Selected atmospheric conditions observed near Space Shuttle STS-6 launch time on April 4, 1983, at Kennedy Space Center, Florida are summarized. Values of ambient pressure, temperature, moisture, ground winds, visual observations (cloud), and winds aloft are included. The sequence of prelaunch Jimsphere measured vertical wind profiles is given. Also presented are the wind and thermodynamic parameters measured at the surface and aloft in the SRB descent/impact ocean area. Final meteorological tapes, which consist of wind and thermodynamic parameters versus altitude, for STS-6 veicle ascent and SRB descent were constructed. The STS-6 ascent meteorological data tape was constructed by Marshall Space Flight Center in response to Shuttle task agreement No. 936-53-22-368 with Johnson Space Center.

Johnson, D. L.↗

Atmospheric environment for Space Shuttle (STS-7) launch

Selected atmospheric conditions observed near Space Shuttle STS-7 launch time on June 18, 1983, at Kennedy Space Center, Florida are summarized. Values of ambient pressure, temperature, moisture, ground winds, visual observations (cloud), and winds aloft are included. The sequence of prelaunch Jimsphere measured vertical wind profiles is given in this report. Also presented are wind and thermodynamic parameters representative of surface and aloft conditions in the SRB descent/impact ocean area. Final meteorological tapes, which consist of wind and thermodynamic parameters versus altitude, for STS-7 vehicle ascent and Acoustic/SRB descent have been constructed. The STS-7 ascent meteorological data tape has been constructed by Marshall Space Flight Center in response to Shuttle task agreement No. 936-53-22-368 with Johnson Space Center.

Johnson, D. L.↗

Atmospheric environment for Space Shuttle (STS-9) launch

This report presents a summary of selected atmospheric conditions observed near Space Shuttle STS-9 launch time on November 28, 1983, at Kennedy Space Center, Florida. Values of ambient pressure, temperature, moisture, ground winds, visual observations (cloud), and winds aloft are included. The sequence of prelaunch Jimsphere measured vertical wind profiles is given in this report. The final meteorological tape, which consists of wind and thermodynamic parameters versus altitude, for STS-9 vehicle ascent has been constructed. The STS-9 ascent meteorological data tape has been constructed by Marshall Space Flight Center in response to Shuttle task agreement No. 561-81-22-368 with Johnson Space Center.

Johnson, D. L.↗

Atmospheric environment for space shuttle (STS-13) launch

Selected atmospheric conditions observed near Space Shuttle STS-13 launch time on April 6, 1984, at Kennedy Space Center Florida are summarized. Values of ambient pressure, temperature, moisture, ground winds, visual observations (cloud), and winds aloft are included. The sequence of prelaunch Jimsphere measured vertical wind profiles is given. The final meteorological tape, which consists of wind and thermodynamic parameters versus altitude, for STS-13 vehicle ascent was constructed by Marshall Space Flight Center in response to shuttle task agreement No. 561-81-22-368 with Johnson Space Center.

Johnson, D. L.↗

MCC flight operations automation of STS orbiter systems monitoring

The integration of new capabilities into the Mission Control Center at the Johnson Space Center in Houston, Texas in order to improve the data monitoring and analysis of the STS is discussed. User interface application software and systems, such as the flight data file Shuttle mission simulator and failure analysis program, to be utilized for flight operations automation are examined. Consideration is given to task automation, the trend monitoring system, the data retrieval system, and the launch processing system. The development and functions of the Shuttle data analysis system, which is to operate in real time, are described.

Bates, William V., Jr.↗

User interface devices for mission control

The Mission Control Center (MCC) at Johnson Space Center (JSC) in Houston, Texas, is being upgraded with new technology engineering/scientific workstations. These workstations will replace the existing consoles and will emulate the present hardware input and display media. The workstations will be using new and different input devices for the flight controller to interact with the workstation and mainframes. This paper presents the results of the User Interface survey conducted by the Workstation Prototype Lab (WPL). The WPL offered the opportunity for users to do hands-on evaluations of a number of user interface options prototyped by lab personnel.

Boatman, Wayne↗

Metamorphoses of ONAV console operations: From prototype to real time application

The ONAV (Onboard Navigation) Expert System is being developed as a real time console assistant to the ONAV flight controller for use in the Mission Control Center at the Johnson Space Center. Currently the entry and rendezvous systems are in verification, and the ascent is being prototyped. To arrive at this stage, from a prototype to real world application, the ONAV project has had to deal with not only AI issues but operating environment issues. The AI issues included the maturity of AI languages and the debugging tools, what is verification, and availability, stability, and the size of the expert pool. The environmental issues included real time data acquisition, hardware stability, and how to achieve acceptance by users and management.

Millis, Malise↗