Search NASA⌕ Search

SEARCH · Search NASA

Results for “flight subsystem designs”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS1981

Simultaneous in-flight calibrations of the Galileo science platform and attitude control subsystems

This paper presents a design metholodology and simulation study results for a combined star scanner-gyro-scan platform in-flight calibration for the dual spin Galileo spacecraft. The design process involves three separate parts: the construction of an error model, development of the calibration model, and the selection of the appropriate estimation technique. The major innovative contribution lies in the development of the first two parts which are unique to the Galileo design. A unified procedure has been developed to allow simultaneous calibration of the three subsystems. However, provisions are also made in the software to calibrate each subsystem separately when the necessary a priori information is available.

Lai, J. Y.↗
NASA NTRS1975

The shuttle orbiter cabin atmospheric revitalization systems

The Orbiter Atmospheric Revitalization Subsystem (ARS) and Pressure Control Subsystem (ARPCS) are designed to provide the flight crew and passengers with a pressurized environment that is both life-supporting and within crew comfort limitations. The ARPCS is a two-gas (oxygen-nitrogen) system that obtains oxygen from the Power Reactant Supply and Distribution (PRSD) subsystem and nitrogen from the nitrogen storage tanks. The ARS includes the water coolant loop; cabin CO2, odor, humidity and temperature control; and avionics cooling. Baseline ARPCS and ARS changes since 1973 include removal of the sublimator from the water coolant loop, an increase in flowrates to accommodate increased loads, elimination of the avionics bay isolation from the cabin, a decision to have an inert vehicle during ferry flight, elimination of coldwall tubing around windows and hatches, and deletion of the cabin heater.

Ward, C. F.↗
NASA NTRS1989

Weight and cost forecasting for advanced manned space vehicles

A mass and cost estimating computerized methology for predicting advanced manned space vehicle weights and costs was developed. The user friendly methology designated MERCER (Mass Estimating Relationship/Cost Estimating Relationship) organizes the predictive process according to major vehicle subsystem levels. Design, development, test, evaluation, and flight hardware cost forecasting is treated by the study. This methodology consists of a complete set of mass estimating relationships (MERs) which serve as the control components for the model and cost estimating relationships (CERs) which use MER output as input. To develop this model, numerous MER and CER studies were surveyed and modified where required. Additionally, relationships were regressed from raw data to accommodate the methology. The models and formulations which estimated the cost of historical vehicles to within 20 percent of the actual cost were selected. The result of the research, along with components of the MERCER Program, are reported. On the basis of the analysis, the following conclusions were established: (1) The cost of a spacecraft is best estimated by summing the cost of individual subsystems; (2) No one cost equation can be used for forecasting the cost of all spacecraft; (3) Spacecraft cost is highly correlated with its mass; (4) No study surveyed contained sufficient formulations to autonomously forecast the cost and weight of the entire advanced manned vehicle spacecraft program; (5) No user friendly program was found that linked MERs with CERs to produce spacecraft cost; and (6) The group accumulation weight estimation method (summing the estimated weights of the various subsystems) proved to be a useful method for finding total weight and cost of a spacecraft.

Williams, Raymond↗
NASA NTRS1973

Space radiation incident on SATS missions

A special orbital radiation study was conducted in order to evaluate mission encountered energetic particle fluxes. This information is to be supplied to the project subsystem engineers for their guidance in designing flight hardware to withstand the expected radiation levels. Flux calculations were performed for a set of 20 nominal trajectories placed at several altitudes and inclinations. Temporal variations in the ambient electron environment were considered and partially accounted for. Magnetic field calculations were performed with a current field model, extrapolated to the tentative SATS launch epoch with linear time terms. Orbital flux integrations ware performed with the latest proton and electron environment models, using new computational methods. The results are presented in graphical and tabular form. Estimates of energetic solar proton fluxes are given for a one year mission at selected integral energies ranging from 10 to 100 Mev, calculated for a year of maximum solar activity during the next solar cycle.

Stassinopoulos, E. G.↗
NASA NTRS2010

Lessons Learned from the Node 1 Temperature and Humidity Control Subsystem Design

Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Temperature and Humidity Control (THC) subsystem and it will document some of the lessons that have been learned to date for this subsystem and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs. 1

Williams, David E.↗
NASA NTRS1972

Trajectory correction propulsion for TOPS

A blowdown-pressurized hydrazine propulsion system was selected to provide trajectory correction impulse for outer planet flyby spacecraft as the result of cost/mass/reliability tradeoff analyses. Present hydrazine component and system technology and component designs were evaluated for application to the Thermoelectric Outer Planet Spacecraft (TOPS); while general hydrazine technology was adequate, component design changes were deemed necessary for TOPS-type missions. A prototype hydrazine propulsion system was fabricated and fired nine times for a total of 1600 s to demonstrate the operation and performance of the TOPS propulsion configuration. A flight-weight trajectory correction propulsion subsystem (TCPS) was designed for the TOPS based on actual and estimated advanced components.

Long, H. R.↗
NASA NTRS2010

Lessons Learned from the Node 1 Atmosphere Control and Storage and Water Recovery and Management Subsystem Design

Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Atmosphere Control and Storage (ACS) and Water Recovery and Management (WRM) subsystems and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs.

Williams, David E.↗
NASA NTRS2011

Lessons Learned from the Node 1 Atmosphere Control and Storage and Water Recovery and Management Subsystem Design

Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Atmosphere Control and Storage (ACS) and Water Recovery and Management (WRM) subsystems and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs.

Williams, David E.↗
NASA NTRS1975

Apollo experience report: Guidance and control systems. Lunar module stabilization and control system

A brief functional description of the Apollo lunar module stabilization and control subsystem is presented. Subsystem requirements definition, design, development, test results, and flight experiences are discussed. Detailed discussions are presented of problems encountered and the resulting corrective actions taken during the course of assembly-level testing, integrated vehicle checkout and test, and mission operations. Although the main experiences described are problem oriented, the subsystem has performed satisfactorily in flight.

Shelton, D. H.↗
NASA NTRS2003

A 94 GHz RF Electronics Subsystem for the CloudSat Cloud Profiling Radar

The CloudSat spacecraft, scheduled for launch in 2004, will carry the 94 GHz Cloud Profiling Radar (CPR) instrument. The design, assembly and test of the flight Radio Frequency Electronics Subsystem (RFES) for this instrument has been completed and is presented here. The RFES consists of an Upconverter (which includes an Exciter and two Drive Amplifiers (DA's)), a Receiver, and a Transmitter Calibrator assembly. Some key performance parameters of the RFES are as follows: dual 100 mW pulse-modulated drive outputs at 94 GHz, overall Receiver noise figure < 5.0 dB, a highly stable W-band noise source to provide knowledge accuracy of Receiver gain of < 0.4 dB over the 2 year mission life, and a W-band peak power detector to monitor the transmitter output power to within 0.5 dB over life. Some recent monolithic microwave integrated circuit (MMIC) designs were utilized which implement the DA's in 0.1 micron GaAs high electron-mobility transistor (HEMT) technology and the Receiver low-noise amplifier (LNA) in 0.1 micron InP HEMT technology.

radio frequency electronics subsystem (RFES)↗
NASA NTRS1972

Development and testing of the flight command subsystem for the Mariner Mars 1971 spacecraft

The flight command subsystem for the Mariner Mars 1971 spacecraft is of the same basic design and construction as that for Mariner Mars 1969 except for its expanded capability. Its primary purpose is to provide remote control for the spacecraft. This report briefly describes the design changes, fabrication, and significant problems associated with the development of the Mariner Mars 1971 flight command subsystem.

Chitty, W. H.↗
NASA NTRS2013

Flight Hardware Packaging Design for Stringent EMC Radiated Emission Requirements

This packaging design approach can help heritage hardware meet a flight project's stringent EMC radiated emissions requirement. The approach requires only minor modifications to a hardware's chassis and mainly concentrates on its connector interfaces. The solution is to raise the surface area where the connector is mounted by a few millimeters using a pedestal, and then wrapping with conductive tape from the cable backshell down to the surface-mounted connector. This design approach has been applied to JPL flight project subsystems. The EMC radiated emissions requirements for flight projects can vary from benign to mission critical. If the project's EMC requirements are stringent, the best approach to meet EMC requirements would be to design an EMC control program for the project early on and implement EMC design techniques starting with the circuit board layout. This is the ideal scenario for hardware that is built from scratch. Implementation of EMC radiated emissions mitigation techniques can mature as the design progresses, with minimal impact to the design cycle. The real challenge exists for hardware that is planned to be flown following a built-to-print approach, in which heritage hardware from a past project with a different set of requirements is expected to perform satisfactorily for a new project. With acceptance of heritage, the design would already be established (circuit board layout and components have already been pre-determined), and hence any radiated emissions mitigation techniques would only be applicable at the packaging level. The key is to take a heritage design with its known radiated emissions spectrum and repackage, or modify its chassis design so that it would have a better chance of meeting the new project s radiated emissions requirements.

Lortz, Charlene L.↗
NASA NTRS2010

NASA Spacecraft Fault Management Workshop Results

Fault Management is a critical aspect of deep-space missions. For the purposes of this paper, fault management is defined as the ability of a system to detect, isolate, and mitigate events that impact, or have the potential to impact, nominal mission operations. The fault management capabilities are commonly distributed across flight and ground subsystems, impacting hardware, software, and mission operations designs. The National Aeronautics and Space Administration (NASA) Discovery & New Frontiers (D&NF) Program Office at Marshall Space Flight Center (MSFC) recently studied cost overruns and schedule delays for 5 missions. The goal was to identify the underlying causes for the overruns and delays, and to develop practical mitigations to assist the D&NF projects in identifying potential risks and controlling the associated impacts to proposed mission costs and schedules. The study found that 4 out of the 5 missions studied had significant overruns due to underestimating the complexity and support requirements for fault management. As a result of this and other recent experiences, the NASA Science Mission Directorate (SMD) Planetary Science Division (PSD) commissioned a workshop to bring together invited participants across government, industry, academia to assess the state of the art in fault management practice and research, identify current and potential issues, and make recommendations for addressing these issues. The workshop was held in New Orleans in April of 2008. The workshop concluded that fault management is not being limited by technology, but rather by a lack of emphasis and discipline in both the engineering and programmatic dimensions. Some of the areas cited in the findings include different, conflicting, and changing institutional goals and risk postures; unclear ownership of end-to-end fault management engineering; inadequate understanding of the impact of mission-level requirements on fault management complexity; and practices, processes, and tools that have not kept pace with the increasing complexity of mission requirements and spacecraft systems. This paper summarizes the findings and recommendations from that workshop, as well as opportunities identified for future investment in tools, processes, and products to facilitate the development of space flight fault management capabilities.

Newhouse, Marilyn↗
NASA NTRS2010

Results from the NASA Spacecraft Fault Management Workshop: Cost Drivers for Deep Space Missions

Fault Management, the detection of and response to in-flight anomalies, is a critical aspect of deep-space missions. Fault management capabilities are commonly distributed across flight and ground subsystems, impacting hardware, software, and mission operations designs. The National Aeronautics and Space Administration (NASA) Discovery & New Frontiers (D&NF) Program Office at Marshall Space Flight Center (MSFC) recently studied cost overruns and schedule delays for five missions. The goal was to identify the underlying causes for the overruns and delays, and to develop practical mitigations to assist the D&NF projects in identifying potential risks and controlling the associated impacts to proposed mission costs and schedules. The study found that four out of the five missions studied had significant overruns due to underestimating the complexity and support requirements for fault management. As a result of this and other recent experiences, the NASA Science Mission Directorate (SMD) Planetary Science Division (PSD) commissioned a workshop to bring together invited participants across government, industry, and academia to assess the state of the art in fault management practice and research, identify current and potential issues, and make recommendations for addressing these issues. The workshop was held in New Orleans in April of 2008. The workshop concluded that fault management is not being limited by technology, but rather by a lack of emphasis and discipline in both the engineering and programmatic dimensions. Some of the areas cited in the findings include different, conflicting, and changing institutional goals and risk postures; unclear ownership of end-to-end fault management engineering; inadequate understanding of the impact of mission-level requirements on fault management complexity; and practices, processes, and tools that have not kept pace with the increasing complexity of mission requirements and spacecraft systems. This paper summarizes the findings and recommendations from that workshop, particularly as fault management development issues affect operations and the development of operations capabilities.

Newhouse, Marilyn E.↗
NASA NTRS2020

An Ejectable Data Recorder Subsystem for the Ascent Abort-2 Test Flight of the Orion Launch Abort System

The Ejectable Data Record (EDR) subsystem was a unique development opportunity at NASA with challenges that necessitated innovation. EDR employed a “skunkworks” development approach in which we designed, built, and delivered 47 end items, not including ground support equipment. We used as many COTS components as possible, we looked for process efficiencies to meet our tight deadlines, and the EDR team was involved in the flight operations of the AA-2 test flight and responsible for the recovery operations of the ejected payloads. This paper will discuss the design and development of the EDR subsystem, as well as the results of the system performance during the AA-2 test flight.

Rojdev, Kristina↗
NASA NTRS1992

Man-Vehicle Systems Research Facility - Design and operating characteristics

This paper describes the full-mission flight simulation facility at the NASA Ames Research Center. The Man-Vehicle Systems Research Facility (MVSRF) supports aeronautical human factors research and consists of two full-mission flight simulators and an air-traffic-control simulator. The facility is used for a broad range of human factors research in both conventional and advanced aviation systems. The objectives of the research are to improve the understanding of the causes and effects of human errors in aviation operations, and to limit their occurrence. The facility is used to: (1) develop fundamental analytical expressions of the functional performance characteristics of aircraft flight crews; (2) formulate principles and design criteria for aviation environments; (3) evaluate the integration of subsystems in contemporary flight and air traffic control scenarios; and (4) develop training and simulation technologies.

Shiner, Robert J.↗
NASA NTRS2005

Relevant Parameter Evolution in Team X Mission Concept Designs

The Advanced Projects Design Team, also known as Team X, is a concurrent engineering team that quickly and cheaply designs space mission architectures including the flight system and subsystems, the trajectory, and ground system. Through the use of ICEMaker, an Excel spreadsheet database, the parameters from each subsystem can be shared and used among the other subsystems. This allows for entire missions to be planned with only a few short design team sessions. Based on the results, the feasibility of the mission concept can be determined. Over the Years since the team was created, the amount of information being shared among subsystems on the database has increased, however many of the parameters are now obsolete. Removal of these unused parameters Will clean UP the database and help to streamline the mission design process. By comparing parameter files from previous Team X mission studies, the parameter usage can be determined. As was initially suspected there are more unused parameters on the database than parameters that are actually used.

Huelman, Brandon N.↗
NASA NTRS2019

Multipoint Variable Cycle Engine Design Using Gradient-based Optimization

Supersonic aircraft are challenging to optimally design due to the widely varying constraints and flight conditions they experience. Additionally, a large number of disciplinary subsystems must be considered due to highly complex design requirements. One subsystem that has a major effect on overall performance is the engine. In this work, we construct a supersonic mixed-flow variable cycle engine and perform multipoint gradient-based optimization using this model. We see that the operational variables allow the optimizer to tailor performance at each individual flight condition, leading to better overall performance. To simulate airframe integration constraints, we run successive optimizations with increasingly restrictive inlet areas and see decreases in engine performance. This work is part of a larger effort to incorporate engine design into aero-thermal-mission optimization of a supersonic aircraft.

Cycle analysis↗