Mission design and operations

A planetary mission is a decade-long argument that a particular set of measurements is worth a particular sum of money. The engineering follows from that argument, and understanding the structure explains why missions look the way they do.

Science traceability

Every instrument on a spacecraft must trace back to a question someone agreed to fund. The science traceability matrix makes that chain explicit.

The matrix is not paperwork. It is the defence against the most common failure in mission formulation: an instrument that is interesting, well-built and unable to answer the question the mission was funded to answer. Read the other way, it is also the tool that decides what to cut when the budget is exceeded, because any instrument that traces to no objective is removable.

Phases

The gates between phases exist to kill missions cheaply. Roughly 80% of lifecycle cost is committed by the end of Phase B while only a small fraction has been spent, which is why the preliminary design review carries so much weight: after it, changing the architecture means rebuilding rather than redrawing. See Spacecraft systems engineering.

Cost classes

Space agencies group missions into classes with fixed cost caps and competed selection. The structure shapes what gets proposed.

Competed classes work by inviting proposals against a cost cap and selecting on science value per dollar. The discipline is real: a proposal that exceeds the cap is not evaluated. This produces tightly scoped missions with a single clear objective, which is why Discovery missions tend to do one thing extremely well.

Flagship missions are directed rather than competed, arise from the decadal survey process, and carry the risk that a single overrun consumes a whole programme’s budget. Mars Sample Return is the current illustration of that failure mode. See Sample return missions.

The decadal survey

In the United States, the National Academies publish a decadal survey that ranks priorities for the coming ten years. It is produced by the scientific community rather than the agency, and its recommendations carry unusual weight because they represent a community consensus rather than an agency preference.

The system’s strength is that it prevents priorities from shifting with each administration. Its weakness is that a decade is long enough for cost estimates to be overtaken, and a mission recommended on a $2B estimate that becomes$5B distorts everything ranked below it.

Concept of operations

The ConOps describes what the spacecraft does, in sequence, from separation to disposal. It is where the mission becomes concrete, and it usually exposes the conflicts that the requirements documents hid.

The arrival box is where missions are lost. Orbit insertion and entry, descent and landing are single-attempt events with no opportunity to retry, executed autonomously because light time makes ground intervention impossible. Every other phase tolerates a problem and a recovery; this one does not.

Extended missions deserve emphasis because they are frequently the best value in the portfolio. The spacecraft is already there, already working and already paid for, so an extension costs only operations. Cassini’s extensions delivered the Enceladus plume science that justified the mission in retrospect, and Opportunity’s ninety-day nominal mission ran for fourteen years.

Operations

Operating a planetary mission differs from operating an Earth satellite in one decisive respect: light time. At Mars, one-way delay runs from 4 to 21 minutes depending on geometry; at Jupiter it is over 40 minutes.

Nothing can be flown by hand at those delays. The spacecraft executes stored command sequences, and the ground builds each sequence, validates it against a simulator, and uplinks it days ahead. A rover drive is planned, simulated, uplinked and executed before the team sees the result.

This drives three practices. Sequence validation is exhaustive, because an error executes without supervision. Onboard autonomy handles anything too fast for the ground, including fault protection and hazard avoidance during landing. And safe mode must be survivable for days, since that is how long a recovery cycle takes. See Fault tolerance and reliability and Autonomous spacecraft.

Planetary protection

Missions to bodies that might harbour life, or that might contaminate Earth on return, are governed by planetary protection requirements derived from the Outer Space Treaty and codified by COSPAR.

These requirements are expensive and constrain the design directly. Spacecraft components may need dry heat sterilisation, which not all electronics survive, and orbiters must be placed in orbits that will not decay onto the surface within a specified period. Galileo and Cassini were both deliberately destroyed in their host planets’ atmospheres to eliminate any chance of contaminating Europa and Enceladus.

References

• NASA/SP-2016-6105 Rev 2, NASA Systems Engineering Handbook.
• National Academies of Sciences, Engineering and Medicine, Origins, Worlds and Life: A Decadal Strategy for Planetary Science and Astrobiology 2023-2032, 2022.
• Brown, C. D. Spacecraft Mission Design, 2nd ed., AIAA, 1998.
• COSPAR Policy on Planetary Protection, current revision.
• Squyres, S. Roving Mars, Hyperion, 2005. An unusually candid account of proposal, development and operations from the inside.