Constellation: test an architecture before it changes

NASA’s Constellation program developed a human exploration architecture in the years following the 2004 policy direction. It included Orion crew spacecraft, the Ares I crew launcher, the larger Ares V cargo launcher and a planned lunar lander. These elements had different jobs within a proposed return to the Moon, rather than being alternate names for one rocket.

The architecture separated crew launch from heavy cargo launch. That choice affected rendezvous, assembly, operations and the evidence required before people could fly. A diagram connecting the elements describes how a mission was intended to work; it does not establish that the complete sequence was ever carried out.

On October 28, 2009, Ares I-X flew an uncrewed suborbital development test. It combined a Shuttle-derived four-segment solid rocket motor with simulator hardware — open definition representing other portions of the intended vehicle. The test investigated flight dynamics, control, separation, recovery and ground operations.

Its upper stage, crew module and abort-system shapes were simulators rather than a complete operational crew vehicle. A successful test could supply useful data without qualifying all the systems needed for an astronaut mission. Reading the hardware configuration prevents the launch photograph from being mistaken for an Orion crew leaving for the Moon.

Constellation ended without carrying out its planned crewed lunar missions. Development wound down following the 2010 cancellation decision, with Ares I work continuing into early 2011. Reviews of its test program documented the effects of schedule and budget pressures on the planned evidence for later crewed flight.

Some technologies and work continued in subsequent exploration efforts, including Orion, but a later program was not simply every Constellation plan achieved unchanged. The useful historical question is which hardware, knowledge and requirements carried forward and which did not. Completed tests remain accomplishments while an unflown end-to-end architecture remains unflown.