Lesson 4 of 5 · Hermes spaceplane
Hermes: learn from an unflown spaceplane
8 minute lesson · 3 checks along the way
Your goal for this lessonDistinguish Hermes’s changing design proposals, development decisions and legacy from demonstrated flight capability.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Words with a dotted underline open a short definition right here in the lesson.
Read & understand
Understand the proposed role
CNES began studying a small European spaceplane in the early 1980s. Hermes was intended to provide European crew access to orbit, eventually using Ariane 5. The proposal was associated with a free-flying station element in the original Columbus planning. That historical architecture should not be mistaken for the Columbus laboratory later attached to the International Space Station.
ESA approved Hermes in November 1987 with a preliminary development phase. Approval opened further work; it did not certify a flight-ready spacecraft. The program sought a combination of crew transport, orbital operations and a return landing, connecting national ambitions with European cooperation. Those goals help explain why the project mattered even though it never carried a crew into space.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Follow the changes through the whole system
The proposed design changed as payload, crew accommodation, launch capability and safety requirements interacted. Following Challenger, added precautions contributed to mass and cost pressures. Hermes influenced Ariane 5’s requirements. ESA’s historical account describes cancellation in 1992 after delays and difficulty meeting cost and performance goals. No Hermes spaceplane flew.
For a fictional design exercise, suppose a new safety system adds mass. The team cannot evaluate it only as an isolated component: added mass changes launch demands and may compete with payload or other equipment. Removing mass elsewhere can create another compromise. The right comparison records the design version, assumptions and consequences, rather than assembling the most attractive specifications from different proposals.
Hermes: distinguish development from flight
Original teaching diagram. Development. Changing requirements and models. ESA approval and design work. Outcome. Cancelled without flight. Influence needs a documented link. A proposed capability remains a proposal until demonstrated.
Open full-size diagram in a new tab: Hermes: distinguish development from flightCheck 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Compare a proposal with a demonstrated capability
A mock-up can communicate shape and accommodation. An can support particular tests. Neither is automatically a flight vehicle, and a proposed mission date is not a completed launch. Hermes drawings should be labeled with their purpose and design stage. A surviving model does not contradict the fact that an operational Hermes spacecraft was never built.
Imagine an exhibit comparing Hermes with ATV. A useful comparison can discuss European goals, technical choices and institutional experience while clearly distinguishing Hermes’s unflown development from ATV’s completed missions. Cancellation is an outcome worth explaining, not a reason to erase the project. Equally, later European achievements do not retroactively demonstrate every Hermes design claim. Trace which ideas influenced later work and what evidence actually establishes each capability.
Check 3 of 3
10 pointsUse the reading above. You can try again without losing points.
Put it together
Your lesson progress
Each check connects to a part of the story. Complete all 3 to earn your 25-point lesson bonus.
Explore further · Optional
Go to the source
Explore the evidence behind this lesson. These optional readings and videos open in a new tab.