Results for “proximal operator” — Page 7

NASA NTRSDate not supplied

Comparing Pre-Launch Assumptions to In-Flight Navigation Performance of OSIRIS-REx

The Sample Return Capsule (SRC) onboard the NASA Origins, Spectral Inter-pretation, Resource Identification, and Security–Regolith Explorer (OSIRIS-REx)spacecraft is currently carrying samples of the B-type asteroid Bennu for safe re-turn to Earth at the Utah Test and Training Range on September 24, 2023. These samples were collected during the Touch And Go (TAG) sampling event on October 20, 2020, when the spacecraft contacted the surface for a few seconds at a location less than 1 meter from the target. The unprecedented navigation performance achieved during that event was the culmination of experience gained during two years of cruise and two years of increasingly challenging operation sat Bennu. As we had hoped, the proximity navigation performance at Bennu exceeded pre-launch analysis. This paper will compare the navigation performance through the proximity operation phases to our pre-launch analysis and will quantify how refinements of the small force models governing the spacecraft motion near Bennu considerably improved the down-track state predictions leading up to the successful TAG event. It was evident to the team and to expert peer reviewers during the design phase that exquisite model fidelity and aggressive operational concepts, which challenged and advanced the state of the art for deep space proximity operations, would be required to meet the mission’s objectives. This paper summarizes the superlative achievements of the team in rising to and overcoming these challenges.

Peter G Antresian↗

NASA NTRSDate not supplied

International Space Station Bipropellant Plume Contamination Model Update for Short Thruster Pulse Widths

The International Space Station (ISS) Bipropellant Plume Contamination Model has been a vital tool for characterizing the thruster plume-induced contamination environment at the ISS but was not intended to be used for very short thruster pulse widths. This paper presents an updated model that ensures full start-up and shut-down phases are modeled for each thruster firing, when the majority of liquid phase contaminant mass is released. The updated ISS Bipropellant Plume Contamination Model prevents potential under-prediction of thruster plume-induced contamination due to visiting vehicle proximity operations and provides a way to take advantage of thruster start-up and shut-down data performance data gathered during thruster test programs, if available. The International Space Station (ISS) Bipropellant Plume Contamination Model developed by Boeing Space Environments is a semi-empirical model anchored in flight experiment data and has been a vital tool for characterizing the thruster plume-induced contamination environment at the ISS.[1] The current model utilizes flight experiment data from the Plume Impingement Contamination (PIC) and Shuttle Plume Impingement Flight Experiment (SPIFEX) studies, which include Orbiter 3870 N Primary Reaction Control System (PRCS) and Russian 130 N thrusters operating in pulse mode with 80-100 ms.[2] As the next generation of crew and cargo visiting vehicles are developed and arrive at ISS, minimum pulse widths of vehicle thrusters used for ISS proximity operations have decreased significantly below 80 ms. An update to the ISS Bipropellant Contamination Model is needed to prevent potential under-prediction of thruster plume-induced contamination for these very short pulse widths. Contamination due to thruster plumes occurs in the liquid phase (i.e., unburned or partially burned propellant in the plume). Liquid phase releases primarily occur during thruster start-up and shut-down phases, with the steady state phase contributing a small amount to the total contaminant mass released. The current ISS Bipropellant Plume Contamination Model includes functional dependencies on thruster parameters (thrust, mass flow rate, specific impulse (Isp)), distance to receiver surface, and angle off plume centerline. For modeling purposes, contaminant mass released scales linearly with pulse width. This is a conservative approach for pulse widths greater than 80 ms but could under-predict contamination for very short pulse widths (i.e., with little or no steady state phase). This paper presents a model update to add a functional dependency on commanded pulse width to ensure the portion of the pulse spent in start-up and shut-down phases is appropriately modeled, when the majority of liquid phase contaminant mass is released. The updated model prevents potential under-prediction of thruster plume-induced contamination due to visiting vehicle proximity operations while providing a way to take advantage of thruster start-up and shut-down data gathered during test programs, if available. Developing the plume model for a specific thruster using the ISS Bipropellant Plume Contamination Model must be done in consideration of all available thruster performance data. Example thruster data will be used to illustrate this point and options for implementing the model update with existing ISS Bipropellant Plume Contamination Model code will be discussed.

plume contamination↗

NASA NTRS2009

Hubble Servicing Challenges Drive Innovation of Shuttle Rendezvous Techniques

Hubble Space Telescope (HST) servicing, performed by Space Shuttle crews, has contributed to what is arguably one of the most successful astronomy missions ever flown. Both nominal and contingency proximity operations techniques were developed to enable successful servicing, while lowering the risk of damage to HST systems, and improve crew safety. Influencing the development of these techniques were the challenges presented by plume impingement and HST performance anomalies. The design of both the HST and the Space Shuttle was completed before the potential of HST contamination and structural damage by shuttle RCS jet plume impingement was fully understood. Relative navigation during proximity operations has been challenging, as HST was not equipped with relative navigation aids. Since HST reached orbit in 1990, proximity operations design for servicing missions has evolved as insight into plume contamination and dynamic pressure has improved and new relative navigation tools have become available. Servicing missions have provided NASA with opportunities to gain insight into servicing mission design and development of nominal and contingency procedures. The HST servicing experiences and lessons learned are applicable to other programs that perform on-orbit servicing and rendezvous, both human and robotic.

Goodman, John L.↗

NASA NTRS2011

Guidance, Navigation, and Control Program

The Rendezvous and Proximity Operations Program (RPOP) is real-time guidance, navigation, and control (GN&C) domain piloting-aid software that provides 3D Orbiter graphics and runs on the Space Shuttle's Criticality-3 Payload and General Support Computer (PGSC) in the crew cockpit. This software provides the crew with Situational Awareness during the rendezvous and proximity operations phases of flight. RPOP can be configured from flight to flight, accounting for mission-specific flight scenarios and target vehicles, via initialization load (I-load) data files. The software provides real-time, automated, closed-loop guidance recommendations and the capability to integrate the crew s manual backup techniques. The software can bring all relative navigation sensor data, including the Orbiter's GPC (general purpose computer) data, into one central application to provide comprehensive situational awareness of the rendezvous and proximity operations trajectory. RPOP also can separately maintain trajectory estimates (past, current, and predicted) based on certain data types and co-plot them, in order to show how the various navigation solutions compare. RPOP s best estimate of the relative trajectory is determined by a relative Kalman filter processing data provided by the sensor suite s most accurate sensor, the trajectory control sensor (TCS). Integrated with the Kalman filter is an algorithm that identifies the reflector that the TCS is tracking. Because RPOP runs on PC laptop computers, the development and certification lifecycles are more agile, flexible, and cheaper than those that govern the Orbiter FSW (flight software) that runs in the GPC. New releases of RPOP can be turned around on a 3- to 6-month template, from new Change Request (CR) to certification, depending on the complexity of the changes.

Hinkel, Heather↗

NASA NTRS2010

The Evolution of the Rendezvous Profile During the Space Shuttle Program

The rendezvous and proximity operations approach design techniques for space shuttle missions has changed significantly during the life of the program in response to new requirements that were not part of the original mission design. The flexibility of the shuttle onboard systems design and the mission planning process has allowed the program to meet these requirements. The design of the space shuttle and the shift from docking to grappling with a robotic ann prevented use of legacy Apollo rendezvous techniques. Over the life of the shuttle program the rendezvous profile has evolved due to several factors, including lowering propellant consumption and increasing flexibility in mission planning. Many of the spacecraft that the shuttle rendezvoused with had unique requirements that drove the creation of mission-unique proximity operations. The dockings to the Russian Mir space station and International Space Station (ISS) required further evolution of rendezvous and proximity operations techniques and additional sensors to enhance crew situational awareness. After the Columbia accident, a Rendezvous Pitch Maneuver (RPM) was added to allow tile photography from ISS. Lessons learned from these rendezvous design changes are applicable to future vehicle designs and operations concepts.

Summa, William R.↗

NASA NTRS2000

Trajectories in Close Proximity to Asteroids

Spacecraft motion in close proximity to irregularly shaped, rotating bodies such as asteroids presents a unique dynamical environment as compared to most space missions. There are several fundamental novelties in this environment that spacecraft must deal with. These include the possibility of orbital instabilities that can act over very short time spans (on the order of hours for some systems), possible non-uniform rotation of the central gravity field, divergence of traditional gravity field representations when close to the asteroid surface, dominance of perturbing forces, an extremely large asteroid model parameter space that must be prepared for in the absence of reliable information, and the possibility of employing new and novel trajectory control techniques such as hovering and repeated landings on the asteroid surface. An overview of how these novelties impact the space of feasible close proximity operations and how different asteroid model properties will affect their implementation is given. In so doing, four fundamental types of close proximity operations will be defined. Listed in order of increasing technical difficulty these are: (1) close, stable orbits; (2) low-altitude flyovers; (3) landing trajectories; and (4) hovering trajectories. The feasibility and difficulty of implementing these operations will vary as a function of the asteroid shape, size, density, and rotation properties, and as a function of the spacecraft navigation capability. Additional information is contained in the original extended abstract.

Scheeres, D. J.↗

NASA NTRS2013

The Regolith Biters: A Divide-And-Conquer Architecture for Sample-Return Missions

The collective interaction of simple systems can be leveraged to attain complex goals. Based on this principle, we envision space system architectures where the core functional components are decoupled, autonomous, and cooperative. We aim to pursue this vision in the context of small-body sample-return missions. After all, no experimental study sheds more light into our understanding of the origin and evolution of the Solar System than the analysis of samples from asteroids and comets. We also believe that their study is important from a strategic perspective: meteorite impacts pose a direct and credible threat to life on Earth, and the development of contingency small-body deflection missions presupposes some knowledge of the target body. The current architectural paradigm for sample-return missions is centered around a design where spacecraft and sampling device are merged into a single, complex system. We argue that this monolithic approach couples the navigation and sample-collection problems, making both more difficult. In contrast, we propose a decoupled system based on the coordinated interaction between a spacecraft and a collective of small, simple devices - the Regolith Biters (RBs). A spacecraft carrying a number of RBs would travel to the vicinity of a small body. From a favorable vantage point, and while remaining within a safe distance in a non-colliding trajectory, it would release the RBs towards the target body. Upon encountering the body, they would bite the regolith (thus retaining a sample), and eject back to orbit. The spacecraft, being endowed with appropriate navigation and tracking capabilities, would rendezvous with and collect those RBs within its reach, and bring them back to Earth. Separating the navigation and sampling concerns removes the need for proximity operations with the small body-the stage in current architectures that carries the most challenges and risks. Eliminating the need for proximity operations brings back to the discussion the exploration of exciting prospects, like highly active comets, fast-rotating bodies, and binary systems. Distributing the sampling problem among a collective of agents provides the opportunity to sample multiple regions in a single mission. It also provides robustness to various environmental conditions, and may enable the distributed, in situ characterization of the body. In the search for reliability, current architectures rely on complexity: an elaborate system should succeed at once. We rely on numbers: a given agent may fail at any stage, but success is attained by the collective.

Asteroids↗

NASA NTRSDate not supplied

A Comparison of Bearing Measurements to Surface Features Generated Using Stereophotoclinometry and Surface Feature Navigation Techniques

The Origins Spectral Interpretation Resource Identification Security Regolith Explorer (OSIRIS-REx) mission to the asteroid Bennu completed successful two-and-a-half year proximity operations in May 2021. The mission comprehensively mapped Bennu at unprecedented detail and collected a sample of Bennu’s surface to return to Earth. Throughout proximity operations, the OSIRIS-REx navigation team used the maps made of Bennu’s surface to navigate in the Bennu environment with high accuracy through the use of precise and accurate optical navigation data, radiometric data, and force modelling. The primary type of optical navigation measurements extracted from the images captured by OSIRIS-REx (particularly after first entering orbit around Bennu) were observations of known features on Bennu’s surface. Two related but different techniques/tools were used to extract these observations from the images: the Goddard Image Analysis and Navigation Tool Surface Feature Navigation (GIANT SFN) and Stereophotoclinometry (SPC) Autoregister. In this paper we compare the differences between the observables extracted using GIANT SFN and SPC Autoregister, explain the differences, and discuss where each technique is best suited.

Andrew Liounis↗

NASA NTRS2007

Automated Rendezvous and Docking Sensor Testing at the Flight Robotics Laboratory

The Exploration Systems Architecture defines missions that require rendezvous, proximity operations, and docking (RPOD) of two spacecraft both in Low Earth Orbit (LEO) and in Low Lunar Orbit (LLO). Uncrewed spacecraft must perform automated and/or autonomous rendezvous, proximity operations and docking operations (commonly known as Automated Rendezvous and Docking, AR&D). The crewed versions may also perform AR&D, possibly with a different level of automation and/or autonomy, and must also provide the crew with relative navigation information for manual piloting. The capabilities of the RPOD sensors are critical to the success of the Exploration Program. NASA has the responsibility to determine whether the Crew Exploration Vehicle (CEV) contractor-proposed relative navigation sensor suite will meet the CEV requirements. The relatively low technology readiness of relative navigation sensors for AR&D has been carried as one of the CEV Projects top risks. The AR&D Sensor Technology Project seeks to reduce this risk by increasing technology maturation of selected relative navigation sensor technologies through testing and simulation, and to allow the CEV Project to assess the relative navigation sensors.

Mitchell, J.↗

NASA NTRS2007

Automated Rendezvous and Docking Sensor Testing at the Flight Robotics Laboratory

The Exploration Systems Architecture defines missions that require rendezvous, proximity operations, and docking (RPOD) of two spacecraft both in Low Earth Orbit (LEO) and in Low Lunar Orbit (LLO). Uncrewed spacecraft must perform automated and/or autonomous rendezvous, proximity operations and docking operations (commonly known as Automated Rendezvous and Docking, (AR&D).) The crewed versions of the spacecraft may also perform AR&D, possibly with a different level of automation and/or autonomy, and must also provide the crew with relative navigation information for manual piloting. The capabilities of the RPOD sensors are critical to the success of the Exploration Program. NASA has the responsibility to determine whether the Crew Exploration Vehicle (CEV) contractor-proposed relative navigation sensor suite will meet the CEV requirements. The relatively low technology readiness of relative navigation sensors for AR&D has been carried as one of the CEV Projects top risks. The AR&D Sensor Technology Project seeks to reduce this risk by increasing technology maturation of selected relative navigation sensor technologies through testing and simulation, and to allow the CEV Project to assess the relative navigation sensors.

Howard, Richard T.↗

NASA NTRS2008

Integrated Docking Simulation and Testing with the Johnson Space Center Six-Degree of Freedom Dynamic Test System

The Exploration Systems Architecture defines missions that require rendezvous, proximity operations, and docking (RPOD) of two spacecraft both in Low Earth Orbit (LEO) and in Low Lunar Orbit (LLO). Uncrewed spacecraft must perform automated and/or autonomous rendezvous, proximity operations and docking operations (commonly known as Automated Rendezvous and Docking, AR&D). The crewed versions may also perform AR&D, possibly with a different level of automation and/or autonomy, and must also provide the crew with relative navigation information for manual piloting. The capabilities of the RPOD sensors are critical to the success of the Constellation Program; this is carried as one of the CEV Project top risks. The Exploration Technology Development Program (ETDP) AR&D Sensor Technology Project seeks to reduce this risk by increasing technology maturation of selected relative navigation sensor technologies through testing and simulation. One of the project activities is a series of "pathfinder" testing and simulation activities to integrate relative navigation sensors with the Johnson Space Center Six-Degree-of-Freedom Test System (SDTS). The SDTS will be the primary testing location for the Orion spacecraft s Low Impact Docking System (LIDS). Project team members have integrated the Orion simulation with the SDTS computer system so that real-time closed loop testing can be performed with relative navigation sensors and the docking system in the loop during docking and undocking scenarios. Two relative navigation sensors are being used as part of a "pathfinder" activity in order to pave the way for future testing with the actual Orion sensors. This paper describes the test configuration and test results.

Mitchell, Jennifer D.↗

NASA NTRS2007

Multi-Sensor Testing for Automated Rendezvous and Docking Sensor Testing at the Flight Robotics Laboratory

The Exploration Systems Architecture defines missions that require rendezvous, proximity operations, and docking (RPOD) of two spacecraft both in Low Earth Orbit (LEO) and in Low Lunar Orbit (LLO). Uncrewed spacecraft must perform automated and/or autonomous rendezvous, proximity operations and docking operations (commonly known as AR&D). The crewed missions may also perform rendezvous and docking operations and may require different levels of automation and/or autonomy, and must provide the crew with relative navigation information for manual piloting. The capabilities of the RPOD sensors are critical to the success of the Exploration Program. NASA has the responsibility to determine whether the Crew Exploration Vehicle (CEV) contractor proposed relative navigation sensor suite will meet the requirements. The relatively low technology readiness level of AR&D relative navigation sensors has been carried as one of the CEV Project's top risks. The AR&D Sensor Technology Project seeks to reduce the risk by the testing and analysis of selected relative navigation sensor technologies through hardware-in-the-loop testing and simulation. These activities will provide the CEV Project information to assess the relative navigation sensors maturity as well as demonstrate test methods and capabilities. The first year of this project focused on a series of"pathfinder" testing tasks to develop the test plans, test facility requirements, trajectories, math model architecture, simulation platform, and processes that will be used to evaluate the Contractor-proposed sensors. Four candidate sensors were used in the first phase of the testing. The second phase of testing used four sensors simultaneously: two Marshall Space Flight Center (MSFC) Advanced Video Guidance Sensors (AVGS), a laser-based video sensor that uses retroreflectors attached to the target vehicle, and two commercial laser range finders. The multi-sensor testing was conducted at MSFC's Flight Robotics Laboratory (FRL) using the FRL's 6-DOF gantry system, called the Dynamic Overhead Target System (DOTS). The target vehicle for "docking" in the laboratory was a mockup that was representative of the proposed CEV docking system, with added retroreflectors for the AVGS. The multi-sensor test configuration used 35 open-loop test trajectories covering three major objectives: (1) sensor characterization trajectories designed to test a wide range of performance parameters; (2) CEV-specific trajectories designed to test performance during CEV-like approach and departure profiles; and (3) sensor characterization tests designed for evaluating sensor performance under more extreme conditions as might be induced during a spacecraft failure or during contingency situations. This paper describes the test development, test facility, test preparations, test execution, and test results of the multi-sensor series of trajectories.

Brewster, L.↗

NASA NTRS2008

Multi-Sensor Testing for Automated Rendezvous and Docking Sensor Testing at the Flight Robotics Lab

The Exploration Systems Architecture defines missions that require rendezvous, proximity operations, and docking (RPOD) of two spacecraft both in Low Earth Orbit (LEO) and in Low Lunar Orbit (LLO). Uncrewed spacecraft must perform automated and/or autonomous rendezvous, proximity operations and docking operations (commonly known as AR&D). The crewed missions may also perform rendezvous and docking operations and may require different levels of automation and/or autonomy, and must provide the crew with relative navigation information for manual piloting. The capabilities of the RPOD sensors are critical to the success ofthe Exploration Program. NASA has the responsibility to determine whether the Crew Exploration Vehicle (CEV) contractor-proposed relative navigation sensor suite will meet the requirements. The relatively low technology readiness level of AR&D relative navigation sensors has been carried as one of the CEV Project's top risks. The AR&D Sensor Technology Project seeks to reduce the risk by the testing and analysis of selected relative navigation sensor technologies through hardware-in-the-Ioop testing and simulation. These activities will provide the CEV Project information to assess the relative navigation sensors maturity as well as demonstrate test methods and capabilities. The first year of this project focused on a series of "pathfinder" testing tasks to develop the test plans, test facility requirements, trajectories, math model architecture, simulation platform, and processes that will be used to evaluate the Contractor-proposed sensors. Four candidate sensors were used in the first phase of the testing. The second phase of testing used four sensors simultaneously: two Marshall Space Flight Center (MSFC) Advanced Video Guidance Sensors (AVGS), a laser-based video sensor that uses retroreflectors attached to the target vehicle, and two commercial laser range finders. The multi-sensor testing was conducted at MSFC's Flight Robotics Laboratory (FRL) using the FRL's 6-DOF gantry system, called the Dynamic Overhead Target System (DOTS). The target vehicle for "docking" in the laboratory was a mockup that was representative of the proposed CEV docking system, with added retroreflectors for the AVGS.' The multi-sensor test configuration used 35 open-loop test trajectories covering three major objectives: (l) sensor characterization trajectories designed to test a wide range of performance parameters; (2) CEV-specific trajectories designed to test performance during CEV-like approach and departure profiles; and (3) sensor characterization tests designed for evaluating sensor performance under more extreme conditions as might be induced during a spacecraft failure or during contingency situations. This paper describes the test development, test facility, test preparations, test execution, and test results of the multisensor series oftrajectories

Brewster, Linda L.↗

NASA NTRS1991

Applications of fuzzy logic to control and decision making

Long range space missions will require high operational efficiency as well as autonomy to enhance the effectivity of performance. Fuzzy logic technology has been shown to be powerful and robust in interpreting imprecise measurements and generating appropriate control decisions for many space operations. Several applications are underway, studying the fuzzy logic approach to solving control and decision making problems. Fuzzy logic algorithms for relative motion and attitude control have been developed and demonstrated for proximity operations. Based on this experience, motion control algorithms that include obstacle avoidance were developed for a Mars Rover prototype for maneuvering during the sample collection process. A concept of an intelligent sensor system that can identify objects and track them continuously and learn from its environment is under development to support traffic management and proximity operations around the Space Station Freedom. For safe and reliable operation of Lunar/Mars based crew quarters, high speed controllers with ability to combine imprecise measurements from several sensors is required. A fuzzy logic approach that uses high speed fuzzy hardware chips is being studied.

Lea, Robert N.↗

NASA NTRS2011

Development of Tools and Techniques for Processing STORRM Flight Data

While at JSC for the summer of 2011, I was assigned to work on the sensor test for Orion relative-navigation risk mitigation (STORRM) development test objective (DTO). The STORRM DTO was flown on-board Endeavor during STS-134. The objective of the STORRM DTO is to test the visual navigation system (VNS), which will be used as the primary relative navigation sensor for the Orion spacecraft. The VNS is a flash lidar system intended to provide both line of sight and range information during rendezvous and proximity operations. The STORRM DTO also serves as a testbed for the high-resolution docking camera. This docking camera will be used to provide piloting cues for the crew during proximity operations. These instruments were mounted next to the trajectory control sensor (TCS) in Endeavour s payload bay. My principle objective for the summer was to generate a best estimated trajectory (BET) for Endeavor using the flight data collected by the VNS during rendezvous and the unprecedented re-rendezvous with the ISS. I processed the raw images from the VNS to produce range and bearing measurements. I then aggregated these measurements and extracted the measurements corresponding to individual reflectors. I combined the information contained in these measurements with data from the Endeavour's inertial sensors using Kalman smoothing techniques to ultimately produce a BET. This work culminated with a final presentation of the result to division management. Development of this tool required that traditional linear smoothing techniques be modified in a novel fashion to permit for the inclusion of non-linear measurements. This internship has greatly helped me further my career by providing exposure to real engineering projects. I also have benefited immensely from the mentorship of the engineers working on these projects. Many of the lessons I learned and experiences I had are of particular value because then can only be found in a place like JSC.

Robinson, Shane↗

NASA NTRS2014

RS-34 Phoenix In-Space Propulsion System Applied to Active Debris Removal Mission

In-space propulsion is a high percentage of the cost when considering Active Debris Removal mission. For this reason it is desired to research if existing designs with slight modification would meet mission requirements to aid in reducing cost of the overall mission. Such a system capable of rendezvous, close proximity operations, and de-orbit of Envisat class resident space objects has been identified in the existing RS-34 Phoenix. RS-34 propulsion system is a remaining asset from the de-commissioned United States Air Force Peacekeeper program; specifically the pressure-fed storable bi-propellant Stage IV Post Boost Propulsion System. The National Aeronautics and Space Administration (NASA) Marshall Space Flight Center (MSFC) gained experience with the RS-34 propulsion system on the successful Ares I-X flight test program flown in the Ares I-X Roll control system (RoCS). The heritage hardware proved extremely robust and reliable and sparked interest for further utilization on other potential in-space applications. Subsequently, MSFC has obtained permission from the USAF to obtain all the remaining RS-34 stages for re-use opportunities. The MSFC Advanced Concepts Office (ACO) was commissioned to lead a study for evaluation of the Rocketdyne produced RS-34 propulsion system as it applies to an active debris removal design reference mission for resident space object targets including Envisat. Originally designed, the RS-34 Phoenix provided in-space six-degrees-of freedom operational maneuvering to deploy payloads at multiple orbital locations. The RS-34 Concept Study lead by sought to further understand application for a similar orbital debris design reference mission to provide propulsive capability for rendezvous, close proximity operations to support the capture phase of the mission, and deorbit of single or multiple large class resident space objects. Multiple configurations varying the degree of modification were identified to trade for dry mass optimization and propellant load. The results of the RS-34 Phoenix Concept Study show that the system is technically sufficient to successfully support all of the missions to rendezvous, capture, and de-orbit targets including Envisat and Hubble Space Telescope. The results and benefits of the RS-34 Orbital Debris Application Concept Study are presented in this paper.

Esther, Elizabeth A.↗

NASA NTRS2016

A Collision Avoidance Strategy for a Potential Natural Satellite around the Asteroid Bennu for the OSIRIS-REx Mission

The cadence of proximity operations for the OSIRIS-REx mission may have an extra induced challenge given the potential of the detection of a natural satellite orbiting the asteroid Bennu. Current ground radar observations for object detection orbiting Bennu show no found objects within bounds of specific size and rotation rates. If a natural satellite is detected during approach, a different proximity operation cadence will need to be implemented as well as a collision avoidance strategy for mission success. A collision avoidance strategy will be analyzed using the Wald Sequential Probability Ratio Test.

satellite↗

NASA NTRS2016

A Collision Avoidance Strategy for a Potential Natural Satellite Around the Asteroid Bennu for the OSIRIS-REx Mission

The cadence of proximity operations for the OSIRIS-REx mission may have an extra induced challenge given the potential of the detection of a natural satellite orbiting the asteroid Bennu. Current ground radar observations for object detection orbiting Bennu show no found objects within bounds of specific size and rotation rates. If a natural satellite is detected during approach, a different proximity operation cadence will need to be implemented as well as a collision avoidance strategy for mission success. A collision avoidance strategy will be analyzed using the Wald Sequential Probability Ratio Test.

bennu↗