SEARCH · Engineering Papers
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.
Basic requirements for a space shuttle orbiter waste collection system are established. They are intended to be an aid in the development and procurement of a representative flight test article. Orbiter interface requirements, performance requirements, flight crew operational requirements, flight environmental requirements, and ground operational and environmental requirements are considered.
Approach and Lending Test Vehicle (ALTV) reduces risk to the X-37 orbital vehicle (OV) flight program by: Testing a subset of OV technologies in a critical portion of the flight envelope. Validating the calculated air data system (CADS) performance/subsonic aerodynamic database. Demonstrating OV approach and landing trajectory. Expending the operational flight envelope of the OV-enabling more landing opportunities for orbital missions.
Recently, the ATM community has made important progress in collaborative trajectory management through the introduction of a new FAA traffic management initiative called a Collaborative Trajectory Options Program (CTOP). FAA can use CTOPs to manage air traffic under multiple constraints (manifested as flow constrained areas or FCAs) in the system, and it allows flight operators to indicate their preferences for routing and delay options. CTOPs also permits better management of the overall trajectory of flights by considering both routing and departure delay options simultaneously. However, adoption of CTOPs in airspace has been hampered by many factors that include challenges in how to identify constrained areas and how to set rates for the FCAs. Decision support tools providing assistance would be particularly helpful in effective use of CTOPs. Such DSTs tools would need models of demand and capacity in the presence of multiple constraints. This study examines different approaches to using historical data to create and validate models of maximum flows in sectors and other airspace regions in the presence of multiple constraints. A challenge in creating an empirical model of flows under multiple constraints is a lack of sufficient historical data that captures diverse situations involving combinations of multiple constraints especially those with severe weather. The approach taken here to deal with this is two-fold. First, we create a generalized sector model encompassing multiple sectors rather than individual sectors in order to increase the amount of data used for creating the model by an order of magnitude. Secondly, we decompose the problem so that the amount of data needed is reduced. This involves creating a baseline demand model plus a separate weather constrained flow reduction model and then composing these into a single integrated model. A nominal demand model is a flow model (gdem) in the presence of clear local weather. This defines the flow as a function of weather constraints in neighboring regions, airport constraints and weather in locations that can cause re-routes to the location of interest. A weather constrained flow reduction model (fwx-red) is a model of reduction in baseline counts as a function of local weather. Because the number of independent variables associated with each of the two decomposed models is smaller than that with a single model, need for amount of data is reduced. Finally, a composite model that combines these two can be represented as fwx-red (gdem(e), l) where e represents non-local constraints and l represents local weather. The approaches studied to developing these models are divided into three categories: (1) Point estimation models (2) Empirical models (3) Theoretical models. Errors in predictions of these different types of models have been estimated. In situations when there is abundant data, point estimation models tend to be very accurate. In contrast, empirical models do better than theoretical models when there is some data available. The biggest benefit of theoretical models is their general applicability in wider range situations once the degree of accuracy of these has been established.
Recently, the ATM community has made important progress in collaborative trajectory management through the introduction of a new FAA traffic management initiative called a Collaborative Trajectory Options Program (CTOP). FAA can use CTOPs to manage air traffic under multiple constraints (manifested as flow constrained areas or FCAs) in the system, and it allows flight operators to indicate their preferences for routing and delay options. CTOPs also permits better management of the overall trajectory of flights by considering both routing and departure delay options simultaneously. However, adoption of CTOPs in airspace has been hampered by many factors that include challenges in how to identify constrained areas and how to set rates for the FCAs. Decision support tools providing assistance would be particularly helpful in effective use of CTOPs. Such DSTs tools would need models of demand and capacity in the presence of multiple constraints. This study examines different approaches to using historical data to create and validate models of maximum flows in sectors and other airspace regions in the presence of multiple constraints. A challenge in creating an empirical model of flows under multiple constraints is a lack of sufficient historical data that captures diverse situations involving combinations of multiple constraints especially those with severe weather. The approach taken here to deal with this is two-fold. First, we create a generalized sector model encompassing multiple sectors rather than individual sectors in order to increase the amount of data used for creating the model by an order of magnitude. Secondly, we decompose the problem so that the amount of data needed is reduced. This involves creating a baseline demand model plus a separate weather constrained flow reduction model and then composing these into a single integrated model. A nominal demand model is a flow model (gdem) in the presence of clear local weather. This defines the flow as a function of weather constraints in neighboring regions, airport constraints and weather in locations that can cause re-routes to the location of interest. A weather constrained flow reduction model (fwx-red) is a model of reduction in baseline counts as a function of local weather. Because the number of independent variables associated with each of the two decomposed models is smaller than that with a single model, need for amount of data is reduced. Finally, a composite model that combines these two can be represented as fwx-red (gdem(e), l) where e represents non-local constraints and l represents local weather. The approaches studied to developing these models are divided into three categories: (1) Point estimation models (2) Empirical models (3) Theoretical models. Errors in predictions of these different types of models have been estimated. In situations when there is abundant data, point estimation models tend to be very accurate. In contrast, empirical models do better than theoretical models when there is some data available. The biggest benefit of theoretical models is their general applicability in wider range situations once the degree of accuracy of these has been established.
The primary objective of the X-57 Mod II test flights is to perform a functional checkout of the research traction battery power and motor systems, perform an airworthiness assessment of the modified vehicle, and to collect baseline performance, stability, and acoustic data for comparisons with later modifications of the X-57 airplane. This paper describes the planned flight operations of the Mod II airplane, the unique considerations and decisions made in operating an electric aircraft, and the development and planning of the research test points necessary to achieve the Mod II flight objectives. Due to the constrained flight time, which resulted from limited capacity of the battery system, careful scripting of flights was required to maximize test time and execute test points efficiently.
NASA is examining the merits of a significant expansion of its avionics, controls, and human factors technology program for the 1980's. The rationale for an expanded program is related to two factors. One factor is related to a utilization of recent and anticipated significant advances in microelectronics. The second factor is the need to develop new concepts in avionics and control systems for more efficient aircraft operation and better utilization of extremely limited airport capacity. Substantial benefits could be realized in three major categories, including improved aircraft efficiency, improved flight operations, and improved/extended operational capability. The NASA Avionics, Controls, and Human Factors Technology Plan is the report of a task force of agency personnel working in close cooperation with industry, DOD, and FAA. Attention is given to the NASA role, aircraft controls, crew station technology, flight management, integration and interfacing, commercial transports, general aviation, rotorcraft, V/STOL, and high performance aircraft.
Titan/Centaur TC-4 was launched from the Eastern Test Range, Complex 41, at 05:22 PM EDT on Wednesday, August 20, 1975. This was the second operational flight of the newest NASA unmanned launch vehicle. The spacecraft was the Viking A, the first of two orbiting and landing missions to Mars planned for the 1975 Martian launch opportunity. The objective of the launch phase of the mission, to inject the Viking spacecraft onto the planned transfer orbit to Mars, was successfully accomplished. This report presents a review of the launch vehicle system flight data.
Titan/Centaur TC-3 was launched from the Eastern Test Range, Complex 41, at 02:34 PM EDT on Tuesday, September 9, 1975. This was the third operational flight of the newest NASA unmanned launch vehicle. The spacecraft was the Viking B, the second of two orbiting and landing missions to Mars planned for the 1975 Martian launch opportunity. The objective of the launch phase of the mission, to inject the Viking spacecraft onto the planned transfer orbit to Mars, was successfully accomplished. A review of the launch vehicle system flight data is presented.
The flight operations task, as developed in support of the Skylab Program, was evolutionary in nature and, to a great extent, was an orderly extension of the flight control concepts used in the Apollo Program, tempered by the nature of the Skylab Program. During the terminal portion of the Apollo Program, many of the operating concepts proposed for Skylab were tested and used for Apollo support to obtain a realistic evaluation of these new techniques. The principal concept developed in the Apollo Program and augmented in support of the Skylab Program was one wherein a professional operations team would provide support to the scientists in the areas of mission integration, experiment, and experiment support systems, monitoring and control, and data retrieval.
This paper expands upon the ASTM industry standard F3269-17 to outline a run-time assurance (RTA) network architecture for use in ensuring safe flight operations of a highly autonomous aircraft. An RTA network architecture is proposed and critical features discussed to implement functions where automation is primarily responsible for the safety of the aircraft instead of a pilot. This shift in responsibility, made possible by the proposed architecture, is key to highly resilient automation and is a core enabler for future “pilotless” transportation concepts. The findings in this paper stem from the researcher’s experiences with ASTM in the generation of the standard and some seven years of RTA system development on various flight programs leveraging the RTA concepts outlined in the ASTM standard.
This Technology Description Document (TDD) provides an overview of the technology for the Phase 1 Baseline and Phase 2 Fused demonstrations of the Integrated Arrival, Departure, and Surface (IADS) prototype system of the National Aeronautics and Space Administration’s (NASA) Airspace Technology Demonstration 2 (ATD-2) project, which has been demonstrated since October of 2017 at Charlotte Douglas International Airport (CLT). Development, integration, and field demonstration of relevant technologies of the IADS system directly address recommendations made by the Next Generation Air Transportation System (NextGen) Integration Working Group (NIWG) on Surface and Data Sharing and the Surface Collaborative Decision Making (Surface CDM) concept of operations developed jointly by the Federal Aviation Administration (FAA) and aviation industry partners. NASA has been developing the IADS traffic management system under the ATD-2 project in coordination with the FAA, flight operators, CLT airport operators, and the National Air Traffic Controllers Association (NATCA). The primary goal of ATD-2 is to improve the predictability and operational efficiency of the air traffic system in metroplex environments, through the enhancement, development, and integration of the nation’s most advanced and sophisticated arrival, departure, and surface prediction, scheduling, and management systems. The ATD-2 project is a 5-year research activity beginning in 2015 and extending through 2020. The Phase 1 Baseline IADS capability resulting from the ATD-2 research has been demonstrated at the CLT airport since the beginning of October 2017. Phase 1 provided data exchange and integration with the initial demonstration of the integrated system of strategic and tactical scheduling, collaborative tactical surface metering, tactical departure scheduling to an en route meter point and overhead stream insertion, initial integration of a TFDM SWIM prototype feed, and an early implementation prototype of a Terminal Flight Data Manager (TFDM) Electronic Flight Data (EFD) system. The strategic surface scheduling element of the capability is consistent with the Surface CDM Concept of Operations published in 2014 by the FAA Surface Operations Directorate.1 The Phase 2 Fused IADS system provided substantial updates to baseline IADS Demonstration capability. Improvements were made to the IADS modeler; tactical surface scheduling, and metering; tactical departure scheduling for overhead stream insertion; Electronic Flight Data (EFD) and the integration with the FAA Advanced Electronic Flight Strip (AEFS); RTC/RMTC, and departure trajectories. New capabilities included a TFDM SWIM prototype feed and delivery of IADS data via the TFDM Terminal Publication (TTP) service of the FAA’s SWIM system; strategic surface scheduling and metering as well as fusion with tactical surface metering; integration and ingestion of data from TTP-connected Mobile App and texting industry for General Aviation (GA) flights; and expansion of airspace deployments to include adjacent Center automation, in particular interface with the Atlanta Center (ZTL) arrival metering TBFM system to evaluate pre-scheduling of flights. Improvements in Data Analysis and System Health (DASH) monitoring and updates were completed as well.
When the systems are developed and in place to provide the services needed to operate en route and on the Lunar and Martian surfaces, an Earth based replication will need to be in place for the safety and protection of mission success. The replication will entail all aspects of the flight configuration end to end but will not include any closed loop systems. This would replicate the infrastructure from Lunar and Martian robots, manned surface excursions, through man and unmanned terrestrial bases, through the various types of communication systems and technologies, manned and un-manned space vehicles (large and small), to Earth based systems and control centers. An Earth based replicated infrastructure will enable checkout and test of new technologies, hardware, software updates and upgrades and procedures without putting humans and missions at risk. Analysis of events, what ifs and trouble resolution could be played out on the ground to remove as much risk as possible from any type of proposed change to flight operational systems. With adequate detail, it is possible that failures could be predicted with a high probability and action taken to eliminate failures. A major factor in any mission to the Moon and to Mars is the complexity of systems, interfaces, processes, their limitations, associated risks and the factor of the unknown including the development by many contractors and NASA centers. The need to be able to introduce new technologies over the life of the program requires an end to end test bed to analyze and evaluate these technologies and what will happen when they are introduced into the flight system. The ability to analyze system behaviors end to end under varying conditions would enhance safety e.g. fault tolerances. This analysis along with the ability to mine data from the development environment (e.g. test data), flight ops and modeling/simulations data would provide a level of information not currently available to operations and astronauts. In this paper we will analyze the beginnings of such a replication and what it could do in terms of reducing risk in the near term for development. We will analyze the Space Shuttle Main Engine (SSME) test lab which has to a large extent accomplished this replication for the SSME and has been highly successful in analyzing hardware and software problems and changes. The cost of replicating the flight system as proposed here could be very high if attempted as an afterthought. We will describe the initial steps for the development of a replication of this infrastructure starting with the communication infrastructure. The Constellation of Labs (CofL) under the Command, Control, Communication and Information (C3I) project for the NASA Exploration Initiative will provide the initial foundation upon which to base this replication. Simply put, there is very little margin for error in high latency situations e.g. en-route to/from Mars or in an autonomous process on the Lunar far side. Any thought out approach to reduce risk and increase safety needs to be accomplished end to end with the actual systems configuration.
Information required to calibrate, functionally check, and operate the Instrumentation Branch equipment on the NASA-6 aircraft is provided. All procedures required for preflight checks and in-flight operation of the NASA-6 atmospheric measuring station are given. The calibration section is intended for only that portion of the system maintained and calibrated by IN-MSD-12 Systems Operation contractor personnel. Maintenance is not included.
A number of changes are expected to occur in the near future which could have important consequences for Atlantic flight operations for the next decade. These changes are identified and their impact on aircraft operating efficiency is discussed. Possible alternatives for North Atlantic air carriers are reviewed and strategies and actions are suggested which may give a considerable impact on fuel savings for years to come.
A comprehensive software control and system configuration management process for flight-crucial digital control systems of advanced aircraft has been developed and refined to insure efficient flight system development and safe flight operations. Because of the highly complex interactions among the hardware, software, and system elements of state-of-the-art digital flight control system designs, a systems-wide approach to configuration control and management has been used. Specific procedures are implemented to govern discrepancy reporting and reconciliation, software and hardware change control, systems verification and validation testing, and formal documentation requirements. An active and knowledgeable configuration control board reviews and approves all flight system configuration modifications and revalidation tests. This flexible process has proved effective during the development and flight testing of several research aircraft and remotely piloted research vehicles with digital flight control systems that ranged from relatively simple to highly complex, integrated mechanizations.
A comprehensive software control and system configuration management process for flight-crucial digital control systems of advanced aircraft has been developed and refined to insure efficient flight system development and safe flight operations. Because of the highly complex interactions among the hardware, software, and system elements of state-of-the-art digital flight control system designs, a systems-wide approach to configuration control and management has been used. Specific procedures are implemented to govern discrepancy reporting and reconciliation, software and hardware change control, systems verification and validation testing, and formal documentation requirements. An active and knowledgeable configuration control board reviews and approves all flight system configuration modifications and revalidation tests. This flexible process has proved effective during the development and flight testing of several research aircraft and remotely piloted research vehicles with digital flight control systems that ranged from relatively simple to highly complex, integrated mechanizations.
This paper presents a status report on the study of a next-generation manned launch system, called Shuttle II, being conducted at the NASA Langley Research Center. Underlying reasons for considering such a system include the need for low-cost, safe, and reliable manned access to space. System and operational characteristics for a Shuttle II vehicle are presented. The need for fully reusable launch systems with radically simpler ground and flight operations is stated to be critical in reducing launch costs. Advancing technologies have a major impact on the choice of vehicle concepts. For a near-term level of technology, a two-stage vertical-takeoff rocket vehicle has been selected for further in-depth Shuttle II studies. The role of the Shuttle II vehicle in a proposed space transportation system, which includes heavy lift and Space Shuttle complementary manned systems, is discussed.
This viewgraph presentation gives an overview of the spaceport operations element, including details on NASA Ames air traffic management technologies, reusable launch vehicles, space transportation of the future, and spaceport flight operations research topics.