Cases › DCA14FA002 › The analyst
BEECH 1900CERA AVIATION INC
What the docket says, assembled. No language model is involved, so nothing on this page can be invented — every line traces to a recorder, a report page or the Board's own record.
4
timed facts
8
precedents
11
passages to ask
Ask the docket
passages, not paraphrasesTry
Every answer is a passage of the docket with the page it came from, or the words “not in the docket”. Nothing is summarised or reasoned for you — read the source.
One timeline
4 timed factsthe recorder events from the FDR report, with the transcript's warnings, callouts, the words nearest each event and the final seconds — on one clock, as printed in each report- 14:54:24 AKDTFDRtakeoffp.4Aircraft began turning to line up with the runway heading of about 70 degreessee the traces at this moment ↗
- about 14:54:50 AKDTFDRclimbp.4Pressure altitude began increasing as the aircraft climbed to cruise altitudesee the traces at this moment ↗
- 15:22:58 AKDTFDRlandingp.4After an uneventful flight, the aircraft experienced dynamic vertical accelerations (nose and main landing gear collapse during landing on runway 22 at Homer)see the traces at this moment ↗
- about 15:23:20 AKDTFDRlandingp.4Vertical accelerations began to subsidesee the traces at this moment ↗
Recorder events without a clock time
- shortly after recording beganEngines spooled up to about 1700 rpm
Flight Data Recorder - Specialist's Factual Report · 5 events extracted by claude-fable-5-1 (in-session)
How the Board coded the sequence
- Landing-landing roll: Landing gear not configured→
- Landing-landing roll: Landing gear collapse
Precedents
8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded- BOEING 737-932ER · Delta Air LinesAtlanta, GA
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Action/decision › Info processing/decision
- ●Personnel issues › Task performance › Use of equip/info
- BOEING 767 34AF · UNITED PARCEL SERVICE COAlbuquerque, NM
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Action/decision › Info processing/decision
- ●Personnel issues › Task performance › Use of equip/info
- AIRBUS A320-232 · JETBLUE AIRWAYS CORPSacramento, CA
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Task performance › Use of equip/info
- AIRBUS A321 · Delta Air Lines, Inc.Atlanta, GA
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Task performance › Use of equip/info
- BOEING 737 7L9 · Eastern Airlines Group, Inc.,New York, NY
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Action/decision › Info processing/decision
- ●Personnel issues › Task performance › Use of equip/info
- BOEING 737 7H4 · SOUTHWEST AIRLINES COFlushing, NY
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Task performance › Use of equip/info
Landing gear collapse - BOEING 737 7H4 · SOUTHWEST AIRLINES COBranson, MO
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Action/decision › Info processing/decision
- ●Personnel issues › Task performance › Use of equip/info
- AIRBUS A320 - 214 · US AIRWAYS INCPhiladelphia, PA
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Action/decision › Info processing/decision
Landing gear collapse
What the record says
a pattern, not a findingacross the 8 closest cases · 8 carry coded findings · 8 have a probable causeFindings the Board cited in those cases
- 8 of 8Personnel issues › Action/decision › Actioncited here too
- 7 of 8Personnel issues › Task performance › Use of equip/infocited here too
- 5 of 8Personnel issues › Action/decision › Info processing/decisioncited here too
- 2 of 8Aircraft › Aircraft oper/perf/capability › Performance/control parameters
Occurrences it coded
- 2 of 8Tailstrike
- 2 of 8Abnormal runway contact
- 2 of 8Landing gear collapse
Set against the Board’s own findings for this case
Cited here, and common in the precedents
- Action/decision › Action
- Action/decision › Info processing/decision
- Task performance › Use of equip/info
Cited here, not seen in the precedents
- —
Common in the precedents, not cited here
- Aircraft oper/perf/capability › Performance/control parameters
A teaching device, not a verdict: what the record would have looked at, next to what the Board found.
In the Board’s words — the closest cases
- DCA18IA0262017-11-29 · BOEING 737-932ER · Delta Air Lines
The flight crewmembers’ failure to properly monitor the airplane’s flightpath, which caused the approach to become unstabilized and resulted in the airplane’s descent below the decision altitude while misaligned with the localizer course. Contributing to the incident were the first officer’s delay in setting go-around thrust after the captain called for the go-around and the captain’s failure to take control of the airplane after go-around thrust was not immediately set, both of which caused the airplane to come wi…
- DCA16CA1132016-03-05 · BOEING 767 34AF · UNITED PARCEL SERVICE CO
the pilot flying's failure to maintain airspeed and correct pitch attitude. Contributing to the accident was the pilot's failure to maintain appropriate thrust after disconnecting the autothrottles. Also contributing was the first officer's failure to monitor the decaying airspeed and increasing pitch.
- WPR10IA4302010-08-26 · AIRBUS A320-232 · JETBLUE AIRWAYS CORP
The first officer’s inadvertent activation of the parking brake in flight, which led to the airplane abruptly stopping and all four of its main landing gear tires deflating, and his use of a nonstandard procedure to cancel the airplane's monitoring alert system.
- DCA17LA1452017-06-23 · AIRBUS A321 · Delta Air Lines, Inc.
The first officer's improper landing flare, which resulted in a hard, bounced landing, and the flight crew’s improper bounced landing recovery procedures.
- DCA17IA0202016-10-27 · BOEING 737 7L9 · Eastern Airlines Group, Inc.,
The first officer's failure to attain the proper touchdown point and the flight crew's failure to call for a go-around, which resulted in the airplane landing more than halfway down the runway. Contributing to the incident were, the first officer's initiation of the landing flare at a relatively high altitude and his delay in reducing the throttles to idle, the captain's delay in manually deploying the speed brakes after touchdown, the captain's lack of command authority, and a lack of robust training provided by t…
What it recommended after them
- A-15-009TO THE FEDERAL AVIATION ADMINISTRATION: Amend air traffic control procedures so that controllers withhold landing clearance until the aircraft has passed all other airports that may be confused with the destination airport. · DCA14IA037Open Acceptable Alternate Response
- A-15-010TO THE FEDERAL AVIATION ADMINISTRATION: Modify the minimum safe altitude warning (MSAW) software to apply the MSAW parameters for the flight plan destination airport to touchdown, rather than automatically reassigning the flight to another… · DCA14IA037Open Acceptable Alternate Response
This is the pattern in the NTSB’s own record across similar accidents — which findings it cited, what it coded, what it recommended. It is drawn from the record, not written about this case, and it never assigns blame: investigations exist to prevent the next accident (ICAO Annex 13).