Ground testing the Apollo vehicle.
Static structure ground test for Saturn-Apollo vehicle short stack, describing air pressure simulation, data acquisition and readout systems
SEARCH · Engineering Papers
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.
Static structure ground test for Saturn-Apollo vehicle short stack, describing air pressure simulation, data acquisition and readout systems
The Ares I-X Flight Test Vehicle was launched on October 28, 2009 and was the first and only test flight of NASA s two-stage Ares I launch vehicle design. The launch was successful and the flight test met all of its primary and secondary objectives. This paper discusses the stage separation and reentry trajectory analysis that was performed in support of the Ares I-X test flight. Pre-flight analyses were conducted to assess the risk of stage recontact during separation, to evaluate the first stage flight dynamics during reentry, and to define the range safety impact ellipses of both stages. The results of these pre-flight analyses were compared with available flight data. On-board video taken during flight showed that the flight test vehicle successfully separated without any recontact. Reconstructed trajectory data also showed that first stage flight dynamics were well characterized by pre-flight Monte Carlo results. In addition, comparisons with flight data indicated that the complex interference aerodynamic models employed in the reentry simulation were effective in capturing the flight dynamics during separation. Finally, the splash-down locations of both stages were well within predicted impact ellipses.
Vibration test specifications for flight vehicle components developed from broad engineering viewpoint
Hydrogen-fueled Centaur launch vehicle test space flight - Surveyor project
Skidding causes many traffic accidents. Streets and highways with skid-resisting surfaces reduce the incidence of such accidents. In fact, resurfacing roads to improve skid resistance is now required by federal law. Skid resistance is measured by road testing with specially equipped skid trailers. A project underway at NASA-Langley may considerably reduce the cost of skid trailers, thus making them more widely available to highway departments. For testing the skid resistance of aircraft runways, Langley engineers developed a relatively inexpensive test vehicle and a "pulsed braking" technique that is now being applied experimentally to road testing. The vehicle is a standard automobile modified to incorporate instrumentation, special test tires and valves, and a trailing fifth wheel for monitoring distance and velocity. The instrumentation includes a low-cost meter, a set of accelerometers that sense motion changes, and a chart recorder.
Atmospheric acoustic factors in saturn launch vehicle testing - reduction by weather forecasting
Variable frequency vibration tests on S-2A STRUCTURAL test vehicle - Surveyor project
Fabrication and testing of cesium loaded thermionic converter test vehicle
Limitations in the acquisition of nonlinear aerodynamic coefficients from free-oscillation data by means of the Chapman-Kirk technique, SAM-D control test vehicle trajectory plannning and flight test analysis, and determination of aerodynamic drag from radar data are among the topics covered in papers concerned with atmospheric flight mechanics. Other areas covered include fixed and rotary-wing aircraft, ordnance and reentry vehicles, and analysis and measurement techniques. Individual items are announced in this issue.
The Low Density Supersonic Decelerator Project has undertaken the task of developing and testing a large supersonic ringsail parachute. The parachute under development is intended to provide mission planners more options for parachutes larger than the Mars Science Laboratory's 21.5m parachute. During its development, this new parachute will be taken through a series of tests in order to bring the parachute to a TRL-6 readiness level and make the technology available for future Mars missions. This effort is primarily focused on two tests, a subsonic structural verification test done at sea level atmospheric conditions and a supersonic flight behind a blunt body in low-density atmospheric conditions. The preferred method of deploying a parachute behind a decelerating blunt body robotic spacecraft in a supersonic flow-field is via mortar deployment. Due to the configuration constraints in the design of the test vehicle used in the supersonic testing it is not possible to perform a mortar deployment. As a result of this limitation an alternative deployment process using a ballute as a pilot is being developed. The intent in this alternate approach is to preserve the requisite features of a mortar deployment during canopy extraction in a supersonic flow. Doing so will allow future Mars missions to either choose to mortar deploy or pilot deploy the parachute that is being developed.
NASA is developing a Navigational Doppler LiDAR (NDL) for use in missions involving robotic and human landing scenarios on solar system bodies. The NDL provides unprecedented accuracy in position and velocity measurement for the guidance, navigation and control (GNC) subsystem of a spacecraft. NDL performance has been characterized over different phases of its development through ground tests, helicopter flight tests, and onboard rocket-powered test vehicles, however, none of these tests provided measurements over its full performance envelope. For this reason, a high speed rocket sled test was recently conducted to resolve both range and velocity up to the maximum limits of the NDL. This test campaign was performed at the Supersonic Naval Ordnance Research Tracks (SNORT) facility, Naval Air Weapons Station China Lake, as part of the Safe & Precise Landing and Integrated Capabilities Evolution (SPLICE) project.
Flow in the empty Unitary Planform Wind Tunnel at the NASA Langley Research Center issimulated with computational fluid dynamics methods. The objectives are to assess CFD’s truepredictive capability and to generate flow-field maps upstream of the tunnel’s test section foruse in associated vehicle tests. Multiple CFD solvers, grid adaption methods, and turbulencemodels are used by five teams doing the simulations. The simulation domain is as large aspractical: from the start of the settling chamber, just downstream of the last set of turningvanes, to well downstream of the test section. Simulations are done at three Mach numbers andseveral Reynolds numbers that cover most of the tunnel’s operating range. The sensitivity ofthe CFD solutions to simulation process details, including turbulence model, spatial resolutionand settling-chamber inflow velocity profile, is characterized. Significant sensitivities in somedetails of the predicted test section flow are described. CFD predicts that details of flow inthe settling chamber can affect the flow in the test section. Turning of the flow through thetunnel contraction and past nozzle-block hardware generates streamwise vortices, some ofwhich survive into the core of the test section, principally at low Mach number. Preliminarycomparisons to experimental measurements are given. The major flow characteristics andthe dynamical vortices predicted by CFD exist in the experiment. Several details in CFD andexperiment are observed to differ, including the effects of the vortices and features that appearto be Mach waves in the test section. Sensitivity to grid resolution and turbulence modelingis noted in the vortices; no potential cause for the differences in Mach waves has yet beenidentified in the CFD sensitivity studies.
The span of history covered is from 1958 to the present. The outline of this lecture draws from historical examples of liquid propulsion testing done at AEDC primarily for NASA's Marshall Space Flight Center (NASA/MSFC) in the Saturn/Apollo Program and for USAF Space and Missile Systems dual-use customers. NASA has made dual use of Air Force launch vehicles, Test Ranges and Tracking Systems, and liquid rocket altitude test chambers / facilities. Examples are drawn from the Apollo/ Saturn vehicles and the testing of their liquid propulsion systems. Other examples are given to extend to the family of the current ELVs and Evolved ELVs (EELVs), in this case, primarily to their Upper Stages. The outline begins with tests of the XLR 99 Engine for the X-15 aircraft, tests for vehicle / engine induced environments during flight in the atmosphere and in Space, and vehicle staging at high altitude. The discussion is from the author's perspective and background in developmental testing.
On October 28th, 2009, the National Aeronautics and Space Administration (NASA) launched the Ares I-X Flight Test Vehicle (FTV) from pad 39B, providing the first set of flight test data for NASA's Ares I vehicle design team. This test was critical in providing insight into areas were significant design challenges existed. This paper discusses the objectives of the mission and how they were satisfied. It discusses the overall results of the flight test and look at the data retrieved from the flight. Ares I-X was highly instrumented with over 700 channels of Developmental Flight Instrumentation (DFI). Significant insight was gained in the areas of thrust oscillation, vibro-acoustics, predicting jet interactions and slag ejection from solid rocket systems with submerged nozzles. The paper outlines results from the Guidance Navigation & Control (GN&C), Thermal, Vibro-acoustic, Structures, Aero, Aero-Acoustic and Trajectory teams.
On July 2, 2019, the Ascent Abort 2 (AA-2) Flight Test Vehicle was launched from Cape Canaveral, with the goal of demonstrating the performance of Orion’s Launch Abort System (LAS) and collecting data from hundreds of sensors throughout the vehicle. The data collected during this test flight is of paramount importance, as it will be used to certify the Orion vehicle for human spaceflight. Originally, the data was to be downlinked via a single string network of antennas on the LAS, with the associated risk of potential data dropouts, as well as loss of data once the LAS was jettisoned. Thus, additional antennas were added onto the crew module (CM) to support data downlink post-LAS jettison, a buffer rebroadcast capability was added to fill in any gaps in data downlink transmissions, and an ejectable data recorder (EDR) subsystem was added to the CM as a redundant measure to collect all the instrumentation data. The EDR subsystem was added to the project about one year after the project commenced, which significantly reduced the available development time when compared with the other subsystems of the AA-2 Test Flight. The project was further accelerated by six months, around the critical design review gate. Due to the schedule compression challenge and the fact that the EDR subsystem was a backup system and not flight critical, the EDR subsystem was further challenged to find a new and more efficient way to develop hardware. Thus, the EDR subsystem experimented with different management and systems engineering processes, team sizes, communication methods, and tools. Some examples are novel uses of SharePoint as a Data-centric Project Management & Systems Engineering environment, a continuous testing approach through the lifecycle, and a Skunkworks approach to managing the team. The EDR subsystem blended Commercial Off The Shelf (COTS) hardware with in-house developed hardware and software to create a novel data retrieval capability. The capability evolved rapidly through a hardware in the loop simulation environment that enabled incremental component updates for not only the EDR subsystem but across the entire Crew Module. This paper will present an overview of how the EDR subsystem was managed and compare it to an Agile approach to managing projects. The paper will further provide a recommended approach to future Agile-like hardware development that incorporates lessons learned from the EDR experience.
Flight tests of trailblazer i reentry vehicles
Early in calendar year 1958 Space Technology Laboratories, Inc. (STL) (then Space Technology Laboratories, a division of the Ramo-Wooldridge Corp.) developed for the Air Force Ballistic Missile Division (AFBMD) an Advanced Re-entry Test Vehicle (ARTV) for the purpose of testing ballistic missile nose cones at the full range of 5500 nautical miles. The two-stage ARTV utilized the Thor ballistic missile and the second stage propulsion system developed for the Vanguard program. In late 1957 and early 1958, STL/AFBMD prepared studies of various missile combinations which could be utilized for space testing. The Thor, in combination with the Vanguard second and third stages, was one of the vehicles considered which offered a very early capability of placing a reasonable payload in a lunar orbit. These STL/AFBMD studies were presented to various appropriate groups including the Killian, Millikan, H. J . Stewart Committees; Headquarters, Air Research and Development Command, and ARDC Centers. Subsequently the Advanced Research Projects Agency (ARPA) contacted STL relative to the availability of hardware for an early lunar shot. By utilizing existing spares already purchased for the ARTV, and by making use of the ARTV contractors already in being, it appeared feasible to launch by the third quarter of calendar year 1958 a payload which would be captured by the moon's gravitational force. On 27 March 1958, ARPA directed STL to proceed with a program of three lunar shots. As much as possible, these shots were to utilize existing ARTV spare hardware and impose no interference with the ballistic missile programs. In September this program was transferred to the direction of the National Aeronautics and Space Administration (NASA). On 17 August 1958 the first launching of the Able-1 vehicle was attempted, but the flight was terminated by a propulsion failure of the first stage. Subsequent launchings were attempted on 13 October and 8 November 1958. Of these launchirigs the October attempt was the most successful. Although the payload did not reach the vicinity of the moon, a maximum altitude of 71,700 was attained, and useful scientific data was obtained from the instrumentation.
The pertinent events concerned with the launch, float, and flight of balloon launched decelerator test vehicle AV-2 are discussed. The performance of the decelerator system is analyzed. Data on the flight trajectory and decelerator test points at the time of decelerator deployment are provided. A description of the time history of vehicle events and anomalies encounters during the mission is included.