Design, manufacture, development, test, and evaluation of boron/aluminum structural components for space shuttle. Volume 2: Materials and processing
Explore the source record for details and available documents.
SEARCH · Search NASA
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.
Explore the source record for details and available documents.
A plan for the production of two PEP flight systems is defined. The task's milestones are described. Provisions for the development and assembly of new ground support equipment required for both testing and launch operations are included.
The thermal protection systems for the shuttle/Centaur would have had to provide fail-safe thermal protection during prelaunch, launch ascent, and on-orbit operations as well as during potential abort. The thermal protection systems selected used a helium-purged polyimide foam beneath three rediation shields for the liquid-hydrogen tank and radiation shields only for the liquid-oxygen tank (three shields on the tank sidewall and four on the aft bulkhead). A double-walled vacuum bulkhead separated the two tanks. The liquid-hydrogen tank had one 0.75-in-thick layer of foam on the forward bulkhead and two layers on the larger area sidewall. Full scale tests of the flight vehicle in a simulated shuttle cargo bay that was purged with gaseous nitrogen gave total prelaunch heating rates of 88,500 Btu/hr and 44,000 Btu/hr for the liquid-hydrogen and -oxygen tanks, respectively. Calorimeter tests on a representative sample of the liquid-hydrogen tank sidewall thermal protection system indicated that the measured unit heating rate would rapidly decrease from the prelaunch rate of approx 100 Btu/hr/sq ft to a desired rate of less than 1.3 Btu/hr/sq ft once on orbit.
The Boeing Company demonstrated the application of stitched/resin infused (S/RFI) composite materials on commercial transport aircraft primary wing structures under the Advanced Subsonic technology (AST) Composite Wing contract. This report describes a weight trade study utilizing a wing torque box design applicable to a 220-passenger commercial aircraft and was used to verify the weight savings a S/RFI structure would offer compared to an identical aluminum wing box design. This trade study was performed in the AST Composite Wing program, and the overall weight savings are reported. Previous program work involved the design of a S/RFI-base-line wing box structural test component and its associated testing hardware. This detail structural design effort which is known as the "semi-span" in this report, was completed under a previous NASA contract. The full-scale wing design was based on a configuration for a MD-90-40X airplane, and the objective of this structural test component was to demonstrate the maturity of the S/RFI technology through the evaluation of a full-scale wing box/fuselage section structural test. However, scope reductions of the AST Composite Wing Program pre-vented the fabrication and evaluation of this wing box structure. Results obtained from the weight trade study, the full-scale test component design effort, fabrication, design development testing, and full-scale testing of the semi-span wing box are reported.
Explore the source record for details and available documents.
Design and development of prototype Digital Test Set /DTS/ for onboard checkout system design
This report presents the results of the test matrix development for design verification at the component level for the National Launch System (NLS) space transportation main engine (STME) thrust chamber assembly (TCA) components including the following: injector, combustion chamber, and nozzle. A systematic approach was used in the development of the minimum recommended TCA matrix resulting in a minimum number of hardware units and a minimum number of hot fire tests.
The CEV TPS Advanced Development Project (ADP) is a NASA in-house activity for providing two heatshield preliminary designs (a Lunar direct return as well as a LEO only return) for the CEV, including the TPS, the carrier structure, the interfaces and the attachments. The project s primary objective is the development of a single heatshield preliminary design that meets both Lunar direct return and LEO return requirements. The effort to develop the Lunar direct return capable heatshield is considered a high risk item for the NASA CEV development effort due to the low TRL (approx. 4) of the candidate TPS materials. By initiating the TPS ADP early in the development cycle, the intent is to use materials analysis and testing in combination with manufacturing demonstrations to reduce the programmatic risk of using advanced TPS technologies in the critical path for CEV. Due to the technical and schedule risks associated a Lunar return heatshield, the ADP will pursue a parallel path design approach, whereby a back-up TPS/heatshield design that only meets LEO return requirements is also developed. The TPS materials and carrier structure design concept selections will be based on testing, analysis, design and evaluation of scalability and manufacturing performed under the ADP. At the TPS PDR, the preferred programmatic strategy is to transfer the continued (detailed) design, development, testing and evaluation (DDT&E) of both the Lunar direct and LEO return designs to a government/prime contractor coordinated sub-system design team. The CEV prime contractor would have responsibility for the continued heatshield sub-system development. Continued government participation would include analysis, testing and evaluation as well as decision authority at TPS Final System Decision (FSD) (choosing between the primary and back-up heatshields) occurring between TPS PDR and TPS Critical Design Review (CDR). After TPS FSD the prime CEV contractor will complete the detailed design, certification testing, procurement, and integration of the CEV TPS.
The Nuclear Thermal Rocket (NTR) derives its energy from fission of uranium-235 atoms contained within fuel elements that comprise the engine's reactor core. It generates high thrust and has a specific impulse potential of approximately 900 specific impulse - a 100 percent increase over today's best chemical rockets. The Nuclear Thermal Propulsion (NTP) project, funded by NASA's Advanced Exploration Systems (AES) program, includes five key task activities: (1) Recapture, demonstration, and validation of heritage graphite composite (GC) fuel (selected as the Lead Fuel option); (2) Engine Conceptual Design; (3) Operating Requirements Definition; (4) Identification of Affordable Options for Ground Testing; and (5) Formulation of an Affordable Development Strategy. During fiscal year (FY) 2014, a preliminary Design Development Test and Evaluation (DDT&E) plan and schedule for NTP development was outlined by the NASA Glenn Research Center (GRC), Department of Energy (DOE) and industry that involved significant system-level demonstration projects that included Ground Technology Demonstration (GTD) tests at the Nevada National Security Site (NNSS), followed by a Flight Technology Demonstration (FTD) mission. To reduce cost for the GTD tests and FTD mission, small NTR engines, in either the 7.5 or 16.5 kilopound-force thrust class, were considered. Both engine options used GC fuel and a common fuel element (FE) design. The small approximately 7.5 kilopound-force criticality-limited engine produces approximately157 thermal megawatts and its core is configured with parallel rows of hexagonal-shaped FEs and tie tubes (TTs) with a FE to TT ratio of approximately 1:1. The larger approximately 16.5 kilopound-force Small Nuclear Rocket Engine (SNRE), developed by Los Alamos National Laboratory (LANL) at the end of the Rover program, produces approximately 367 thermal megawatts and has a FE to TT ratio of approximately 2:1. Although both engines use a common 35-inch (approximately 89-centimeters) -long FE, the SNRE's larger diameter core contains approximately 300 more FEs needed to produce an additional 210 thermal megawatts of power. To reduce the cost of the FTD mission, a simple one-burn lunar flyby mission was considered to reduce the liquid hydrogen (LH2) propellant loading, the stage size and complexity. Use of existing and flight proven liquid rocket and stage hardware (e.g., from the RL10B-2 engine and Delta Cryogenic Second Stage) was also maximized to further aid affordability. This paper examines the pros and cons of using these two small engine options, including their potential to support future human exploration missions to the Moon, near Earth asteroids (NEA), and Mars, and recommends a preferred size. It also provides a preliminary assessment of the key activities, development options, and schedule required to affordably build, ground test and fly a small NTR engine and stage within a 10-year timeframe.
John C. Stennis Space Center (SSC) is the premier test facility for liquid rocket engine development and certification for the National Aeronautics and Space Administration (NASA). Therefore, it is no surprise that the SSC will play the most prominent role in the engine development testing and certification for the J-2X engine. The Pratt & Whitney Rocketdyne J-2X engine has been selected by the Constellation Program to power the Ares I Upper Stage Element and the Ares V Earth Departure Stage in NASA s strategy of risk mitigation for hardware development by building on the Apollo program and other lessons learned to deliver a human-rated engine that is on an aggressive development schedule, with first demonstration flight in 2010 and human test flights in 2012. Accordingly, J-2X engine design, development, test, and evaluation is to build upon heritage hardware and apply valuable experience gained from past development and testing efforts. In order to leverage SSC s successful and innovative expertise in the plume diagnostics for the space shuttle main engine (SSME) health monitoring,1-10 this paper will present a blueprint for plume diagnostics for various proposed ground testing activities for J-2X at SSC. Complete description of the SSC s test facilities, supporting infrastructure, and test facilities is available in Ref. 11. The A-1 Test Stand is currently being prepared for testing the J-2X engine at sea level conditions. The A-2 Test Stand is currently being used for testing the SSME and may also be used for testing the J-2X engine at sea level conditions in the future. Very recently, ground-breaking ceremony for the new A-3 rocket engine test stand took place at SSC on August 23, 2007. A-3 is the first large - scale test stand to be built at the SSC since the A and B stands were constructed in the 1960s. The A-3 Test Stand will be used for testing J-2X engines under vacuum conditions simulating high altitude operation at approximately 30,480 m (100,000 ft). To achieve the simulated altitude environment, chemical steam generators using isopropyl alcohol, LOX, and RELEASED - Printed documents may be obsolete; validate prior to use. water would run for the duration of the test and would generate approximately 2096 Kg/s of steam to reduce pressure in the test cell and downstream of the engine. The testing at the A-3 Test Stand is projected to begin in late 2010, meanwhile the J-2X component testing on A-1 is scheduled to begin later this year.
Lifting body stability augmentation systems design, development, ground tests and flight data including frequency response, limit cycle and structural resonance
The Advanced Supersonic Parachute Inflation Research Experiments (ASPIRE) project was launched in 2016 to develop a capability for testing supersonic parachutes at Mars-relevant conditions. Three parachute tests successfully tested two candidate parachute designs and qualified a parachute for NASA’s Mars 2020 mission (that successfully delivered Perseverance rover to the surface of Mars in Feb 2021). To achieve Mars-relevant densities, these parachutes were deployed at targeted conditions at high altitudes over Earth, launched via sounding rockets. ASPIRE Flight Tests provided valuable data on parachute inflation, forces, and aerodynamic behavior. Design of the flight tests depended on flight mechanics simulations which in turn required aerodynamic models for the payload, and the parachute. Computational Fluid Dynamics (CFD) was used to generate these models pre-flight and they are compared against the flight data after the tests. This talk will go over some aspects of the test design, development of pre-flight models, and comparison with flight test data.
In FY11, NASA formulated a plan for Nuclear Thermal Propulsion (NTP) development that included Foundational Technology Development followed by system-level Technology Demonstrations. The ongoing NTP project, funded by NASA's Advanced Exploration Systems (AES) program, is focused on Foundational Technology Development and includes 5 key task activities: (1) Fuel element fabrication and non-nuclear validation testing of heritage fuel options; (2) Engine conceptual design; (3) Mission analysis and engine requirements definition; (4) Identification of affordable options for ground testing; and (5) Formulation of an affordable and sustainable NTP development program. Performance parameters for Point of Departure designs for a small criticality-limited and full size 25 klb (sub f) (kip, or 1000 pound-force)-class engine were developed during FYs 13-14 using heritage fuel element designs for both Rover NERVA (Nuclear Engine for Rocket Vehicle Applications) Graphite Composite (GC) and Ceramic Metal (Cermet) fuel forms. To focus the fuel development effort and maximize use of its resources, the AES program decided, in FY14, that a leader-follower down-selection between GC and cermet fuel was required. An Independent Review Panel (IRP) was convened by NASA and tasked with reviewing the available fuel data and making a recommendation to NASA. In February 2015, the IRP recommended and the AES program endorsed GC as the leader fuel In FY14, a preliminary development schedule DDTE (Design Development Test and Evaluation) plan was produced by GRC (Glenn Research Center), DOE (Department of Energy) and industry for the AES program. Assumptions, considerations and key task activities are presented here. At the direction of NASA HQ (32515), NASA and DOE are to work together to formulate a detailed development plan and schedule allowing the affordable development of a small (7.5-16.5 klbf) GC engine for possible flight technology demonstration (FTD) mission within a 10-year timeframe.
External configuration, environmental, and internal design requirements for the 300 foot diameter MOD-2 rotor are discussed, with emphasis on design details, significance of fatigue strength, design development test results, and conclusions of the preliminary design efforts.
In January 2006, NASA streamlined its U.S. Vision for Space Exploration hardware development approach for replacing the Space Shuttle after it is retired in 2010. The revised CLV upper stage will use the J-2X engine, a derivative of NASA s Apollo Program Saturn V s S-II and S-IVB main propulsion, which will also serve as the Earth Departure Stage (EDS) engine. This paper gives details of how the J- 2X engine effort mitigates risk by building on the Apollo Program and other lessons learned to deliver a human-rated engine that is on an aggressive development schedule, with first demonstration flight in 2010 and human test flights in 2012. It is well documented that propulsion is historically a high-risk area. NASA s risk reduction strategy for the J-2X engine design, development, test, and evaluation is to build upon heritage hardware and apply valuable experience gained from past development efforts. In addition, NASA and its industry partner, Rocketdyne, which originally built the J-2, have tapped into their extensive databases and are applying lessons conveyed firsthand by Apollo-era veterans of America s first round of Moon missions in the 1960s and 1970s. NASA s development approach for the J-2X engine includes early requirements definition and management; designing-in lessons learned from the 5-2 heritage programs; initiating long-lead procurement items before Preliminary Desi& Review; incorporating design features for anticipated EDS requirements; identifying facilities for sea-level and altitude testing; and starting ground support equipment and logistics planning at an early stage. Other risk reduction strategies include utilizing a proven gas generator cycle with recent development experience; utilizing existing turbomachinery ; applying current and recent main combustion chamber (Integrated Powerhead Demonstrator) and channel wall nozzle (COBRA) advances; and performing rigorous development, qualification, and certification testing of the engine system, with a philosophy of "test what you fly, and fly what you test". These and other active risk management strategies are in place to deliver the J-2X engine for LEO and lunar return missions as outlined in the U.S. Vision for Space Exploration.
On October 24th, 1998, the Deep Space One (DS-1) spacecraft launched aboard a Delta II rocket as the first step towards the bold task of testing and validating 12 new technologies for future missions. This launch also represented yet another thrilling event; namely, the successful test and validation of a 13th heretofore undisclosed technology: model-based code-generation of the spacecraft's system-level fault-protection (FP) software from behavioral state diagrams and structural models.In this paper, we describe the process we used to leverage model-based code generation from state diagrams and structural specifications to better respond to the evolving requirements and scope of DS- I's system-level fault-protection design, development, test and operation. The evolution of the high-level design and the low-level changes in the flight software architecture and interfaces contributed to multiplying the number and frequency of fault-protection software releases thereby creating a multitude of software integration issues. To address the resulting software integration issues, we broadened the scope of code -eneration to other forms of model- based analysis techniques more traditionally associated with first-principle's reasoning about physical models. Additionally, we describe our in-flight launch and initial acquisition experience.
The purpose of CASTOR (Cathode/Anode Satellite Thruster for Orbital Repositioning) satellite is to demonstrate in Low Earth Orbit (LEO) a nanosatellite that uses a Divergent Cusped Field Thruster (DCFT) to perform orbital maneuvers representative of an orbital transfer vehicle. Powered by semi-deployable solar arrays generating 165W of power, CASTOR will achieve nearly 1 km/s of velocity increment over one year. As a technology demonstration mission, success of CASTOR in LEO will pave the way for a low cost, high delta-V orbital transfer capability for small military and civilian payloads in support of Air Force and NASA missions. The educational objective is to engage graduate and undergraduate students in critical roles in the design, development, test, carrier integration and on-orbit operations of CASTOR as a supplement to their curricular activities. This program is laying the foundation for a long-term satellite construction program at MIT. The satellite is being designed as a part of AFRL's University Nanosatellite Program, which provides the funding and a framework in which student satellite teams compete for a launch to orbit. To this end, the satellite must fit within an envelope of 50cmx50cmx60cm, have a mass of less than 50kg, and meet stringent structural and other requirements. In this framework, the CASTOR team successfully completed PDR in August 2009 and CDR in April 2010 and will compete at FCR (Flight Competition Review) in January 2011. The complexity of the project requires implementation of many systems engineering techniques which allow for development of CASTOR from conception through FCR and encompass the full design, fabrication, and testing process.
Over the past few years interest in the development and use of small satellites has rapidly gained momentum with universities, commercial, and government organizations. In a few years we may see networked clusters of dozens or even hundreds of small, cheap, easily replaceable satellites working together in place of the large, expensive and difficult-to-replace satellites now in orbit. Standards based satellite buses and deployment mechanisms, such as the CubeSat and Poly Pico-satellite Orbital Deployer (P-POD), have stimulated growth in this area. The use of small satellites is also proving to be a cost effective capability in many areas traditionally dominated by large satellites, though many challenges remain. Currently many of these small satellites undergo very little testing prior to flight. As these small satellites move from technology demonstration and student projects toward more complex operational assets, it is expected that the standards for verification and validation will increase.