FRA Portal
NTSB accident reports broken down into chains of what happened and why
Description
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.
Features
- Downloads and checksums the NTSB’s accident databases, about 94,000 events across both eras
- An aircraft taxonomy of 20 classes, 229 families and 276 variants, held to 281 golden test cases
- A causal vocabulary that maps all but 0.003% of post-2008 NTSB finding text
- Chains, incidence and attribution with confidence intervals, from a Rust reference implementation
- Analyses written by Claude Code through an authenticated MCP server, one report at a time