Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “vehicle data”

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 595 records · Page 33
All sourcesNASA NTRSDOE OSTI
NASA NTRS1977

Linear aerospike engine study

Parametric data on split-combustor linear engine propulsion systems are presented for use in mixed-mode single-stage-to-orbit (SSTO) vehicle studies. Preliminary design data for two selected engine systems are included. The split combustor was investigated for mixed-mode operations with oxygen/hydrogen propellants used in the inner combustor in Mode 2, and in conjunction with either oxygen/RP-1, oxygen/RJ-5, O2/CH4, or O2/H2 propellants in the outer combustor for Mode 1. Both gas generator and staged combustion power cycles were analyzed for providing power to the turbopumps of the inner and outer combustors. Numerous cooling circuits and cooling fluids (propellants) were analyzed and hydrogen was selected as the preferred coolant for both combustors and the linear aerospike nozzle. The maximum operating chamber pressure was determined to be limited by the availability of hydrogen coolant pressure drop in the coolant circuit.

Diem, H. G.↗
NASA NTRS1978

A hingeless rotor XV-15 design integration feasibility study. Volume 1: Engineering design studies

A design integration feasibility study was carried out to investigate what modifications to the basic XV-15 were necessary to accomplish a flight demonstration of the XV-15 with a Boeing hingeless rotor. Also investigated were additional modifications which would exploit the full capability provided by the combination of the new rotor and the existing T53 engine. An evaluation of the aircraft is presented and the data indicate improved air vehicle performance, acceptable aeroelastic margins, lower noise levels and improved flying qualities compared with the XV-15 aircraft. Inspection of the rotor system data provided shows an essentially unlimited life rotor for the flight spectrum anticipated for the XV-15.

Magee, J. P.↗
NASA NTRS2015

Common Cause Failure Modeling

Common Cause Failures (CCFs) are a known and documented phenomenon that defeats system redundancy. CCFS are a set of dependent type of failures that can be caused by: system environments; manufacturing; transportation; storage; maintenance; and assembly, as examples. Since there are many factors that contribute to CCFs, the effects can be reduced, but they are difficult to eliminate entirely. Furthermore, failure databases sometimes fail to differentiate between independent and CCF (dependent) failure and data is limited, especially for launch vehicles. The Probabilistic Risk Assessment (PRA) of NASA's Safety and Mission Assurance Directorate at Marshall Space Flight Center (MFSC) is using generic data from the Nuclear Regulatory Commission's database of common cause failures at nuclear power plants to estimate CCF due to the lack of a more appropriate data source. There remains uncertainty in the actual magnitude of the common cause risk estimates for different systems at this stage of the design. Given the limited data about launch vehicle CCF and that launch vehicles are a highly redundant system by design, it is important to make design decisions to account for a range of values for independent and CCFs. When investigating the design of the one-out-of-two component redundant system for launch vehicles, a response surface was constructed to represent the impact of the independent failure rate versus a common cause beta factor effect on a system's failure probability. This presentation will define a CCF and review estimation calculations. It gives a summary of reduction methodologies and a review of examples of historical CCFs. Finally, it presents the response surface and discusses the results of the different CCFs on the reliability of a one-out-of-two system.

Hark, Frank↗
NASA NTRS2016

Common Cause Failure Modeling

Common Cause Failures (CCFs) are a known and documented phenomenon that defeats system redundancy. CCFS are a set of dependent type of failures that can be caused by: system environments; manufacturing; transportation; storage; maintenance; and assembly, as examples. Since there are many factors that contribute to CCFs, the effects can be reduced, but they are difficult to eliminate entirely. Furthermore, failure databases sometimes fail to differentiate between independent and CCF (dependent) failure and data is limited, especially for launch vehicles. The Probabilistic Risk Assessment (PRA) of NASA's Safety and Mission Assurance Directorate at Marshal Space Flight Center (MFSC) is using generic data from the Nuclear Regulatory Commission's database of common cause failures at nuclear power plants to estimate CCF due to the lack of a more appropriate data source. There remains uncertainty in the actual magnitude of the common cause risk estimates for different systems at this stage of the design. Given the limited data about launch vehicle CCF and that launch vehicles are a highly redundant system by design, it is important to make design decisions to account for a range of values for independent and CCFs. When investigating the design of the one-out-of-two component redundant system for launch vehicles, a response surface was constructed to represent the impact of the independent failure rate versus a common cause beta factor effect on a system's failure probability. This presentation will define a CCF and review estimation calculations. It gives a summary of reduction methodologies and a review of examples of historical CCFs. Finally, it presents the response surface and discusses the results of the different CCFs on the reliability of a one-out-of-two system.

Hark, Frank↗
NASA NTRS2006

An Alternative for Emergency Preemption of Traffic Lights

An electronic communication-and-control system has been developed as a prototype of advanced means of automatically modifying the switching of traffic lights to give priority to emergency vehicles. This system could be used alternatively or in addition to other emergency traffic-light-preemption systems, including a variety of systems now in use as well as two proposed systems described in "Systems Would Preempt Traffic Lights for Emergency Vehicles" (NPO-30573), NASA Tech Briefs, Vol. 28, No. 10 (October 2004), page 36. Unlike those prior systems that depend on detection of sounds and/or lights emitted by emergency vehicles, this system is not subject to severe range limitations. This system can be retrofitted into any pre-existing traffic-light-control system, without need to modify that system other than to make a minimal number of wire connections between the two systems. This system comprises several subsystems, including a transponder and interface circuitry on each emergency vehicle, a monitoring and control unit at each intersection equipped with traffic lights, and a wide-area two-way radio communication network that connects the emergency vehicles and intersection units. Computers in the various intersections and vehicle units run special-purpose software that implements the traffic- light-preemption scheme. The operations of the intersection and vehicle units are synchronized by use of Global Positioning System (GPS) timing signals. The transponder in each vehicle estimates its own position and velocity by use of GPS signals, deductive ("dead") reckoning, data from the onboard diagnostic (OBD) computer of the vehicle, and/or triangulation of beacon signals. When the operator of an emergency vehicle turns on its flashing lights and sirens in response to a request for an emergency response, the transponder unit goes into action, reading the OBD data to determine speed and acceleration, and reading and gathering further navigational data as described above. The position, velocity, and acceleration data are combined with vehicle-identification data in a prescribed format, and the resulting set of data is transmitted to the intersections within communication range of the transponder.

Foster, Conrad↗
NASA NTRS1979

Hydrogen-fueled postal vehicle performance evaluation

Fuel consumption, range, and emissions data were obtained while operating a hydrogen-fueled postal delivery vehicle over a defined Postal Service Driving Cycle and the 1975 Urban Driving Cycle. The vehicle's fuel consumption was 0.366 pounds of hydrogen per mile over the postal driving cycle and 0.22 pounds of hydrogen per mile over the urban driving cycle. These data correspond to 6.2 and 10.6 mpg equivalent gasoline mileage for the two driving cycles, respectively. The vehicle's range was 24.2 miles while being operated on the postal driving cycle. Vehicle emissions were measured over the urban driving cycle. HC and CO emissions were quite low, as would be expected. The oxides of nitrogen were found to be 4.86 gm/mi, a value which is well above the current Federal and California standards. Vehicle limitations discussed include excessive engine flashbacks, inadequate acceleration capability the engine air/fuel ratio, the water injection systems, and the cab temperature. Other concerns are safety considerations, iron-titanium hydride observed in the fuel system, evidence of water in the engine rocker cover, and the vehicle maintenance required during the evaluation.

Hall, R. A.↗
NASA NTRS1991

Vibroacoustic Payload Environment Prediction System (VAPEPS): VAPEPS management center remote access guide

A Vibroacoustic Payload Environment Prediction System (VAPEPS) Management Center was established at the JPL. The center utilizes the VAPEPS software package to manage a data base of Space Shuttle and expendable launch vehicle payload flight and ground test data. Remote terminal access over telephone lines to the computer system, where the program resides, was established to provide the payload community a convenient means of querying the global VAPEPS data base. This guide describes the functions of the VAPEPS Management Center and contains instructions for utilizing the resources of the center.

Fernandez, J. P.↗
NASA NTRS2015

Electron Beam Irradiated Intercalated CNT Yarns For Aerospace Applications

Multi-walled CNT yarns have been experimentally and commercially created to yield lightweight, high conductivity fibers with good tensile properties for application as electrical wiring and multifunctional tendons. Multifunctional tendons are needed as the cable structures in tensegrity robots for use in planetary exploration. These lightweight robust tendons can provide mechanical strength for movement of the robot in addition to power distribution and data transmission. In aerospace vehicles, such as Orion, electrical wiring and harnessing mass can approach half of the avionics mass. Use of CNT yarns as electrical power and data cables could reduce mass of the wiring by thirty to seventy percent. These fibers have been intercalated with mixed halogens to increase their specific electrical conductivity to that near copper. This conductivity, combined with the superior strength and fatigue resistance makes it an attractive alternative to copper for wiring and multifunctional tendon applications. Electron beam irradiation has been shown to increase mechanical strength in pristine CNT fibers through increased cross-linking. Both pristine and intercalated CNT yarns have been irradiated using a 5-megavolt electron beam for various durations and the conductivities and tensile properties will be discussed. Structural information obtained using a field emission scanning electron microscope, energy dispersive X-ray spectroscopy (EDS), and Raman spectroscopy will correlate microstructural details with bulk properties.

electrical wiring↗
NASA NTRS2020

Electromagnetic Compatibility Considerations for International Space Station Payload Developers

The International Space Station (ISS) is a laboratory for scientific research, innovative technology development, and global education. The ISS provides a number of facilities and platforms for payload developers and investigators to conduct biological, microgravity, and Earth and space observation science, as well as for performing technology development. Due to the unique nature of the ISS vehicle and its electrical power and data systems, achieving electromagnetic compatibility (EMC) with the vehicle requires special considerations by the payload developer. The ISS electromagnetic interference (EMI) requirements and test methods are based on MIL-STD-461, “Electromagnetic Emissions and Susceptibility Requirements for the Control of Electromagnetic Interference”, Revision C, and MIL-STD-462, “Electromagnetic Interference Characteristics, Measurement of,” respectively. The low source impedance of the test setup requires special considerations when designing or selecting EMI power filters and switched mode power supplies. Many filters, suited for later revisions of MIL-STD-461, will result in non-compliant designs. ISS electrical power system power quality requirements, imposed to protect the stability of the system, can also affect EMI filter design. The selection and use of commercial-off-the-shelf (COTS) equipment for ISS applications requires special considerations to meet both EMC and crew safety requirements. Furthermore, the ISS environment can provide unique immunity challenges; if the payload developer ignores these challenges, the result is a possible loss of science or impact to technology demonstration. The ISS provides a unique opportunity for the science and technology development community. However, in order to be successful, the payload developer must incorporate special EMC considerations, many of which will be presented.

McCollum, Matthew↗
NASA NTRS1974

Earth Observatory Satellite system definition study. Report no. 3: Design/cost tradeoff studies. Appendix A: EOS program WBS dictionary. Appendix B: EOS mission functional analysis

The work breakdown structure (WBS) dictionary for the Earth Observatory Satellite (EOS) is defined. The various elements of the EOS program are examined to include the aggregate of hardware, computer software, services, and data required to develop, produce, test, support, and operate the space vehicle and the companion ground data management system. A functional analysis of the EOS mission is developed. The operations for three typical EOS missions, Delta, Titan, and Shuttle launched are considered. The functions were determined for the top program elements, and the mission operations, function 2.0, was expanded to level one functions. Selection of ten level one functions for further analysis to level two and three functions were based on concern for the EOS operations and associated interfaces.

Source record↗
NASA NTRS1983

Development of environmental criteria guidelines for aerospace vehicle design

The types of guideline data on natural environmental conditions for the various major geographic locations that are applicable to the design of aerospace vehicles and associated equipment are discussed. Since relationships between aerospace vehicle parameters and atmospheric variables cannot always be clearly defined, there should be a close working relationship and team philosophy between the design/operational engineer and the respective organizations' aerospace meteorologists. Consideration should be given to protecting aerospace vehicles from some extremes by using support equipment and specialized monitoring personnel to advise on the expected occurrence of critical environmental conditions. It is pointed out that the services of these specialized personnel may be very economical in comparison with the more expensive designing that would be necessary to cope with all environmental possibilities. The environment considered here includes wind, atmospheric electricity, upper atmospheric density, and solar wind.

Turner, R. E.↗
NASA NTRS2002

Process Cost Modeling for Multi-Disciplinary Design Optimization

For early design concepts, the conventional approach to cost is normally some kind of parametric weight-based cost model. There is now ample evidence that this approach can be misleading and inaccurate. By the nature of its development, a parametric cost model requires historical data and is valid only if the new design is analogous to those for which the model was derived. Advanced aerospace vehicles have no historical production data and are nowhere near the vehicles of the past. Using an existing weight-based cost model would only lead to errors and distortions of the true production cost. This report outlines the development of a process-based cost model in which the physical elements of the vehicle are costed according to a first-order dynamics model. This theoretical cost model, first advocated by early work at MIT, has been expanded to cover the basic structures of an advanced aerospace vehicle. Elemental costs based on the geometry of the design can be summed up to provide an overall estimation of the total production cost for a design configuration. This capability to directly link any design configuration to realistic cost estimation is a key requirement for high payoff MDO problems. Another important consideration in this report is the handling of part or product complexity. Here the concept of cost modulus is introduced to take into account variability due to different materials, sizes, shapes, precision of fabrication, and equipment requirements. The most important implication of the development of the proposed process-based cost model is that different design configurations can now be quickly related to their cost estimates in a seamless calculation process easily implemented on any spreadsheet tool. In successive sections, the report addresses the issues of cost modeling as follows. First, an introduction is presented to provide the background for the research work. Next, a quick review of cost estimation techniques is made with the intention to highlight their inappropriateness for what is really needed at the conceptual phase of the design process. The First-Order Process Velocity Cost Model (FOPV) is discussed at length in the next section. This is followed by an application of the FOPV cost model to a generic wing. For designs that have no precedence as far as acquisition costs are concerned, cost data derived from the FOPV cost model may not be accurate enough because of new requirements for shape complexity, material, equipment and precision/tolerance. The concept of Cost Modulus is introduced at this point to compensate for these new burdens on the basic processes. This is treated in section 5. The cost of a design must be conveniently linked to its CAD representation. The interfacing of CAD models and spreadsheets containing the cost equations is the subject of the next section, section 6. The last section of the report is a summary of the progress made so far, and the anticipated research work to be achieved in the future.

Bao, Han P.↗
NASA NTRS2013

Structural Dynamics and Data Analysis

This project consists of two parts, the first will be the post-flight analysis of data from a Delta IV launch vehicle, and the second will be a Finite Element Analysis of a CubeSat. Shock and vibration data was collected on WGS-5 (Wideband Global SATCOM- 5) which was launched on a Delta IV launch vehicle. Using CAM (CAlculation with Matrices) software, the data is to be plotted into Time History, Shock Response Spectrum, and SPL (Sound Pressure Level) curves. In this format the data is to be reviewed and compared to flight instrumentation data from previous flights of the same launch vehicle. This is done to ensure the current mission environments, such as shock, random vibration, and acoustics, are not out of family with existing flight experience. In family means the peaks on the SRS curve for WGS-5 are similar to the peaks from the previous flights and there are no major outliers. The curves from the data will then be compiled into a useful format so that is can be peer reviewed then presented before an engineering review board if required. Also, the reviewed data will be uploaded to the Engineering Review Board Information System (ERBIS) to archive. The second part of this project is conducting Finite Element Analysis of a CubeSat. In 2010, Merritt Island High School partnered with NASA to design, build and launch a CubeSat. The team is now called StangSat in honor of their mascot, the mustang. Over the past few years, the StangSat team has built a satellite and has now been manifested for flight on a SpaceX Falcon 9 launch in 2014. To prepare for the final launch, a test flight was conducted in Mojave, California. StangSat was launched on a Prospector 18D, a high altitude rocket made by Garvey Spacecraft Corporation, along with their sister satellite CP9 built by California Polytechnic University. However, StangSat was damaged during an off nominal landing and this project will give beneficial insights into what loads the CubeSat experienced during the crash. During the year, the MIHS students generated a SolidWorks (CAD software) geometry model of StangSat. This model will be imported into FEMAP (Finite Element Analysis (FEA) Software) and a finite element model wiiJ be created to predict the loads encountered during the crash of this rocket. This analysis will require learning how to import CAD models into the FEM, mesh and add constraints and concentrated masses to represent components inside the CubeSat frame, such as circuit boards, batteries and accelerometers. During the analysis the loads will be varied, in effort to duplicate the damage to the CubeSat. Results will then be peer reviewed and documented.

Luthman, Briana L.↗
NASA NTRS2012

Current CFD Practices in Launch Vehicle Applications

The quest for sustained space exploration will require the development of advanced launch vehicles, and efficient and reliable operating systems. Development of launch vehicles via test-fail-fix approach is very expensive and time consuming. For decision making, modeling and simulation (M&S) has played increasingly important roles in many aspects of launch vehicle development. It is therefore essential to develop and maintain most advanced M&S capability. More specifically computational fluid dynamics (CFD) has been providing critical data for developing launch vehicles complementing expensive testing. During the past three decades CFD capability has increased remarkably along with advances in computer hardware and computing technology. However, most of the fundamental CFD capability in launch vehicle applications is derived from the past advances. Specific gaps in the solution procedures are being filled primarily through "piggy backed" efforts.on various projects while solving today's problems. Therefore, some of the advanced capabilities are not readily available for various new tasks, and mission-support problems are often analyzed using ad hoc approaches. The current report is intended to present our view on state-of-the-art (SOA) in CFD and its shortcomings in support of space transport vehicle development. Best practices in solving current issues will be discussed using examples from ascending launch vehicles. Some of the pacing will be discussed in conjunction with these examples.

Kwak, Dochan↗
NASA NTRS2005

Traffic-Light-Preemption Vehicle-Transponder Software Module

A prototype wireless data-communication and control system automatically modifies the switching of traffic lights to give priority to emergency vehicles. The system, which was reported in several NASA Tech Briefs articles at earlier stages of development, includes a transponder on each emergency vehicle, a monitoring and control unit (an intersection controller) at each intersection equipped with traffic lights, and a central monitoring subsystem. An essential component of the system is a software module executed by a microcontroller in each transponder. This module integrates and broadcasts data on the position, velocity, acceleration, and emergency status of the vehicle. The position, velocity, and acceleration data are derived partly from the Global Positioning System, partly from deductive reckoning, and partly from a diagnostic computer aboard the vehicle. The software module also monitors similar broadcasts from other vehicles and from intersection controllers, informs the driver of which intersections it controls, and generates visible and audible alerts to inform the driver of any other emergency vehicles that are close enough to create a potential hazard. The execution of the software module can be monitored remotely and the module can be upgraded remotely and, hence, automatically

Bachelder, Aaron↗
NASA NTRS2003

Vortex Flows at Supersonic Speeds

A review of research conducted at the National Aeronautics and Space Administration (NASA) Langley Research Center (LaRC) into high-speed vortex flows during the 1970s, 1980s, and 1990s is presented. The data are for flat plates, cavities, bodies, missiles, wings, and aircraft with Mach numbers of 1.5 to 4.6. Data are presented to show the types of vortex structures that occur at supersonic speeds and the impact of these flow structures on vehicle performance and control. The data show the presence of both small- and large-scale vortex structures for a variety of vehicles, from missiles to transports. For cavities, the data show very complex multiple vortex structures exist at all combinations of cavity depth to length ratios and Mach number. The data for missiles show the existence of very strong interference effects between body and/or fin vortices. Data are shown that highlight the effect of leading-edge sweep, leading-edge bluntness, wing thickness, location of maximum thickness, and camber on the aerodynamics of and flow over delta wings. Finally, a discussion of a design approach for wings that use vortex flows for improved aerodynamic performance at supersonic speeds is presented.

Wood, Richard M.↗
NASA NTRS1974

Transportation vehicle energy intensities. A joint DOT/NASA reference paper

A compilation of data on the energy consumption of air and ground vehicles is presented. The ratio BTU/ASM, British Thermal Units/Available Seat Mile, is used to express vehicle energy intensiveness, and related to the energy consumed directly in producing seat-mile or ton-mile productivity. Data is presented on passenger and freight vehicles which are in current use or which are about to enter service, and advanced vehicles which may be operational in the 1980's and beyond. For the advanced vehicles, an estimate is given of the date of initial operational service, and the performance characteristics. Other key considerations in interpreting energy intensiveness for a given mode are discussed, such as: load factors, operations, overhead energy consumption, and energy investments in new structure and equipment.

Mascy, A. C.↗