Operational Collision Avoidance at Esoc

Operational Collision Avoidance at Esoc

OPERATIONAL COLLISION AVOIDANCE AT ESOC Q. Funke2), B. Bastida Virgili2), V. Braun2), T. Flohrer1), H. Krag1), S. Lemmens1), F. Letizia2), K. Merz1), J. Siminski2) 1) Space Debris Office (HSO-GR), ESA/ESOC 2) IMS Space Consultancy GmbH at Space Debris Office (HSO-GR), ESA/ESOC Abstract The European Space Agency's (ESA) Space Debris Office provides a service to support operational collision avoidance activities. This support currently covers ESA's missions Cryosat-2, Aeolus, the constellation of Swarm-A/B/C, seven Sentinels, as well as missions of third party customers. In this work, we describe the current collision avoidance process for ESA and third-party missions in LEO. We give an overview on conjunction event detection, collision risk assessment, orbit determination, orbit and covariance propagation, process control, and data handling. We pay special attention to the effect of warning thresholds on the risk reduction and manoeuvre rates, as they are established through risk mitigation and analysis tools, such as ESA's Debris Risk Assessment and Mitigation Analysis (DRAMA) software suite. In order to handle the large number of Conjunction Data Messages and the associated risk analyses, a database-centric approach has been developed. All CDMs and risk analysis results are stored in a database. In this way, a temporary local "mini-catalogue" of objects close to our target spacecraft is obtained, which can be used e.g. for manoeuvre screening and avoidance manoeuvre planning. The database is also used as the backbone for a web-based tool, which consists of the visualisation component and a collaboration tool that facilitates the status monitoring and task allocation within the support team as well as the commu- nication with the control team. Finally, we provide statistics on the identified conjunction events, taking into account the known significant changes in the LEO orbital environment, and share ESA's experience along with recent examples. EISCAT European Incoherent Scatter Sci- GLOSSARY entific Association EO Earth Observers ACPL Accepted Collision Probability ESA European Space Agency Level ESOC European Space Operations Centre ARES Assessment of Risk Event Statis- IADC Inter-Agency Space Debris Coor- tics dination CAMOS Collision Avoidance Manoeuvre Committee Optimization Software ISO International Organization for CDM Conjunction Data Message Standardization CORAM Collision JSpOC Joint Space Operations Center Risk Assessment and Avoidance LEO Low Earth Orbit Manoeuvre LEOP Launch and Early Orbit Phase CORCOS Collision Risk COmputation Soft- MASTER Meteoroid and Space Debris Ter- ware restrial Environment reference CRASS Collision Risk ASsessment Soft- NASA National Aeronautics and Space ware Administration CSM Conjunction Summary Message ODIN Orbit Determination by Improved DISCOS Database Information System Normal Equations Characterizing Objects in Space ODR Orbital Data Request DRAMA Debris Risk Assessment and Miti- gation Analysis OEM Orbit Ephemeris Message OGS Optical Ground Station ECSS European Cooperation for Space O/O Owner and/or Operator Standardization SCARF Spacecraft Conjunction Assess- and by having key members in the 13-nations Inter-Agency ment and Risk Frontend Space Debris Coordination Committee (IADC), the SDO SDO Space Debris Office is actively promoting ESA-internal views & public aware- SP Special Perturbations ness on space debris issues. SSA Space Situational Awareness 1.2. Objectives TCA Time of Closest Approach TIRA Tracking and Imaging Radar The goal of this paper is to provide an overview on the re- TLE Two-line Elements cent developments in ESA’s collision avoidance service UN United Nations provided to ESA missions and third parties. USSTRATCOM US Strategic Command With an increasing number of supported missions and var- ious recent changes in the way data on conjunction events is received from external sources, it was necessary to intro- 1. INTRODUCTION duce several changes to the processes at SDO. This in- Today, the European Space Agency (ESA) operates sev- cludes the continuous development of a web-based eral missions in the Low-Earth orbit (LEO) region, i.e. to frontend allowing the different missions to access the pro- altitudes of up to 2000 km. The highly inclined Sun-syn- cessed information on any event related to that mission. chronous orbits offer a wide range of advantages especially Apart from the operational procedures, this paper also dis- for Earth observation. Concurrently, this regime is densely cusses how the experience from collision avoidance oper- populated with space debris, posing a risk of collision to ations are used to cross-validate space debris tools by the the operated satellites. ESA’s Space Debris Office is ad- SDO: the most prominent example is the DRAMA/ARES dressing this particular threat by routinely performing con- (Assessment of Risk Event Statistics) tool, which gives junction analyses for active satellites in LEO. mission designers the possibility to evaluate the mission needs for collision avoidance already at a very early project 1.1. ESA‘s Space Debris Office phase. The Space Debris Office (SDO) provides operational and This paper thus reflects the most recent and on-going ac- contingency support to ESA and third-party missions, dur- tivities of the SDO in the context of a continuously evolv- ing the Launch and Early Operations Phase (LEOP) and ing environment in the collision avoidance area. routine operations, including collision avoidance and re- 1.3. Methodology and outline entry predictions and analyses. Different sensors (e.g. ESA’s Optical Ground Station (OGS) telescope, Fraunho- In order to understand recent changes in the procedures, it fer’s Tracking and Imaging Radar (TIRA), the radar sys- is important to have a full picture of how the different pro- tems of the European Incoherent Scatter Scientific Associ- cesses evolved. Therefore, after a quick overview in Sec- ation (EISCAT), Zimmerwald telescopes) can be utilised tion 2.1, the historic evolution of the process at SDO will for the acquisition of measurements, which are then pro- be described in Section 2.2, also introducing the user into cessed at the SDO to provide additional information in the different types of data and formats involved in the pro- those mission phases. cess. Then, the current approach will be described in Sec- The development and the maintenance of an infrastructure tion 2.3. in support of ESA’s commitment on space debris mitiga- There has been always the need to define reaction thresh- tion and risk reduction is another key task of the SDO, olds, which trigger events in the collision avoidance pro- which is emphasized by the development and maintenance cess. The different methods to approach collision avoid- of several debris environment and risk analysis tools, The ance and the associated thresholds will be presented in Sec- Meteoroid and Space Debris Terrestrial Environment ref- tion 2.4. erence model (MASTER) and the DRAMA tools suite are The Sections 2.5 and 2.6 give an overview on how experi- downloaded and applied in analyses by users worldwide1, ences from the operational collision avoidance have been and the Database Information System Characterizing Ob- used to validate the ARES tool. jects in Space (DISCOS) database provides information on The updated web-based frontend, which provides access to on-orbit objects2. collision avoidance analysis to the supported missions, is The office is supporting the development of debris envi- presented in Section 2.7. Finally, some statistics and a few ronment remediation technologies, like Active Debris Re- recent examples underline the methodology presented in moval, especially in the context of ESA’s Clean Space in- Section 3. itiative. Further, based on the office’s expertise in running An important aspect in the operational collision avoidance operational services on Space Situational Awareness is to assess the efficiency of a method, by addressing ques- (SSA) data and space surveillance techniques, office mem- tions like: how much risk is mitigated by collision avoid- bers lead the Space Surveillance and Tracking Segment of ance manoeuvres? What is the number of false positives ESA’s SSA Programme. where a manoeuvre was performed but a collision would By coordinating ESA’s debris research through contrib- not have occurred without the manoeuvre? While it is dif- uting to the European Cooperation for Space Standardiza- ficult to validate the number of false positives, as this tion (ECSS), the International Organization for Standardi- would imply an actual collision for a satellite that is cov- zation (ISO) and to United Nations (UN) mitigation efforts, 1 AcCessible via https://sdup.esoc.esa.int 2 AcCessible via https://disCosweb.esoC.esa.int ered by a collision avoidance support, it is possible to as- sess the risk mitigation introduced by a collision avoidance Table 1: Supported ESA and third-party missions and ser- process. This has been done in the past, e.g. via an analysis vices provided, February 2019. of Conjunction Summary Messages (CSM) and combining those data with the one obtained from dedicated tracking Satellite Comment [2], and will thus not be part of this paper. ERS-2 Manoeuvre/TLE screening, CDM processing, fully operational from 2. COLLISION AVOIDANCE PROCESS AT ESA 2006 ended after de-orbiting phase in 2011 In this section we describe ESA’s collision avoidance pro- Envisat Manoeuvre/TLE screening, CDM cess, based on detailed descriptions in earlier work [1,2]. processing, fully

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    13 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us