Search NASA⌕ Search

SEARCH · Search NASA

Results for “flight following mode”

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 19 records

The 4D area navigation system description and flight test results

A 4D area navigation system was designed to guide aircraft along a prespecified flight path (reference path) such that the aircraft would arrive at the approach gate at a time specified by the ATC controller. Key components to achieve this requirement were: (1) stored reference trajectories; (2) a continuously recomputed capture trajectory to a selected waypoint on the reference trajectory so as to achieve the desired time of arrival; (3) electronic situation displays; and (4) a control system to follow the overall trajectory in space and time. The system was implemented in a digital integrated avionics system (STOLAND) installed on a CV-340 airplane. Although the 4D system was designed primarily for automatic operation, it was flight tested in a flight director mode (the pilot follows the flight director commands), because the CV-340 autopilot servos were not tied to the avionics system. The flight test showed that, even in the flight director mode, the pilot did achieve the objectives of path tracking and time of arrival control with only moderate workload. The system also permitted controlled delay of the time of arrival by path stretching, which takes advantage of the continuously changing capture trajectory to predict the time of arrival. Simulations in the automatic and manual modes were used to complement the flight data.

Lee, H. Q.↗

Comanche Helmet-Mounted Display Heading-Tape Simulation

The Aeroflightdynamics Directorate (AMRDEC) conducted a simulation to assess the performance associated with a Contact Analog, world-referenced heading tape as implemented on the Comanche Helmet Integrated Display Sight System (HIDSS) when compared with a Compressed heading tape similar to that specified by the former Military Standard (MIL-STD) 1295. Six experienced pilots flew three modified Aeronautical Design Standards (ADS)-33 maneuvers (Hover Turn, Bob-up, Transient Turn) and a precision traffic pattern in the NASA Vertical Motion Simulator (VMS). Analysis of the pilot objective performance data and subjective handling qualities ratings (HQRs) showed the following: Compressed symbology in the Velocity Stabilization (VelStab) flight mode generally produced the most precise performances over Contact Analog symbology with respect to the heading, altitude, position, and time criteria specified for the maneuvers tested. VelStab outperformed the Automatic Flight Control System (AFCS) on all maneuvers achieving desired performance on most maneuvers for both symbol sets. Performance in the AFCS mode was generally desirable to adequate for heading and altitude and did not meet adequate standards for hover position and time for the Hover Turn and Bob-up maneuvers. VelStab and AFCS performance were nearly the same for the Transient Turn. Pilot comments concerning the Contact Analog heading-tape implementation were generally unfavorable in spite of the achieved levels of performance. HQRs showed Compressed symbology in the VelStab flight mode produced the lowest mean HQR, encompassing mixed ratings of satisfactory handling and needing improvement. All other symbology/flight-mode combinations yielded higher HQRs, which characterized opinions that deficiencies in aircraft handling due to HMD symbology would need improvement. Contact Analog heading tape and other symbology require improvement, especially when operating in the AFCS mode. NASA-TLX rated Compressed symbology in the VelStab flight mode as the least demanding on resources, closely followed by ratings for Contact Analog in the VelStab mode. In a similar pattern, TLX ratings for maneuvers completed in the AFCS mode yielded a higher level of resource demand with even slighter differences between Contact Analog and Compressed symbology sets. Further research should be conducted where objective data and subjective HQR ratings indicate a need for improvement. The areas requiring attention are those where the symbology implementation, the flight control system, or a combination of both caused workload to reach an objectionable level where adequate performance was either difficult to achieve or unachievable. These areas are clearly identified in this report. Symbology that received negative HQR comments by a majority of pilots should also be examined. The summary of pilot comments can be found in appendix A. Additional simulation trials should be considered to address the identified issues.

Turpin, Terry↗

A helicopter terrain following system for terminal area operations

This paper discusses the terminal area guidance and terrain following system developed for the USAF HH-60A Night Hawk Search and Rescue Helicopter. A Multi-Mode Radar and three-cue Flight Path Vector Director provide a terrain following capability at all airspeeds, allowing a decelerating approach to a hover over varying terrain to a designated point. Properties of the terrain following design are discussed. Simulation results using the NASA Ames piloted Vertical Motion Simulator are presented.

Kilmer, F. G.↗

Effect of lead-aircraft ground-speed on self-spacing performance using a cockpit display of traffic information

A simulator investigation was conducted to determine the effect of the lead-aircraft ground-speed quantization level on self-spacing performance using a Cockpit Display of Traffic Information (CDTI). The study utilized a simulator employing cathode-ray tubes for the primary flight and navigation displays and highly augmented flight control modes. The pilot's task was to follow, and self-space on, a lead aircraft which was performing an idle-thrust profile descent to an instrument landing system (ILS) approach and landing. The spacing requirement was specified in terms of both a minimum distance and a time interval. The results indicate that the ground-speed quantization level, lead-aircraft scenario, and pilot technique had a significant effect on self-spacing performance. However, the ground-speed quantization level only had a significant effect on the performance when the lead aircraft flew a fast final approach.

Kelly, J. R.↗

Technical challenges of integrating the Space Shuttle

A review is presented of the technology involved in integrating the Space Shuttle system. A powered flight analysis of the Shuttle is presented, touching upon the following areas: ascent profile and abort mode integration, sizing and design, control of load factor by a stage thrust shaping, structural load constraints, flight performance reserve and trajectory design for the orbital flight test. A discussion is presented of aerothermodynamics including aerodynamic and plume heating. Flight control and separation is considered with attention paid to liftoff, ascent to booster staging, elevon load relief, booster tailoff thrust mismatch and gimbal limitations and booster separation. Structural analysis and dynamics is examined, considering: vehicle loads and modes and the pogo effect. Propulsion aspects (hydraulics, the LH2 recirculation system, the antigeyser system, the pressurization system, etc.), ground vibration tests, separation system verification and flight readiness firing are all described.

Martin, A. C.↗

Monitoring Airspace Complexity and Determining Contributing Factors

The national airspace has evolved over many years to accommodate increased traffic demand [1] while simultaneously maintaining one of the safest forms of transportation [2], [3]. One of the reasons for this success is the ability of the system and the operators to adapt and accommodate to situations that routinely disrupt optimal operations. These situations may include: adverse weather, delays, early arrivals, equipment outages, and other factors that are outside the operators ability to control. These factors can lead to states where automation is unable to properly handle these issues and therefore air traffic controllers and pilots have to intervene, ultimately increasing communication between operators resulting in higher workload. As controller workload increases to handle sub-optimal operating conditions this can be viewed as an increase in complexity. The reasoning for this is because humans are now required to make tactical decisions in response to external factors, resulting in a departure from the strategic plan where operations would be more efficiently managed. Human operators control airspace complexity under rigid regulations that are constantly changing. The airspace is divided into sectors and the number of aircraft assigned to each controller is limited for safe handling. There has been past work that devised airspace complexity metrics in commercial aviation and related these metrics to controller workload (e.g., [4],[5]). The upper bounds on the system load are pre-determined. Such bounds on complexity make for a safe system, but the system cannot scale and adapt to autonomous, dense, and heterogeneous traffic, including the many types of Unmanned Aerial Vehicles (UAVs) envisioned to be added to the operations. We hypothesize that, as traffic density and heterogeneity grow, and other key metrics change, there will be phase transitions at which the way traffic should be managed changes significantly [6]. We offer a method for in-time detection of contributing factors that lead to phase transitions, characterized by increased complexity. To the best of our knowledge, there is no tool similar to our proposed effort that identifies such contributing factors or precursor patterns. To define the scope we are proposing to measure complexity from the viewpoint of the Terminal Radar Approach Control Facilities (TRACON) controller’s perspective. In particular we are analyzing arrivals into KSFO. With safety as the top concern for airspace operators, it is important to recognize that as density and heterogeneity grow, the focus of the system will change. Times of the day when the airspace has low density and heterogeneity, the flights will follow more efficient paths where the aircraft move on established routes that are more or less directly to the destination. However, when density and heterogeneity increases, the system will begin changing focus to avoiding conflicts and collisions and route the flights in a more flexible way. Higher flexibility requires more communication and coordination between controllers and pilots which the current automation is unable to handle. This paper proposes a novel approach that monitors airspace complexity at multiple scales, uses a Machine Learning-based tool that predicts when operations will transition to a regime of greater complexity, and identifies actions that can reduce the complexity while still maintaining efficient and safe operations. We demonstrate our proposed approach using data from multiple complementary sources. This includes, but is not limited to: historical aircraft surveillance data from NASA’s Sherlock Data Warehouse [7], METAR weather data, and airport configuration data from Aviation System Performance Metrics (ASPM). The surveillance data flight paths are sampled at a variable sample rate — increasing as the aircraft approaches the airport. This is due to how Sherlock manages flight track stitching between different radar facilities which have different sampling rates. The weather and performance data are logged at defined intervals throughout the day at a courser refresh rate. In addition to the logged data and metrics, we leverage pre-defined Standard Terminal Arrival Routes (STARs) procedures to characterize the path of each flight. Each flight files for one of these routes in the flight plan well before entering the terminal airspace, and approximately follows the route until it leaves the STAR, typically on the final fix of a runway transition. However, most flights do not always fly the full STAR procedure to completion [8], but the majority do adhere to the fixes within the common route of the procedure. Our approach leverages fixes in the common route of each of the STARs to build a reference path to the airport. This allows us to characterize the flight paths in what we are defining as the “maneuvering area” (the airspace between the STAR and before the flight is lined up on the runway’s final approach) to determine how off nominal the flights are to calculate its complexity score. Determining airspace complexity is a concept that does not have a concrete answer. In designing this metric, we consider what increases the workload for the air traffic controllers. Consequently more specialized vectoring maneuvers results in higher workload. Accordingly, we start with a theory: each flight has a direct path it takes from the STAR’s common route to the final approach’s outer marker fix for the flight’s landing runway. It is important to note that the direct path is only used as a reference. If the majority of the flights have a large consistent offset as compared to other routes it does not necessarily mean that those flights have higher complexity. We are merely building a distribution based on this direct path for that particular STAR and runway pair to determine the normal mode of operations for that route. Flights that are in the upper tail of these distributions will result in higher complexity scores and flights that fly in the median will represent the normal mode of operations and therefore will have lower complexity scores. Since flights following each STAR route take different paths to the airport, we have a different distribution for each STAR route and therefore can model these distributions to compute a complexity score from their respective normalized distributions. To evaluate the effectiveness of our proposed airspace complexity metric we will compare against an established approach based on trajectory clustering [9]. This unsupervised learning technique consists of the following steps: (1) identify the general maneuvering areas (waypoints) by performing $\kappa$-means or DBSCAN clustering on locations where aircraft frequently turn based on the surveillance radar track data, (2) map flight trajectories onto sequences of waypoints, and (3) cluster the sequences based on their common subsequences. From a high-level perspective, this baseline model learns nominal operations in the airspace through the sequence of waypoints that are representative of where aircraft change direction and defines deviations from the nominal operations as “complex.” Therefore, more deviations from the nominal operations correspond to higher complexity values. For our validation, we re-implemented this technique and tune model hyper-parameters to correctly detect waypoints for the arrival traffic into the San Francisco bay area. We will compute the complexity measure over a one-year period using our proposed technique as well as the baseline. Our validation will be based on each technique’s ability to detect a set of undesirable outcomes (e.g., go-arounds, holding patterns, average time in the airspace, etc.). Since our current complexity metric is derived from the offset from the direct reference path, it’s important to understand what causes these offsets. In many of the flights with high offset distance, flights performing holding patterns and S turns can be observed. These maneuvering tactics are utilized to add distance between the aircraft and the destination runway to prevent multiple flights from having conflicting arrival times. In order to predict a rise in complexity (or the precursor to complexity), it’s necessary to be able to identify these potential conflicts (which in turn, result in higher offsets). To do this, we define a “representative flight” for each STAR route and runway pair. This flight is approximately the path the flight would take if there was a clear path with no other flights in the airspace — including the time remaining to the airport. We first identify the flights for a given STAR runway pair using the offset to the reference path distributions that fall between the 44-55 percentiles. This yields the flights that conform to the most normal mode of operation. Each of these flights is partitioned based on the percent complete from the entry point into the maneuvering areas from 0\% – 100\% complete. Then for each percent “bin”, we take the median value of the flight’s latitude/longitude coordinates, airspeed, and (non causal) time remaining to the airport to construct a lookup table for each percent complete bin on a given route. As a flight enters the maneuvering area, we can find the estimated arrival time of a flight to the airport by finding the closest point to the representative path’s percent complete bin (relative to the flight’s current position at any snapshot in the airspace) and therefore retrieve the corresponding remaining time left on the “representative path”. We assume that the flight will follow the representative path to completion when deriving these estimates. We can then compare these estimated arrival times against other flights for the same snapshot in time to identify potential conflicts. If more flights are estimated to arrive within a tolerance window than there are runways available, then we have a potential conflict. We can use this derived measure along with other factors expected to add disruption to the operation such as weather and runway configuration changes as an input to machine learning tools to detect precursors that increases in our complexity measure. This novel method will assist in uncovering insights into the contributing factors that lead to increased complexity that may allow for in-time responses to avoid reaching a high complexity state in the airspace.

complexity↗

User's guide to the Mission Analysis Evaluation and Space Trajectory Operations program (MAESTRO)

The MAESTRO system is a mission analysis tool designed to present to the user information necessary to make the various decisions required in the design and execution of a spaceflight mission. The system was designed so that it can be used in both the pre-launch mission planning phase of a mission and during the flight as an in-flight decision making tool. A description of each of the following modes is presented: (1) trajectory propagation mode; (2) retro-fire determination mode; (3) midcourse analysis determination mode; (4) Monte Carlo mode; (5) verification mode; (6) orbit stability mode; and (7) post injection trim mode. A description of the inputs necessary to run the program mode is given along with a sample case.

Lutzky, D.↗

Integration of an Autopilot for a Micro Air Vehicle

Two autopilots providing autonomous flight capabilities are presented herein. The first is the Pico-Pilot, demonstrated for the 12-inch size class of micro air vehicles. The second is the MicroPilot MP2028(sup g), where its integration into a 36-inch Zagi airframe (tailless, elevons only configuration) is investigated and is the main focus of the report. Analytical methods, which include the use of the Advanced Aircraft Analysis software from DARCorp, were used to determine the stability and control derivatives, which were then validated through wind tunnel experiments. From the aerodynamic data, the linear, perturbed equations of motion from steady-state flight conditions may be cast in terms of these derivatives. Using these linear equations, transfer functions for the control and navigation systems were developed and feedback control laws based on Proportional, Integral, and Derivative (PID) control design were developed to control the aircraft. The PID gains may then be programmed into the autopilot software and uploaded to the microprocessor of the autopilot. The Pico-Pilot system was flight tested and shown to be successful in navigating a 12-inch MAV through a course defined by a number of waypoints with a high degree of accuracy, and in 20 mph winds. The system, though, showed problems with control authority in the roll and pitch motion of the aircraft: causing oscillations in these directions, but the aircraft maintained its heading while following the prescribed course. Flight tests were performed in remote control mode to evaluate handling, adjust trim, and test data logging for the Zagi with integrated MP2028(sup g). Ground testing was performed to test GPS acquisition, data logging, and control response in autonomous mode. Technical difficulties and integration limitations with the autopilot prevented fully autonomous flight from taking place, but the integration methodologies developed for this autopilot are, in general, applicable for unmanned air vehicles within the 36-inch size class or larger that use a PID control based autopilot.

Platanitis, George↗

Space shuttle horizontal flight test plan

A horizontal takeoff flight test concept for testing space shuttle vehicles is presented. The guidelines used in planning and support requirements for the flight tests are developed. Details of the test program are provided. The instrumentation requirements are defined. The limitations imposed by the short flight endurance and restricted maneuvering capability of the shuttle booster/orbiter in the horizontal mode are described. The test program covers the following investigations. (1) stall and lift boundary tests, (2)takeoff and landing tests, (3) level flight speed power tests, (4) longitudinal and laterial directional dynamic stability, and (5) static directional stability.

Mosley, R. L.↗

Task Analytic Models to Guide Analysis and Design: Use of the Operator Function Model to Represent Pilot-Autoflight System Mode Problems

Task-analytic models structure essential information about operator interaction with complex systems, in this case pilot interaction with the autoflight system. Such models serve two purposes: (1) they allow researchers and practitioners to understand pilots' actions; and (2) they provide a compact, computational representation needed to design 'intelligent' aids, e.g., displays, assistants, and training systems. This paper demonstrates the use of the operator function model to trace the process of mode engagements while a pilot is controlling an aircraft via the, autoflight system. The operator function model is a normative and nondeterministic model of how a well-trained, well-motivated operator manages multiple concurrent activities for effective real-time control. For each function, the model links the pilot's actions with the required information. Using the operator function model, this paper describes several mode engagement scenarios. These scenarios were observed and documented during a field study that focused on mode engagements and mode transitions during normal line operations. Data including time, ATC clearances, altitude, system states, and active modes and sub-modes, engagement of modes, were recorded during sixty-six flights. Using these data, seven prototypical mode engagement scenarios were extracted. One scenario details the decision of the crew to disengage a fully automatic mode in favor of a semi-automatic mode, and the consequences of this action. Another describes a mode error involving updating aircraft speed following the engagement of a speed submode. Other scenarios detail mode confusion at various phases of the flight. This analysis uses the operator function model to identify three aspects of mode engagement: (1) the progress of pilot-aircraft-autoflight system interaction; (2) control/display information required to perform mode management activities; and (3) the potential cause(s) of mode confusion. The goal of this paper is twofold: (1) to demonstrate the use of the operator functio model methodology to describe pilot-system interaction while engaging modes And monitoring the system, and (2) to initiate a discussion of how task-analytic models might inform design processes. While the operator function model is only one type of task-analytic representation, the hypothesis of this paper is that some type of task analytic structure is a prerequisite for the design of effective human-automation interaction.

Degani, Asaf↗

Digital command system

The correct processing of the Digital Command System (DCS), which provides a limited real-time means of controlling specific flight program functions, was verified. The ability of the flight program to correctly read and process DCS commands was verified. Tests made by the flight program after reading the contents of the command decoder register to establish the validity of the received data were verified through the following: DCS mode command verification, DCS data command verification, DCS data validation, and DCS error message. The operation of the following DCS commands accepted and processed by the flight program was tested: time base update, navigation update, generalized switch selector, memory dump, terminate, execute generalized maneuver, return to nominal timeline, ECS water control valve logic inhibit, execute maneuver, execute alternate sequence, targeting load, ladder magnitude limit, S-IVB/IU de-orbit, compressed data dump, and remove inhibit on the extraction maneuver.

Source record↗

FRESCO: A Framework for Spacecraft Systems Autonomy

Achieving the science exploration and defense goals of the following decades will require flight systems capable of operations with limited operator contact, system mode changes and retasking based on sensor data, and complex robotic operations. To support these capabilities, increasingly autonomous flight systems are required that can perform dedicated mission functions, e.g. payload targeting and communications, and system-level functions, e.g. planning and goal monitoring. Architecting an autonomous system requires a well-reasoned, self-consistent framework to avoid \textit{ad hoc} design choices that will introduce complexity and risk. The Framework for Robust Execution and Scheduling of Commands On-Board, FRESCO, is the result of lessons learned in developing a software architecture to enable autonomous solar system exploration. FRESCO generalizes this work to offer a modular, software-agnostic approach to developing verifiable architecture for autonomous space systems. FRESCO specifies guiding principles, functions, interfaces, and interactions from which mission-specific autonomous control architectures can be derived. FRESCO is a principled framework relying on explicit, state-based goal definitions, centralized management of state knowledge, clearly separated control boundaries, and hierarchical reasoning. Using components from FRESCO reference architecture, an autonomous decision-making architecture can be designed for spacecraft which can then be mapped to flight software architecture. FRESCO is flexibly defined to enable autonomous control of flight systems built using extensive software and hardware heritage. Finally, FRESCO-derived architectures support a spectrum of operator/spacecraft interactions, ranging from traditional commanding to goal-driven commanding with the ability to change mission goals autonomously. FRESCO has been used in defining the autonomy architectures for the ASTERIA mission and have been demonstrated in laboratory and software simulation for small body rendezvous and in-space servicing missions.

Kolcio, Ksenia↗

In-trail following during profile descents with a cockpit display of traffic information

Four line pilots performed simulator flights of 747s on different air routes in conditions of following other aircraft while maintaining a specified temporal flight interval separation. The flights were made in the heading-select mode of the autopilot, and the pitch wheel or altitude select/hold mode with the throttle on manual. A cockpit display of traffic information (CDTI) on a CRT was presented in front of the throttles. A VOR radial with dotted centerlines and sidebands representing 3 km intervals was displayed, along with scales of distance depending on altitude. Traffic information was updated every four seconds. Simulated flights began at cruise and followed a standard profile descent, and traffic following intervals of 60, 80, 120, and 140 seconds were presented in different trials. Results indicated that a CDTI was sufficient instrumentation for trailing other aircraft, with low error rates up to the point of landing preparations.

Chappell, S. L.↗

Modern digital flight control system design for VTOL aircraft

Methods for and results from the design and evaluation of a digital flight control system (DFCS) for a CH-47B helicopter are presented. The DFCS employed proportional-integral control logic to provide rapid, precise response to automatic or manual guidance commands while following conventional or spiral-descent approach paths. It contained altitude- and velocity-command modes, and it adapted to varying flight conditions through gain scheduling. Extensive use was made of linear systems analysis techniques. The DFCS was designed, using linear-optimal estimation and control theory, and the effects of gain scheduling are assessed by examination of closed-loop eigenvalues and time responses.

Broussard, J. R.↗

An in-flight simulation of VTOL hover control concepts

Results of several parametric ground-based simulations covering a variety of VTOL in-hover control concepts are reviewed. The systems considered are angular acceleration, rate, and attitude control, as well as translational rate control. Since many cues are severely restricted by ground-based simulation (e.g., motion, peripheral vision, and environment), some form of in-flight validation of these results is desired. Such a study has been undertaken utilizing the NASA Ames X-14B VTOL aircraft. This in-flight simulator has been configured with a fly-by-wire capability in the hover mode through an analog-/digital variable stability system. This system permits the implementation of either response-feedback or model-following type of control. A comparison of flight- and ground-based data is shown for the attitude control system with the X-14B being flown in both a tethered hover and a free-flight hover.

Corliss, L. D.↗

Flight evaluation of augmented controls for approach and landing of powered-lift aircraft

Flight experiments were conducted with Ames Research Center's Quiet Short-Haul Research Aircraft to evaluate the influence of highly augmented control modes on the ability of pilots to execute precision instrument flight operations in the terminal area, particularly approaches to and landings on a short runway. The aircraft is a powered-lift, short-takeoff and landing configuration that is equipped with a modern digital fly-by-wire flight control system, a head-up display, and a solar head-down display that make it possible to investigate control concepts and display format and content for full envelope, powered-lift operations. Considerable attention has been devoted in this flight program to assessing flightpath and airspeed command and stabilization modes developed using nonlinear, inverse model-following methods. The primary benefit of this control concept was realized when the pilot was required to execute a complex transition and approach under instrument conditions and in the presence of a wide range of wind and turbulence conditions.

Franklin, J. A.↗

Independent Orbiter Assessment (IOA): Analysis of the displays and controls subsystem

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA approach features a top-down analysis of the hardware to determine failure modes, criticality, and potential critical items. To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. This report documents the independent analysis results corresponding to the Orbiter Displays and Controls (D and C) subsystem hardware. The function of the D and C hardware is to provide the crew with the monitor, command, and control capabilities required for management of all normal and contingency mission and flight operations. The D and C hardware for which failure modes analysis was performed consists of the following: Acceleration Indicator (G-METER); Head Up Display (HUD); Display Driver Unit (DDU); Alpha/Mach Indicator (AMI); Horizontal Situation Indicator (HSI); Attitude Director Indicator (ADI); Propellant Quantity Indicator (PQI); Surface Position Indicator (SPI); Altitude/Vertical Velocity Indicator (AVVI); Caution and Warning Assembly (CWA); Annunciator Control Assembly (ACA); Event Timer (ET); Mission Timer (MT); Interior Lighting; and Exterior Lighting. Each hardware item was evaluated and analyzed for possible failure modes and effects. Criticality was assigned based upon the severity of the effect for each failure mode.

Trahan, W. H.↗