NASA Schedules Four-Day Manned Gemini Flight from Cape Kennedy
Gemini 4 manned orbital space flight - plan for launching, maneuvers, rendezvous, docking, and reentry
SEARCH · Search NASA
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.
Gemini 4 manned orbital space flight - plan for launching, maneuvers, rendezvous, docking, and reentry
The results of a NASA-sponsored study examining the effectiveness of a brief, preplanned cockpit rest period to improve pilot alertness and performance in nonaugmented long-haul flight operations are discussed. Four regularly scheduled trans-Pacific flight legs were studied. The shortest flight legs were about 7 h and the longest about 9.5 h, with duty periods averaging about 11 h and layovers about 25 h. Three-person B747 crews were divided randomly into two volunteer pilot groups. These crews were nonaugmented, and therefore no relief pilots were available. The rest group, consisting of four crews, was allowed a 40 min opportunity to rest during the overwater cruise portion of the flight. On a preplanned, rotating basis, individual crew members were allowed to nap. It is concluded that a preplanned cockpit nap is associated with significantly better behavioral performance and higher levels of physiological alertness and that this can be accomplished without disrupting normal flight operations or compromising safety.
Usually aviation accidents are categorized and analyzed within flight conduct rules (Part 121, Part 135, Part 91) because differences in accident rates within flight rules have been demonstrated. Even within a particular flight rule the flights have different purposes. For many, Part 121 flights are synonymous with scheduled passenger transport, and indeed this is the largest group of Part 121 accidents. But there are also non-scheduled (charter) passenger transport and cargo flights. The primary purpose of the analysis reported here is to examine the differences in aviation accidents based on the purpose of the flight. Some of the factors examined are the accident severity, aircraft characteristics and accident occurrence categories. Twenty consecutive years of data were available and utilized to complete this analysis.
No abstract available
The Federal Aviation Administration's Next Generation Air Transportation System will combine advanced air traffic management technologies, performance-based procedures, and state-of-the-art avionics to maintain efficient operations throughout the entire arrival phase of flight. Flight deck Interval Management (FIM) operations are expected to use sophisticated airborne spacing capabilities to meet precise in-trail spacing from top-of-descent to touchdown. Recent human-in-the-loop simulations by the National Aeronautics and Space Administration have found that selection of the assigned spacing goal using the runway schedule can lead to premature interruptions of the FIM operation during periods of high traffic demand. This study compares three methods for calculating the assigned spacing goal for a FIM operation that is also subject to time-based metering constraints. The particular paradigms investigated include: one based upon the desired runway spacing interval, one based upon the desired meter fix spacing interval, and a composite method that combines both intervals. These three paradigms are evaluated for the primary arrival procedures to Phoenix Sky Harbor International Airport using the entire set of Rapid Update Cycle wind forecasts from 2011. For typical meter fix and runway spacing intervals, the runway- and meter fix-based paradigms exhibit moderate FIM interruption rates due to their inability to consider multiple metering constraints. The addition of larger separation buffers decreases the FIM interruption rate but also significantly reduces the achievable runway throughput. The composite paradigm causes no FIM interruptions, and maintains higher runway throughput more often than the other paradigms. A key implication of the results with respect to time-based metering is that FIM operations using a single assigned spacing goal will not allow reduction of the arrival schedule's excess spacing buffer. Alternative solutions for conducting the FIM operation in a manner more compatible with the arrival schedule are discussed in detail.
The Automated Flight Test Management System (ATMS) is being developed as part of the NASA Aircraft Automation Program. This program focuses on the application of interdisciplinary state-of-the-art technology in artificial intelligence, control theory, and systems methodology to problems of operating and flight testing high-performance aircraft. The development of a Flight Test Engineer's Workstation (FTEWS) is presented, with a detailed description of the system, technical details, and future planned developments. The goal of the FTEWS is to provide flight test engineers and project officers with an automated computer environment for planning, scheduling, and performing flight test programs. The FTEWS system is an outgrowth of the development of ATMS and is an implementation of a component of ATMS on SUN workstations.
Salient design features of a new NASA/Army research rotorcraft - the Rotorcraft Aircrew Systems Concepts Airborne Laboratory (RASCAL) - are described. Using a UH-60A Black Hawk helicopter as a baseline vehicle, the RASCAL will be a flying laboratory capable of supporting the research requirements of major NASA and Army guidance, control, and display research programs. The paper describes the research facility requirements of these programs together with other critical constraints on the design of the research system, including safety-of-flight. Research program schedules demand a phased development approach, wherein specific research capability milestones are met and flight research projects are flown throughout the complete development cycle of the RASCAL. This development approach is summarized, and selected features of the research system are described. The research system includes a full-authority, programmable, fault-tolerant/fail-safe, fly-by-wire flight control system and a real-time obstacle detection and avoidance system which will generate low-latitude guidance commands to the pilot on a wide field-of-view, color helmet-mounted display.
Salient design features of a new NASA/Army research rotorcraft - the Rotorcraft-Aircrew Systems Concepts Airborne Laboratory (RASCAL) - are described. Using a UH-60A Black Hawk helicopter as a baseline vehicle, the RASCAL will be a flying laboratory capable of supporting the research requirements of major NASA and Army guidance, control, and display research programs. The paper describes the research facility requirements of these programs together with other critical constraints on the design of the research system, including safety-of-flight. Research program schedules demand a phased development approach, wherein specific research capability milestones are met and flight research projects are flown throughout the complete development cycle of the RASCAL. This development approach is summarized, and selected features of the research system are described. The research system includes a full-authority, programmable, fault-tolerant/fail-safe, fly-by-wire flight control system and a real-time obstacle detection and avoidance system which will generate low-altitude guidance commands to the pilot on a wide field-of-view, color helmet-mounted display.
Goddard Space Flight Center's Flight Projects Directorate employed a Business Change Initiative (BCI) to infuse a series of activities coordinated to drive improved cost and schedule performance across Goddard's missions. This sustaining change framework provides a platform to manage and implement cost and schedule control techniques throughout the project portfolio. The BCI concluded in December 2014, deploying over 100 cost and schedule management changes including best practices, tools, methods, training, and knowledge sharing. The new business approach has driven the portfolio to improved programmatic performance. The last eight launched GSFC missions have optimized cost, schedule, and technical performance on a sustained basis to deliver on time and within budget, returning funds in many cases. While not every future mission will boast such strong performance, improved cost and schedule tools, management practices, and ongoing comprehensive evaluations of program planning and control methods to refine and implement best practices will continue to provide a framework for sustained performance. This paper will describe the tools, techniques, and processes developed during the BCI and the utilization of collaborative content management tools to disseminate project planning and control techniques to ensure continuous collaboration and optimization of cost and schedule management in the future.
The 1978 scheduled solar cell calibration balloon flight was successfully completed. Thirty six modules were carried to an altitude of above 36 kilometers. Recovery of telemetry and flight packages was without incident. These calibrated standard cells are used as reference standards in simulator testing of cells and arrays with similar spectral response characteristics. The factors affecting the spectral transmission of the atmosphere at various altitudes are summarized.
Due to an aggressive schedule for the first space flight of an unmanned Orion capsule, currently known as Exploration Flight Test One (EFT1), combined with severe programmatic funding constraints, an effort was made within the Orion Program 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 MPLM cabin Positive Pressure Relief Assembly (PPRA), and the Shuttle Ground Support Equipment Heat Exchanger (GSE HX). 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 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 activities required in order to utilize heritage hardware for EFT1.
The topics are covered in view graph form and include the following: (1) major elements of deep space flight programs; (2) development schedule; (3) primary design goals; (4) Space Flight Operations Center (SFOC) data systems architecture; (5) technical guidelines; (6) SFOC data system functional architecture; (7) typical SFOC node; (8) SFOC components; (9) SFOC software categories; (10) planned subsystem core diagram for Mars observer; (11) SFOC use of public domain/3rd party software; (12) SFOC hardware; (13) SFOC target six mission configuration; and (14) SFOC development status and plans.
The first flight test of the Orion Abort Flight Test project is scheduled to launch in Spring 2010. This flight test is known as Pad Abort 1 (PA-1) and it is intended to accomplish a series of flight test objectives, including demonstrating the capability of the Launch Abort System (LAS) to propel the Crew Module (CM) to a safe distance from a launch vehicle during a pad abort. The PA-1 Flight Test Article (FTA) is actively controlled by a guidance, navigation, and control (GN&C) system for much of its flight. The purpose of this paper is to describe the design, development, and analysis of the PA-1 GN&C system. A description of the technical solutions that were developed to meet the challenge of satisfying many competing requirements is presented. A historical perspective of how the Orion LAV compares to the Apollo Launch Escape Vehicle (LEV) design will also be included.
The space shuttle solid rocket boosters (SRBs) experience a severe environment during their brief flight. During the last few years several SRB's have sustained noticeable structural damage. The environmental characteristics (vibration, structure, and thermal) encountered by the SRB's during ascent, descent and water impact are in most cases unknown. A developmental flight instrumentation (DFI) system collected data from the SRBs' first four flights in the early 1980's, and after the first three flights during the shuttle return-to-flight phase after the Challenger accident. However, the DFI data collected are of low fidelity and do not correlate well with cases of observed structural damage. The DFI system was evaluated for reuse, but the cost to fly it was prohibitive. The space shuttle is presently scheduled to fly until 2030. To support the shuttle flight schedule, avionics on the SRB's will be upgraded. The environments on the different sections of the SRB will need to be defined more completely to properly qualify the avionics for multiple flights. The DFI data previously gathered do not provide enough information to properly qualify the avionics. Marshall Space Flight Center's (MSFC) SRB Project Office requested the Science and Engineering (S&E) Directorate to develop a stand-alone data acquisition system that could collect data from any area of the booster. In answer to this requirement, S&E developed the Enhanced Data Acquisition System (EDAS). To minimize development time and cost, the development team used state-of-the-art commercial off the shelf (COTS) equipment. The first two flights of this system occurred on shuttle mission STS-91 in June 1998 and STS-95 in October 1998. Twenty-one measurements were successfully recorded on the STS-91 right hand booster, providing new accelerometer, strain, temperature, and heating rate data to analysts. Twenty-four measurements were successfully recorded on the STS-95 left hand booster, providing data from the booster and the external tank. This paper summarizes the effort to develop, test, qualify and fly the EDAS to meet SRB flight and data collection requirements.
The space shuttle solid rocket boosters (SRBs) experience a severe environment during their brief flight. During the last few years several SRB's have sustained noticeable structural damage. The environmental characteristics (vibration, structure, and thermal) encountered by the SRB's during ascent, descent and water impact are in most cases unknown. A developmental flight instrumentation (DFI) system collected data from the SRBs' first four flights in the early 1980's, and after the first three flights during the shuttle return-to-flight phase after the Challenger accident. However, the DFI data collected are of low fidelity and do not correlate well with cases of observed structural damage. The DFI system was evaluated for reuse, but the cost to fly it was prohibitive. The space shuttle is presently scheduled to fly until 2030. To support the shuttle flight schedule, avionics on the SRB's will be upgraded. The environments on the different sections of the SRB will need to be defined more completely to properly qualify the avionics for multiple flights. The DFI data previously gathered do not provide enough information to properly qualify the avionics. Marshall Space Flight Center's (MSFC) SRB Project Office requested the Science and Engineering (S&E) Directorate to develop a stand-alone data acquisition system that could collect data from any area of the booster. In answer to this requirement, S&E developed the Enhanced Data Acquisition System (EDAS). To minimize development time and cost, the development team used state-of-the-art commercial off the shelf (COTS) equipment. The first two flights of this system occurred on shuttle mission STS-91 in June 1998 and STS-95 in October 1998. Twenty-one measurements were successfully recorded on the STS-91 right hand booster, providing new accelerometer, strain, temperature, and heating rate data to analysts. Twenty-four measurements were successfully recorded on the STS-95 left hand booster, providing data from the booster and the external tank. This paper summarizes the effort to develop, test, qualify and fly the EDAS to meet SRB flight and data collection requirements.
The current system used by the FAA to schedule arrivals is the Traffic Based Flow Manager (TBFM). It is a centralized system that gives an operator (airline) no influence over scheduled times of arrival assigned to its flights. Future systems for managing arrival scheduling are proposed as distributed systems. Such a system is called upon to give operators influence to schedule and negotiate resources for their flights, and to resolve other technical challenges, such as eliminating a single point of failure. A distributed system for managing diverse air traffic will need the capability of computing a schedule for the given arriving flights in a way that complies with the operational constraints. This paper contributes an algorithm that computes such a schedule. Although developed as part of an effort toward a distributed system, the algorithm itself is neither inherently distributed nor inherently centralized and can be used in either type of system.
The current system used by the FAA to schedule arrivals is the Traffic Based Flow Manager (TBFM). It is a centralized system that gives an operator (airline) no influence over scheduled times of arrival assigned to its flights. Future systems for managing arrival scheduling are proposed as distributed systems. Such a system is called upon to give operators influence to schedule and negotiate resources for their flights, and to resolve other technical challenges, such as eliminating a single point of failure. A distributed system for managing diverse air traffic will need the capability of computing a schedule for the given arriving flights in a way that complies with the operational constraints. This paper contributes an algorithm that computes such a schedule. Although developed as part of an effort toward a distributed system, the algorithm itself is neither inherently distributed nor inherently centralized and can be used in either type of system.
The U.S. National Aeronautics and Space Administration (NASA) Sounding Rockets and Balloon Programs conduct a combined total of approximately fifty to sixty missions per year in support of the NASA scientific community. These missions are provided in support of investigations sponsored by NASA'S Offices of Space Science, Life and Microgravity Sciences & Applications, and Earth Science. The Goddard Space Flight Center has management and implementation responsibility for these programs. The NASA Sounding Rockets Program has continued to su,pport the science community by integrating their experiments into the sounding rocket payload and providing the rocket vehicle and launch operations necessary to provide the altitude/time required obtain the science objectives. The sounding rockets continue to provide a cost-effective way to make in situ observations from 50 to 1500 km in the near-earth environment and to uniquely cover the altitude regime between 50 km and 130 km above the Earth's surface, which is physically inaccessible to either balloons or satellites. A new architecture for providing this support has been introduced this year with the establishment of the NASA Sounding Rockets Contract. The Program has continued to introduce improvements into their operations and ground and flight systems. An overview of the NASA Sounding Rockets Program with special emphasis on the new support contract will be presented. The NASA Balloon Program continues to make advancements and developments in its capabilities for support of the scientific ballooning community. Long duration balloon (LDB) is a prominent aspect of the program with two campaigns scheduled for this calendar year. Two flights are scheduled in the Northern Hemisphere from Fairbanks, Alaska, in June and two flights are scheduled from McMurdo, Antarctica, in the Southern Hemisphere in December. The comprehensive balloon research and development (R&D) effort has continued with advances being made across the spectrum of balloon related disciplines. As a result of these technology advancements a new ultra long duration balloon project (ULDB) for the development of a 100- day duration balloon capability has been initiated. The ULDB will rely upon new balloon materials and designs to accomplish its goals. The Program has also continued to introduce new technology and improvements into flights systems, ground systems and operational techniques. An overview of the various aspects of the NASA Balloon Program will be presented.