The ESA OGS (image credit: Emmet Fletcher)

There are sometimes confusing statements made regarding the different sensors used within a Space Situational Awareness (SSA) system. Even if we are discussing radar or optical, there are – in essence – three types of sensor: surveillance, tracking and imaging. Since imaging sensors are a very special type – and do not figure in the development of the ESA SSA system, we will ignore them for this specific discussion. What we will discuss here is the difference between surveillance and tracking sensors – a difference that is often overlooked or ignored or just not understood, but is of prime concern when discussing the development of an effective space surveillance system.

Tracking Sensors

It is probably easier to start any discussion of the differences between tracking and surveillance sensors by focussing (no pun intended) on the major characteristics of a tracking sensor.

Tracking sensors usually have a very small field of view – rather like when you use a domestic telescope and you can see a very small area of the sky. Given a fixed detector performance, the smaller the field of view, the more precise the locations of the objects detected within this field of view (when comparing like-for-like). This is fantastic when you want to increase the precision of an object for when you already have some orbital data of, such as a piece of debris for which you have a rough orbit and may collide with an operational spacecraft. You just take this rough orbit and set your tracking sensor to point along this orbit at the position you think the debris should be. When you see the debris, you can then create a more precise orbit – since your detector is looking at a very small region of space and so has a high precision.

The problem is – of course – that since you only see a small area of the sky, if the error on your rough orbit is too high, you might not see the debris at all (it might slip by outside your field of view). It also makes these sensors very inefficient (read: almost useless) for the build-up a catalogue of objects. Since the view is small, it is difficult to trap new objects, unless you are very lucky. Even then, given the small view, you only have a very short reading as the debris passes across the sensor. This results in an initial orbit guess (orbit determination) which can have very high errors. For the development and maintainence of a catalogue, we need a surveillance sensor.

Examples of European tracking sensors: TIRA (Germany), BEM Monge (France), OGS (ESA), CAMRA (UK)

Surveillance Sensors

The TFRM (image credits: Emmet Fletcher)

A surveillance sensor is the workhorse of a surveillance system. It provides the data for both the initial catalogue development (the so-called ‘cold start’) as well as the day-to-day maintenence of the catalogue.

The main difference between the tracking and surveillance sensor is that the surveillance sensor sees a very large area of the sky at the same time. It is also not actively looking for objects, but rather passively (which counterintuitveilly can be active) waiting for debris – any debris – to pass over it. Once it detects something passing over it, the data related to this pass is processed and passed to the catalogue maintainence system.

In this way, the surveillance sensor creates a ‘fence’ which is triggered by any object passing through it. No prior information is needed by the sensor to generate new data regarding a specific debris object and the system therefore does not need to be ‘tasked’ to look out for an object. In reality, the fence can also be generated using an active sensor scanning the sky with a frequency that ensures nothing will be missed. This is the case for radar systems which quickly scan across a path. It doesn’t look in all directions at all times, but still forms an effective fence.

Through the use of surveillance sensors, a catalogue can be built up. The precision of this catalogue will not be very high initially, although the design of the surveillance network should be such that the eventual precision using just the surveillance assets will be enough to give a reliable warning of potential collisions with operational satellites. When the warning is triggered, then comes the turn of the tracking sensors to refine the orbit of this debris and provide the precise information that satellite operators need to plan their maneouvres.

Examples of European surveillance sensors: GRAVES (France), RAF Fylingdales (UK/US), TFRM (Spain)

If you have any comments, clarifications, corrections or suggestions – please comment!

· Comments Off · Categories: news · Tags: ,

msnbc.com
Russian Mars probe crash sets off confusion, conspiracy theories
msnbc.com
[ 6 Biggest Spacecraft to Fall Uncontrolled From Space ] "You're never quite sure," said Emmet Fletcher, Space Surveillance and Tracking Manager at the European Space Agency (ESA). "Eyewitness accounts are good, so if someone sees it coming in and

· Write a comment · Categories: interviews, media · Tags:

Amigos de la onda corta – 16/07/11

La basura espacial. Emmet Fletcher, responsable del segmento de vigilancia espacial del programa europeo de Conocimiento del Medio Espacial de la Agencia Espacial Europea, nos habla de cómo los satélites de telecomunicaciones y otros fragmentos de diferentes dimensiones se han convertido en un verdadero problema para las operaciones espaciales. También del trabajo que realizan para catalogar y clasificar esta basura cósmica que ayudarán a evitar colisiones y mejoren la seguridad de los satélites.

Onda Cero Interview 16 July 2011

Holger Krag, Heiner Klinkrad, Tim Flohrer, Emmet Fletcher. SpaceOps2010 Conference, 25-30 April 2010, Huntsville, Alabama AIAA 2010-1927

Europe is preparing for the development of an autonomous system for space situational awareness. One important segment of this new system will be dedicated to the surveillance and tracking of space objects in Earth orbits. First concept and capability analysis studies have led to a draft system proposal. This foresees, as a first deployment step, a ground-based system consisting of radar sensors and a network of optical telescopes. These sensors will be designed to have the capability of building-up and maintaining orbital elements and properties of space objects in a catalogue. Based on these capabilities, a number of related services will be provided including collision avoidance and the prediction of uncontrolled re-entry events. For the time being, user requirements; defining the various services and their required accuracy and timeliness, are being consolidated. Parameters such as the lower diameter limit above which catalogue coverage is to be achieved, the level of catalogue coverage in various orbital regions and the accuracy of the orbit data maintained in the catalogue are important design drivers for the number, location and performance of the various sensors. In this requirement consolidation process the performance to be specified has to be based on a careful analysis which takes into account accuracy constraints of the services to be provided, the technical feasibility, complexity and costs. User requirements cannot be defined without understanding the consequences they would pose on the system design.

This paper will outline the user requirement consolidation process for the surveillance and tracking segment. It will present the core user requirements and the definition of the services that are derived from them. The desired performance parameters are explained, together with the corresponding justification. This will be followed by an identification of the major design drivers. The influence of these drivers on the system design will be analysed, including limiting diameter, catalogue coverage and orbit maintenance accuracy driven by the planned collision avoidance service. Finally, a first-pass compilation of settled performance parameters for the surveillance and tracking segment will be presented and design solution concepts of a corresponding ground-based surveillance radar.