SEARCH · Search NASA

Results for “Workload”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 703 records · Page 39

All sources NASA NTRS DOE OSTI

NASA NTRS2012

I/O Performance Characterization of Lustre and NASA Applications on Pleiades

In this paper we study the performance of the Lustre file system using five scientific and engineering applications representative of NASA workload on large-scale supercomputing systems such as NASA s Pleiades. In order to facilitate the collection of Lustre performance metrics, we have developed a software tool that exports a wide variety of client and server-side metrics using SGI's Performance Co-Pilot (PCP), and generates a human readable report on key metrics at the end of a batch job. These performance metrics are (a) amount of data read and written, (b) number of files opened and closed, and (c) remote procedure call (RPC) size distribution (4 KB to 1024 KB, in powers of 2) for I/O operations. RPC size distribution measures the efficiency of the Lustre client and can pinpoint problems such as small write sizes, disk fragmentation, etc. These extracted statistics are useful in determining the I/O pattern of the application and can assist in identifying possible improvements for users applications. Information on the number of file operations enables a scientist to optimize the I/O performance of their applications. Amount of I/O data helps users choose the optimal stripe size and stripe count to enhance I/O performance. In this paper, we demonstrate the usefulness of this tool on Pleiades for five production quality NASA scientific and engineering applications. We compare the latency of read and write operations under Lustre to that with NFS by tracing system calls and signals. We also investigate the read and write policies and study the effect of page cache size on I/O operations. We examine the performance impact of Lustre stripe size and stripe count along with performance evaluation of file per process and single shared file accessed by all the processes for NASA workload using parameterized IOR benchmark.

Saini, Subhash↗

NASA NTRS2012

The Human Dimension of Closing the Training Gap for Fifth-Generation Fighters

Based on a review of the recent technical literature there is little question that a serious training gap exists for fifth-generation fighters, primarily arising from the need to provide their own red-air. There are several methods for reducing this gap, including injecting virtual and constructive threats into the live cockpit. This live-virtual-constructive (LVC) training approach provides a cost effective means for addressing training needs but faces several challenges. Technical challenges include data links and information assurance. A more serious challenge may be the human factors dimension of representing virtual and constructive entities in the cockpit while ensuring safety-of-flight. This also needs to happen without increasing pilot workload. This paper discusses the methods Rockwell Collins and the University of Iowa's Operator Performance Lab use to assess pilot workload and training fidelity measures in an LVC training environment and the research we are conducting in safety-of-flight requirements of integrated LVC symbology.

Hoke, Jaclyn↗

NASA NTRS2013

Experiment Description and Results for Arrival Operations Using Interval Management with Spacing to Parallel Dependent Runways (IMSPiDR)

The predicted increase in the number of commercial aircraft operations creates a need for improved operational efficiency. Two areas believed to offer increases in aircraft efficiency are optimized profile descents and dependent parallel runway operations. Using Flight deck Interval Management (FIM) software and procedures during these operations, flight crews can achieve by the runway threshold an interval assigned by air traffic control (ATC) behind the preceding aircraft that maximizes runway throughput while minimizing additional fuel consumption and pilot workload. This document describes an experiment where 24 pilots flew arrivals into the Dallas Fort-Worth terminal environment using one of three simulators at NASA?s Langley Research Center. Results indicate that pilots delivered their aircraft to the runway threshold within +/- 3.5 seconds of their assigned time interval, and reported low workload levels. In general, pilots found the FIM concept, procedures, speeds, and interface acceptable. Analysis of the time error and FIM speed changes as a function of arrival stream position suggest the spacing algorithm generates stable behavior while in the presence of continuous (wind) or impulse (offset) error. Concerns reported included multiple speed changes within a short time period, and an airspeed increase followed shortly by an airspeed decrease.

Baxley, Brian T.↗

NASA NTRS2013

Evolution of International Space Station Program Safety Review Processes and Tools

The International Space Station Program at NASA is constantly seeking to improve the processes and systems that support safe space operations. To that end, the ISS Program decided to upgrade their Safety and Hazard data systems with 3 goals: make safety and hazard data more accessible; better support the interconnection of different types of safety data; and increase the efficiency (and compliance) of safety-related processes. These goals are accomplished by moving data into a web-based structured data system that includes strong process support and supports integration with other information systems. Along with the data systems, ISS is evolving its submission requirements and safety process requirements to support the improved model. In contrast to existing operations (where paper processes and electronic file repositories are used for safety data management) the web-based solution provides the program with dramatically faster access to records, the ability to search for and reference specific data within records, reduced workload for hazard updates and approval, and process support including digital signatures and controlled record workflow. In addition, integration with other key data systems provides assistance with assessments of flight readiness, more efficient review and approval of operational controls and better tracking of international safety certifications. This approach will also provide new opportunities to streamline the sharing of data with ISS international partners while maintaining compliance with applicable laws and respecting restrictions on proprietary data. One goal of this paper is to outline the approach taken by the ISS Progrm to determine requirements for the new system and to devise a practical and efficient implementation strategy. From conception through implementation, ISS and NASA partners utilized a user-centered software development approach focused on user research and iterative design methods. The user-centered approach used on the new ISS hazard system utilized focused user research and iterative design methods employed by the Human Computer Interaction Group at NASA Ames Research Center. Particularly, the approach emphasized the reduction of workload associated with document and data management activities so more resources can be allocated to the operational use of data in problem solving, safety analysis, and recurrence control. The methods and techniques used to understand existing processes and systems, to recognize opportunities for improvement, and to design and review improvements are described with the intent that similar techniques can be employed elsewhere in safety operations. A second goal of this paper is to provide and overview of the web-based data system implemented by ISS. The software selected for the ISS hazard systemMission Assurance System (MAS)is a NASA-customized vairant of the open source software project Bugzilla. The origin and history of MAS as a NASA software project and the rationale for (and advantages of) using open-source software are documented elsewhere (Green, et al., 2009).

Ratterman, Christian D.↗

NASA NTRS2013

Spot and Runway Departure Advisor

The Spot and Runway Departure Advisor (SARDA) is a research prototype of a decision support tool for ATC tower controllers to assist in manging and controlling traffic on the surface of an airport. SARDA employs a scheduler to generate an optimal runway schedule and gate push-back - spot release sequence and schedule that improves efficiency of surface operations. The advisories for ATC tower controllers are displayed on an Electronic Flight Strip (EFS) system. The human-in-the-loop simulation of the SARDA tool was conducted for east operations of Dallas-Ft. Worth International Airport (DFW) to evaluate performance of the SARDA tool and human factors, such as situational awareness and workload. The results indicates noticeable taxi delay reduction and fuel savings by using the SARDA tool. Reduction in controller workload were also observed throughout the scenario runs. The future plan includes modeling and simulation of the ramp operations of the Charlotte International Airport, and develop a decision support tool for the ramp controllers.

decision support tool↗

NASA NTRS2013

NextGen Operations in a Simulated NY Area Airspace

A human-in-the-loop simulation conducted in the Airspace Operations Laboratory (AOL) at NASA Ames Research Center explored the feasibility of a Next Generation Air Transportation System (NextGen) solution to address airspace and airport capacity limitations in and around the New York metropolitan area. A week-long study explored the feasibility of a new Optimal Profile Descent (OPD) arrival into the airspace as well as a novel application of a Terminal Area Precision Scheduling and Spacing (TAPSS) enhancement to the Traffic Management Advisor (TMA) arrival scheduling tool to coordinate high volume arrival traffic to intersecting runways. In the simulation, four en route sector controllers and four terminal radar approach control (TRACON) controllers managed traffic inbound to Newark International Airport's primary runway, 22L, and its intersecting overflow runway, 11. TAPSS was used to generate independent arrival schedules for each runway and a traffic management coordinator participant adjusted the arrival schedule for each runway 11 aircraft to follow one of the 22L aircraft. TAPSS also provided controller-managed spacing tools (slot markers with speed advisories and timelines) to assist the TRACON controllers in managing the arrivals that were descending on OPDs. Results showed that the tools significantly decreased the occurrence of runway violations (potential go-arounds) when compared with a Baseline condition with no tools. Further, the combined use of the tools with the new OPD produced a peak arrival rate of over 65 aircraft per hour using instrument flight rules (IFR), exceeding the current maximum arrival rate at Newark Liberty International Airport (EWR) of 52 per hour under visual flight rules (VFR). Although the participants rated the workload as relatively low and acceptable both with and without the tools, they rated the tools as reducing their workload further. Safety and coordination were rated by most participants as acceptable in both conditions, although the TRACON Runway Coordinator (TRC) rated neither as acceptable in the Baseline condition. Regarding the role of the TRC, the two TRACON controllers handling the 11 arrivals indicated that the TRC was very much needed in the Baseline condition without tools, but not needed in the condition with tools. This indicates that the tools were providing much of the sequencing and spacing information that the TRC had supplied in the Baseline condition.

NextGen↗

NASA NTRS2014

Unmanned Aircraft System (UAS) Delegation of Separation in NextGen Airspace

The purpose of this study was to determine the feasibility of unmanned aircraft systems (UAS) performing delegated separation in the national airspace system (NAS). Delegated separation is the transfer of responsibility for maintaining separation between aircraft or vehicles from air navigation service providers to the relevant pilot or flight operator. The effects of delegated separation and traffic display information level were collected through performance, workload, and situation awareness measures. The results of this study show benefits related to the use of conflict detection alerts being shown on the UAS operator's cockpit situation display (CSD), and to the use of full delegation. Overall, changing the level of separation responsibility and adding conflict detection alerts on the CSD was not found to have an adverse effect on performance as shown by the low amounts of losses of separation. The use of conflict detection alerts on the CSD and full delegation responsibilities given to the UAS operator were found to create significantly reduced workload, significantly increased situation awareness and significantly easier communications between the UAS operator and air traffic controller without significantly increasing the amount of losses of separation.

NextGen↗

NASA NTRS2015

Bayesian Safety Risk Modeling of Human-Flightdeck Automation Interaction

Usage of automatic systems in airliners has increased fuel efficiency, added extra capabilities, enhanced safety and reliability, as well as provide improved passenger comfort since its introduction in the late 80's. However, original automation benefits, including reduced flight crew workload, human errors or training requirements, were not achieved as originally expected. Instead, automation introduced new failure modes, redistributed, and sometimes increased workload, brought in new cognitive and attention demands, and increased training requirements. Modern airliners have numerous flight modes, providing more flexibility (and inherently more complexity) to the flight crew. However, the price to pay for the increased flexibility is the need for increased mode awareness, as well as the need to supervise, understand, and predict automated system behavior. Also, over-reliance on automation is linked to manual flight skill degradation and complacency in commercial pilots. As a result, recent accidents involving human errors are often caused by the interactions between humans and the automated systems (e.g., the breakdown in man-machine coordination), deteriorated manual flying skills, and/or loss of situational awareness due to heavy dependence on automated systems. This paper describes the development of the increased complexity and reliance on automation baseline model, named FLAP for FLightdeck Automation Problems. The model development process starts with a comprehensive literature review followed by the construction of a framework comprised of high-level causal factors leading to an automation-related flight anomaly. The framework was then converted into a Bayesian Belief Network (BBN) using the Hugin Software v7.8. The effects of automation on flight crew are incorporated into the model, including flight skill degradation, increased cognitive demand and training requirements along with their interactions. Besides flight crew deficiencies, automation system failures and anomalies of avionic systems are also incorporated. The resultant model helps simulate the emergence of automation-related issues in today's modern airliners from a top-down, generalized approach, which serves as a platform to evaluate NASA developed technologies

Ancel, Ersin↗

NASA NTRS2016

Characterization of Carbon Dioxide Washout Measurement Techniques in the Mark-III Space Suit

It is essential to provide adequate carbon dioxide (CO2) washout in a space suit to reduce the risks associated with manned operations in space suits. Symptoms of elevated CO2 levels range from reduced cognitive performance and headache to unconsciousness and death at high levels of CO2. Because of this, NASA imposes limits on inspired CO2 levels for space suits when they are used in space and for ground testing. Testing and/or analysis must be performed to verify that a space suit meets CO2 washout requirements. Testing for developmental space suits has traditionally used an oronasal mask that collects CO2 samples at the left and rights sides of the mouth. Testing with this mask resulted in artificially elevated CO2 concentration measurements, which is most likely due to the dead space volume at the front of the mask. The mask also extends outward and into the supply gas stream, which may disrupt the washout effect of the suit supply gas. To mitigate these problems, a nasal cannula was investigated as a method for measuring inspired CO2 based on the assumptions that it is low profile and would not interfere with the designed suit gas flow path, and it has reduced dead space. This test series compared the performance of a nasal cannula to the oronasal mask in the Mark III space suit. Inspired CO2 levels were measured with subjects at rest and at metabolic workloads of 1000, 2000, and 3000 BTU/hr. Workloads were achieved by use of an arm ergometer or treadmill. Test points were conducted at air flow rates of 2, 4, and 6 actual cubic feet per minute, with a suit pressure of 4.3 psid. Results from this test series will evaluate the accuracy and repeatability across subjects of the nasal cannula collection method, which will provide rationale for using a nasal cannula as the new method for measuring inspired CO2 in a space suit. Proper characterization of sampling methods and of suit CO2 washout capability will better inform requirements definition and verification techniques for future CO2 washout limits in space suits

Meginnis, I↗

NASA NTRS2015

Flight Deck Interval Management Avionics: Eye-Tracking Analysis

Interval Management (IM) is one NexGen method for achieving airspace efficiencies. In order to initiate IM procedures, Air Traffic Control provides an IM clearance to the IM aircraft's pilots that indicates an intended spacing from another aircraft (the target to follow - or TTF) and the point at which this should be achieved. Pilots enter the clearance in the flight deck IM (FIM) system; and once the TTF's Automatic Dependent Surveillance-Broadcast signal is available, the FIM algorithm generates target speeds to meet that IM goal. This study examined four Avionics Conditions (defined by the instrumentation and location presenting FIM information) and three Notification Methods (defined by the visual and aural alerts that notified pilots to IM-related events). Current commercial pilots flew descents into Dallas/Fort-Worth in a high-fidelity commercial flight deck simulation environment with realistic traffic and communications. All 12 crews experienced each Avionics Condition, where order was counterbalanced over crews. Each crew used only one of the three Notification Methods. This paper presents results from eye tracking data collected from both pilots, including: normalized number of samples falling within FIM displays, normalized heads-up time, noticing time, dwell time on first FIM display look after a new speed, a workload-related metric, and a measure comparing the scan paths of pilot flying and pilot monitoring; and discusses these in the context of other objective (vertical and speed profile deviations, response time to dial in commanded speeds, out-of-speed-conformance and reminder indications) and subjective measures (workload, situation awareness, usability, and operational acceptability).

Latorella, Kara↗

NASA NTRS2015

Scheduling and Delivering Aircraft to Departure Fixes in the NY Metroplex with Controller-Managed Spacing Tools

In this paper, successful Time-Based Flow Management (TBFM) scheduling systems for arrivals are considered and adapted to apply to departures. We present a concept of operations that integrates Controller-Managed Spacing tools for departures (CMS-D) with existing tactical departure scheduling tools to coordinate demand at departure fixes in a metroplex environment. We tested our concept in a Human-in-the-Loop simulation and compared the effect of two scheduling conditions: 1) "Departure Scheduling" consisting of an emulation of the Integrated Departure and Arrival Capability (IDAC) where Towers and a Planner (Traffic Management Coordinator at the appropriate facility) coordinate aircraft scheduled takeoff times to departure fixes; and 2) "Arrival Sensitive Departure Scheduling" where, in addition, the Tower and Planner also consider arrival Scheduled Time of Arrivals (STAs) at the airport's dependent runway. Results indicate little difference between the two scheduling conditions, but a large difference between the No Tools and the two scheduling conditions with CMS-D tools. The scheduling/CMS-D tools conditions markedly reduced heading, speed clearances, and workload for controllers who were merging flows at the departure fixes. In the tool conditions, departure controllers conditioned departures earlier rather than later when aircraft were tied near the departure fixes. In the scheduling/CMS-D tools conditions, departures crossed the departure fixes 50 seconds earlier and with an 8% error rate (consisting of time ahead or behind desired time of arrival) compared to a 19% error rate in the No Tool condition. Two exploratory runs showed that similar beneficial effects can be obtained only with the CMS-D tools without scheduling takeoff times, but at the cost of a somewhat higher workload for controllers, indicating the benefits of pre-departure scheduling of aircraft with minimal delays. Hence, we found that CMS-D tools were very beneficial in the metroplex environment we tested but that further research is needed to clarify the benefits of the various scheduling approaches.

terminal airspace↗

NASA NTRS2015

Evaluation of Pushback Decision-Support Tool Concept for Charlotte Douglas International Airport Ramp Operations

This paper proposes a new departure pushback decision-support tool (DST) for airport ramp-tower controllers. It is based on NASA's Spot and Runway Departure Advisor (SARDA) collaborative decision-making concept, except with the modification that the gate releases now are controlled by tactical pushback (or gate-hold) advisories instead of strategic pre-assignments of target pushback times to individual departure flights. The proposed ramp DST relies on data exchange with the airport traffic control tower (ATCT) to coordinate pushbacks with the ATCT's flow-management intentions under current operational constraints, such as Traffic Management Initiative constraints. Airlines would benefit in reduced taxi delay and fuel burn. The concept was evaluated in a human-in-the-loop simulation experiment with current ramp-tower controllers at the Charlotte Douglas International Airport as participants. The results showed that the tool helped reduce taxi time by one minute per flight and overall departure flight fuel consumption by 10-12% without reducing runway throughput. Expect Departure Clearance Time (EDCT) conformance also was improved when advisories were provided. These benefits were attained without increasing the ramp-tower controllers' workload. Additionally, the advisories reduced the ATCT controllers' workload.

aerospace human factors↗

NASA NTRS2016

TASAR Flight Trial 2: Assessment of Air Traffic Controller Acceptability of TASAR Requests

In support of the Flight Trial (FT-2) of NASA's prototype of the Traffic Aware Strategic Aircrew Requests (TASAR) concept, observations were conducted at the air traffic facilities to identify and assess the main factors that affect the acceptability of pilot requests by air traffic controllers. Two observers shadowed air traffic controllers at the Atlanta (ZTL) and Jacksonville (ZJX) air traffic control centers as the test flight pilot made pre-scripted requests to invoke acceptability issues and then they interviewed the observed and other controllers voluntarily. Fifty controllers were interviewed with experience ranging from one to thirty-five years. All interviewed controllers were enthusiastic about the technology and accounting for sector boundaries in pilot requests, particularly if pilots can be made aware of high workload situations. All interviewed controllers accept more than fifty percent of pilot requests; forty percent of them reject less than ten percent of requests. The most common reason for rejecting requests is conflicting with traffic followed by violating letters of agreement (LOAs) and negatively impacting neighboring sector workload, major arrival and departure flows and flow restrictions. Thirty-six requests were made during the test, eight of which were rejected due to: the aircraft already handed off to another sector, violating LOA, opposing traffic, intruding into an active special use airspace (SUA), intruding into another center, weather, and unfamiliarity with the requested waypoint. Nine requests were accepted with delay mostly because the controller needed to locate unfamiliar waypoints or to coordinate with other controllers.

Idris, Husni↗

NASA NTRS2016

Charlotte - EDC Evaluation and Demonstration (CEED) Human-in-the-Loop Results Briefing to ATD-2 FAA Partners

The Charlotte EDC Evaluation and Demonstration (CEED) was the first Human-In-The-Loop experiment under the Air Traffic Management Technology Demonstration-2 (ATD-2) project. The purpose of the study was fourfold: 1) to establish a simulation environment (Charlotte) for airspace operations for ATD-2 technology, 2) to simulate current-day departures and arrival operations, 3) to assess the impact of current Traffic Management Initiatives (TMI) on Charlotte (CLT) departure flows and en route operations in Washington (ZDC) and Atlanta Centers (ZTL), and 4) to assess the impact of departure takeoff time compliance on airspace operations. The experimental design compared 3 TMIs and 2 compliance levels. Fourteen FAA retired controllers participated in the simulation. In addition, two Traffic Management Coordinators from ZTL and ZDC managed traffic flows. Surface and airborne delays, control efficiency, throughput, realism, workload, and acceptability were assessed and will be compared across the experimental conditions. Participants rated the simulation as very realistic. Results indicate that different TMIs have different impacts on surface and airspace delay. Departure compliance indicates partial benefits to sector complexity and controller workload. This simulation will provide an initial assessment of the tactical scheduling problems that the ATD-2 technology will address in the near term.

airspace technology demonstration 2↗

NASA NTRS2017

Quantifying Pilot Contribution to Flight Safety During Dual Generator Failure

Accident statistics cite flight crew error in over 60% of accidents involving transport category aircraft. Yet, a well-trained and well-qualified pilot is acknowledged as the critical center point of aircraft systems safety and an integral safety component of the entire commercial aviation system. No data currently exists that quantifies the contribution of the flight crew in this role. Neither does data exist for how often the flight crew handles non-normal procedures or system failures on a daily basis in the National Airspace System. A pilot-in-the-loop high fidelity motion simulation study was conducted by the NASA Langley Research Center in partnership with the Federal Aviation Administration (FAA) to evaluate the pilot's contribution to flight safety during normal flight and in response to aircraft system failures. Eighteen crews flew various normal and non-normal procedures over a two-day period and their actions were recorded in response to failures. To quantify the human's contribution, crew complement was used as the experiment independent variable in a between-subjects design. Pilot actions and performance when one of the flight crew was unavailable were also recorded for comparison against the nominal two-crew operations. This paper details diversion decisions, perceived safety of flight, workload, time to complete pertinent checklists, and approach and landing results while dealing with a complete loss of electrical generators. Loss of electrical power requires pilots to complete the flight without automation support of autopilots, flight directors, or auto throttles. For reduced crew complements, the additional workload and perceived safety of flight was considered unacceptable.

Etherington, Timothy J.↗

NASA NTRS2017

An Advanced Trajectory-Based Operations Prototype Tool and Focus Group Evaluation

Trajectory-based operations (TBO) is a key concept in the Next Generation Air Transportation System transformation of the National Airspace System (NAS) that will increase the predictability and stability of traffic flows, support a common operational picture through the use of digital data sharing, facilitate more effective collaborative decision making between airspace users and air navigation service providers, and enable increased levels of integrated automation across the NAS. The National Aeronautics and Space Administration (NASA) has been developing trajectory-based systems to improve the efficiency of the NAS during specific phases of flight and is now also exploring Advanced 4-Dimensional Trajectory (4DT) operational concepts that will integrate these technologies and incorporate new technology where needed to create both automation and procedures to support gate-to-gate TBO. A TBO Prototype simulation toolkit has been developed that demonstrates initial functionality that may reside in an Advanced 4DT TBO concept. Pilot and controller subject matter experts (SMEs) were brought to the Air Traffic Operations Laboratory at NASA Langley Research Center for discussions on an Advanced 4DT operational concept and were provided an interactive demonstration of the TBO Prototype using four example scenarios. The SMEs provided feedback on potential operational, technological, and procedural opportunities and concerns. After viewing the interactive demonstration scenarios, the SMEs felt the operational capabilities demonstrated would be useful for performing TBO while maintaining situation awareness and low mental workload. The TBO concept demonstrated produced defined routings around weather which resulted in a more organized, consistent flow of traffic where it was clear to both the controller and pilot what route the aircraft was to follow. In general, the controller SMEs felt that traffic flow management should be responsible for generating and negotiating the operational constraints demonstrated, in cooperation with the Air Traffic Control System Command Center, while air traffic control should be responsible for the implementation of those constraints. The SMEs also indicated that digital data communications would be very beneficial for TBO operations and would result in less workload due to reduced communications, would eliminate issues due to language barriers and frequency problems, and would make receiving, loading, accepting, and executing clearances easier, less ambiguous, and more expeditious. This paper describes an Advanced 4DT operational concept, the TBO Prototype, the demonstration scenarios and methods used, and the feedback obtained from the pilot and controller SMEs in this focus group evaluation.

Guerreiro, Nelson M.↗

NASA NTRS2017

Assessment of Air Traffic Controller Acceptability of Aircrew Route Change Requests

NASA developed the traffic aware strategic aircrew requests concept for a cockpit automation that identifies route improvements and advises the aircrew to request the change from the air traffic controller. In order to increase the chance of air traffic control approval, the automation ensures that the route is clear of known traffic, weather, and airspace restrictions. Hence the technology is anticipated to provide benefits in areas such as flight efficiency, flight schedule compliance, passenger comfort, and pilot and controller workload. In support of a field trial of a prototype of the technology, observations were conducted at the Atlanta and Jacksonville air traffic control centers to identify the main factors that affect the acceptability of aircrew requests by air traffic controllers. Observers shadowed air traffic controllers as the test flight pilot made pre-scripted requests to invoke acceptability issues and then they interviewed voluntarily fifty controllers with experience ranging from one to thirty-five years. The most common reason for rejecting requests is conflicting with traffic followed by violating air traffic procedures, increasing sector workload, and conflicting with major arrival and departure flows and flow restrictions. Quantitative parameters such as the distance that a route should maintain from sector boundaries and special use airspace were identified and recommended for inclusion in the automation.

Flight Optimization; Field Trial↗

NASA NTRS2017

Assessment of Air Traffic Controller Acceptability of Aircrew Route Change Requests

Flight Optimization; Field Trial↗