Incorporating a Test Flight into the Standard Development Cycle

Incorporating a Test Flight into the Standard Development Cycle

What could be called a Catch-22, or at least a thorny obstacle, exists in the standard development cycle. A component does not get into space until it’s proven, and it’s not proven until it gets into space. Of course, this is not absolute, but a gray area nevertheless exists in this aspect of the development cycle. This paper proposes the insertion of a test flight into the standard development cycle and, in the process, will detail the logistics, options, and costs associated with such a proposal. Finally, it will outline the ways in which customers—those purchasing new technologies—can use the concept of test flights to their advantage in the buying process.