Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Flight Plan”

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 1,063 records · Page 59

The rationale for an aeroassist flight experiment

The states of several technologies are reviewed which are critical to the design of an aeroassisted orbital transfer vehicle. In these technologies, advancements are needed which hinge on obtaining new flight data. While some of the work can be done with the wind tunnel and computational disciplines, much of the required new data are tied to finite chemical reaction rates, possible thermal nonequilibrium, high flow enthalpy, and strong viscous effects. Because these effects cannot be modeled adequately in ground-based facilities, computational methods lack adequate verification to allow committing to the design of an aeroassist vehicle. Thus a new flight experiment is being planned by NASA to gather the required data. The flight experiment and associated instrumentation which NASA is proposing is discussed briefly.

Jones, Jim J.↗

Spacecraft contamination experience

Effective contamination control must encompass all aspects of ground and flight from design of the system through the end of mission life. Design systems are needed to minimize sensitivity to contamination, ease of cleaning, and contaminant production. Facilities and procedures are critical to maintaining cleanliness during ground operations. Flight operations should be planned so as to minimize contamination. More data from flights are required to assess the adequacy of designs and operations. Standards and specifications should include contamination control requirements.

Borson, E. N.↗

Outcomes of 7 Years of Airborne Trace Gas Measurements over California and Nevada: The Alpha Jet Atmospheric eXperiment (AJAX)

The Alpha Jet Atmospheric eXperiment (AJAX) has been flying a scientific payload since January 2011 measuring ozone, carbon dioxide, methane, formaldehyde and meteorological parameters up to 9 kilometers. AJAX is located and operated from the San Francisco Bay Area and has flown a total of 229 flights, on a regular basis (approximately 3 per month) over all seasons cataloguing a long-term record of trace gas concentrations over California and Nevada. The AJAX project focuses on science questions which benefit from routine, frequent observations with flexible scheduling. This presentation will provide an overview of AJAX activities including a discussion of airborne measurements for: Long-Range Transport (LRT) and Stratosphere-to-Troposphere Transport (STT). Regular sampling by AJAX has aided identification of LRT and evidence of STT, which during spring and summer months are visible as elevated O3 laminae within airborne profiles. Some laminae have the ability to impact surface level air quality; Satellite validation - Regular AJAX missions include flights to Railroad Valley, NV in coordination with GOSAT (Greenhouse Gases Observing Satellite) and OCO-2 (Carbon Observatory-2) observations, and more recently to provide coincident measurements under TROPOMI (TROPOspheric Monitoring Instrument); The AJAX project is uniquely flexible to incorporate specialized flights with limited planning notice, such as sampling emissions from California wildfires. Nine wildfires have been sampled, with some more than once allowing to observe emission changes as the fire progresses; Pandora validation - Future work will include development of flight strategies for validation of ground based Pandora spectrometers.

Yates, Emma L.↗

Cassini's Grand Finale: A Mission Planning Retrospective

On September 15, 2017, Cassini plunged deep into Saturn, down to where the atmosphere was sufficiently dense to destroy the spacecraft, making it part of Saturn forever. In the five months leading up to its destruction, Cassini flew between Saturn and its rings 22 times, collecting data from the never before-explored region of the Kronian system. These orbits, the Grand Finale of Cassini, were the culmination of years of planning by the Cassini flight team. This paper looks back upon the mission planning effort in particular, comparing the baseline operational scenarios and contingency plans to the as flown Grand Finale. The bulk of the Grand Finale mission planning effort was focused on the environmental hazards present in the region between Saturn and its rings: the dust and the atmosphere. Dust hazard and atmospheric transit contingency plans were in place to help ensure spacecraft health and maximize science data return. The dust hazard plan gave the operations team the option to turn the spacecraft to a safe attitude during ring-plane crossings had the dust environment proved more threatening than anticipated. The atmospheric transit plan would have made use of an orbital trim maneuver in order to raise or lower periapsis depending on the density of the atmosphere. The proximal environment did have its surprises, though they were good surprises. The dust was significantly less hazardous than predicted. So much so that elements of the contingency plan were leveraged in order to remove a dust hazard protection from the baseline plan, rather than add one to it. While the atmosphere was substantially denser than predicted, it was not dense enough to warrant a periapsis-raise maneuver and actually meant that better in-situ data was gathered. Ultimately, from a mission planning perspective, the Grand Finale went better than expected.

Sturm II, Erick J.↗

Delivery of Colloid Micro-Newton Thrusters for the Space Technology 7 Mission

Two flight-qualified clusters of four Colloid Micro-Newton Thruster (CMNT) systems have been delivered to the Jet Propulsion Laboratory (JPL). The clusters will provide precise spacecraft control for the drag-free technology demonstration mission, Space Technology 7 (ST7). The ST7 mission is sponsored by the NASA New Millennium Program and will demonstrate precision formation flying technologies for future missions such as the Laser Interferometer Space Antenna (LISA) mission. The ST7 disturbance reduction system (DRS) will be on the ESA LISA Pathfinder spacecraft using the European gravitational reference sensor (GRS) as part of the ESA LISA Technology Package (LTP). Developed by Busek Co. Inc., with support from JPL in design and testing, the CMNT has been developed over the last six years into a flight-ready and flight-qualified microthruster system, the first of its kind. Recent flight-unit qualification tests have included vibration and thermal vacuum environmental testing, as well as performance verification and acceptance tests. All tests have been completed successfully prior to delivery to JPL. Delivery of the first flight unit occurred in February of 2008 with the second unit following in May of 2008. Since arrival at JPL, the units have successfully passed through mass distribution, magnetic, and EMI/EMC measurements and tests as part of the integration and test (I&T) activities including the integrated avionics unit (IAU). Flight software sequences have been tested and validated with the full flight DRS instrument successfully to the extent possible in ground testing, including full functional and 72 hour autonomous operations tests. Delivery of the cluster assemblies along with the IAU to ESA for integration into the LISA Pathfinder spacecraft is planned for the summer of 2008 with a planned launch and flight demonstration in late 2010.

Precision Formation Flying↗

Five Year Changes in Surface Elevations Of The Greenland Ice Sheet Measured by Aircraft Laser Altimetry

The Arctic Ice Mapping group (Project AIM) at NASA's Wallops Flight Facility has been conducting systematic topographic surveys of the Greenland Ice Sheet since 1993, using scanning airborne laser altimeters combined with GPS positioning technology. Flight lines were planned to cover all major ice drainage basins, with the intention to repeat the surveys after a 5-year interval in order to detect changes in the ice-sheet volume. The first resurvey was completed in June/July, 1998, along flight lines in the southern half of Greenland which had been first surveyed in 1993. The northern half of the ice sheet will be resurveyed in 1999. The resulting data sets will provide the first comprehensive examination of regional changes in the the surface elevation of the World's second largest ice sheet. This analysis includes the ice sheet fringe areas, which are expected to be much more climatically sensitive than the interior. Data will be presented which demonstrate the combination of the ATM (Airborne Topographic Mapper) sensors and GPS (Global Positioning System) yields measurements which are repeatable at the 10 cm level over baselines in excess of 1000 km.

Krabill, W. B.↗

Flight Test Overview for UAS Integration in the NAS Project

The National Aeronautics and Space Administration is conducting a series of flight tests intended to support the reduction of barriers that prevent unmanned aircraft from flying without the required waivers from the Federal Aviation Administration. The most recent testing supported two separate test configurations. The first investigated the timing of Detect and Avoid (DAA) alerting thresholds using a radar-equipped unmanned vehicle and multiple live intruders flown at varying encounter geometries. The second configuration included a surrogate unmanned vehicle (flown from a ground control station, with a safety pilot on board) flying a mission in a virtual air traffic control airspace sector using research pilot displays and DAA advisories to maintain separation from live and virtual aircraft. The test was conducted over a seven-week span in the summer of 2015. The data from over 100 encounter sorties will be used to inform the RTCA Phase 1 Detect and Avoid and Command and Control Minimum Operating Performance Standards (MOPS) intended to be completed by the summer of 2016. Follow-on flight-testing is planned for the spring of 2016 to capture remaining encounters and support validation of the MOPS.

UAS↗

Atmospheric, Magnetospheric and Plasmas in Space (AMPS) spacelab payload definition study - program analysis and planning for phase C/D document - Volume 7

Typical missions identified for AMPS flights in the arly 1980's are described. Experiment objectives and typical scientific instruments selected to accomplish these objectives are discussed along with mission requirements and shuttle and Spacelab capabilities assessed to determine any AMPS unique requirements. Preliminary design concepts for the first two AMPS flights form the basis for the Phase C/D program plan. This plan implements flights 1 and 2 and indicates how both the scientific and flight support hardware can be systematically evolved for future AMPS flights.

Keeley, J. T.↗

Hyper-X Research Vehicle (HXRV) Experimental Aerodynamics Test Program Overview

This paper provides an overview of the experimental aerodynamics test program to ensure mission success for the autonomous flight of the Hyper-X Research Vehicle (HXRV). The HXRV is a 12-ft long, 2700 lb lifting body technology demonstrator designed to flight demonstrate for the first time a fully airframe integrated scramjet propulsion system. Three flights are currently planned, two at Mach 7 and one at Mach 10, beginning in the fall of 2000. The research vehicles will be boosted to the prescribed scramjet engine test point where they will separate from the booster, stabilize. and initiate engine test. Following 5+ seconds of powered flight and 15 seconds of cowl-open tares, the cowl will close and the vehicle will fly a controlled deceleration trajectory which includes numerous control doublets for in-flight aerodynamic parameter identification. This paper reviews the preflight testing activities, wind tunnel models, test rationale. risk reduction activities, and sample results from wind tunnel tests supporting the flight trajectory of the HXRV from hypersonic engine test point through subsonic flight termination.

Holland, Scott D.↗

Hyper-X Research Vehicle (HXRV) Experimental Aerodynamics Test Program Overview

This paper provides an overview of the experimental aerodynamics test program to ensure mission success for the autonomous flight of the Hyper-X Research Vehicle (HXRV). The HXRV is a 12-ft long, 2700 lb lifting body technology demonstrator designed to flight demonstrate for the first time a fully airframe integrated scramjet propulsion system. Three flights are currently planned, two at Mach 7 and one at Mach 10, beginning in the fall of 2000. The research vehicles will be boosted to the prescribed scramjet engine test point where they will separate from the booster, stabilize, and initiate engine test. Following 5+ seconds of powered flight and 15 seconds of cow-open tares, the cowl will close and the vehicle will fly a controlled deceleration trajectory which includes numerous control doublets for in-flight aerodynamic parameter identification. This paper reviews the preflight testing activities, wind tunnel models, test rationale, risk reduction activities, and sample results from wind tunnel tests supporting the flight trajectory of the HXRV from hypersonic engine test point through subsonic flight termination.

Holland, Scott D.↗

Spacecraft Software Maintenance: An Effective Approach to Reducing Costs and Increasing Science Return

Flight software is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are typically dealing almost entirely with the capabilities of onboard software. This software, even more than critical ground/flight communications systems, is expected to perform perfectly during all phases of spacecraft life. Due to the fact that it can be reprogrammed on-orbit to accommodate degradations or failures in flight hardware, new insights into spacecraft characteristics, new control options which permit enhanced science options, etc., the on- orbit flight software maintenance team is usually significantly responsible for the long term success of a science mission. Failure of flight software to perform as needed can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to maintaining spacecraft software--namely using the original developers, using the mission operations personnel, or assembling a center of excellence for multi-spacecraft software maintenance. Not planning properly for flight software maintenance can lead to unnecessarily high on-orbit costs and/or unacceptably long delays, or errors, in patch installations. A common approach for flight software maintenance is to access the original development staff. The argument for utilizing the development staff is that the people who developed the software will be the best people to modify the software on-orbit. However, it can quickly becomes a challenge to obtain the services of these key people. They may no longer be available to the organization. They may have a more urgent job to perform, quite likely on another project under different project management. If they havn't worked on the software for a long time, they may need precious time for refamiliarization to the software, testbeds and tools. Further, a lack of insight into issues related to flight software in its on-orbit environment, may find the developer unprepared for the challenges. The second approach is to train a member of the flight operations team to maintain the spacecraft software. This can prove to be a costly and inflexible solution. The person assigned to this duty may not have enough work to do during a problem free period and may have too much to do when a problem arises. If the person is a talented software engineer, he/she may not enjoy the limited software opportunities available in this position; and may eventually leave for newer technology computer science opportunities. Training replacement flight software personnel can be a difficult and lengthy process. The third approach is to assemble a center of excellence for on-orbit spacecraft software maintenance. Personnel in this specialty center can be managed to support flight software of multiple missions at once. The variety of challenges among a set of on-orbit missions, can result in a dedicated, talented staff which is fully trained and available to support each mission's needs. Such staff are not software developers but are rather spacecraft software systems engineers. The cost to any one mission is extremely low because the software staff works and charges, minimally on missions with no current operations issues; and their professional insight into on-orbit software troubleshooting and maintenance methods ensures low risk, effective and minimal-cost solutions to on-orbit issues.

Shell, Elaine M.↗

Software verification plan for GCS

This verification plan is written as part of an experiment designed to study the fundamental characteristics of the software failure process. The experiment will be conducted using several implementations of software that were produced according to industry-standard guidelines, namely the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, Software Consideration in Airborne Systems and Equipment Certification, for the development of flight software. This plan fulfills the DO-178A requirements for providing instructions on the testing of each implementation of software. The plan details the verification activities to be performed at each phase in the development process, contains a step by step description of the testing procedures, and discusses all of the tools used throughout the verification process.

Dent, Leslie A.↗

Scenario Complexity for Unmanned Aircraft System Traffic

This work introduces an approach to estimate the complexity of a low-altitude air traffic scenario involving multiple UASs using mathematical programming. Given a set of multi-point UAS flight trajectories, vehicle dynamics, and a conflict resolution algorithm, an abstract model is developed such that it can be solved quickly using a mathematical programming optimization software without running high-fidelity simulations that can be computationally expensive and may not suit real-time apA quick and accurate assessment of complexity for a given traffic scenario can help plan and schedule flights to alleviate traffic bottleneck and mitigate operation risks, especially for unmanned aerial system traffic management where high traffic density or complexity is expected. This work introduces a traffic scenario complexity metric that was constructed based on the number of potential conflicts weighted by the conflict resolution cost associated. The cost associated with a conflict is calculated based on the corresponding conflict resolution maneuvers. To obtain the conflict resolution maneuvers, a MILP-based optimization was formulated with the vehicle model and conflict management parameters incorporated. To evaluate the complexity metrics, an approach of using measurements from high-fidelity simulations was proposed. The scenario complexity measurements for 920 random-generated scenarios were obtained through high-fidelity simulations and treated as the ground truth. Two statistics methods: Pearson and Alternative Conditional Expectations were applied for analysis. The results showed that the number of flights has low correlation with the scenario complexity according to the correlation coefficients calculated by both methods. The Alternative Conditional Expectations method shows that the proposed scenario complexity metric has better correlation with the ground truth than the number of potential conflicts.plications. In the abstract model, each vehicle is represented by a time-varied vector associated with position, speed, and heading information. The total extra distance that aircraft need to divert from their original routes to avoid collisions is computed and used to setup a quadratic programming formula. The metrics including the number of conflicts and extra distances travelled by all vehicles are then utilized to estimate the complexity of a given UAS flight scenario. Results and verification against high-fidelity simulations will be provided in the final draft.

traffic complexity↗

757 Fly-By-Wire Demonstrator Flight Test

The Boeing Company modified a production 757-200 to emulate the 777 fly-by-wire control laws in order to evaluate the operation and performance of the 777 FBW flight control laws in flight. Following installation and checkout of the FBW system, testing began in March, 1992. Flight testing is currently planned to continue through August, 1992. The conventional 757 longitudinal flight control system is retained but controlled by only the captain’s column. The fly-by-wire system is evaluated by the pilot in the first officer’s seat and the safety pilot function is conducted from the captain’s seat. The flight test FBW longitudinal system is a 2-channel flight control system. The first officer’s column drives the current 757 left and right flight control computers (autopilots) which are modified to act as FBW computers. These FBW computers, which emulate the 777-200 FBW control laws, drive their respective autopilot actuators to control the airplane pitch axis. Directional FBW control laws arc emulated in the existing 757 yaw dampers, with corresponding modifications to the normal 757 directional control system. This paper presents a summary of the airplane FBW modifications and the flight test program to evaluate/validate the 777 FBW flight control laws.

Flight Testing↗

Bantam System Technology Project Ground System Requirements Document

The Low Cost Booster Project (LCBP), also known as Bantam, is an element of the Advanced Space Transportation Program focused on Low Cost Booster Technologies. During FY 99 flight demonstrations are planned to demonstrate the feasibility of producing a booster capable of inserting a 150 kg payload into low earth orbit. The ground support system is an element of the full launch system. The ground support system provides for integration of the payload with the launch vehicle, preparation of the vehicle for launch (including maintenance, integration and test of the vehicle flight software), monitor and control of the launch sequence, range safety during launch, and collection of telemetry during the flight up to payload release. The ground support system is intended to make the maximum possible use of Government Off-the-Shelf (GOTS) or Commercial Off-the-Shelf (COTS) hardware and software to obtain the best value in terms of development operations support and ultimate life cycle cost for the launch system.

Moon, J. M.↗

Executive Summary of Propulsion on the Orion Abort Flight-Test Vehicles

The NASA Orion Flight Test Office was tasked with conducting a series of flight tests in several launch abort scenarios to certify that the Orion Launch Abort System is capable of delivering astronauts aboard the Orion Crew Module to a safe environment, away from a failed booster. The first of this series was the Orion Pad Abort 1 Flight-Test Vehicle, which was successfully flown on May 6, 2010 at the White Sands Missile Range in New Mexico. This paper provides a brief overview of the three propulsive subsystems used on the Pad Abort 1 Flight-Test Vehicle. An overview of the propulsive systems originally planned for future flight-test vehicles is also provided, which also includes the cold gas Reaction Control System within the Crew Module, and the Peacekeeper first stage rocket motor encased within the Abort Test Booster aeroshell. Although the Constellation program has been cancelled and the operational role of the Orion spacecraft has significantly evolved, lessons learned from Pad Abort 1 and the other flight-test vehicles could certainly contribute to the vehicle architecture of many future human-rated space launch vehicles.

Jones, Daniel S.↗

A Full-Envelope Air Data Calibration and Three-Dimensional Wind Estimation Method Using Global Output-Error Optimization and Flight-Test Techniques

A novel, efficient air data calibration method is proposed for aircraft with limited envelopes. This method uses output-error optimization on three-dimensional inertial velocities to estimate calibration and wind parameters. Calibration parameters are based on assumed calibration models for static pressure, angle of attack, and flank angle. Estimated wind parameters are the north, east, and down components. The only assumptions needed for this method are that the inertial velocities and Euler angles are accurate, the calibration models are correct, and that the steady-state component of wind is constant throughout the maneuver. A two-minute maneuver was designed to excite the aircraft over the range of air data calibration parameters and de-correlate the angle-of-attack bias from the vertical component of wind. Simulation of the X-48B (The Boeing Company, Chicago, Illinois) aircraft was used to validate the method, ultimately using data derived from wind-tunnel testing to simulate the un-calibrated air data measurements. Results from the simulation were accurate and robust to turbulence levels comparable to those observed in flight. Future experiments are planned to evaluate the proposed air data calibration in a flight environment.

Taylor, Brian R.↗