Search NASA⌕ Search

SEARCH · Search NASA

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 307 records · Page 17

Practical aspects of modeling aircraft dynamics from flight data

The purpose of parameter estimation, a subset of system identification, is to estimate the coefficients (such as stability and control derivatives) of the aircraft differential equations of motion from sampled measured dynamic responses. In the past, the primary reason for estimating stability and control derivatives from flight tests was to make comparisons with wind tunnel estimates. As aircraft became more complex, and as flight envelopes were expanded to include flight regimes that were not well understood, new requirements for the derivative estimates evolved. For many years, the flight determined derivatives were used in simulations to aid in flight planning and in pilot training. The simulations were particularly important in research flight test programs in which an envelope expansion into new flight regimes was required. Parameter estimation techniques for estimating stability and control derivatives from flight data became more sophisticated to support the flight test programs. As knowledge of these new flight regimes increased, more complex aircraft were flown. Much of this increased complexity was in sophisticated flight control systems. The design and refinement of the control system required higher fidelity simulations than were previously required.

Iliff, K. W.↗

Numerical Simulations and Diagnostic Studies of Meteorological Conditions During PEM-Tropics B

Provides a final report on the work accomplished by several meteorological scientists under a NASA grant in conjunction with the DC-8 component of Pacific Exploratory Mission (PEM)-Tropics B. The responsibilities of the principal investigator included collaboration with the Science Team on flight planning, presentation of forecasts, and the preparation of map discussions for each flight. In a published manuscript, the principal investigator summarized the meteorological conditions during PEM-TB which included mean flow patterns, subtropical anticyclones, the South Pacific Convergence Zone (SPCZ), and the Intertropical Convergence Zone (ITCZ). Methodologies used included streamlines, ten day backward trajectories, thermodynamic soundings, and satellite imagery. Other interests included air sampling for the purpose of determining pollution levels.

Fuelberg, Henry E.↗

Use NU-WRF and GCE Model to Simulate the Precipitation Processes During MC3E Campaign

One of major CRM approaches to studying precipitation processes is sometimes referred to as "cloud ensemble modeling". This approach allows many clouds of various sizes and stages of their lifecycles to be present at any given simulation time. Large-scale effects derived from observations are imposed into CRMs as forcing, and cyclic lateral boundaries are used. The advantage of this approach is that model results in terms of rainfall and QI and Q2 usually are in good agreement with observations. In addition, the model results provide cloud statistics that represent different types of clouds/cloud systems during their lifetime (life cycle). The large-scale forcing derived from MC3EI will be used to drive GCE model simulations. The model-simulated results will be compared with observations from MC3E. These GCE model-simulated datasets are especially valuable for LH algorithm developers. In addition, the regional scale model with very high-resolution, NASA Unified WRF is also used to real time forecast during the MC3E campaign to ensure that the precipitation and other meteorological forecasts are available to the flight planning team and to interpret the forecast results in terms of proposed flight scenarios. Post Mission simulations are conducted to examine the sensitivity of initial and lateral boundary conditions to cloud and precipitation processes and rainfall. We will compare model results in terms of precipitation and surface rainfall using GCE model and NU-WRF

Tao, Wei-Kuo↗

Complete Decoding and Reporting of Aviation Routine Weather Reports (METARs)

Aviation Routine Weather Report (METAR) provides surface weather information at and around observation stations, including airport terminals. These weather observations are used by pilots for flight planning and by air traffic service providers for managing departure and arrival flights. The METARs are also an important source of weather data for Air Traffic Management (ATM) analysts and researchers at NASA and elsewhere. These researchers use METAR to correlate severe weather events with local or national air traffic actions that restrict air traffic, as one example. A METAR is made up of multiple groups of coded text, each with a specific standard coding format. These groups of coded text are located in two sections of a report: Body and Remarks. The coded text groups in a U.S. METAR are intended to follow the coding standards set by National Oceanic and Atmospheric Administration (NOAA). However, manual data entry and edits made by a human report observer may result in coded text elements that do not follow the standards, especially in the Remarks section. And contrary to the standards, some significant weather observations are noted only in the Remarks section and not in the Body section of the reports. While human readers can infer the intended meaning of non-standard coding of weather conditions, doing so with a computer program is far more challenging. However such programmatic pre-processing is necessary to enable efficient and faster database query when researchers need to perform any significant historical weather analysis. Therefore, to support such analysis, a computer algorithm was developed to identify groups of coded text anywhere in a report and to perform subsequent decoding in software. The algorithm considers common deviations from the standards and data entry mistakes made by observers. The implemented software code was tested to decode 12 million reports and the decoding process was able to completely interpret 99.93 of the reports. This document presents the deviations from the standards and the decoding algorithm. Storing all decoded data in a database allows users to quickly query a large amount of data and to perform data mining on the data. Users can specify complex query criteria not only on date or airport but also on weather condition. This document also describes the design of a database schema for storing the decoded data, and a Data Warehouse web application that allows users to perform reporting and analysis on the decoded data. Finally, this document presents a case study correlating dust storms reported in METARs from the Phoenix International airport with Ground Stops issued by Air Route Traffic Control Centers (ATCSCC). Blowing widespread dust is one of the weather conditions when dust storm occurs. By querying the database, 294 METARs were found to report blowing widespread dust at the Phoenix airport and 41 of them reported such condition only in the Remarks section of the reports. When METAR is a data source for an ATM research, it is important to include weather conditions not only from the Body section but also from the Remarks section of METARs.

METAR Decoder/Parser↗

Tactical Separation and Safety Alerting System for Terminal Airspace

Provision of tactical alerts to aid air traffic controllers in providing separation assurance in terminal airspace is hindered by the complexity of the airspace, its operations, and flight procedures. A prototype automation system is studied that provides controllers with both separation and safety alerts based on or derived from the separation standard for terminal airspace. The system models flight trajectories heuristically, with use of merged intent information from readily available sources: area navigation departure procedures, flight-plan routes, and arrival nominal interior routes used in terminal automation systems. Flight vertical intent is modeled according to standard procedural restrictions except when superseded by controller-issued altitude clearances. Importantly, flight trajectories are modeled for all aircraft, including those conducting visual approaches. New safety-alert thresholds for aircraft conducting visual approaches are studied. Performance of the system is evaluated through fast-time playback of recorded air traffic data from high-fidelity Human-In-The-Loop simulations and real-world operations in two Terminal Radar Approach Control facilities. The prototype system is found to produce a false-alert rate of 8% for separation alerts. The number and validity of safety alerts are studied by comparing with the current Conflict Alert system, showing that the false alerts of Conflict Alert are at 85% and they are avoided in the prototype system.

Air Traffic Management↗

Peroxide Propulsion at the Turn of the Century

A resurgence of interest in peroxide propulsion has occurred in the last years of the 21st Century. This interest is driven by the need for lower cost propulsion systems and the need for storable reusable propulsion systems to meet future space transportation system architectures. NASA and the Air Force are jointly developing two propulsion systems for flight demonstration early in the 21st Century. One system will be a development of Boeing's AR2-3 engine, which was successfully fielded in the 1960s. The other is a new pressure-fed design by Orbital Sciences Corporation for expendable mission requirements. Concurrently NASA and industry are pursuing the key peroxide technologies needed to design, fabricate, and test advanced peroxide engines to meet the mission needs beyond 2005. This paper will present a description of the AR2-3, report the status of its current test program, and describe its intended flight demonstration. This paper will then describe the Orbital 10K engine, the status of its test program, and describe its planned flight demonstration. Finally the paper will present a plan, or technology roadmap, for the development of an advanced peroxide engine for the 21st Century.

Anderson, William E.↗

Concept of Operations for Management by Trajectory

This document describes Management by Trajectory (MBT), a concept for future air traffic management (ATM) in which every flight operates in accordance with a four-dimensional trajectory (4DT) that is negotiated between the airspace user and the Federal Aviation Administration (FAA) to respect the airspace user's goals while complying with National Airspace System (NAS) constraints. In the present-day NAS, the ATM system attempts to predict the trajectory for each flight based on the approved flight plan and scheduled or controlled departure time. However, once the aircraft starts to move, controllers tactically manage the aircraft to implement traffic management restrictions, separate otherwise conflicting aircraft, and address arising NAS constraints. Tactical controller actions are not directly communicated to the automation systems or other stakeholders. Furthermore, the initial trajectory prediction does not anticipate these disruptions or how they will impact the flight. Consequently, and compounded by gaps in required data and models, trajectory predictions are less accurate than possible, which affects Traffic Flow Management (TFM) performance. A cornerstone of the MBT concept is that all air vehicles have, at all times, an assigned 4DT from their current state to their destination. These assigned trajectories consist of trajectory constraints and descriptions. Pilots and air traffic controllers, with the aid of automation, operate the aircraft to comply with the assigned trajectory, unless first negotiating a revision. Equipped aircraft have substantial responsibility for complying with the assigned trajectory without controller intervention. To maximize the operational flexibility available to the airspace user, the assigned trajectory only imposes trajectory constraints as required to achieve the ATM goals of NAS constraint compliance and aircraft separation. Trajectory descriptions are added to the assigned trajectory to ensure sufficient predictability. To further improve trajectory prediction accuracy, airspace users supplement the assigned trajectory by broadcasting intent information and updating it as necessary. Air vehicle intent is a more detailed description of the airspace user's plan for how the flight will fly the assigned trajectory. Air vehicle intent can change freely, without negotiation, as long as it remains in compliance with the assigned trajectory. Aircraft assigned trajectories, air vehicle intent, and predicted trajectories are shared, creating a common view among stakeholders. A NAS Constraint Service gathers and publishes information about all known NAS constraints, enabling airspace users to be informed participants in trajectory negotiation. Trajectory constraints in the assigned trajectory are mapped to NAS constraints to facilitate identifying which aircraft are affected when NAS constraints change. To support efficient trajectory negotiation, all aircraft provide current information about air vehicle capabilities. Assigned trajectories are constructed to satisfy all known NAS constraints, improving trajectory stability and predictability. Uncertainty and disruptions are handled by modifying the assigned trajectory as far in advance as possible. By proactively negotiating changes to the assigned trajectory, rather than relying on controller-selected tactical actions such as vectors to resolve traffic conflicts or implement miles-in-trail restrictions, MBT keeps aircraft on closed trajectories that are fully known to all stakeholders. Since reactive air traffic control actions cannot be predicted in advance, the downstream trajectory cannot be accurately predicted until they happen. Reliable trajectory predictions allow the system to identify needed modifications to trajectories further in advance, where they can be negotiated and communicated as amendments (i.e., additional or altered trajectory constraints) to the assigned trajectory. Decision Support Tools (DSTs) aid controllers in rapidly defining and communicating closed trajectories to the aircraft and support all stakeholders in trajectory negotiation. Anticipated MBT benefit mechanisms include more accurate trajectory predictions, improved ATM performance and robustness to off-nominal conditions, increased flexibility and operational efficiency, reduced impediments to emerging classes of airspace users accessing NAS resources, reduced environmental impacts, and enhanced safety.

ConOps↗

Launch mission summary: Intelsat 5 (F3) Atlas/Centaur-55

Intelsat 5 (F3) spacecraft, launch vehicle, and mission are described. Information relative to launch windows, flight plan, radar and telemetry coverage, selected trajectory information, and a brief sequence of flight events is provided.

Source record↗

Launch mission summary INTELSAT V (F5) Atlas/Centaur-60

The Atlas/Centaur 60 launch vehicle, INTELSAT V (F5) spacecraft, and mission are summarized. Also included is information relative to launch windows, flight plan, radar and telemetry coverage, selected trajectory information, and a brief sequence of flight events.

Source record↗

Pilot Interactions in an Over-Constrained Conflict Scenario as Studied in a Piloted Simulation of Autonomous Aircraft Operations

Feasibility and safety of autonomous aircraft operations were studied in a multi-piloted simulation of overconstrained traffic conflicts to determine the need for, and utility of, priority flight rules to maintain safety in this extraordinary and potentially hazardous situation. An overconstrained traffic conflict is one in which the separation assurance objective is incompatible with other objectives. In addition, a proposed scheme for implementing priority flight rules by staggering the alerting time between the two aircraft in conflict was tested for effectiveness. The feasibility study was conducted through a simulation in the Air Traffic Operations Laboratory at the NASA Langley Research Center. This research activity is a continuation of the Distributed Air-Ground Traffic Management feasibility analysis reported in the 4th USA/Europe Air Traffic Management R&D Seminar in December 2001 (paper #48). The over-constrained conflict scenario studied here consisted of two piloted aircraft that were assigned an identical en-route waypoint arrival time and altitude crossing restriction. The simulation results indicated that the pilots safely resolved the conflict without the need for a priority flight rule system. Occurrences of unnecessary maneuvering near the common waypoint were traced to false conflict alerts, generated as the result of including waypoint constraint information in the broadcast data link message issued from each aircraft. This result suggests that, in the conservative interests of safety, broadcast intent information should be based on the commanded trajectory and not on the Flight Management System flight plan, to which the aircraft may not actually adhere. The use of priority flight rules had no effect on the percentage of the aircraft population meeting completely predictable which aircraft in a given pair would meet the constraints and which aircraft would make the first maneuver to yield right-of-way. Therefore, the proposed scheme for implementing priority flight rules through staggering the alerting time between the two aircraft was completely effective. The data and observations from this experiment, together with results from the previously reported study, support the feasibility of autonomous aircraft operations.

Wing, David J.↗

Synthetic Vision Enhanced Surface Operations and Flight Procedures Rehearsal Tool

Limited visibility has been cited as predominant causal factor for both Controlled-Flight-Into-Terrain (CFIT) and runway incursion accidents. NASA is conducting research and development of Synthetic Vision Systems (SVS) technologies which may potentially mitigate low visibility conditions as a causal factor to these accidents while replicating the operational benefits of clear day flight operations, regardless of the actual outside visibility condition. Two experimental evaluation studies were performed to determine the efficacy of two concepts: 1) head-worn display application of SVS technology to enhance transport aircraft surface operations, and 2) three-dimensional SVS electronic flight bag display concept for flight plan preview, mission rehearsal and controller-pilot data link communications interface of flight procedures. In the surface operation study, pilots evaluated two display devices and four display modes during taxi under unlimited and CAT II visibility conditions. In the mission rehearsal study, pilots flew approaches and departures in an operationally-challenged airport environment, including CFIT scenarios. Performance using the SVS concepts was compared to traditional baseline displays with paper charts only or EFB information. In general, the studies evince the significant situation awareness and enhanced operational capabilities afforded from these advanced SVS display concepts. The experimental results and conclusions from these studies are discussed along with future directions.

Arthur, Jarvis J., III↗

Evolution of Space Shuttle Range Safety Ascent Flight Envelope Design

For every space vehicle launch from the Eastern Range in Florida, the range user must provide specific Range Safety (RS) data products to the Air Force's 45th Space Wing in order to obtain flight plan approval. One of these data products is a set of RS ascent flight envelope trajectories that define the normal operating region of the vehicle during powered flight. With the Shuttle Program launching 135 manned missions over a 30-year period, 135 envelope sets were delivered to the range. During this time, the envelope methodology and design process evolved to support mission changes, maintain high data quality, and reduce costs. The purpose of this document is to outline the shuttle envelope design evolution and capture the lessons learned that could apply to future spaceflight endeavors.

Brewer, Joan↗

SEACIONS During the 2012 Asian Monsoon: A Strategic Approach to Determining Convective Impacts on Tropospheric Ozone and TTL Gravity Waves

Purpose of making ozone and water vapor profiles measurements in SEAC4RS is to give consistent coverage of the vertical structure at fixed sites to (1) complement 2 campaign aircraft sampling; (2) ground-truth satellite measurements of H O and ozone; (3) provide profiles for model evaluation; (4) study processes responsible for day-to-day variability at each site. Revised objective for 2013, due to cancellation of the 2012 and 2013 plans to operate in Southeast Asia: rapidly re-configure the original "SEACIONS," Southeast Asian Consortium for Intensive Ozonesonde Network Study, to a SouthEast American plan (SEACIONS) for collecting daily ozonesonde data during DC-8 and ER-2 flights throughout the southeastern US. As in previous IONS (2004, 2006, 2008), students were trained at St Louis, Tallahassee, Houston, Penn State, Huntsville, Socorro. Images of the soundings and related flight-planning products were posted each day at NASA and Penn State (PSU) websites. With the aircraft based at Ellington Field (Houston), water CFH (cryogenic frost-point hygrometer) sondes in addition to ozonesondes, were to be taken launched at that site.

Thompson, Anne M.↗

Streak Instability Analysis for BOLT Configuration

The BOLT configuration designed for an upcoming flight experiment exemplifies the complexities of hypersonic boundary layer transition in the presence of multiple and potentially interacting instability mechanisms. A numerical study of the boundary layer instabilities over this configuration has been performed with the goal of applying state-of-the-art tools in multidimensional stability analysis that complement the other ongoing research related to the BOLT flight campaign. Specifically, the paper outlines modal instability characteristics of the boundary layer streaks adjacent to the minor-axis symmetry plane of a 1/3 rd scale BOLT configuration that was tested in the low-disturbance hypersonic wind tunnel at Purdue University and both quiet and conventional tunnels at Texas A&M University (TAMU). The basic state computations agree well with the heat flux measurements in the Purdue quiet tunnel as well as with the off-body velocity field described in a previous DNS study at the University of Minnesota. The encouraging agreement between the predicted frequency spectra of the streak instability in the region of increased boundary layer thickness and the surface pressure spectra measured during the TAMU experiments suggests that these streak instabilities may play an important role during the transition process near the symmetry plane. The modest value of the predicted peak N-factor (N max ≈ 5) for the streak instabilities provides a potential explanation for why transition is not observed under quiet flow conditions, but may occur in a noisy wind tunnel. Similar instability analyses are performed for the flight configuration at two selected flow conditions from the ascent portion of the planned flight trajectory. The predicted values of the peak N-factor suggest that transition onset in the vicinity of the center plane is possible at the ascent time of t = 26.98 seconds (N max ≈ 12.5 at X/L = 0.77), but the streak instabilities weaken sufficiently at the later time of t = 28.88 seconds (N max ≈ 11.5 at X/L ≈ 1.00) and are less likely to cause transition at that time.

Laminar turbulent transition↗

Computing Proximity to Threat Along Uncertain Trajectory to Support Urban Air Mobility

Many airspace threats affect the selection of a flight route, such as terrain, physical obstacles, adverse weather, and special-use airspace, among others. Threat avoidance during Urban Air Mobility (UAM) and Low Altitude Mobility (LAM) flights is especially challenging due to their lower cruising altitudes. These operations may be exposed to buildings, towers, trees, terrain undulations, etc., along much of their flight route. Moreover, these low-altitude flights in urban environments are expected to encounter very busy airspace, increasing the workload associated with threat avoidance. The Proximity to Threat (PtT) function aims to support onboard or remote pilots by computing the risk from geospatial threats in the airspace along an aircraft’s flight path. The threats are both static entities and dynamic airspace restrictions that have been modeled and stored in geo-referenced mapping databases. The flight path may be specified by waypoints, airways, or similar discrete route elements or by a time series of closely spaced position and altitude points. Flight path uncertainty can also be taken into account by assuming both the position and altitude to be sampled from two normal distributions, each being specified by a mean and variance. PtT uses this additional information to verify that the flight path remains clear of threats along a wider path or if a position is reached earlier or later than anticipated, assuring the pilot or operator that there will be an available safety margin even if the aircraft deviates due to one or more occurrences of unexpected wind gusts, mechanical failures, airspeed changes, collision avoidance maneuvers, etc. The client can specify an uncertainty confidence level to bound the set of trajectories evaluated for threats so that the confidence level corresponds to the client’s risk tolerance under the expected conditions. PtT can be used as a pre-flight planning tool to determine a safe route through known threats and in-flight to avoid emerging or changing threats. In this report, we present the PtT function, discuss how the trajectory uncertainty is incorporated into the PtT function, and describe the use of this PtT function in a representative scenario.

urban air mobility↗

The Space Shuttle Orbiter approach and landing tests - A correlation of flight and predicted performance data

This paper represents the results of a program in which a flight test vehicle was flown for a limited number of flights. The vehicle was the Space Shuttle Orbiter. The total free flight time for the entire flight test program was less than half an hour. The flight regime tested represented only the approach and landing phase of the vehicle's planned flight capability. The program relied heavily on an extensive wind tunnel test program to predict the aerodynamic performance data over the complete flight range, as well as to predict data tolerances. During the flight test program, short maneuvers performed were to provide flight motion data. A data extraction program was developed to produce flight derived aerodynamic performance data in coefficient form from the motion data. The resultant flight test data was correlated with the predicted data and fell within the predicted data tolerances for all phases of the subsonic flight test regime, including ground effects.

Romere, P. O.↗

Launch mission summary: FLTSATCOM-D Atlas/Centaur-57

The largest and heaviest spacecraft yet to be launched into geosynchronous orbit by an Atlas Centaur launch vehicle, FLTSATCOM D is part of a versatile military satellite communication system which includes terminals at Navy land bases, and on naval aircraft, ships, and submarines. The design and capabilities of the launch vehicle are described as well as those of the satellite. Information relative to launch windows, flight plan, radar and telemetry coverage, selected trajectory information is presented. A brief sequence of flight events is included.

Source record↗