SEARCH · Engineering Papers

Results for “Jettison”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 91 records · Page 5

All sources NASA NTRS DOE OSTI

NASA NTRS1972

Rocket nozzle automatic release system

The function of the mechanism described is to automatically jettison a rocket nozzle element at the conclusion of boost in order to achieve a cruise mode nozzle configuration for the balance of powered flight. The boost nozzle is retained by latched pistons that are mechanically secured until released by chamber pressure, which simultaneously assumes retention of the nozzle by holding the primary piston in place. Upon attainment of cruise mode, the chamber pressure drops, allowing springs to overcome the primary piston force and pull the keeper ring forward to free the nozzle for jettison by motor exhaust.

Kimball, J. B.↗

NASA NTRS1971

Magnetic simulation of gravity.

Investigation of the feasibility of a magnetically simulated gravity that could make it possible to simulate aircraft jettison processes in a wind tunnel. It is shown that coils capable to produce a thereto suitable magnetic field configuration do exist. Circumstances are defined for which multiple jettison releases may be simulated, and an approximate calculation for the errors due to magnetic field nonuniformities is presented.

Covert, E. E.↗

NASA NTRS1982

Explosively Actuated Opening for Rapid Egress

Flexible linear-shaped charge provides explosive energy to create opening and to jettison panel. Container around explosive charge protects pilot from effects of explosion. Exterior steel strip receives most of force of explosion to jettison severed panel. System allows pilot to bail out from left side of airplane by creating opening where no door exists. Egress system is simple and highly responsive, requiring minimal modifications to airplane.

Bement, L. J.↗

NASA NTRS1981

LANDSAT-D flight segment operations manual, volume 2

Functions, performance capabilities, modes of operation, constraints, redundancy, commands, and telemetry are described for the thematic mapper; the global positioning system; the direct access S-band; the multispectral scanner; the payload correction; the thermal control subsystem; the solar array retention, deployment, and jettison assembly; and the boom antenna retention, deployment, and jettison assembly for LANDSAT 4.

Varhola, J.↗

NASA NTRS1988

The space station integrated refuse management system

The design and development of an Integrated Refuse Management System for the proposed International Space Station was performed. The primary goal was to make use of any existing potential energy or material properties that refuse may possess. The secondary goal was based on the complete removal or disposal of those products that could not, in any way, benefit astronauts' needs aboard the Space Station. The design of a continuous living and experimental habitat in space has spawned the need for a highly efficient and effective refuse management system capable of managing nearly forty-thousand pounds of refuse annually. To satisfy this need, the following four integrable systems were researched and developed: collection and transfer; recycle and reuse; advance disposal; and propulsion assist in disposal. The design of a Space Station subsystem capable of collecting and transporting refuse from its generation site to its disposal and/or recycling site was accomplished. Several methods of recycling or reusing refuse in the space environment were researched. The optimal solution was determined to be the method of pyrolysis. The objective of removing refuse from the Space Station environment, subsequent to recycling, was fulfilled with the design of a jettison vehicle. A number of jettison vehicle launch scenarios were analyzed. Selection of a proper disposal site and the development of a system to propel the vehicle to that site were completed. Reentry into the earth atmosphere for the purpose of refuse incineration was determined to be the most attractive solution.

Anderson, Loren A.↗

NASA NTRS1990

A GNM mission and system design proposal

Here, the author takes an advocacy position for the proposed Mars Global Network Mission (GNM); it is not intended to be an objective review, although both pros and cons are presented in summary. The mission consists of launches from earth in the '96, '98, and '01 opportunities on Delta-class launch vehicles (approx. 1000 kg injected to Mars in 8 to 10 ft diameter shroud). The trans Mars boost stage injects a stack of small independent, aeroshelled spacecraft. The stack separates from the boost stage and each rigid (as opposed to deployable) aeroshell flies to Mars on its own, performing midcourse maneuvers as necessary. Each spacecraft flies a unique trajectory which is targeted to achieve approach atmospheric interface at the desired latitude and lighting conditions; arrival times may vary by a month or more. A direct entry is performed, there is no propulsive orbit capture. The aeroshelled rough-landers are targeted to achieve a desired attitude and entry flight path angle, and then follow a passive ballistic trajectory until terminal descent. Based on sensed acceleration (integrated to deduce altitude), the aft aeroshell skirt is jettisoned; a short later a supersonic parachute is deployed. The ballistic coefficient of the parachute is sized to achieve terminal velocity at about 8 km. However the parachute is not deployed until a few Km above the surface to minimize wind-induced drift. The nose cap descent imaging begins, a laser altimeter also measures true altitude. Based on range and range rate to the surface, the parachute is jettisoned and the lander uses descent engines to achieve touchdown velocity. A contact sensor shuts down the motors to avoid cratering, and the lander rough-lands at less than 5 m/sec. The remaining aeroshell and a deployable bladder attenuate landing loads and minimize the possibility of tip over. Science instruments are deployed and activated, and the network is established.

Bailey, Stephen↗

NASA NTRS1990

The final days of Solar Max - Lessons learned from engineering evaluation tests

End-of-life engineering evaluation tests were performed on Solar Max between October and November 1989. The tests included four-wheel control law operation; reaction wheel rundowns; modular power subsystem standard power regulator unit voltage-temperature level tests; battery rundown/2nd plateau determination; high gain antenna retraction and jettison; and solar array jettison. This paper presents these tests, their results, and the lessons learned from them.

Donnelly, Michael L.↗

NASA NTRS1993

TranAir applications to predicting transonic aircraft/store loads

During a recent AIWS wind tunnel test for the F-18, the AIWS grid loads were in substantial disagreement with carriage loads measured on the opposite pylon at M = 0.95. Carriage loads indicated that the AIWS configuration might impact the fuel tank mounted on the inboard pylon during jettison at M = 0.95, while CTS data indicated this to be a safe jettison condition. An attempt was made to determine the correct loads for this condition. On the basis of PAN AIR and TranAir calculations, it appears that the carriage loads are correct, while the CTS measured grid data may be subject to sting-fuel tank interference effects at transonic speeds.

Cenko, A.↗

NASA NTRS1959

Free-Flight Test of a Technique for Inflating an NASA 12-Foot-Diameter Sphere at High Altitudes

A free-flight test has been conducted to check a technique for inflating an NASA 12-foot-diameter inflatable sphere at high altitudes. Flight records indicated that the nose section was successfully separated from the booster rocket, that the sphere was ejected, and that the nose section was jettisoned from the fully inflated sphere. On the basis of preflight and flight records, it is believed that the sphere was fully inflated by the time of peak altitude (239,000 feet). Calculations showed that during descent, jettison of the nose section occurred above an altitude of 150,000 feet. The inflatable sphere was estimated to start to deform during descent at an altitude of about 120,000 feet.

Kehlet, Alan B.↗

NASA NTRS1999

Rapid Chill and Fill of a Liquid Hydrogen Tank Demonstrated

The NASA Lewis Research Center, in conjunction with Boeing North American, has been supporting the High Energy Upper Stage (HEUS) program by performing feasibility studies at Lewis Supplemental Multilayer Insulation Research Facility (SMIRF). These tests were performed to demonstrate the feasibility of chilling and filling a tank with liquid hydrogen in under 5 minutes. The goal of the HEUS program is to release a satellite from the shuttle cargo bay and then use a cryogenic (high-energy) upper stage to allow the satellite to achieve final orbit. Because of safety considerations, the propellant tanks for the upper stage will be launched warm and dry. They will be filled from the shuttle's external tank during the mission phase after the solid rocket boosters have jettisoned and prior to jettison of the external tank. Data from previous shuttle missions have been analyzed to ensure that sufficient propellant would be available in the external tank to fill the propellant tank of the proposed vehicle upper stage. Because of mission time-line considerations, the propellant tanks for the upper stage will have to be chilled down and filled in approximately 5 minutes. An existing uninsulated flight weight test tank was installed inside the vacuum chamber at SMIRF, and the chamber was evacuated to the 10(exp -5) torr range to simulate space vacuum conditions in the cargo bay with the doors open. During prerun operations, the facility liquid hydrogen (LH2) supply piping was prechilled with the vent gas bypassing the test article. The liquid hydrogen supply dewar was saturated at local ambient pressure and then pressurized with ambient temperature gaseous helium to the test pressure. A control system was used to ensure that the liquid hydrogen supply pressure was maintained at the test pressure.

Kudlac, Maureen T.↗

NASA NTRS2005

MicroPPT-Based Secondary/Backup ACS for a 160-m, 450-kg Solar Sail Spacecraft

Solar sail tip-mounted, lightweight pulsed plasma thrusters (PPTs) are proposed for a secondary (or backup) attitude control system (ACS) of a 160-m, 450-kg solar sail spacecraft of the Solar Polar Imager (SPI) mission. A propellantless primary ACS of the SPI sailcraft employs trim control masses running along mast lanyards for pitch/yaw control together with roll stabilizer bars at the mast tips for quadrant tilt (roll) control. The robustness of such a propellantless primary ACS would be further enhanced by a secondary ACS utilizing tip-mounted, lightweight PPTs. The microPPT-based ACS is intended mainly for attitude recovery maneuvers from various off-nominal conditions that cannot be reliably handled by the propellantless primary ACS. However, it can also be employed for: i) the checkout or standby mode prior to and during sail deployment, ii) the post-deployment transition mode (prior to the propellantless primary ACS mode operation), iii) the solar sailing cruise mode of a trimmed sailcraft, and iv) the spin-stabilized, sun-pointing, safe mode. Although a conventional bus ACS is required for the SPI mission as the sail is jettisoned at the start of its science mission phase, the microPPT-based ACS option promises greater redundancy and robustness for the SPI mission. For other sailing missions, where the sail is never jettisoned, this secondary ACS provides a lower-cost, lower-mass propulsion for deployment control and greater redundancy than any traditional reaction-jet control system. This paper presents an overview nf the state--of-the--art microPPT technology, the design requirements of microPPTs for solar sail attitude control, and the preliminary ACS design and simulation results.

Wie, Bong↗

NASA NTRS2011

Mesh-Based Entry Vehicle and Explosive Debris Re-Contact Probability Modeling

The risk to a crewed vehicle arising from potential re-contact with fragments from an explosive breakup of any jettisoned spacecraft segments during entry has long sought to be quantified. However, great difficulty lies in efficiently capturing the potential locations of each fragment and their collective threat to the vehicle. The method presented in this paper addresses this problem by using a stochastic approach that discretizes simulated debris pieces into volumetric cells, and then assesses strike probabilities accordingly. Combining spatial debris density and relative velocity between the debris and the entry vehicle, the strike probability can be calculated from the integral of the debris flux inside each cell over time. Using this technique it is possible to assess the risk to an entry vehicle along an entire trajectory as it separates from the jettisoned segment. By decoupling the fragment trajectories from that of the entry vehicle, multiple potential separation maneuvers can then be evaluated rapidly to provide an assessment of the best strategy to mitigate the re-contact risk.

McPherson, Mark A.↗

NASA NTRS2015

SLS Test Stand Site Selection

Test site selection is a critical element of the design, development and production of a new system. With the advent of the new Space Launch System (SLS), the National Aeronautics and Space Administration (NASA) had a number of test site selection decisions that needed to be made early enough in the Program to support the planned Launch Readiness Date (LRD). This case study focuses on decisions that needed to be made in 2011 and 2012 in preparation for the April 2013 DPMC decision about where to execute the Main Propulsion Test that is commonly referred to as "Green Run." Those decisions relied upon cooperative analysis between the Program, the Test Lab and Center Operations. The SLS is a human spaceflight vehicle designed to carry a crew farther into space than humans have previously flown. The vehicle consists of four parts: the crew capsule, the upper stage, the core stage, and the first stage solid rocket boosters. The crew capsule carries the astronauts, while the upper stage, the core stage, and solid rocket boosters provide thrust for the vehicle. In other words, the stages provide the "lift" part of the lift vehicle. In conjunction with the solid rocket boosters, the core stage provides the initial "get-off-the-ground" thrust to the vehicle. The ignition of the four core stage engines and two solid rocket boosters is the first step in the launch portion of the mission. The solid rocket boosters burn out after about 2 minutes of flight, and are then jettisoned. The core stage provides thrust until the vehicle reaches a specific altitude and speed, at which point the core stage is shut off and jettisoned, and the upper stage provides vehicle thrust for subsequent mission trajectories. The integrated core stage primarily consists of a liquid oxygen tank, a liquid hydrogen tank, and the four core stage engines. For the SLS program, four RS-25 engines were selected as the four core stage engines. The RS-25 engine is the same engine that was used for Space Shuttle. The test plan for the integrated core stage was broken down into several segments: Component testing, system level testing, and element level testing. In this context, components are items such as valves, controllers, sensors, etc. Systems are items such as an entire engine, a tank, or the outer stage body. The core stage itself is considered to be an element. The rocket engines are also considered an element. At the program level, it was decided to perform a single green run test on the integrated core stage prior to shipment of it to Kennedy Space Center (KSC) for use in the EM-1 test flight of the SLS vehicle. A green run test is the first live fire of the new integrated core stage and engine elements - without boosters of course. The SLS Program had to decide where to perform SLS green run testing.

Crowe, Kathryn↗

NASA NTRS1972

Apollo 16 Press Kit

The Apollo 16 spacecraft is scheduled for launch on Apr. 16, 1972 from Complex 39A at the Kennedy Space Center, Florida by the Saturn V launch vehicle. Crewmen are mission commander John W. Young, command module pilot Thomas K. Mattingly II and lunar module pilot Charles M. Duke Jr. Objectives of the mission, to last up to 12 days, as outlined by NASA: to perform selenological inspection, survey and sampling of materials in a preselected region of Descartes using a lunar roving' vehicle; deploy and activate Apollo surface experiments; develop man's capability to work in the lunar environment; obtain photographs of candidate exploration sites; and toconduct inflight experiments and photographic tasks in lunar orbit. Following launch, the spacecraft will reach Earth Parking Orbit and remain in orbit for about two and one-half revolutions prior to Translunar Injection. Next, the Command and Service Module docks with the Lunar Module and the spacecraft "coasts" to the moon. In orbit around the moon, the Command and Service Module/Lunar Module combination will descend to within 50,000 feet of the lunar surface before undocking. The Lunar Module will continue to descend while the Command and Service Module returns to an orbit approximately 60 miles high. Stay time on the lunar surface is scheduled for approximately 73 hours. The ascent stage of the Lunar Module then lifts the astronauts back into lunar orbit where they will dock with the Command/Service Module. The Lunar Module is jettisoned and Transearth Injection follows. Just prior to reentry into the earth's atmosphere, the Service Module is jettisoned, and the astronauts in the Command Module splashdown in the Pacific Ocean. The target point for end-of-mission splashdown is at 05 degrees 0 minutes north latitude and 158 degrees 40 minutes west longitude or approximately 985 nautical miles south of Honolulu, Hawaii. Splashdown is scheduled for Apr. 28, 1972 at 10:30 a.m. Hawaiian Standard Time (2:30 p.m. CST). Recovery forces for Apollo 16, stationed in both the Atlantic and Pacific Oceans, will consist of three ships, nine aircraft and nearly 1,700 personnel. CTF-130 (Manned Spacecraft Recovery Force, Pacific) forces will be stationed south of Hawaii. Three ships, eight helicopters and three Air Force HC-130H aircraft, and nearly 1,100 personnel, will take part. Task Force 140 (Manned Spacecraft Recovery Force, Atlantic), comprising one ship, six HC-130H aircraft, three helicopters and approximately 300 personnel, will be positioned for possible launch abort operations. Two ships in the Atlantic will also be used for acoustical testing. Other forces, primarily aircraft and personnel of the Air Force Aerospace Rescue and Recovery Service will be on alert around the world for contingency recovery support.

Source record↗

NASA NTRS2017

Comparing Trash Disposal and Reuse Options for Deep Space Gateway and Mars Missions

Taking out the trash at NASA's newly proposed Deep Space Gateway (DSG) will not be a trivial task. While not the most important aspect of planning this cislunar outpost, there are several options that should be carefully considered since they may affect the crew as well as mission mass and volume. This study extends an earlier one, which focused on waste disposal options for a Mars Transit Vehicle. In that study, gasifying and venting trash along the way was found to noticeably reduce propellant needs and launch mass, whereas keeping processed trash on board in the form of radiation shielding tiles would significantly lower the crew's radiation dose during a solar particle event. Another favorable strategy was packing trash in a used logistics module for disposal. Since the DSG does not need much propulsion to maintain its orbit and Orion will be present with its own radiation storm shelter at the Gateway, the driving factors of the waste disposal trade study are different than for the Mars mission. Besides reviewing the propulsion and radiation shielding factors, potential drivers such as mass, power, volume, crew time, and human factors (e.g. smell) were studied. Disposal options for DSG include jettison of a used logistics module containing waste after every human stay, jettison of the same logistics module after several missions once it is full, regular disposal of trash via an airlock, or gasifying waste products for easier disposal or reuse. Conversely, a heat melt compactor device could be used to remove water and stabilize trash into tiles which could be more compactly stored on board and used as radiation shielding. Equivalent system mass analysis is used to tally the benefits and costs (mass, volume, power, crew time) of each case on an equivalent mass basis. Other more subjective factors are also discussed. Recommendations are made for DSG and Mars mission waste disposal.

Ewert, Michael↗

NASA NTRS2017

Vented Launch Vehicle Adaptor for a Manned Spacecraft with "Pusher" Launch Abort System

A system, method, and apparatus for a vented launch vehicle adaptor (LVA) for a manned spacecraft with a "pusher" launch abort system are disclosed. The disclosed LVA provides a structural interface between a commercial crew vehicle (CCV) crew module/service module (CM/SM) spacecraft and an expendable launch vehicle. The LVA provides structural attachment of the module to the launch vehicle. It also provides a means to control the exhaust plume from a pusher-type launch abort system that is integrated into the module. In case of an on-pad or ascent abort, which requires the module to jettison away from the launch vehicle, the launch abort system exhaust plume must be safely directed away from critical and dangerous portions of the launch vehicle in order to achieve a safe and successful jettison.

Vandervort, Robert E.↗

NASA NTRS2019

Software Tool for Tracking & Mapping the NASA Orion AA-2 Test Flight Ejectable Data Recorders in Real Time

On 2 July 2019, the NASA Ascent Abort 2 flight took place off the Florida coast to test the emergency systems to separate the Orion Crew Module (CM) from the future Space Launch System rocket in the event of a malfunction. During this high-altitude test, instrumentation data was recorded on twelve customized buoyant Ejectable Data Recorders (EDRs) and subsequently jettisoned from the CM in mid-air. Upon release, the EDRs activated their GPS-Iridium beacon systems and began transmitting Short Burst Data (SBD) messages via the Iridium satellite network to relay their individual location and system health information. To locate, track and retrieve each EDR from the ocean surface in real-time, multiple open-source programming tools (Python and Linux shells) were developed for parsing the incoming Iridium binary SBD messages. For this, a Linux laptop was used to receive the Iridium-generated emails containing the SBD messages and autonomously execute the parsing tools. The received SBD data contained location, timestamp and health status information that was translated, saved, and subsequently used for simultaneously generating a continuously updated color-coded tabular display summary and unique KML files used with Google Earth to track their locations. Once their locations were known, dedicated recovery vessels retrieved all EDRs from the ocean. An additional tool was also developed in order to generate 5- and 10-minute geolocation predictions for each EDR by deriving the displacement distance, elapsed time, displacement heading and velocity based on the latest known information available. The recovery vessels were also tracked with the use of a separate commercial GPS beacon system. After jettison, 67% of the EDRs transmitted valid data by the time they were retrieved from the ocean. However, the real-time information presented by the plotting tool allowed for the ready depiction of EDR dispersal patterns and reference drift trajectories, which contributed to the recovery of all twelve EDRs and the AA-2 flight data. Lastly, the available data showed that the distance between the software’s reported drift/predicted locations and the recovery locations did not exceed 38 meters, therefore demonstrating the advantages of this software tool for supporting real-time tracking and recovery efforts of beacon devices.

Moxey, Lucas↗

NASA NTRSDate not supplied

An Agile-Like Approach to Hardware Development: The Ejectable Data Recorder (EDR) for Orion's Ascent Abort 2 (AA-2) Test Flight

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.

Agile↗