Cases › DCA25LA251 › The analyst
BOEING 737-924ERUNITED AIRLINES 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.
7
timed facts
8
precedents
21
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
7 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- 00:21:52.3 PDTFDRLandingp.5Left and right main landing gear weight on wheels transitioned from air to groundsee the traces at this moment ↗
- 00:21:52.3 to 00:21:55.5 PDTFDRLandingp.5Left and right main landing gear weight on wheels transitioned from air to ground, to air, back to ground, and remained ground for the rest of the data; computed airspeed decreased from about 146 kts to about 141 kts and ground speed decreased from about 157 kts to 153 ktssee the traces at this moment ↗
- 00:21:55.4 PDTFDRLandingp.5Maximum vertical acceleration recorded at 2.40 gsee the traces at this moment ↗
- 00:21:55.5 PDTFDRLandingp.5Maximum pitch angle recorded at 8.26 degreessee the traces at this moment ↗
- 00:21:59.5 PDTFDRLanding rolloutp.5Nose landing gear weight on wheels transitioned from air to ground; computed airspeed decreased to about 126 kts and ground speed decreased to about 136 ktssee the traces at this moment ↗
- 00:22:22 PDTFDRTaxip.5Aircraft began a right turn and began taxiingsee the traces at this moment ↗
- 00:28:29 PDTFDRTaxip.5Data ended while the ground speed was 3 ktssee the traces at this moment ↗
FLIGHT DATA RECORDER SPECIALIST'S FACTUAL REPORT · 7 events extracted by claude-sonnet-5
How the Board coded the sequence
- 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 · UNITED AIRLINES INCHouston, TX
- ●Aircraft › Aircraft oper/perf/capability › Performance/control parameters
- ●Personnel issues › Task performance › Use of equip/info
Tailstrike - AIRBUS A300 F4-622R · United Parcel Service CoLouisville, KY
- ●Aircraft › Aircraft oper/perf/capability › Performance/control parameters
- ●Personnel issues › Task performance › Use of equip/info
Tailstrike - AIRBUS A321-231 · AMERICAN AIRLINES INCCharlotte, NC
- ●Aircraft › Aircraft oper/perf/capability › Performance/control parameters
- ●Personnel issues › Task performance › Use of equip/info
Tailstrike - AIRBUS A320 · NORTHWEST AIRLINES INCDenver, CO
- ●Aircraft › Aircraft oper/perf/capability › Performance/control parameters
- ●Personnel issues › Task performance › Use of equip/info
Tailstrike - BOEING 757-251 · DELTA AIR LINES INCAtlanta, GA
- ●Aircraft › Aircraft oper/perf/capability › Performance/control parameters
- ●Personnel issues › Task performance › Use of equip/info
Tailstrike - Boeing 757 · American AirlinesLas Vegas, NV
- ●Personnel issues › Task performance › Use of equip/info
Tailstrike - DOUGLAS C 118A · Tatonduk Outfitters LimitedBuckland, AK
- ●Aircraft › Aircraft oper/perf/capability › Performance/control parameters
- ●Personnel issues › Task performance › Use of equip/info
- Convair 440 · Ferreteria E Implementos San FranciscoMonclova, OH
- ●Aircraft › Aircraft oper/perf/capability › Performance/control parameters
- ●Personnel issues › Task performance › Use of equip/info
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 › Task performance › Use of equip/infocited here too
- 7 of 8Aircraft › Aircraft oper/perf/capability › Performance/control parameterscited here too
Occurrences it coded
- 6 of 8Tailstrike
Set against the Board’s own findings for this case
Cited here, and common in the precedents
- Aircraft oper/perf/capability › Performance/control parameters
- Task performance › Use of equip/info
Cited here, not seen in the precedents
- —
Common in the precedents, not cited here
- —
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
- DCA23LA2212023-03-22 · AIRBUS A320-232 · UNITED AIRLINES INC
The first officer's failure to maintain the correct airspeed and pitch attitude during landing which resulted in a tailstrike.
- DCA25LA0152024-10-29 · AIRBUS A300 F4-622R · United Parcel Service Co
The pilot’s incorrect pitch attitude during a bounced landing which resulted in a tailstrike.
- DCA23LA2782023-05-05 · AIRBUS A321-231 · AMERICAN AIRLINES INC
The captain’s failure to maintain the appropriate airspeed and pitch attitude during landing which resulted in a tailstrike.
- DCA09FA0472009-05-04 · AIRBUS A320 · NORTHWEST AIRLINES INC
The first officer’s excessive pitch-up of the airplane while landing with a tailwind, which resulted in a tailstrike following a bounced landing. Contributing to the bounced landing were a high descent rate and excessive thrust resulting from the first officer’s delay in retarding the thrust levers to idle, thereby providing residual thrust and preventing spoiler deployment.
- DCA22LA1782022-08-07 · BOEING 757-251 · DELTA AIR LINES INC
The overpitch control of the airplane during landing resulting in a tail strike.
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).