CARA Large Constellation Status
Explore the source record for details and available documents.
SEARCH · Search NASA
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.
Explore the source record for details and available documents.
The growing number of large-scale constellations and the improvements made in the tracking and detection of resident space objects have contributed to the increase of satellite conjunction events. As a result of the increase of objects in Earth orbit, the timeline for risk analysis computations for satellite collision avoidance is more urgent when conjunctions occur. It is imperative NASA maintains a space environment safety functionality for the agency that allows CARA remote access to the ground system while maintaining redundancy. CARA’s On-premises (On-prem) ground system would no longer be able to meet these access and redundancy requirements, hence the investigation and eventual implementation of a Cloud-based ground station infrastructure as a viable solution. This paper will provide an overview of the principal parts of the Conjunction Assessment (CA) risk analysis process used at CARA, summarize the key drivers towards the Cloud solution, and share key lessons learned that are significant for any operational entity considering a cloud solution for real-time satellite operations to ensure a sustainable space traffic environment for all.
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.
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.
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.
Satellite constellations that employ on-spacecraft flight dynamics and conjunction assessment (CA) approaches face particular challenges. First, they must arrange to obtain and upload to the constellation satellite close approach information, such as Conjunction Data Messages, so that their on-board systems will have the data they need to make informed CA decisions. Second, given current latencies in obtaining CA screening information, such systems often cannot obtain dedicated screenings of their proposed maneuvers before they are executed. Third, they usually cannot engage in real time with owner/operators (O/Os) with whom they may come into conjunction, relying instead on pre-arranged courses of action that may or may not fit a given situation well. Despite these difficulties, it is nonetheless possible, as operators such as SpaceX have demonstrated, to operate safely using on-board CA calculations, in the presence of a largely collaborative operating environment. The situation breaks down, however, when two constellations that operate with such a paradigm are placed in the same orbital region and will experience conjunctions with each other. Each may have a vague idea of where the other’s satellites are, or perhaps even a somewhat precise idea if they exchange O/O ephemerides, but neither will know the other’s more immediate maneuver intentions, especially for situations in which they are in a high-risk conjunction with each other and a mitigation maneuver is required. As there is no formalized way for these automated systems to ascertain each other’s intentions for this type of conjunction, it is quite possible that each spacecraft may choose a maneuver that results in the two objects’ colliding. An opportunity to develop a solution to this problem was presented by the NASA “Starling” project, a small experimental constellation developed to demonstrate autonomous satellite control and constellation reconfiguration and for which a launch was obtained that, serendipitously, will place this constellation close to the SpaceX Starlink constellation. Because the NASA constellation is experimental, an extended mission part of the mission has been negotiated to implement and test mechanisms for resolving the problem of co-located constellations with on-board flight dynamics control. For the last eighteen months, a consortium among NASA Ames (the Starling satellite providers), NASA CARA (the Agency organization responsible for conjunction assessment), Space X, and the Department of Commerce (in observer status) has met regularly to assemble a concept of operations for a robust solution to this problem and has developed a prototype ground node that will serve as a needed CA screening and information dispensary. The approach and methods, as well as the active employment of the developed ground node, will be tested both in simulation before actual use and then in actual spacecraft operations, which are anticipated to begin in January 2024. This paper will describe the co-located autonomously-controlled constellation problem and the developed solution in detail, outlining what ground node (i.e., government) infrastructure and features are required, what particular capabilities are needed by the constellations themselves in order to make use of this deconfliction paradigm, and the migration path forward to allow such a capability set to be incorporated by the Department of Commerce’s space traffic coordination system.