AIRBUS 320United Airlines
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.
Ask the docket
passages, not paraphrasesEvery 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
0 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 reportNo timed facts: this docket has no extracted recorder sequence and no transcript.
- about 3 minutes before touchdownStart of plots; after completing a left turn the aircraft straightened on the runway heading with flaps and slats deployed
- touchdownBoth main gear touched down at the same moment, accompanied by two vertical acceleration spikes about two seconds apart (tail strike)
- about 15 seconds after main gear touchdownNose gear touched down
- landingThe copilot's sidestick was being operated at the time of the incident; the pilot's was not
- 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 321 · U.A Airways IncLas Vegas, NV
- ●Personnel issues › Action/decision › Action
Tailstrike - BOEING 757 · United AirlinesSan Diego, CA
- ●Personnel issues › Action/decision › Action
Tailstrike - BOEING 737 · UNITED AIRLINES INCHouston, TX
- ●Personnel issues › Action/decision › Action
Tailstrike - BOEING 757-224 · United Airlines Inc.Newark, NJ
- ●Personnel issues › Action/decision › Action
Tailstrike - BOEING 737 · SOUTHWEST AIRLINES COLas Vegas, NV
- ●Personnel issues › Action/decision › Action
Tailstrike - BOEING 757-232 · DELTA AIR LINES INCAtlanta, GA
- ●Personnel issues › Action/decision › Action
Tailstrike - BOEING 757 · Delta Air LinesRaleigh, NC
- ●Personnel issues › Action/decision › Action
Tailstrike - Airbus A321 · Frontier AirlinesOrlando, FL
- ●Personnel issues › Action/decision › Action
Tailstrike
What the record says
a pattern, not a findingacross the 8 closest cases · 8 carry coded findings · 8 have a probable cause- 8 of 8Personnel issues › Action/decision › Actioncited here too
- 8 of 8Tailstrike
- Action/decision › Action
- —
- —
A teaching device, not a verdict: what the record would have looked at, next to what the Board found.
- DCA13FA0712013-04-05 · AIRBUS 321 · U.A Airways Inc
the captain's improper recovery from a bounced landing which resulted in a tailstrike.
- DCA14LA1372014-07-30 · BOEING 757 · United Airlines
the first officer's failure to maintain the correct airspeed and pitch attitude during landing that resulted in a tailstrike.
- DCA24LA0652024-01-10 · BOEING 737 · UNITED AIRLINES INC
The airplane’s aft fuselage impacted the runway as a result of a delayed flare and subsequent nose-high pitch inputs during the aircraft’s multiple touchdowns.
- DCA22LA0022021-09-27 · BOEING 757-224 · United Airlines Inc.
The nose high attitude on landing resulted in a tailstrike.
- DCA14CA0342014-01-04 · BOEING 737 · SOUTHWEST AIRLINES CO
the captain's over rotation during the bounced landing.
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).