Prototype · Specification
FRA Portal
NTSB accident reports broken down into chains of what happened and why.
DWMM Holdings · Prototype · Rust, TypeScript, Preact
Abstract
Flight Report Analysis takes the NTSB’s fixed-wing accident records and turns each one into a chain of causes, using a method called What–Why Chain Analysis. A fatal collision is the what, the forced landing before it is its why, the power loss is the why of that, and so on down to the pilot’s fuel error. Pick any link as the what and you get the breakdown of its whys across every accident, at whatever depth and level of detail you choose. The pipeline downloads the NTSB’s accident databases, classifies every aircraft against a taxonomy of 276 variants, and maps the NTSB’s coded findings onto one shared vocabulary for both of its coding eras. Reports are then analyzed one at a time by Claude Code and stored through a hosted MCP server, and 112 fatal airplane accidents from 2024 and 2025 have been done so far. A web viewer reads them; it and the MCP server are still scaffolds.
1Every accident is a chain. Each link is the why of the one above it.
The fatal collision is a what, and the forced landing is its why. The forced landing is a what, and the power loss is its why. The method builds that chain for every aircraft in every NTSB record.
outcome.fatal
end.collision ← WHAT the user sees first
end.forced_landing ← its WHY … and the next WHAT
crit.power_loss.total ← WHY of the forced landing
mech.fuel.starvation [C] ← WHY of the power loss
act.pilot.fuel_mgmt [C] ← WHY of the starvation (root why)
env.terrain [F] ← context: trees at the landing site- outcome
- How bad it was
- end
- The final event: a collision, a forced landing
- crit
- The critical event that started it: a power loss, a stall
- mech
- The mechanism behind that: fuel, the engine, the airframe
- act / env
- What a person did, and the conditions around it
2Status
Prototype. Works, but isn’t finished.
If this is useful to you, or you’d like to see it built, get in touch