ESA title
Herschel control room at ESOC
Agency

Routine operations

4546 views 5 likes
ESA / About Us / ESOC

With the launch a success, and the spacecraft safely in orbit, the Flight Control Team settles in for what may turn into years of routine daily activities. The key elements of success at ESOC include long-term planning, accommodating changing conditions as the mission progresses through eclipses or orbital evolutions and – always – anticipating the unexpected.

Continuing teamwork

In the months and years after launch, the Flight Control Team at ESOC works closely with the mission’s Science Operations Centre (SOC), for ESA’s planetary, observatory and solar missions, or the Payload Data Ground Segment (PDGS), for the Agency’s Earth missions, to plan and carry out the daily observation activities of the satellite (the team may work closely with other centres involved in the mission as well).

Space navigators at work
Space navigators at work

These plans must not only take into account the scientists’ requests for specific observations, for example radar imaging of a particular region of a planet’s surface, they must also consider the constraints associated with operation of the satellite.

These may include:

  • Limitations on available power under certain conditions
  • Restrictions on available on-board storage of data
  • Restrictions on which directions the satellite is permitted to point as it moves through its orbit
  • Restrictions on simultaneous operation of certain instruments
  • Minimisation of fuel expenditure so as to prolong the satellite’s life as much as possible
  • Ground station availability and location

… and there are many more!

The flight control team works daily with specialist teams at ESOC in the areas of flight dynamics, software systems, Estrack stations and others to ensure that the mission is fully supported, especially during demanding periods such as eclipses, solar conjunctions, manoeuvres or orbit changes, which, in varying degrees, are experienced by every mission. 

Critical operations: everyday life at ESOC

Mission operations during the routine phase involves, for most missions, certain critical events that require particular attention and many months or even years of preparation. Successfully handling these is one of the specialities of ESOC, where an enormous reservoir of expertise and skill in all types of mission operations exists and which we apply in carrying out difficult and often unique operations.

LISA Pathfinder control room at ESOC
LISA Pathfinder control room at ESOC

For instance, most interplanetary missions experience several critical events in their lifetime, from swing-bys – planetary gravity assists – to fast fly-bys of small solar system objects like asteroids or comets to landings and orbit entries.

These operations require highly precise trajectory determinations and a complex sequence of actions that have to work perfectly the first time, as they do not usually offer a second opportunity. Particularly critical are the insertions into planetary orbit or any landing activity: anything going wrong in these critical events may result in the total loss of a mission.

Other types of missions also experience critical events during their ‘routine’ phase: these include special trajectory adjustments, collision avoidance manoeuvres, re-entry or de-orbiting operations at the end of life, etc.

Software support engineer
Software support engineer

In fact, the routine phase can be anything but!

Intensely routine

  • For Herschel and Planck, mission teams had to regularly monitor the spacecrafts’ remaining level of liquid helium coolant, which naturally evaporates slowly over time; once this was gone, the missions ended.
  • The orbital separation between the Cluster mission’s four individual satellites varies regularly from a few hundred to several thousand kilometres; this involves tricky orbit adjustments, carefully computed to minimize the use of thruster fuel.
  • XMM Newton has no on-board storage; each day, its observations must be carefully planned to occur during a ground station pass, so that its data can be downloaded as soon as acquired, otherwise it would be lost.
  • Venus Express has conducted several ‘aerobraking’ campaigns, in which controllers gingerly lower the satellite’s orbit so that it skims the top of the Venusian atmosphere, generating a drag force that helps scientists better understand the enigmatic planet’s complex atmospheric dynamics.
  • Mars Express must frequently manoeuvre to avoid a ‘conjunction’ (which means, in this case, ‘collision’) with Mars moon Phobos. ESA’s Red Planet operations team has also been called upon by NASA to track, record and relay signals transmitted by the US Phoenix and Mars Curiosity missions during their arrival at Mars. And Mars Express routinely tests its capability to relay telecommands to US rovers operating on the planet’s surface.
  • When Rosetta conducted a fly-by of asteroid 2867 Steins in 2008 and Lutetia in 2010, the Flight Control Team spent months preparing and rehearsing for the high-speed events. For Lutetia, at closest approach, the relative speed between Rosetta and the asteroid was 15 km/second; if you had been riding on Rosetta and you blinked, you would have missed seeing the mysterious asteroid!

Since the 1960s, ESOC has built up the tools and expertise required to perform re-entries, de-orbiting, collision avoidance manoeuvres and other complex actions in a robust, reliable and safe way.

Unexpected events

Not all missions progress smoothly, however, and in the harsh environment of space unexpected events sometimes occur. These can have numerous causes: for instance, a critical on-board component can fail due to mechanical or thermal stress, a previously undetected bug in pre-loaded software can suddenly cause an anomaly or solar radiation can cause a vital electronic chip to stop working.

 

Unexpected problems can also arise in ground systems; at least these have the benefit of happening in computers, hardware and software that engineers can physically examine or replace. 

For every alarm condition raised, spacecraft controllers identify the anomaly and take immediate recovery actions, using the flight control procedures developed at ESOC prior to launch.

Recovering missions

Recovery actions first aim to stabilise the situation and ensure the spacecraft’s basic survival. Next, the problem is analysed and the cause isolated.

If the cause can be removed – because it was due to a temporary glitch or it can be solved by an on-board software update or by switching a failed hardware unit to an equivalent redundant unit – the solution is implemented, the relevant procedures updated and the nominal mission can be resumed.

If the failure is permanent and non-recoverable, the ingenuity of ESOC’s operations experts comes into play! Teams devise and implement a work-around solution that ensures the continuation of the mission even in the presence of the failure, and often without affecting the mission’s scientific goals.

Teams also regularly train on recovering missions from unexpected anomalies; if a new recovery procedure needs to be devised for a complex unforeseen anomaly, it will be developed and exercised on the simulator before the operation is attempted on the spacecraft itself.

In the past decades, ESOC has developed an enviable record of recovery and rescue of missions thought initially to be totally lost. These include:

• Giotto (1985) – New scientifically valuable mission designed and implemented after satellite (unexpectedly) survived encounter with comet Halley
• Olympus (1989) – Telecom satellite that began tumbling and drifted out of control
• Hipparcos (1989) – Star-observatory mission injected into incorrect orbit
• XMM Newton (2008) – Recovery of mission after complete loss of contact
• Mars Express (2011) – Recovery of mission after malfunctioning of on-board mass memory

… and many more!

End of mission

A spacecraft is designed to fulfil the mission objectives for a defined period of time, ranging typically from two to ten or more years. In some cases, mission termination can be unexpected and dramatic, but normally termination is planned in order to not lose contact with the spacecraft and to control it while it moves into a safe graveyard orbit.
 

Operations team planning ERS-2 passivation and deorbit burns
Operations team planning ERS-2 passivation and deorbit burns

It is now common practice at ESA to apply space debris mitigation measures, which are especially important in densely populated orbits. For example, geostationary spacecraft are boosted 300 km above (or below) the geostationary orbital plane, to a disposal orbit where they don’t pose a danger to active spacecraft.

Spacecraft in low or medium orbits are typically commanded to re-enter into the Earth’s atmosphere, where they burn up.

Whatever the fate of the spacecraft, the mission is considered permanently ended once ground contact with the spacecraft is no longer possible.

Related Links