Results for “Operational flexibility” — Page 46

NASA NTRS2003

Transonic Unsteady Aerodynamics of the F/A-18E at Conditions Promoting Abrupt Wing Stall

A transonic wind tunnel test of an 8% F/A-18E model was conducted in the NASA Langley Research Center (LaRC) 16-Foot Transonic Tunnel (16-Ft TT) to investigate the Abrupt Wing Stall (AWS) characteristics of this aircraft. During this test, both steady and unsteady measurements of balance loads, wing surface pressures, wing root bending moments, and outer wing accelerations were performed. The test was conducted with a wide range of model configurations and test conditions in an attempt to reproduce behavior indicative of the AWS phenomenon experienced on full-scale aircraft during flight tests. This paper focuses on the analysis of the unsteady data acquired during this test. Though the test apparatus was designed to be effectively rigid. model motions due to sting and balance flexibility were observed during the testing, particularly when the model was operating in the AWS flight regime. Correlation between observed aerodynamic frequencies and model structural frequencies are analyzed and presented. Significant shock motion and separated flow is observed as the aircraft pitches through the AWS region. A shock tracking strategy has been formulated to observe this phenomenon. Using this technique, the range of shock motion is readily determined as the aircraft encounters AWS conditions. Spectral analysis of the shock motion shows the frequencies at which the shock oscillates in the AWS region, and probability density function analysis of the shock location shows the propensity of the shock to take on a bi-stable and even tri-stable character in the AWS flight regime.

Schuster, David M.↗

NASA NTRS2003

Lockheed Martin Response to the OSP Challenge

The Lockheed Martin Orbital Space Plane System provides crew transfer and rescue for the International Space Station more safely and affordably than current human space transportation systems. Through planned upgrades and spiral development, it is also capable of satisfying the Nation's evolving space transportation requirements and enabling the national vision for human space flight. The OSP System, formulated through rigorous requirements definition and decomposition, consists of spacecraft and launch vehicle flight elements, ground processing facilities and existing transportation, launch complex, range, mission control, weather, navigation, communication and tracking infrastructure. The concept of operations, including procurement, mission planning, launch preparation, launch and mission operations and vehicle maintenance, repair and turnaround, is structured to maximize flexibility and mission availability and minimize program life cycle cost. The approach to human rating and crew safety utilizes simplicity, performance margin, redundancy, abort modes and escape modes to mitigate credible hazards that cannot be designed out of the system.

Sullivan, Robert T.↗

NASA NTRS2001

A theoretical analysis of vacuum arc thruster performance

In vacuum arc discharges the current is conducted through vapor evaporated from the cathode surface. In these devices very dense, highly ionized plasmas can be created from any metallic or conducting solid used as the cathode. This paper describes theoretical models of performance for several thruster configurations which use vacuum arc plasma sources. This analysis suggests that thrusters using vacuum arc sources can be operated efficiently with a range of propellant options that gives great flexibility in specific impulse. In addition, the efficiency of plasma production in these devices appears to be largely independent of scale because the metal vapor is ionized within a few microns of the cathode electron emission sites, so this approach is well-suited for micropropulsion.

thruster↗

NASA NTRS2006

Software Defined Radio Standard Architecture and its Application to NASA Space Missions

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG's SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA's current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Andro, Monty↗

NASA NTRS2006

Space Telecommunications Radio Architecture (STRS)

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG's SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA s current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Reinhart, Richard C.↗

NASA NTRS2007

NASA's SDR Standard: Space Telecommunications Radio System

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG s SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA s current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Reinhart, Richard C.↗

NASA NTRS2007

Strategic Adaptation of SCA for STRS

The Space Telecommunication Radio System (STRS) architecture is being developed to provide a standard framework for future NASA space radios with greater degrees of interoperability and flexibility to meet new mission requirements. The space environment imposes unique operational requirements with restrictive size, weight, and power constraints that are significantly smaller than terrestrial-based military communication systems. With the harsh radiation environment of space, the computing and processing resources are typically one or two generations behind current terrestrial technologies. Despite these differences, there are elements of the SCA that can be adapted to facilitate the design and implementation of the STRS architecture.

Quinn, Todd↗

NASA NTRS1983

Control device for prosthetic urinary sphincter cuff

A device for controlling flow of fluid to and from a resilient inflatable cuff implanted about the urethra to control flow of urine therethrough. The device comprises a flexible bulb reservoir and a control unit that includes a manually operated valve that opens automatically when the bulb is squeezed to force fluid into the cuff for closing the urethra. The control unit also includes a movable valve seat member having a relatively large area exposed to pressure of fluid in a chamber that is connected to the cuff and which moves to a position in which the valve member is unseated by an abutment when fluid pressure in the chamber exceeds a predetermined value to thereby relieve excess fluid pressure in the cuff. The arrangement is such that the valve element is held closed against the seat member by the full differential in fluid pressures acting on both sides of the valve element until the seat member is moved away from the valve element to thus insure positive closing of the valve element until the seat member is moved out of engagement with the valve element by excess pressure differential.

Reinicke, Robert H.↗

NASA NTRS2009

Simulation of Attitude and Trajectory Dynamics and Control of Multiple Spacecraft

Agora software is a simulation of spacecraft attitude and orbit dynamics. It supports spacecraft models composed of multiple rigid bodies or flexible structural models. Agora simulates multiple spacecraft simultaneously, supporting rendezvous, proximity operations, and precision formation flying studies. The Agora environment includes ephemerides for all planets and major moons in the solar system, supporting design studies for deep space as well as geocentric missions. The environment also contains standard models for gravity, atmospheric density, and magnetic fields. Disturbance force and torque models include aerodynamic, gravity-gradient, solar radiation pressure, and third-body gravitation. In addition to the dynamic and environmental models, Agora supports geometrical visualization through an OpenGL interface. Prototype models are provided for common sensors, actuators, and control laws. A clean interface accommodates linking in actual flight code in place of the prototype control laws. The same simulation may be used for rapid feasibility studies, and then used for flight software validation as the design matures. Agora is open-source and portable across computing platforms, making it customizable and extensible. It is written to support the entire GNC (guidance, navigation, and control) design cycle, from rapid prototyping and design analysis, to high-fidelity flight code verification. As a top-down design, Agora is intended to accommodate a large range of missions, anywhere in the solar system. Both two-body and three-body flight regimes are supported, as well as seamless transition between them. Multiple spacecraft may be simultaneously simulated, enabling simulation of rendezvous scenarios, as well as formation flying. Built-in reference frames and orbit perturbation dynamics provide accurate modeling of precision formation control.

Stoneking, Eric T.↗

NASA NTRS2006

Space Telecommunications Radio Architecture (STRS): Technical Overview

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG s SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA's current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Reinhart, Richard C.↗

NASA NTRS2012

Review of Human Cognitive Performance in Spaceflight

Human space exploration is inherently hazardous, particularly for lon g duration (LD) missions (22 days or longer). Maintenance of cognitive functioning is essential, but flight environments pose numerous pote ntial risks to the brain and cognitive performance (eg, radiation, to xins, chronic stress, sleep deprivation, hypercarbia, fluid shifts, h ormone imbalances, and injury). There have been persistent anecdotal reports of cognitive deficits during missions, but an up?-to-date rev iew of the evidence for such changes has remained unavailable. Method s: We identified and reviewed English language publications found via electronic searches in PubMed, PsycInfo, Inspec, the NASA Technical Report Server, and the Defense Technical Information Center, plus rec ursive searches of publication bibliographies. Search terms included the word cognition, cognitive, or performance along with spaceflight, flight, mission, or closely related terms. Results: Inter?-study variability precluded meta?-analysis. Some 32 published studies involving cognitive assessment during spaceflight were identified, involving a total of 110 participants (mean: 3.4 participants per study). The lo ngest?-duration study spanned 438 days, with six additional studies i nvolving flight durations of 90 days, and 11 more studies involved fl ight durations exceeding 21 days. The available evidence failed to st rongly support or refute the existence of cognitive deficits in LD sp aceflight, in part due to inadequate power or control conditions. Evi dence of increased variability in cognitive performance during spacef light, both within and between individuals, was common. Discussion: T hese results represent a negative finding based on small numbers of s ubjects for any given cognitive function. The increased variability within and (particularly) between individuals highlights the potential danger of generalizing from case studies. A mismatch therefore remain s between anecdotal reports describing generalized cognitive slowing, attention and memory problems during missions and the experimental e vidence supporting such deficits. Since a major justification for man ned spaceflight rests with the cognitive flexibility of humans, addit ional studies and further analysis of existing operational data appea rs warranted.

Strangman, Gary↗

NASA NTRS2013

Development of Hybrid Product Breakdown Structure for NASA Ground Systems

The Product Breakdown Structure is traditionally a method of identification of the products of a project in a tree structure. It is a tool used to assess, plan, document, and display the equipment requirements for a project. It is part of a product based planning technique, and attempts to break down all components of a project in as much detail as possible, so that nothing is overlooked. The PBS for ground systems at the Kennedy Space Center is being developed to encompass the traditional requirements including the alignment of facility, systems, and components to the organizational hierarchy. The Ground Operations Product Breakdown Structure is a hybrid in nature in that some aspects of a work breakdown structure will be incorporated and merged with the Architecture Concept of Operations, Master Subsystem List, customer interface, and assigned management responsibility. The Ground Operations Product Breakdown Structure needs to be able to identify the flexibility of support differing customers (internal and external) usage of ground support equipment within the Kennedy Space Center launch and processing complex. The development of the Product Breakdown Structure is an iterative activity Initially documenting the organization hierarchy structure and relationships. The Product Breakdown Structure identifies the linkage between the customer program requirements, allocation of system resources, development of design goals, and identification logistics products. As the Product Breakdown Structure progresses the incorporation of the results of requirement planning for the customer occurs identifying facility needs and systems. The mature Product Breakdown Structure is baselined with a hierarchical drawing, the Product Breakdown Structure database, and an associated document identifying the verification of the data through the life cycle of the program/product line. This paper will document, demonstrate, and identify key aspects of the life cycle of a Hybrid Product Breakdown Structure. The purpose is to show how a project management and system engineering approach can be utilized for providing flexible customer service in an evolving manned space flight launch processing environment.

Monaghan, Mark W.↗

NASA NTRS2013

Development of Hybrid Product Breakdown Structure for NASA Ground Systems

The Product Breakdown Structure is traditionally a method of identification of the products of a project in a tree structure. It is a tool used to assess, plan, document, and display the equipment requirements for a project. It is part of a product based planning technique, and attempts to break down all components of a project in as much detail as possible, so that nothing is overlooked. The PBS for ground systems at the Kennedy Space Center is being developed to encompass the traditional requirements including the alignment of facility, systems, and components to the organizational hierarchy. The Ground Operations Product Breakdown Structure is a hybrid in nature in that some aspects of a work breakdown structure will be incorporated and merged with the Architecture Concept of Operations, Master Subsystem List, customer interface, and assigned management responsibility. The Ground Operations Product Breakdown Structure needs to be able to identify the flexibility of support differing customers (internal and external) usage of ground support equipment within the Kennedy Space Center launch and processing complex. The development of the Product Breakdown Structure is an iterative activity Initially documenting the organization hierarchy structure and relationships. The Product Breakdown Structure identifies the linkage between the customer program requirements, allocation of system resources, development of design goals, and identification logistics products. As the Product Breakdown Structure progresses the incorporation of the results of requirement planning for the customer occurs identifying facility needs and systems. The mature Product Breakdown Structure is baselined with a hierarchical drawing, the Product Breakdown Structure database, and an associated document identifying the verification of the data through the life cycle of the program/product line. This paper will document, demonstrate, and identify key aspects of the life cycle of a Hybrid Product Breakdown Structure. The purpose is to show how a project management and system engineering approach can be utilized for providing flexible customer service in an evolving manned space flight launch processing environment.

Monaghan, Mark W.↗

NASA NTRS2014

Five-Channel Infrared Laser Absorption Spectrometer for Combustion Product Monitoring Aboard Manned Spacecraft

Continuous combustion product monitoring aboard manned spacecraft can prevent chronic exposure to hazardous compounds and also provides early detection of combustion events. As future missions extend beyond low-Earth orbit, analysis of returned environmental samples becomes impractical and safety monitoring should be performed in situ. Here, we describe initial designs of a five-channel tunable laser absorption spectrometer to continuously monitor combustion products with the goal of minimal maintenance and calibration over long-duration missions. The instrument incorporates dedicated laser channels to simultaneously target strong mid-infrared absorption lines of CO, HCl, HCN, HF, and CO2. The availability of low-power-consumption semiconductor lasers operating in the 2 to 5 micron wavelength range affords the flexibility to select absorption lines for each gas with maximum interaction strength and minimal interference from other gases, which enables the design of a compact and mechanically robust spectrometer with low-level sensitivity. In this paper, we focus primarily on absorption line selection based on the availability of low-power single-mode semiconductor laser sources designed specifically for the target wavelength range.

Briggs, Ryan M.↗

NASA NTRS2017

The Generic Resolution Advisor and Conflict Evaluator (GRACE) for Detect-And-Avoid Systems

Java Architecture for Detect-And-Avoid (DAA) Extensibility and Modeling (JADEM) was developed at NASA Ames Research Center as a research and modeling tool for Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS). UAS will be required to have DAA systems in order to fulfill the regulatory requirement to remain well clear'' of other traffic. JADEM supports research on technological requirements and Minimum Operational Performance Standards (MOPS) for UAS DAA systems by providing a flexible and extensible software platform that includes models and algorithms for all major DAA functions. This paper describes one of these algorithms, the Generic Resolution Advisor and Conflict Evaluator (GRACE). GRACE supports two core DAA functions: threat evaluation and guidance. GRACE is generic in the sense that it is designed to work with any aircraft or sensor type (both cooperative and non-cooperative), and to be used in various applications and DAA guidance concepts, thus supporting evolving MOPS requirements and research. GRACE combines flexibility, robustness, and computational efficiency. It has modest memory requirements and can handle multiple cooperative and noncooperative intruders. GRACE has been used as a core JADEM component in several real-time and fast-time experiments, including human-in-the-loop simulations and live flight tests.

detect and avoid↗

NASA NTRS2016

International Space Station (ISS) Payload Autonomous Operations Past, Present and Future

Draper Laboratorys Timeliner is a scripting and automation system that runs onboard computers in the International Space Station (ISS). Timeliner is fully integrated with ISS and can be used to automate ISS operations tasks. Some of the most challenging aspects of operating a payload in low earth orbit are communication delays, ground equipment failures, and human errors. How does a Payload Developer (PD) know their equipment is operating nominally and collecting science in the most efficient way possible or even powered at any given time? During a ground Loss of Signal (LOS) data outage, PDs have no insight into their experiments state, and benefit greatly from Timeliner scripts executing on ISS to perform telemetry monitoring and commanding operations. This paper will discuss current software designs, and new operational uses for Timeliner. Existing Timeliner capabilities discussed will include: autonomous EXPRESS Rack activation and deactivation; autonomous science data downlinks; Minus Eighty Degree Freezer (MELFI) Dewar autonomous safing; JAXA and ESA module autonomous payload facility safing; as well as many others. New operational concepts discussed will include allowing Timeliner on the payload computer to issue core commands (Thermal, Power, Fire Detection), creation of new ground tools that will monitor the current status of Payload Racks as well as all the messaging from autonomous scripts executing, decreasing approval time for Timeliner bundles, and opening up the Payload MDM Enhanced Processor Integrated Communications Card (EPIC) interface. The EPIC interface could provide a new crew interface for PL Timeliner execution. The new interface could operate on either a Payload Computer System (PCS) or a Station Support Computer (SSC) that is plugged into either the Payload LAN or the Operations LAN which will make communicating to the PL MDM more flexible and greatly increase band width for communication.

Space Mission Automation↗

NASA NTRSDate not supplied

Assessing Helicopter Pilots’ Detect and Avoid and Collision Avoidance Performance With ACAS Xr

The latest variant of the Federal Aviation Administration’s Airborne Collision Avoidance System (ACAS X) is being designed for both crewed and uncrewed rotorcraft. Referred to as ACAS Xr, the system joins a suite of other ACAS X variants poised to replace the Traffic Alert and Collision Avoidance System (TCAS II). ACAS Xr is tuned to support current-day helicopter platforms as well as electric Vertical Takeoff and Landing (eVTOL) vehicles that are still under development. Given this flexibility, ACAS Xr may be used by helicopter crews currently in operation or by remotely-operated eVTOL aircraft in the emerging Advanced Air Mobility (AAM) market. To cover the range of potential uses, two distinct configurations are being proposed for ACAS Xr: Collision Avoidance System (CAS) and Detect and Avoid (DAA). Under the CAS configuration, ACAS Xr provides minimal caution-level alerting but issues directive warning-level alerting and guidance. The DAA configuration, by contrast, provides caution-level alerting and guidance, in addition to the warning-level alerting and guidance. The current study was performed as part of the National Aeronautics and Space Administration’s AAM project. Six helicopter pilots were recruited to fly a variety of scripted traffic scenarios in a full-motion, crewed eVTOL simulator. Participants flew 60 encounters over two days, reacting to pre-recorded intruder aircraft that were scripted to fly into the participant’s aircraft from different approach angles, relative altitudes, and during different phases of flight. The pilots flew half of the encounters with the CAS configuration and half with the DAA configuration. Within each block of 30 encounters, pilots experienced 10 conflicts while in cruise, 10 in hover, and 10 while on approach to a heliport. Results showed that pilot response times were consistently under 5 seconds for RAs and under 10 seconds for DAA alerts, when present, during all three phases of flight. Unsurprisingly, the DAA configuration was associated with lower rates of en-route and high-severity losses of DAA well clear compared to the CAS configuration in all phases of flight except for the terminal area. Rates of losses of DAA well clear were found to be substantially higher in the Hover scenario, compared to Cruise. Pilots failed to fully comply with RAs at a rate of 0.10-0.18 in all conditions except for the DAA configuration in the Hover scenario, which was associated with a higher non-compliance rate of 0.4 due to Descend RAs issued at low altitudes. The implications of these results with regards to the ongoing development of ACAS Xr is discussed.

air taxis↗

NASA NTRSDate not supplied

Assessing Helicopter Pilots’ Detect and Avoid and Collision Avoidance Performance with ACAS Xr

The latest variant of the Federal Aviation Administration’s Airborne Collision Avoidance System (ACAS X) is being designed for both crewed and uncrewed rotorcraft. Referred to as ACAS Xr, the system joins a suite of other ACAS X variants poised to replace the Traffic Alert and Collision Avoidance System (TCAS II). ACAS Xr is tuned to support current-day helicopter platforms as well as electric Vertical Takeoff and Landing (eVTOL) vehicles that are still under development. Given this flexibility, ACAS Xr may be used by helicopter crews currently in operation or by remotely-operated eVTOL aircraft in the emerging Advanced Air Mobility (AAM) market. To cover the range of potential uses, two distinct configurations are being proposed for ACAS Xr: Collision Avoidance System (CAS) and Detect and Avoid (DAA). Under the CAS configuration, ACAS Xr provides minimal caution-level alerting but issues directive warning-level alerting and guidance. The DAA configuration, by contrast, provides caution-level alerting and guidance, in addition to the warning-level alerting and guidance. The current study was performed as part of the National Aeronautics and Space Administration’s AAM project. Six helicopter pilots were recruited to fly a variety of scripted traffic scenarios in a full-motion, crewed eVTOL simulator. Participants flew 60 encounters over two days, reacting to pre-recorded intruder aircraft that were scripted to fly into the participant’s aircraft from different approach angles, relative altitudes, and during different phases of flight. The pilots flew half of the encounters with the CAS configuration and half with the DAA configuration. Within each block of 30 encounters, pilots experienced 10 conflicts while in cruise, 10 in hover, and 10 while on approach to a heliport. Results showed that pilot response times were consistently under 5 seconds for RAs and under 10 seconds for DAA alerts, when present, during all three phases of flight. Unsurprisingly, the DAA configuration was associated with lower rates of en-route and high-severity losses of DAA well clear compared to the CAS configuration in all phases of flight except for the terminal area. Rates of losses of DAA well clear were found to be substantially higher in the Hover scenario, compared to Cruise. Pilots failed to fully comply with RAs at a rate of 0.10-0.18 in all conditions except for the DAA configuration in the Hover scenario, which was associated with a higher non-compliance rate of 0.4 due to Descend RAs issued at low altitudes. The implications of these results with regards to the ongoing development of ACAS Xr is discussed.

air taxis↗