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.

SourceResearch connectionFrom yearThrough year

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

At least 865 records · Page 48

All sources NASA NTRS DOE OSTI

NASA NTRS2017

MESA: Message-Based System Analysis Using Runtime Verification

In this paper, we present a novel approach and framework for run-time verication of large, safety critical messaging systems. This work was motivated by verifying the System Wide Information Management (SWIM) project of the Federal Aviation Administration (FAA). SWIM provides live air traffic, site and weather data streams for the whole National Airspace System (NAS), which can easily amount to several hundred messages per second. Such safety critical systems cannot be instrumented, therefore, verification and monitoring has to happen using a nonintrusive approach, by connecting to a variety of network interfaces. Due to a large number of potential properties to check, the verification framework needs to support efficient formulation of properties with a suitable Domain Specific Language (DSL). Our approach is to utilize a distributed system that is geared towards connectivity and scalability and interface it at the message queue level to a powerful verification engine. We implemented our approach in the tool called MESA: Message-Based System Analysis, which leverages the open source projects RACE (Runtime for Airspace Concept Evaluation) and TraceContract. RACE is a platform for instantiating and running highly concurrent and distributed systems and enables connectivity to SWIM and scalability. TraceContract is a runtime verication tool that allows for checking traces against properties specified in a powerful DSL. We applied our approach to verify a SWIM service against several requirements.We found errors such as duplicate and out-of-order messages.

Message-based System↗

NASA NTRS2017

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. The present study is the final in a series of human-in-the-loop experiments designed to explore and test the various display and alerting requirements being incorporated into the minimum operational performance standards (MOPS) for a UAS-specific detect and avoid system that would replace the see and avoid function required of manned aircraft. Two display configurations were tested - an integrated display and a standalone display - and their impact on pilot response times and ability to maintain DAA well clear were compared. Results indicated that the current draft of the MOPS result in high-level performance and did not meaningfully differ by display configuration.

unmanned aircraft systems↗

NASA NTRS2017

Flight Test Evaluation of an Unmanned Aircraft System Traffic Management (UTM) Concept for Multiple Beyond-Visual-Line-of-Sight Operations

This study evaluates a traffic management concept designed to enable simultaneous operations of multiple small unmanned aircraft systems (UAS) in the national airspace system (NAS). A five-day flight-test activity is described that examined the feasibility of operating multiple UAS beyond visual line of sight (BVLOS) of their respective operators in the same airspace. Over the five-day campaign, three groups of five flight crews operated a total of eleven different aircraft. Each group participated in four flight scenarios involving five simultaneous missions. Each vehicle was operated BVLOS up to 1.5 miles from the pilot in command. Findings and recommendations are presented to support the feasibility and safety of routine BVLOS operations for small UAS.

UTM↗

NASA NTRS2017

Subject Matter Expert Evaluation of Multi-Flight Common Route Advisories

Traffic flow management seeks to balance the demand for National Airspace System (NAS) flight resources, such as airspace and airports, with the available supply. When forecasted weather blocks nominal air traffic routes, traffic managers must re-route affected flights for weather avoidance. Depending on the nature and scope of the weather, traffic managers may use pre-coordinated re-routes such as Playbook Routes or Coded Departure Routes, or may design ad hoc local re-routes. The routes of affected flights are modified accordingly. These weather avoidance routes will, of course, be less efficient than the nominal routes due to increased flight time and fuel burn. In current traffic management operations, the transition into a weather avoidance re-routing initiative is typically implemented more aggressively than the transition out of that initiative after the weather has dissipated or moved away. For example, strategic large-scale Playbook re-routes are sometimes left in place (as initially implemented) for many hours before being lifted entirely when the weather dissipates. There is an opportunity to periodically modify the re-routing plan as weather evolves, thereby attenuating its adverse impact on flight time and fuel consumption; this is called delay recovery. Multi-Flight Common Routes (MFCR) is a NASA-developed operational concept and associated decision support tool for delay recovery, designed to assist traffic managers to efficiently update weather avoidance traffic routes after the original re-routes have become stale due to subsequent evolution of the convective weather system. MFCR groups multiple flights to reduce the number of advisories that the traffic manager needs to evaluate, and also merges these flights on a common route segment to provide an orderly flow of re-routed traffic. The advisory is presented to the appropriate traffic manager who evaluates it and has the option to modify it using MFCRs graphical user interface. If the traffic manager finds the advisory to be operationally appropriate, he or she would coordinate with the Area Supervisor(s) of the sectors that currently control the flights in the advisory. When the traffic manager accepts the MFCR advisory via the user interface, the corresponding flight plan amendments would be sent to the displays of the appropriate sector controllers, using the Airborne Re-Routing (ABRR) capability which is scheduled for nationwide operation in 2017. The sector controllers would then offer this time-saving route modification to the pilots of the affected flights via datalink (or voice), and implement the corresponding flight plan amendment if the pilots accept it. MFCR is implemented as an application in the software environment of the Future Air traffic management Concepts Evaluation Tool (FACET). This paper focuses on an initial subject matter expert (SME) evaluation of MFCR. The evaluation covers MFCRs operational concept, algorithm, and user interface.

Traffic flow management↗

NASA NTRS2017

Initial Concept of Operations for Full Management by Trajectory

This document describes Management by Trajectory (MBT), a concept for future air traffic management (ATM) in which flights are assigned four-dimensional trajectories (4DTs) through a negotiation process between the Federal Aviation Administration (FAA) and flight operators that respects the flight operator's goals while complying with National Airspace System (NAS) constraints.

Fernandes, Alicia D.↗

NASA NTRS2017

Management by Trajectory Trade Study of Roles and Responsibilities Between Participants and Automation Report

This report describes a trade study of roles and responsibilities associated with the Management by Trajectory (MBT) concept. The MBT concept describes roles, responsibilities, and information and automation requirements for providing air traffic controllers and managers the ability to quickly generate, evaluate and implement changes to an aircraft's trajectory. In addition, the MBT concept describes mechanisms for imposing constraints on flight operator preferred trajectories only to the extent necessary to maintain safe and efficient traffic flows, and the concept provides a method for the exchange of trajectory information between ground automation systems and the aircraft that allows for trajectory synchronization and trajectory negotiation. The participant roles considered in this trade study include: airline dispatcher, flight crew, radar controller, traffic manager, and Air Traffic Control System Command Center (ATCSCC) traffic management specialists. The proposed allocation of roles and responsibilities was based on analysis of several use cases that were developed for this purpose as well as for walking through concept elements. The resulting allocation of roles and responsibilities reflects both increased automation capability to support many aviation functions, as well as increased flexibility to assign responsibilities to different participants - in many cases afforded by the increased automation capabilities. Note that the selection of participants to consider for allocation of each function is necessarily rooted in the current environment, in that MBT is envisioned as an evolution of the National Airspace System (NAS), and not a revolution. A key feature of the MBT allocations is a vision for the traffic management specialist to take on a greater role. This is facilitated by the vision that separation management functions, in addition to traffic management functions, will be carried out as trajectory management functions. This creates an opportunity for flexibility, allowing the traffic management specialist to carry out tasks that today can only be carried out by the controller currently in contact with the aircraft. This additional tasking for the traffic management specialist comes with requirements for workload management. An increased role for the Data-side (D-side) controller relative to the Radar-side (R-side) controller is a potential approach to mitigating workload for the traffic management specialist, as the D-side controller would have similar ability to perform separation management functions in what today might be considered the "trajectory management" timeframe. This analysis did not distinguish between the D-side and R-side controllers since in many cases the R-side controller works unassisted.

Fernandes, Alicia D.↗

NASA NTRS2017

Flight Test Evaluation of an Unmanned Aircraft System Traffic Management (UTM) Concept for Multiple Beyond-Visual-Line-of-Sight (BVLOS) Operations

UA↗

NASA NTRS2017

Comparison of Selected Weather Translation Products

Weather is a primary contributor to the air traffic delays within the National Airspace System (NAS). At present, it is the individual decision makers who use weather information and assess its operational impact in creating effective air traffic management solutions. As a result, the estimation of the impact of forecast weather and the quality of ATM response relies on the skill and experience level of the decision maker. FAA Weather-ATM working groups have developed a Weather-ATM integration framework that consists of weather collection, weather translation, ATM impact conversion and ATM decision support. Some weather translation measures have been developed for hypothetical operations such as decentralized free flight, whereas others are meant to be relevant in current operations. This paper does comparative study of two different weather translation products relevant in current operations and finds that these products have strong correlation with each other. Given inaccuracies in prediction of weather, these differences would not be expected to be of significance in statistical study of a large number of decisions made with a look-ahead time of two hours or more.

Kulkarni, Deepak↗

NASA NTRS2018

Unmanned Aircraft Systems Demand and Economic Benefit Forecast Study

This presentation describes the need to calculate projections for the demands and benefits of operating commercial unmanned aircraft within the NAS.

outreach↗

NASA NTRS2018

Warning Alert HITL Experiment Results

Minimum Operational Performance Standards (MOPS) are being developed to support the integration of Unmanned Aircraft Systems (UAS) in the National Airspace (NAS). Input from subject matter experts and multiple research studies have informed display requirements for Detect-and-Avoid (DAA) systems aimed at supporting timely and appropriate pilot responses to collision hazards. Phase 1 DAA MOPS alerting is designed to inform pilots if an avoidance maneuver is necessary; the two highest alert levels - caution and warning - indicate how soon pilot action is required and whether there is adequate time to coordinate with the air traffic controller (ATC). Additional empirical support is needed to clarify the extent to which warning-level alerting impacts DAA task performance. The present study explores the differential effects of the auditory and visual cues provided by the DAA Warning alert, and performance implications compared to caution-only alerting are discussed.

alerting↗

NASA NTRS2018

Impact of Different Trajectory Option Set Participation Levels within an Air Traffic Management Collaborative Trajectory Option Program

This paper presents the methodology and results of a Human-In-The-Loop (HITL) simulation study conducted in the Airspace Operations Laboratory at NASA Ames Research Center. This study is a part of NASA's ongoing research into developing an Integrated Demand Management (IDM) concept, whose aim is to improve traffic flow management (TFM) by coordinating the FAA's strategic Traffic Flow Management System (TFMS) with its more tactical Time-Based Flow Management (TBFM) system. The purpose of TFM is to regulate air traffic demand so that it is delivered efficiently through constrained airspace resources without exceeding their capacity limits. The IDM concept leverages a new TFMS capability called the Collaborative Trajectory Options Program (CTOP) to strategically pre-condition traffic demand flowing into a TBFM-managed arrival environment, where TBFM is responsible for managing traffic tactically by generating precise arrival schedules. Unlike other TFM tools, CTOP gives flight operators the option of submitting a set of user-preferred alternative trajectories for each flight. CTOP can then use these trajectory option sets (or TOSs) to find user-preferred alternative routes to reduce demand on an overloaded resource. CTOP's effectiveness in redistributing demand is limited, however, by the availability of flights with alternative routes. The research presented in this paper focuses on evaluating the impact on TFM operations by varying the percentage of flights that submit a multiple-option TOS ('TOS participation levels'). Results show the impact on overall system performance and on the rerouted flights themselves. The simulation used a Newark (EWR) airport arrival scenario, with en route weather affecting traffic inbound from the west. Participants were asked to control each of the three arrival flows (north, west, and south) to meet their individual capacity constraints while simultaneously ensuring efficient utilization of the capacity at the destination airport. A large, permeable convective weather cell located southeast of Chicago severely reduced the capacity of the west flow. The study evaluated the impact of five different TOS participation levels on CTOP's ability to re-allocate traffic from the west and improve TFM performance in terms of delay assignment and traffic delivery rate to the airport. Overall, the results showed that increasing TOS submissions allowed the overall system delays to be reduced and fairly distributed among the three arrival flows, at the same time achieving the airport throughput rate. Moreover, it was found that aircraft who submitted a TOS saw a greater reduction in delay, even when they were assigned longer routes. This was particularly true when fewer aircraft submitted a TOS. The results confirm that the CTOP operations with higher TOS participation levels helped utilize the overall National Airspace System (NAS) resources as well as benefited the users who participated.

Yoo, Hyo-Sang↗

NASA NTRS2018

Air Traffic Management Technology Demonstration - 3 (ATD-3): Operational Concept for the Integration of ATD-3 Capabilities Version 1.0

ATD-3 has developed four capabilities to address its goal and objectives. The four ATD-3 capabilities include: Dynamic Weather Routes (DWR), Multi-Flight Common Routes (MFCR), Traffic Aware Strategic Aircrew Requests (TASAR), and Dynamic Routes for Arrivals in Weather (DRAW). This document describes the long-term, mature vision for the use and incorporation of the ATD-3 capabilities into the National Airspace System (NAS). This vision describes their complementary interaction and the benefit capture that accrues from use. Recognizing that all capabilities are unlikely to be implemented in unison, each of the capabilities is designed and able to be implemented independently. As discrete portions of the integrated capabilities are planned, additional integration efforts should be undertaken to validate the complementary interactions and benefit pool are realized from the selected subset.

ConOps↗

NASA NTRS2018

Overview of NASA's Air Traffic Management - eXploration (ATM-X) Project

Projected increases in new vehicle types, new missions, and the continual growth in traditional (e.g., airlines, general aviation) aviation will require changes to the current air traffic system, particularly to accommodate the desire of operators to be more involved in air traffic decisions. To address these challenges, the National Airspace System needs to undergo a transformation to a more scalable, flexible, user-focused system that addresses safety and security requirements and resiliency for current and new users. A system designed to integrate modular software services, provided by users, third parties and government for air traffic management functions, will be scalable and more easily allow modernization and for collaboration between users and service providers. ATM-X is responding to NASA's pivot towards integrating projected new, diverse entrants into the NAS, while also leveraging NASA's prior ATM achievements that continue to improve traditional airspace operations. This project is a two-phased approach to conduct research and focused evaluations to assess the feasibility of a service-based approach and to identify critical design considerations to enable airspace access for new entrants, integrated with current traditional operations. Phase 1 research will be conducted to determine what is needed to reach the ATM-X goals based on specific use-cases to enable large-scale, passenger-carrying Urban Air Mobility operations in a metroplex environment, and also to improve traditional operations in the Northeast Region leveraging mature NASA technologies. Some of these evaluations will be conducted in simulations and field activities. Phase 2 will build upon Phase 1 towards more defined, focused research and field demonstrations in real-world environments to integrate multiple elements of a scalable, service-based ATM-X concept.

air traffic management↗

NASA NTRS2018

Safe2Ditch Autonomous Crash Management System for Small Unmanned Aerial Systems: Concept Definition and Flight Test Results

Small unmanned aerial systems (sUAS) have the potential for a large array of highly-beneficial applications. These applications are too numerous to comprehensively list, but include search and rescue, fire spotting, precision agriculture, etc. to name a few. Typically sUAS vehicles weigh less than 55 lbs and will be performing flight operations in the National Air Space (NAS). Certain sUAS applications, such as package delivery, will include operations in the close proximity of the general public. The full benefit from sUAS is contingent upon the resolution of several technological areas in order to provide an acceptable level of risk for widespread sUAS operations. Operations of sUAS vehicles pose risks to people and property on the ground as well as manned aviation. Several of the more significant sUAS technological areas include, but are not limited to: autonomous sense and avoid and deconfliction of sUAS from other sUAS and manned aircraft, communications and interfaces between the vehicle and human operators, and the overall reliability of the sUAS and constituent subsystems. While all of the technological areas listed contribute significantly to the safe execution of the sUAS flight operations, contingency or emergency systems can greatly contribute to sUAS risk mitigations to manage situations where the vehicle is in distress. The Safe2Ditch (S2D) system is an autonomous crash management system for sUAS. Its function is to enable sUAS to execute emergency landings and avoid injuring people on the ground, damaging property, and lastly preserving the sUAS and payload. A sUAS flight test effort was performed to test the integration of sub-elements of the S2D system with a representative sUAS multi-rotor.

Glaab, Louis J.↗

NASA NTRS2016

Reducing Departure Delays for Adjacent Center Airports using Time-Based Flow Management Scheduler: Checkbox On or Off?

The Federal Aviation Administration (FAA) has enhanced the Time-Based Flow Management (TBFM) scheduling tool with a "Checkbox ON" vs. "OFF" function which allows Traffic Management Coordinators (TMCs) to make room in a crowded arrival stream for a departure. When scheduling a departure, having the checkbox ON can delay the Scheduled Times of Arrivals (STAs) of the airborne flights upstream of the TBFM freeze horizons and can compress these flights to their minimum required spacing, thereby creating a slot for a departure. Hence, having the checkbox ON can reduce the frequent ground delays of aircraft departing near high volume airports but can increase delays for airborne arrivals. A Human-in-the-Loop (HITL) simulation compared arrival and departure delays to Newark Airport (EWR) with the checkbox ON vs. OFF as the default position. Three other conditions in this HITL involved various National Airspace System (NAS)-wide approaches for timely delivery of aircraft to the TBFM region. These conditions were: Baseline, using current Mile-in-Trail (MIT) spacing restrictions; Integrated Demand Management (IDM), where all aircraft were given departure times (Expect Departure Clearance Times, or EDCTs), ultimately based on the EWR Airport Arrival Rate; and IDM plus Required Time of Arrival (RTA), a flight deck tool which allowed some aircraft to meet a controlled time of arrival to the TBFM area more precisely. Results showed that the checkbox tool was powerful: with the checkbox ON, departure delays decreased and airborne delays increased, as predicted. However, assuming that the cost ratio of a minute of airborne delay to a minute of departure delay is in the range of 1.2 to 3, as commonly indicated by the literature, checkbox ON and checkbox OFF conditions showed approximately equal total delay costs, i.e., the cost of delays in the air balanced the cost of the delay on the ground. The three scheduling conditions also had approximately equal total delay costs, although a simulation artifact may have reduced the delays in the Baseline condition. In the debrief following the simulation, the TMCs concluded that the checkbox should be used flexibly depending on the current delay situation, and suggested modifications to the checkbox tool which would help them use it in this way, along with enhanced training. The relatively similar total cost of both checkbox default options in this simulation indicates that this might be a fruitful approach, and replace the necessity to have the checkbox rigidly set to either ON or OFF.

departure delay↗

NASA NTRS2016

NASA WorldWind: Open Source Visualization Technology for Earth Observation

NASA WorldWind: Open Source Visualization Technology for Earth Observation WorldWind, open source virtual globe technology for Java, iOS, Android and Web, is provided by NASA and is architected as API-centric modular componentry. This enable it to be continually optimized and feature-enriched in ways that allow applications based on this SDK (Software Development Kit) to benefit Earth Observation, especially Open Science, with minimal or no adjustment for the decade ahead. The next-generation National Airspace System (NAS) aviation management system for the U.S. Federal Aviation Administration, FAA, uses WorldWind, as do applications currently being developed by the European Space Agency, along with several other US and European government agencies and industry partners. This presentation will demonstrate several NASA open source use cases for WorldWind technology that include advances being made to optimize access to NetCDF and HDF data via WebWorldWind.NASA WorldWind: Multidimensional Geospatial Web Platform The ability to see spatial data in its native context is essential for that data to be appreciated whether by the scientific community, policy and decision-makers or the general public. Recently, the accessibility of spatial data has dramatically improved. Without the need to install an application, spatial data can now be experienced via any web browser, mobile devices included. For developers, by simply updating the app on your server, the latest version of your application is now immediately available to your entire usercommunity. Unlike other virtual globes such as Google Earth, NASA World Wind offers something very special, full control to customize the interface with any features or functionalities you might need. You decide how the data is accessed and experienced. This allows you to provide maximum value of the information to your user community. The web version of NASA WorldWind (WebWorldWind) has made it possible for a whole new suite of applications for managing and sharing spatial data. Apps built with this web version are ideal for immediate social media type activity and also facilitate delivery of sophisticated data exchange scenarios such as weather and climate research, disaster response, personal navigation, and industrial-strength tracking for transportation, supply chain, aviation and satellites. WebWorldWind is an application component, not an app in itself. It is written in JavaScript and provides the real world geographic context for spatial data and information visualization, using a rich set of shapes and graphic primitives. WebWorldWind also provides platform independence, while accommodating any number of data types. Web WorldWind runs on any platform via a browser, i.e., Internet Explorer, Firefox, Chrome and Safari. Features include, 3D virtual globe, 2D map with multiple projection choices (Mercator, Polar, UPS, Equirectangular), imagery and elevation import, extensible, data retrieval (via REST, WMS, WCS, WFS, Bing, User-Defined), decluttering, measurement, accurate line-ofsight, subsurface visualization, and more.

Open Source Mapping↗

NASA NTRS2016

The Collection of Human Factors Incident Reports via UAS Pilot Focus Groups

There is a need for incident data relevant to the operation of civilian unmanned aircraft systems (UAS) in the National Air Space (NAS). Currently, the tightly-restricted civilian UAS industry has produced relatively few incident reports that shed light on the human factors of UAS operations. An exploratory study is being conducted to examine the feasibility of using the critical incident technique (Flanagan, 1954) to collect reports from UAS pilots. The information is being used to identify areas where human factors guidelines will be of assistance. Experienced UAS pilots are participating in small focus groups in which they are prompted to describe critical incidents that either reveal a system flaw, or highlight a case where the human operator contributed to system resilience or mission success. To date, 90 incidents have been reported by UAS pilots. The de-identified incidents are being analyzed to identify contributing factors, with a focus on design issues that either hindered or assisted the pilot in dealing with the incident..

Hobbs, Alan↗

NASA NTRS2015

Unmitigated ACES Simulation Supporting Draft DAA MOPS Alerting

Realization of the expected proliferation of Unmanned Aircraft System (UAS) operations in the National Airspace System (NAS) depends on the development and validation of performance standards for UAS Detect and Avoid (DAA) Systems. The RTCA Special Committee 228 is charged with leading the development of draft Minimum Operational Performance Standards (MOPS) for UAS DAA Systems. NASA, as a participating member of RTCA SC-228 is committed to supporting the development and validation of draft requirements for DAA alerting system performance. A recent study conducted using NASA's ACES (Airspace Concept Evaluation System) simulation capability begins to address questions surrounding the development of draft MOPS for DAA alerting systems. ACES simulations were conducted to study the performance of an alerting scheme proposed by the SC-228 DAA Alerting sub-group. Analysis included but was not limited to: 1) correct alert (and their timeliness), 2) false alert (and their severity and duration), 3) missed alert, and 4) probability of an alert type at the time of loss of well clear. The results will be used by SC-228 to inform decisions about the alerting aspect of UAS DAA systems and future requirements development and validation efforts.

alerting↗