Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operational Collision Avoidance”

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 181 records · Page 10

UAS in the NAS Flight Test Series 4 Overview

Flight Test Series 4 (FT4) provides the researchers with an opportunity to expand on the data collected during the first flight tests. Following Flight Test Series 3, additional scripted encounters with different aircraft performance and sensors will be conducted. FT4 is presently planned for Spring of 2016 to ensure collection of data to support the validation of the final RTCA Phase 1 DAA (Detect and Avoid) Minimum Operational Performance Standards (MOPS). There are three research objectives associated with this goal: Evaluate the performance of the DAA system against cooperative and non-cooperative aircraft encounters Evaluate UAS (Unmanned Aircraft Systems) pilot performance in response to DAA maneuver guidance and alerting with live intruder encounters Evaluate TCAS/DAA (Traffic Alert and Collision Avoidance System/Detect and Avoid) interoperability. This flight test series will focus on only the Scripted Encounters configuration, supporting the collection of data to validate the interoperability of DAA and collision avoidance algorithms.

flight test↗

A Provably Correct Floating-Point Implementation of Well Clear Avionics Concepts

The NASA DAIDALUS library provides formal definitions for Detect-and-Avoid avionics concepts such as when an aircraft is well-clear with respect to the surrounding air traffic, i.e., it does not operate in such proximity to create a collision hazard. While several properties are proven correct for DAIDALUS assuming ideal real number arithmetic, an actual implementation that uses floating-point numbers may behave unexpectedly because of round-off errors and run-time exceptions. This paper presents an experience report on the application of a formal methods toolchain to extract and verify floating-point C code from a real-valued specification of the well-clear module of DAIDALUS. This toolchain comprises the PVS theorem prover, the PRECiSA floating-point analyzer and code generator, and the Frama-C analysis suite. The generated code is automatically instrumented to detect when the control flow of the floating-point program may diverge from the ideal real number specification, and it is annotated with contracts that state the maximum accumulated round-off error. The absence of overflows is also formally verified for the generated code. In order to apply the toolchain to an industrial case study such as DAIDALUS, a formally verified pre-processing of the input specification is performed, which includes a program slicing and several semantic-preserving simplifications.

Program verification↗

Shear and mixing effects on cells in agitated microcarrier tissue culture reactors

Tissue cells are known to be sensitive to mechanical stresses imposed on them by agitation in bioreactors. The amount of agitation provided in a microcarrier or suspension bioreactor should be only enough to provide effective homogeneity. Three distinct flow regions can be identified in the reactor: bulk turbulent flow, bulk laminar flow and boundary-layer flows. Possible mechanisms of cell damage are examined by analyzing the motion of microcarriers or free cells relative to the surrounding fluid, to each other and to moving or stationary solid surfaces. The primary mechanisms of cell damage appear to result from: (1) direct interaction between microcarriers and turbulent eddies; (2) collisions between microcarriers in turbulent flow; and (3) collisions against the impeller or other stationary surfaces. If the smallest eddies of turbulent flow are of the same size as the microcarrier beads, they may cause high shear stresses on the cells. Eddies the size of the average interbead spacing may cause bead-bead collisions which damage cells. The severity of the collisions increases when the eddies are also of the same size as the beads. Impeller collisions occur when beads cannot avoid the impeller leading edge as it advances through the liquid. The implications of the results of this analysis on the design and operation of tissue culture reactors are discussed.

Cherry, Robert S.↗

Design of a Multi-mode Flight Deck Decision Support System for Airborne Conflict Management

NASA Langley has developed a multi-mode decision support system for pilots operating in a Distributed Air-Ground Traffic Management (DAG-TM) environment. An Autonomous Operations Planner (AOP) assists pilots in performing separation assurance functions, including conflict detection, prevention, and resolution. Ongoing AOP design has been based on a comprehensive human factors analysis and evaluation results from previous human-in-the-loop experiments with airline pilot test subjects. AOP considers complex flight mode interactions and provides flight guidance to pilots consistent with the current aircraft control state. Pilots communicate goals to AOP by setting system preferences and actively probing potential trajectories for conflicts. To minimize training requirements and improve operational use, AOP design leverages existing alerting philosophies, displays, and crew interfaces common on commercial aircraft. Future work will consider trajectory prediction uncertainties, integration with the TCAS collision avoidance system, and will incorporate enhancements based on an upcoming air-ground coordination experiment.

Barhydt, Richard↗

NASA's Orbital Debris Conjuction Assessment and Collision Avoidance Strategy

NASA has successfully used debris avoidance maneuvers to protect our spacecraft for more than 20 . years. This process which started out using parametric data and maneuver boxes has seen considerable evolution and now allows us to continue nominal operations for all but the most threatening objects. This has greatly reduced the interruptions to the critical mission objectives being pursued by NASA s Space Station, Space Shuttle, and robotic satellites.

Gavin, Richard T.↗

Appendix A: NAS-Wide Encounter Rate Evaluation Using Historical Radar Data and the Airspace Concept Evaluation System (ACES)

Regulations that establish operational and performance requirements for unmanned aircraft systems (UAS) are being developed by a consortium of government, industry and academic institutions. Those requirements will apply to detect-and-avoid (DAA) systems and other equipment necessary to integrate UAS with the National Airspace System (NAS) and are determined according to their contribution to the overall level of safety required to operate in the airspace. Several key gaps must be addressed in order to link equipment requirements to an airspace level of safety. Foremost among these is the calculation of the relative effectiveness of a particular system to mitigate violations of a separation standard with other aircraft, which is known as the systems risk ratio. The risk ratio is calculated as the probability of mid-air collision with a DAA system divided by the probability of mid-air collision without a DAA system. The risk ratio of a DAA system, in combination with the risk ratios of other collision avoidance mitigations, will determine the overall safety of the airspace measured in terms of the number of mid-air collisions per flight hour. Defining the required risk ratio that the DAA system needs to ensure the safety of the airspace requires an evaluation of the current airspace and a simulated evaluation that incorporates UAS aerodynamic performance and the mission characteristics of future UAS operations that are projected to be conducted in areas that interact with current operations. These evaluations will produce the frequency of encounters that currently exist in the airspace and those that could be generated with the introduction of UAS. Together, the frequency of encounters, an evaluation of unmitigated risk of collision, and a desired level of safety of the airspace will yield a required risk ratio of the DAA system. This study will focus on evaluating the encounter rates between aircraft based on historical radar data and encounter rates that could occur based on simulated UAS missions.

Unmanned Aircraft Systems↗

Solutions Network Formulation Report: Improving NOAA's PORTS(R) Through Enhanced Data Inputs from NASA's Ocean Surface Topography Mission

The Nation uses water-level data for a variety of practical purposes, including nautical charting, maritime navigation, hydrography, coastal engineering, and tsunami and storm surge warnings. Long-term applications include marine boundary determinations, tidal predictions, sea-level trend monitoring, oceanographic research, and climate research. Accurate and timely information concerning sea-level height, tide, and ocean current is needed to understand their impact on coastal management, disaster management, and public health. Satellite altimeter data products are currently used by hundreds of researchers and operational users to monitor ocean circulation and to improve scientists understanding of the role of the oceans in climate and weather. The NOAA (National Oceanic and Atmospheric Administration) National Ocean Service has been monitoring sea-level variations for many years. NOAA s PORTS (Physical Oceanographic Real-Time System) DST (decision support tool), managed by the Center for Operational Oceanographic Products and Services, supports safe and cost-efficient navigation by providing ship masters and pilots with accurate real-time information required to avoid groundings and collisions. This report assesses the capacity of NASA s satellite altimeter data to meet societal decision support needs through incorporation into NOAA s PORTS. NASA has a long heritage of collecting data for ocean research, including its current Terra and Aqua missions. Numerous other missions provide additional important information for coastal management issues, and data collection will continue in the coming decade with such missions as the OSTM (Ocean Surface Topography Mission). OSTM will provide data on sea-surface heights for determining ocean circulation, climate change, and sea-level rise. We suggest that NASA incorporate OSTM altimeter data (C- and Ku-band) into NOAA s PORTS DST in support of NASA s Coastal Management National Application with secondary support to the Disaster Management and Public Health National Applications.

Guest, DeNeice↗

System Autonomy for Space Traffic Management

This paper proposes an initial architecture for a Space Traffic Management (STM) system, based on openApplication Programming Interfaces (APIs) and drawing on previous work by the NASA Ames Research Center (ARC) to develop an architecture for low-altitude Unmanned Aerial System Traffic Management (UTM). The authors explore how autonomy could be used to enhance an STM system, and how constraints inherent in STM complicate and challenge certain applications of autonomy. We conceptually explore how autonomy could be used within an STM architecture, with multiple non-authoritative catalogs of resident space objects, and to determine which oftwo conjuncting spacecraft moves. NASA ARC is developing a software research environment for STM, along with a physical laboratory and visualization space. We invite STM stakeholders to collaborate in our infrastructure, to help inform the design of the proposed STM architecture, and to participate in the refinement and validation of its concept of operations using the software research platform.

space situational awareness↗

TPSAS-NF1676L-10776-DND

Airborne self-separation (SSEP) among aircraft is proposed as a means for improving air traffic system capacity and safety in the future National Airspace System and for improving the efficiency of flight for all aircraft performing this function. The concept is examined in the U.S. en route domain, in an environment of mixed conventional and SSEP operations. No airspace is set aside for this purpose and the first aircraft equipped to perform the function can receive its benefits. For aircraft operating in the SSEP mode, the Air Navigation Service Provider (ANSP) turns over control and responsibility for all separation tasks to the pilots of SSEP aircraft. This includes separation from all other aircraft, from severe weather hazards and from Special Use Airspace. Connection to the centralized traffic flow management function is retained throughout the flight, however, and compliance with any Required Time of Arrival assignments is maintained. The SSEP function is accomplished in the aircraft through the use of airborne surveillance, data communications and processing equipment, and procedures defined in a new set of operating rules called "Autonomous Flight Rules" (AFR). The technical enablers are Automatic Dependent Surveillance - Broadcast (ADS-B), Traffic Information Service - Broadcast (TIS-B), and Traffic Alert and Collision Avoidance System (TCAS). This briefing presents an overview of the concept.

Frank Bussink↗

Monitoring Airspace Complexity and Determining Contributing Factors

The national airspace has evolved over many years to accommodate increased traffic demand [1] while simultaneously maintaining one of the safest forms of transportation [2], [3]. One of the reasons for this success is the ability of the system and the operators to adapt and accommodate to situations that routinely disrupt optimal operations. These situations may include: adverse weather, delays, early arrivals, equipment outages, and other factors that are outside the operators ability to control. These factors can lead to states where automation is unable to properly handle these issues and therefore air traffic controllers and pilots have to intervene, ultimately increasing communication between operators resulting in higher workload. As controller workload increases to handle sub-optimal operating conditions this can be viewed as an increase in complexity. The reasoning for this is because humans are now required to make tactical decisions in response to external factors, resulting in a departure from the strategic plan where operations would be more efficiently managed. Human operators control airspace complexity under rigid regulations that are constantly changing. The airspace is divided into sectors and the number of aircraft assigned to each controller is limited for safe handling. There has been past work that devised airspace complexity metrics in commercial aviation and related these metrics to controller workload (e.g., [4],[5]). The upper bounds on the system load are pre-determined. Such bounds on complexity make for a safe system, but the system cannot scale and adapt to autonomous, dense, and heterogeneous traffic, including the many types of Unmanned Aerial Vehicles (UAVs) envisioned to be added to the operations. We hypothesize that, as traffic density and heterogeneity grow, and other key metrics change, there will be phase transitions at which the way traffic should be managed changes significantly [6]. We offer a method for in-time detection of contributing factors that lead to phase transitions, characterized by increased complexity. To the best of our knowledge, there is no tool similar to our proposed effort that identifies such contributing factors or precursor patterns. To define the scope we are proposing to measure complexity from the viewpoint of the Terminal Radar Approach Control Facilities (TRACON) controller’s perspective. In particular we are analyzing arrivals into KSFO. With safety as the top concern for airspace operators, it is important to recognize that as density and heterogeneity grow, the focus of the system will change. Times of the day when the airspace has low density and heterogeneity, the flights will follow more efficient paths where the aircraft move on established routes that are more or less directly to the destination. However, when density and heterogeneity increases, the system will begin changing focus to avoiding conflicts and collisions and route the flights in a more flexible way. Higher flexibility requires more communication and coordination between controllers and pilots which the current automation is unable to handle. This paper proposes a novel approach that monitors airspace complexity at multiple scales, uses a Machine Learning-based tool that predicts when operations will transition to a regime of greater complexity, and identifies actions that can reduce the complexity while still maintaining efficient and safe operations. We demonstrate our proposed approach using data from multiple complementary sources. This includes, but is not limited to: historical aircraft surveillance data from NASA’s Sherlock Data Warehouse [7], METAR weather data, and airport configuration data from Aviation System Performance Metrics (ASPM). The surveillance data flight paths are sampled at a variable sample rate — increasing as the aircraft approaches the airport. This is due to how Sherlock manages flight track stitching between different radar facilities which have different sampling rates. The weather and performance data are logged at defined intervals throughout the day at a courser refresh rate. In addition to the logged data and metrics, we leverage pre-defined Standard Terminal Arrival Routes (STARs) procedures to characterize the path of each flight. Each flight files for one of these routes in the flight plan well before entering the terminal airspace, and approximately follows the route until it leaves the STAR, typically on the final fix of a runway transition. However, most flights do not always fly the full STAR procedure to completion [8], but the majority do adhere to the fixes within the common route of the procedure. Our approach leverages fixes in the common route of each of the STARs to build a reference path to the airport. This allows us to characterize the flight paths in what we are defining as the “maneuvering area” (the airspace between the STAR and before the flight is lined up on the runway’s final approach) to determine how off nominal the flights are to calculate its complexity score. Determining airspace complexity is a concept that does not have a concrete answer. In designing this metric, we consider what increases the workload for the air traffic controllers. Consequently more specialized vectoring maneuvers results in higher workload. Accordingly, we start with a theory: each flight has a direct path it takes from the STAR’s common route to the final approach’s outer marker fix for the flight’s landing runway. It is important to note that the direct path is only used as a reference. If the majority of the flights have a large consistent offset as compared to other routes it does not necessarily mean that those flights have higher complexity. We are merely building a distribution based on this direct path for that particular STAR and runway pair to determine the normal mode of operations for that route. Flights that are in the upper tail of these distributions will result in higher complexity scores and flights that fly in the median will represent the normal mode of operations and therefore will have lower complexity scores. Since flights following each STAR route take different paths to the airport, we have a different distribution for each STAR route and therefore can model these distributions to compute a complexity score from their respective normalized distributions. To evaluate the effectiveness of our proposed airspace complexity metric we will compare against an established approach based on trajectory clustering [9]. This unsupervised learning technique consists of the following steps: (1) identify the general maneuvering areas (waypoints) by performing $\kappa$-means or DBSCAN clustering on locations where aircraft frequently turn based on the surveillance radar track data, (2) map flight trajectories onto sequences of waypoints, and (3) cluster the sequences based on their common subsequences. From a high-level perspective, this baseline model learns nominal operations in the airspace through the sequence of waypoints that are representative of where aircraft change direction and defines deviations from the nominal operations as “complex.” Therefore, more deviations from the nominal operations correspond to higher complexity values. For our validation, we re-implemented this technique and tune model hyper-parameters to correctly detect waypoints for the arrival traffic into the San Francisco bay area. We will compute the complexity measure over a one-year period using our proposed technique as well as the baseline. Our validation will be based on each technique’s ability to detect a set of undesirable outcomes (e.g., go-arounds, holding patterns, average time in the airspace, etc.). Since our current complexity metric is derived from the offset from the direct reference path, it’s important to understand what causes these offsets. In many of the flights with high offset distance, flights performing holding patterns and S turns can be observed. These maneuvering tactics are utilized to add distance between the aircraft and the destination runway to prevent multiple flights from having conflicting arrival times. In order to predict a rise in complexity (or the precursor to complexity), it’s necessary to be able to identify these potential conflicts (which in turn, result in higher offsets). To do this, we define a “representative flight” for each STAR route and runway pair. This flight is approximately the path the flight would take if there was a clear path with no other flights in the airspace — including the time remaining to the airport. We first identify the flights for a given STAR runway pair using the offset to the reference path distributions that fall between the 44-55 percentiles. This yields the flights that conform to the most normal mode of operation. Each of these flights is partitioned based on the percent complete from the entry point into the maneuvering areas from 0\% – 100\% complete. Then for each percent “bin”, we take the median value of the flight’s latitude/longitude coordinates, airspeed, and (non causal) time remaining to the airport to construct a lookup table for each percent complete bin on a given route. As a flight enters the maneuvering area, we can find the estimated arrival time of a flight to the airport by finding the closest point to the representative path’s percent complete bin (relative to the flight’s current position at any snapshot in the airspace) and therefore retrieve the corresponding remaining time left on the “representative path”. We assume that the flight will follow the representative path to completion when deriving these estimates. We can then compare these estimated arrival times against other flights for the same snapshot in time to identify potential conflicts. If more flights are estimated to arrive within a tolerance window than there are runways available, then we have a potential conflict. We can use this derived measure along with other factors expected to add disruption to the operation such as weather and runway configuration changes as an input to machine learning tools to detect precursors that increases in our complexity measure. This novel method will assist in uncovering insights into the contributing factors that lead to increased complexity that may allow for in-time responses to avoid reaching a high complexity state in the airspace.

complexity↗

Notional Airspace Operations Demonstration Plan

The airspace operations demonstration (AOD) is intended to show that the Access 5 Step 1 functional requirements can be met. The demonstration will occur in two phases. The initial on-range phase will be carried out in restricted airspace to demonstrate the cooperative collision avoidance (CCA) functional requirements and to provide risk-reduction for the AOD by allowing the test team to rehearse some elements of the demonstration mission. The CCA system to be used in these flights is based on Automatic Dependent Surveillance-Broadcast (ADS-B) which is a commercially-available system by which airplanes constantly broadcast their current position and altitude to other aircraft and ground resources over a dedicated radio datalink. The final phase will occur in the national airspace (NAS) and will be the formal demonstration of the remainder of the proposed functional requirements. The general objectives of the AOD are as follows: (1) Demonstrate that the UAS can aviate in the NAS (2) Demonstrate that the UAS can navigate in the NAS (3) Demonstrate that the UAS can communicate with the NAS (4) Demonstrate that the UAS can perform selected collision avoidance functions in the NAS (5) Demonstrate that the UAS can evaluate and avoid weather conflicts in the NAS (6) Demonstrate that the UAS can provide adequate command and control in the NAS In addition to the stated objectives, there are a number of goals for the flight demonstration. The demo can be accomplished successfully without achieving these goals, but these goals are to be used as a guideline for preparing for the mission. The goals are: (1) Mission duration of at least 24 hours (2) Loiter over heavy traffic to evaluate the data block issue identified during the Access 5 Airspace Operations Simulations (3) Document the contingency management process and lessons learned (4) Document the coordination process for Ground Control Stations (GCS) handoff (5) Document lessons learned regarding the process of flying in the NAS Preliminary planning for a notional mission to achieve the objectives and goals has been prepared. The planning is intended to serve as a guide for detailed planning of the AOD.

Trongale, Nicholas A.↗

Test Results for the Automated Rendezvous and Capture System

The Automated Rendezvous and Capture (AR&C) system was designed and tested at NASA's Marshall Space Flight Center (MSFC) to demonstrate technologies and mission strategies for automated rendezvous and docking of spacecraft in Earth orbit, The system incorporates some of the latest innovations in Global Positioning, System space navigation, laser sensor technologies and automated mission sequencing algorithms. The system's initial design and integration was completed in 1998 and has undergone testing at MSFC. This paper describes the major components of the AR&C system and presents results from the official system tests performed in MSFC's Flight Robotics Laboratory with digital simulations and hardware in the loop tests. The results show that the AR&C system can safely and reliably perform automated rendezvous and docking missions in the absence of system failures with 100 percent success. When system failures are included, the system uses its automated collision avoidance maneuver logic to recover in a safe manner. The primary objective of the AR&C project is to prove that by designing a safe and robust automated system, mission operations cost can be reduced by decreasing the personnel required for mission design, preflight planning and training required for crewed rendezvous and docking missions.

Cruzen, Craig↗

NASA Conjunction Assessment Risk Analysis (CARA) Ground Systems, Software and Operations Infrastructure Cloud Implementation

The growing number of large-scale constellations and the improvements made in the tracking and detection of resident space objects have contributed to the increase of satellite conjunction events. As a result of the increase of objects in Earth orbit, the timeline for risk analysis computations for satellite collision avoidance is more urgent when conjunctions occur. It is imperative NASA maintains a space environment safety functionality for the agency that allows CARA remote access to the ground system while maintaining redundancy. CARA’s On-premises (On-prem) ground system would no longer be able to meet these access and redundancy requirements, hence the investigation and eventual implementation of a Cloud-based ground station infrastructure as a viable solution. This paper will provide an overview of the principal parts of the Conjunction Assessment (CA) risk analysis process used at CARA, summarize the key drivers towards the Cloud solution, and share key lessons learned that are significant for any operational entity considering a cloud solution for real-time satellite operations to ensure a sustainable space traffic environment for all.

Sustainability↗

Designing planetary protection into the Mars observer mission

Planetary protection has been an important consideration during the process of designing the Mars Observer mission. It affected trajectory design of both the interplanetary transfer and the orbits at Mars; these in turn affected the observation strategies developed for the mission. The Project relied mainly on the strategy of collision avoidance to prevent contamination of Mars. Conservative estimates of spacecraft reliability and Martian atmosphere density were used to evaluate decisions concerning the interplanetary trajectory, the orbit insertion phase at Mars, and operations in orbit at Mars and afterwards. Changes in the trajectory design, especially in the orbit insertion phase, required a refinement of those estimates.

Sweetser, T. H.↗

Synchronized Position Hold, Engage, Reorient, Experimental Satellites

Synchronized Position Hold, Engage, Reorient, Experimental Satellites (SPHERES) are bowling-ball sized spherical satellites. They will be used inside the space station to test a set of well-defined instructions for spacecraft performing autonomous rendezvous and docking maneuvers. Three free-flying spheres will fly within the cabin of the station, performing flight formations. Each satellite is self-contained with power, propulsion, computers and navigation equipment. The results are important for satellite servicing, vehicle assembly and formation flying spacecraft configurations. SPHERES is a testbed for formation flying by satellites, the theories and calculations that coordinate the motion of multiple bodies maneuvering in microgravity. To achieve this inside the ISS cabin, bowling-ball-sized spheres perform various maneuvers (or protocols), with one to three spheres operating simultaneously . The Synchronized Position Hold, Engage, Reorient, Experimental Satellites (SPHERES) experiment will test relative attitude control and station-keeping between satellites, re-targeting and image plane filling maneuvers, collision avoidance and fuel balancing algorithms, and an array of geometry estimators used in various missions. SPHERES consists of three self-contained satellites, which are 18 sided polyhedrons that are 0.2 meter in diameter and weigh 3.5 kilograms. Each satellite contains an internal propulsion system, power, avionics, software, communications, and metrology subsystems. The propulsion system uses CO2, which is expelled through the thrusters. SPHERES satellites are powered by AA batteries. The metrology subsystem provides real-time position and attitude information. To simulate ground station-keeping, a laptop will be used to transmit navigational data and formation flying algorithms. Once these data are uploaded, the satellites will perform autonomously and hold the formation until a new command is given.

Miller, David W.↗

Traffic Alert and Collision Avoidance System (TCAS): Cockpit Display of Traffic Information (CDTI) investigation. Phase 1: Feasibility study

The possibility of the Threat Alert and Collision Avoidance System (TCAS) traffic sensor and display being used for meaningful Cockpit Display of Traffic Information (CDTI) applications has resulted in the Federal Aviation Administration initiating a project to establish the technical and operational requirements to realize this potential. Phase 1 of the project is presented here. Phase 1 was organized to define specific CDTI applications for the terminal area, to determine what has already been learned about CDTI technology relevant to these applications, and to define the engineering required to supply the remaining TCAS-CDTI technology for capacity benefit realization. The CDTI applications examined have been limited to those appropriate to the final approach and departure phases of flight.

Burgess, Malcolm↗

LightForce: An Update on Orbital Collision Avoidance Using Photon Pressure

We present an update on our research on collision avoidance using photon-pressure induced by ground-based lasers. In the past, we have shown the general feasibility of employing small orbit perturbations, induced by photon pressure from ground-based laser illumination, for collision avoidance in space. Possible applications would be protecting space assets from impacts with debris and stabilizing the orbital debris environment. Focusing on collision avoidance rather than de-orbit, the scheme avoids some of the security and liability implications of active debris removal, and requires less sophisticated hardware than laser ablation. In earlier research we concluded that one ground based system consisting of a 10 kW class laser, directed by a 1.5 m telescope with adaptive optics, could avoid a significant fraction of debris-debris collisions in low Earth orbit. This paper describes our recent efforts, which include refining our original analysis, employing higher fidelity simulations and performing experimental tracking tests. We investigate the efficacy of one or more laser ground stations for debris-debris collision avoidance and satellite protection using simulations to investigate multiple case studies. The approach includes modeling of laser beam propagation through the atmosphere, the debris environment (including actual trajectories and physical parameters), laser facility operations, and simulations of the resulting photon pressure. We also present the results of experimental laser debris tracking tests. These tests track potential targets of a first technical demonstration and quantify the achievable tracking performance.

Stupl, Jan↗

Airborne Radar for sUAS Sense and Avoid

A primary challenge for the safe integration of small UAS operations into the National Airspace System (NAS) is traffic deconfliction, both from manned and unmanned aircraft. The UAS Traffic Management (UTM) project being conducted at the National Aeronautics and Space Administration (NASA) considers a layered approach to separation provision, ranging from segregation of operations through airspace volumes (geofences) to autonomous sense and avoid (SAA) technologies for higher risk, densely occupied airspace. Cooperative SAA systems, such as Automatic Dependent Surveillance-Broadcast (ADS-B) and/or vehicle-to-vehicle communication systems provide significant additional risk mitigation but they fail to adequately mitigate collision risks for non-cooperative (non-transponder equipped) airborne aircraft. The RAAVIN (Radar on Autonomous Aircraft to Verify ICAROUS Navigation) flight test being conducted by NASA and the Mid-Atlantic Aviation Partnership (MAAP) was designed to investigate the applicability and performance of a prototype, commercially available sUAS radar to detect and track non-cooperative airborne traffic, both manned and unmanned. The radar selected for this research was a Frequency Modulated Continuous Wave (FMCW) radar with 120 degree azimuth and 80 degree elevation field of view operating at 24.55GHz center frequency with a 200 MHz bandwidth. The radar transmits 2 watts of power thru a Metamaterial Electronically Scanning Array antenna in horizontal polarization. When the radar is transmitting, personnel must be at least 1 meter away from the active array to limit nonionizing radiation exposure. The radar physical dimensions are 18.7cm by 12.1cm by 4.1cm and it weighs less than 820 grams making it well suited for installation on small UASs. The onboard, SAA capability, known as ICAROUS, (Independent Configurable Architecture for Reliable Operations of Unmanned Systems), developed by NASA to support sUAS operations, will provide autonomous guidance using the traffic radar tracks from the onboard radar. The RAAVIN set of studies will be conducted in three phases. The first phase included outdoor, ground-based radar evaluations performed at the Virginia Tech’s Kentland Farm testing range in Blacksburg, VA. The test was designed to measure how well the radar could detect and track a small UAS flying in the radar’s field of view. The radar was used to monitor 5 test flights consisting of outbound, inbound and crossing routes at different ranges and altitudes. The UAS flown during the ground test was the Inspire 2, a quad copter weighing less than 4250 grams (10 pounds) at maximum payload. The radar was set up to scan and track targets over its full azimuthal field of view from 0 to 40 degrees in elevation. The radar was configured to eliminate tracks generated from any targets located beyond 2000 meters from the radar and moving at velocities under 1.45 meters per second. For subsequent phases of the study the radar will be integrated with a sUAS platform to evaluate its performance in flight for SAA applications ranging from sUAS to manned GA aircraft detections and tracking. Preliminary data analysis from the first outdoor ground tests showed the radar performed well at tracking the vehicle as it flew outbound and repeatedly maintained a track out to 1000 meters (maximum 1387 meters) until the vehicle slowed to a stop to reverse direction to fly inbound. As the Inspire flew inbound tracks from beyond 800 meters, a reacquisition time delay was consistently observed between when the Inspire exceeds a speed of 1.45 meters per second and when the radar indicated an inbound target was present and maintained its track. The time delay varied between 6 seconds to over 37 seconds for the inbound flights examined, and typically resulted in about a 200 meter closure distance before the Inspire track was maintained. The radar performed well at both acquiring and tracking the vehicle as it flew crossing routes out past 400 meters across the azimuthal field of view. The radar and ICAROUS software will be integrated and flown on a BFD-1400-SE8-E UAS during the next phase of the RAAVIN project. The main goal at the conclusion of this effort is to determine if this radar technology can reliably support minimum requirements for SAA applications of sUAS. In particular, the study will measure the range of vehicle detections, lateral and vertical angular errors, false and missed/late detections, and estimated distance at closest point of approach after an avoidance maneuver is executed. This last metric is directly impacted by sensor performance and indicates its suitability for the task.

Szatkowski, George N.↗