Engineering topics
Publications and source records attributed to Smith, Nancy.
Overview of NASA Integrated Demand Management (IDM) research into synchronized use of strategic and tactical air traffic management systems describes the initial motivation for the research, summary description of key experiments conducted between 2016 and the present, collaboration with outside partners and stakeholders, and the current status of the research.
This presentation provides a summary of August 2017 Newark airport simulation, with focus on impact of varying Trajectory Options Set (TOS) "participation levels" (i.e., the percentage of flights that submit TOSs), as well as the results from March 2018 LaGuardia simulation with Flow Evaluation Team, which focused on benefits to individual carriers of participation. During the study, we demonstrated that both the participating and non-participating airlines benefited when TOSs but that the participating airlines benefited most and the improvement seen by participants was greatest when overall participation was lower.
A series of human-in-the-loop simulation sessions were conducted in the Airspace Operations Laboratory (AOL) to evaluate a new traffic management concept called Integrated Demand Management (IDM). The simulation explored how to address chronic equity, throughput and delay issues associated with New Yorks high-volume airports by operationally integrating three current and NextGen capabilities the Collaborative Trajectory Options Program (CTOP), Time-Based Flow Management (TBFM) and Required Time of Arrival (RTA) in order to better manage traffic demand within the National Air Traffic System. A package of presentation slides was developed to describe the concept, tools, and training materials used in the simulation sessions. The package will be used to outbrief our stakeholders by both presenting orally and disseminating of the materials via email.
Airports with shared runway operations between arrivals and departures can experience severe departure gridlock and delays during a heavy arrival push due to insufficient gaps in the arrival stream for aircraft to depart. The problem is accentuated in situations when a large gap in the arrival spacing has to be created at the last minute due to wake vortex separation requirements. At LaGuardia airport, wake vortex separation problems arise when a heavy jet, such as a B757, departing on Runway 31 needs additional spacing between arrivals on Runway 22. A standard solution for controllers in many airports in situations such as this is to extend the downwind leg of arrival aircraft to create extra space between the arrivals. The question addressed in this paper is how such route extensions would work with terminal scheduling operations, namely (1) the automated Terminal Sequencing and Spacing (TSS) tools and (2) a new scheduling tool which increases the availability of gaps for departure aircraft (Departure Sensitive Arrival Spacing or DSAS). In a simulated LaGuardia airport (LGA) Terminal Radar Approach Control (TRACON) airspace, two new RNAV arrival routes were created along with extensions to these routes. The arrival route from the south had a downwind leg extension near the airport in the final sector. The arrival route from the north had an extension in a feeder sector further from the airport. An exploratory one-hour run with the route extensions was compared to an hour run without the extensions. Topics included in the paper are 1) how the route extensions were developed, 2) a procedure outlining how the aircraft could be scheduled to the extensions and who would do it, and 3) the results of the exploratory run compared to the original run without the extensions. The results indicated that the extended downwind leg route helped to create a B757 departure gap in the middle of a packed arrival stream, resulting in a reduction of 11 minutes in average wait time for the B757s, but at a cost of increased controller self-reported workload from low to moderate.
This paper reviews three Next Generation Air Transportation System (NextGen) based high fidelity air traffic control human-in-the-loop (HITL) simulations, with a focus on the expected requirement of enhanced automated trajectory assessment and modification tools to support future air traffic flow management (ATFM) planning positions. The simulations were conducted at the National Aeronautics and Space Administration (NASA) Ames Research Centers Airspace Operations Laboratory (AOL) in 2009 and 2010. The test airspace for all three simulations assumed the mid-term NextGenEn-Route high altitude environment utilizing high altitude sectors from the Kansas City and Memphis Air Route Traffic Control Centers. Trajectory assessment, modification and coordination decision support tools were developed at the AOL in order to perform future ATFM tasks. Overall tool usage results and user acceptability ratings were collected across three areas of NextGen operatoins to evaluate the tools. In addition to the usefulness and usability feedback, feasibility issues, benefits, and future requirements were also addressed. Overall, the tool sets were rated very useful and usable, and many elements of the tools received high scores and were used frequently and successfully. Tool utilization results in all three HITLs showed both user and system benefits including better airspace throughput, reduced controller workload, and highly effective communication protocols in both full Data Comm and mixed-equipage environments.
A human-in-the-Ioop (HITL) simulation was conducted to assess potential user and system benefits of Flexible Airspace Management (FAM) concept, as well as designing role definitions, procedures, and tools to support the FAM operations in the mid-term High Altitude Airspace (HAA) environment. The study evaluated the benefits and feasibility of flexible airspace reconfiguration in response to traffic overload caused by weather deviations, and compared them to those in a baseline condition without the airspace reconfiguration. The test airspace consisted of either four sectors in one Area of Specialization or seven sectors across two Areas. The test airspace was assumed to be at or above FL340 and fully equipped Vvith data communications (Data Comm). Other assumptions were consistent with those of the HAA concept. Overall, results showed that FAM operations with multiple Traffic Management Coordinators, Area Supervisors, and controllers worked remarkably well. The results showed both user and system benefits, some of which include the increased throughput, decreased flight distance, more manageable sector loads, and better utilized airspace. Also, the roles, procedures, airspace designs, and tools were all very well received. Airspace configuration options that resulted from a combination of algorithm-generated airspace configurations with manual modifications were well acceptec and posed little difficuIty and/or workload during airspace reconfiguration process. The results suggest a positive impact of FAM operations in HAA. Further investigation would be needed to evaluate if the benefits and feasibility would extend in either non-HAA or mixed equipage environment.
A human-in-the-loop (HITL) simulation was conducted in May 2010 to determine the feasibility and value 01 conducting multi-sector planning (MSP) operations in a mixed equipage environment. Aircraft were categorized as equipped or unequipped based on the presence or absence of an air-ground data communications (Data Comm) capability for receiving auto-loadable clearances and transfer of communication messages from the air navigation service provider (ANSP). The purpose of the study was to determine the feasibility and possible benefits of introducing multi-sector planning in a mixed equipage context, or whether Data Comm equipage was required for MSP operations. Each test scenario presented one of three different equipage levels to the controllers (10%, 50% or 90% equipped aircraft), so that the operational impact of different equipage levels could be observed. Operational feasibility assessment addressed two related questions: (1) are MSP operations feasible for unequipped aircraft, and (2) are they feasible in a mixed equipage context. Similarly, two categories of potential benefits were explored: (1) system performance improvements (e.g., throughput, workload) associated with MSP at different equipage levels, and (2) the possibility of providing differential service for equipage through MSP operations. Tool requirements (for both planning and controller stations), as well as planning and coordination procedures - within facility (traffic management unit/operational area) and within sector (R-Side/D-Side) - were two other topics addressed in the study. Overall, results suggested that MSP operations were feasible in a mixed equipage environment and that the tools were effective with both equipped and unequipped aircraft. Using the MSP tools, traffic management coordinators were able to manage controller task load, effectively balancing throughput with complexity and controller task load at each of the three equipage levels tested.
An exploratory human-in-the-loop study was conducted to better understand the impact of Dynamic Airspace Configuration (DAC) on air traffic controllers. To do so, a range of three progressively more aggressive algorithmic approaches to sectorizations were chosen. Sectorizations from these algorithms were used to test and quantify the range of impact on the controller and traffic. Results show that traffic count was more equitably distributed between the four test sectors and duration of counts over MAP were progressively lower as the magnitude of boundary change increased. However, taskload and workload were also shown to increase with the increase in aggressiveness and acceptability of the boundary changes decreased. Overall, simulated operations of the DAC concept did not appear to compromise safety. Feedback from the participants highlighted the importance of limiting some aspects of boundary changes such as amount of volume gained or lost and the extent of change relative to the initial airspace design.
This study used a human-in-the-loop simulation to examine the feasibility of mixed equipage operations in an automated separation assurance environment under higher traffic densities. The study involved two aircraft equipage alternatives with and without data link and four traffic conditions. In all traffic conditions the unequipped traffic count was increased linearly throughout the scenario from approximately 5 to 20 aircraft. Condition One consisted solely of this unequipped traffic, while the remaining three conditions also included a constant number of equipped aircraft operating within the same airspace: 15 equipped aircraft in condition two, 30 in condition three, and 45 in condition four. If traffic load became excessive during any run, participants were instructed to refuse sector entry to inbound unequipped aircraft until sector load became manageable. Results showed a progressively higher number of unequipped aircraft turned away under the second, third, and fourth scenario conditions. Controller workload also increased progressively. Participants rated the mixed operations concept as acceptable, with some qualifications about procedures and information displays. These results showed that mixed operations might be feasible in the same airspace, if unequipped aircraft count is held to a workable level. This level will decrease with increasing complexity. The results imply that integrated airspace configuration is feasible to a limit. The results also indicate that the conflict detection and resolution automation, equipage, and traffic density are important factors that will need to be considered for airspace configuration.
This study used a human-in-the-loop simulation to examine the feasibility of mixed equipage operations in an automated separation assurance environment under higher traffic densities. The study involved two aircraft equipage alternatives - with and without data link- and four traffic conditions. In all traffic conditions the unequipped traffic count was increased linearly throughout the scenario from approximately 5 to 20 aircraft. Condition One consisted solely of this unequipped traffic, while the remaining three conditions also included a constant number of equipped aircraft operating within the same airspace: 15 equipped aircraft in condition two, 30 in condition three, and 45 in condition four. If traffic load became excessive during any run, participants were instructed to refuse sector entry to inbound unequipped aircraft until sector load became manageable. Results showed a progressively higher number of unequipped aircraft turned away under the second, third, and fourth scenario conditions. Controller workload also increased progressively. Participants rated the mixed operations concept as acceptable, with some qualifications about procedures and information displays. These results showed that mixed operations might be feasible in the same airspace, if unequipped aircraft count is held to a workable level. This level will decrease with increasing complexity. The results imply that integrated airspace configuration is feasible to a limit. The results also indicate that the conflict detection and resolution automation, equipage, and traffic density are important factors that will need to be considered for airspace configuration.
In order to meet the anticipated future demand for air travel, the National Aeronautics and Space Administration (NASA) is investigating a new concept of operations known as Distributed Air-Ground Traffic Management (DAG-TM). Under the En Route Free Maneuvering component of DAG-TM, appropriately equipped autonomous aircraft self separate from other autonomous aircraft and from managed aircraft that continue to fly under today s Instrument Flight Rules (IFR). Controllers provide separation services between IFR aircraft and assign traffic flow management constraints to all aircraft. To address concept feasibility issues pertaining to integrated air/ground operations at various traffic levels, NASA Ames and Langley Research Centers conducted a joint human-in-the-loop experiment. Professional airline pilots and air traffic controllers flew a total of 16 scenarios under four conditions: mixed autonomous/managed operations at three traffic levels and a baseline all-managed condition at the lowest traffic level. These scenarios included en route flights and descents to a terminal area meter fix in airspace modeled after the Dallas Ft. Worth area. Pilots of autonomous aircraft met controller assigned meter fix constraints with high success. Separation violations by subject pilots did not appear to vary with traffic level and were mainly attributable to software errors and procedural lapses. Controller workload was lower for mixed flight conditions, even at higher traffic levels. Pilot workload was deemed acceptable under all conditions. Controllers raised several safety concerns, most of which pertained to the occurrence of near-term conflicts between autonomous and managed aircraft. These issues are being addressed through better compatibility between air and ground systems and refinements to air and ground procedures.
Free-flight is considered to play a major role in the future air traffic environment. Studies are underway addressing different concepts for free-flight and self separation in enroute airspace. One common opinion throughout the different concepts is that the airspace surrounding major airports, the Terminal Radar Approach CONtrol (TRACON) will not be a free flight area. This means that aircraft in this area are completely controlled by air traffic controllers, who may be supported by decision support system like the Center TRACON Automation System (CTAS). How the transition from the free-flight area (enroute airspace) to the terminal area will take place is currently unclear, This paper describes a study at NASA Ames Research Center addressing the perspective of air traffic controllers handling user-preferred (FMS-optimized) descent trajectories during this transition phase. Two major issues in enabling user preferred descents from the controllers' point of view are predictability and controllability. In an environment in which the air traffic services are highly responsive to user preferences controllers need to know, where and when aircraft will change their trajectory and they need to have appropriate means and procedures at hand to control the aircraft according to the overall traffic situation. Predictability shall be enhanced by: 1) Indicating airspace corridors for descending aircraft; 2) Modify the controller interface; 3) Using a ground based conflict probe; 4) Making use of downlinked intent information from the aircraft FMS; and 5) Requiring to fly pilots on user preferred trajectories coupled to the FMS in the lateral and vertical axis. Additional controllability shall be achieved by supporting the controllers with CTAS center tools: 1) Traffic Management Advisor (TMA); 2) Conflict Probing and Trial Planning (CP/TP); and 3) Enroute Descent Advisor (E/DA). The paper describes the general concept and the modifications to current systems required to enable the concept. It explains the experiment design and discusses the results with regard to controller acceptability and usability. Potential benefits and drawbacks of the overall concept are indicated.
Current Flight Management Systems (FMS) do a good job of constructing and flying an optimal trajectory for a single aircraft. Unfortunately, flight crews are often unable to fly these FMS routes during arrivals at busy airports. The Center TRACON Automation System (CTAS) has been designed to aid Center and TRACON (Terminal Radar Approach Control) controllers in assigning runways, sequencing and vectoring all classes of aircraft. CTAS bases its advisories on trajectory predictions for arriving aircraft using algorithms very similar to those in airborne FMS systems. This paper presents near and far term operational concepts for how a ground ATM (air traffic management) automation system like CTAS could work more effectively with the airborne automation in FMS equipped aircraft. The concepts for a more compatible air-ground system include: 1) a common route databases for both CTAS and FMS; 2) datalink to downlink information on aircraft weight, final approach speed and trajectory intent and to uplink wind information; 3) new FMS functions to allow flight crews to easily update their FMS trajectory to match the trajectory suggested by the ground automation with voice clearances, and 4) in the far term, datalink to downlink user preferred trajectories and to uplink trajectory clearances in the terminal area. The paper analyses some of the human factors issues that may result in allowing aircraft to fly FMS routes during enroute descent and in the terminal area. A series of linked human in the loop flight deck and air traffic control simulations and a field test with the NASA 757 are being conducted at NASA's Ames and Langley Research Centers to address these issues and to evaluate the operational feasibility of these approaches to more efficient flight and increased airport throughput.
The recent certification and implementation of the Future Air Navigation System (FANS- 1) was based on the benefits of reduced separation minima, ability to optimize flight plans enroute, and the prompt transmission and reception of messages between oceanic controllers and 747-400 aircraft transiting the Pacific. In addition, FANS was intended to supersede High Frequency (HF) radio which has been the staple, yet problematic, long distance communication link for years. However, in the three initial years of operation, FANS has revealed its own unique operational issues. Although some technical and engineering problems have been studied and addressed, little research has been conducted on human factors issues associated with the use of FANS on the flight deck. This lack of prior data on the operational use of FANS prompted a joint NASA/Aviation Safety Reporting System (ASRS) inquiry into FANS datalink. In addition, two foreign air carriers and their respective safety agencies were recruited to participate. This international FANS research effort consisting of three aviation safety agencies and three international commercial air-carriers has provided a unique opportunity for conducting human factors research in an operational environment. An ASRS 'callback' format was chosen for the study as a practical and viable method for capturing FANS events on the flight deck. Initially, 747-400 pilots were encouraged to submit reports to their respective safety agencies if they had experienced any positive or negative incidents with the use of FANS. Upon receipt of a report, it was evaluated and if deemed pertinent to the study, a telephone interview or 'callback' was conducted on the FANS incident to elicit further details, capture the key events, and gather contextual information. Once the operational data collection phase was completed, the reports and interviews were analyzed with two purposes in mind: primarily to identify and address problematic human factors issues with current FANS technology, and, secondarily, to provide 'lessons learned' for future datalink systems and implementation.
A survey was used to collect data from Boeing 747-400 pilots who fly with three international carriers about their operational experience using FANS-1 CPDLC (controller-pilot datalink communication) for oceanic communication with air traffic control (ATC). The survey provides data characterizing the operators' experiences performing all routine datalink communication tasks, with the goal of determining how well the FANS-1 CPDLC system supports task performance, the problems flight crews experience when using the system, and the possible operational consequences of those problems. Survey questions were developed from an analysis of activities performed by pilots when using FANS-1 CPDLC. Seven routine tasks were identified: (1) preflight initialization; (2) ATC facility logon; (3) monitoring ATC facility handoffs; (4) monitoring integrity of FANS- 1 CPDLC connection; (5) responding to ATC communications; (6) sending ATC requests; and (7) sending ATC position reports. A decomposition of each task described its information requirements, task timing requirements, user interface actions, company procedures and documentation, and the available cues and feedback provided by the interface. This analysis was used to determine where the system might provide poor support for task performance, and survey questions were developed to determine whether operator experience reflected problems in these areas.
Substantial increases in the volume of air traffic in the National Airspace System (NAS) are forecast for the next decade, with the number of passengers travelling on U.S. airlines expected to increase by as much as 60%. This increased demand on system capacity will be accompanied by increases in traffic complexity as air traffic service providers routinely accommodate user preferred routing requests. Changes to the NAS to meet these new demands are currently underway, including development of new decision support tools to aid controllers in monitoring and managing air traffic, and increased air-to-air and air-to-ground information exchange. Changes in roles and responsibilities of pilots and controllers in flight path management will accompany these changes in traffic patterns and information technology, however the ultimate responsibility for maintaining aircraft separation will remain with the air traffic controller. A thorough understanding of the methods controllers use to manage air traffic will help ensure that changes to the NAS are implemented in a way that maintains the controller's ability to separate aircraft as the system evolves. This presentation describes the strategies controllers use today to manage arrival traffic in its descent from cruise altitude to the Terminal Radar Approach Control (TRACON) boundary. Factors that increase the complexity of this task include the presence of overflight traffic, varying aircraft performance characteristics, winds aloft, ground speed variations with altitude, the need to merge arrival traffic into a single stream, and, when arrival traffic exceeds airport runway capacity, the added task of metering flow into the TRACON. Because of the limited information available to controllers to manage arrival traffic, their strategies are often driven by the need to reduce the task's complexity, which can result in de-optimized flight paths for individual aircraft (e.g., sub-optimal descent or speed profiles). Understanding these strategies and the cognitive demands that drive them will support a safe transition to a NAS that relies on enhanced technologies. In addition, it could enable system developers to identify opportunities for new automation-based procedures or information displays that could reduce the controller's workload and increase operational efficiency.
A task-analytic approach was used to evaluate the results from an experiment comparing two training methods for the "Precision Descent," a cockpit procedure designed to complement a new, computer-based air traffic control advisory system by allowing air traffic controllers to assign precise descent trajectories to aircraft. A task model was developed for the procedure using a methodology that represents four different categories of task-related knowledge: (1) ability to determine current flight goals; (2) ability to assess the current flight situation relative to those goals; (3) operational knowledge about flight-related tasks; and (4) knowledge about task selection. This model showed what knowledge experienced pilots already possessed, and how that knowledge was supplemented by training material provided in the two training conditions. All flight crews were given a "Precision Descent Chart" that explained the procedure's clearances and compliance requirements. This information enabled pilots to establish appropriate flight goals for the descent, and to monitor their compliance with those goals. In addition to this chart, half of the crews received a "Precision Descent Bulletin" containing technique recommendations for performing procedure-related tasks. The Bulletin's recommendations supported pilots in task selection and helped clarify the procedure's compliance requirements. Eight type-rated flight crews flew eight Precision Descents in a Boeing 747-400 simulator, with four crews in each of the two training conditions. Both conditions (Chart and Chart-with-Bulletin) relied exclusively on the use of those documents to introduce the procedure. No performance feedback was provided during the experiment. Preliminary result show better procedure compliance and higher acceptability ratings from flight crews in the Chart-with-Bulletin condition. These crews performed flight-related tasks less efficiently, however, using the simpler but less efficient methods suggested in the Bulletin. When a more efficient method was recognized, these crews tended to use the more efficient method in addition to the Bulletin's recommendation, instead of replacing it.
An experiment was conducted to evaluate flight crew performance of the "Precision Descent," a new cockpit procedure designed to support the Descent Advisor (DA), one of the components in a new air traffic control advisory system called the "Center-TRACON Automation System" (CTAS). The DA predicts when aircraft will reach a specific waypoint on the arrival route, and presents controllers with clearance advisories designed to improve the sequencing of arriving aircraft. The effectiveness of the DA depends on the aircraft's descent trajectory: where it begins descent, what speed it maintains, how fast and at what altitude it crosses the bottom-of-descent waypoint. The Precision Descent allows controllers to assign these descent parameters to the flight crew. A Field Evaluation of the DA was conducted in Denver in 1995. Three separate clearances using standard ATC phraseology were used to support the cockpit descent procedure during this evaluation. The number and length of these clearances caused problems for both controllers and flight crews, causing readback errors, repeat requests and procedure misunderstandings. These observations led to a focus group meeting in which controller and pilot participants in the 1995 FE assisted in the redesign of the procedure. The Precision Descent eliminates one clearance used in the earlier study, and greatly reduces the length of the remaining clearances. This was accomplished by using non-standard clearance phraseology that relies on a published procedure chart for correct interpretation. Eight type-rated flight crews flew eight Precision Descents in a Boeing 747-400 simulator. No training was provided: crews received either a procedure chart or a procedure chart with a flight manual bulletin describing procedure techniques. Video and digital data were recorded for each descent. Preliminary results indicate that moving information from the verbal clearance to the chart was successful: the shorter clearances and the procedure's default crossing restriction were understood, and procedure compliance of 81% was observed across all descents on six independent compliance measures. Some readback errors and procedure misunderstandings were still observed, however; particularly when descent clearances deviated from the normative procedure.