Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “and Operations”

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 1,099 records · Page 61
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

Lessons Learned in the First Year Operating Software Defined Radios in Space

Operating three unique software defined radios (SDRs) in a space environment aboard the Space Communications and Navigation (SCaN) Testbed for over one year has provided an opportunity to gather knowledge useful for future missions considering using software defined radios. This paper provides recommendations for the development and use of SDRs, and it considers the details of each SDRs approach to software upgrades and operation. After one year, the SCaN Testbed SDRs have operated for over 1000 hours. During this time, the waveforms launched with the SDR were tested on-orbit to assure that they operated in space at the same performance level as on the ground prior to launch to obtain an initial on-orbit performance baseline. A new waveform for each SDR has been developed, implemented, uploaded to the flight system, and tested in the flight environment. Recommendations for SDR-based missions have been gathered from early development through operations. These recommendations will aid future missions to reduce the cost, schedule, and risk of operating SDRs in a space environment. This paper considers the lessons learned as they apply to SDR pre-launch checkout, purchasing space-rated hardware, flexibility in command and telemetry methods, on-orbit diagnostics, use of engineering models to aid future development, and third-party software. Each SDR implements the SCaN Testbed flight computer command and telemetry interface uniquely, allowing comparisons to be drawn. The paper discusses the lessons learned from these three unique implementations, with suggestions on the preferred approach. Also, results are presented showing that it is important to have full system performance knowledge prior to launch to establish better performance baselines in space, requiring additional test applications to be developed pre-launch. Finally, the paper presents the issues encountered with the operation and implementation of new waveforms on each SDR and proposes recommendations to avoid these issues.

radio equipment↗
NASA NTRS2014

Lessons Learned in the First Year Operating Software Defined Radios in Space

Operating three unique software defined radios (SDRs) in a space environment aboard the Space Communications and Navigation (SCaN) Testbed for over one year has provided an opportunity to gather knowledge useful for future missions considering using software defined radios. This paper provides recommendations for the development and use of SDRs, and it considers the details of each SDR's approach to software upgrades and operation. After one year, the SCaN Testbed SDRs have operated for over 1000 hours. During this time, the waveforms launched with the SDR were tested on-orbit to assure that they operated in space at the same performance level as on the ground prior to launch to obtain an initial on-orbit performance baseline. A new waveform for each SDR has been developed, implemented, uploaded to the flight system, and tested in the flight environment. Recommendations for SDR-based missions have been gathered from early development through operations. These recommendations will aid future missions to reduce the cost, schedule, and risk of operating SDRs in a space environment. This paper considers the lessons learned as they apply to SDR pre-launch checkout, purchasing space-rated hardware, flexibility in command and telemetry methods, on-orbit diagnostics, use of engineering models to aid future development, and third-party software. Each SDR implements the SCaN Testbed flight computer command and telemetry interface uniquely, allowing comparisons to be drawn. The paper discusses the lessons learned from these three unique implementations, with suggestions on the preferred approach. Also, results are presented showing that it is important to have full system performance knowledge prior to launch to establish better performance baselines in space, requiring additional test applications to be developed pre-launch. Finally, the paper presents the issues encountered with the operation and implementation of new waveforms on each SDR and proposes recommendations to avoid these issues.

space communication↗
NASA NTRS2013

Operation of Direct Drive Systems: Experiments in Peak Power Tracking and Multi-Thruster Control

Direct-drive power and propulsion systems have the potential to significantly reduce the mass of high-power solar electric propulsion spacecraft, among other advantages. Recent experimental direct-drive work has significantly mitigated or retired the technical risks associated with single-thruster operation, so attention is now moving toward systems-level areas of interest. One of those areas is the use of a Hall thruster system as a peak power tracker to fully use the available power from a solar array. A simple and elegant control based on the incremental conductance method, enhanced by combining it with the unique properties of Hall thruster systems, is derived here and it is shown to track peak solar array power very well. Another area of interest is multi-thruster operation and control. Dualthruster operation was investigated in a parallel electrical configuration, with both thrusters operating from discharge power provided by a single solar array. Startup and shutdown sequences are discussed, and it is shown that multi-thruster operation and control is as simple as for a single thruster. Some system architectures require operation of multiple cathodes while they are electrically connected together. Four different methods to control the discharge current emitted by individual cathodes in this configuration are investigated, with cathode flow rate control appearing to be advantageous. Dual-parallel thruster operation with equal cathode current sharing at total powers up to 10 kW is presented.

solar electric propulsion (SEP) vehicles↗
NASA NTRS2010

In-Flight Operation of the Dawn Ion Propulsion System: Status at One Year from the Vesta Rendezvous

The Dawn mission, part of NASA's Discovery Program, has as its goal the scientific exploration of the two most massive main-belt asteroids, Vesta and Ceres. The Dawn spacecraft was launched from Cape Canaveral Air Force Station on September 27, 2007 on a Delta-II 7925H-9.5 (Delta-II Heavy) rocket that placed the 1218 kg spacecraft into an Earth-escape trajectory. On-board the spacecraft is an ion propulsion system (IPS) developed at the Jet Propulsion Laboratory which will provide most of the delta V needed for heliocentric transfer to Vesta, orbit capture at Vesta, transfer among Vesta science orbits, departure and escape from Vesta, heliocentric transfer to Ceres, orbit capture at Ceres, and transfer among Ceres science orbits. The Dawn ion thruster [I thought we only called it a thruster. Both terms are used in the paper, but I think a replacement of every occurrence of "engine" with "thruster" would be clearer.] design is based on the design validated on NASA's Deep Space 1 (DS1) mission. However, because of the very substantial (11 km/s) delta V requirements for this mission Dawn requires two engines to complete its mission objectives. The power processor units (PPU), digital control and interface units (DCIU) slice boards and the xenon control assembly (XCA) are derivatives of the components used on DS1. The DCIUs and thrust gimbal assemblies (TGA) were developed at the Jet Propulsion Laboratory. The spacecraft was provided by Orbital Sciences Corporation, Sterling, Virginia, and the mission is managed by and operated from the Jet Propulsion Laboratory. Dawn partnered with Germany, Italy and Los Alamos National Laboratory for the science instruments. The mission is led by the principal investigator, Dr. Christopher Russell, from the University of California, Los Angeles. The first 80 days after launch were dedicated to the initial checkout of the spacecraft followed by cruise to Mars. Cruise thrusting leading to a Mars gravity assist began on December 17, 2007 and was successfully concluded as planned on October 31, 2008. During this time period the Dawn IPS was operated mostly at full power for approximately 6500 hours, consumed 71.7 kg of xenon and delivered approximately 1.8 km/s of delta V to the spacecraft. The thrusting to Mars was followed by a coasting period of approximately 3.5 months that included a Mars flyby in February of 2009. The Mars flyby provided a gravity assist (MGA) for a plane change and approximately 1 km/s of heliocentric energy increase and is the only part of the mission following launch in which a needed velocity change is not accomplished by the IPS. During the coast period IPS was operated for a trajectory correction maneuver and for engineering tests but was not operated for primary propulsion. Closest approach to Mars occurred as planned on February 17, 2009 and was followed by another coasting period of just under 4 months in duration. During this last coasting phase IPS was operated only for routine maintenance activities and for system engineering tests. Deterministic thrusting for heliocentric transfer to Vesta resumed on June 8, 2009. Since resumption of cruise to Vesta IPS has been operated at throttled power levels, most of the time at full power, and with a duty cycle of approximately 93%, leading to an arrival at Vesta in July of 2011 and arrival at Ceres in February 2015. This paper provides an overview of Dawn's mission objectives and the results of Dawn IPS mission operations through one year from the spacecraft's rendezvous with Vesta.

Garner, Charles E.↗
NASA NTRS2009

In-Flight Operation of the Dawn Ion Propulsion System Through Start of the Vesta Cruise Phase

The Dawn mission, part of NASA's Discovery Program, has as its goal the scientific exploration of the two most massive main-belt asteroids, Vesta and Ceres. The Dawn spacecraft was launched from Cape Canaveral Air Force Station on September 27, 2007 on a Delta-II 7925H-9.5 (Delta-II Heavy) rocket that placed the 1218 kg spacecraft into an Earth-escape trajectory. On-board the spacecraft is an ion propulsion system (IPS) which will provide most of the delta V needed for heliocentric transfer to Vesta, orbit capture at Vesta, transfer to Vesta science orbits, departure and escape from Vesta, heliocentric transfer to Ceres, orbit capture at Ceres, and transfer to Ceres science orbits. The Dawn ion design is based on the design validated on NASA's Deep Space 1 (DS1) mission. However, because of the very substantial (11 km/s) delta V requirements for this mission Dawn requires two engines to complete its mission objectives. The power processor units (PPU), digital control and interface units (DCIU) slice boards and the xenon control assembly (XCA) are derivatives of the components used on DS1. The DCIUs and thrust gimbal assemblies (TGA) were developed at the Jet Propulsion Laboratory. The spacecraft was provided by Orbital Sciences Corporation, Sterling, Virginia, and the mission is managed by and operated from the Jet Propulsion Laboratory. Dawn partnered with Germany, Italy and Los Alamos National Laboratory for the science instruments. The mission is led by the principal investigator, Dr. Christopher Russell, from the University of California, Los Angeles. The first 80 days after launch were dedicated to the initial checkout of the spacecraft followed by cruise to Mars. Cruise thrusting leading to a Mars gravity assist began on December 17, 2007 and was successfully concluded as planned on October 31, 2008. During this time period the Dawn IPS was operated mostly at full power for approximately 6500 hours, consumed 71.7 kg of xenon and delivered approximately 1.8 km/s of delta V to the spacecraft. The thrusting to Mars was followed by a coasting period of approximately 3.5 months that included a Mars flyby in February of 2009. The Mars flyby provided a gravity assist (MGA) for a plane change and approximately 1 km/s of heliocentric energy increase and is the only part of the mission following launch in which a needed velocity change is not accomplished by the IPS. During the coast period IPS was operated for a trajectory correction maneuver and for engineering tests but was not operated for primary propulsion. Closest approach to Mars occurred as planned on February 17, 2009 and was followed by another coasting period of just under 4 months in duration. During this last coasting phase IPS was operated only for routine maintenance activities and for system engineering tests. Deterministic thrusting for heliocentric transfer to Vesta resumed on June 8, 2009. IPS will be operated for over two years at throttled power levels leading to arrival at Vesta in September of 2011 and arrival at Ceres in February 2015. This paper provides an overview of Dawn's mission objectives and the results of Dawn IPS mission operations through the start of deterministic thrusting to Vesta.

Garner, Charles E.↗
NASA NTRS2008

In-Flight Operation of the Dawn Ion Propulsion System - The First Nine Months

The Dawn mission, part of NASA's Discovery Program, has as its goal the scientific exploration of the two most massive main-belt asteroids, Vesta and Ceres. The Dawn spacecraft was launched from Cape Canaveral Air Force Station on September 27, 2007 on a Delta-II 7925H-9.5 (Delta-II Heavy) rocket that placed the 1218 kg spacecraft into an Earth-escape trajectory. On-board the spacecraft is an ion propulsion system (IPS) which will provide most of the delta-V needed for heliocentric transfer to Vesta, orbit capture at Vesta, transfer to Vesta science orbits, departure and escape from Vesta, heliocentric transfer to Ceres, orbit capture at Ceres, and transfer to Ceres science orbits. The Dawn ion engine design is based on the design validated on NASA's Deep Space 1 mission. However, because of the very substantial (11 km/s) delta-V requirements for this mission Dawn requires two engines to complete its mission objectives. The power processor units (PPU), digital control and interface units (DCIU) slice boards and the xenon control assembly (XCA) are also based on the DS1 design. The DCIUs and thrust gimbal assemblies (TGA) were developed at the Jet Propulsion Laboratory. The spacecraft was provided by Orbital Sciences Corporation, Sterling, Virginia, and the mission is managed by and operated from the Jet Propulsion Laboratory. Dawn partnered with Germany, Italy and Los Alamos National Laboratory for the science instruments. The mission is led by the principal investigator, Dr. Christopher Russell, from the University of California, Los Angeles. The first 80 days after launch were dedicated to the initial checkout of the spacecraft prior to the initiation of long-term thrusting for the heliocentric transfer to Vesta. The IPS hardware, consisting of three ion thrusters and TGAs, two PPUs and DCIUs, xenon feed system, and spacecraft control software, was investigated extensively. Thrust measurements, roll torque measurements, pointing capabilities, control characteristics, and thermal behavior of the spacecraft and IPS were carefully evaluated. The Dawn IPS fully met all its initial checkout performance objectives. Deterministic thrusting for cruise began on December 17, 2007. Over the subsequent approximately 330 days the IPS will be operated virtually continuously at full power thrusting (approximately 91 mN) leading to a Mars flyby in February 2009. The encounter with Mars provides a gravity assist for a plane change and is the only source of post-launch delta-V apart from the IPS. Following the Mars gravity assist IPS will be operated for approximately one year at full power and for 1.3 years at throttled power levels leading to rendezvous with Vesta in August of 2011. Following nine months of orbital operations with IPS providing the propulsion needed for orbit capture, science orbit transfer and orbit maintenance and Vesta escape, Dawn will transit to Ceres with an expected arrival date of February 2015. As of June 16, 2008 the ion thrusters on Dawn have operated for close to 3,846 hours and have delivered nearly 1 km/s of delta-V to the spacecraft. Dawn IPS operation has been almost flawless during the initial checkout and six months of cruise. This paper provides an overview of Dawn's mission objectives, mission and system design, and the results of the post-launch Dawn IPS mission operations through June 2008

Garner, Charles E.↗
NASA NTRS2006

SiC Field Effect Transistor Technology Demonstrating Prolonged Stable Operation at 500 C

While there have been numerous reports of short-term transistor operation at 500 degree C or above, these devices have previously not demonstrated sufficient long-term operational durability at 500 degree C to be considered viable for most envisioned applications. This paper reports the development of Silicone Carbi field effect transistors capable of long-term electrical operation at 500 degree C. A 6H-SiC MESFET was packaged and subjected to continuous electrical operation while residing in a 500 degree C oven in oxidizing air atmosphere for over 2400 hours. The transistor gain, saturation current (IDSS), and on-resistance (RDS) changed by less than 20% from initial values throughout the duration of the biased 500 degree C test. Another high-temperature packaged 6H-SiC MESFET was employed to form a simple one-stage high-temperature low-frequency voltage amplifier. This single-stage common-source amplifier demonstrated stable continuous electrical operation (negligible changes to gain and operating biases) for over 600 hours while residing in a 500 degree C air ambient oven. In both cases, increased leakage from annealing of the Schottky gate-to-channel diode was the dominant transistor degradation mechanism that limited the duration of 500 degree C electrical operation.

Neudeck, Philip G.↗
NASA NTRS2015

SPHERES: From Ground Development to Operations on ISS

SPHERES (Synchronized Position Hold Engage and Reorient Experimental Satellites) is an internal International Space Station (ISS) Facility that supports multiple investigations for the development of multi-spacecraft and robotic control algorithms. The SPHERES Facility on ISS is managed and operated by the SPHERES National Lab Facility at NASA Ames Research Center (ARC) at Moffett Field California. The SPHERES Facility on ISS consists of three self-contained eight-inch diameter free-floating satellites which perform the various flight algorithms and serve as a platform to support the integration of experimental hardware. To help make science a reality on the ISS, the SPHERES ARC team supports a Guest Scientist Program (GSP). This program allows anyone with new science the possibility to interface with the SPHERES team and hardware. In addition to highlighting the available SPHERES hardware on ISS and on the ground, this presentation will also highlight ground support, facilities, and resources available to guest researchers. Investigations on the ISS evolve through four main phases: Strategic, Tactical, Operations, and Post Operations. The Strategic Phase encompasses early planning beginning with initial contact by the Principle Investigator (PI) and the SPHERES program who may work with the PI to assess what assistance the PI may need. Once the basic parameters are understood, the investigation moves to the Tactical Phase which involves more detailed planning, development, and testing. Depending on the nature of the investigation, the tactical phase may be split into the Lab Tactical Phase or the ISS Tactical Phase due to the difference in requirements for the two destinations. The Operations Phase is when the actual science is performed; this can be either in the lab, or on the ISS. The Post Operations Phase encompasses data analysis and distribution, and generation of summary status and reports. The SPHERES Operations and Engineering teams at ARC is composed of experts who can guide the Payload Developer (PD) and Principle Investigator (PI) in reaching critical milestones to make their science a reality using the SPHERES platform. From performing integrated safety and verification assessments, to assisting in developing crew procedures and operations products, to organizing, planning, and executing all test sessions, to helping manage data products, the SPHERES team at ARC is available to support microgravity research with the SPEHRES Guest Scientist Program.

ISS Research↗
NASA NTRS2017

Prototype Tool and Focus Group Evaluation for an Advanced Trajectory-Based Operations Concept

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. 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 of 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. 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 activity.

Guerreiro, Nelson M.↗
NASA NTRS2017

Flight Deck Surface Trajectory-Based Operations

Surface Trajectory-Based Operations (STBO) is a future concept for surface operations where time requirements are incorporated into taxi operations to support surface planning and coordination. Pilot-in-the-loop flight deck simulations have been conducted to study flight deck displays algorithms to aid pilots in complying with the time requirements of time-based taxi operations (i.e., at discrete locations in 3 12 D operations or at all points along the route in 4DT operations). The results of these studies (conformance, time-of-arrival error, eye-tracking data, and safety ratings) are presented. Flight deck simulation work done in collaboration with DLR is described. Flight deck research issues in future auto-taxi operations are also introduced.

flight deck↗
NASA NTRS2018

Automated Impact Assessment: A New Approach to ISS Payload Operations Anomaly Response

The International Space Station (ISS) Payload Operations and Integration Center (POIC) is undergoing rapid growth as the space station program focuses on science and commercial activities. The ISS is expanding its onboard capabilities to support additional science activities. In parallel, the POIC is expanding the capabilities of our operations tools to support the higher pace of payload activities being executed each week. An effect of these changes is that anomaly resolution has become more challenging. In the event of a real-time system fault, operators are responsible for analyzing telemetry displays, anomaly monitoring tools, documentation, and system models in order to produce failure impacts and recovery strategies. This approach to operations relies on the operator to ingest, process, and analyze information from an array of deterministic sources to provide actionable data on impacted systems and activities. Changing the existing approach of anomaly response is necessary if the ISS community is to succeed in the age of science and commercialization of space. The creation of a tool that captures deterministic technical systems knowledge and integrates existing telemetry, documentation, and planning information will allow the burden of impact assessment to be automated, thereby allowing the operator to focus on non-deterministic tasks, such as recovering failed systems and restoring critical payload operations.

Hall, R. Mason↗
NASA NTRS2016

Unmanned Aircraft System Traffic Management (UTM) Concept of Operations

Many applications of small Unmanned Aircraft System (sUAS) have been envisioned. These include surveillance of key assets such as pipelines, rail, or electric wires, deliveries, search and rescue, traffic monitoring, videography, and precision agriculture. These operations are likely to occur in the same airspace in presence of many static and dynamic constraints such as airports, and high wind areas. Therefore, small UAS, typically 55 pounds and below, operations need to be managed to ensure safety and efficiency of operations is maintained. This paper will describe the Concept of Operations (ConOps) for NASA's UAS Traffic Management (UTM) research initiative. The UTM ConOps is focused on safely enabling large-scale small UAS (sUAS) operations in low altitude airspace. The UTM construct supports large-scale visual line of sight and beyond visual line of sight operations. It is based on two primary mantras: (1) flexibility where possible and structure where necessary (2) a risk-based approach where geographical needs and use case indicate the airspace performance requirements. Preliminary stakeholder feedback and initial UTM tests conducted by NASA show promise of UTM to enable large-scale low altitude UAS operations safely.

autonomy↗
NASA NTRS2018

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↗
NASA NTRS2018

Biocybernetic Adaptation Strategies: Machine Awareness of Human Engagement for Improved Operational Performance

Human operators interacting with machines or computers continually adapt to the needs of the system ideally resulting in optimal performance. In some cases, however, deteriorated performance is an outcome. Adaptation to the situation is a strength expected of the human operator which is often accomplished by the human through self-regulation of mental state. Adaptation is at the core of the human operator's activity, and research has demonstrated that the implementation of a feedback loop can enhance this natural skill to improve training and human/machine interaction. Biocybernetic adaptation involves a “loop upon a loop,” which may be visualized as a superimposed loop which senses a physiological signal and influences the operator’s task at some point. Biocybernetic adaptation in, for example, physiologically adaptive automation employs the “steering” sense of “cybernetic,” and serves a transitory adaptive purpose – to better serve the human operator by more fully representing their responses to the sys- tem. The adaptation process usually makes use of an assessment of transient cog- nitive state to steer a functional aspect of a system that is external to the operator’s physiology from which the state assessment is derived. Therefore, the objective of this paper is to detail the structure of biocybernetic systems regarding the level of engagement of interest for adaptive systems, their processing pipeline, and the adaptation strategies employed for training purposes, in an effort to pave the way towards machine awareness of human state for self-regulation and improved operational performance.

Stephens, Chad↗
NASA NTRS2018

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↗
NASA NTRS2019

Initial TASAR Operations Onboard Alaska Airlines

NASA and Alaska Airlines jointly conducted an operational evaluation of NASA’s Traffic Aware Strategic Aircrew Request (TASAR) concept. Featuring a NASA-developed cockpit automation tool, the Traffic Aware Planner (TAP), and leveraging the emerging “connected aircraft” architecture, TASAR enables pilots to identify route changes compatible with nearby traffic and airspace constraints that improve flight efficiency and are more likely to receive Air Traffic Control approval. TASAR was developed in anticipation of saving fuel and flight time, thereby providing immediate and pervasive benefits to the aircraft operator. Following a previously reported, extensive program of integration and preliminary in-flight testing, the operational evaluation of TASAR in revenue service by Alaska Airlines took place from July 2018 to April 2019. This paper describes the operational evaluation, the methodology for quantifying operational benefits, preliminary benefit results, and other unexpected impacts of TASAR operations during revenue flights. Based on the subset of data available at publication, preliminary estimated benefits averaged about $92 per flight across all flights including those without benefit. Identified factors indicate the estimated benefit per flight was likely a conservative estimate. Benefit categories including home runs, cumulative small gains, and plan validation benefits are illustrated with specific examples observed during the operational evaluation.

Wing, David J.↗
NASA NTRS2019

SAFE50 Reference Design Study for Large-Scale High-Density Low-Altitude UAS Operations in Urban Areas

Enabling safe, routine, and high-density flight operations of small UAS at low-altitude over heavily populated urban centers presents a difficult challenge for emerging UAS Traffic Management (UTM) system concepts. Urban operations by definition involve flight over people, property, and infrastructure. Low-altitude urban environments - such as urban canyons – are one of the most difficult areas for UTM to consider. Mission concepts require routine operations in a cluttered radio-frequency (RF) environment with degraded or denied Global Positioning System (GPS) reception. Flights with any appreciable distance will be beyond visual and communications line-of-sight from ground operators. Timely detection and response to emergencies and onboard failures, which is critical for safe aircraft operation, will be difficult. This work seeks to establish a feasible reference autonomy architecture for autonomous vehicles in an urban UTM system, then verifying and validating this architecture within a complete UTM concept point-design and systems analysis study. In this paper, we present the results from the NASA SAFE50 conceptual design and systems study that investigates the trade-space of urban UTM operations. This advanced conceptual design study develops a feasible, verified, validated point-design solution. The SAFE50 point-design concept places emphasis on advanced, highly-autonomous, and highly-capable vehicles that favors intelligent onboard autonomy over direct human control with today's technologies and operating in today's urban environments. This paper focuses on an general overview of the design study, highlighting decisions made in the architectural solution. This paper will presents a summary of the study, architectures, and requirements. We present an overview of the architecture designs as derived from the top-level UTM system. The point-design has been implemented in both simulation and through flight testing of hardware design prototypes. The results from simulation and flight testing as part of the verification and validation process of the reference design study.

Ippolito, Corey A.↗
NASA NTRS2020

Stereo Combining NASA Technologies and Partnerships to Transform Current-Day Emergency Response Operations

STEReO brings together several technologies in Unmanned Aircraft Systems (UAS) Traffic Management (UTM), Autonomy, Communications, Human Factors, and Domain Expertise & Tools, aimed at providing scalability and flexibility, as well as operational resiliency to dynamic changes during a disaster event. Some of the concepts STEReO explores are: collaborative tools to ingest remote sensing information and distribute a common mission operating picture, apply ad-hoc communication networks to facilitate timely information sharing and communication of changes, vehicle-to-vehicle and onboard autonomy technologies ensure the safety and resiliency of operations, and apply NASA’s UAS traffic management system (UTM) as a public safety UAS Service Supplier (USS) to access and coordinate use of the airspace by both manned and unmanned operations. The potential benefits of STEReO include: standardized, cross-platform communication means increased interoperability and ease of cooperation/collaboration, increased situation awareness and common operating picture allow for earlier detection and decision making, and scalable to size and complexity of environment, operations, and mission objectives. This presentation gives an overview of the STEReO project and introduces a stakeholder workshop as a three-day activity to solicit input from the community of emergency response operators and related industry representatives.

Mercer, Joey S.↗