Search NASA⌕ Search

SEARCH · Search NASA

Results for “Space Shuttle Program”

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 307 records · Page 17

Space Shuttle Orbiter approach and landing program status

The space shuttle approach and landing test (ALT) program is being conducted in four phases. The first phase, completed in March of 1977, consisted of verifying the airworthiness of the mated B-747 shuttle carrier aircraft and orbiter. The second phase consists of checking the orbiter systems in captive flight. The third phase is to be confined to launching the orbiter with and without the tail cone installed to evaluate the final landing phase of the shuttle operations through the verification of the automatic landing system. The fourth and final phase of the program is to document the mated configuration's performance relative to the ferry operations to be conducted between the return from the orbiter's landing sites and launch sites. This paper presents the results of the SCA inert orbiter flight testing and the program plans up to the completion of the ALT program.

Andrews, W. H.↗

The Logical Extension

The same software controlling autonomous and crew-assisted operations for the International Space Station (ISS) is enabling commercial enterprises to integrate and automate manual operations, also known as decision logic, in real time across complex and disparate networked applications, databases, servers, and other devices, all with quantifiable business benefits. Auspice Corporation, of Framingham, Massachusetts, developed the Auspice TLX (The Logical Extension) software platform to effectively mimic the human decision-making process. Auspice TLX automates operations across extended enterprise systems, where any given infrastructure can include thousands of computers, servers, switches, and modems that are connected, and therefore, dependent upon each other. The concept behind the Auspice software spawned from a computer program originally developed in 1981 by Cambridge, Massachusetts-based Draper Laboratory for simulating tasks performed by astronauts aboard the Space Shuttle. At the time, the Space Shuttle Program was dependent upon paper-based procedures for its manned space missions, which typically averaged 2 weeks in duration. As the Shuttle Program progressed, NASA began increasing the length of manned missions in preparation for a more permanent space habitat. Acknowledging the need to relinquish paper-based procedures in favor of an electronic processing format to properly monitor and manage the complexities of these longer missions, NASA realized that Draper's task simulation software could be applied to its vision of year-round space occupancy. In 1992, Draper was awarded a NASA contract to build User Interface Language software to enable autonomous operations of a multitude of functions on Space Station Freedom (the station was redesigned in 1993 and converted into the international venture known today as the ISS)

Source record↗

The simulation of the alternate turbopump development high pressure oxygen and fuel turbopumps for the space shuttle main engine using the Shaberth computer program

The Space Shuttle Main Engine (SSME) is basically comprised of a combustion chamber and nozzle, high and low pressure oxygen turbopumps and high and low pressure fuel turbopumps. In the current configuration, the high pressure fuel (HPTFP) and high pressure oxygen turbopumps (HPOTP) have experienced a history of ball bearing wear. The wear problem can be attributed to numerous factors including the hydrodynamic axial and radial loads caused by the flow of liquid oxygen and liquid hydrogen through the turbopump impellers and turbine. Also, friction effects between the rolling elements, races, and cage can create thermally induced bearing geometry changes. To alleviate some of the current configuration problems, an alternate turbopump development (ATD) was proposed. However, the ATD HPOTP and HPTFP are constrained to operate interchangeably with the current turbopumps, thus, the operation conditions must be similar. The ATD configuration features a major change in bearings used to support the integrated shaft, impeller, and turbine system. A single ball and single roller will replace the pump-end and turbine and duplex ball bearings. The Shaft-Bearing-Thermal (SHABERTH) computer code was used to model the ATD HPOTP and ATD HPFTP configurations. A two bearing model was used to simulate the HPOTP and HPFTP bearings and shaft geometry. From SHABERTH, a comparison of bearing reaction loads, frictional heat generation rates, and Hertz contact stresses will be attempted with analysis at the 109 percent and 65 percent power levels.

Mcdonald, Gary H.↗

Real-time simulation for Space Station

Development of a new Space Station simulation designed to provide long-term support to the Space Station Program is well under way. A description of the two Engineering Directorate simulation facilities, the Systems Engineering Simulator and the Shuttle Avionics Integration Laboratory, is presented. The function of each in support of the Space Shuttle Program is discussed, with emphasis on functions applicable to Space Station. The function of the Systems Engineering Simulator in Space Station development is described. Finally, a comprehensive and detailed description of the new Space Station simulation under development on the System Engineering Simulator is presented.

St. John, Robert H.↗

HAL/S programmer's guide

This programming language was developed for the flight software of the NASA space shuttle program. HAL/S is intended to satisfy virtually all of the flight software requirements of the space shuttle. To achieve this, HAL/s incorporates a wide range of features, including applications-oriented data types and organizations, real time control mechanisms, and constructs for systems programming tasks. As the name indicates, HAL/S is a dialect of the original HAL language previously developed. Changes have been incorporated to simplify syntax, curb excessive generality, or facilitate flight code emission.

Newbold, P. M.↗

HAL/SM language specification

A programming language is presented for the flight software of the NASA Space Shuttle program. It is intended to satisfy virtually all of the flight software requirements of the space shuttle. To achieve this, it incorporates a wide range of features, including applications-oriented data types and organizations, real time control mechanisms, and constructs for systems programming tasks. It is a higher order language designed to allow programmers, analysts, and engineers to communicate with the computer in a form approximating natural mathematical expression. Parts of the English language are combined with standard notation to provide a tool that readily encourages programming without demanding computer hardware expertise. Block diagrams and flow charts are included. The semantics of the language is discussed.

Williams, G. P. W., Jr.↗

NASA Kennedy Space Center: Contributions to Sea Turtle Science and Conservation

The National Aeronautics and Space Administration (NASA) is a United States (US) federal agency that oversees US space exploration and aeronautical research. NASA's primary launch site, Kennedy Space Center (KSC) is located along the east coast of Florida, on Cape Canaveral and the western Atlantic Ocean. The natural environment within KSC's large land boundaries, not only functions as an extensive safety buffer-area, it performs simultaneously as a wildlife refuge and a national seashore. In the early 1960s, NASA was developing KSC for rocket launches and the US was establishing an awareness of, and commitment to protecting the environment. The US began creating regulations that required the consideration of the environment when taking action on federal land or with federal funds. The timing of the US Endangered Species Act (1973), the US National Environmental Policy Act (1972), coincided with the planning and implementation of the US Space Shuttle Program. This resulted in the first efforts to evaluate the impacts of space launch operation operations on waterways, air quality, habitats, and wildlife. The first KSC fauna and flora baseline studies were predominantly performed by University of Central Florida (then Florida Technological University). Numerous species of relative importance were observed and sea turtles were receiving regulatory review and protection as surveys by Dr. L Ehrhart (UCF) from 1973-1978 described turtles nesting along the KSC beaches and foraging in the KSC lagoon systems. These data were used in the first NASA Environmental Impact Statement for the Space Transportation System (shuttle program) in 1980. In 1982, NASA began a long term ecological monitoring program with contracted scientists on site. This included efforts to track sea turtle status and trends at KSC and maintain protective measures for these species. Many studies and collaborations have occurred on KSC over these last 45 years with agencies (USFWS, NOAA, NAVY), students, and universities (UCF, University of Toronto, Texas A&M, UF). This presentation will review the various studies and collaborations on sea turtles at KSC that include: nest distributions and success, stranding network development, aerial survey testing for nest counts, predator control assessments, the earliest baseline blood chemistry health determinations on nesting females, stress hormones in nesting females, multi-year study of hatchling sex ratios, genetics, species composition, abundance and distribution of in-water juveniles, turtle cold stun response, exterior lighting impacts and control, and satellite tag tracking of post-nesting turtles in the vicinity of near shore shoals and sand mining sites. Through these studies, monitoring, and recommendations, KSC has provided excellent stewardship and protection of the local environment. While conducting its space program mission, KSC has also made significant contributions of information for agencies charged with the conservation and management of these species

Provancha, Jane A.↗

STS-41 Space Shuttle mission report

The STS-41 Space Shuttle Program Mission Report contains a summary of the vehicle subsystem activities on this thirty-sixth flight of the Space Shuttle and the eleventh flight of the Orbiter vehicle, Discovery (OV-103). In addition to the Discovery vehicle, the flight vehicle consisted of an External Tank (ET) (designated as ET-39/LWT-32), three Space Shuttle main engines (SSME's) (serial numbers 2011, 2031, and 2107), and two Solid Rocket Boosters (SRB's), designated as BI-040. The primary objective of the STS-41 mission was to successfully deploy the Ulysses/inertial upper stage (IUS)/payload assist module (PAM-S) spacecraft. The secondary objectives were to perform all operations necessary to support the requirements of the Shuttle Backscatter Ultraviolet (SSBUV) Spectrometer, Solid Surface Combustion Experiment (SSCE), Space Life Sciences Training Program Chromosome and Plant Cell Division in Space (CHROMEX), Voice Command System (VCS), Physiological Systems Experiment (PSE), Radiation Monitoring Experiment - 3 (RME-3), Investigations into Polymer Membrane Processing (IPMP), Air Force Maui Optical Calibration Test (AMOS), and Intelsat Solar Array Coupon (ISAC) payloads. The sequence of events for this mission is shown in tabular form. Summarized are the significant problems that occurred in the Orbiter subsystems during the mission. The official problem tracking list is presented. In addition, each Orbiter problem is cited in the subsystem discussion.

Camp, David W.↗

Aerothermodynamic Data Base

Space shuttle aerothermodynamic data, collected from a continuing series of wind tunnel tests, are permanently stored with the Data Management Services (DMS) system. Information pertaining to current baseline configuration definition is also stored. A list of documentation of DMS processed data arranged sequentially and by space shuttle configuration is presented. The listing provides an up to date record of all applicable aerothermodynamic data collected, processed, or summarized during the space shuttle program. Tables are designed to provide survey information to the various space shuttle managerial and technical levels.

Source record↗

HAL/S language specification

A programming language for the flight software of the NASA space shuttle program was developed and identified as HAL/S. The language is intended to satisfy virtually all of the flight software requirements of the space shuttle. The language incorporates a wide range of features, including applications-oriented data types and organizations, real time control mechanisms, and constructs for systems programming tasks.

Newbold, P. M.↗

Columbia Accident Investigation Board Report. Volume Five

Volume V of the Report contains appendices that were not cited in VolumeI. These consist of documents produced by NASA and other organizations, which were provided to the Columbia Accident Investigation Board in support of its inquiry into the February 1, 2003 destruction of the Space Shuttle Columbia The contents include:. Appendix G.1 Requirements and Procedures for Certification of Flight Readiness; Appendix G.2 Appendix R, Space Shuttle Program Contingency Action Plan; Appendix G.3 CAIB Charter, with Revisions; Appendix G.4 Group 1 Matrix Brief on Maintenance, Material, and Management; Appendix G.5 Vehicle Data Mapping(VDM) Team Final Report, Jun 13, 2003; Appendix G.6 SRB Working Group Presentation to CAIB; Appendix G. 7 Starfire Team Final Report, Jun 3, 2003; Appendix G.8 Using the Data and Observations from Flight STS-107, Executive Summary; Appendix G.9 Contracts, Incentives, and Safety/Technical Excellence; Appendix G.10 Detailed Summaries: Rogers Commission Report, ASAP Report, SIAT Report; Appendix G.11 Foam Application and Production Chart; Appendix G.12 Crew Survivability Report; and Appendix G.12 Aero/Aerothermal/ Thermal/Structures Team FinalReport, August 6, 2003.

CAIB (COLUMBIA ACCIDENT INVESTIGATION BOARD)↗

Medical care delivery in space

Consideration is given to the delivery of medical care in space. The history of aviation medicine is reviewed. Medical support for the early space programs is discussed, including the Mercury, Gemini, Apollo, and Skylab programs. The process of training crew members for basic medical procedures for the Space Shuttle program is briefly described and medical problems during the Shuttle program are noted. Plans for inflight medical care on the Space Station are examined, including the equipment planned for the Health Maintenance Facility, the use of exercise to help prevent medical problems.

Stewart, Don F.↗

Reference earth orbital research and applications investigations (blue book). Volume 1: Summary

The criteria, guidelines, and an organized approach for use in the space station and space shuttle program definition phase are presented. Subjects discussed are: (1) background information and evolution of the studies, (2) definition of terms used, (3) concepts of the space shuttle, space station, experiment modules, shuttle-sortie operations and modular space station, and (4) summary of functional program element (FPE) requirements. Diagrams of the various configurations and the experimental equipment to be installed in the structures are included.

Source record↗

Portable computers as companions in space

The paper describes a Space Shuttle Program payload that uses a Macintosh portable computer to gather human performance data for a cursor control device experiment and to test prototype software applications for the Space Station Freedom (SSF). The payload is the first phase of a NASA research and development project to operationally test human-computer interface requirements and crew support applications for an advanced portable computer for the SSF.

Microgravity↗

Use of Heritage Hardware on MPCV Exploration Flight Test One

Due to an aggressive schedule for the first orbital test flight of an unmanned Orion capsule, known as Exploration Flight Test One (EFT1), combined with severe programmatic funding constraints, an effort was made to identify heritage hardware, i.e., already existing, flight-certified components from previous manned space programs, which might be available for use on EFT1. With the end of the Space Shuttle Program, no current means exists to launch Multi Purpose Logistics Modules (MPLMs) to the International Space Station (ISS), and so the inventory of many flight-certified Shuttle and MPLM components are available for other purposes. Two of these items are the Shuttle Ground Support Equipment Heat Exchanger (GSE Hx) and the MPLM cabin Positive Pressure Relief Assembly (PPRA). In preparation for the utilization of these components by the Orion Program, analyses and testing of the hardware were performed. The PPRA had to be analyzed to determine its susceptibility to pyrotechnic shock, and vibration testing had to be performed, since those environments are predicted to be significantly more severe during an Orion mission than those the hardware was originally designed to accommodate. The GSE Hx had to be tested for performance with the Orion thermal working fluids, which are different from those used by the Space Shuttle. This paper summarizes the certification of the use of heritage hardware for EFT1.

Rains, George Edward↗

Motivational contracting in space programs - Government and industry prospectives

NASA's Marshall Space Flight Center has used incentive-free policies in contracting for Apollo's Saturn Launch vehicle hardware, as well as award-fee contracts for major development and early production programs in the case of the Space Shuttle Program. These programs have evolved to a point at which multiple incentive fees are useful in motivating cost reductions and assuring timely achievement of delivery requirements and flight mission goals. An examination is presently conducted of the relative success of these motivation-oriented techniques, drawing on the comments of both government and industry personnel.

Clough, D. R.↗

PLAID as a maintainability tool

PLAID is a computer-aided design tool for human factors engineering which has been used successfully in the Space Shuttle program and for design analysis of Space Station Freedom. PLAID capability includes analysis of visual fields of view, of the ability to reach a specified point, and of spatial conflicts. It enables the creation of animations which depict whole sequences of motions of astronauts and equipment. The PLAID graphics capability is described and its application to man-systems integration is briefly examined. The use of PLAID for maintainability is addressed, and future plans for PLAID are discussed.

Woolford, Barbara J.↗

A New Heavy-Lift Capability for Space Exploration: NASA's Ares V Cargo Launch Vehicle

The National Aeronautics and Space Administration (NASA) is developing new launch systems and preparing to retire the Space Shuttle by 2010, as directed in the United States (U.S.) Vision for Space Exploration. The Ares I Crew Launch Vehicle (CLV) and the Ares V heavy-lift Cargo Launch Vehicle (CaLV) systems will build upon proven, reliable hardware derived from the Apollo-Saturn and Space Shuttle programs to deliver safe, reliable, affordable space transportation solutions. This approach leverages existing aerospace talent and a unique infrastructure, as well as legacy knowledge gained from nearly 50 years' experience developing space hardware. Early next decade, the Ares I will launch the new Orion Crew Exploration Vehicle (CEV) to the International Space Station (ISS) or to low-Earth orbit for trips to the Moon and, ultimately, Mars. Late next decade, the Ares V's Earth Departure Stage will carry larger payloads such as the lunar lander into orbit, and the Crew Exploration Vehicle will dock with it for missions to the Moon, where astronauts will explore new territories and conduct science and technology experiments. Both Ares I and Ares V are being designed to support longer future trips to Mars. The Exploration Launch Projects Office is designing, developing, testing, and evaluating both launch vehicle systems in partnership with other NASA Centers, Government agencies, and industry contractors. This paper provides top-level information regarding the genesis and evolution of the baseline configuration for the Ares V heavy-lift system. It also discusses riskbased, management strategies, such as building on powerful hardware and promoting common features between the Ares I and Ares V systems to reduce technical, schedule, and cost risks, as well as development and operations costs. Finally, it summarizes several notable accomplishments since October 2005, when the Exploration Launch Projects effort officially kicked off, and looks ahead at work planned for 2007 and beyond.

Sumrall, John P.↗