Lesson 2 of 4 · Qualify the engine cluster
Qualify the engine cluster
6 minute lesson · 3 checks along the way
Your goal for this lessonExplain why inherited engines still require integrated verification in a changed launcher.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Follow a linked name to explore its archive card. “Back to your lesson” brings you to the same part of the reading.
Read & understand
Reuse hardware and recheck its connections
The LE-7A was already part of H-IIA’s technical heritage. H-IIB used a pair of these first-stage engines. Reusing a developed engine can reduce the amount of entirely new component work, but the pair must operate with the new stage’s propellant system, structure and controls. A new arrangement creates new interfaces to verify.
Imagine two independently qualified engines connected to a shared stage. Their individual test results are useful evidence. They do not by themselves demonstrate the combined vibration environment, startup behavior or response to changing supply conditions. Integration tests ask whether the complete arrangement behaves as required.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Two engines do not automatically mean redundancy
Adding engines can increase available thrust. It does not automatically establish that a launcher can safely continue if one stops. Remaining thrust, vehicle mass, control authority, trajectory and fault response all matter. Without demonstrated capability for the relevant flight phase, an engine cluster should not be described as guaranteed backup propulsion.
For an original simplified force exercise, suppose two engines provide 100 units of thrust each and a particular flight segment requires at least 150 units. Losing one leaves 100 units, below the requirement. This is a fictional comparison, not H-IIB flight data; it shows why counting engines alone cannot establish fault tolerance.
Check 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Use flight evidence at its proper scale
H-IIB’s first launch on September 11, 2009 in Japan carried the HTV demonstration spacecraft, recorded here as HTV-1. The night photograph shows powered ascent above Tanegashima. The completed launch record provides evidence about the whole flight that a single photograph cannot supply.
The 2012 project-manager account also describes changes between flights, including fairing improvements and work on newer avionics. A vehicle’s configuration can evolve within a program. When assessing heritage, ask which parts remained the same, which changed and what evidence covers the changed combination. A program name alone is not a complete hardware specification.
NARITA Masahiro’s photograph of H-IIB’s first launch carrying HTV-1, September 11, 2009 JST. The full source frame is retained; resized and compressed only for display. CC BY-SA 3.0.
Look closely
What does the ascent view establish, and which later results require flight records?
See what to notice
The photograph shows the identified vehicle in powered ascent. It does not establish the later delivered orbit, spacecraft separation or station arrival.
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.