Search NASA⌕ Search

SEARCH · Search NASA

Results for “space traffic management”

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 19 records

Exploring the Effectiveness of Maneuvering Guidelines for Space Traffic Management

The number of objects in space has been increasing rapidly, and the risk of collision has grown as well. Many spacecraft operators are now receiving multiple collision warnings a day. Despite this, systems to manage space traffic have been limited: there are no broadly agreed upon guidelines or rules governing the response to predicted potential collisions. Instead, spacecraft operators generally determine whether, when, and how to respond to these warnings on a manual and ad hoc basis. Coordination between operators, if it occurs, often requires repeated communication and negotiation. Some space actors have suggested that the space community should develop right of way rules, similar to those in the ground, sea, and air domains, to guide collision response decisions. However, it is unclear whether such rules would be effective, and it’s unknown whether such rules would have an equitable impact across various spacecraft operators. To address these issues, we developed the Virtual Environment for Space Traffic Analysis (VESTA), a software tool that was used to simulate the space environment with a recent catalog of objects obtained from the U.S. Space-Track.org system. We implemented multiple potential right of way rules within this model. The analysis confirmed that the choice of right of way rule makes a meaningful difference in terms of both efficiency and distributional effects in terms of collision avoidance maneuvers. For example, our analysis shows that rules in which the less massive satellite is required to maneuver results in a more equitable distribution of maneuver responsibility among space actors and also requires less fuel mass, compared to a rule in which the more massive satellite maneuvers.

space traffic management↗

Space Traffic Management with a NASA UAS Traffic Management (UTM) Inspired Architecture

Space is becoming increasingly congested as the number of on-orbit satellites and debris objects continues to grow. Space traffic management (STM) is critical for ensuring that the expanding orbital population operates safely and efficiently, avoiding collisions and radio-frequency interference while still facilitating widespread space operations. Recent events such as the FCC approval of SpaceX’s ~12,000 satellite constellation, the signing of Space Policy Directive 3 (which moves Space Situational Awareness responsibilities away from the Department of Defense and to a civil agency), and the growth in rideshare and small launch vehicles illustrate the rapidly changing nature of this domain. This paper will describe the concept of operations (ConOps) for a civilian STM research initiative, which has been developed from previous NASA work to enable safe operation of small unmanned aircraft systems. The STM ConOps proposes an architecture to enable efficient data sharing and coordination between participants to facilitate safe spaceflight operations. It is designed to utilize and promote the emerging field of commercial STM services, as a complement to existing government-provided STM services. The concept envisions a phased evolution that would gradually integrate additional capabilities, proposing a first phase architecture and tentative plans for a broader system. Work towards developing an STM research and prototyping platform is also discussed.

UTM↗

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↗

Exploring the Impact of Compliance With Maneuvering Guidelines for Space Traffic Management

If the current estimate of proposed large constellations is realized, the near-Earth space environment will see more than 50,000 new satellites added to the catalog of resident space objects (RSOs) in the coming decade. This is an order of magnitude increase from the current population and poses new policy challenges as global operators seek to leverage the benefits these new satellite systems provide while also ensuring a sustainable approach to collision avoidance. Various guidelines have been proposed to date to support this effort, including the development of right of way rules to guide how a collision avoidance maneuver should be performed, and how the maneuver burden should be shared between the two satellites involved. However, it is very difficult to evaluate and compare proposed guidelines due to the complex nature of space traffic and the rapidly changing space environment. This study seeks to address this issue by utilizing the Virtual Environment for Space Traffic Analysis (VESTA), a high-fidelity simulation tool that has been developed at Georgia Tech over the past few years with the explicit purpose of evaluating the future of space traffic environment. Using this tool, a sensitivity study is performed that incorporates a likely set of future large constellations and provides metrics on the impact that a select set of proposed maneuvering guidelines would have on operators given realistic variations in spacecraft capabilities (e.g. maneuverability and propulsion capabilities), and other factors (owner-country, public vs. private, etc.). Specifically, this study compares three potential right of way rules: 1) a rule based on maneuverability proposed by the Space Safety Coalition, 2) a rule based on the geometry of the spacecraft rendezvous, and 3) a rule that equally distributes the maneuver burden between two operators, The results highlight general observations on the effectiveness and limitations of each of the proposed maneuvering guidelines. In addition to the choice of right of way rule, success of space traffic management will be significantly impacted by compliance – which operators, or how many operators, comply with the space traffic rules. The findings of this analysis have important implications for future methods that could be pursued to put in place right of way rules. For example, non-binding right of way rules may have variable levels of compliance that differ across actors. The impact of compliance by just one nation, or non-compliance by just one nation, help to demonstrate the impact of ensuring all major space actors coordinate on this effort. Overall, this analysis provides insight into the relative gains in safety (decrease in collision risk) that would likely result from more politically intense efforts to increase the number of countries implementing space traffic management rules.

conjunction assessment↗

System Autonomy for Space Traffic Management

This paper proposes an initial architecture for a Space Traffic Management (STM) system, based on openApplication Programming Interfaces (APIs) and drawing on previous work by the NASA Ames Research Center (ARC) to develop an architecture for low-altitude Unmanned Aerial System Traffic Management (UTM). The authors explore how autonomy could be used to enhance an STM system, and how constraints inherent in STM complicate and challenge certain applications of autonomy. We conceptually explore how autonomy could be used within an STM architecture, with multiple non-authoritative catalogs of resident space objects, and to determine which oftwo conjuncting spacecraft moves. NASA ARC is developing a software research environment for STM, along with a physical laboratory and visualization space. We invite STM stakeholders to collaborate in our infrastructure, to help inform the design of the proposed STM architecture, and to participate in the refinement and validation of its concept of operations using the software research platform.

space situational awareness↗

Validation of A Simulation Environment for Future Space Traffic Management

This study presents initial results of a newly developed simulation environment intendedto explore and assess future Space Traffic Management (STM) scenarios. The number ofnew Resident Space Objects (RSOs) in near-Earth orbit is expected to increase significantlywith the expected future deployment of a number of large constellations. These futurescenarios involve the addition of many tens of thousands of new RSOs, making the analysisinto their impact on collision risk extend beyond what traditional data-mining of present-dayconjunction data can reliably predict. To address this, a robust simulation environment wasdeveloped that implements a full force-model for orbit propagation, and computes continuousall-on-all conjunction statistics for arbitrarily large catalog sizes and simulation timeframes.Collision avoidance and station-keeping maneuvers can be optionally implemented based onconfigurable user inputs including physical characteristics and spacecraft meta-data (e.g.,commercial/government, owner country, etc.). Constellation build-out and de-orbit scenarioswere also implemented and modeled based on real-data analysis. Validation of the simulationresults was a critical component of the simulation development, and was done using the currentcatalog with comparisons against both public and internal NASA data-sets. The comparisonsdemonstrate that, with the appropriate settings, representative levels of conjunction ratesand probabilities can be obtained, providing confidence that the simulation tool can generatemeaningful outcomes for test scenarios. As an initial demonstration of the tool’s capabilities,year-long simulations with station-keeping were conducted to examine conjunction historiesusing both the current object catalog (5800 active satellites) and a hypothetical 60,000 objectscenario involving five potential large constellations. Output metrics include the number ofconjunction events, estimates of collision consequence (fragmentation), delta-V maneuver costs,and the probability of at least one collision occurring. The results highlight the potential thatthe simulation tool has for incorporating and running performance comparisons between, e.g.,various sets of maneuver guidelines, industry norms, and definitions of risk, with the overallobjective of providing actionable data to STM policy makers. The presentation will providean overview of the simulation development and validation efforts, as well as a discussion ofobservations gathered from the initial simulations performed.

conjunction assessment↗

An Investigation Into Transecting Satellites in Future Space Traffic Management Scenarios

The number of satellites expected to populate the near-Earth space environment is set to dramatically increase in the coming decade as new large constellations are approved and deployed. Current strategies for deploying new batches of these satellites often involve launching into an initial orbit, and then performing apogee raising maneuvers to reach a target altitude. Similarly, end-of-life planning for these constellation satellites can consist of de-orbit burns that lower perigee to permit disposal via re-entry. Both the raising and de-orbiting maneuvers can result in the individual satellites traveling in transecting orbits that have the potential to cross other spacecraft trajectories. While individual large constellations may be able to coexist in separate altitude and inclination bands, having thousands of satellites moving between these bands as new satellites are added and old satellites are removed could pose additional collision risks. Similar concerns have been raised regarding the impact that large numbers of university-class CubeSats might have in terms of their overall collision risk, especially as these satellites typically do not have propulsion systems for active maneuvering. To assess the impact that transecting satellites might have on future space traffic management strategies, this study explored a variety of realistic future scenarios using a high-fidelity simulation tool. The model can simulate the orbit of tens of thousands of resident space objects (RSOs) simultaneously, to include active satellites, debris, rocket bodies, or even future hypothetical satellite constellations, using a realistic force model that incorporates non-spherical gravity, atmospheric drag, and solar radiation pressure, as well as station-keeping. The simulation can be customized to accommodate different methods of calculating the probability of collision, as well as the process for determining probability ellipsoids and screening volumes. This makes it possible to replicate, and compare, different processes used by different spacecraft operators and space situational awareness (SSA) providers. As the model is run forward in time, each conjunction event is recorded, allowing for the analysis of statistics and meta-data related to these events, providing insight into the nature and frequency of potential collisions, such as whether are they active or passive objects, what size are the two objects, and who owns the objects (if known). This information makes it possible to characterize how changes to the status quo affect the number and type of conjunctions that occur, as well as the distributional effects on various types of satellite operators. To assess the general risks that transecting satellites might pose for hypothetical future space object environments, approximately 60,000 new large constellation satellites were considered, in addition to the existing catalog of approximately 7800 known resident space objects (RSOs), over a simulation period of one year. The results indicate that the future space environment will introduce a non-linear increase in conjunction events as the number of RSOs also increase. This will require adjustments to spacecraft fuel budgets in order to conduct the avoidance maneuvers necessary to minimize collision risk, both for existing and new satellites. This increase is due in large part to the higher density of RSOs and the overlap between some constellation orbits. Current catalog objects were shown to require three times more ∆V for collision avoidance (CA) maneuvers in the simulated future environment, and some constellation spacecraft were estimated to devote the majority of their annual ∆V to CA. The impact of small satellites was found to be proportional for the current space environment, and actually decreased in terms of percentage for the future scenario, suggesting that small satellites do not pose an outsized collision risk. Lastly, transecting satellites were found to contribute thousands of additional conjunctions outside of their operational orbit, and may require up to an additional 5% in CA maneuver fuel allocation.

conjunction assessment↗

An Initial Analysis of Automating Conjunction Assessment and Collision Avoidance Planning in Space Traffic Management

We introduce a framework that automates the process of assessing potential satellite conjunctions in space, and generating collision avoidance maneuvers to support mitigation efforts within a novel space traffic management (STM) architecture. A software implementation of the framework was developed in a MATLAB-STK integrated environment, however, the concept and framework is agnostic to the language or environment. The software pulls from existing catalogs of spaceborne objects and ingests user-defined parameters to produce conjunction data, which could potentially aid collision avoidance planning in the STM architecture. The utility of the software in maneuver planning and exploring a performance-based tradespace of actions is demonstrated using three example cases: one-to-one conjunction, one-versus-four conjunctions, and a near head-on collision. The framework also provides a test-bed for the use of application programming interfaces (APIs) to demonstrate machine-to-machine communication between entities in our proposed STM architecture. Results from this software implementation are expected to aid distributed decision-making among various stakeholders, and inform efficient, autonomous, structured but flexible concept of operations within STM.

Space Systems Engineering↗

A Concept for Civil Space Traffic Management

As technology has improved, operators have sought to use cubesats, as well as smallsats more generally, to perform increasingly more ambitious and sophisticated functions. Despite this, practical concerns associated with cubesat infant mortality, conjunctions, limited maneuverability, and debris generation have been relatively muted because most cubesats have been launched to lower orbits that limit both their orbital lifetime and consequences should a collision occur. NASA ARC has developed a concept for a highly-automated and distributed space traffic management (STM) architecture, drawing on similar work done to provide traffic management for small unmanned aerial systems (UAS) operating at low altitudes. The system proposes a strategy to accommodate growing space traffic volume safely, as well as pave the way for a transition of civil STM authority to a civilian governmental entity. The architecture envisions an open-access software platform architecture of data and service suppliers, consumers, and regulators, connected via a set of application programming interfaces (APIs). The platform would build on, rather than replicate existing integration and coordination efforts within the space situational awareness ecosystem, using existing standards for data message formats from organizations like the Consultative Committee for Space Data Systems and wrapping, rather than replacing existing integrations. We will present an initial STM architecture in this presentation, with a few examples showing how stakeholders can interact structurally, but flexibly, within this architecture.

Space Situational Awareness↗

An Investigation Into Transecting Satellites in Future Space Traffic Management Scenarios

The number of satellites expected to populate the near-Earth space environment is set to dramatically increase in the coming decade as new large constellations are approved and deployed. Current strategies for placing new batches of these satellites on orbit often involve launching into an initial orbit, and then performing apogee raising maneuvers to reach a target altitude. Similarly, end-of-life planning for these constellation satellites can consist of de-orbit burns that lower perigee to permit disposal via re-entry. Both the raising and de-orbiting maneuvers can result in the individual satellites traveling in high-eccentricity orbits that have the potential to transect other spacecraft trajectories. While individual large constellations may be able to coexist in separate altitude and inclination bands, having thousands of satellites moving between these bands as new satellites are replaced and old ones are removed could pose additional collision risks. Similar concerns have been raised regarding the impact that large numbers of university-class CubeSats might have in terms of their overall collision risk, especially as these satellites typically do not have propulsion systems for active maneuvering. To assess the impact that transecting satellites might have to future space traffic management strategies, this study explored a variety of future realistic scenarios using a high-fidelity simulation tool. The model can simulate the orbit of tens of thousands of resident space objects (RSOs) simultaneously, to include active satellites, debris, rocket bodies, or even future hypothetical scenarios, using a realistic force model that incorporates non-spherical gravity, atmospheric drag, solar radiation pressure, and more. As the model is run forward in time, various statistics and meta-data are gathered on any predicted conjunction event, providing insight into the nature and frequency of potential collisions, e.g., what size are the two satellites, who operates the satellites, are they active or passive objects, etc. Additional customization is available in terms of how probability of collision is computed, and how the probability ellipsoids and screening volumes are determined. The simulation tool also allows for rule-based maneuvers for active satellites, e.g, given an advance conjunction “warning,” one or both of the satellites can maneuver to a safe distance. A wide range of maneuvers can be implemented using impulsive or low-thrust methods, and the latencies can also be varied, e.g., using maneuver lead times of 48 hours, 24 hours, or 12 hours. Validation of the simulation results is performed against current and historical datasets available, to include comparisons to prior conjunction data messages (CDMs), object properties (mass, volume, etc.), and two-line-element records from both public and internal sources. Using the simulation environment, an assessment on the general risks that transecting satellites might pose for hypothetical future space object environments will be presented. This will involve the simulation of approximately 50,000 new large constellation satellites, in addition to the existing catalog of approximately 20,000 known resident space objects (RSOs), over propagation periods of one month to one year. A description of the simulation methodologies, scenarios evaluated, and validation methods will also be presented, as well as a preliminary assessment of the effectiveness of several candidate maneuver strategies that have the potential to reduce collision risk between active satellites.

Brian Gunter↗

SO-QT: Collaborative Tool to Project the Future Space Object Population

Earth orbit gets increasingly congested, a challenge to space operators, both in governments and industry. We present a web tool that provides: 1) data on todays and the historic space object environments, by aggregating object-specific tracking data; and 2) future trends through a collaboration platform to collect information on planed launches. The collaborative platform enables experts to pool and compare their data in order to generate future launch scenarios. The tool is intended to support decision makers and mission designers while they investigate future missions and scholars as they develop strategies for space traffic management.

space debris↗

Space Debris Environment Remediation Concepts

Long-term projections of the space debris environment indicate that even drastic measures, such as an immediate, complete halt of launch and release activities, will not result in a stable environment of man-made space objects. Collision events between already existing space hardware will within a few decades start to dominate the debris population, and result in a net increase of the space debris population, also in size regimes which may cause further catastrophic collisions. Such a collisional cascading will ultimately lead to a run-away situation ("Kessler syndrome"), with no further possibility of human intervention. The International Academy of Astronautics (IAA) has been investigating the status and the stability of the space debris environment in several studies by first looking into space traffic management possibilities and then investigating means of mitigating the creation of space debris. In an ongoing activity, an IAA study group looks at ways of active space debris environment remediation. In contrast to the former mitigation study, the current activity concentrates on the active removal of small and large objects, such as defunct spacecraft, orbital stages, and mission-related objects, which serve as a latent mass reservoir that fuels initial catastrophic collisions and later collisional cascading. The paper will outline different mass removal concepts, e.g. based on directed energy, tethers (momentum exchange or electrodynamic), aerodynamic drag augmentation, solar sails, auxiliary propulsion units, retarding surfaces, or on-orbit capture. Apart from physical principles of the proposed concepts, their applicability to different orbital regimes, and their effectiveness concerning mass removal efficiency will be analyzed. The IAA activity on space debris environment remediation is a truly international project which involves more than 23 contributing authors from 9 different nations.

Johnson, Nicholas L.↗

Starling Swarm Mission – Technology Objectives, Status and Future Applications

NASA’s Starling mission is advancing the readiness of technologies for cooperative groups of space craft referred to as swarms. The Starling swarm of four 6U spacecraft launched in July 2023, and is completing its tests in Low Earth Orbit (LEO) of four key technologies that will enable future swarm missions: onboard maneuver planning and execution to adjust the swarm formation; establishing and maintaining an adhoc network in space; relative and absolute orbit determination using optical sensors; autonomous collaboration between spacecraft for establishing and conducting a science observation plan. A mission extension is also being prepared to demonstrate a space traffic management architecture to address the large and rapidly growing number of space craft in LEO. In this presentation, the objectives of the Starling mission and its extension will be reviewed along with the latest status and mission outcomes. The presentation will also look at the revolutionary potential for swarms in future science and exploration missions and the impact to operations.

SpaceOps Starling Swarm Distributed Spacecraft Net↗

Satellite Conjunction Assessment Risk Analysis for "Dilution Region" Events: Issues and Operational Approaches

An important activity within Space Traffic Management is the detection and prevention of possible on-orbit collisions between space objects. The principal parameter for assessing collision likelihood is the probability of collision, which is widely accepted among conjunction assessment practitioners; but it possesses a known deficiency in that it can produce a false sense of safety when the orbital position uncertainties for the conjuncting objects are high. The probability of collision is said to be “diluted” in such a situation and to understate the possible risk; certain approaches have been recommended by researchers to provide (largely conservative) risk estimates and remediation methodologies in these cases. The present analysis explores two of the main proposals for quantifying and remediating possible risk in the dilution region and quantifies their operational implications. These implications with regard to imputed additional workload are considerable, especially in anticipating the conjunction event levels expected with the deployment of the USAF Space Fence radar. This effort has been undertaken as part of a larger enterprise that seeks to clarify the philosophical and statistical underpinnings of the conjunction risk assessment process. The analysis presented herein argues that a form of hypothesis testing is implicitly used in conjunction assessment risk analysis, and that there are a number of conceptual and practical reasons for constructing the associated null hypothesis to counsel against a satellite conjunction remediation action. In short, it is concluded that, for the purposes of determining whether a conjunction remediation action should be pursued, dilution-region probabilities of collision should be treated no differently from those produced under other circumstances.

Probability of collision↗