Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “collision operators”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

NASA CARA Prelaunch Analysis and Process

NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.

conjunction assessment↗
NASA NTRSDate not supplied

NASA CARA Prelaunch Analysis and Process

NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.

conjunction assessment↗
NASA NTRS1980

Collision avoidance in space

Collisions in earth orbital space between operational payloads and various forms of space debris (nonoperational payloads, nonfunctional mission-related objects and fragments resulting from collisions and explosions) are discussed and possible means of avoiding them are considered. From 10,000 to 15,000 objects are estimated to be in earth orbital space, most of which represent spacecraft fragments and debris too small to be detected and tracked by earth-based sensors, and it is considered likely that some of them will be or have already been involved in direct collisions with the ever increasing number of operational satellites and space stations. Means of protecting proposed large space structures and smaller spacecraft from significant damage by larger space objects, particularly in the 400-4000 km altitude range where most debris occurs, include structural redundancy and the double shielding of sensitive components. Other means of collision avoidance are the collection or relocation of satellites, rocket bodies and other objects by the Space Shuttle, the prevention of explosions and the disposal of spent rocket parts by reentry. Finally, a management structure would be required to administer guidelines for the prevention and elimination of space debris.

Kessler, D. J.↗
NASA NTRS2018

[Micron]ADS-B Detect and Avoid Flight Tests on Phantom 4 Unmanned Aircraft System

Researchers at the National Aeronautics and Space Administration Armstrong Flight Research Center in Edwards, California and Vigilant Aerospace Systems collaborated for the flight-test demonstration of an Automatic Dependent Surveillance-Broadcast based collision avoidance technology on a small unmanned aircraft system equipped with the uAvionix Automatic Dependent Surveillance-Broadcast transponder. The purpose of the testing was to demonstrate that National Aeronautics and Space Administration / Vigilant software and algorithms, commercialized as the FlightHorizon UAS"TM", are compatible with uAvionix hardware systems and the DJI Phantom 4 small unmanned aircraft system. The testing and demonstrations were necessary for both parties to further develop and certify the technology in three key areas: flights beyond visual line of sight, collision avoidance, and autonomous operations. The National Aeronautics and Space Administration and Vigilant Aerospace Systems have developed and successfully flight-tested an Automatic Dependent Surveillance-Broadcast Detect and Avoid system on the Phantom 4 small unmanned aircraft system. The Automatic Dependent Surveillance-Broadcast Detect and Avoid system architecture is especially suited for small unmanned aircraft systems because it integrates: 1) miniaturized Automatic Dependent Surveillance-Broadcast hardware; 2) radio data-link communications; 3) software algorithms for real-time Automatic Dependent Surveillance-Broadcast data integration, conflict detection, and alerting; and 4) a synthetic vision display using a fully-integrated National Aeronautics and Space Administration geobrowser for three dimensional graphical representations for ownship and air traffic situational awareness. The flight-test objectives were to evaluate the performance of Automatic Dependent Surveillance-Broadcast Detect and Avoid collision avoidance technology as installed on two small unmanned aircraft systems. In December 2016, four flight tests were conducted at Edwards Air Force Base. Researchers in the ground control station looking at displays were able to verify the Automatic Dependent Surveillance-Broadcast target detection and collision avoidance resolutions.

avoidance↗
NASA NTRS2019

Cloud Computing Methods for Near Rectilinear Halo Orbit Trajectory Design

Complicated mission design problems require innovative computational solutions. As spacecraft depart from a proposed Gateway in a Near Rectilinear Halo Orbit (NRHO), recontact analysis is required to avoid risk of collision and ensure safe operations. Escape dynamics from NRHOs are governed by multiple gravitational bodies, yielding a trajectory design space that is exhaustively large. This paper summarizes the recontact analysis for departure from the NRHO and describes how the Deep Space Trajectory Explorer (DSTE) trajectory design software incorporates high performance cloud computing to compute and visualize the orbit design space. Recent focus on exploration missions to cislunar space has kindled accelerated interest in multibody orbit solutions. Trajectory analysis in the presence of multiple gravity fields is complex, and innovative computational tools are needed to simplify complicated design spaces, to generate large quantities of data quickly, and to visualize the output for user accessibility. The Gateway mission is a prime example. The Gateway1 is proposed as a human outpost in deep space. The current baseline orbit for the Gateway is a Near Rectilinear Halo Orbit (NRHO) near the Moon.2 The NRHO exists in a regime that experiences the gravitational effects of the Earth and the Moon simultaneously, complicating orbit analysis. The mission design process benefits greatly from updated computational tools for multibody missions like the Gateway. As an example, consider the problem of assessing the risk of collision in an NRHO. As a staging location to missions to the lunar surface and beyond the Earth-Moon system, the Gateway will experience spacecraft and other objects regularly arriving and departing. Departing objects potentially include spent logistics modules, visiting crew vehicles, debris objects, wastewater particles, and cubesats. Each departure is governed by the dynamics of the Gateway orbit and the surrounding dynamical environment. Over time, any unmaintained object in such an orbit eventually departs due to the small instabilities associated with the NRHOs. A separation maneuver speeds the departure from the NRHO, but the effects of the maneuver on the spacecraft behavior depend on the location, magnitude, and direction of the burn. Escape dynamics from the NRHO with regard to these maneuver options open up an enormous potential trajectory design space where subtle changes in input can produce dramatically large changes in the results. Any departing object must avoid recontacting the Gateway as it leaves the lunar vicinity, and a recontact analysis thus involves a significant number of computations and extensive output data. To explore the dynamics of this extensive design space, the Deep Space Trajectory Explorer3 (DSTE) trajectory design software incorporates new High Performance Computing (HPC) services and novel interactive visualizations. This paper details the HPC and cloud infrastructure techniques that are implemented in the DSTE, applying the new capabilities to analysis of recontact risk with the Gateway in NRHO. NEAR RECTILINEAR HALO ORBITS The Gateway is planned to fly in a lunar NRHO as its baseline orbit. The NRHO families of orbits are subsets of the larger halo families, which originate from planar orbits near the L1 and L2 libration points; the Earth-Moon L2 halo family appears in Figure 1. Each halo orbit is perfectly periodic in the Circular Restricted 3-Body Problem (CR3BP) and becomes a quasi-periodic orbit in a higher fidelity ephemeris force model. The NRHOs are defined as those members of the halo family with bounded stability properties;2 they pass near the Moon at perilune and are nearly polar. Families exist with apolunes located both above the lunar north pole and above the lunar south pole; the Gateway is planned to reside in a southern L2 NRHO in a 9:2 resonance with the lunar synodic period. The 9:2 NRHO is characterized by a period of about 6.5 days, a perilune radius of about 3,500 km, and an apolune radius of about 71,000 km; it is strongly affected by the gravity of both the Earth and the Moon simultaneously. This NRHO offers extended communications with assets on the south pole of the Moon,4 as well as low-cost orbit maintenance and attitude control,5 favorable eclipse avoidance properties,6 and inexpensive transfers from Earth and to other destinations.5,7 The NRHO portion of the southern L2 halo family is highlighted in black in Figure 1, and the 9:2 NRHO appears in blue.

Phillips, Sean M.↗
NASA NTRS2015

An Updated Process for Automated Deepspace Conjunction Assessment

There is currently a high level of interest in the areas of conjunction assessment and collision avoidance from organizations conducting space operations. Current conjunction assessment activity is mainly focused on spacecraft and debris in the Earth orbital environment [1]. However, collisions are possible in other orbital environments as well [2]. This paper will focus on the current operations of and recent updates to the Multimission Automated Deep Space Conjunction Assessment Process (MADCAP) used at the Jet Propulsion Laboratory for NASA to perform conjunction assessment at Mars and the Moon. Various space agencies have satellites in orbit at Mars and the Moon with additional future missions planned. The consequences of collisions are catastrophically high. Intuitive notions predict low probability of collisions in these sparsely populated environments, but may be inaccurate due to several factors. Orbits of scientific interest often tend to have similar characteristics as do the orbits of spacecraft that provide a communications relay for surface missions. The MADCAP process is controlled by an automated scheduler which initializes analysis based on a set timetable or the appearance of new ephemeris files either locally or on the Deep Space Network (DSN) Portal. The process then generates and communicates reports which are used to facilitate collision avoidance decisions. The paper also describes the operational experience and utilization of the automated tool during periods of high activity and interest such as: the close approaches of NASA's Lunar Atmosphere & Dust Environment Explorer (LADEE) and Lunar Reconnaissance Orbiter (LRO) during the LADEE mission. In addition, special consideration was required for the treatment of missions with rapidly varying orbits and less reliable long term downtrack estimates; in particular this was necessitated by perturbations to MAVEN's orbit induced by the Martian atmosphere. The application of special techniques to non-operational spacecraft with large uncertainties is also studied. Areas for future work are also described. Although the applications discussed in this paper are in the Martian and Lunar environments, the techniques are not unique to these bodies and could be applied to other orbital environments.

collision↗
NASA NTRS2008

The Effect of a Potentially Low Solar Cycle #24 on Orbital Lifetimes of Fengyun 1-C Debris

The magnitude of Solar Cycle #24 will have a non-trivial impact on the lifetimes of debris pieces that resulted from the intentional hypervelocity impact of the Fengyun 1-C satellite in January 2007. Recent solar flux measurements indicate Solar Cycle #24 has begun in the last few months, and will continue until approximately 2019. While there have been differing opinions on whether the intensity of this solar cycle will be higher or lower than usual, the Space Weather Prediction Center within the National Oceanic Atmospheric Administration (NOAA/SWPC) has recently forecast unusually low solar activity, which would result in longer orbital lifetimes. Using models for both the breakup of Fengyun 1-C and the propagation of the resultant debris cloud, the Orbital Debris Program Office at NASA Johnson Space Center conducted a study to better understand the impact of the solar cycle on lifetimes for pieces as small as 1 mm. Using a modified collision breakup model and PROP3D propagation software, the orbits of nearly 2 million objects 1 mm and larger were propagated for up to 200 years. By comparing a normal solar cycle with that of the NOAA/SWPC forecast low cycle, the effect of the solar flux on the lifetimes of the debris pieces is evaluated. The modeling of the low solar cycle shows an additional debris count of 12% for pieces larger than 10 cm by 2019 when compared to the resultant debris count using a normal cycle. The difference becomes more exaggerated (over 15%) for debris count in the smaller size regimes. However, in 50 years, the models predict the differences in debris count from differing models of Solar Cycle #24 to be less than 10% for all size regimes, with less variance in the smaller sizes. Understanding the longevity of the debris cloud will affect collision probabilities for both operational spacecraft and large derelict objects over the next century and beyond.

Whitlock, David↗
NASA NTRS1990

The JPL/KSC telerobotic inspection demonstration

An ASEA IRB90 robotic manipulator with attached inspection cameras was moved through a Space Shuttle Payload Assist Module (PAM) Cradle under computer control. The Operator and Operator Control Station, including graphics simulation, gross-motion spatial planning, and machine vision processing, were located at JPL. The Safety and Support personnel, PAM Cradle, IRB90, and image acquisition system, were stationed at the Kennedy Space Center (KSC). Images captured at KSC were used both for processing by a machine vision system at JPL, and for inspection by the JPL Operator. The system found collision-free paths through the PAM Cradle, demonstrated accurate knowledge of the location of both objects of interest and obstacles, and operated with a communication delay of two seconds. Safe operation of the IRB90 near Shuttle flight hardware was obtained both through the use of a gross-motion spatial planner developed at JPL using artificial intelligence techniques, and infrared beams and pressure sensitive strips mounted to the critical surfaces of the flight hardward at KSC. The Demonstration showed that telerobotics is effective for real tasks, safe for personnel and hardware, and highly productive and reliable for Shuttle payload operations and Space Station external operations.

Mittman, David↗
NASA NTRS1972

A method for direct numerical integration of the Boltzmann equation

The principal difficulties in numerical solution of the Boltzmann equation are considered. The study is aimed at formulating a numerical solution in such a manner that it contains a minimum amount of excess information at the distribution function level. It is pointed out that the accurate calculation of the distribution function at each point in phase space requires a tremendous number of operations, due to the necessity of solving five-fold quadratures in the collision integral. This results in the operational memory of the digital computer being insufficient to store all the data on the distribution functions at the necessary points in phase space. An algorithm is constructed involving successive iterations of the Boltzmann equation which does not require storage of each step of the new distribution function.

Cheremisin, F. G.↗
NASA NTRS1992

Interactive collision detection

The assembly of Space Station Freedom will require operations where large bodies are manipulated in close proximity to one other. A fast and reliable method for performing collision detection would greatly benefit the development and verification of such operations. The Interactive Graphics and Operations Analysis Laboratory (IGOAL) has developed an algorithm for performing collision detection which provides accurate results at interactive speeds. This algorithm uses a highly-optimized ray tracer for performing the analysis. The purpose of this presentation is to describe the algorithm and demonstrate its capabilities.

Bell, Brad↗
NASA NTRS2019

Prototyping Operational Autonomy for Space Traffic Management

Current state of the art in Space Traffic Management (STM) relies on a handful of providers for surveillance and collision prediction, and manual coordination between operators. Neither is scalable to support the expected 10x increase in spacecraft population in less than 10 years, nor does it support automated manuever planning. We present a software prototype of an STM architecture based on open Application Programming Interfaces (APIs), drawing on previous work by NASA to develop an architecture for low-altitude Unmanned Aerial System Traffic Management. The STM architecture is designed to provide structure to the interactions between spacecraft operators, various regulatory bodies, and service suppliers, while maintaining flexibility of these interactions and the ability for new market participants to enter easily. Autonomy is an indispensable part of the proposed architecture in enabling efficient data sharing, coordination between STM participants and safe flight operations. Examples of autonomy within STM include syncing multiple non-authoritative catalogs of resident space objects, or determining which spacecraft maneuvers when preventing impending conjunctions between multiple spacecraft. The STM prototype is based on modern micro-service architecture adhering to OpenAPI standards and deployed in industry standard Docker containers, facilitating easy communication between different participants or services. The system architecture is designed to facilitate adding and replacing services with minimal disruption. We have implemented some example participant services (e.g. a space situational awareness provider/SSA, a conjunction assessment supplier/CAS, an automated maneuver advisor/AMA) within the prototype. Different services, with creative algorithms folded into then, can fulfil similar functional roles within the STM architecture by flexibly connecting to it using pre-defined APIs and data models, thereby lowering the barrier to entry of new players in the STM marketplace. We demonstrate the STM prototype on a multiple conjunction scenario with multiple maneuverable spacecraft, where an example CAS and AMA can recommend optimal maneuvers to the spacecraft operators, based on a predefined reward function. Such tools can intelligently search the space of potential collision avoidance maneuvers with varying parameters like lead time and propellant usage, optimize a customized reward function, and be implemented as a scheduling service within the STM architecture. The case study shows an example of autonomous maneuver planning is possible using the API-based framework. As satellite populations and predicted conjunctions increase, an STM architecture can facilitate seamless information exchange related to collision prediction and mitigation among various service applications on different platforms and servers. The availability of such an STM network also opens up new research topics on satellite maneuver planning, scheduling and negotiation across disjoint entities.

space traffic management↗
NASA NTRS1995

Molecular vibrational states during a collision

Alternative algebraic techniques to approximate a given Hamiltonian by a harmonic oscillator are described both for time-independent and time-dependent systems. We apply them to the description of a one dimensional atom-diatom collision. From the resulting evolution operator, we evaluate vibrational transition probabilities as well as other time-dependent properties. As expected, the ground vibrational state becomes a squeezed state during the collision.

Recamier, Jose A.↗
NASA NTRS2015

Risk-Based Causal Modeling of Airborne Loss of Separation

Maintaining safe separation between aircraft remains one of the key aviation challenges as the Next Generation Air Transportation System (NextGen) emerges. The goals of the NextGen are to increase capacity and reduce flight delays to meet the aviation demand growth through the 2025 time frame while maintaining safety and efficiency. The envisioned NextGen is expected to enable high air traffic density, diverse fleet operations in the airspace, and a decrease in separation distance. All of these factors contribute to the potential for Loss of Separation (LOS) between aircraft. LOS is a precursor to a potential mid-air collision (MAC). The NASA Airspace Operations and Safety Program (AOSP) is committed to developing aircraft separation assurance concepts and technologies to mitigate LOS instances, therefore, preventing MAC. This paper focuses on the analysis of causal and contributing factors of LOS accidents and incidents leading to MAC occurrences. Mid-air collisions among large commercial aircraft are rare in the past decade, therefore, the LOS instances in this study are for general aviation using visual flight rules in the years 2000-2010. The study includes the investigation of causal paths leading to LOS, and the development of the Airborne Loss of Separation Analysis Model (ALOSAM) using Bayesian Belief Networks (BBN) to capture the multi-dependent relations of causal factors. The ALOSAM is currently a qualitative model, although further development could lead to a quantitative model. ALOSAM could then be used to perform impact analysis of concepts and technologies in the AOSP portfolio on the reduction of LOS risk.

Geuther, Steven C.↗
NASA NTRS1991

Collision avoidance for CTV: Requirements and capabilities

Collision avoidance must be ensured during Cargo Transfer Vehicle (CTV) operations near the space station. The design of the Collision Avoidance Maneuver (CAM) will involve analysis of CTV failure modes during rendezvous and proximity operations as well as analysis of possible problems external to the CTV, but that would require CTV to execute a CAM. In considering the requirements and design of the CAM for the CTV, the CAM design for the Orbital Maneuvering Vehicle (OMV) is a useful reference point from which some lessons can be learned and many CTV design options can be set forth.

Nosek, Thomas↗
NASA NTRSDate not supplied

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

Defining the Collision Avoidance Region for DAA Systems

Unmanned aircraft systems (UAS) will be required to equip with a detect-­‐and-­‐avoid (DAA) system in order to satisfy the federal aviation regulations to maintain well clear of other aircraft, some of which may be equipped with a Traffic Collision Avoidance System (TCAS) to mitigate the possibility of mid-­‐air collisions. As such, the minimum operational performance standards (MOPS) for UAS DAA systems are being designed with TCAS interoperability in mind by a group of industry, government, and academic institutions named RTCA Special Committee-228 (SC-228). This document will discuss the development of the spatial-­‐temporal volume known as the collision avoidance region in which the DAA system is not allowed to provide vertical guidance to maintain or regain DAA well clear that could conflict with resolution advisories (RAs) issued by the intruder aircraft's TCAS system. Three collision avoidance region definition candidates were developed based on the existing TCAS RA and DAA alerting definitions. They were evaluated against each other in terms of their interoperability with TCAS RAs and DAA alerts in an unmitigated factorial encounter analysis of 1.3 million simulated pairs.

collision avoidance region↗