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 1,243 records · Page 69

Technical and Programmatic Consequences of a Hypersonic Vehicle Flight Test Ban

The hypersonic vehicle (HV) is defined as any vehicle capable of traveling at or above five times the local speed of sound (Mach 5). Development of hypersonic flight has been pursued since the late 1950s, especially for reentry of missile warheads and returning orbiting spacecraft. Although considerable progress has been made since then, air- breathing and gliding hypersonic flight remains in the development and testing phase. Concerns have been raised, however, about continued HV flight tests because of HV's potential military use, which has the potential to encourage hair-trigger tactics that would increase crisis instability. In recent years, non-governmental organizations have called for a ban on HV flight testing for the primary purpose of halting continued development of the HV as a weapon. The emphasis on banning flight tests is due to its vital role in aerospace programs. Without it, significant technical uncertainties remain, creating safety and reliability issues that would discourage commercial development. Although the cost and time involved in flight tests have already spurred the use of other test methods, none can completely reproduce the flight test environment. Flight tests are important for reasons such as generating data unique to flight test environments to use in validating models and verifying ground test data, identifying unanticipated problems, and reducing risk. Commercial HV technology development today depends on advancements in four areas: propulsion; aerodynamics; critical guidance, navigation and control; and thermal management. This report summarizes the ramifications on HV technology development if flight tests were banned.

42 ENGINEERING↗

Life sciences Spacelab Mission Development test 3 (SMD 3) data management report

Development of a permanent data system for SMD tests was studied that would simulate all elements of the shuttle onboard, telemetry, and ground data systems that are involved with spacelab operations. The onboard data system (ODS) and the ground data system (GDS) were utilized. The air-to-ground link was simulated by a hardwired computer-to-computer interface. A patch board system was used on board to select experiment inputs, and the downlink configuration from the ODS was changed by a crew keyboard entry to support each experiment. The ODS provided a CRT display of experiment parameters to enable the crew to monitor experiment performance. An onboard analog system, with recording capability, was installed to handle high rate data and to provide a backup to the digital system. The GDS accomplished engineering unit conversion and limit sensing, and provided realtime parameter display on CRT's in the science monitoring area and the test control area.

Moseley, E. C.↗

Acoustic Phased Array Quantification of Quiet Technology Demonstrator 3 Advanced Inlet Liner Noise Component

Acoustic phased array flyover noise measurements were acquired as part of the Boeing 737 MAX-7 NASA Advanced Inlet Liner segment of the Quiet Technology Demonstrator 3 (QTD3) flight test program. This paper reports on the processes used for separating and quantifying the engine inlet, exhaust and airframe noise source components and provides sample phased array-based comparisons of the component noise source levels associated with the inlet liner treatment configurations. Full scale flyover noise testing of NASA advanced inlet liners was conducted as part of the Quiet Technology Demonstrator 3 flight test program in July and August of 2018. Details on the inlet designs and testing are provided in the companion paper of Reference 1. The present paper provides supplemental details relating to the acoustic phased array portion of the analyses provided in Ref. 1. In brief, the test article was a Boeing 737MAX-7 aircraft with a modified right hand (starboard side) engine inlet, which consisted of either a production inlet liner, a NASA designed inlet liner or a simulated hard wall configuration (accomplished by applying speed tape over the inlet acoustic treatment areas). In all three configurations, the engine forward fan case acoustic panel was replaced with a unperforated (hardwall) panel. No other modifications to any other acoustic treatment areas were made. The left hand (port side) engine was a production engine and was flown at idle thrust for all measurements in order to isolate the effects of the inlet liners to the right hand engine. As described in Ref. 1, the NASA inlet treatment consists of laterally cut slots (cut perpendicular to the flow direction) which are designed to reduce excrescence drag while maintaining or exceeding the liner acoustic noise reduction capabilities. The NASA inlet liner consists of a Multi-Degree of Freedom (MDOF) design with two breathable septum layers inserted into each honeycomb cell [1]. The aircraft noise measurements were acquired for both takeoff (flaps 1 setting, gear up) and approach (flaps 30 gear up and gear down) configurations. The inlet and flight test configurations are summarized in Table 1. Table 1: Inlet Treatment and Flight Configurations Inlet Forward Fan Case Aircraft Production Hardwall Flaps 1, gear up; flaps 30 gear up; flaps 30 gear down NASA Hardwall Flaps 1, gear up; flaps 30 gear up; flaps 30 gear down Hardwall Hardwall Flaps 1, gear up; flaps 30 gear up; flaps 30 gear down III.Test Description and Hardware The flight testing was conducted at the Grant County airport in Moses Lake, WA, between 27 July and 6 August 2018. The noise measurement instrumentation included 8 flush dish microphones arranged in a noise certification configuration as well as an 840 microphone phased array. The flush dish microphones were used to quantify the levels and differences in levels between the various inlet treatments. The phased array was used to separate and quantify the narrowband (tonal) and broadband noise component levels from the engine inlet/exhaust and from the airframe. Phased array extraction of the broadband component was critical to this study because it allowed for the separation of the inlet component from the total airplane level noise even when it was significantly below the total level. Figure 1 provides an overview of the phased array microphone layout as well as a detailed image of an individual phased array microphone mounted in a plate holder (the microphone sensor is the dot in the center of the plate). The ground plane ensemble array microphones (referred to as “ensemble array” in this paper) were mounted in plates with “flower petal” edges designed to minimize edge scattering effects. Fig. 1 Flyover test microphone layout. The phased array configuration was the result of a progressive development of concepts originally implemented in Ref. 2 and refined over the following years, consisting namely of multiple multi-arm logarithmic spiral subarrays designed to cover overlapping frequency ranges and optimized for various aircraft emission angles. For the present case, the signals from all 840 microphones were acquired on a single system. The 840 microphones were parsed into 11 primary subarray sets spanning from smallest to largest aperture size and labeled accordingly as “a, b, …, k”, where “a” corresponds to the smallest fielded subarray and “k” corresponds to the largest aperture subarray. The apertures ranged from approximately 10 ft to 427 ft in size (in the flight direction) with the subarrays consisting of between 215 and 312 microphones. Figure 2 shows three such subarrays, k, h and a. As done in Ref. 2, microphones were shared between subarrays in order to reduce total channel count. Fig. 2 Sample subarray sizes (20° from overhead – refer to Figure 3a discussion). In addition to the above, each of the 11 primary subarray sets consisted of four subarrays optimized to provide near equivalent array spatial resolution in both the flight and lateral directions within 30 degrees of overhead (i.e., airplane directly above the center of the array), namely, at angles  of 0, ±10, ±20 and ±30 degrees relative to overhead where angle  is defined as shown in Figure 3a. This allowed for optimized aircraft noise measurements from 60 to 120 degree emission angle.6 An example of this pletharray design is shown in Figure 3b for the k subarray. When the aircraft is at overhead, the microphones indicated by the blue markers are used for beamforming. When the aircraft is at angles ±10 degrees from overhead, both the blue and red colored microphones are used, and so on for the ±20 and ±30 degree aircraft locations. See Ref. 3 for extensive details on pletharray design for aeroacoustic phased array testing. 6 In the discussions that follow, emission angle values are used. These are the angles at the time sound is emitted relative to the engine axis and are calculated based on flight path angle, body aircraft body angle with respect to the relative wind direction, and engine axis angle relative to aircraft body angle.

Brusniak, Leon↗

Ubiquitous Nuclear Threat Detection Final Report, Harvey Mudd College Engineering Clinic

The Lawrence Livermore National Labs clinic team was asked to design a repeatable, portable procedure that would incentivize participants to carry detectors that form a radiation sensor network along repeated paths, to precisely known locations and past known radioactive sources. To achieve these goals, the team designed day-long and week-long data collection procedures in the form of puzzle hunt events. The team also created an Android app in order to support this measurement campaign and foster engagement. A ground truth collection method was constructed and validated through repeated use. Information concerning effective deployment of the data-collection procedure was gathered for future iterations. Over the course of procedural testing, 6 de 17 HMC students participated and collected 250 hours of data. 3 deployments of the procedure were conducted in each semester. A total of 63 students participated and collected 300 hours of data over the year. Deployment 1: 16 students, Deployment 2: 17 students, Deployment 3: 8 users, ~18 active hours, Deployment 4: 4 students, ~10 active hours, and Deployment 5: 18 students, ~40 active hours.

42 ENGINEERING↗

The deep space network, volume 6

Progress on Deep Space Network (DSN) supporting research and technology is presented, together with advanced development and engineering, implementation, and DSN operations of flight projects. The DSN is described. Interplanetary and planetary flight projects and radio science experiments are discussed. Tracking and navigational accuracy analysis, communications systems and elements research, and supporting research are considered. Development of the ground communications and deep space instrumentation facilities is also presented. Network allocation schedules and angle tracking and test development are included.

Source record↗

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

An aeroacoustic test program was performed with a YF-12 aircraft at ground static conditions. The objective was to collect acoustic and aerodynamic data that could determine the cause of YF-12 inlet noise suppression observed earlier. The results showed that the far-field noise level was lower with the YF-12 inlet than with a bellmouth inlet at engine speeds above 5500 rpm. The differences were about 5 PNdB to 11 PNdB, depending on YF-12 inlet configuration and on engine speed. Measurements showed that YF-12 inlet noise suppression was not caused by flow choking. The spike support struts were probably responsible, as in that region the spectral peak near the blade passing frequency disappeared between 6000 and 6600 rpm, and multiple pure tones were greatly reduced.

Bangert, L. H.↗

SPS technical issues

The technical issues which would either seriously impact or potentially negate the integrity of a solar power satellite program are enumerated. Issues are identified not only relating to the question of engineering feasibility, but also to the equally important areas of environmental and social acceptability and, especially, economic viability. Specific information required for resolution of the issues was developed and a planned overall approach for resolution was identified. Results of these analyses show that 60% of the technical issues can be resolved with analysis only; 10% require only ground testing for resolution; and the remaining 30% require space experiments or demonstrations for resolution. The results also show that 85% resolution of the issues may be accomplished prior to development of a protoype.

Guttman, C. H.↗

Flexible structure control experiments using a real-time workstation for computer-aided control engineering

A Real-Time Workstation for Computer-Aided Control Engineering has been developed jointly by the Communications Research Centre (CRC) and Ruhr-Universitaet Bochum (RUB), West Germany. The system is presently used for the development and experimental verification of control techniques for large space systems with significant structural flexibility. The Real-Time Workstation essentially is an implementation of RUB's extensive Computer-Aided Control Engineering package KEDDC on an INTEL micro-computer running under the RMS real-time operating system. The portable system supports system identification, analysis, control design and simulation, as well as the immediate implementation and test of control systems. The Real-Time Workstation is currently being used by CRC to study control/structure interaction on a ground-based structure called DAISY, whose design was inspired by a reflector antenna. DAISY emulates the dynamics of a large flexible spacecraft with the following characteristics: rigid body modes, many clustered vibration modes with low frequencies and extremely low damping. The Real-Time Workstation was found to be a very powerful tool for experimental studies, supporting control design and simulation, and conducting and evaluating tests withn one integrated environment.

Stieber, Michael E.↗

Constellation's First Flight Test: Ares I-X

On October 28, 2009, NASA launched Ares I-X, the first flight test of the Constellation Program that will send human beings to the Moon and beyond. This successful test is the culmination of a three-and-a-half-year, multi-center effort to design, build, and fly the first demonstration vehicle of the Ares I crew launch vehicle, the successor vehicle to the Space Shuttle. The suborbital mission was designed to evaluate the atmospheric flight characteristics of a vehicle dynamically similar to Ares I; perform a first stage separation and evaluate its effects; characterize and control roll torque; stack, fly, and recover a solid-motor first stage testing the Ares I parachutes; characterize ground, flight, and reentry environments; and develop and execute new ground hardware and procedures. Built from existing flight and new simulator hardware, Ares I-X integrated a Shuttle-heritage four-segment solid rocket booster for first stage propulsion, a spacer segment to simulate a five-segment booster, Peacekeeper axial engines for roll control, and Atlas V avionics, as well as simulators for the upper stage, crew module, and launch abort system. The mission leveraged existing logistical and ground support equipment while also developing new ones to accommodate the first in-line rocket for flying astronauts since the Saturn IB last flew from Kennedy Space Center (KSC) in 1975. This paper will describe the development and integration of the various vehicle and ground elements, from conception to stacking in KSC s Vehicle Assembly Building; hardware performance prior to, during, and after the launch; and preliminary lessons and data gathered from the flight. While the Constellation Program is currently under review, Ares I-X has and will continue to provide vital lessons for NASA personnel in taking a vehicle concept from design to flight.

Davis, Stephan R.↗

A proven approach for more effective software development and maintenance

Modern space flight mission operations and associated ground data systems are increasingly dependent upon reliable, quality software. Critical functions such as command load preparation, health and status monitoring, communications link scheduling and conflict resolution, and transparent gateway protocol conversion are routinely performed by software. Given budget constraints and the ever increasing capabilities of processor technology, the next generation of control centers and data systems will be even more dependent upon software across all aspects of performance. A key challenge now is to implement improved engineering, management, and assurance processes for the development and maintenance of that software; processes that cost less, yield higher quality products, and that self-correct for continual improvement evolution. The NASA Goddard Space Flight Center has a unique experience base that can be readily tapped to help solve the software challenge. Over the past eighteen years, the Software Engineering Laboratory within the code 500 Flight Dynamics Division has evolved a software development and maintenance methodology that accommodates the unique characteristics of an organization while optimizing and continually improving the organization's software capabilities. This methodology relies upon measurement, analysis, and feedback much analogous to that of control loop systems. It is an approach with a time-tested track record proven through repeated applications across a broad range of operational software development and maintenance projects. This paper describes the software improvement methodology employed by the Software Engineering Laboratory, and how it has been exploited within the Flight Dynamics Division with GSFC Code 500. Examples of specific improvement in the software itself and its processes are presented to illustrate the effectiveness of the methodology. Finally, the initial findings are given when this methodology was applied across the mission operations and ground data systems software domains throughout Code 500.

Pajerski, Rose↗

One-man, self-contained CO2 concentrating system

A program to design, fabricate, and test a 1-man, self-contained, electrochemical CO2 concentrating system is described. The system was designed with electronic controls and instrumentation to regulate performance, to analyze and display performance trends, and to detect and isolate faults. Ground support accessories were included to provide power, fluids, and a Parametric Data Display allowing real time indication of operating status in engineering units.

Wynveen, R. A.↗

Electronic delay ignition module for single bridgewire Apollo standard initiator

An engineering model and a qualification model of the EDIM were constructed and tested to Scout flight qualification criteria. The qualification model incorporated design improvements resulting from the engineering model tests. Compatibility with single bridgewire Apollo standard initiator (SBASI) was proven by test firing forty-five (45) SBASI's with worst case voltage and temperature conditions. The EDIM was successfully qualified for Scout flight application with no failures during testing of the qualification unit. Included is a method of implementing the EDIM into Scout vehicle hardware and the ground support equipment necessary to check out the system.

Ward, R. D.↗

Uncertainty of in-flight thrust determination

Methods for estimating the measurement error or uncertainty of in-flight thrust determination in aircraft employing conventional turbofan/turbojet engines are reviewed. While the term 'in-flight thrust determination' is used synonymously with 'in-flight thrust measurement', in-flight thrust is not directly measured but is determined or calculated using mathematical modeling relationships between in-flight thrust and various direct measurements of physical quantities. The in-flight thrust determination process incorporates both ground testing and flight testing. The present text is divided into the following categories: measurement uncertainty methodoogy and in-flight thrust measurent processes.

Abernethy, Robert B.↗

Preliminary flight test results of a fly-by-throttle emergency flight control system on an F-15 airplane

A multi-engine aircraft, with some or all of the flight control system inoperative, may use engine thrust for control. NASA Dryden has conducted a study of the capability and techniques for this emergency flight control method for the F-15 airplane. With an augmented control system, engine thrust, along with appropriate feedback parameters, is used to control flightpath and bank angle. Extensive simulation studies have been followed by flight tests. This paper discusses the principles of throttles-only control, the F-15 airplane, the augmented system, and the flight results including landing approaches with throttles-only control to within 10 ft of the ground.

Burcham, Frank W., Jr.↗

Autonomous Satellite Command and Control through the World Wide Web: Phase 3

NASA's New Millenium Program (NMP) has identified a variety of revolutionary technologies that will support orders of magnitude improvements in the capabilities of spacecraft missions. This program's Autonomy team has focused on science and engineering automation technologies. In doing so, it has established a clear development roadmap specifying the experiments and demonstrations required to mature these technologies. The primary developmental thrusts of this roadmap are in the areas of remote agents, PI/operator interface, planning/scheduling fault management, and smart execution architectures. Phases 1 and 2 of the ASSET Project (previously known as the WebSat project) have focused on establishing World Wide Web-based commanding and telemetry services as an advanced means of interfacing a spacecraft system with the PI and operators. Current automated capabilities include Web-based command submission, limited contact scheduling, command list generation and transfer to the ground station, spacecraft support for demonstrations experiments, data transfer from the ground station back to the ASSET system, data archiving, and Web-based telemetry distribution. Phase 2 was finished in December 1996. During January-December 1997 work was commenced on Phase 3 of the ASSET Project. Phase 3 is the subject of this report. This phase permitted SSDL and its project partners to expand the ASSET system in a variety of ways. These added capabilities included the advancement of ground station capabilities, the adaptation of spacecraft on-board software, and the expansion of capabilities of the ASSET management algorithms. Specific goals of Phase 3 were: (1) Extend Web-based goal-level commanding for both the payload PI and the spacecraft engineer; (2) Support prioritized handling of multiple PIs as well as associated payload experimenters; (3) Expand the number and types of experiments supported by the ASSET system and its associated spacecraft; (4) Implement more advanced resource management, modeling and fault management capabilities that integrate the space and ground segments of the space system hardware; (5) Implement a beacon monitoring test; (6) Implement an experimental blackboard controller for space system management; (7) Further define typical ground station developments required for Internet-based remote control and for full system automation of the PI-to-spacecraft link. Each of those goals is examined in the next section. Significant sections of this report were also published as a conference paper.

Cantwell, Brian↗

Design Considerations of ISTAR Hydrocarbon Fueled Combustor Operating in Air Augmented Rocket, Ramjet and Scramjet Modes

The development and ground test of a rocket-based combined cycle (RBCC) propulsion system is being conducted as part of the NASA Marshall Space Flight Center (MSFC) Integrated System Test of an Airbreathing Rocket (ISTAR) program. The eventual flight vehicle (X-43B) is designed to support an air-launched self-powered Mach 0.7 to 7.0 demonstration of an RBCC engine through all of its airbreathing propulsion modes - air augmented rocket (AAR), ramjet (RJ), and scramjet (SJ). Through the use of analytical tools, numerical simulations, and experimental tests the ISTAR program is developing and validating a hydrocarbon-fueled RBCC combustor design methodology. This methodology will then be used to design an integrated RBCC propulsion system that produces robust ignition and combustion stability characteristics while maximizing combustion efficiency and minimizing drag losses. First order analytical and numerical methods used to design hydrocarbon-fueled combustors are discussed with emphasis on the methods and determination of requirements necessary to establish engine operability and performance characteristics.

Andreadis, Dean↗

Design Considerations of Istar Hydrocarbon Fueled Combustor Operating in Air Augmented Rocket, Ramjet and Scramjet Modes

The development and ground test of a rocket-based combined cycle (RBCC) propulsion system is being conducted as part of the NASA Marshall Space Flight Center (MSFC) Integrated System Test of an Airbreathing Rocket (ISTAR) program. The eventual flight vehicle (X-43B) is designed to support an air-launched self-powered Mach 0.7 to 7.0 demonstration of an RBCC engine through all of its airbreathing propulsion modes - air augmented rocket (AAR), ramjet (RJ), and scramjet (SJ). Through the use of analytical tools, numerical simulations, and experimental tests the ISTAR program is developing and validating a hydrocarbon-fueled RBCC combustor design methodology. This methodology will then be used to design an integrated RBCC propulsion system thai: produces robust ignition and combustion stability characteristics while maximizing combustion efficiency and minimizing drag losses. First order analytical and numerical methods used to design hydrocarbon-fueled combustors are discussed with emphasis on the methods and determination of requirements necessary to establish engine operability and performance characteristics.

Andreadis, Dean↗

[The Engineering and Technical Services Directorate at the Glenn Research Center]

My name is James Moon and I am a senior at Tennessee State University where my major is Aeronautical and Industrial Technology with a concentration in industrial electronics. I am currently serving my internship in the Engineering and Technical Services Directorate at the Glenn Research Center (GRC). The Engineering and Technical Service Directorate provides the services and infrastructure for the Glenn Research Center to take research concepts to reality. They provide a full range of integrated services including engineering, advanced prototyping and testing, facility management, and information technology for NASA, industry, and academia. Engineering and Technical Services contains the core knowledge in Information Technology (IT). This includes data systems and analysis, inter and intranet based systems design and data security. Including the design and development of embedded real-time s o h a r e applications for flight and supporting ground systems, Engineering and Technical Services provide a wide range of IT services and products specific to the Glenn Research Center research and engineering community. In the 7000 Directorate I work directly in the 7611 organization. This organization is known as the Aviation Environments Technical Branch. My mentor is Vincent Satterwhite who is also the Branch Chief of the Aviation Environments Technical Branch. In this branch, I serve as the Assistant program manager of the Engineering Technology Program. The Engineering Technology Program (ETP) is one of three components of the High School L.E.R.C.I.P. This is an Agency-sponsored, eight-week research-based apprenticeship program designed to attract traditionally underrepresented high school students that demonstrate an aptitude for and interest in mathematics, science, engineering, and technology.

Moon, James↗