Search NASA⌕ Search

SEARCH · Search NASA

Results for “Engine Ground Testing”

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 649 records · Page 36

Performance of a 300-horsepower Hispano-Suiza airplane engine

The National Bureau of Standards tested a 300-horsepower Hispano-Suiza engine to determine the characteristic performance of the engine at various altitudes. The engine was operated at the ground, at 25,000 feet, and at intermediate altitudes, both at full loads similar to those that would be imposed upon the engine at various speeds by a propeller whose normal full-load speed was 1,800 r.p.m. Friction horsepower also was determined in order that the mechanical efficiency of the engine might be calculated. From the test data there were computed the brake horsepower, brake mean effective pressure, specific fuel consumption, mixture ratio, jacket loss, exhaust loss, and thermal, mechanical, and volumetric efficiencies. A record of jacket water temperatures, oil temperatures, manifold pressures, etc., shows the conditions under which the test was made.

Sparrow, S W↗

A Combustion Research Facility for Testing Advanced Materials for Space Applications

The test facility presented herein uses a groundbased rocket combustor to test the durability of new ceramic composite and metallic materials in a rocket engine thermal environment. A gaseous H2/02 rocket combustor (essentially a ground-based rocket engine) is used to generate a high temperature/high heat flux environment to which advanced ceramic and/or metallic materials are exposed. These materials can either be an integral part of the combustor (nozzle, thrust chamber etc) or can be mounted downstream of the combustor in the combustor exhaust plume. The test materials can be uncooled, water cooled or cooled with gaseous hydrogen.

Bur, Michael J.↗

Wind-Tunnel Overpressure Signatures From a Low-Boom HSCT Concept With Aft-Fuselage-Mounted Engines

A 1:300 scale wind-tunnel model of a conceptual High-Speed Civil Transport (HSCT) designed to generate a shaped, low-boom pressure signature on the ground was tested to obtain sonic-boom pressure signatures in the Langley Research Center Unitary Plan Wind Tunnel at a Mach number of 1.8 and a separation distance of about two body lengths or four wing-spans from the model. Two sets of engine nacelles representing two levels of engine technology were used on the model to determine the effects of increased nacelle volume. Pressure signatures were measured for (model lift)/(design lift) ratios of 0.5, 0.63, 0.75, and 1.0 so that the effect of lift on the pressure signature could be determined. The results of these tests were analyzed and used to discuss the agreement between experimental data and design expectations.

Mack, Robert J.↗

Fault detection and accommodation testing on an F100 engine in an F-15 airplane

The fault detection and accommodation (FDA) methodology for digital engine-control systems may range from simple comparisons of redundant parameters to the more complex and sophisticated observer models of the entire engine system. Evaluations of the various FDA schemes are done using analytical methods, simulation, and limited-altitude-facility testing. Flight testing of the FDA logic has been minimal because of the difficulty of inducing realistic faults in flight. A flight program was conducted to evaluate the fault detection and accommodation capability of a digital electronic engine control in an F-15 aircraft. The objective of the flight program was to induce selected faults and evaluate the resulting actions of the digital engine controller. Comparisons were made between the flight results and predictions. Several anomalies were found in flight and during the ground test. Simulation results showed that the inducement of dual pressure failures was not feasible since the FDA logic was not designed to accommodate these types of failures.

Myers, L. P.↗

A Saturn launched X-ray astronomy experiment. Volume 1: S-027

The S-027 X-Ray Astronomy Experiment originally proposed in early 1966, was developed to detect X-rays in the 2 keV to 10 keV range. Both a prototype unit and flight unit were constructed with the prototype unit also serving as the engineering model, the qualification test unit, and after refurbishment, as the back-up flight unit. Two Ground Support Equipment consoles were built to verify the experiment operation. A photograph of one experiment package with its Ground Support Equipment is shown. The S-027 experiment was scheduled for launch in 1968/69 and although both units were completed and tested to the extent that either would be ready for the scheduled launch, delays in the space program resulted in a launch date slip of several years. When the 1968/69 launch delay became official, provisions were made for storage of the two experiment packages at SCI Electronics in Huntsville, Alabama until a new launch date could be established.

Source record↗

OAST Space Theme Workshop. Volume 3: Working group summary. 9: Aerothermodynamics (M-3). A: Statement. B: Technology needs (form 1). C. Priority assessment (form 2). D. Additional assessments

Twelve aerothermodynamic space technology needs were identified to reduce the design uncertainties in aerodynamic heating and forces experienced by heavy lift launch vehicles, orbit transfer vehicles, and advanced single stage to orbit vehicles for the space transportation system, and for probes, planetary surface landers, and sample return vehicles for solar system exploration vehicles. Research and technology needs identified include: (1) increasing the fluid dynamics capability by at least two orders of magnitude by developing an advanced computer processor for the solution of fluid dynamic problems with improved software; (2) predicting multi-engine base flow fields for launch vehicles; and (3) developing methods to conserve energy in aerothermodynamic ground test facilities.

Source record↗

Flight tests and preliminary aerodynamic parameter extraction of an externally piloted vehicle aircraft model

Model aircraft flight test investigations have been undertaken to develop a low cost flight data acquisition system and to evaluate aerodynamic parameter estimation techniques. The externally piloted vehicles (EPVs) used are instrumented with sensors measuring acceleration, angular rates, angles of attack and sideslip, flight path velocity, and control deflections. Measured state variables are downlink telemetered to a ground-based real time flight data acquisition system; the data thus recorded are used by flight test engineers and EPV pilots to monitor conditions and aid in piloting tasks. Attention is given to comparisons of F-16 EPV data with wind tunnel data.

White, E. R.↗

Application of Single Crystal Failure Criteria: Theory and Turbine Blade Case Study

The orientation of the single crystal material within a structural component is known to affect the strength and life of the part. The first stage blade of the High Pressure Fuel Turbopump (HPFTP)/ Alternative Turbopump Development (ATD), of the Space Shuttle Main Engine (SSME) was used to study the effects of secondary axis'orientation angles on the failure rate of the blade. A new failure criterion was developed based on normal and shear strains on the primary crystallographic planes. The criterion was verified using low cycle fatigue (LCF) specimen data and a finite element model of the test specimens. The criterion was then used to study ATD/HPFTP first stage blade failure events. A detailed ANSYS finite element model of the blade was used to calculate the failure parameter for the different crystallographic orientations. A total of 297 cases were run to cover a wide range of acceptable orientations within the blade. Those orientations are related to the base crystallographic coordinate system that was created in the ANSYS finite element model. Contour plots of the criterion as a function of orientation for the blade tip and attachment were obtained. Results of the analysis revealed a 40% increase in the failure parameter due to changing of the primary and secondary axes of material orientations. A comparison between failure criterion predictions and actual engine test data was then conducted. The engine test data comes from two ATD/HPFTP builds (units F3- 4B and F6-5D), which were ground tested on the SSME at the Stennis Space Center in Mississippi. Both units experienced cracking of the airfoil tips in multiple blades, but only a few cracks grew all the way across the wall of the hollow core airfoil.

Sayyah, Tarek↗

NASA's Space Launch System Moves into Testing and Integration

NASA's Space Launch System (SLS) has moved from design and manufacturing into testing and integration for its first flight as early as December 2019. In 2017, the NASA/industry team completed manufacturing of all major structural elements for the launch vehicle for Exploration Mission-I (EM-1 ). That work included shipping the first major flight hardware element to the launch site. The team processed all four RS-25 engines for stage integration, cast all 10 booster flight motor segments, and manufactured all five major sections of the core stage. The program also completed major structural work on the B-2 test stand at Stennis Space Center, which will be used for the core stage "green run" test; delivered the core stage and engine simulators used for training; and much of the transportation equipment for the core stage. Engineers completed structural testing on the upper stage/payload section of the vehicle as well as the engine section test article. In 2018, the program will deliver the Orion Stage Adapter (OSA) to Exploration Ground Systems (EGS) at KSC and send the test articles for the core stage liquid hydrogen tank, liquid oxygen tank, and intertank to NASA's Marshall Space Flight center for structural testing. Additionally, workers will begin the challenging process of integrating the major sections of the 212-foot EM-1 core stage. This work is focused on the initial Block 1 variant of SLS, capable of launching more than 70 metric tons (t) to low Earth orbit (LEO). However, work concurrently is underway on the Block lB variant, which will enable 105 t to LEO and more than 37t to trans-lunar injection (TLI). Block lB will be the workhorse vehicle of NASA's lunar exploration plans. As the needs of the nation's deep space exploration program grow, SLS performance is designed to evolve to a payload mass of 130 t to LEO and up to 45t to TLI. The advantages of this mass - as well as volume- are critical to the entire exploration architecture for deep space exploration. They translate to greater capability, greater infrastructure and operational simplicity, less overall mission risk, and opportunities to accomplish unprecedented exploration and discovery. This paper will discuss SLS progress to date and planned future work.

Honeycutt, John↗

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗

Reynolds-Averaged Turbulence Model Assessment for a Highly Back-Pressured Isolator Flowfield

The use of computational fluid dynamics in scramjet engine component development is widespread in the existing literature. Unfortunately, the quantification of model-form uncertainties is rarely addressed with anything other than sensitivity studies, requiring that the computational results be intimately tied to and calibrated against existing test data. This practice must be replaced with a formal uncertainty quantification process for computational fluid dynamics to play an expanded role in the system design, development, and flight certification process. Due to ground test facility limitations, this expanded role is believed to be a requirement by some in the test and evaluation community if scramjet engines are to be given serious consideration as a viable propulsion device. An effort has been initiated at the NASA Langley Research Center to validate several turbulence closure models used for Reynolds-averaged simulations of scramjet isolator flows. The turbulence models considered were the Menter BSL, Menter SST, Wilcox 1998, Wilcox 2006, and the Gatski-Speziale explicit algebraic Reynolds stress models. The simulations were carried out using the VULCAN computational fluid dynamics package developed at the NASA Langley Research Center. A procedure to quantify the numerical errors was developed to account for discretization errors in the validation process. This procedure utilized the grid convergence index defined by Roache as a bounding estimate for the numerical error. The validation data was collected from a mechanically back-pressured constant area (1 2 inch) isolator model with an isolator entrance Mach number of 2.5. As expected, the model-form uncertainty was substantial for the shock-dominated, massively separated flowfield within the isolator as evidenced by a 6 duct height variation in shock train length depending on the turbulence model employed. Generally speaking, the turbulence models that did not include an explicit stress limiter more closely matched the measured surface pressures. This observation is somewhat surprising, given that stress-limiting models have generally been developed to better predict shock-separated flows. All of the models considered also failed to properly predict the shape and extent of the separated flow region caused by the shock boundary layer interactions. However, the best performing models were able to predict the isolator shock train length (an important metric for isolator operability margin) to within 1 isolator duct height.

Baurle, Robert A.↗

Aerodynamic and acoustic behavior of a YF-12 inlet at static conditions

An aeroacoustic test program to determine the cause of YF-12 inlet noise suppression was performed with a YF-12 aircraft at ground static conditions. Data obtained over a wide range of engine speeds and inlet configurations are reported. Acoustic measurements were made in the far field and aerodynamic and acoustic measurements were made inside the inlet. The J-58 test engine was removed from the aircraft and tested separately with a bellmouth inlet. The far field noise level was significantly lower for the YF-12 inlet than for the bellmouth inlet at engine speeds above 5500 rpm. There was no evidence that noise suppression was caused by flow choking. Multiple pure tones were reduced and the spectral peak near the blade passing frequency disappeared in the region of the spike support struts at engine speeds between 6000 and 6600 rpm.

Bangert, L. H.↗

Engine inlet distortion in a 9.2 percent scale vectored thrust STOVL model in ground effect

Advanced Short Takeoff/Vertical Landing (STOVL) aircraft which can operate from remote locations, damaged runways, and small air capable ships are being pursued for deployment around the turn of the century. To achieve this goal, NASA Lewis Research Center, McDonnell Douglas Aircraft, and DARPA defined a cooperative program for testing in the NASA Lewis 9- by 15-foot low speed wind tunnel (LSWT) to establish a database for hot gas ingestion, one of the technologies critical to STOVL. Results are presented which show the engine inlet distortions (both temperature and pressure) in a 9.2 percent scale vectored thrust STOVL model in ground effects. Results are shown for the forward nozzle splay angles of 0 degrees, -6 degrees, and 18 degrees. The model support system had 4 degrees of freedom, heated high pressure air for nozzle flow, and a suction system exhaust for inlet flow. The headwind (freestream) velocity was varied from 8 to 23 knots.

Johns, Albert L.↗

Scramjet testing from Mach 4 to 20 - Present capability and needs for the nineties

Consideration is given to the development of testing methods for the National Aerospace Plane (NASP) program, focusing on techniques for simulating and testing scramjet engines and scramjet engine components during flight from Mach 4 to Mach 20. The flight conditions associated with the NASP are outlined and the stagnation temperatures and pressures required to simulate flight up to orbital speeds are presented. The types of test facilities needed for scramjet propulsion testing are discussed, including combustion-heated facilities, electric arc-heated facilities, convection-heated facilities, shock tunnels, and expansion tubes. Issues related to assessing the flow quality in the scramjet ground testing facilities are examined, including uniformity, contamination, dissociation, ionization, nonequilibrium, and turbulence. Direct-connect combustor versus free-jet scramjet engine tests are compared and the capabilities of current and near-future scramjet engine test facilities are evaluated.

Thomas, Scott R.↗

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗

Avoiding Human Error in Mission Operations: Cassini Flight Experience

Operating spacecraft is a never-ending challenge and the risk of human error is ever- present. Many missions have been significantly affected by human error on the part of ground controllers. The Cassini mission at Saturn has not been immune to human error, but Cassini operations engineers use tools and follow processes that find and correct most human errors before they reach the spacecraft. What is needed are skilled engineers with good technical knowledge, good interpersonal communications, quality ground software, regular peer reviews, up-to-date procedures, as well as careful attention to detail and the discipline to test and verify all commands that will be sent to the spacecraft. Two areas of special concern are changes to flight software and response to in-flight anomalies. The Cassini team has a lot of practical experience in all these areas and they have found that well-trained engineers with good tools who follow clear procedures can catch most errors before they get into command sequences to be sent to the spacecraft. Finally, having a robust and fault-tolerant spacecraft that allows ground controllers excellent visibility of its condition is the most important way to ensure human error does not compromise the mission.

guidance and control↗

Initial Test Firing Results for Solid CO/GOX Cryogenic Hybrid Rocket Engine for Mars ISRU Propulsion Applications

ORBITEC is developing methods for producing, testing, and utilizing Mars-based ISRU fuel/oxidizer combinations to support low cost, planetary surface and flight propulsion and power systems. When humans explore Mars we will need to use in situ resources that are available, such as: energy (solar); gases or liquids for life support, ground transportation, and flight to and from other surface locations and Earth; and materials for shielding and building habitats and infrastructure. Probably the easiest use of Martian resources to reduce the cost of human exploration activities is the use of the carbon and oxygen readily available from the CO2 in the Mars atmosphere. ORBITEC has conducted preliminary R&D that will eventually allow us to reliably use these resources. ORBITEC is focusing on the innovative use of solid CO as a fuel. A new advanced cryogenic hybrid rocket propulsion system is suggested that will offer advantages over LCO/LOX propulsion, making it the best option for a Mars sample return vehicle and other flight vehicles. This technology could also greatly support logistics and base operations by providing a reliable and simple way to store solar or nuclear generated energy in the form of chemical energy that can be used for ground transportation (rovers/land vehicles) and planetary surface power generators. This paper describes the overall concept and the test results of the first ever solid carbon monoxide/oxygen rocket engine firing.

Rice, Eric E.↗

Propulsion Controlled Aircraft design and development

This paper describes the design, development, and ground testing of the propulsion controlled aircraft (PCA) flight control system. A backup flight control system which uses only engine thrust, the PCA system utilizes collective and differential thrust changes to steer an aircraft that experiences partial or complete failure of the hydraulically actuated control surfaces. The objective of the program was to investigate, in flight, the throttles-only control capability of the F-15, using manual control, and also an augmented PCA mode in which computer-controlled thrust was used for flight control. The objective included PCA operation in up-and-away flight and, if performance was adequate, a secondary objective to make actual PCA landings. The PCA design began with a feasibility study which evaluated many control law designs. The study was done using off-line control analysis, simulation, and on-line manned flight simulator tests. Control laws, cockpit displays, and cockpit controls were evaluated by NASA test pilots. A flight test baseline configuration was selected based on projected flight performance, applicability to transport and fighter aircraft, and funding costs. During the PCA software and hardware development, the initial design was updated as data became available from throttle-only flight experiments conducted by NASA on the F-15. This information showed basic airframe characteristics that were not observed in the F-15 flight simulator and resulted in several design changes. After the primary objectives of the PCA flight testing were accomplished, additional PCA modes of operation were developed and implemented. The evolution of the PCA system from the initial feasibility study, control law design, simulation, hardware-in-the-loop tests, pilot-in-the-loop tests, and ground tests is presented.

Wells, Edward A.↗