Escape testing and its limits

Orion’s Launch Abort System is intended to move the crew capsule away from a dangerous launch situation. Escape must produce a suitable separation and orientation for subsequent events; it is a coordinated sequence rather than simply the largest available thrust.

An abort system addresses selected emergencies during its period of availability. It does not substitute for every other safety function during the journey. For an original review exercise, distinguish escaping a failed ascent from maintaining a cabin during cruise: both protect people, but they involve different conditions and equipment.

NASA flew Ascent Abort-2 on July 2, 2019 using a test version of Orion and a functioning launch-abort system. The mission exercised ascent escape under its specified flight conditions. It was not an inhabited mission around the Moon.

The AA-2 capsule had no parachutes and was not recovered. Its test data were transmitted and also stored in ejectable recorders that could be recovered. Parachute qualification belonged to a separate test campaign. Those details make the test more informative: they show which questions the team deliberately included and which it answered elsewhere.

Read the boundary of an abort test

Suppose an escape test establishes suitable clearance and orientation, while a separate descent test establishes parachute behavior for its own conditions. A system review must show how the conditions at the end of escape connect to the conditions assumed for descent. Two positive test reports do not automatically establish that boundary.

Good test interpretation asks what was built, what environment it experienced, what was measured and what was excluded. A simplified article is not an inferior photograph of the final vehicle; it is an instrument for investigating selected requirements. Its usefulness comes from an explicit relationship to the flight design.