Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “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 937 records · Page 52
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

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.↗
NASA NTRS1999

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.↗
NASA NTRS2014

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↗
NASA NTRS2009

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.↗