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 397 records · Page 22

Planning: Management of predictability and uncertainty and keeping abreast of developments

The purpose of this study is to propose method to set up and control of a space mission plan such as that of the HERMES spaceplane. The interest of this subject, other than its complexity, is due to the need to manage imprecision and uncertainty during a mission, as well as changes in between missions. Under these conditions, the set up and control of a flight plan require certain special attention and this has led us to define a certain number of qualities: mastery of complexity in order to resolve conflicts between activities: configuration, resource and time management; consideration of various criteria such as risk minimization or the attainment of mission objectives; robustness and flexibility to allow for hazards and deviations from the norm during operation without having to draw up new plans; aptness for replanning by making changes to the plan without having to set up the whole plan again; and memorization and explanation facility in order to manage developments between missions.

Bastien-Thiry, Christophe↗

Dynamic Arrival Routes: A Trajectory-Based Weather Avoidance System for Merging Arrivals and Metering

Convective weather can cause arrival traffic to fly less efficient weather avoidance routes and is the primary cause for time-based metering to be discontinued. Dynamic Arrival Routes (DAR) is a trajectory-based weather avoidance system that is designed to help improve arrival traffic flow when weather is present. The DAR system continuously analyzes airborne arrival flights for opportunities to reroute them to more efficient arrival routes or around weather that is predicted to be on their current flight plan early enough to allow the arrival time-based metering system to adjust its times of arrival for the presence of weather. Analysis of 93 hours of actual traffic over 12 different days from Fort Worth Center showed DAR proposed more efficient arrival reroutes for 352 arrival flights for an average time savings of 12.3 minutes per flight at a look-ahead time of 60 minutes from the meter fix. DAR also identified 642 arrival flights with a need to deviate around weather and proposed weather avoidance routes that were analytically shown to remain weather-free 83 percent of the time for a look-ahead time of 30 minutes from the meter fix.

Arrivals↗

A Near-Term Concept for Trajectory Based Operations with Air/Ground Data Link Communication

An operating concept and required system components for trajectory-based operations with air/ground data link for today's en route and transition airspace is proposed. Controllers are fully responsible for separation as they are today, and no new aircraft equipage is required. Trajectory automation computes integrated solutions to problems like metering, weather avoidance, traffic conflicts and the desire to find and fly more time/fuel efficient flight trajectories. A common ground-based system supports all levels of aircraft equipage and performance including those equipped and not equipped for data link. User interface functions for the radar controller's display make trajectory-based clearance advisories easy to visualize, modify if necessary, and implement. Laboratory simulations (without human operators) were conducted to test integrated operation of selected system components with uncertainty modeling. Results are based on 102 hours of Fort Worth Center traffic recordings involving over 37,000 individual flights. The presence of uncertainty had a marginal effect (5%) on minimum-delay conflict resolution performance, and windfavorable routes had no effect on detection and resolution metrics. Flight plan amendments and clearances were substantially reduced compared to today s operations. Top-of-descent prediction errors are the largest cause of failure indicating that better descent predictions are needed to reliably achieve fuel-efficient descent profiles in medium to heavy traffic. Improved conflict detections for climbing flights could enable substantially more continuous climbs to cruise altitude. Unlike today s Conflict Alert, tactical automation must alert when an altitude amendment is entered, but before the aircraft starts the maneuver. In every other failure case tactical automation prevented losses of separation. A real-time prototype trajectory trajectory-automation system is running now and could be made ready for operational testing at an en route Center in 1-2 years.

McNally, David↗

Generation and evoluation of near-optimum vertical flight profiles

The overall objectives of this research effort have been to develop and evaluate algorithms and flight management concepts for minimization of fuel or direct operating costs. These concepts are to be used for flight planning or for on-board computation and steering of turbojet transport aircraft in the vertical path. Within this research context, a computer program, called OPTIM, has been developed to use these algorithms to generate near-optimum vertical reference profiles. OPTIM contains control options to examine effects of various flight constraints on cost performance. A companion program, called TRAGEN, was developed to simulate an aircraft flying along a given vertical reference profile. TRAGEN is used to verify OPTIM's output , to examine the effects of parameter value uncertainty (such as prevailing wind), and to compare cost performance of profiles generated by different techniques. This paper describes OPTIM and TRAGEN and presents examples of the programs utility.

Sorensen, J. A.↗

Three Years of Airborne Observations During NASA Activate: A Statistical Summary of Chemical, Optical, and Microphysical Aerosol Properties Over the Western North Atlantic Ocean

Airborne observations are critical to understanding Earth’s climate system and surface-level air quality by providing both spatial and vertical information that is not possible through ground measurement networks or satellite observations. Airborne platforms allow assessments of long-range transport, vertical redistribution, boundary-layer dynamics, and cloud-aerosol-interactions that are critical to model evaluation and satellite validation. Still, the high cost and effort of aircraft operations can limit measurement campaigns to short, focused time periods. Multiple deployments are often necessary for seasonal comparisons, and results can be limited if target phenomenon are infrequent. Subsequent analyses typically focus on case studies, especially if deployment conditions are climatologically anomalous. The NASA ACTIVATE (Aerosol Cloud meTeorology Interactions oVer the western ATlantic Experiment) mission was designed to overcome these limitations by operating semi-continuously over multiple months during multiple seasons. Flight plans were intentionally simple, repetitive, and systematic to provide a statistically robust dataset that could be utilized similarly to a ground-network. Here, we present an overview of three years (2020-2022) of aerosol measurements from the NASA HU-25 Falcon aircraft supporting the ACTIVATE mission. Data from 179 flights were considered, the majority of which were based at NASA Langley Research Center and flown locally over the Wester North Atlantic Ocean just east of Hampton, VA, USA. Airmass characteristics tended to transition from continental outflow near the coast to mostly marine over the open ocean. Seasonal, diurnal, spatial, and vertical trends in aerosol microphysical, optical, and chemical properties are discussed in the context of synoptic scale meteorology. Statistical benefits of the ACTIVATE sampling strategy are discussed with regard to future model evaluation.

Luke D Ziemba↗

A PC based tool for mission plan production

Satellite positioning is managed according to a mission plan (MP) which provides, on a minute accuracy basis, a chronological list of events and associated actions to be performed. This tool, called MM2, is designed under the Windows environment. Excel is used to provide the MP itself. A Visual Basic process then translates it into a graphic symbolic representation called flight plan (FP). During operations, MM2 is also used to log the actual event dates and/or dated OPS Manager live comments.

Joli, Jean-Pierre↗

Survey Development and Initial Data: Flight Context and Pilot Techniques in Everyday Flights

The aviation industry is recognizing that flight crews routinely contribute to system safety in ways that go beyond adherence to standard operating procedures (SOPs). Our research goals were to explore a) whether a survey could shed light on pilots' contributions to adaptation and resilience in everyday flights and b) relevant assessment methods. The survey focused on challenges faced by pilots in normal operations, and on the ways that pilots anticipate and monitor those challenges. We collected responses concerning revenue flights from two pilot groups; one group also provided responses concerning a simulated scenario. The results indicated that relatively few flights proceeded exactly as in the original flight plan. Pilots routinely anticipated and adapted to changing circumstances. We discuss some design and assessment challenges encountered for a survey on this topic, we provide 5 approaches to assessment, and we present example findings as illustrations. We hope assessment methods such as these will lead to useful surveys of resilience in flight.

pilot behavior↗

A practical scheduling algorithm for Shuttle-based astronomy missions

In the Astro mission series (initial flight planned for March, 1986), the Shuttle will be used as a dedicated stellar astronomy observatory. A modified Spacelab pallet is to be used for the Astro payload, which will consist of three ultraviolet (UV) telescopes and a wide field camera mounted together on a single gimbal mount called the Inertial Pointing System (IPS). Three flights of 7-10 days duration are to be made with the same payload at intervals of 8-9 months. Previous experience has shown that changes in design requirements are inevitable, and the evolution of operational concepts will effect changes in scheduling algorithm software. For these reasons, the design goals of the Astron algorithm and its family of auxiliary software modules have been related to functional modularity, constraint flexibility, user friendliness, and 'light' input requirements. Attention is given to hardware characteristics, environmental constraints, the basic criteria function, 'Cinderella' logic, counters and constraints, and scheduling trends.

Guffin, O. T.↗

GeneLab: A Systems Biology Platform for Spaceflight Omics Data

NASA's mission includes expanding our understanding of biological systems to improve life on Earth and to enable long-duration human exploration of space. Resources to support large numbers of spaceflight investigations are limited. NASA's GeneLab project is maximizing the science output from these experiments by: (1) developing a unique public bioinformatics database that includes space bioscience relevant "omics" data (genomics, transcriptomics, proteomics, and metabolomics) and experimental metadata; (2) partnering with NASA-funded flight experiments through bio-sample sharing or sample augmentation to expedite omics data input to the GeneLab database; and (3) developing community-driven reference flight experiments. The first database, GeneLab Data System Version 1.0, went online in April 2015. V1.0 contains numerous flight datasets and has search and download capabilities. Version 2.0 will be released in 2016 and will link to analytic tools. In 2015 Genelab partnered with two Biological Research in Canisters experiments (BBRIC-19 and BRIC-20) which examine responses of Arabidopsis thaliana to spaceflight. GeneLab also partnered with Rodent Research-1 (RR1), the maiden flight to test the newly developed rodent habitat. GeneLab developed protocols for maxiumum yield of RNA, DNA and protein from precious RR-1 tissues harvested and preserved during the SpaceX-4 mission, as well as from tissues from mice that were frozen intact during spaceflight and later dissected. GeneLab is establishing partnerships with at least three planned flights for 2016. Organism-specific nationwide Science Definition Teams (SDTs) will define future GeneLab dedicated missions and ensure the broader scientific impact of the GeneLab missions. GeneLab ensures prompt release and open access to all high-throughput omics data from spaceflight and ground-based simulations of microgravity and radiation. Overall, GeneLab will facilitate the generation and query of parallel multi-omics data, and deep curation of metadata for integrative analysis, allowing researchers to uncover cellular networks as observed in systems biology platforms. Consequently, the scientific community will have access to a more complete picture of functional and regulatory networks responsive to the spaceflight environment.. Analysis of GeneLab data will contribute fundamental knowledge of how the space environment affects biological systems, and enable emerging terrestrial benefits resulting from mitigation strategies to prevent effects observed during exposure to space. As a result, open access to the data will foster new hypothesis-driven research for future spaceflight studies spanning basic science to translational science.

proteomics↗

Activation of microcarrier-attached lymphocytes in microgravity

A technology has been developed to achieve optimal attachment of adhesion-independent lymphocytes to microcarrier beads. The activation of T-lymphocytes by concanavalin A was tested under microgravity conditions in an experiment carried out in space during the first Spacelab Life Science Mission. Activation, measured as the synthesis of deoxyribonucleic acid (DNA) and the production of interferon-gamma, more than doubled in attached lymphocytes in microgravity. The depression of the activation discovered in previous space experiments is due to an impairment not of the lymphocyte but of the macrophage function. The system described here may be useful for radiobiological investigations on the effect of high-energy particles and for testing the efficiency of the immune system in humans during the long-duration space flight planned in the future. The biotechnological significance of the increased lymphokine production in space remains to be assessed.

Non-NASA Center↗

Feasibility of Varying Geo-Fence Around an Unmanned Aircraft Operation Based on Vehicle Performance and Wind

Managing trajectory separation is critical to ensuring accessibility, efficiency, and safety in the unmanned airspace. The notion of geo-fences is an emerging concept, where distance buffers enclose individual trajectories and areas of operation in order to manage the airspace. Currently, the Air Traffic Management system for commercial travel defines static distance buffers around the aircraft; however, commercial UASs are envisioned to operate in significantly closer proximity to other UAS requiring a geo-fence for spacing operations. The geo-fence size can be determined based on vehicle performance characteristics, state of the airspace, weather, and other unforeseen events such as emergency or disaster response. Calculation of the geo-fence size could be determined as part of pre-flight planning and during real-time operations. A largely non-homogeneous fleet of UASs will be operating in low altitude and will likely be commercially developed. Due to intellectual property concerns, the operators may not provide detailed specifications of the control system to UTM. In addition, the huge variety of UAS makes modeling each control system prohibitive and flight data for these vehicles may not exist. Therefore, a generalized, simple geo-fence sizing algorithm must be developed such that it does not rely on detailed knowledge of the vehicle control system, accounts for the presence of urban winds, and is sufficiently accurate. In this work, two simple models are investigated to determine its feasibility as an adequate means for calculating the geo-fence size. The vehicle data used in this work are provided by UAS manufactures who have partnered with NASA's UTM project and some publicly available websites. The first model utilizes wind data processed from the NOAA HRRR (Hourly Rapid Refresh) product and Sonar Annemometer data provided by San Jose State. The second model utilizes OpenFOAM which is a CFD code used to generate a wind field for flow around a single building. The key vehicle performance parameters can include UAS response time to disturbances, command to actuation latency, control system rate limits, time to recovery to desired path, and aerodynamics. It was found that the first model provides an initial understanding of geo-fence sizing, but does not provide enough accuracy to provide UTM with an efficient means of scheduling vehicles. The results of the second model reveal that modeling UAS controls systems with a linearized plant and gain scheduled PID controller does not allow capture the UAS flight dynamics within a significant envelope of the wind disturbances.

uncertainty↗

Improving Operational Acceptability of Dynamic Weather Routes Through Analysis of Commonly Use Routings

The Dynamic Weather Routes (DWR) tool is a ground-based trajectory automation system that continuously and automatically analyzes active in-flight aircraft in en route airspace to find simple modifications to flight plan routes that can save significant flying time, while avoiding weather and considering traffic conflicts, airspace sector congestion, special use airspace, and FAA routing restrictions. Trials of the DWR system have shown that significant delay savings are possible. However, some DWR advised routes are also rejected by dispatchers or modified before being accepted. Similarly, of those sent by dispatchers to flight crews as proposed route change requests, many are not accepted by air traffic control, or are modified before implementation as Center route amendments. Such actions suggest that the operational acceptability of DWR advised route corrections could be improved, which may reduce workload and increase delay savings. This paper analyzes the historical usage of different flight routings, varying from simple waypoint pairs to lengthy strings of waypoints incorporating jet routes, in order to improve DWR route acceptability. An approach is developed that can be incorporated into DWR, advising routings with high historical usage and savings potential similar to that of the nominal DWR advisory. It is hypothesized that modifying a nominal DWR routing to one that is commonly used, and nearby, will result in more actual savings since common routings are generally familiar and operationally acceptable to air traffic control. The approach allows routing segments with high historical usage to be concatenated to form routes that meet all DWR constraints. The relevance of a route's historical usage to its acceptance by dispatchers and air traffic control is quantified by analyzing historical DWR data. Results indicate that while historical usage may be less of a concern to flight dispatchers accepting or rejecting DWR advised route corrections, it may be important to air traffic control acceptance of DWR routes.

dynamic weather routes↗

Improving Operational Acceptability of Dynamic Weather Routes (DWR) Through Analysis of Commonly Used Routings

The Dynamic Weather Routes (DWR) tool is a ground-based trajectory automation system that continuously and automatically analyzes active in-flight aircraft in en route airspace to find simple modifications to flight plan routes that can save significant flying time, while avoiding weather and considering traffic conflicts, airspace sector congestion, special use airspace, and FAA routing restrictions. Trials of the DWR system have shown that significant delay savings are possible. However, some DWR advised routes are also rejected by dispatchers or modified before being accepted. Similarly, of those sent by dispatchers to flight crews as proposed route change requests, many are not accepted by air traffic control, or are modified before implementation as Center route amendments. Such actions suggest that the operational acceptability of DWR advised route corrections could be improved, which may reduce workload and increase delay savings. This paper analyzes the historical usage of different flight routings, varying from simple waypoint pairs to lengthy strings of waypoints incorporating jet routes, in order to improve DWR route acceptability. An approach is developed that can be incorporated into DWR, advising routings with high historical usage and savings potential similar to that of the nominal DWR advisory. It is hypothesized that modifying a nominal DWR routing to one that is commonly used, and nearby, will result in more actual savings since common routings are generally familiar and operationally acceptable to air traffic control. The approach allows routing segments with high historical usage to be concatenated to form routes that meet all DWR constraints. The relevance of a routes historical usage to its acceptance by dispatchers and air traffic control is quantified by analyzing historical DWR data. Results indicate that while historical usage may be less of a concern to flight dispatchers accepting or rejecting DWR advised route corrections, it may be important to air traffic control acceptance of DWR routes.

Operational Acceptability↗

Management by Trajectory: Improving Predictability for Airspace Operations

In the present-day National Airspace System, the air traffic management system attempts to predict the trajectory for each flight based on the flight plan and scheduled or controlled departure time. However, gaps in trajectory data and models, coupled with tactical control actions that are not communicated to automation systems or other stakeholders, lead to trajectory predictions that are less accurate than they could be. This affects traffic flow management performance. Management by Trajectory (MBT) is a NASA concept for air traffic management in which every flight operates in accordance with a 4D trajectory that is negotiated between the airspace user and the FAA to account for the airspace user’s goals while complying with NAS constraints. The primary benefit of MBT is an improvement in system performance due to increased trajectory predictability and stability, which result from managing traffic in all four dimensions (2D route, vertical, and time), ensuring that changes to the flight’s trajectory are incorporated into the assigned trajectory, and utilizing improved time or arrival control standards. Importantly, the performance improvements support increasing efficiency without increasing collision risk. This paper provides an overview of MBT and describes fast-time simulation results evaluating the safety, performance, and efficiency effects of MBT.

Fernandes, Alicia B.↗

Airspace Technology Demonstration 3 (ATD-3): Dynamic Weather Routes (DWR) Technology Transfer Document Summary Version 2.0

This summary document and accompanying technology artifacts satisfy the first of three Research Transition Products (RTPs) defined in the Applied Traffic Flow Management (ATFM) Research Transition Team (RTT) Plan. The original transfer, completed in September 2016, consisted of NASA's legacy Dynamic Weather Routes (DWR) work for efficient routing for en-route weather avoidance. This transfer updates the Concept of Operations document to a publicly-available NASA Technical Memorandum. Dynamic Weather Routes (DWR) is a ground-based trajectory automation system that continuously and automatically analyzes active in-flight aircraft in en route airspace to identify opportunities for simple corrections to flight plan routes that can save significant flying time, at least five minutes wind-corrected, while avoiding weather and considering traffic conflicts, airspace sector congestion, special use airspace, and FAA routing restrictions.

DWR↗

Flight test of ARINC 741 configuration low gain SATCOM system on Boeing 747-400 aircraft

The Boeing company conducted a flight test of a SATCOM system similar to the ARINC 741 configuration on a production model 747-400. A flight plan was specifically designed to test the system over a wide variety of satellite elevations and aircraft attitudes as well as over land and sea. Interface bit errors, signal quality and aircraft position and navigational inputs were all recorded as a function of time. Special aircraft maneuvers were performed to demonstrate the potential for shadowing by aircraft structures. Both a compass rose test and the flight test indicated that shadowing from the tail is insignificant for the 747-400. However, satellite elevation angles below the aircraft horizon during banking maneuvers were shown to have a significant deleterious effect on SATCOM communications.

Murphy, Timothy A.↗

Validation of an Automated System for Arrival Traffic Management

The fuel-efficiencies of arrival flights that were managed by an automated system were compared to the fuel-efficiencies of arrival flights that were managed by air traffic controllers. It was infeasible to have the automated system control arrivals in real operations, so the comparison was accomplished by setting up a fast-time simulation where the automated system could manage arrivals with the same initial conditions and flight plans as those that operated in real operations during a selected comparison period and in the same background traffic. For this study, Newark Liberty International Airport was selected as the arrival airport because its high traffic load and constrained arrival procedures were expected to highlight fuel-efficiency benefits of an automated system. In the simulation, the automated system managed Newark arrivals, and the other flights (arrivals to other airports, departures, and overflights) composed the background traffic. To match the simulation and the real operations background traffic, the other flights flew in simulation the same trajectory that they flew in real operations during the comparison period. Fuel-efficiency was measured by calculating fuel burns of the arrival trajectories. The fuel-efficiencies of arrival trajectories produced in the simulation were compared with the estimated fuel-efficiencies of arrival trajectories recorded from real operations during the comparison period. Results showed that automation managed arrivals burned 346 lbs less fuel per flight on average than controller managed arrivals.

air traffic control↗

Validation of an Automated System for Arrival Traffic Management

The fuel-efficiencies of arrival flights that were managed by an automated system were compared to the fuel-efficiencies of arrival flights that were managed by air traffic controllers. It was infeasible to have the automated system control arrivals in real operations, so the comparison was accomplished by setting up a fast-time simulation where the automated system could manage arrivals with the same initial conditions and flight plans as those that operated in real operations during a selected comparison period and in the same background traffic. For this study, Newark Liberty International Airport was selected as the arrival airport because its high traffic load and constrained arrival procedures were expected to highlight fuel-efficiency benefits of an automated system. In the simulation, the automated system managed Newark arrivals, and the other flights (arrivals to other airports, departures, and overflights) composed the background traffic. To match the simulation and the real operations background traffic, the other flights flew in simulation the same trajectory that they flew in real operations during the comparison period. Fuel-efficiency was measured by calculating fuel burns of the arrival trajectories. The fuel-efficiencies of arrival trajectories produced in the simulation were compared with the estimated fuel-efficiencies of arrival trajectories recorded from real operations during the comparison period. Results showed that automation managed arrivals burned 346 lbs less fuel per flight on average than controller managed arrivals.

air traffic control↗