Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “alertness”

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 433 records · Page 24

Pilot Evaluation of a UAS Detect-and-Avoid System's Effectiveness in Remaining Well Clear

Unmanned aircraft will equip with a detect-and-avoid (DAA) system that enables them to comply with the requirement to "see and avoid" other aircraft, an important layer in the overall set of procedural, strategic and tactical separation methods designed to prevent mid-air collisions. Regulators will establish minimum operating standards for DAA effectiveness, but different combinations of algorithms, displays and procedures could be used to meet those standards. The research presented in this paper indicates the effectiveness of the combined pilot-DAA system as a function of the DAA design requirements and provides data that may be used to model the behavior of pilots when employing such systems. Two simulations involving 21 professional unmanned aircraft system (UAS) pilots evaluated eight different DAA system designs in order to assess their ability to maintain the "well clear" separation standard, i.e., the state of maintaining a safe distance from other aircraft that would not normally cause the initiation of a collision avoidance maneuver by either aircraft. When the traffic display was integrated with the primary mission map directly in front of the pilot, there were fewer losses of well clear. Greater warning time provided to the pilot was strongly correlated with success in remaining well clear. Pilots' ability to separate from aircraft with cooperative and non-cooperative surveillance systems was nearly the same after accounting for the amount of alert time provided in each encounter, although the limited surveillance volume for the airborne-equipped aircraft meant alerts tended to occur later and therefore were more difficult to resolve.

detect-and-avoid↗

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

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

detect and avoid↗

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project: ACAS Xu Engineering Analysis Results

This presentation provides an overview of the results from a two-part engineering analysis conducted as part of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project. Part one of this analysis examined how to present resolution advisories (RAs) issued by Airborne Collision Avoidance System (ACAS) Xu, which can be in the vertical dimension, the horizontal dimension, or both (i.e., "blended"). The study varied the appearance of the alerting and the verbiage used in the aural alerts. Results revealed high acceptability ratings for the appearance of the RA guidance. Part two of the analysis assessed pilot acceptability of varying levels of automation in the collision avoidance (CA) task. Pilots experienced conditions in which ACAS Xu RAs were executed either manually or automatically (i.e., auto-Collision Avoidance). In some conditions the return to a previously filed course was also executed automatically (auto-Return to Course). Results indicated that improvements are needed to how the state of the automation is presented. Implications of these findings are also discussed.

Detect and Avoid↗

A Comparison of Two Terminal Area Detect and Avoid Well Clear Definitions

Technical requirements are currently under development for a detect and avoid system (DAA) that would support the operation of Unmanned Aircraft Systems (UAS) within the National Airspace System (NAS). Such a system would aid UAS operators in maintaining sufficient separation, or "well clear", from other aircraft in their vicinity. The first set of technical standards for a UAS DAA system (referred to as "Phase 1" requirements) was limited to UAS operations transiting through Class D, E, and G airspace to, or from, Class A (or special-use) airspace. Explicitly out of scope of the Phase 1 requirements was the operation of UAS within terminal airspace in the NAS. Fern, Rorie, Roberts and Monk (2018) explored the application of a Phase 1 DAA system within Class D terminal airspace in a human-in-the-loop simulation. The results of the study demonstrated a poor fit of the Phase 1 DAA well clear (DWC) definition to these terminal operations. The original DWC definition was designed for the en-route environment and could not account for the complex, tightly-choreographed nature of traffic typically found near an airport. The interaction of the en-route DWC definition and the terminal area traffic led to excessive DAA alerting against safely-separated traffic. The frequent alerting quickly degraded pilots' ability to discriminate between encounters where a maneuver was or was not necessary. This resulted in slower response times, higher rates of losses of DAA well clear, and more severe losses of DAA well clear than had been observed in previous DAA research (e.g., Rorie et al., 2017). The current paper reports on a follow-on study to Fern et al. (2018) that tested two DWC definitions designed to accommodate standard terminal area operating procedures, such as traffic in the downwind leg of a VFR traffic pattern while the UAS is on final. The two definitions utilized identical horizontal and vertical thresholds but differed in whether or not Tau (a function that takes into account the closure rate of two aircraft) was included as a part of the DWC hazard zone. The "Tau" DWC candidate definition nominally extended the DWC hazard zone by 15 seconds in the direction of the intruder aircraft, while the "No Tau" DWC candidate definition did not extend the DWC hazard zone. The results of this follow-on study indicated that both candidate definitions improved pilot and DAA system performance relative to Fern et al (2018). Pilot response times and rates of losses of DWC returned to levels comparable to earlier research in the en-route environment. Several important differences between the two DWC candidate definitions, however, are also discussed.

Terminal Area↗

Evaluating Performance of UAS Detect-And-Avoid System Using a Fast-Time Simulation Tool

Most unmanned aircraft systems will be required to be equipped with a Detect-and-Avoid (DAA) system. The surveillance performance of the DAA system to detect and track intruder aircraft will depend on the encounter geometries that unmanned aircraft are expected to have with other aircraft in the airspace. The performance of DAA alerting and avoidance system is also dependent on the timeliness of alerting for UAS pilots to give a sufficient time to determine and command a resolution maneuver to avoid well clear separation violations. This presentation introduces general background of UAS DAA systems and concept of well clear separation standard to satisfy see and avoid regulations. The presentation shows the several UAS mission profiles and analysis of the encounter geometries that were simulated using historical VFR traffic data and some proposed UAS missions. This presentation introduces several potential metrics for evaluating the performance of a DAA system and shows the results that measured through fast-time simulation with traffic scenarios that include NAS-wide VFR manned aircraft and IFR UAS flights. At the end, some research areas will be briefly discussed.

UAS↗

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project: Low SWaP HITL 2, SC-228 Outbrief, EO/IR & ATAR Breakout

This presentation provides an overview of a recently completed human-in-the-loop simulation, conducted as part of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project. This study explored the differential effects of four low size, weight, and power radar declaration ranges on pilot and system performance. Pilots were to avoid DAA well clear against cooperative and non-cooperative aircraft under 1.5, 2, 2.5, and 3 nautical mile non-cooperative detection ranges. Results revealed that pilot performance was primarily influenced by warning-level alert duration, with sufficient alerting time being most prevalent at 2.5 nautical miles and above.

Monk, Kevin J.↗

Applying Sensor Uncertainty Mitigation Schemes to Detect-and-Avoid Systems

Impact of sensor noise on the performance of Detect-And-Avoid (DAA) systems can be reduced by implementing various mitigation schemes. This paper evaluates the Sensor Uncertainty Mitigation (SUM) method, implemented in the Detect and Avoid Alerting Logic for Unmanned Systems (DAIDALUS) algorithm, a reference implementation in the DAA minimum operational performance standards. DAIDALUS SUM performance is evaluated using a few safety and operational suitability metrics and compared with more traditional approaches using static safety buffers. A large number of encounters representative of low-speed unmanned aircraft against non-cooperative manned aircraft are simulated and evaluated. An air-to-air radar model produces representative sensor noise for the DAA system. Results show that increasing the tunable parameters for horizontal and vertical uncertainty in DAIDALUS SUM improves the safety metric at the cost of increasing the number of system alerts leading to increased workload. A range of SUM parameters is recommended as suitable values for the type of operations considered for this work. General trends and optimal SUM configurations were found to be nearly the same for two large and very different encounter data sets.

detect and avoid↗

An Approach for Defining IASMS Services, Functions, and Capabilities

Assuring safety in the NAS with the inclusion of new entrants, such as Advanced Air Mobility (AAM), will require overcoming unique safety challenges that result from combining innovative technologies with novel airspace concepts for moving people and cargo using autonomous vehicles. The focus of the In-time Aviation Safety Management System (IASMS) is to overcome AAM’s safety assurance challenges. The IASMS Concept of Operations (ConOps) describes an interconnected set of services, functions, and capabilities (SFCs) designed to manage operational risks, identify unknown risks, and inform system designs. This paper describes an approach for defining SFCs based on technology trends in research, assessment of known and unknown risks in voluntary safety reports, and causal and contributing factors in aviation accidents and incidents. This approach would identify potential SFCs that further expand the Monitor, Assess, and Mitigate (M-A-M) functionality that represents the enabling framework of the IASMS. Safety implications that will result from integration of AAM in the transformation of the National Airspace System (NAS) were addressed in National Academies committees reports on AAM and IASMS. Development of a ConOps for IASMS was a top recommendation and can be represented as a reframing of safety assurance that builds on real-time alerting such as the Traffic Alert and Collision Avoidance System, and adds the more encompassing in-time temporal parameter in recognition of the different timelines for collecting and assessing safety data for risk mitigations. For example, mining for safety trends from data sources such as the Aviation Safety Information Analysis and Sharing system occurs over a longer time period. Research on AAM operations poses that SFCs can be designed to monitor the safety margin appropriate for AAM including with regards to the distance between current flight parameters and nominal ideal conditions. These in-time comparisons will become more complex as the density of operations increases at least in certain areas and can include planned and actual 4D trajectory, and in-time comparisons having implications on conflict modeling and prediction including expected and actual departure time, fix/waypoint crossing times, and arrival time. These comparisons would be integrated as part of SFCs that redefine and inform new safety margin. An increased safety margin improves management of operational risks while reducing the potential for anomalies. An increased safety margin also has implications for operator confidence in the certainty of its operations and trust in automation. Technology trends in research could be used to refine existing SFCs and define needs for additional SFCs that provide safety improvements to the design and operation of vehicles, airspace design, and operator performance requirements. NASA is developing innovative approaches to safeguard against major accidents and incidents that have occurred in the NAS and those anticipated with the inclusion of envisioned AAM operations. The innovations use operational performance data to monitor, detect, and predict flight variations exceeding safe nominal patterns, such as would be caused by navigational error, severe weather complications, or hijacking of UAS controls. These innovative approaches have high potential to prevent accidents and incidents in the new AAM era. It is anticipated that elements of the innovations will evolve into SFCs for the IASMS. Voluntary safety reports can be monitored to identify anomalies related to design or operational performance risks. Reports could be periodically monitored and assessed for specific topics. Reports might serve as weak signals or precursors indicative of emergent risk such as when combined with other safety information. The architecture could include SFCs that are based on voluntary safety reports recognizing the periodic temporal nature of data analysis. As previously mentioned, aviation accidents with their causal and contributing precursors can inform the need for SFCs in the IASMS. Accidents and incidents at San Francisco International Airport such as Asiana 214 and Air Canada 759 illustrate how combinations of different factors lead to increased risk. These types of precursors and different factors have implications on the types of SFCs that could be needed to monitor and manage different sources and types of design and operational risk. Continuing to assure the safety of AAM as designs and operations gain in complexity can be accompanied by defining SFCs that also increase in complexity. These SFCs can leverage information from findings and recommendations synthesized across on-going research, voluntary safety reports, and accident and incident reports. These SFCs can serve to refine accuracy of algorithms and resolve limitations with current practices. The IASMS architecture represents the framework for the SFCs and their critical role in safety assurance.

In-Time Aviation Safety Management System↗

The Zwicky Transient Facility: Data Processing, Products, and Archive

The Zwicky Transient Facility (ZTF) is a new robotic time-domain survey currently in progress using the Palomar 48-inch Schmidt Telescope. ZTF uses a 47 square degree field with a 600 megapixel camera to scan the entire northern visible sky at rates of ∼3760 square degrees/hour to median depths of g ~ 20.8 and r ~ 20.6 mag (AB, 5σ in 30 sec). We describe the Science Data System that is housed at IPAC, Caltech. This comprises the data-processing pipelines, alert production system, data archive, and user interfaces for accessing and analyzing the products. The real-time pipeline employs a novel image-differencing algorithm, optimized for the detection of point-source transient events. These events are vetted for reliability using a machine-learned classifier and combined with contextual information to generate data-rich alert packets. The packets become available for distribution typically within 13 minutes (95th percentile) of observation. Detected events are also linked to generate candidate moving-object tracks using a novel algorithm. Objects that move fast enough to streak in the individual exposures are also extracted and vetted. We present some preliminary results of the calibration performance delivered by the real-time pipeline. The reconstructed astrometric accuracy per science image with respect to Gaia DR1 is typically 45 to 85 milliarcsec. This is the RMS per-axis on the sky for sources extracted with photometric S/N ≥10 and hence corresponds to the typical astrometric uncertainty down to this limit. The derived photometric precision (repeatability) at bright unsaturated fluxes varies between 8 and 25 millimag. The high end of these ranges corresponds to an airmass approaching ∼2—the limit of the public survey. Photometric calibration accuracy with respect to Pan-STARRS1 is generally better than 2%. The products support a broad range of scientific applications: fast and young supernovae; rare flux transients; variable stars; eclipsing binaries; variability from active galactic nuclei; counterparts to gravitational wave sources; a more complete census of Type Ia supernovae; and solar-system objects.

Frank J. Masci↗

The Zwicky Transient Facility: Science Objectives

The Zwicky Transient Facility (ZTF), a public–private enterprise, is a new time-domain survey employing a dedicated camera on the Palomar 48-inch Schmidt telescope with a 47 sq. deg field of view and an 8 second readout time. It is well positioned in the development of time-domain astronomy, offering operations at 10% of the scale and style of the Large Synoptic Survey Telescope (LSST) with a single 1-m class survey telescope. The public surveys will cover the observable northern sky every three nights in g and r filters and the visible Galactic plane every night in g and r. Alerts generated by these surveys are sent in real time to brokers. A consortium of universities that provided funding (“partnership”) are undertaking several boutique surveys. The combination of these surveys producing one million alerts per night allows for exploration of transient and variable astrophysical phenomena brighter than r ~20.5 on timescales of minutes to years. We describe the primary science objectives driving ZTF, including the physics of supernovae and relativistic explosions, multi-messenger astrophysics, supernova cosmology, active galactic nuclei, and tidal disruption events, stellar variability, and solar system objects.

Matthew J. Graham↗

Evaluation of Sensor Uncertainty Mitigation Methods for Detect-and-Avoid Systems

The impact of sensor noise on the performance of Detect-And-Avoid (DAA) systems can be reduced by implementing various mitigation schemes. This paper evaluates two such methods. One of them is the Sensor Uncertainty Mitigation (SUM) method, implemented in the Detect and Avoid Alerting Logic for Unmanned Systems (DAIDALUS) algorithm, a reference implementation in the DAA minimum operational performance standards. The second method is the Virtual Intruder State Aggregation (VISA), which averages multiple subsequent intruder states extrapolated to the current (most recent) time into a single ``aggregated`` intruder state. The VISA method can be used either individually as a sensor noise mitigation method in its own right, or in combination with DAIDALUS SUM. The performance of these methods is evaluated using three safety and operational suitability metrics and compared with a baseline configuration using static safety buffers. A large number of encounters representative of low-speed unmanned aircraft against non-cooperative manned aircraft, not equipped with a broadcasting transponder or ADS-B out system, are simulated and evaluated. An air-to-air radar model produces representative sensor noise for the DAA system. Results show that increasing the DAIDALUS SUM parameters for horizontal and vertical uncertainty improves the safety metric at the cost of increasing the number of actionable alerts leading to increased workload. A range of SUM parameters is recommended as suitable values for the type of operations considered for this work. VISA was found to be almost as effective as other noise mitigation methods even when it was used alone. Combining VISA with DAIDALUS SUM achieved the best performance among all investigated methods used with DAIDALUS. General trends and optimal SUM configurations were found to be nearly the same for two large and very different encounter data sets.

Detect-and-Avoid Systems↗

DDOTI Observations of Gravitational-Wave Sources Discovered in O3

We present optical follow-up observations with the Deca-Degree Optical Transient Imager (DDOTI) telescope of gravitational-wave (GW) events detected during the Advanced LIGO and Advanced Virgo O3 observing run. DDOTI is capable of responding to an alert in a few minutes, has an instantaneous field of about 69 deg2, and obtains 10σ upper limits of wlim = 18.5–20.5 AB mag in 1000 s of exposure, depending on the conditions. We observed 54 per cent (26 out of 48) of the unretracted GW alerts and did not find any electromagnetic counterparts. We compare our upper limits to various possible counterparts: the kilonova AT 2017gfo, models of radioactive- and magnetar-powered kilonovae, short gamma-ray burst afterglows, and active galactic nucleus (AGN) flares. Although the large positional uncertainties of GW sources do not allow us to place strong constraints during O3, DDOTI observations of well-localized GW events in O4 and beyond could meaningfully constrain models of compact binary mergers. We show that DDOTI is able to detect kilonovae similar to AT 2017gfo up to about 200 Mpc and magnetar-powered kilonovae up to 1 Gpc. We calculate that nearby (≲200 Mpc) afterglows have a high chance (≈70 per cent) to be detected by rapid (≲3 h) DDOTI observations if observed on-axis, whereas off-axis afterglows are unlikely to be seen. Finally, we suggest that long-term monitoring of massive BBH events with DDOTI could confirm or rule out late AGN flares associated with these events.

gravitational waves↗

Decision Support Tool for Risk Assessment & Maneuver Planning in Collision Avoidance

As the quantity of orbital debris continues to grow, so too does the rate of conjunction messages that suggest possible collisions between high value payloads and debris. The abundance of these conjunction messages, and eventual misses, has led to a culture of ignored alerts, and an increase in satellite operation costs as a result of the frequent need to plan resources for maneuver planning and execution. The loss of “trust” in conjunction alerts is due to the poorly characterized evolution in probability of collision (Pc) as time approaches the time of closest approach (TCA) between two objects, as well as the interpretation of Pc in the context of maneuver planning. To address these problems, and in collaboration with the NASA Conjunction Assessment Risk Analysis (CARA) program, the Industrial Sciences Group has developed a novel Maneuver Decision Support System (MDSS) to assist satellite operations in conjunction assessment and Maneuver planning. It provides a meaningful and intuitive Urgency metric for actionable maneuver decisions, based on the physical dynamics of conjunctions. It is based on a forecast of the evolution of Pc over time and represents an advance over current methods that are in use for satellite conjunction monitoring and planning. The result is to give satellite operators a validated decision support systems to plan for maneuver execution or mitigation or monitoring up to 3 days before TCA.

Decision Support Tool↗

Formalized Reasoning of Operational Volumes for Wildland Fire Fighting

This work is focused on the formalized reasoning of operational volumes as it relates to the current and future technologies developed by NASA to aid in wildfire fighting operations. One such technology is the unmanned aircraft system pilot kit (UASP-kit) developed by the Scalable Traffic Management for Emergency Response Operations (STEReO) project at NASA, which is used to increase situation awareness for a ground operator in the field. The UASP-kit utilizes operational volumes which represent mission areas and alerting volumes, to alert when another aircraft is within one of these volumes from received ADS-B data. This work is focused on developing a rigorous foundation for the concept of operational volumes for modeling and prototyping operations in such a tool as the UASP-kit. This includes establishing a class of algorithms to detect when an object is in an operational volume, and when an operational volume is intersecting or contained within another. Additionally, this work is focused on providing rigorous proof in an interactive theorem prover that the algorithms work as intended. Scenarios are presented that model current UASP-kit operations and extend past the current capabilities of the technology to modeling more complex scenarios such as mission planning.

Operational Volumes↗

Formalized Reasoning of Operational Volumes for Wildland Fire Fighting

This work is focused on the formalized reasoning of operational volumes as it relates to the current and future technologies developed by NASA to aid in wildland firefighting operations. One such technology is the Unmanned Aircraft System Pilot Kit (UASP-kit) developed by the Scalable Traffic Management for Emergency Response Operations (STEReO) project at NASA, which is used to increase situational awareness for a ground operator in the field. The UASP-kit utilizes operational volumes to represent mission areas and alerting volumes; these volumes, in combinations with ADS-B data, can then be used to alert the ground operator when another aircraft has entered one of these areas. This work presents a rigorous foundation for the concept of operational volumes for modeling and prototyping operations in such a tool as the UASP-kit. This includes establishing a class of algorithms to detect when an object is in an operational volume, and when one operational volume intersects or is contained in another. Additionally, this work provides rigorous proof that the algorithms work as intended. Scenarios are presented that model current UASP-kit operations and extend past the current capabilities of the technology to modeling more complex scenarios such as mission planning.

Operational Volumes↗

X-57 Cockpit Interface Control Document (ICD-CEPT-006)

The Cockpit Interface Control Document defines the hardware interfaces between the X-57 cockpit and subsystems. It provides locational and operational information in support of ground and flight operations with details on controls and displays that include Modes of Operation, Start-Up and Shut- Down Sequence diagrams and captures the current state of the MOD II Avionics Power Architecture. There is also preliminary information of the MOD III and MOD IV configurations. Microsoft PowerPoint was chosen for the document as early development required frequent meetings with multiple customers including aircraft operators (pilots), ground operations, support contractors and power, instrumentation, and human systems integration engineers and PowerPoint enabled presentations that could be quickly modified based on customer and developer interaction. One of the driving requirements for the cockpit design was to keep the left side panel as close the stock Tecnam panel as possible to reduce the failure risk of flight critical indicators. The original annunciator panel in the left side panel was modified to alert the pilot to failures in critical X-57 subsystems and an operator audio alert capability was added for these subsystems. Power-Up switches for the aircraft low voltage 13.8 VDC systems are located at the bottom of the left side panel and center panel, the same location as the stock Tecnam 13.8 VDC switches. The switches for energizing the high voltage system were located in the overhead panel to reduce the risk of inadvertently energizing the high voltage system during the low voltage power-up sequence. The Cruise Motor ARM switches were also located in the overhead panel and correspond to the same location as the stock Tecnam ignition switches. The stock Tecnam throttle levers and prop pitch levers were retained for the X-57. The throttle levers were renamed torque levers since they controlled the commanded torque to the cruise motors. The prop pitch levers provide a commanded RPM signal to an electronic prop pitch controller. X-57 specific displays, located in the right-side panel, are driven by dedicated sensors that monitor right and left side cruise motor RPM, right and left high voltage “Traction Bus” A and B (voltage, current and power) and the Avionics Bus DC converters (A and B) voltage and current. An X-57 Multi-Function Display (MFD) located in the center panel displays CAN Bus parameters. CAN Bus architecture is not certified for flight so these displays could not be used for safety critical information but were designed to be used for test point information only.

Laura Kushner↗

Integration of Automated Systems (IAS) Flight Test - Hazard Perception & Avoidance (HPA) Results

The Integration of Automated Systems (IAS) flight test series concluded in October 2023 in support of NASA's Advanced Air Mobility (AAM) project. These flights include crewed, test (i.e., ownship) and traffic (i.e., intruder) aircraft that flew with unique technologies onboard. The presentation includes overviews of the flight tet itself and the specific results that pertain to the Hazard Perception and Avoidance (HPA) technical areas. HPA tested the FAA's Airborne Collision Avoidance System X (ACAS X), a next-generation collision avoidance tool developed to support different aircraft types and operations. The rotorcraft variant, ACAS Xr, is designed to accommodate existing helicopter platforms and in-development, vertical takeoff and landing (VTOL) concepts, which are critical to the emerging AAM concept of operations. Two configurations of ACAS Xr were examined: Collision Avoidance System (CAS, similar to the Traffic Collision Avoidance System [TCAS] II) and Detect and Avoid (DAA, previously developed to provide added situational awareness for remote pilots). Additionally, this system was flown in cruise and low-speed flight regimes as well as within en-route and (emulated), structured (i.e., dense/urban), and terminal airspaces. Results include the types of alerts generated by ACAS Xr across the different configurations, the distances at which the alerts were generated, response times, manuever sizes, miss distances, and general comments from pilots. Key takeaways and next steps are also provided.

detect and avoid↗

Detect and Avoid and Collision Avoidance Flight Test Results with ACAS Xr

In October 2023, the National Aeronautics and Space Administration (NASA) completed its Integration of Automated Systems flight test series, conducted under NASA’s Advanced Air Mobility project and in partnership with Sikorsky and the Defense Advanced Research Projects Agency (DARPA). The flight test effort included two crewed rotorcraft platforms. The first, a modified S-76B helicopter, served as the “ownship” for the duration of the flight test. The second vehicle, a modified S-70, served as the intruder aircraft. One Sikorsky pilot and one NASA test pilot was onboard each aircraft for every test point, with the NASA test pilot responsible for interacting with the research systems under test. Approximately half of the flight test was devoted to assessing the Federal Aviation Administration’s (FAA) next-generation collision avoidance system, the Airborne Collision Avoidance System X for Rotorcraft (ACAS Xr). The two configurations available within ACAS Xr – the Collision Avoidance System (CAS) configuration and the Detect and Avoid (DAA) configuration – were flown with an onboard pilot under Visual Flight Rules in controlled airspace over the Long Island Sound (Connecticut, USA). A total of 33 flight test cards were flown with ACAS Xr active. The ownship was equipped with ACAS Xr and the intruder was equipped with Automatic Dependent Surveillance-Broadcast (ADS-B). The test points were blocked by ACAS Xr configuration, with individual encounters varying the ownship speed (90 knots or 20 knots), the intruder designation (en-route, terminal area, or structured airspace), and method of RA execution (automated or manually executed). Results showed that the ACAS Xr alerting and guidance was largely effective and rated positively by the NASA test pilots, exemplified by zero instances of the pilots overriding an ACAS Xr Resolution Advisory (RA). Key areas of improvement, however, were noted, particularly with regards to the lack of an aural alert indicating a need to accelerate when receiving an RA at low speed and the occurrence of multiple RAs that the pilots found to be unacceptable.

detect and avoid↗