Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “NaS”

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 883 records · Page 49

A Component-Level Model of Automatic Dependent Surveillance - Broadcast (ADS-B)

Automatic Dependent Surveillance – Broadcast (ADS-B) is being employed in numerous peer-to-peer initiatives attempting to expand the capacity of the National Airspace System (NAS) or enable mixed operations of manned and unmanned vehicles. Safety assessments of these initiatives rely, in part, on modeling the accuracy of ADS-B in reporting the position and direction of an ownship and surrounding traffic. Frequently, these initiatives utilize a position uncertainty model that applies a reported ADS-B estimation position uncertainty (EPU) value to a Rayleigh distribution and uses a Gauss-Markov random walk to add error to the ADS-B output of a vehicle. This model of ADS-B state error is easy to implement and apply to numerous problems. However, it has a couple of draw-backs. First, the ADS-B state errors are equally probable in all directions. This is a good assumption in situations where aircraft maneuvering is not constrained. However, in situations where the aircraft maneuvering is constrained such as landing, the error distribution is likely to exhibit directionality and the non-directional model may skew results especially when assessing very low probabilities (e.g., 10(exp -9)) of catastrophic encounters. Second, the model does not account for processing latency in the receiving aircraft. NASA Langley Research Center (LaRC) recently examined the feasibility of decreasing the spacing of aircraft on parallel approaches to runways separated by as little as 700 feet. For Monte-Carlo analysis using a high-fidelity simulation of a large transport, LaRC started with a Gauss-Markov model of ADS-B error but then developed a component level model of ADS-B error to increase the fidelity of results.

Madden, Michael M.↗

An Exploratory Evaluation of UAS Detect and Avoid Operations in the Terminal Environment

New technical standards for Unmanned Aircraft Systems (UAS) detect and avoid (DAA) systems mark recent progress toward realizing the goal of full integration of UAS into the National Airspace System (NAS). The DAA system is intended to provide a means of compliance with operating regulations that required pilots on board manned aircraft to remain "well clear" of other aircraft which is accomplished through out-the-window visual acquisition of other aircraft and application of a subjective judgment of safe separation. The requirements for the DAA system, including the specification of a DAA well clear threshold as well as functional requirements for detecting, tracking, alerting and guidance processing, and displays, are specified in DO-365, Minimum Operational Performance Standards (MOPS) for DAA Systems developed within RTCA (Radio Technical Commission for Aeronautics) Special Committee 228 (SC-228). Intended as the first in a series of phased versions, these requirements are frequently referred to as the "Phase 1" DAA system. The Phase 1 DAA system is limited for use by aircraft transitioning to and from Class A or special use airspace, through Class D, E, and G airspace. In particular, the Phase 1 DAA MOPS are not intended for terminal airspace operations, a critical gap for enabling a full range of UAS operations. The application of the Phase 1 DAA system and DAA well clear threshold within the terminal area is predicted to result in a high number of unnecessary alerts when the UAS is safely separated from other traffic. The goal of the present study was to examine pilot performance and operational issues related to the operation of the Phase 1 DAA system in a terminal area. This experiment was intended as an exploratory study that would be used to inform the development of a new terminal area-specific DAA well clear definition, and associated alerting and guidance requirements. The two main objectives of this study were to: 1) characterize pilot behavior in the terminal environment with the Phase 1 DAA system, and 2) investigate the effect of modifications to the Phase 1 DAA alerting and guidance structure. In particular, the authors were interested in determining whether the removal of specific alerting and guidance levels, without changing the DAA well clear definition or alerting thresholds, would impact pilot performance while conducting terminal operations. The results indicate that the Phase 1 well clear definition and alerting and guidance resulted in frequent alerting that degraded pilots' ability to discriminate between encounters where another aircraft was safely separated versus when a maneuver was necessary. The resulting impact on pilot performance was slower response times and higher frequency and severity of losses of DAA well clear compared to those observed for experiments examining pilot performance in the en route environment. There was no significant effect of alerting and guidance display configuration on pilot performance.

terminal area↗

Urban Air Mobility (UAM) Market Study

The Booz Allen Team explored market size and potential barriers to Urban Air Mobility (UAM) by focusing on three potential markets – Airport Shuttle, Air Taxi, and Air Ambulance. We found that the Airport Shuttle and Air Taxi markets are viable, with a significant total available market value in the U.S. of $500 billion, for a fully unconstrained scenario. In this unconstrained best-case scenario, passengers would have the ability to access and fly a UAM at any time, from any location to any destination, without being hindered by constraints such as weather, infrastructure, or traffic volume. Significant legal and regulatory, weather, certification, public perception, and infrastructure constraints exist, which reduce the market potential for these applications to only about 0.5% of the total available market, or $2.5 billion, in the near term. However, we determined that these constraints can be addressed through ongoing intra-governmental partnerships, government and industry collaboration, strong industry commitment, and existing legal and regulatory enablers. We found that the Air Ambulance market is not a viable market if served by electric vertical takeoff and landing (eVTOL) vehicles due to technology constraints but may potentially be viable if a hybrid VTOL aircraft are utilized. The barriers and challenges we characterized in this study can be stratified according to their applicability or potential mitigation through technology as well as market maturity (Figure 1). In the near term, high cost of service will be a key economic challenge. We found potential for significant reduction in service cost through increased vehicle and component efficiency, and automation in a more mature market scenario. Weather conditions also pose a challenge to the UAM market, though there is potential for mitigation of some of these impacts through technology such as sensors enabling operations in low visibility. However, even in a mature market with advanced technology, disruptions are still likely to occur due to weather events such as thunderstorms and strong winds. High density operations will likely stress the current Air Traffic Management (ATM) system in the near term, but technology and new initiatives such as the Air Traffic Management -eXploration project (ATM-X) will enable safe and efficient integration of UAM into the National Airspace System (NAS). Current battery technology creates a barrier in the near term, especially for the Air Ambulance market, as battery weight and extensive recharging times would be needed for these operations. Advancements in battery technology, as well as use of hybrid VTOLs, could significantly reduce this barrier in the longer term. As UAM emerges as a viable mode of transportation in the near term, adverse energy and environmental impacts, particularly noise, may impact community acceptance and potentially persist as the market matures into larger-scale operations. For non-technology related challenges, we found that infrastructure constraints will create a significant barrier to UAM in the near term but could be addressed in the longer term through development and expansion of vertiports. Competition from existing modes of transportation such as ride-sharing (e.g., Lyft, Uber) and ground taxi’s pose a key barrier to UAM in the short term, which will likely evolve into competition from other emerging technologies such as autonomous cars and electric trains in the longer term. Weather events will influence other components of the operation such as passenger comfort (e.g., extreme temperatures, turbulence) and infrastructure (e.g., winter weather causing cracks and degradation in vertiports). There is also potential for these impacts to be heightened in the longer term from the increased frequency of adverse weather such as thunderstorms due to changing climatic conditions. We also found that the public has strong concerns about safety as a passenger in a piloted UAM, including “lasing” of pilots, unruly passengers, and sabotage. They would prefer that all passengers pass through a security screening process before boarding a vehicle. They would also prefer to use UAM for longer regional trips, such as flying from Washington, DC to Baltimore, MD or San Diego, CA to Los Angeles, CA. A longer term automated UAM vehicle market will face challenges due to public apprehension about automation and unmanned operations, and a preference to fly with passengers they know in an autonomous (unmanned) operational scenario.

Rohit Goyal↗

An Exploratory Evaluation of UAS Detect and Avoid Operations in the Terminal Environment

New technical standards for Unmanned Aircraft Systems (UAS) detect and avoid (DAA) systems mark recent progress toward realizing the goal of full integration of UAS into the National Airspace System (NAS). The DAA system is intended to provide a means of compliance with operating regulations that required pilots on board manned aircraft to remain "well clear" of other aircraft which is accomplished through out-the-window visual acquisition of other aircraft and application of a subjective judgment of safe separation. The requirements for the DAA system, including the specification of a DAA well clear threshold as well as functional requirements for detecting, tracking, alerting and guidance processing, and displays, are specified in DO-365, Minimum Operational Performance Standards (MOPS) for DAA Systems developed within RTCA Special Committee 228 (SC-228). Intended as the first in a series of phased versions, these requirements are frequently referred to as the "Phase 1" DAA system. The Phase 1 DAA system is limited for use by aircraft transitioning to and from Class A or special use airspace, through Class D, E, and G airspace. In particular, the Phase 1 DAA MOPS are not intended for terminal airspace operations, a critical gap for enabling a full range of UAS operations. The application of the Phase 1 DAA system and DAA well clear threshold within the terminal area is predicted to result in a high number of unnecessary alerts when the UAS is safely separated from other traffic. The goal of the present study was to examine pilot performance and operational issues related to the operation of the Phase 1 DAA system in a terminal area. This experiment was intended as an exploratory study that would be used to inform the development of a new terminal area-specific DAA well clear definition, and associated alerting and guidance requirements. The two main objectives of this study were to: 1) characterize pilot behavior in the terminal environment with the Phase 1 DAA system, and 2) investigate the effect of modifications to the Phase 1 DAA alerting and guidance structure. In particular, the authors were interested in determining whether the removal of specific alerting and guidance levels, without changing the DAA well clear definition or alerting thresholds, would impact pilot performance while conducting terminal operations. The results indicate that the Phase 1 well clear definition and alerting and guidance resulted in frequent alerting that degraded pilots' ability to discriminate between encounters where another aircraft was safely separated versus when a maneuver was necessary. The resulting impact on pilot performance was slower response times and higher frequency and severity of losses of DAA well clear compared to those observed for experiments examining pilot performance in the en route environment. There was no significant effect of alerting and guidance display configuration on pilot performance.

Rorie, Conrad↗

New Features in the SPOC Pipeline Release 4.0

The Science Processing Operations Center is in the process of testing and deploying Release 4.0 of the codebase in the March 2019 timeframe. This paper describes the new features of the software and their likely impact on the quality of the TESS science data products. The major goals of Release 4.0 are to improve the extraction of photometry from the pixels in light of the non-uniform pointing performance and the identification of instrumental signatures from the light curves. We also describe modifications to the FFI pipeline to allow the generation of FFI light curves, correction of the instrumental systematics therein, and planet searches, primarily for the purpose of validating the 2-min pipeline against the FFI pipeline, but also to be able to provide cotrending basis vectors (CBVs) derived directly from the FFIs to the public to aid them in their extraction and correction of photometry. We also discuss the improvements in photometric performance of the pipeline and its various components.The lapse in funding experienced between 22 December 2018 and 27 January 2019 significantly delayed our ability to conduct integration testing as planned for late December/early January, delaying the start of V&V by one month to the end of February 2019.The TESS Mission is funded by NASA's Science Mission Directorate as an Astrophysics Explorer Mission.The Science Processing Operations Center is in the process of testing and deplo!"ing Release 4.0 of thecodebase In the March 2019 tlmeframe. This paper describes the new features or the software and theirlikely impact on the quality of the TESS science data products. The major goals or Release 4.0 are to Imtheidentification of instrumental signatures from the light cuNes. We also describe modifications tothe FFI pipeline to allow the generation of FFI light curves, correction of the instrumental systematicstherein, and planet searches, primarily for the purpose of validating the 2-min pipelineagainst the FFI pipeline, but also to be able to provide cotrending basis vectors (C3Vs) ,,.~,.;.derived directly from the FFls to the public to aid them in their extractbn and correction , :-; ~'-'\'.'.of photometry. We also discuss the Improvements In photometric performance• of ~~\":;:•the pipeline and its various components. :,;.-.;The lapse In funding experienced between 22 December 2018 and 27January 2019 significantly delayed our ability to conduct Integrationtesting as planned for late December/early January, delaying thestart of V&V by one month to the end of February 2019.The TESS Mission is funded by NASA's Science Mission Directorateas an Astrophysics Explorer Mission.o.iu.c...,.....~~New Features in SPOC 4.01. Use of quatemions In photometry and centroiding.2. Use of quaternions to Identify high-motion cadences and exclude same.3. Use of the TPS detections to deemphasize pathological cadences ("skyline flattenlng"I.4. Improved CAL calculations for black and smear correction.5. PA brightness metric calculation improvements (induo'e crowding in calrulation)./ • 6. Improved POC spike goodness metric.•~• 7. Improved handling of gaps and momentum duni:>S in POC.8. Improved tuning of POC., 9. Improved attitude tweak correction in PDC.10. Improvements in PDC introduced noise and correlation goodness metrics11. Using the improved spike goodness metric to minimize overlitting in the spikeremover ' • :,''l./ 12. Enable FFI processing through planet search.,,. ,• • "« ,;,,,•.~'A , 13.1 D4.V S mtreinaim-relipnoinrgts d aartcah irveetrdie tvoa Ml aAnSdT p ersistence to database 15. Improved management of jobs on the NAS Pleiadss supercomputer

Jenkins, Jon M.↗

Evaluating the Suitability of Commercial Clouds for NASA's High Performance Computing Applications: A Trade Study

NASA’s High-End Computing Capability (HECC) Project is periodically asked if it could be more cost effective through the use of commercial cloud resources. To answer the question, HECC’s Application Performance and Productivity (APP) team undertook a performance and cost evaluation comparing three domains: two commercial cloud providers, Amazon and Penguin, and HECC’s in-house resources—the Pleiades and Electra systems. In the study, the APP team used a combination of the NAS Parallel Benchmarks (NPB) and six full applications from NASA’s workload on Pleiades and Electra to compare performance of nodes based on three different generations of Intel Xeon processors—Haswell, Broadwell, and Skylake. Because of export control limitations, the most heavily used applications on Pleiades and Electra could not be used in the cloud; therefore, only one of the applications, OpenFOAM, represents work from the Aeronautics Research Mission Directorate and the Human and Exploration Mission Directorate. The other five applications are from the Science Mission Directorate.

High Performance↗

Automatic Execution of Collision Avoidance and Return to Course Analysis (D.6.20) Experiment Review

This presentation details the experimental design for an upcoming engineering analysis of a mock version of the Airborne Collision Avoidance System (ACAS), specifically the 'Xu' variant, which is designed for unmanned aircraft platforms. As a component of the Unmanned Aircraft System (UAS) Integration into the National Airspace System (NAS) project, this engineering analysis intends to study aspects of ACAS Xu in two parts. In the first phase of the study, the display and alerting guidance for collision avoidance (CA) resolution advisories (RA) shown to pilots at a ground control station will be manipulated, varying in level of RA transparency and presentation of safe maneuver parameters. The second phase of the engineering analysis will examine pilots' response to increasing levels of automation in the tasks of collision avoidance and return-to-course (RTC).

Sadler, Garrett↗

Overview of Sense and Avoid/Separation Assurance Interoperability (SSI)

The UAS in the NAS project is studying the minimum operational performance standards for unmanned aerial systems (UAS's) detect-and-avoid (DAA) system in order to operate in the National Airspace System. The project is executing a series of fast-time simulation, human-in-the-loop experiments, and flight test in support of this effort. Officials of the Swiss Government (Peter Winter, Director of Aeronautical Systems, and Michel Godinat, Head of the Certification Office) are visiting NASA to become more familiar with the advances being made to integrate UAS into civilian airspace. This briefing will review the activities and results over the past 3 years within the Separation AssuranceSense-and-Avoid Interoperability team.

Santiago, Confesor↗

Understanding Community Needs and Desires

This panel exchange is focused on the Integration Test phase within the development lifecycle with special emphasis and dedicated discussion on integration and testing of complex systems. Layout and scheduling of integration tasks come from the verification of interface and performance requirements. However, planning for integration activities of complex systems is inherently different from traditional systems engineering integration planning activities. Decisions about the systems under development have to consider not only the technical and programmatic viewpoints but also the political, societal, operational, and economic viewpoints. Definition of performance measures, found intrinsic in the plan, with trans-disciplinary implications will be discussed. A scenario of integration of UAS in the NAS will be used as a benchmark of current views and lifecycle challenges.

Murphy, James R.↗

ACES Preliminary Results Supporting Selection of SARP Well-Clear Definitions

The UAS in the NAS project is studying the minimum operational performance standards for unmanned aerial systems (UAS's) detect-and-avoid (DAA) system in order to operate in the National Airspace System. The DoD's Science and research Panel Well-Clear Workshop is investigating the time and spatial boundary at which an UAS violates well-clear. NASA is supporting this effort through use of its Airspace Concept Evaluation System (ACES) simulation platform. This presentation reviews how the simulation was used to support this work, lessons learned during the experiment, and introduces preliminary results.

well-clear↗

Investigating the Impacts of a Separation Standard for UAS Operations in Enroute and Transition Airspace

Unmanned aircraft systems will be required to equip with a detect and avoid system in order to satisfy the federal aviation regulations to remain well clear of other aircraft. To comply with regulations in today’s operations manned aircraft must “see and avoid” other aircraft and use subjective judgment to determine whether those aircraft are well clear. For a detect-and- avoid (DAA) system to satisfy the requirement to stay well clear, a quantitative definition of well clear needs to be defined and evaluated. Definitions for the boundary of well clear have been proposed by the Unmanned Aircraft System (UAS) Executive Committee Science and Research Panel (SaRP) and the Radio Technical Commission for Aeronautics (RTCA) Special Committee 228 on Detect and Avoid Systems. This study investigates the interoperability implications of UAS using proposed well clear definitions as a separation standard for conducting operations in the national airspace system. The first analysis in the study focuses on the effect of variations in well clear definition parameters on the rate of losses of well clear per flight hour. The second analysis considers three well clear definitions and presents the relative state conditions of intruder aircraft as they encroach upon the well clear boundary. The third analysis focuses on the definition of the alerting criteria needed to inform the UAS operator of a potential loss of well clear. All three analyses are conducted in a NAS-wide fast-time simulation environment using UAS aircraft models, proposed UAS missions, and historical air defense radar data to populate the background traffic operating under visual flight rules. The results from the three analyses presented in this study inform the safety case, requirements development, and the operational environment for the DAA minimum operational performance standards.

UAS Seperation Standard↗

NASA ACES V&V Alignment Briefing

Regulations to establish operational and performance requirements for unmanned aircraft systems (UAS) are being developed by a consortium of government, industry and academic institutions. Those requirements will apply to the new detect and avoid (DAA) systems and other equipment necessary to integrate UAS with the National Airspace System (NAS) and are determined according to their contribution to the overall safety case for such an integration. This briefing focuses on providing an overview of the Airspace Concept Evaluation System (ACES) platform, review of detect-and-avoid models incorprated in ACES, sumamry of two planned ACES studies, and a way forward to impact the SC-228 VV plan.

Santiago, Confesor↗

Proposal for a Sample Pilot Response Model

Regulations to establish operational and performance requirements for unmanned aircraft systems (UAS) are being developed by a consortium of government, industry and academic institutions. Those requirements will apply to the new detect and avoid (DAA) systems and other equipment necessary to integrate UAS with the National Airspace System (NAS) and are determined according to their contribution to the overall safety case for such an integration. In order to perform end-to-end verification and validation of DAA requirements, a committee accepted pilot response model is needed to emulate UAS pilots in closed-loop Monte Carlo fast-time simulations. This briefing focuses on background of the pilot model used in previous Airspace Concept Evaluation System studies, identification of strengths and weaknesses in that model, and proposals on model improvements. The briefing also looks to build consensus around a common architecture and assumptions for modeling the pilot for UAS DAA systems.

Santiago, Confesor↗

Simulation and Flight Test Data Collection Review for Supporting Phase 1 Detect and Avoid MOPS

RTCA Special Committee 228 is a consortium of government, industry, and academic organizations tasked to develop minimum operational performance standards for UAS detect and avoid systems. The UAS in the NAS (National Airspace System) project is studying the minimum operational performance standards for unmanned aerial systems (UAS's) detect-and-avoid (DAA) system in order to operate in the National Airspace System. Over the past 3 years, the project has executed a series of fast-time simulation, human-in-the-loop experiments, and flight tests in support of this effort. The purpose of this briefing is to summarize the models developed and data collected to overcome UAS integration barriers, so UAS can remain well clear of all traffic.

Santiago, Confesor↗

Validation of Minimum Display Requirements for a UAS Detect and Avoid System

The full integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS), a prerequisite for enabling a broad range of public and commercial UAS operations, presents several technical challenges to UAS developers, operators and regulators. A primary barrier is the inability for UAS pilots (situated at a ground control station, or GCS) to comply with Title 14 Code of Federal Regulations sections 91.111 and 91.113, which require pilots to “see and avoid” other aircraft in order to maintain well clear. UAS pilots’ removal from the flight deck of the aircraft necessitates the development of a UAS-specific system for detecting nearby traffic and displaying traffic information to the pilot to support their ability to maintain an objectively defined “DAA well clear” threshold from other aircraft. This new UAS-specific function of remaining DAA well clear is called traffic avoidance. The resulting Detect and Avoid (DAA) system, however, will be subject to a collection of requirements that manufacturers will be obligated to meet in order to certify their equipment. RTCA Special Committee 228 (SC-228), a consortium of representatives from government, industry and academia, is responsible for developing and documenting the Minimum Operational Performance Standards (MOPS) for UAS DAA systems. The present study is the final in a series of human-in-the-loop (HITL) experiments designed to explore and test the various display and alerting requirements being incorporated into the DAA MOPS. Whereas the prior DAA HITLs examined a wide variety of DAA display features and concepts, the current experiment aims to validate the latest minimum display requirements for Phase 1 of the DAA MOPS. Rather than test different display concepts, this study tests two configurations of a MOPS-compatible DAA display: a version that is integrated into the primary navigation and control display of the GCS and a version that is physically separated from the primary display. This manipulation tests the draft minimum requirement that allows the DAA traffic display to be a separate, or standalone, configuration. This type of configuration is a more achievable near-term technology solution since it does not stipulate additional certification or integration requirements on UAS manufacturers. However, a standalone display configuration has the potential to result in pilot performance issues resulting from the cognitive costs of switching between the primary DAA display and the primary navigation and control display. This configuration is also particularly susceptible to errors if the displays are in different orientations (e.g., north-up versus track-up). Both the integrated and standalone display configurations were presented to 16 active UAS pilots in a medium-fidelity simulation, which included confederate air traffic controllers and pseudo pilots operating simulated manned traffic. Pilots were tasked with navigating two different mission routes while maintaining DAA well clear with scripted conflicts. Pilot response times (i.e., measured response) and ability to remain DAA well clear are reported. Primary results indicate that both display configurations resulted in favorable response times and well clear rates. While there were clear trends of pilots objectively performing better in the integrated display condition, with several measured response metrics reaching statistical significance, the differences between the two displays were typically moderate. While the primary variable of DAA display location did not have an especially large impact on pilot performance on its own, when examined alongside the type of DAA threat the pilot was facing (a caution-level versus a warning-level alert), the response time benefits associated with the integrated display were amplified. The implications of these American Institute of Aeronautics and Astronautics 2 results on the Phase 1 DAA MOPS and the connection of this data to previous studies is also discussed.

detect and avoid↗

Indoor Ground Testing of a Small UAS Sense and Avoid Airborne Doppler Radar

The National Aeronautics and Space Administration’s Unmanned Aircraft System (UAS) Traffic Management (UTM) project is researching prototype technologies needed to ensure safe integration of UAS operations into the National Airspace System (NAS). Within the UTM Concept of Operations, UAS would be equipped with on-board Sense and Avoid (SAA) technology to continually monitor for manned and unmanned aircraft in its vicinity while operating beyond visual line of sight in uncontrolled airspace. To support this effort, a candidate commercially available 24.5 GHz Doppler radar was selected and evaluated to determine if the technology could reliably support minimum requirements for SAA applications of small UAS (sUAS). Indoor ground tests were conducted inside the NASA Langley Research Center’s Experimental Test Range (ETR) from a stationary platform to evaluate the Doppler radar performance characteristics and gain operational proficiency before the radar was authorized to transmit outdoors. A high speed linear rail system was developed for the radar evaluation and was shown to be an effective method to generate Doppler radar targets of known radar cross section. The accuracy of the range and velocity reported by the radar was shown to be dependent on the Kalman filter state variance parameter settings. Antenna measurements were collected with the radar installed both on and off a sUAS to quantify the relative antenna gain, beam width and side lobe levels of the radar’s Metamaterial Electronically Scanning Array (MESA) antennas at boresight and extreme field of view pointing vectors. The relative antenna gain measured 2.6 dB lower at extreme field view angles compared to the boresight radiation pattern.

Szatkowski, George N.↗

In-Flight Evaluation of the Traffic Aware Planner on the NASA HU-25A Guardian Aircraft

NASA’s Traffic Aware Planner (TAP) software is a research-prototype decision support tool that provides pilots with time- and fuel-saving route recommendations that optimize their current trajectory. The software runs on a first-of-a-kind system architecture onboard three aircraft in revenue service conducting operational evaluations with a major domestic airline. Therefore, significant NASA-internal testing is required prior to releasing the software to the partner airline. This paper describes a flight test plan that exercises the functionality of the TAP software in a representative operational environment, describes the system architecture developed and implemented for the NASA Langley HU-25A Guardian aircraft to support the test objectives, presents outcomes of the flight test campaign, and discusses use cases that demonstrate the value of flight testing for this activity.Research into flight path optimization of transport aircraft conducted by the National Aeronautics and SpaceAdministration (NASA) has produced an operational concept known as Traffic Aware Strategic Aircrew Requests(TASAR) [1, 2]. This near-term concept [3] provides the aircrew with a flight deck decision support tool known asthe Traffic Aware Planner (TAP). The TAP software leverages a growing number of information sources on the flightdeck to make time- and fuel-saving route optimization recommendations to the aircrew while en route. The aircrewcan then use the suggestions provided by the tool to make route change requests with a greater likelihood of acceptanceby air traffic control (ATC). Since TASAR is a concept intended for the current operational environment, it isintentionally designed to have no safety-critical impact or require any changes to current Federal AviationAdministration (FAA) rules and procedures [4, 5].The research prototype TAP system [6–8], explained further in Section III.C, continually incorporates up-to-dateaircraft state data from onboard avionics, as well as the latest position of surrounding traffic, the most recent windforecast, and the most recent convective weather forecast, in order to calculate candidate trajectory modifications thatimprove upon the current active route. These trajectories account for user-selectable objective functions [3] of reducedfuel burn, reduced flight time, or an airline-derived combination of factors known as trip cost. Previous analyses andsimulations have estimated substantial savings for airlines employing this technique within the U.S. National AirspaceSystem (NAS) [9–11]. Operational evaluations with Alaska Airlines seek to validate these projected benefits usingmeasured data while simultaneously providing benefits to the airline [12, 13].The TAP software has undergone a number of human-in-the-loop simulations [14] and flight test activities[15–17] in order to validate the operational concept, evaluate human factors considerations (e.g., workload, usability,distraction, etc.), and to assess the ability of the software to function in a representative operational environment (e.g.,connected to live avionics data, using in-flight internet connectivity, etc.). However, these simulations and flight testcampaigns did not account for the hardware architecture implemented on the three aircraft for Alaska Airlines’operational evaluations of the TAP software. Therefore, a need was identified to thoroughly test the functionality ofthe software in a similar hardware architecture to that of the partner airline’s aircraft. Information regarding testapparatus and environments used to evaluate TAP prior to testing on the HU-25A can be found in reference [18].A campaign of flight trials on a NASA aircraft, the HU-25A Guardian, was conducted to ensure that the researchprototype TAP system functions well in a configuration similar to the Alaska Airlines aircraft prior to deployment.This airborne, networked environment enables an assessment of the operational factors unique to the flight environment. Additionally, this activity evaluated the effectiveness and benefit of new TAP functionality andoperation in a relevant flight environment while allowing the rapid prototyping of new concepts and features.This paper is organized as follows: Section II discusses the details of the flight test plan, flight profiles, and theduties of personnel involved with conducting flight operations. Section III describes the test platform, avionicsequipage, and system architecture. Section IV presents a discussion of results, and Section V contains concludingremarks.

Underwood, Matthew C.↗