Lesson 3 of 4 · Investigate a failure chain
Investigate a failure chain
6 minute lesson · 3 checks along the way
Your goal for this lessonConnect telemetry, recovered hardware and testing to a defensible failure explanation.
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
From observed shutdown to a mechanism
H-II Flight 8 failed on November 15, 1999. The first-stage LE-7 stopped early, and the payload did not reach its intended orbit. NASDA’s May 24, 2000 report drew on flight data, the recovered engine, simulations and confirmation tests. It connected the shutdown to hydrogen turbopump stall following damage to the pump’s inducer.
The inducer helps feed liquid into the pump. The report linked its damage to interacting fluid disturbances, including cavitation-related pressure fluctuations and blade vibration. That is a chain of causes, not a claim that every failed engine has the same defect. The report’s date matters: it records a developed investigation rather than an explanation available at the instant of launch.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Different evidence answers different questions
Telemetry can reveal when pressure or rotation changed. Recovered material can reveal the location and character of damage. Controlled testing can examine whether a proposed mechanism appears under relevant conditions. Each source has limits: a broken part alone may not show whether it broke first or was damaged during the later accident.
Imagine two fictional explanations for a pump shutdown: loss of supply pressure or an electrical sensor fault. A pressure trace alone may be ambiguous. Independent measurements, physical inspection and tests that reproduce the suspected condition can help distinguish them. The goal is to find evidence that separates explanations, rather than collecting many copies of the same signal.
Build and test a failure explanation
Original teaching diagram. Original investigation guide; no claim that one source proves every step.
Open full-size diagram in a new tab: Build and test a failure explanationCheck 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Turn an explanation into a verification plan
The May 2000 development plan describes tests at varied engine-inlet pressures and attention to manufacturing quality for the successor H-IIA. These actions connect the suspected mechanism to conditions that could be measured and controlled. A planned test, however, is not automatically a completed qualification result.
In an original review exercise, a team proposes a new pump part but tests it only under the conditions that previously caused no trouble. That leaves the failure-related conditions unresolved. A stronger plan states the operating range, manufacturing differences to examine, acceptance criteria and evidence needed before proceeding. Learning from a failure requires checking the proposed remedy, not simply renaming the design.
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.