Outcomes from the Brine Availability Test in Salt (BATS) Heater Test at WIPP
Explore the source record for details and available documents.
Mills, Melissa Marie [Sandia National Laboratories↗
SEARCH · Engineering Papers
Results for “test”
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.
An Investigation On The Brazilian Disc Test As An Indirect Tensile Strength Test
Explore the source record for details and available documents.
Engineering - Mechanical and civil engineering↗
Benchmark Mechanical Test Results of Westinghouse Zirconium Cladding and Irradiated Testing Readiness
Explore the source record for details and available documents.
Garrison, Ben [ORNL] (ORCID:0000000316880682)↗
Evaluation of Zero-Net-Rate Pumping Tests
Accurately estimating the distribution of aquifer properties is key to understanding contaminant movement in the subsurface. The distribution of aquifer properties is typically addressed using slug or constant-rate well tests, and the pros and cons of these tests are well known. Slug tests are appealing because they avoid removing contaminated water, but their results are affected by well skin and the small volume of displaced water limits the volume of aquifer that can be evaluated. Constant-rate well tests have the disadvantage of requiring disposal of potentially contaminated water, but they can generate properties that are more representative than slug tests, and they can be used to estimate well efficiency and storativity, which are difficult to characterize using slug tests. Periodic pumping tests are appealing because they have many of the advantages and few of the disadvantages of slug and constant-rate well tests. Periodic pumping tests involve cycling the pumping rate with a regular period and measuring the resulting response in monitoring wells. Some of these tests involve imposing a periodic rate on a constant mean rate. However, other tests involve moving water out and back into the well at rates that are balanced so the net rate after each period is zero. Some zero-net-rate (ZNR) well tests use rates that follow a sinusoidal pattern, whereas others use a square wave pattern that switches between a constant rate of pumping and a constant rate of injection to achieve a zero-net rate. ZNR well tests appear to be a useful compromise between slug and constant rate tests, but methods for conducting and analyzing the results from these tests have received limited evaluation. Periodic pumping tests are typically evaluated through recorded pressure responses to a disturbance source. Recent work has demonstrated that the strain field in the vadose zone shows a response to disturbances in the underlying aquifer. Various instrument designs are available that can record vertical and horizontal strain to very precise resolutions (10-9 ε). Measuring the strain in the vadose zone can present lower costs than measuring pressure in a monitoring well, so using strain could improve the resolution of ZNR tests, as well as make these tests potentially cheaper. A ZNR periodic pumping system was constructed and used to perform tests in the Clemson, South Carolina area. The system was designed to pump and inject with a periodic square-wave, so pumping occurs at a constant rate for half the period and is followed by injection at the same rate for half the period resulting in no net gain or loss of water from the aquifer. The system is designed to generate flow rates from 1 to 3.5 gallons per minute (gpm) with a capacity of 875-gallon per half period. Pressure and strain monitoring points are located in the vicinity of the pumping well. A series of 10 ZNR periodic pumping tests were conducted at the field site, with periods ranging from 2 to 540 minutes. Pressure data were collected and recorded in four monitoring wells in various locations around the pumping well. In addition, vertical and horizontal strain and tilt data were recorded in various locations around the pumping well. Traditional aquifer tests, including slug tests and constant-rate pumping tests were conducted at the field site to provide a baseline of aquifer parameter estimates that are compared the results of ZNR tests. Pressure data measured at monitoring wells during ZNR tests were analyzed utilizing an analytical solution (Streltsova, 1988) that assumes a confined aquifer and estimates hydraulic diffusivity and transmissivity using the time lag and amplitude of the pressure signal. The storativity can be separated out from the hydraulic diffusivity using the transmissivity estimate. The time-lag and amplitude of the pressure signals were estimated using a Fourier transform. The time-lag of the primary period of the pressure increases as a linear function of distance from the pumping well, and it increases as the square root of the period of the ZNR test over a range of periods spanning two orders of magnitudes. The first few harmonics follow similar trends, but the higher frequency harmonics diverge from this trend. Strain and tilt data from various instruments in the vadose and saturated zones are periodic during ZNR tests. The time lags of the strain components increase roughly linearly with distance from the well. Many of the time lags of the strain data from the vadose zone are similar to the time lags observed in the pressure data from a similar distance and pumping period. Theoretical experiments were performed to understand how pressure and strain responds to ZNR periodic pumping. The time-lags of the simulated pressure responses match the field data trends. The results were used to validate the Streltsova (1988) solution for periodic pumping to estimate hydraulic diffusivity. Hydraulic diffusivity was estimated to be 1.8 x 10-2 m2s-1 < Dh < 9.0 x 10-2 m2s-1 using pressure data from all the wells during ZNR tests. Transmissivity was estimated to be 0.8 x 10-4 m2s-1 < T < 4.3 x 10-4 m2s-1. Assuming Storativity = T/Dh gives 1.1 x 10-3 < S < 19 x10-3. Transmissivity is used to estimate the hydraulic conductivity, K, by dividing by the assumed aquifer thickness. Two constant-rate pumping tests were conducted and analyzed using two conceptual models: The Hantush (1961) solution was used to analyze data assuming confined conditions and the Neuman (1974) solution was used to analyze data assuming unconfined conditions. The Hantush (1961) solution estimated transmissivity to be 1.6 x 10-4 m2s-1 < T < 1.8 x 10-4 m2s-1 when using data from all the wells. Storativity was estimated to be 4.4 x 10-3 < S < 8.2 x 10-3. Assuming Dh = T/S gives 0.22 x 10-2 m2s-1 < Dh < 3.6 x 10-2 m2s-1. The Neuman (1974) solution estimated transmissivity to be 0.80 x 10-4 m2s-1 < T < 0.84 x 10-4 m2s-1. Total storativity (S + Sy) was estimated to be 22 x 10-3 < S < 110 x 10-3. Storativity excluding the Sy term was estimated to be 2.2 x 10-3 < S < 2.5 x 10-3. Assuming Dh = T/S gives 0.073 x 10-2 m2s-1 < S < 0.36 x 10-2 m2s-1. Two slug tests were performed on the pumping well, PW-2. The Bouwer and Rice (1976) solution for slug tests was used to analyze the data. This solution works for both confined and unconfined conditions, so both conceptual models were covered through the analysis. Hydraulic conductivity was estimated to be 1.95 x 10-6 ms-1 < K < 2.49 x 10-6 ms-1. Statistical comparison show generally no significant difference in the estimates of Dh, K, or S made using ZNR and conventional pumping tests.. However, the total storage estimated by the Neuman (1974) solution for unconfined settings is larger than that estimate using the Streltsove analysis applied to the ZNR tests. This is likely because the Neuman solution considers delayed yield from storage that the water table, whereas the Streltsova (1988) solution assumes confined conditions. The analysis also indicates that there is a statistically significant difference between parameters estimated with conventional slug tests and those measured with either constant-rate pumping tests or ZNR tests. Hydraulic diffusivity is estimated from the time-lag and the distance from the well. The time-lags of the strain data from the vadose zone are similar to the lags of the pressure data from a similar distance. This indicates that hydraulic diffusivities estimated from the strain data measured in the vadose zone would be similar to the estimates from the pressure data measured in the aquifer. There appear to be sign reversals in some of the strain data that were corrected to estimate the time lag. The dissolved oxygen (CO) concentration was measured during several ZNR tests to evaluate the feasibility of using the procedure to increase contaminant degradation kinetics that are related to DO. The results indicate that DO can be increased during the cycling of ZNR tests in some cases.
Smith-Jones, Austin↗
Nuclear Thermal Propulsion Ground Test History
Nuclear Thermal Propulsion (NTP) was started in ~1955 under the Atomic Energy Commission as project Rover and was assigned to Los Alamos National Laboratory. The Nevada Test Site was selected in 1956 and facility construction began in 1957. The KIWI-A was tested on July 1, 1959 for 5 minutes at 70MW. KIWI-A1 was tested on July 8, 1960 for 6 minutes at 85MW. KIWI-A3 was tested on October 10, 1960 for 5 minutes at 100MW. The National Aeronautics and Space Administration (NASA) was formed in 1958. On August 31, 1960 the AEC and NASA established the Space Nuclear Propulsion Office and named Harold Finger as Director. Immediately following the formation of SNPO, contracts were awarded for the Reactor In Flight Test (RIFT), master plan for the Nuclear Rocket Engine Development Station (NRDS), and the Nuclear Engine for Rocket Vehicle Application (NERVA). From December 7, 1961 to November 30, 1962, the KIWI-B1A, KIWI-B1B, and KIWI-B4A were tested at test cell A. The last two engines were only tested for several seconds before noticeable failure of the fuel elements. Harold Finger called a stop to any further hot fire testing until the problem was well understood. The KIWI-B4A cold flow test showed the problem to be related to fluid dynamics of hydrogen interstitial flow causing fuel element vibrations. President Kennedy visited the NTS one week after the KIWI-B4A failure and got to see the engine starting to be disassembled in the maintenance facility. The KIWI-B4D and KIWI-B4E were modified to not have the vibration problems and were tested in test cell C. The NERVA NRX program started testing in early 1964 with NRX-A1 cold flow test series (unfueled graphite core), NRX-A2 and NRX-A3 power test series up to 1122 MW for 13 minutes. In March 1966, the NRX-EST (Engine System Test) was the first breadboard using flight functional relationship and total operating time of 116 minutes. The NRX-EST demonstrated the feasibility of a hot bleed cycle. The NRX-A5 had multiple start-ups in May-June 1966 with 30.75 minutes accumulative operating time at or above 1GW. The NRX-A6 was tested in December 1969 and ran for 62 minutes at 1100 MW. Each engine had post-test examination and found various structure anomalies which were identified for correction and the fuel element corrosion rate was reduced. The Phoebus series of research reactors began testing at test cell C, in June 1965 with Phoebus 1A. Phoebus 1A operated for 10.5 minutes at 1100 MW before unexpected loss of propellant and leading to an engine breakdown. Phoebus 1B ran for 30 minutes in February of 1967. Phoebus 2A was the highest steady state reactor built at 5GW. Phoebus 2A ran for 12 minutes at 4100 MW demonstrating sufficient power is available. The Peewee test bed reactor was tested November- December 1968 in test cell C for 40 minutes at 500MW with overall performance close to pre-run predictions. The XE' engine was the only engine tested with close to a flight configuration and fired downward into a diffuser at the Engine Test Stand (ETS) in 1969. The XE' was 1100 MW and had ~28 start-ups. The nuclear furnace NF-1 was operated at 44 MW with multiple test runs at 90 minutes in the summer of 1972. The NF-1 was the last NTP reactor tested. The Rover/NERVA program was cancelled in 1973. However, before cancellation, a lot of other engineering work was conducted by Aerojet on a 75, 000 lbf prototype flight engine and by Los Alamos on a ~16,000 lbf "Small Engine" nuclear rocket design. The ground test history of NTP at the NRDS also offers many lessons learned on how best to setup, operate, emergency shutdown, and post-test examine NTP engines. The reactor and engine maintenance and disassembly facilities were used for assembly and inspection of radioactive engines after testing. Most reactor/ engines were run at test cell A or test cell C with open air exhaust. The Rover/NERVA program became aware of a new environmental regulation that would restrict the amount of radioactive particulates allowed to be release in open air and successfully demonstrated a scrubber concept with the NF-1. The ETS stand was the only one with a high altitude test chamber used for XE'. The ETS and other test cells showed the effects the engine's radiation had on the facility materials and instrumentation as well as side effects the ground test facility has back on the engine operation. The breakdown of Phoebus 1A at test cell C showed how the site was cleaned up and back to operation for five more engines before the program was cancelled.
Gerrish, Harold P.↗
Carbon Fiber Reinforced/Silicon Carbide Turbine Blisk Testing in the SIMPLEX Turbopump
A program designed to implement a ceramic matrix composite integrally bladed disk (blisk) into rocket engine style turbomachinery has successfully completed testing. The Marshall Space Flight Center (MSFC) program, utilizing the MSFC turbomachinery design, analysis, and testing capabilities along with materials development capabilities from both Glenn Research Center (GRC) and MSFC, has tested two carbon fiber reinforced silicon carbide blisks in the Simplex Turbopump at MSFC's Test Stand 500. One blisk contained a polar woven fiber preform, while the second blisk tested utilized a quasi-isotropic preform. Vhile earlier papers have chronicled the program's design, material testing, and torque testing efforts, this paper focuses on the testing of the blisks in the Simplex turbopump. Emphasis will be placed on the actual condition of the blisks before and after the testing test program design methodology, and conclusions that can be drawn from the test data and blisk final conditions. The program performed three separate test series. The first series was needed to validate that the Simplex turbopump was correctly re-built following a major incident to the turbopump. The turbopump had two major differences from the original design. The most obvious difference was the sleeve required throughout the bore of the main housing. The second major difference was modifications to the pump diffuser to improve performance. Several areas were burnt during the incident and were either repaired by weld repair (pump inlet housing) or simply smoothed out (turbine nozzle discharge). The test series was designed to weed out any turbopump design and manufacturing flaws or fatigue issues prior to putting the C/SiC blisks into it. The second and third series were the C/SiC blisk test series. The primary goal of these series was to expose the blisks to as much fatigue causing dynamic stress as possible to examine the material's capability. Initially, the test plan was to put equal time on the two blisks, however, as the test series progressed, the funding allowed additional testing to occur. The additional test time was placed on the polar weave blisk. The total test time accrued on the polar blisk was 2550 seconds with 860 seconds near the turbopump design speed of 25,000 rpm. This testing included 6 tests / 775 seconds pumping liquid nitrogen and 7 tests / 1775 seconds pumping liquid oxygen. The drive gas for all of the tests was gaseous nitrogen due to the lack of hot gas source for the Simplex turbopump. The quasi-isotropic blisk was tested for XX total tests and XXXX seconds with X tests/XXXX seconds pumping liquid nitrogen and X tests/XXXX seconds pumping liquid \oxygen.During the test series, the blisks were inspected following each test. Inspections initially were viewed from the downstream side of the blisks only. Midway through the testing, a method of borescoping the leading edges of the blades was devised, and subsequently, both sides of the blades were inspected following each test. The leading and trailing edges of the polar blisk held up better than the quasi-isotropic blisk. This was a known possibility due to the varying fiber direction in the blades as the rectangular preform weave is cut in a circular pattern. The surprising fact about the testing was that there was no measurable performance loss due to the inaccuracies in the blade manufacturing in the C/SiC blisks, the surface roughness C/SiC of the blades, or the loss of the material in the polar blisk. A performance shift was seen in the quasi-isotropic blisk as portions of the leading and trailing edges were lost. After the testing was completed, detailed inspections of the blisks were performed. The largest surprise was the polar blisk had a obvious crack in a single blade that was located nearly midspan which was not detected in test. The crack ran completely through the blade circumferenciary and through the radial length of the blade. However, the crack does not appear to extend into the blisk hub. Although the cause of the crack is still under investigation, the material appears to be tolerant of this crack, and other hairline cracks discovered under higher magnification. This bodies well for eventual use of this material in actual flight turbopumps where monolithic fracture toughness issues limit its use.
Genge, Gary G.↗
Anomalous Thrust Production from an RF Test Device Measured on a Low-Thrust Torsion Pendulum
This paper describes the eight-day August 2013 test campaign designed to investigate and demonstrate viability of using classical magnetoplasmadynamics to obtain a propulsive momentum transfer via the quantum vacuum virtual plasma. This paper will not address the physics of the quantum vacuum plasma thruster, but instead will describe the test integration, test operations, and the results obtained from the test campaign. Approximately 30-50 micro-Newtons of thrust were recorded from an electric propulsion test article consisting primarily of a radio frequency (RF) resonant cavity excited at approximately 935 megahertz. Testing was performed on a low-thrust torsion pendulum that is capable of detecting force at a single-digit micronewton level, within a stainless steel vacuum chamber with the door closed but at ambient atmospheric pressure. Several different test configurations were used, including two different test articles as well as a reversal of the test article orientation. In addition, the test article was replaced by an RF load to verify that the force was not being generated by effects not associated with the test article. The two test articles were designed by Cannae LLC of Doylestown, Pennsylvania. The torsion pendulum was designed, built, and operated by Eagleworks Laboratories at the NASA Johnson Space Center of Houston, Texas. Approximately six days of test integration were required, followed by two days of test operations, during which, technical issues were discovered and resolved. Integration of the two test articles and their supporting equipment was performed in an iterative fashion between the test bench and the vacuum chamber. In other words, the test article was tested on the bench, then moved to the chamber, then moved back as needed to resolve issues. Manual frequency control was required throughout the test. Thrust was observed on both test articles, even though one of the test articles was designed with the expectation that it would not produce thrust. Specifically, one test article contained internal physical modifications that were designed to produce thrust, while the other did not (with the latter being referred to as the "null" test article). Test data gathered includes torsion pendulum displacement measurements which are used to calculate generated force, still imagery in the visible spectrum to document the physical configuration, still imagery in the infrared spectrum to characterize the thermal environment, and video imagery. Post-test data includes static and animated graphics produced during RF resonant cavity characterization using the COMSOL Multiphysics® software application. Excerpts from all of the above are included and discussed in this paper. Lessons learned from test integration and operations include identification of the need to replace manual control of the resonant cavity target frequency with an automated frequency control capability. Future test plans include the development of an automatic frequency control circuit. Test results indicate that the RF resonant cavity thruster design, which is unique as an electric propulsion device, is producing a force that is not attributable to any classical electromagnetic phenomenon and therefore is potentially demonstrating an interaction with the quantum vacuum virtual plasma. Future test plans include independent verification and validation at other test facilities.
Brady, David↗
An Analysis of Rocket Propulsion Testing Costs
The primary mission at NASA Stennis Space Center (SSC) is rocket propulsion testing. Such testing is generally performed within two arenas: (1) Production testing for certification and acceptance, and (2) Developmental testing for prototype or experimental purposes. The customer base consists of NASA programs, DOD programs, and commercial programs. Resources in place to perform on-site testing include both civil servants and contractor personnel, hardware and software including data acquisition and control, and 6 test stands with a total of 14 test positions/cells. For several business reasons there is the need to augment understanding of the test costs for all the various types of test campaigns. Historical propulsion test data was evaluated and analyzed in many different ways with the intent to find any correlation or statistics that could help produce more reliable and accurate cost estimates and projections. The analytical efforts included timeline trends, statistical curve fitting, average cost per test, cost per test second, test cost timeline, and test cost envelopes. Further, the analytical effort includes examining the test cost from the perspective of thrust level and test article characteristics. Some of the analytical approaches did not produce evidence strong enough for further analysis. Some other analytical approaches yield promising results and are candidates for further development and focused study. Information was organized for into its elements: a Project Profile, Test Cost Timeline, and Cost Envelope. The Project Profile is a snap shot of the project life cycle on a timeline fashion, which includes various statistical analyses. The Test Cost Timeline shows the cumulative average test cost, for each project, at each month where there was test activity. The Test Cost Envelope shows a range of cost for a given number of test(s). The supporting information upon which this study was performed came from diverse sources and thus it was necessary to build several intermediate databases in order to understand, validate, and manipulate data. These intermediate databases (validated historical account of schedule, test activity, and cost) by themselves are of great value and utility. For example, for the Project Profile, we were able to merged schedule, cost, and test activity. This kind of historical account conveys important information about sequence of events, lead time, and opportunities for improvement in future propulsion test projects. The Product Requirement Document (PRD) file is a collection of data extracted from each project PRD (technical characteristics, test requirements, and projection of cost, schedule, and test activity). This information could help expedite the development of future PRD (or equivalent document) on similar projects, and could also, when compared to the actual results, help improve projections around cost and schedule. Also, this file can be sorted by the parameter of interest to perform a visual review of potential common themes or trends. The process of searching, collecting, and validating propulsion test data encountered a lot of difficulties which then led to a set of recommendations for improvement in order to facilitate future data gathering and analysis.
Ramirez-Pagan, Carmen P.↗
An automatic input/output test experience of FPGA-based logic controller with I/O stimulator - 282
This paper describes an automatic testing approach instead of a traditional manual test for an FPGA-based Logic Controller (FLC). It mainly describes an automatic testing of FLC using an I/O stimulator with the initiated manual action. The FLC was developed by Doosan Heavy Industry and KAERI in S. Korea. We also developed a test-bed like I/O stimulator for a burning test based on the operational scenario. Signal sources from the I/O stimulator contain an analog input, an analog output, a digital input and a digital output, a programmable power supply, an RS232C serial interface, and a dual port Ethernet interface. LabVIEW Programming was used for the automatic testing. The FLC consists of a general processor module (FPM-01), a complex processor module (FPM-02), analog input modules (FAI-01), analog output modules (FAO-01), digital input modules (FDI-01), digital output modules (FDO-01), a data link module (FDL-01), and a network module (FNW-01). Among these, in this paper, automatic digital I/O testing and automatic analog I/O testing are described. In addition, for the accuracy of the automatic testing, two graphic recorders are used. One is the output results of general processor based testing, and the other is the output results of complex processor based testing. These are different company products. Redundancy recording was found in the test results. The test results were synchronized internally with the existing I/O stimulator and externally with two graphic recorders. Calibrations of all of the equipment were made before the system testing. Before the testing started, a test plan and the test procedure were set up in advance, and we performed test scenario-based automatic functional testing for the FLC as the qualification process. It can be several executed depending on the scenario and conditional parameters of the test. For validation of the accuracy and reliability in our automated test, manual testing was also performed. Manual tests were conducted in two ways. The first one was a manual test using Fluke 754 and Fluke 715. The other one was using embedded manual features of the I/O stimulator. By performing the automatic input and output testing using the I/O stimulator, the time and expense of FLC testing can be reduced significantly compared with a conventional manual test. We rechecked the automatic test results using Fluke754 manually. (authors)
46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗
Creep Testing of Vectran Yarn
NASA and industry are developing inflatable space structures to provide deployable habitable volumes for future exploration missions in space and on the surface of the Moon and Mars. These structures must withstand the constant pressure loading of multi-year missions. These missions therefore require excellent creep resistance in the constituent cordage and webbings that provide the primary structure of the vessel, which is typically constructed using high-strength synthetic materials such as Vectran. Real-time and accelerated creep testing of Vectran webbings has been performed at NASA Langley Research Center (LaRC), however, acceptable correlation between the results of the two approaches has not yet been achieved. Given the additional complexity of the webbing architecture, creep testing at the yarn level is being studied to reduce the number of interacting properties and focus on the core creep behavior to see if better correlation can be achieved between real-time and accelerated tests. To achieve this objective a creep test stand that is able to support simultaneous testing of five Vectran yarns had been previously designed and built. The test stand utilizes two clamp-wrap grips to mount the yarn and has a 10:1 load ratio, via a lever-arm, henceforth, known as the lever-arm test stand. Real-time creep testing (without measuring the strain of the yarn) in this fixture produces yarn ruptures in the gauge section. However, a large scatter in the times to failure was seen in the results across multiple loading conditions. For example, a test at 70% of the ultimate tensile strength (UTS) was found to have specimens that failed within a matter of hours and others that took over 6 weeks to fail. Prior test data on Vectran webbings had indicated high variability in the material strength, leading to higher than average scatter in the creep testing of webbings, which could translate to the scatter in creep behavior at the yarn level as well. However, there was still the possibility that the lever-arm test stand was causing the high scatter in data; specifically, due to potential variability in the loading of each specimen. Therefore, an additional creep test setup was designed and built to attempt to determine if the large scatter in the results was due to inherent material properties, the lever-arm test stand, or both. The newly designed creep test stand, henceforth known as the conventional test stand, utilized the more typical method for creep testing which involved hanging a weight from the yarn with no additional load amplification. The conventional test stand was designed and fabricated in-house at LaRC. High speed cameras were used to validate that the specimens in the conventional test stand failed in the gauge section. Once it was determined that the conventional test stand would provide valid failures in the gauge section, creep tests on the Vectran yarns were run to compare to the lever-arm test stand results. Preliminary results for a 70% UTS creep test have some specimens failing within a number of hours and some failing in excess of 6 weeks. These results are similar to those seen on the lever-arm test stand, pointing towards a large variability inherent in the material. The poster/presentation will focus on the design, fabrication, and validation of the conventional test stand as well as present preliminary results comparing the creep data from the conventional and lever-arm test stands
creep testing↗
Introduction to Flight Test Engineering [Introduction Aux Techniques Des Essais En Vol]
Flight test is at the core of what organizations must do in order to validate the operation and systems on an aircraft. While the AGARDograph series 300 and 160 series deal with aspects of this testing, this volume pulls it all together as an introduction to the process required to do effective flight test engineering. This volume was originally published in 1995. Its utility has been proven in that many flight test organizations and universities have requested copies for their engineers and students. It was felt that re-issuing it in a new format designed for electronic publication would be valuable to the community. This second printing changes none of the text, but rather reformats it. All the original references to AGARD (instead of RTO) are left in place so that none of the flavor of the original publication is lost. This is the Introductory Volume to the Flight Test Techniques Series. It is a general introduction to the various activities and aspects of Flight Test Engineering that must be considered when planning, conducting, and reporting a flight test program. Its main intent is to provide a broad overview to the novice engineer or to other people who have a need to interface with specialists within the flight test community. The first two Sections provide some insight into the question of why flight test and give a short history of flight test engineering. Sections 3 through 10 deal with the preparation for flight testing. They provide guidance on the preliminary factors that must be considered; the composition of the test team; the logistic support requirements; the instrumentation and data processing requirements; the flight test plan; the associated preliminary ground tests; and last, but by no means least, discuss safety aspects. Sections 11 through 27 describe the various types of flight tests that are usually conducted during the development and certification of a new or modified aircraft type. Each Section offers a brief introduction to the topic under consideration, and the nature and the objectives of the tests to be conducted. It lists the test instrumentation (and, where appropriate, other test equipment and facilities) required, describes the test maneuvers to be executed, and indicates the way in which the test data is selected, analyzed, and presented. The various activities that should take place between test flights are presented next. Items that are covered are: who to debrief; what type of reports to send where: types of data analysis required for next flight; review of test data to make a comparison to predicted data and some courses of action if there is not good agreement; and comments on selecting the next test flight. The activities that must take place upon completion of the test program are presented. The types of reports and briefings that should take place and a discussion of some of the uses of the flight test data are covered. A brief forecast is presented of where present trends may be leading.
Test facilities↗
Orion Launch Abort System Performance on Exploration Flight Test 1
This paper will present an overview of the flight test objectives and performance of the Orion Launch Abort System during Exploration Flight Test-1. Exploration Flight Test-1, the first flight test of the Orion spacecraft, was managed and led by the Orion prime contractor, Lockheed Martin, and launched atop a United Launch Alliance Delta IV Heavy rocket. This flight test was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety. This test included the first flight test of the Launch Abort System preforming Orion nominal flight mission critical objectives. NASA is currently designing and testing the Orion Multi-Purpose Crew Vehicle (MPCV). Orion will serve as NASA's new exploration vehicle to carry astronauts to deep space destinations and safely return them to earth. The Orion spacecraft is composed of four main elements: the Launch Abort System, the Crew Module, the Service Module, and the Spacecraft Adapter (Fig. 1). The Launch Abort System (LAS) provides two functions; during nominal launches, the LAS provides protection for the Crew Module from atmospheric loads and heating during first stage flight and during emergencies provides a reliable abort capability for aborts that occur within the atmosphere. The Orion Launch Abort System (LAS) consists of an Abort Motor to provide the abort separation from the Launch Vehicle, an Attitude Control Motor to provide attitude and rate control, and a Jettison Motor for crew module to LAS separation (Fig. 2). The jettison motor is used during a nominal launch to separate the LAS from the Launch Vehicle (LV) early in the flight of the second stage when it is no longer needed for aborts and at the end of an LAS abort sequence to enable deployment of the crew module's Landing Recovery System. The LAS also provides a Boost Protective Cover fairing that shields the crew module from debris and the aero-thermal environment during ascent. Although the Orion Program has tested a number of the critical systems of the Orion spacecraft on the ground, the launch environment cannot be replicated completely on Earth. A number of flight tests have been conducted and are planned to demonstrate the performance and enable certification of the Orion Spacecraft. Exploration Flight Test 1, the first flight test of the Orion spacecraft, was successfully flown on December 5, 2014 from Cape Canaveral Air Force Station's Space Launch Complex 37. Orion's first flight was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety, such as heat shield performance, separation events, avionics and software performance, attitude control and guidance, parachute deployment and recovery operations. One of the key separation events tested during this flight was the nominal jettison of the LAS. Data from this flight will be used to verify the function of the jettison motor to separate the Launch Abort System from the crew module so it can continue on with the mission. The LAS nominal jettison event on Exploration Flight Test 1 occurred at six minutes and twenty seconds after liftoff (See Fig. 3). The abort motor and attitude control motors were inert for Exploration Flight Test 1, since the mission did not require abort capabilities. A suite of developmental flight instrumentation was included on the flight test to provide data on spacecraft subsystems and separation events. This paper will focus on the flight test objectives and performance of the LAS during ascent and nominal jettison. Selected LAS subsystem flight test data will be presented and discussed in the paper. Exploration Flight Test -1 will provide critical data that will enable engineering to improve Orion's design and reduce risk for the astronauts it will protect as NASA continues to move forward on its human journey to Mars. The lessons learned from Exploration Flight Test 1 and the other Flight Test Vehicles will certainly contribute to the vehicle architecture of a human-rated space launch vehicle.
McCauley, R.↗
Gripper Test Assembly Status Report (FY2020)
Refueling systems for fast reactors are designed to handle fresh and used core assemblies (fuel, reflector, and shield core assemblies) within the reactor vessel in an opaque coolant environment without visual reference. These refueling machines are designed to work in a sodium (or other fast reactor coolant) and argon vapor space environment and are engineered with the rotatable plug system to allow for the movement of fresh and spent fuel into and out of the reactor core. The refueling machines are a critical component in any reactor and thus need to undergo extensive testing in a prototypic environment to ensure that they will meet all of the system functions and requirements. Argonne has developed an innovative compact refueling system design for the Advanced Fast Reactor-100 that is based upon some mechanisms used in previous reactor designs, such as the U.K.’s Prototype Fast Reactor (PFR) and some mechanisms that have not been used in sodium. This compact refueling machine supports the reduction in size of the AFR-100’s reactor vessel, and if fully developed, would support and inform the development of the in-vessel refueling machines for such commercial reactors as the GEH PRISM reactor plant, the ARC Clean Energy’s ARC-100 reactor, and the Natrium reactor, among others. This refueling system is a vital component of a fast reactor that supports reducing the cost of the reactor and increasing its reliability. During the development of the compact fuel handling machine conceptual design for the AFR-100, a lack of testing data for many mechanical components in sodium under typical in-reactor loads and conditions was discovered. The reduction in lifetime of the various mechanical components in the liquid sodium environment needs to be quantified versus the calculated component lifetimes under normal conditions in the testing while they are subjected to typical loading profiles experienced in the past. The Gripper Test Assembly discussed here includes a full-size gripper device with appropriate mechanical features that will be tested in sodium to provide this testing data. The Gripper Test Assembly is used to test various mechanical fuel handling components submerged in high temperature liquid sodium. These mechanisms are gears, bearings, gripper jaws and head, universal joints and shafts, ball screws, among others. These components will be tested under the typical sodium environmental conditions experienced during refueling operations with appropriate loading conditions that simulate the removal and insertion of core assemblies into a fast reactor grid plate structure. This Gripper Test Assembly is the second in a series of refueling system mechanisms developed for testing in sodium. The first test assembly is the Gear Test Assembly (GTA) which was used to test the performance of gears and bearings operating in sodium. Because of the successful testing conducted with the GTA, it was decided to continue with the development of the Gripper Test Assembly which uses the same gears and bearings tested in GTA. Using the data collected during operation of this gripper test assembly, lifetime reduction factors of the various mechanical components can be calculated for the material combinations selected. These lifetime reduction factors can be used in the design of future mechanical systems which operate in these environments to accurately predict component end of life. In addition, an understanding of the ability of these components and mechanisms to operate under-sodium with the chosen materials will be accomplished. Again, this Gripper Test Assembly is the follow-on test article to the Gear Test Assembly which was testing the ability of gears and bearings operating in a sodium environment. Once fabricated and qualified, it will be tested in the Mechanism Engineering Test Loop (METL) facility located in Building 308 at Argonne National Laboratory.
21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
A Method for Calculating the Probability of Successfully Completing a Rocket Propulsion Ground Test
Propulsion ground test facilities face the daily challenges of scheduling multiple customers into limited facility space and successfully completing their propulsion test projects. Due to budgetary and schedule constraints, NASA and industry customers are pushing to test more components, for less money, in a shorter period of time. As these new rocket engine component test programs are undertaken, the lack of technology maturity in the test articles, combined with pushing the test facilities capabilities to their limits, tends to lead to an increase in facility breakdowns and unsuccessful tests. Over the last five years Stennis Space Center's propulsion test facilities have performed hundreds of tests, collected thousands of seconds of test data, and broken numerous test facility and test article parts. While various initiatives have been implemented to provide better propulsion test techniques and improve the quality, reliability, and maintainability of goods and parts used in the propulsion test facilities, unexpected failures during testing still occur quite regularly due to the harsh environment in which the propulsion test facilities operate. Previous attempts at modeling the lifecycle of a propulsion component test project have met with little success. Each of the attempts suffered form incomplete or inconsistent data on which to base the models. By focusing on the actual test phase of the tests project rather than the formulation, design or construction phases of the test project, the quality and quantity of available data increases dramatically. A logistic regression model has been developed form the data collected over the last five years, allowing the probability of successfully completing a rocket propulsion component test to be calculated. A logistic regression model is a mathematical modeling approach that can be used to describe the relationship of several independent predictor variables X(sub 1), X(sub 2),..,X(sub k) to a binary or dichotomous dependent variable Y, where Y can only be one of two possible outcomes, in this case Success or Failure. Logistic regression has primarily been used in the fields of epidemiology and biomedical research, but lends itself to many other applications. As indicated the use of logistic regression is not new, however, modeling propulsion ground test facilities using logistic regression is both a new and unique application of the statistical technique. Results from the models provide project managers with insight and confidence into the affectivity of rocket engine component ground test projects. The initial success in modeling rocket propulsion ground test projects clears the way for more complex models to be developed in this area.
Messer, Bradley P.↗
Chapter 9 - Pre-Flight Tests
Pre-flight testing is critical to the success of any flight test program. Pre-flight tests are performed to measure and evaluate the characteristics of an aircraft in a non-flying environment and to verify that these characteristics are as desired. Since aircraft systems are becoming more and more complex, conducting proper pre-flight testing to help identify system characteristics and deficiencies prior to flight is more important now than ever before. Much flight test time has been lost fixing problems that should have been found and corrected prior to flight. Accidents have occurred because pre-flight tests and verification procedures were not conducted thoroughly enough to identify the aircraft's characteristics properly or to find system discrepancies. Proper pre-flight testing helps ensure that the aircraft is ready to fly and contributes toward an efficient, productive, and safe flight test program. The reader should be aware that this Section is dedicated to the testing that should take place prior to the first flight. There are other "pre-flight" tests that take place prior to each individual flight. These latter tests are not discussed in this Section. The following paragraphs of this Section describe significant tests that are usually accomplished prior to flying a new or highly modified aircraft. Test objectives, descriptions, products, and requirements are provided in the following subsections: 9.1 Wind tunnel tests 9.2 Simulation tests 9.3 Propulsion tests 9.4 Weight and balance tests 9.5 Ground vibration tests 9.6 Structural loads tests 9.7 Gain margin tests 9.8 Verification and calibration tests 9.9 Taxi tests The specific examples given and the test facilities mentioned in this Section will illustrate the approach taken and the techniques used by the US Air Force; however, they are typical of those used by other test organizations.
Paul W Kirsten↗
Test Analysis Guidelines
Development of analysis guidelines for Exploration Life Support (ELS) technology tests was completed. The guidelines were developed based on analysis experiences gained from supporting Environmental Control and Life Support System (ECLSS) technology development in air revitalization systems and water recovery systems. Analyses are vital during all three phases of the ELS technology test: pre-test, during test and post test. Pre-test analyses of a test system help define hardware components, predict system and component performances, required test duration, sampling frequencies of operation parameters, etc. Analyses conducted during tests could verify the consistency of all the measurements and the performance of the test system. Post test analyses are an essential part of the test task. Results of post test analyses are an important factor in judging whether the technology development is a successful one. In addition, development of a rigorous model for a test system is an important objective of any new technology development. Test data analyses, especially post test data analyses, serve to verify the model. Test analyses have supported development of many ECLSS technologies. Some test analysis tasks in ECLSS technology development are listed in the Appendix. To have effective analysis support for ECLSS technology tests, analysis guidelines would be a useful tool. These test guidelines were developed based on experiences gained through previous analysis support of various ECLSS technology tests. A comment on analysis from an experienced NASA ECLSS manager (1) follows: "Bad analysis was one that bent the test to prove that the analysis was right to begin with. Good analysis was one that directed where the testing should go and also bridged the gap between the reality of the test facility and what was expected on orbit."
Jeng, Frank F.↗
Pressure-Fed LOX/LCH4 Reaction Control System for Spacecraft: Transient Modeling and Thermal Vacuum Hotfire Test Results
An integrated cryogenic liquid oxygen, liquid methane (LOX/LCH4) reaction control system (RCS) was tested at NASA Glenn Research Center's Plum Brook Station in the Spacecraft Propulsion Research Facility (B-2) under vacuum and thermal vacuum conditions. The RCS is a subsystem of the Integrated Cryogenic Propulsion Test Article (ICPTA), a pressure-fed LOX/LCH4 propulsion system composed of a single 2,800 lbf main engine, two 28 lbf RCS engines, and two 7 lbf RCS engines. Propellants are stored in four 48 inch diameter 5083 aluminum tanks that feed both the main engine and RCS engines in parallel. Helium stored cryogenically in a composite overwrapped pressure vessel (COPV) flows through a heat exchanger on the main engine before being used to pressurize the propellant tanks to a design operating pressure of 325 psi. The ICPTA is capable of simultaneous main engine and RCS operation. The RCS engines utilize a coil-on-plug (COP) ignition system designed for operation in a vacuum environment, eliminating corona discharge issues associated with a high voltage lead. There are two RCS pods on the ICPTA, with two engines on each pod. One of these two engines is a heritage flight engine from Project Morpheus. Its sea level nozzle was removed and replaced by an 85:1 nozzle machined using Inconel 718, resulting in a maximum thrust of 28 lbf under altitude conditions. The other engine is a scaled down version of the 28 lbf engine, designed to match the core and overall mixture ratios as well as other injector characteristics. This engine can produce a maximum thrust of 7 lbf with an 85:1 nozzle that was additively manufactured using Inconel 718. Both engines are film-cooled and capable of limited duration gas-gas and gas-liquid operation, as well as steady-state liquid-liquid operation. Each pod contains one of each version, such that two engines of the same thrust level can be fired as a couple on opposite pods. The RCS feed system is composed of symmetrical 3/8 inch lines that tap off of the main propellant manifold to send LOX and LCH4 outboard to the RCS pods. A Thermodynamic Vent System (TVS) is used to condition propellants at each pod by venting through an orifice and then routing the cold expansion products back through tubing that is welded along a large portion of the main RCS feed lines. Prior to final installation on the ICPTA, the RCS engines were tested in a small vacuum chamber at the Johnson Space Center (JSC) Energy Systems Test Area (ESTA) to verify functionality of the new COP ignition system and check out operation of the vacuum nozzles. After engine-level testing, the RCS engines were installed on the vehicle and a series of integrated hot-fire tests were performed at JSC consisting of various pulsing and steady-state firings as well as integrated main engine/RCS operation. The ICPTA was then integrated into the Plum Brook B-2 facility for vacuum and thermal/vacuum testing. Testing in the B-2 facility was composed of multiple thermal and pressure environments. The first set of tests were performed under ambient temperature and altitude pressure conditions. These tests consisted of a range of minimum impulse bit (MIB) pulsing sequences with low duty cycle, analogous to a coast phase in which the RCS is primarily used for station keeping. The primary goal of this sequence is to understand how propellant conditions were effected without an active TVS. In this scenario, consistent gas-gas operation is desirable since it results in a smaller MIB and more efficient propellant consumption. Multiple skin thermocouples are mounted on the feedlines, in addition to a submerged thermocouple on each commodity, in order to gather thermal data on the system. Higher duty cycle pulsing tests were then performed, analogous to an ascent or landing mission phase. The primary goal of this sequence was to examine how well the engines self-conditioned without active TVS when starting from a quiescent state. The TVS was then activated during some tests to demonstrate the capability to quickly condition the engines for higher pulsing demand scenarios. A thermocouple at the TVS outlet allows for the calculation of energy absorbed by the vented propellant. Lastly, tests with longer pulses and multiple engines firing either in sequence or simultaneously were run in order to gather transient system response data on waterhammer. Six total high-speed pressure transducers are installed on the RCS system, one sensor at the end of each propellant manifold line on the pods, and one at the tap-off location for each commodity. This will allow for the accurate characterization of waterhammer in the system under various propellant conditions and firing sequences. Other instrumentation for this test series includes nozzle throat thermocouples, chamber pressure measurement, heat soakback measurement, and tank wall plume impingement temperature measurement. The next set of tests were performed to demonstrate simultaneous main engine and RCS operation. Data from this test will be used to examine if there is any change to nominal operation of the RCS as a result of feed system interaction or other phenomenon. Some of these tests began under high vacuum conditions (target ambient pressure less than 1x10(exp -3) torr) and others began at altitude conditions. The last set of tests were performed with the B-2 cold wall active. Under these tests, many of the same low duty cycle MIB tests were repeated in order to characterize how propellant conditions changed with the lower heat leak. In this scenario the RCS manifold experiences much less heat leak, resulting in a change to how well the engines self-condition. As a result, an increase in maximum waterhammer pressures and a change in natural frequency of the system was expected due to higher density propellants. The lower heat leak should also result in a change to the MIB pulse profile, and data will be examined to understand how MIB repeatability is affected in the different operating environments. Parallel to the test efforts, a set of transient model development efforts were made to predict RCS performance. The primary effort was aimed at producing a SINDA/FLUINT model to predict propellant conditioning up to the engine inlet as a function of different environmental and operating parameters, with the goal of predicting chamber pressure, TVS performance, and propellant consumption over time. Preliminary results for this effort will be presented in comparison with test data. Additional modeling efforts were made using SINDA/FLUINT to predict waterhammer in the system since the software is capable of handling multiphase transient fluid dynamics. These results will be compared with the high-speed pressure transducer test data for validation purposes.
Atwell, Matthew J.↗
System Testing of Ground Cooling System Components
This internship focused primarily upon software unit testing of Ground Cooling System (GCS) components, one of the three types of tests (unit, integrated, and COTS/regression) utilized in software verification. Unit tests are used to test the software of necessary components before it is implemented into the hardware. A unit test determines that the control data, usage procedures, and operating procedures of a particular component are tested to determine if the program is fit for use. Three different files are used to make and complete an efficient unit test. These files include the following: Model Test file (.mdl), Simulink SystemTest (.test), and autotest (.m). The Model Test file includes the component that is being tested with the appropriate Discrete Physical Interface (DPI) for testing. The Simulink SystemTest is a program used to test all of the requirements of the component. The autotest tests that the component passes Model Advisor and System Testing, and puts the results into proper files. Once unit testing is completed on the GCS components they can then be implemented into the GCS Schematic and the software of the GCS model as a whole can be tested using integrated testing. Unit testing is a critical part of software verification; it allows for the testing of more basic components before a model of higher fidelity is tested, making the process of testing flow in an orderly manner.
Unit Test↗