Cases › DCA17LA145 › The analyst
AIRBUS A321Delta Air Lines, 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.
8
timed facts
8
precedents
10
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
8 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- 13:35:55FDRApproachp.3Aircraft descended below 2000 feet AGL; airspeed about 160 knots, vertical speed 500-1000 fpm descent, landing gear selected down, autopilot not engaged, autothrottle engagedsee the traces at this moment ↗
- 13:37:58FDRApproach/Flarep.3Pitch began increasing from 2 degreessee the traces at this moment ↗
- 13:38:03FDRFlarep.3Flare law mode activatedsee the traces at this moment ↗
- 13:38:06FDRFlarep.3Autothrottle disengagedsee the traces at this moment ↗
- 13:38:07FDRTouchdownp.3Both main gear weight on wheels (WOW) status switched from air to ground; aircraft experienced maximum vertical acceleration of 1.89 gsee the traces at this moment ↗
- 13:38:08FDRTouchdown/Bouncep.3Both main gear WOW status switched briefly back to airsee the traces at this moment ↗
- 13:38:09FDRSecond touchdown/Tail strikep.3Both main gear WOW status switched back to ground; aircraft experienced maximum primary pitch angle of 9.7 degrees nose up, maximum standby pitch angle of 9.8 degrees nose up, and a spike in vertical acceleration of 1.65 gsee the traces at this moment ↗
- 13:38:12FDRLanding rollp.3Nose gear WOW status transitioned to ground and the aircraft decelerated using brakes, spoilers, and thrust reverserssee the traces at this moment ↗
FLIGHT DATA RECORDER - SPECIALIST'S FACTUAL REPORT · 8 events extracted by claude-sonnet-5
How the Board coded the sequence
- Landing-flare/touchdown: Abnormal runway contact→
- Landing-flare/touchdown: Tailstrike
Precedents
8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded- AIRBUS A320-232 · JETBLUE AIRWAYS CORPSacramento, CA
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Task performance › Use of equip/info
- BOEING 757 · Delta Air LinesRaleigh, NC
- ●Personnel issues › Action/decision › Action
Tailstrike - AIRBUS 321 · U.A Airways IncLas Vegas, NV
- ●Personnel issues › Action/decision › Action
Tailstrike - BEECH 1900C · ERA AVIATION INCHomer, AK
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Task performance › Use of equip/info
- EMBRAER EMB145 · TRANS STATES AIRLINES INCSt Louis, MO
- ●Personnel issues › Action/decision › Action
Abnormal runway contact - BOEING 767 36N · OMNI AIR INTERNATIONAL INCKabul, AF
- ●Personnel issues › Task performance › Use of equip/info
Abnormal runway contactTailstrike - BOEING 767 34AF · UNITED PARCEL SERVICE COAlbuquerque, NM
- ●Personnel issues › Action/decision › Action
- ●Personnel issues › Task performance › Use of equip/info
Tailstrike - BOEING 737-924ER · UNITED AIRLINES INCLas Vegas, NV
- ●Personnel issues › Task performance › Use of equip/info
Tailstrike
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
- 6 of 8Personnel issues › Action/decision › Actioncited here too
- 5 of 8Personnel issues › Task performance › Use of equip/infocited here too
- 2 of 8Personnel issues › Action/decision › Info processing/decision
Occurrences it coded
- 5 of 8Tailstrike
- 2 of 8Abnormal runway contact
Set against the Board’s own findings for this case
Cited here, and common in the precedents
- Action/decision › Action
- Task performance › Use of equip/info
Cited here, not seen in the precedents
- —
Common in the precedents, not cited here
- Action/decision › Info processing/decision
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
- 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.
- DCA17LA1222017-05-21 · BOEING 757 · Delta Air Lines
the first officer's failure to attain a proper landing flare, which resulted in a tail strike.
- DCA13FA0712013-04-05 · AIRBUS 321 · U.A Airways Inc
the captain's improper recovery from a bounced landing which resulted in a tailstrike.
- DCA14FA0022013-10-23 · BEECH 1900C · ERA AVIATION INC
The first officer inadvertently selecting the landing gear handle up after touchdown during the landing rollout. Contributing to the accident was the first officer's decision to reconfigure the airplane while still on the active runway.
- DCA16LA1002016-02-24 · EMBRAER EMB145 · TRANS STATES AIRLINES INC
the flight crews' failure to consider all available runways for landing to minimize the gusty crosswind component. Contributing to the accident was the captain's reduction of the engine thrust for about 1 second at low altitude immediately after the first officer applied maximum thrust to conduct a go-around.
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).