CARA Presentation for Fall 2021 Mission Operations Working Group (MOWG)
Explore the source record for details and available documents.
Megan Rene Johnson↗
SEARCH · Engineering Papers
Results for “CARA”
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.
SSA Operators' Workshop NASA CARA Best Practices: Potentially Active Secondary Payloads
Explore the source record for details and available documents.
R A Baker↗
A Compendium for Artificial Intelligence and Machine Learning for Satellite Collision Avoidance at NASA Conjunction Assessment Risk Analysis (CARA)
Explore the source record for details and available documents.
Collision Avoidance↗
Decision Aid for Conjunction Risk Mitigation by Differential Drag
In the previous five years, the rate of conjunctions that the NASA Conjunction Assessment Risk Analysis (CARA) team processed and analyzed has more than tripled. (NASA CARA, 2024) New missions in the early development phases are now required to plan for dealing with conjunctions under the present space environment, and also projecting forward into a future likely with even further increased utilization of the space environment. Some missions are investigating the possibility of using differential drag to remediate conjunctions without expending limited fuel or for missions without propulsive capabilities. The NASA CARA team studied the historical record of conjunctions to evaluate the circumstances under which differential drag may be successfully applied and have developed a series of tables to use as a decision aid for missions considering differential drag. Currently, if a CARA-protected mission with maneuvering capabilities is predicted to have a conjunction with probability of collision (Pc) greater than 7E-5 (the default value of the ‘yellow threshold’, which may have some other value agreed by CARA and the mission during the Orbital Collison Avoidance Planning (OCAP) process), CARA will use its Maneuver Trade Space (MTS) tool to evaluate and recommend options for the timing and magnitude of a risk mitigation maneuver (RMM), based on the mission’s capabilities. If the conjunction’s Pc is greater than 1E-4, the ‘red threshold’, then an RMM must be executed per NASA Procedural Requirements (NPR) 8079.1 (NASA, 2023), although missions may execute an RMM even if the Pc is lower. The magnitude of the maneuver is typically a few cm/s, and CARA estimates how many will be required for the mission’s nominal lifetime – typically a few per year – during the OCAP process, to inform the mission’s delta-V requirement. For traditional satellites, this is usually smaller than other requirements for orbit insertion, maintenance, and disposal, but for CubeSats or other small satellite missions, a propulsion system may not provide much more than a few cm/s of delta-V or may not fit at all within the available budget of money, time, size, weight, and/or power (SWaP). Conversely, CubeSats often have deployable solar panels, which offer the capacity to have much higher areas facing some directions than others. Such a mission can instead use ‘differential drag’ to remediate a conjunction -- in other words, change its drag area (usually increasing) to deviate from the predicted collision course. This is how Planet’s Dove spacecraft maintain their formations and remediate conjunction risks without having on-board propulsion (Foster, et al., 2017) (Griffith, et al., 2021). CARA has been developing improvements to MTS to support differential-drag for NASA's missions -- where it is effective. CARA records all conjunctions of their protected payloads, with historical records starting in 2005 (with significant conjunction events starting to occur on or after 2013). From this record, approximately 7,300 had a Pc greater than 1E-4 at 3 days prior to the time of closest approach, the time analyzed for differential drag efficacy. Of those, approximately 4,300 had fully-defined covariance matrices stored for both the primary and secondary objects; this set of conjunctions is the basis for the analysis of this work. CARA’s MTS tool was used to propagate the primary satellite forward from that decision point with varying degrees of increase to ballistic coefficient (BC). Because these conjunctions came from multiple missions, the nondimensional ‘delta-BC’ factor was used to quantify and normalize the increase in ballistic coefficient, defined as follows: Delta-BC = BC_new / BC_old - 1 Positive delta-BC factors represent an increase in drag compared to the nominal attitude, while negative delta-BC factors (to a minimum of -1) represent a decrease in drag. At the conclusion of the differential-drag ‘maneuver’, the Pc was recalculated to evaluate whether or not the conjunction was mitigated (Pc < 3E-6). These results were then binned and sorted along several axes, including altitude, amount of delta-BC, and (pre-maneuver) rate of energy dissipation (EDR), to identify underlying patterns. The altitude plot is shown in Figure 1. To validate this analysis, we consulted the record of a NASA mission which uses differential drag to maintain its orbit and remediate conjunction risk. CARA’s empirical record of the mission’s orbit history suggests it achieves a delta-BC of 2.2. Of the twenty-one RMM plans that were submitted by this mission, eighteen were matched with conjunctions in the historical record; of those, twelve were successfully remediated (final measured Pc < 3E-6), and six were not. This is consistent with the expected efficacy for missions orbiting at that altitude. We are presently simulating this mission’s RMMs with MTS; this work is ongoing, but so far, the MTS results are qualitatively in agreement with the empirical results -- correctly predicting that a maneuver would or would not remediate a conjunction, if not exactly matching the final post-remediation Pc value. We found that differential drag was most successful for satellites with perigees below 560 km, and which could adopt an average delta-BC of 2 or greater (that is, increasing their ballistic coefficient by a factor of 3). However, this is a difficult threshold for a mission to clear; very few spacecraft are capable of adopting a high-drag configuration for 72 hours continuously. Planet’s Dove spacecraft use differential drag to remediate conjunctions (Griffith, et al., 2021), and they have a maximum delta-BC factor of 9, but in practice (with mission and charging constraints) they achieve a time-averaged delta-BC that is closer to 2 (Foster, et al., 2017). A mission’s differential drag utility strongly depends on the operational constraints that has the capacity to limit the time-averaged delta-BC. A mission with a high maximum delta-BC of 5 or more can have an effective delta-BC of less than 1 due to operational constraints such as instrument and solar panel pointing, especially if this constraint results in holding an intermediate drag value for most of its orbit. CARA has developed tables that can be used as decision aids to advise missions-in-development about the best way to utilize their differential drag capabilities. For missions below 560 km with the operational flexibility to devote multiple days to holding a high-drag configuration (or a sufficiently high drag ratio to compensate for limitations on that time), they are -- more likely than not -- able to successfully remediate high-risk conjunctions. Conversely, missions that do not meet these exacting criteria -- most missions -- can instead be advised to use on-board propulsion systems to perform RMMs, or to turn their minimum-area face towards the approach vector, thereby reducing Pc at the moment of conjunction due to the decreased Hard-Body Radius (HBR), that is a strongly correlated variable in the Pc calculations. (NASA, 2023)
conjunction assessment↗
Decision Aid for Conjunction Risk Mitigation by Differential Drag
In the previous five years, the rate of conjunctions that the NASA Conjunction Assessment Risk Analysis (CARA) team processed and analyzed has more than tripled. (NASA CARA, 2024) New missions in the early development phases are now required to plan for dealing with conjunctions under the present space environment, and also projecting forward into a future likely with even further increased utilization of the space environment. Some missions are investigating the possibility of using differential drag to remediate conjunctions without expending limited fuel or for missions without propulsive capabilities. The NASA CARA team studied the historical record of conjunctions to evaluate the circumstances under which differential drag may be successfully applied and have developed a series of tables to use as a decision aid for missions considering differential drag. CARA records all conjunctions of their protected payloads, with historical records starting in 2005 (with significant conjunction events starting to occur on or after 2013). From this record, approximately 7,300 had a probability of collision (Pc) greater than 1 in 10,000, the nominal requirement for a risk mitigation maneuver (RMM) to be made per NASA Procedural Requirements (NPR) 8079.1 (NASA, 2023), at 3 days prior to the time of closest approach, the time analyzed for differential drag efficacy. CARA’s maneuver trade space tool (MTS) was used to prop-agate the primary satellite forward from that decision point with varying degrees of increase to ballistic coefficient (BC), and then recalculate the Pc to evaluate whether or not the conjunction was mitigated (Pc < 3E-6). These results were then binned and sorted along several axes, including altitude, amount of delta-BC, and (pre-maneuver) rate of energy dissipation, to identify underlying patterns. The altitude plot is shown in Figure 1. We found that differential drag was most successful for satellites with perigees below 560 km, and which could adopt an average delta-BC of 2 or greater (that is, increasing their ballistic coefficient by a factor of 3). However, this is a difficult threshold for a mission to clear; very few spacecraft are capable of adopting a high-drag configuration for 72 hours continuously. Planet’s Dove spacecraft use differential drag to remediate conjunctions (Griffith, et al., 2021), and they have a maximum delta-BC factor of 9, but in practice (with mission and charging constraints) they achieve a time-averaged delta-BC that is closer to 2 (Foster, et al., 2017). In contrast, a NASA mission in development reached out to CARA to evaluate the utility of differential drag to remediate potential conjunctions for a spacecraft which is capable of a similar high delta-BC, but with operational constraints that limit their time-averaged delta-BC to less than 1. CARA has developed tables that can be used as decision aids to advise missions-in-development about the best way to utilize their differential drag capabilities. For missions below 560 km with the operational flexibility to devote multiple days to holding a high-drag configuration (or a sufficiently high drag ratio to compensate for limitations on that time), they are able to successfully remediate high-risk conjunctions. Conversely, missions that do not meet these ex-acting criteria – most missions – can instead be advised to use on-board propulsion systems to perform RMMs or to turn their minimum-area face towards the approach vector, thereby reducing Pc at the moment of conjunction. (NASA, 2023)
risk mitigation↗
Summary of Aqua, Aura, and Terra High Interest Events
Single-obs tracking Sparsely tracked objects are an unfortunate reality of CARA operations Terra vs. 32081: new track with bad data was included in OD solution for secondary object and risk became high CARA and JSpOC discussed tracking and OSAs threw out the bad data. Event no longer presented high risk based on new OD Improvement: CARA now sends JSpOC a flag indicating when a single obs is included, so OSAs can evaluate if manual update to OD is required. Missing ASW OCMsAura vs. 87178, TCA: 317 at 08:04 UTC. Post-maneuver risk (conjunction was identified in OO results)CARA confirmed with JSpOC that ASW OCMs should have been received in addition to OO OCMsJSpOC corrected the manual error in their script that prevented the data from being delivered to CARAJSpOC QAd their other scripts to ensure this error did not exist in other places.
Conjunction↗
Use of the NetBeans Platform for NASA Robotic Conjunction Assessment Risk Analysis
The latest Java and JavaFX technologies are very attractive software platforms for customers involved in space mission operations such as those of NASA and the US Air Force. For NASA Robotic Conjunction Assessment Risk Analysis (CARA), the NetBeans platform provided an environment in which scalable software solutions could be developed quickly and efficiently. Both Java 8 and the NetBeans platform are in the process of simplifying CARA development in secure environments by providing a significant amount of capability in a single accredited package, where accreditation alone can account for 6-8 months for each library or software application. Capabilities either in use or being investigated by CARA include: 2D and 3D displays with JavaFX, parallelization with the new Streams API, and scalability through the NetBeans plugin architecture.
assessment↗
NASA Conjunction Assessment Organizational Approach and the Associated Determination of Screening Volume Sizes
NASA is committed to safety of flight for all of its operational assets Performed by CARA at NASA GSFC for robotic satellites Focus of this briefing Performed by TOPO at NASA JSC for human spaceflight he Conjunction Assessment Risk Analysis (CARA) was stood up to offer this service to all NASA robotic satellites Currently provides service to 70 operational satellites NASA unmanned operational assets Other USG assets (USGS, USAF, NOAA) International partner assets Conjunction Assessment (CA) is the process of identifying close approaches between two orbiting objects; sometimes called conjunction screening The Joint Space Operations Center (JSpOC) a USAF unit at Vandenberg AFB, maintains the high accuracy catalog of space objects, screens CARA-supported assets against the catalog, performs OD tasking, and generates close approach data.
Conjunction↗
Predicting Space Weather Effects on Close Approach Events
The NASA Robotic Conjunction Assessment Risk Analysis (CARA) team sends ephemeris data to the Joint Space Operations Center (JSpOC) for conjunction assessment screening against the JSpOC high accuracy catalog and then assesses risk posed to protected assets from predicted close approaches. Since most spacecraft supported by the CARA team are located in LEO orbits, atmospheric drag is the primary source of state estimate uncertainty. Drag magnitude and uncertainty is directly governed by atmospheric density and thus space weather. At present the actual effect of space weather on atmospheric density cannot be accurately predicted because most atmospheric density models are empirical in nature, which do not perform well in prediction. The Jacchia-Bowman-HASDM 2009 (JBH09) atmospheric density model used at the JSpOC employs a solar storm active compensation feature that predicts storm sizes and arrival times and thus the resulting neutral density alterations. With this feature, estimation errors can occur in either direction (i.e., over- or under-estimation of density and thus drag). Although the exact effect of a solar storm on atmospheric drag cannot be determined, one can explore the effects of JBH09 model error on conjuncting objects' trajectories to determine if a conjunction is likely to become riskier, less risky, or pass unaffected. The CARA team has constructed a Space Weather Trade-Space tool that systematically alters the drag situation for the conjuncting objects and recalculates the probability of collision for each case to determine the range of possible effects on the collision risk. In addition to a review of the theory and the particulars of the tool, the different types of observed output will be explained, along with statistics of their frequency.
Space Weather↗
Nasa Conjunction Assessment Risk Analysis Updated Requirements Architecture
The NASA Conjunction Assessment Risk Analysis (CARA) program has been performing routine on-orbit satellite conjunction risk analysis for unmanned NASA spacecraft since 2005, and has developed a robust operations procedure and set of recommended best practices for operational conjunction assessment. However, a number of recent developments in Space Situational Awareness and commercial space operations conduct, such as the immanent deployment of much more sensitive space sensing systems and the launching of much larger satellite constellations, have begun to challenge these standard collision risk parameters and calculations. In response CARA has pursued a multi-year evaluation initiative to re-examine risk assessment algorithms and techniques, to develop needed improvements, and to assemble analysis-based operational requirements. This paper gives an overview of the principal parts of the Conjunction Assessment (CA) risk assessment process used at CARA, outlines the technical challenges that each part presents, surveys the possible solutions, and then indicates which particular solution is being recommended for NASA.
Newman, Lauri K.↗
Decision Aid for Conjunction Risk Mitigation by Differential Drag
The NASA Conjunction Assessment Risk Analysis (CARA) team has conducted are view of the historical record of high-risk conjunctions involving CARA-protected missions and evaluated whether (and how much) differential drag can provide effective mitigation. From this analysis, CARA has identified a rule of thumb: missions with perigees below 560 km capable of tripling their drag area for 72 hours(or a larger scale factor for a lesser amount of time) can reliably use differential drag to remediate high-risk events.
mission design↗
Assessment, Planning, and Execution Considerations for Conjunction Risk Assessment and Mitigation Operations
An operational Conjunction Assessment Risk Analysis (CARA) concept is the real-time process of assessing risk posed by close approaches and reacting to those risks if necessary. The most effective way to completely mitigate conjunction risk is to perform an avoidance maneuver. The NASA Goddard Space Flight Center has implemented a routine CARA process since 2005. Over this period, considerable experience has been gained and many lessons have been learned. This paper identifies and presents these experiences as general concepts in the description of the Conjunction Assessment, Flight Dynamics, and Flight Operations methodologies and processes. These general concepts will be tied together and will be exemplified through a case study of an actual high risk conjunction event for the Aura mission.
Frigm, Ryan C.↗
Evolution and Implementation of the NASA Robotic Conjunction Assessment Risk Analysis Concept of Operations
Reacting to potential on-orbit collision risk in an operational environment requires timely and accurate communication and exchange of data, information, and analysis to ensure informed decision-making for safety of flight and responsible use of the shared space environment. To accomplish this mission, it is imperative that all stakeholders effectively manage resources: devoting necessary and potentially intensive resource commitment to responding to high-risk conjunction events and preventing unnecessary expenditure of resources on events of low collision risk. After 10 years of operational experience, the NASA Robotic Conjunction Assessment Risk Analysis (CARA) is modifying its Concept of Operations (CONOPS) to ensure this alignment of collision risk and resource management. This evolution manifests itself in the approach to characterizing, reporting, and refining of collision risk. Implementation of this updated CONOPS is expected to have a demonstrated improvement on the efficacy of JSpOC, CARA, and owner/operator resources.
operations↗
S-band Fence Study Phase 1: Estimating the Increased Level of Screening Volume Incursions
Motivation: CARA assesses collision risk for a set of high-value satellites. Deploying the S-band Fence (SBF) radar system will significantly increase the number of conjunctions to process, possibly overloading the current CARA system.Phase 1 study objective: Estimate changes in screening volume incursion rates caused by the SBF deploymentPhase 2 study objective: Estimate associated changes in serious conjunction rates (e.g., Pc > 10-4) Phase 3 study objective: Develop methods for filtering and prioritizing the increased tasking, as requiredAll to be discussed today are Phase I results
conjunction assessment operations↗
NASA CA Operations Devolution: Status Update
What is Devolution? Devolution is a spreading of CA (Conjunction Assessment) operations responsibilities to mission FOTs (Flight Operations Teams): Permits efficiencies in handling the increased workload caused by Space Fence and large constellations; Missions given more flexibility in choosing specific approach to CA requirements that resonates best with their particular needs; CARA (Conjunction Assessment Risk Analysis) retains Agency oversight through an established NASA Standard - will establish requirements for devolved CA preparations, processing, and operations conduct. Devolution is a PROPOSED paradigm under consideration by SMD (Space Missions Directorate): Number of activities required before Agency-level decision can be rendered; Agency requirements established via approved CA Standard; Operational experience testimony from two separate pilot programs; After these activities complete, decision will be made whether devolution is a feasible option for missions; CARA is recommending devolution to exist as an option for missions.
conjunction↗
Processing Space Fence Radar Cross-Section Data to produce size and mass estimates
With the addition of the Space Fence (SFK) radar to the Space Surveillance Network (SSN), the NASA Conjunction Assessment Risk Analysis (CARA) team now has access to radar cross-section (RCS) measurements for many Earth orbiting satellites. The CARA team has developed a process to estimate satellite sizes and masses from the SFK RCS measurement data. This study describes the processes used to filter the RCS data, defines the algorithms used to esti-mate satellite sizes and masses, and presents comparisons of estimated values against known satellite sizes and masses.
Radar Cross-Section↗
Processing Space Fence RCS Data for Hard-Body Radius and Mass Estimation
With the addition of the Space Fence (SFK) radar to the Space Surveillance Network (SSN), the NASA Conjunction Assessment Risk Analysis (CARA) team now has access to radar cross-section (RCS) measurements for many Earth orbiting satellites. The CARA team has developed a process to estimate satellite sizes and masses from the SFK RCS measurement data. This study describes the processes used to filter the RCS data, defines the algorithms used to estimate satellite sizes and masses, and presents comparisons of estimated values against known nanosat sizes and masses.
Luis Baars↗
OSIRIS-REx Screening Experience & Lessons Learned
On September 24, 2023, the NASA OSIRIS-REx spacecraft returned a sample of asteroid Bennu, approaching on a hyperbolic impact trajectory relative to Earth. At approximately 108,000 km altitude and four hours prior to hitting the top of the atmosphere, the Sample Return Capsule (SRC) separated from the spacecraft bus, targeting the Utah Test and Training Range. Twenty minutes later, the bus performed a large divert maneuver to fly by at a perigee altitude of ~780 km. Given the immense scientific value of the sample, substantial efforts were undertaken by NASA CARA and the OSIRIS-REx mission to ensure safe passage of the objects from GEO through LEO. This presentation provides an overview of collision avoidance maneuver (CAM) options, results of screenings, coordination with DoD for contingency observations, and lessons learned for screening future Earth flyby and entry trajectories. Two particular challenges included screening two objects using a much larger than normal 250 km spherical monitor volume and decision planning for a single CAM while the SRC was still attached that would alter both trajectories. The larger, non-standard screening volume resulted in custom procedures that CARA personnel had to run manually for each screening, and the initial long propagation times while the objects were more than a week out required significant computing resources. With a single CAM opportunity at 13 hours out, the decision to execute a maneuver had to consider the risk to both objects, where one could imagine a situation where the maneuver would clear a high-risk conjunction for one object and introduce one for the other – begging the question of relative risk posture between the SRC and bus. These among other unique aspects of Earth flyby and entry missions led to novel planning and implementation procedures to support future missions of this type.
Dolan E. Highsmith↗