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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS1991

Avoiding space robot collisions utilizing the NASA/GSFC tri-mode skin sensor

Sensor based robot motion planning research has primarily focused on mobile robots. Consider, however, the case of a robot manipulator expected to operate autonomously in a dynamic environment where unexpected collisions can occur with many parts of the robot. Only a sensor based system capable of generating collision free paths would be acceptable in such situations. Recently, work in this area has been reported in which a deterministic solution for 2DOF systems has been generated. The arm was sensitized with 'skin' of infra-red sensors. We have proposed a heuristic (potential field based) methodology for redundant robots with large DOF's. The key concepts are solving the path planning problem by cooperating global and local planning modules, the use of complete information from the sensors and partial (but appropriate) information from a world model, representation of objects with hyper-ellipsoids in the world model, and the use of variational planning. We intend to sensitize the robot arm with a 'skin' of capacitive proximity sensors. These sensors were developed at NASA, and are exceptionally suited for the space application. In the first part of the report, we discuss the development and modeling of the capacitive proximity sensor. In the second part we discuss the motion planning algorithm.

Prinz, F. B.↗
NASA NTRSDate not supplied

A new template for developing C++ applications in NASA's Core Flight System

In this presentation, we will demonstrate an example Core Flight System (cFS) application written in C++, compatible with the Draco releases of the Core Flight Executive (cFE) and NASA Operating System Abstraction Layer (OSAL). The application boilerplate, supporting library, and associated generation script were recently developed and licensed under the permissive Apache License 2.0 with the goal of easing the cFS app development with C++. The design and features of this application will be presented, including a higher-level interface for interactions with the cFE software bus pipes, tables, and event services. Data structures are provided for centralized telecommand and telemetry parsing which isolates bookkeeping of message components from the calling code in an application's core logic. Specific advantages of writing a cFS application in C++ will be shown, including easier avoidance of symbol collisions via namespaces, expanded compile-time checks via constant expressions, default initialization for data structures, null safety via references, improved syntax for operating on multi-dimensional arrays, and reliable serialization of enumerations via enumeration classes. Special considerations needed for integrating a C++ application will be identified, including function linkage, exceptions, and stack unwinding. Evidence for the usefulness of this template will be discussed in the context of development of a flight software application used for interfacing with a solid-state data recorder.

Dominick Allen↗
NASA NTRS2010

Separation Assurance and Collision Avoidance

Objective SACA-1: Determine the level of safety provided by tactical separation assurance safety monitoring systems for UAS missions. a) Rationale: Continuous mission-risk monitoring can provide equivalent levels of safety for UAS operations possibly reducing the burden on other safety systems. b) Approach: Utilize and adapt algorithms and approaches developed for the NextGen Airspace Systems Program for UAS applications.

Lauderdale, Todd↗
NASA NTRS2018

Comparative Analysis of ACAS-Xu and DAIDALUS Detect-and-Avoid Systems

The Detect and Avoid (DAA) capability of a recent version (Run 3) of the Airborne Collision Avoidance System-Xu (ACAS-Xu) is measured against that of the Detect and AvoID Alerting Logic for Unmanned Systems (DAIDALUS), a reference algorithm for the Phase 1 Minimum Operational Performance Standards (MOPS) for DAA. This comparative analysis of the two systems' alerting and horizontal guidance outcomes is conducted through the lens of the Detect and Avoid mission using flight data of scripted encounters from a recent flight test. Results indicate comparable timelines and outcomes between ACAS-Xu's Remain Well Clear alert and guidance and DAIDALUS's corrective alert and guidance, although ACAS-Xu's guidance appears to be more conservative. ACAS-Xu's Collision Avoidance alert and guidance occurs later than DAIDALUS's warning alert and guidance, and overlaps with DAIDALUS's timeline of maneuver to remain Well Clear. Interesting discrepancies between ACAS-Xu's directive guidance and DAIDALUS's "Regain Well Clear" guidance occur in some scenarios.

Davies, Jason T.↗
NASA NTRS2015

Recommended Screening Practices for Launch Collision Aviodance

The objective of this document is to assess the value of launch collision avoidance (COLA) practices and provide recommendations regarding its implementation for NASA robotic missions. The scope of this effort is limited to launch COLA screens against catalog objects that are either spacecraft or debris. No modifications to manned safety COLA practices are considered in this effort. An assessment of the value of launch COLA can be broken down into two fundamental questions: 1) Does collision during launch represent a significant risk to either the payload being launched or the space environment? 2) Can launch collision mitigation be performed in a manner that provides meaningful risk reduction at an acceptable level of operational impact? While it has been possible to piece together partial answers to these questions for some time, the first attempt to comprehensively address them is documented in reference (a), Launch COLA Operations: an Examination of Data Products, Procedures, and Thresholds, Revision A. This report is the product of an extensive study that addressed fundamental technical questions surrounding launch collision avoidance analysis and practice. The results provided in reference (a) will be cited throughout this document as these two questions are addressed. The premise of this assessment is that in order to conclude that launch COLA is a value-added activity, the answer to both of these questions must be affirmative. A "no" answer to either of these questions points toward the conclusion that launch COLA provides little or no risk mitigation benefit. The remainder of this assessment will focus on addressing these two questions.

recommended screening practicies luanch collision ↗
NASA NTRS2014

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↗
NASA NTRS2015

An Assessment of the Efficacy of Launch Collision Avoidance Analysis in Providing Risk Reduction for NASA

The objective of this document is to assess the value of collision on launch assessment (COLA, often referred to as “launch COLA”) practices and provide recommendations regarding its implementation for NASA robotic missions. The scope of this effort is limited to launch COLA screens against catalog objects that are either spacecraft or debris. No modifications to manned safety launch COLA practices are considered in this effort. An assessment of the value of launch COLA can be broken down into two fundamental questions: 1) Does collision during launch represent a significant risk to either the payload being launched or the space environment? 2) Can launch collision mitigation be performed in a manner that provides meaningful risk reduction at an acceptable level of operational impact? While it has been possible to piece together partial answers to these questions for some time, the first attempt to comprehensively address them is documented in reference (a), Launch COLA Operations: an Examination of Data Products, Procedures, and Thresholds, Revision A. This report is the product of an extensive study that addressed fundamental technical questions surrounding launch collision avoidance analysis and practice. The results provided in reference (a) will be cited throughout this document as these two questions are addressed. The premise of this assessment is that in order to conclude that launch COLA is a value-added activity, the answer to both of these questions must be affirmative. A “no” answer to either of these questions points toward the conclusion that launch COLA provides little or no risk mitigation benefit. The remainder of this assessment will focus on addressing these two questions.

launch COLA↗
NASA NTRS2014

LightForce Photon-Pressure Collision Avoidance: Updated Efficiency Analysis Utilizing a Highly Parallel Simulation Approach

This paper provides an updated efficiency analysis of the LightForce space debris collision avoidance scheme. LightForce aims to prevent collisions on warning by utilizing photon pressure from ground based, commercial off the shelf lasers. Past research has shown that a few ground-based systems consisting of 10 kilowatt class lasers directed by 1.5 meter telescopes with adaptive optics could lower the expected number of collisions in Low Earth Orbit (LEO) by an order of magnitude. Our simulation approach utilizes the entire Two Line Element (TLE) catalogue in LEO for a given day as initial input. Least-squares fitting of a TLE time series is used for an improved orbit estimate. We then calculate the probability of collision for all LEO objects in the catalogue for a time step of the simulation. The conjunctions that exceed a threshold probability of collision are then engaged by a simulated network of laser ground stations. After those engagements, the perturbed orbits are used to re-assess the probability of collision and evaluate the efficiency of the system. This paper describes new simulations with three updated aspects: 1) By utilizing a highly parallel simulation approach employing hundreds of processors, we have extended our analysis to a much broader dataset. The simulation time is extended to one year. 2) We analyze not only the efficiency of LightForce on conjunctions that naturally occur, but also take into account conjunctions caused by orbit perturbations due to LightForce engagements. 3) We use a new simulation approach that is regularly updating the LightForce engagement strategy, as it would be during actual operations. In this paper we present our simulation approach to parallelize the efficiency analysis, its computational performance and the resulting expected efficiency of the LightForce collision avoidance system. Results indicate that utilizing a network of four LightForce stations with 20 kilowatt lasers, 85% of all conjunctions with a probability of collision Pc > 10 (sup -6) can be mitigated.

conjunction analysis↗
NASA NTRS2022

Functional Allocation Approach for Separation Assurance for Remotely Piloted Aircraft

A functional analysis framework is employed with the objective of exploring the separation assurance function for the remotely piloted aircraft system. The architecture of the remotely piloted aircraft system—highlighting several of the component systems and the functions resident onboard the remotely piloted aircraft and in the ground control station—is described to provide the context for understanding the complexity of the said system for a detailed functional analysis. The interactions between the agents of the separation assurance function belonging to the air traffic service provider, remotely piloted aircraft system operator and remotely piloted aircraft are described. Separation assurance by air traffic control, remain well clear by the remotely piloted aircraft system and collision avoidance onboard the remotely piloted aircraft are briefly discussed. The functional analysis framework is illustrated by relating the agents to the actions of (a) acquiring the surveillance information, (b) checking for conflicts, (c) creating the solutions for resolving conflicts and (d) implementing the conflict resolution solutions. This example is offered as a template by which a more detailed functional analysis of this and other functions could be developed. The architecture of the remotely piloted aircraft system is described to aid this process.

functional analysis↗
NASA NTRS2022

Functional Allocation Approach for Separation Assurance for Remotely Piloted Aircraft

A functional analysis framework is employed with the objective of exploring the separation assurance function for the remotely piloted aircraft system. The architecture of the remotely piloted aircraft system—highlighting several of the component systems and the functions resident onboard the remotely piloted aircraft and in the ground control station—is described to provide the context for understanding the complexity of the said system for a detailed functional analysis. The interactions between the agents of the separation assurance function belonging to the air traffic service provider, remotely piloted aircraft system operator and remotely piloted aircraft are described. Separation assurance by air traffic control, remain well clear by the remotely piloted aircraft system and collision avoidance onboard the remotely piloted aircraft are briefly discussed. The functional analysis framework is illustrated by relating the agents to the actions of (a) acquiring the surveillance information, (b) checking for conflicts, (c) creating the solutions for resolving conflicts and (d) implementing the conflict resolution solutions. This example is offered as a template by which a more detailed functional analysis of this and other functions could be developed. The architecture of the remotely piloted aircraft system is described to aid this process.

Functional analysis↗
NASA NTRS2023

Orbital Debris Remediation: Should We Move, Remove, or Reuse Debris?

One way of reducing the risks orbital debris poses to spacecraft operators is to remediate or “clean up” debris. A piece of debris can be remediated by removing it from space, moving it to avoid collision, or finding a way to recycle it. It is unclear which is the best option, so this panel will explore the trade-offs and move toward developing the best possible portfolio to clean up the orbital environment.

Thomas Colvin↗
NASA NTRS2002

Regaining Lost Separation in a Piloted Simulation of Autonomous Aircraft Operations

NASA is currently investigating a new concept of operations for the National Airspace System, designed to improve capacity while maintaining or improving current levels of safety. This concept, known as Distributed Air/Ground Traffic Management (DAG-TM), allows appropriately equipped autonomous aircraft to maneuver freely for flight optimization while resolving conflicts with other traffic and staying out of special use airspace and hazardous weather. While Airborne Separation Assurance System (ASAS) tools would normally allow pilots to resolve conflicts before they become hazardous, evaluation of system performance in sudden, near-term conflicts is needed in order to determine concept feasibility. If an acceptable safety level can be demonstrated in these situations, then operations may be conducted with lower separation minimums. An experiment was conducted in NASA Langley s Air Traffic Operations Lab to address issues associated with resolving near-term conflicts and the potential use of lower separation minimums. Sixteen commercial airline pilots flew a total of 32 traffic scenarios that required them to use prototype ASAS tools to resolve close range pop-up conflicts. Required separation standards were set at either 3 or 5 NM lateral spacing, with 1000 ft vertical separation being used for both cases. Reducing the lateral separation from 5 to 3 NM did not appear to increase operational risk, as indicated by the proximity to the intruder aircraft. Pilots performed better when they followed tactical guidance cues provided by ASAS than when they didn't follow the guidance. As air-air separation concepts are evolved, further studies will consider integration issues between ASAS and existing Airborne Collision Avoidance Systems (ACAS).These types of non-normal events will require the ASAS to provide effective alerts and resolutions prior to the time that an Airborne Collision Avoidance System (ACAS) would give a Resolution Advisory (RA). When an RA is issued, a pilot must take immediate action in order to avoid a potential near miss. The Traffic Alert and Collision Avoidance System (TCAS) II currently functions as an ACAS aboard commercial aircraft. Depending on the own aircraft s altitude, TCAS only issues RA s 15-35 seconds prior to the Closest Point of Approach (CPA). Prior to an RA, DAG-TM pilots operating autonomous aircraft must rely solely on ASAS for resolution guidance. An additional area of DAG-TM concept feasibility relates to a potential reduction in separation standards. Lower separation standards are likely needed in order to improve NAS efficiency and capacity. Current separation minimums are based in large part on the capabilities of older radar systems. Safety assessments are needed to determine the feasibility of reduced separation minimums. They will give strong consideration to surveillance system performance, including accuracy, integrity, and availability. Candidate surveillance systems include Automatic Dependent Surveillance-Broadcast (ADS-B) and multi-lateration systems. Considering studies done for Reduced Vertical Separation Minimums (RVSM) operations, it is likely that flight technical errors will also be considered. In addition to a thorough evaluation of surveillance system performance, a potential decision to lower the separation standards should also take operational considerations into account. An ASAS Safety Assessment study identified improper maneuvering in response to a conflict (due to ambiguous or improper resolution commands or a pilot s failure to comply with the resolution) as a potential safety risk. If near-term conflicts with lower separation minimums were determined to be more challenging for pilots, the severity of these risks could be even greater.

Barhydt, Richard↗
NASA NTRS2016

A Numerical Approach to Estimate the Ballistic Coefficient of Space Debris from TLE Orbital Data

Low Earth Orbit (LEO) is full of space debris, which consist of spent rocket stages, old satellites and fragments from explosions and collisions. As of 2009, more than 21,000 orbital debris larger than 10 cm are known to exist], and while it is hard to track anything smaller than that, the estimated population of particles between 1 and 10 cm in diameter is approximately 500,000, whereas small as 1 cm exceeds 100 million. These objects orbit Earth with huge kinetic energies speeds usually exceed 7 kms. The shape of their orbit varies from almost circular to highly elliptical and covers all LEO, a region in space between 160 and 2,000 km above sea level. Unfortunately, LEO is also the place where most of our active satellites are situated, as well as, International Space Station (ISS) and Hubble Space Telescope, whose orbits are around 400 and 550 km above sea level, respectively.This poses a real threat as debris can collide with satellites and deal substantial damage or even destroy them.Collisions between two or more debris create clouds of smaller debris, which are harder to track and increase overall object density and collision probability. At some point, the debris density couldthen reach a critical value, which would start a chain reaction and the number of space debris would grow exponentially. This phenomenon was first described by Kessler in 1978 and he concluded that it would lead to creation of debris belt, which would vastly complicate satellite operations in LEO. The debris density is already relatively high, as seen from several necessary debris avoidance maneuvers done by Shuttle, before it was discontinued, and ISS. But not all satellites have a propulsion system to avoid collision, hence different methods need to be applied. One of the proposed collision avoidance concepts is called LightForce and it suggests using photon pressure to induce small orbital corrections to deflect debris from colliding. This method is very efficient as seen from theoretical simulations, even few continuous mode 10 kW ground-based lasers, focused by 1.5 m telescopes with adaptive optics, were enough to prevent significant amount of the debris collisions. Simulations were done by propagating all space objects in LEO by 1 year into the future and checking whether the probability of collision was high. For those space objects different ground-based lasers were used to divert them, afterwards collision probabilities were reevaluated. However, the actual accuracy of the LightForce software, which has been developed at NASA AmesResearch Center, depends on the veracity of the input parameters, one of which is the objects ballistic coefficient. It is a measure of bodys ability to overcome air resistance, which has a significant impact on the debris in LEO, and thus it is responsible for the shape of the trajectory of the debris. Having the exact values of the ballistic coefficient would make significantly better collision predictions, unfortunately, we do not know what are the values for most of the objects.In this research, we were working with part of LightForce code, which estimates the ballistic coefficient from ephemerides. Previously used method gave highly inaccurate values, when compared to known objects, and it needed to be changed. The goal of this work was to try out a different method of estimating the ballistic coefficient and to check whether or not it gives noticeable improvements.

Collisions↗
NASA NTRS1992

Robot path planning for space-truss assembly

Construction, repair, and maintenance of space-based structures will require extensive planning of operations in order to effectively carry out these tasks. The path planning algorithm described here is a general approach to generating paths that guarantee collision avoidance for a single chain nonredundant or redundant robot. The algorithm uses a graph search of feasible points in position space, followed by a local potential field method that guarantees collision avoidance among objects, structures, and the robot arm as well as conformance to joint limit constraints. This algorithm is novel in its computation of goal attractive potential fields in Cartesian space, and computation of obstacle repulsive fields in robot joint space. These effects are combined to generate robot motion. Computation is efficiently implemented through the computation of the robot arm Jacobian and not the full inverse arm kinematics. These planning algorithms have been implemented and evaluated using existing space-truss designs, and are being integrated into the RPI-CIRSSE Testbed environment.

Muenger, Rolf↗
NASA NTRS2024

Computing Proximity to Threat Along Uncertain Trajectory to Support Urban Air Mobility

Many airspace threats affect the selection of a flight route, such as terrain, physical obstacles, adverse weather, and special-use airspace, among others. Threat avoidance during Urban Air Mobility (UAM) and Low Altitude Mobility (LAM) flights is especially challenging due to their lower cruising altitudes. These operations may be exposed to buildings, towers, trees, terrain undulations, etc., along much of their flight route. Moreover, these low-altitude flights in urban environments are expected to encounter very busy airspace, increasing the workload associated with threat avoidance. The Proximity to Threat (PtT) function aims to support onboard or remote pilots by computing the risk from geospatial threats in the airspace along an aircraft’s flight path. The threats are both static entities and dynamic airspace restrictions that have been modeled and stored in geo-referenced mapping databases. The flight path may be specified by waypoints, airways, or similar discrete route elements or by a time series of closely spaced position and altitude points. Flight path uncertainty can also be taken into account by assuming both the position and altitude to be sampled from two normal distributions, each being specified by a mean and variance. PtT uses this additional information to verify that the flight path remains clear of threats along a wider path or if a position is reached earlier or later than anticipated, assuring the pilot or operator that there will be an available safety margin even if the aircraft deviates due to one or more occurrences of unexpected wind gusts, mechanical failures, airspeed changes, collision avoidance maneuvers, etc. The client can specify an uncertainty confidence level to bound the set of trajectories evaluated for threats so that the confidence level corresponds to the client’s risk tolerance under the expected conditions. PtT can be used as a pre-flight planning tool to determine a safe route through known threats and in-flight to avoid emerging or changing threats. In this report, we present the PtT function, discuss how the trajectory uncertainty is incorporated into the PtT function, and describe the use of this PtT function in a representative scenario.

urban air mobility↗
NASA NTRSDate not supplied

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↗
NASA NTRS1990

The real-time learning mechanism of the Scientific Research Associates Advanced Robotic System (SRAARS)

Scientific research associates advanced robotic system (SRAARS) is an intelligent robotic system which has autonomous learning capability in geometric reasoning. The system is equipped with one global intelligence center (GIC) and eight local intelligence centers (LICs). It controls mainly sixteen links with fourteen active joints, which constitute two articulated arms, an extensible lower body, a vision system with two CCD cameras and a mobile base. The on-board knowledge-based system supports the learning controller with model representations of both the robot and the working environment. By consecutive verifying and planning procedures, hypothesis-and-test routines and learning-by-analogy paradigm, the system would autonomously build up its own understanding of the relationship between itself (i.e., the robot) and the focused environment for the purposes of collision avoidance, motion analysis and object manipulation. The intelligence of SRAARS presents a valuable technical advantage to implement robotic systems for space exploration and space station operations.

Chen, Alexander Y.↗
NASA NTRS2020

Evaluation, Analysis and Results of the DANTi Flight Test Data, the DAIDALUS Detect and Avoid Algorithm, and the DANTi Concept for Detect and Avoid in the Cockpit

The DAIDALUS Detect and Avoid Algorithm [1] was developed to address the operational needs of Unmanned Aerial Systems (UAS) and meet the Minimum Operational Performance Standards for Detect and Avoid [2]. The DANTi (Detect and Avoid iN the cockpit) concept [3], developed at the National Aeronautics and Space Administration (NASA) Langley Research Center, leverages advancements achieved in surveillance and Detect and Avoid technologies for unmanned aircraft systems as a safety enhancing capability for pilots of manned aircraft. Pilots operating under Visual Flight Rules and not receiving Air Traffic Control radar services rely on see and avoid to remain well clear of other aircraft and avoid collisions. The DANTi concept has been conceived as a safety enhancement capability to remain well clear and avoid potential collisions. The DANTi concept uses a traffic display to provide situational awareness, conflict detection, alerting, and guidance to remain well clear.

Detect and Avoid↗