Search NASA⌕ Search

SEARCH · Search NASA

Results for “FAA”

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 325 records · Page 18

Models of Sector Aircraft Counts in the Presence of Local, Regional and Airport Constraints

Recently, the ATM community has made important progress in collaborative trajectory management through the introduction of a new FAA traffic management initiative called a Collaborative Trajectory Options Program (CTOP). FAA can use CTOPs to manage air traffic under multiple constraints (manifested as flow constrained areas or FCAs) in the system, and it allows flight operators to indicate their preferences for routing and delay options. CTOPs also permits better management of the overall trajectory of flights by considering both routing and departure delay options simultaneously. However, adoption of CTOPs in airspace has been hampered by many factors that include challenges in how to identify constrained areas and how to set rates for the FCAs. Decision support tools providing assistance would be particularly helpful in effective use of CTOPs. Such DSTs tools would need models of demand and capacity in the presence of multiple constraints. This study examines different approaches to using historical data to create and validate models of maximum flows in sectors and other airspace regions in the presence of multiple constraints. A challenge in creating an empirical model of flows under multiple constraints is a lack of sufficient historical data that captures diverse situations involving combinations of multiple constraints especially those with severe weather. The approach taken here to deal with this is two-fold. First, we create a generalized sector model encompassing multiple sectors rather than individual sectors in order to increase the amount of data used for creating the model by an order of magnitude. Secondly, we decompose the problem so that the amount of data needed is reduced. This involves creating a baseline demand model plus a separate weather constrained flow reduction model and then composing these into a single integrated model. A nominal demand model is a flow model (gdem) in the presence of clear local weather. This defines the flow as a function of weather constraints in neighboring regions, airport constraints and weather in locations that can cause re-routes to the location of interest. A weather constrained flow reduction model (fwx-red) is a model of reduction in baseline counts as a function of local weather. Because the number of independent variables associated with each of the two decomposed models is smaller than that with a single model, need for amount of data is reduced. Finally, a composite model that combines these two can be represented as fwx-red (gdem(e), l) where e represents non-local constraints and l represents local weather. The approaches studied to developing these models are divided into three categories: (1) Point estimation models (2) Empirical models (3) Theoretical models. Errors in predictions of these different types of models have been estimated. In situations when there is abundant data, point estimation models tend to be very accurate. In contrast, empirical models do better than theoretical models when there is some data available. The biggest benefit of theoretical models is their general applicability in wider range situations once the degree of accuracy of these has been established.

Kulkarni, Deepak↗

Methodology to Define Delivery Accuracy Under Current Day ATC Operations

In order to enable arrival management concepts and solutions in a NextGen environment, ground- based sequencing and scheduling functions have been developed to support metering operations in the National Airspace System. These sequencing and scheduling algorithms as well as tools are designed to aid air traffic controllers in developing an overall arrival strategy. The ground systems being developed will support the management of aircraft to their Scheduled Times of Arrival (STAs) at flow-constrained meter points. This paper presents a methodology for determining the undelayed delivery accuracy for current day air traffic control operations. This new method analyzes the undelayed delivery accuracy at meter points in order to understand changes of desired flow rates as well as enabling definition of metrics that will allow near-future ground automation tools to successfully achieve desired separation at the meter points. This enables aircraft to meet their STAs while performing high precision arrivals. The research presents a possible implementation that would allow delivery performance of current tools to be estimated and delivery accuracy requirements for future tools to be defined, which allows analysis of Estimated Time of Arrival (ETA) accuracy for Time-Based Flow Management (TBFM) and the FAA's Traffic Management Advisor (TMA). TMA is a deployed system that generates scheduled time-of-arrival constraints for en- route air traffic controllers in the US. This new method of automated analysis provides a repeatable evaluation of the delay metrics for current day traffic, new releases of TMA, implementation of different tools, and across different airspace environments. This method utilizes a wide set of data from the Operational TMA-TBFM Repository (OTTR) system, which processes raw data collected by the FAA from operational TMA systems at all ARTCCs in the nation. The OTTR system generates daily reports concerning ATC status, intent and actions. Due to its availability, ease of use, and vast collection of data across several airspaces it was determined that the OTTR data set would be the best method to utilize moving forward with this analysis. The particular variables needed for further analysis were determined along with the necessary OTTR reports, by working closely with the repository team additional analysis reports were developed that provided key ETA and STA information at the freeze horizon. One major benefit of the OTTR data is that using the correct reports the data across several airports could be analyzed over large periods of time. The OTTR data processes the TBFM data daily and is stored in various formats across several airspaces. This allowed us to develop our own parsing methods and raw data processing that would not rely on other computationally expensive tools that perform more in depth analysis of similar sets of data. The majority of this work consisted of the development of the ability to filter flights to create a subset of flights that could be considered undelayed, which is defined as a flight at the freeze horizon with an ETA and STA difference that was minimal or close to zero. This was a broad method that allowed the consideration of a large data set which consisted of all the traffic across a two month period in 2013, the hottest and coldest months, arriving into four airports: George Bush Intercontinental, Denver International, Los Angeles International, and Phoenix Sky Harbor.

delivery accuracy↗

Assessment of Delivery Accuracy in an Operational-Like Environment

In order to enable arrival management concepts and solutions in a Next Generation Air Transportation System (NextGen) environment, ground-based sequencing and scheduling functions were developed to support metering operations in the National Airspace System. These sequencing and scheduling tools are designed to assist air traffic controllers in developing an overall arrival strategy, from enroute down to the terminal area boundary. NASA developed a ground system concept and protoype capability called Terminal Sequencing and Spacing (TSAS) to extend metering operations into the terminal area to the runway. To demonstrate the use of these scheduling and spacing tools in an operational-like environment, the FAA, NASA, and MITRE conducted an Operational Integration Assessment (OIA) of a prototype TSAS system at the FAA's William J. Hughes Technical Center (WJHTC). This paper presents an analysis of the arrival management strategies utilized and delivery accuracy achieved during the OIA. The analysis demonstrates how en route preconditioning, in various forms, and schedule disruptions impact delivery accuracy. As the simulation spanned both enroute and terminal airspace, the use of Ground Interval Management - Spacing (GIM-S) enroute speed advisories was investigated. Delivery accuracy was measured as the difference between the Scheduled Time of Arrival (STA) and the Actual Time of Arrival (ATA). The delivery accuracy was computed across all runs conducted during the OIA, which included deviations from nominal operations which are known to commonly occur in real operations, such as schedule changes and missed approaches. Overall, 83% of all flights were delivered into the terminal airspace within +/- 30 seconds of their STA and 94% of flights were delivered within +/- 60 seconds. The meter fix delivery accuracy standard deviation was found to be between 36 and 55 seconds across all arrival procedures. The data also showed when schedule disruptions were excluded, the percentage of aircraft delivered within +/- 30 seconds was between 85 and 90% across the various arrival procedures at the meter fix. This paper illustrates the ability to meet new delivery accuracy requirements in an operational-like environment using operational systems and NATCA controller participants, while also including common events that might cause disruptions to the schedule and overall system.

Air Traffic Scheduling↗

Unmanned Aircraft Systems Traffic Management (UTM)

UTM is an 'air traffic management' ecosystem for uncontrolled operations. UTM utilizes industry's ability to supply services under FAA's regulatory authority where these services do not exist. UTM development will ultimately enable the management of large scale, low-altitude UAS operations. Operational concept will address beyond visual line of sight UAS operations under 400 ft. AGL. Information architecture, data exchange protocols, software functions. Roles/responsibilities of FAA and operators. Performance requirements.

UTM↗

An Investigation of Glaciated Cloud Capabilities in the NASA Glenn Icing Research Tunnel

In 2015 the FAA added Appendix D to Part 33 engine certification requirements that included Mixed Phase and Ice Crystal Icing to aircraft engine certification. Replicating the ice crystal environment that is seen in nature has proven to be a challenge, which multiple engine ground testing facilities and icing wind tunnels have achieved to varying degrees. The Icing Research Tunnel (IRT) at NASA Glenn has always been focused on super-cooled liquid water to produce FAA Part 23 and Part 25 regulations, targeting Appendix C and lately also Appendix O. However, due to a growing interest in the field of ice crystals and the high cost of operating engine icing facilities, the IRT staff have recently completed testing using the Multi-Element Sensor (also known as the multi-wire) to measure glaciated cloud conditions. Results indicate that turning off the heat to the nozzle air and water supply can create a stable, fully glaciated cloud in the test section for a small range of conditions: drop-size distribution values below 20 microns (median volumetric diameter), air temperatures as warm as -7 deg C, and airspeeds between 100 and 250 knots. These tests also revealed how varying the total temperature, airspeed, nozzle air pressure, and nozzle water pressure affect the glaciation of the IRT cloud.

ice water content↗

Unmanned Aerial Systems (UAS) Integration into the National Airspace System (NAS)

NASA's Unmanned Aerial Systems (UAS) integration into the National Air Space (NAS) project has been working closely with the FAA and RTCA Special Committee 228 to identify and break down barriers to UAS integration. A focus of this work is on detect and avoid (DAA) technologies. A pilot has responsibility to see and avoid other aircraft and to remain "well clear," using their best judgment (Federal Aviation Regulations (FAR) Sec. 91.113). For UAS to perform this function, the see function is replaced by sensors to detect the other aircraft. Secondly, the pilot judgment of well clear has to be replaced by a mathematical expression. For Phase 1 of this effort, a well clear violation was defined if all three of these conditions are true: a) the horizontal clearance is less than 4000 ft., and b) the vertical clearance is less than 450 ft., and c) the time to loss of well clear is less than 35 seconds. This definition was developed with a great deal of community input and testing to ensure interoperability with Air Traffic Control (ATC) and pilots of manned aircraft. Appropriate guidance, alerting and displays were developed to allow UAS, with the appropriate sensors, to effectively maintain well clear. This work contributed to FAA Technical Standard Orders: TSO-C211, Detect and Avoid and TSO-C212, ATAR for Traffic Surveillance. Phase 2 of this work extends the operational environment to include the terminal area and lesser capable aircraft that might not have the payload capability to carry the RADAR defined in Phase 1. This session reports on work from Phase 1 and initial work in Phase 2.

UAS↗

Detect and Avoid: Efforts from NASA's UAS Integration into the NAS Project

NASA's Unmanned Aerial Systems (UAS) integration into the National Air Space (NAS) project has been working closely with the FAA and RTCA Special Committee 228 to identify and break down barriers to UAS integration. A focus of this work is on detect and avoid (DAA) technologies. A pilot has responsibility to see and avoid other aircraft and to remain "well clear," using their best judgment (Federal Aviation Regulations (FAR) Sec. 91.113). For UAS to perform this function, the see function is replaced by sensors to detect the other aircraft. Secondly, the pilot judgment of well clear has to be replaced by a mathematical expression. For Phase 1 of this effort, a well clear violation was defined if all three of these conditions are true: a) the horizontal clearance is less than 4000 ft., and b) the vertical clearance is less than 450 ft., and c) the time to loss of well clear is less than 35 seconds. This definition was developed with a great deal of community input and testing to ensure interoperability with Air Traffic Control (ATC) and pilots of manned aircraft. Appropriate guidance, alerting and displays were developed to allow UAS, with the appropriate sensors, to effectively maintain well clear. This work contributed to FAA Technical Standard Orders: TSO-C211, Detect and Avoid and TSO-C212, ATAR for Traffic Surveillance. Phase 2 of this work extends the operational environment to include the terminal area and lesser capable aircraft that might not have the payload capability to carry the RADAR defined in Phase 1. This session reports on work from Phase 1 and initial work in Phase 2.

Detect and Avoid (DAA)↗

Ground Based Detect and Avoid

This presentation documents the results of an industry survey performed to help inform future research and requirements development regarding ground-based detect and avoid (GBDAA) systems. The author evaluated and summarized the current-state of existing GBDAA systems with a focus on system capabilities, current use cases, and concepts of operations. The survey included vendors such as Echodyne, Seamatica, and Raytheon, government organizations, including the Air Force and FAA, as well as members from the FAA's UAS Test Sites in New York, Alaska, Nevada, Virginia and North Dakota. High-level findings are provided as well as quotes from individuals involved in building and testing GBDAA systems. Conclusions include a lack of coordination between test sites, manufacturers and standards organizations. There is also a wide range of performance capabilities between test sites and systems. More work is required to define minimum operational performance standards for these systems, which are in a relatively immature state at the moment.

ground-based radar↗

Flyover-Noise Reduction of Commercial Aircraft via Reduced Slat Deflections and Modified Flight Procedures

Current regulation and operation of commercial aircraft result in flyover noise that generates public protest from residents well outside the recognized noise footprint of modern airports. This noise issue was recently exacerbated by the implementation of NextGen air-traffic control which uses GPS-navigation for predictable flight paths and improved efficiency. A side-effect of the narrow flight corridors is a perceived increase in noise level and annoyance experienced by the residents directly under the flight paths. As a possible solution to the community noise issue, the feasibility of a lower slat deflections and modified flight procedures were explored. To document the maximum potential noise reduction, field measurements were conducted on the ground at locations before and after slat deployment. For safety considerations, the stall margin of a lower slat deflection was computed for a realistic geometry based on a modern commercial aircraft. The logistics of setting lower slat angles on current aircraft were also investigated through discussions with the FAA (Federal Aviation Administration) and aircraft manufacturers. The results suggest that community flyover noise could be reduced via lower slat deflections during early approach, but that modifying current aircraft would be difficult due to existing control systems and hurdles in certification. Alternatively, modifications to existing flight procedures could reduce the perceived noise of the NextGen flight patterns. For next generation commercial aircraft, reduced slat deflections could be considered if mandated by FAA noise requirements during early approach.

Storms, Bruce L.↗

UTM RTT CWG Concept & Use Cases Package #2

The Concept & Use Cases Package #2: Technical Capability Level 3 document represents the collaborative research efforts between the FAA and NASA as joint members of the Unmanned Aircraft System Traffic Management (UTM) Research Transition Team (RTT). Contained in this document are the 1) Terms and Definitions, 2) Foundational Principles, 3) Concept Narratives, 4) Use Cases, 5) Operational Views, and 6) Roles and Responsibilities of actors interacting within what is considered to be encompassed by Technical Capability Level 3 UTM operating environments. The contents of Package #2 should NOT be considered established policy or construed as regulatory in nature. What is presented is meant to communicate the current, agreed upon understanding between the FAA and NASA on particular features of UTM as exemplified through use cases and concept narratives for the purposes of supporting joint NASA/Industry Demonstrations and the UTM Pilot Program. It is also meant to foster discussion and refinement of the concepts and approaches being pursued by the other RTT working groups.

RTT↗

Field Evaluation of the Baseline Integrated Arrival, Departure, and Surface Capabilities at Charlotte Douglas International Airport

NASA is currently developing a suite of decision support capabilities for integrated arrival, departure, and surface (IADS) operations in a metroplex environment. The effort is being made in three phases, under NASA's Airspace Technology Demonstration 2 (ATD-2) sub-project, through a strong partnership with the Federal Aviation Administration (FAA), air carriers, airport, and general aviation community. The Phase 1 Baseline IADS capabilities provide enhanced operational efficiency and predictability of flight operations through data exchange and integration, tactical surface metering, and automated coordination of release time of controlled flights for overhead stream insertion. The users of the IADS system include the personnel at the Charlotte Douglas International Airport (CLT) air traffic control tower, American Airlines ramp tower, CLT terminal radar approach control (TRACON), and Washington Center. This paper describes the Phase 1 Baseline IADS capabilities and field evaluation conducted at CLT from September 2017 for a year. From the analysis of operations data, it is estimated that 538,915 kilograms of fuel savings, and 1,659 metric tons of CO2 emission reduction were achieved during the period with a total of 944 hours of engine run time reduction. The amount of CO2 savings is estimated as equivalent to planting 42,560 urban trees. The results have also shown that the surface metering had no negative impact on on-time arrival performance of both outbound and inbound flights. The technology transfer of Phase 1 Baseline IADS capabilities has been made to the FAA and aviation industry, and the development of additional capabilities for the subsequent phases is underway.

Jung, Yoon C.↗

Simple Tool for Aircraft Noise-Reduction Route Design

The design of arrival and departure routes from an airport has to balance the conflicting requirements of fuel efficiency, airport capacity utilization and community emission and noise considerations. The commonly used tools for aircraft noise assessment are the FAA’s Integrated Noise Model (INM) and Aviation Environmental Design Tool (AEDT). These tools are suitable to generate precise noise contours. However, they are harder to use with other tools for route design optimization involving evaluation of a large number of aircraft trajectories. A simplified aircraft noise computation tool, named AIRNOISE, is developed for preliminary aircraft noise-reduction route design in this paper. AIRNOISE computes aircraft noise based on the same SAE-AIR-1845 procedures used by INM and AEDT. AIRNOISE does not consider components related to terrain and atmosphere adjustments. As a result, it is not only computationally efficient but also flexible to use for customized aircraft profiles. The aircraft noise results are compared with the FAA’s AEDT2b and show that the level of accuracy achieved by AIRNOISE can be used to reduce the number of route design options to a small number from a large pool for subsequent accurate analysis by INM.

Li, Jinhua↗

Field Evaluation of the Baseline Integrated Arrival, Departure, and Surface (IADS) Capabilities at Charlotte Douglas International Airport (CLT)

NASA is currently developing a suite of decision support capabilities for integrated arrival, departure, and surface (IADS) operations in a metroplex environment. The effort is being made in three phases, under NASA's Airspace Technology Demonstration 2 (ATD-2) sub-project, through a strong partnership with the Federal Aviation Administration (FAA), air carriers, airport, and general aviation community. The Phase 1 Baseline IADS capabilities provide enhanced operational efficiency and predictability of flight operations through data exchange and integration, tactical surface metering, and automated coordination of release time of controlled flights for overhead stream insertion. The users of the IADS system include the personnel at the Charlotte Douglas International Airport (CLT) air traffic control tower, American Airlines ramp tower, CLT terminal radar approach control (TRACON), and Washington Center. This paper describes the Phase 1 Baseline IADS capabilities and field evaluation conducted at CLT from September 2017 for a year. From the analysis of operations data, it is estimated that 538,915 kilograms of fuel savings, and 1,659 metric tons of CO2 emission reduction were achieved during the period with a total of 944 hours of engine run time reduction. The amount of CO2 savings is estimated as equivalent to planting 42,560 urban trees. The results have also shown that the surface metering had no negative impact on on-time arrival performance of both outbound and inbound flights. The technology transfer of Phase 1 Baseline IADS capabilities has been made to the FAA and aviation industry, and the development of additional capabilities for the subsequent phases is underway.

and Surface (IADS)↗

Automated Discovery of Flight Track Anomalies

As new technologies are developed to handle the complexities of the Next Generation Air Transportation System (NextGen), it is increasingly important to address both current and future safety concerns along with the operational, environmental, and efficiency issues within the National Airspace System (NAS). In recent years, the Federal Aviation Administration’s (FAA) safety offices have been researching ways to utilize the many safety databases maintained by the FAA, such as those involving flight recorders, radar tracks, weather, and many other high- volume sensors, in order to monitor this unique and complex system. Although a number of current technologies do monitor the frequency of known safety risks in the NAS, very few methods currently exist that are capable of analyzing large data repositories with the purpose of discovering new and previously unmonitored safety risks. While monitoring the frequency of known events in the NAS enables mitigation of already identified problems, a more proactive approach of finding unidentified issues still needs to be addressed. This is especially important in the proactive identification of new, emergent safety issues that may result from the planned introduction of advanced NextGen air traffic management technologies and procedures. Development of an automated tool that continuously evaluates the NAS to discover both events exhibiting flight characteristics indicative of safety-related concerns as well as operational anomalies will heighten the awareness of such situations in the aviation community and serve to increase the overall safety of the NAS. This paper discusses the extension of previous anomaly detection work to identify operationally significant flights within the highly complex airspace encompassing the New York area of operations, focusing on the major airports of Newark International (EWR), LaGuardia International (LGA), and John F. Kennedy International (JFK). In addition, flight traffic in the vicinity of Denver International (DEN) airport/airspace is also investigated to evaluate the impact on operations due to variances in seasonal weather and airport elevation. From our previous research, subject matter experts determined that some of the identified anomalies were significant, but could not reach conclusive findings without additional supportive data. To advance this research further, causal examination using domain experts is continued along with the integration of air traffic control (ATC) voice data to shed much needed insight into resolving which flight characteristic(s) may be impacting an aircraft's unusual profile. Once a flight characteristic is identified, it could be included in a list of potential safety precursors. This paper also describes a process that has been developed and implemented to automatically identify and produce daily reports on flights of interest from the previous day.

Matthews, Bryan↗

Integration of Dynamic Weather Routes Automation with Air/Ground Data Communications

The Dynamic Weather Routes (DWR) toolcontinuously and automatically analyzes airborne flights in en route airspace to identify flights where a route correction could save significant flight time and still avoid weather. A partnership between NASA, American Airlines (AA), and the FAA has enabled testing of DWR in real-world air traffic operations. En route Data Communications (Data Comm) could significantly reduce the controller and pilot workload needed to communicate DWR route changes under today’s voice-based operations and thereby enable more timely and frequent high-value corrections to weather avoidance routes. Sample data from the DWR trial at AA illustrate how Data Comm could improve DWR operations. Two operating concepts that integrate DWR with Data Comm are described:(1) route corrections are initiated by air traffic control and implemented using Airborne Reroutes and Data Comm, and (2) route corrections are initiated by the dispatcher and pilot and implemented via Data Comm. Both concepts align with Federal Aviation Administration (FAA) plans for implementation ofData Comm in en route airspace.

weather avoidance↗

Response Timing: Low Airspeed (Energy) Alerting

In response to NTSB Safety Recommendation A-14-043, the FAA was asked to task a panel of human factors, aviation operations, and aircraft design specialists, such as the Avionics Systems Harmonization Working Group (ASHWG), to develop design requirements for context-dependent low energy alerting systems for airplanes engaged in commercial operations. This recommendation is in association to the July 6, 2013, accident involving a Boeing 777-200ER, Korean registration HL7742, operating as Asiana Airlines flight 214, which was on approach to runway 28L when it struck a seawall at San Francisco International Airport (SFO), San Francisco, California. The FAA asked for human factor support from NASA in developing design requirements for context-dependent low energy alerting systems for airplanes engaged in commercial operations. Recently the ASHWG chair asked for continued support in examining flightcrew alert response timing and requested that NASA update the previous working paper on this subject. This product/paper will be provided to the ASHWG as part of the ongoing assignments from each of the ASHWG members in support of developing requirements and guidance for context-dependent low energy alerting systems for airplanes. The ASHWG is made up of interested parties from government and industry.

response timing↗

Airspace Technology Demonstration 3 (ATD-3): Dynamic Routes for Arrivals in Weather (DRAW) Technology Transfer Document Summary Version 2.0

Airspace Technology Demonstration – 3 (ATD-3) is part of NASA’s Airspace Operations and Safety Program (AOSP) – specifically, its Airspace Technology Demonstrations (ATD) Project. ATD-3 is a multi-year research and development effort which proposes to develop and demonstrate automation technologies and operating concepts that enable air navigation service providers and airspace users to continuously assess weather, winds, traffic, and other information to identify, evaluate, and implement workable opportunities for flight plan route corrections that can result in significant flight time and fuel savings in en route airspace. In order to ensure that the products of this tech-transfer are relevant and useful, NASA has created strong partnerships with the FAA and key industry stakeholders. This summary document and accompanying technology artifacts satisfy the third Research Transition Product (RTP) defined in the Applied Traffic Flow Management (ATFM) Research Transition Team (RTT) Plan, which is Dynamic Routes for Arrivals in Weather (DRAW). This technology transfer consists of artifacts for DRAW Arrival Metering (AM) Operations delivered in June 2018, DRAW AM updates, and DRAW Extended Metering (XM) Operations. Blue highlighting indicates the new or modified deliverables. Some of the artifacts in this technology transfer have distribution restrictions that need to be followed. Distribution information is noted in each section. DRAW is a trajectory-based system that combines the legacy Dynamic Weather Routes (DWR) weather avoidance technology with an arrival-specific rerouting algorithm and arrival scheduler to improve traffic flows on weather-impacted arrival routes into major airports. First, DRAW identifies flights that could be rerouted to more efficient Standard Terminal Arrival Routes (STARs) that may have previously been impacted by weather. Second, when weather is impacting the arrival routing, DRAW proposes simple arrival route corrections that enable aircraft to stay on their flight plan while avoiding weather. The DRAW system proposes reroutes early enough to allow Time Based Flow Management (TBFM) to make the necessary schedule adjustments. As a result, metering operations can be sustained longer and more consistently in the presence of weather because the arrival schedule accounts for the dynamic routing intent of arrival flights to deviate around weather. The first DRAW tech transfer in June 2018 focused on arrival metering operations with the DRAW algorithm implemented in the NASA Center TRACON Automation System (CTAS) automation software. This tech transfer delivery includes updates for DRAW implemented in FAA’s TBFM 4.7 automation software and preliminary research into DRAW for XM operations.

Isaacson, Douglas R.↗

UAS Service Supplier Checkout: How UTM Confirmed Readiness of Flight Tests with UAS Service Suppliers

NASA collaborated with industry partners to develop and test the small Unmanned Aircraft System (sUAS) Traffic Management (UTM) research platform, a software prototype used for developing airspace integration requirements for sUAS operations. The lessons learned from these activities will help inform the Federal Aviation Administration (FAA) on what is needed to safely manage sUAS operations. A core component of the UTM platform is the UAS Service Supplier (USS), which acts as a communications bridge to meet the regulatory and operational requirements. As the UTM partners began USS flight tests, NASA found that it was difficult to get all USSs functioning at comparable quality levels to ensure successful flight tests. Also, NASA anticipated that the FAA would encounter similar challenges when they begin to register USSs for operational use. These realizations led to the development of USS Checkout, a set of processes and tools designed to increase flight test efficiency. We learned that a good USS Checkout process is balanced for simplicity versus test coverage, and is amenable to automation. We also learned that when USS Checkout is a USS prerequisite for flight tests, flight tests were more efficient and effective.

Smith, Irene Skupniewicz↗