FlarePath
Cases › DCA19CA167 › The analyst

Boeing 757United 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.

10
timed facts
8
precedents
12
passages to ask

Ask the docket

passages, not paraphrases
Try

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

10 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
  1. 09:51 EDTFDRDeparturep.3
    Aircraft departed Denver
    see the traces at this moment ↗
  2. 12:52 EDTFDRApproachp.3
    Aircraft descended to a pressure altitude of about 2,500 feet and made a turn to the runway heading
    see the traces at this moment ↗
  3. 12:54:54 EDTFDRFinal Approachp.3
    Aircraft on final approach for runway 22L at EWR with the autopilot off, glideslope mode engaged, and both captain and first officer flight directors on
    see the traces at this moment ↗
  4. 12:55:14 EDTFDRLandingp.3
    First indication the main landing gear (MLG) had touched down on the runway
    see the traces at this moment ↗
  5. 12:55:16 EDTFDRLandingp.4
    Variations in the vertical acceleration, pitch, elevator, and control column parameters increased in magnitude
    see the traces at this moment ↗
  6. 12:55:17 EDTFDRLandingp.3
    MLG weight-on-wheels parameter indicated "Air" again for one second before going back to "Ground" one second later
    see the traces at this moment ↗
  7. 12:55:19 EDTFDRLandingp.3
    MLG weight-on-wheels parameter indicated "Air" again for one second before finally indicating "Ground" one second later
    see the traces at this moment ↗
  8. 12:55:20 EDTFDRLandingp.3
    Nose gear weight-on-wheels indicated "Ground" for the first time; largest magnitude vertical acceleration of 1.6042 g's occurred
    see the traces at this moment ↗
  9. 12:55:20 EDTFDRLanding rolloutp.3
    Both left and right engine thrust reversers indicated deployed six seconds after initial MLG touchdown
    see the traces at this moment ↗
  10. 12:55:21 EDTFDRLanding rolloutp.4
    Recording ended, seven seconds after the initial recorded indication of touchdown on the MLG
    see the traces at this moment ↗
FLIGHT DATA RECORDER - SPECIALISTA��S FACTUAL REPORT · 10 events extracted by claude-sonnet-5
How the Board coded the sequence
  1. Landing-flare/touchdown: Hard landing

Precedents

8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded
  • DCA24LA0652024-01-10substantialmatch 79
    BOEING 737 · UNITED AIRLINES INC
    Houston, TX
    • ●Personnel issues › Action/decision › Action
  • DCA14LA1372014-07-30substantialmatch 77
    BOEING 757 · United Airlines
    San Diego, CA
    • ●Personnel issues › Action/decision › Action
  • DCA18CA2662018-07-31substantialmatch 77
    Boeing 757 · American Airlines
    Philadelphia, PA
    • ●Personnel issues › Action/decision › Action
  • DCA19CA1862019-07-23substantialmatch 77
    Boeing 757 · United Airlines
    San Francisco, CA
    • ●Personnel issues › Action/decision › Action
  • DCA22LA0022021-09-27substantialmatch 75
    BOEING 757-224 · United Airlines Inc.
    Newark, NJ
    • ●Personnel issues › Action/decision › Action
  • DCA25LA2302025-06-08no fatalitiesmatch 75
    BOEING 737 · United Airlines
    Phoenix, AZ
    • ●Personnel issues › Action/decision › Action
  • DCA14CA0342014-01-04substantialmatch 74
    BOEING 737 · SOUTHWEST AIRLINES CO
    Las Vegas, NV
    • ●Personnel issues › Action/decision › Action
  • DCA17CA1952017-09-12no fatalitiesmatch 74
    BOEING 737-924ER · United Airlines
    Los Angeles, CA
    • ●Personnel issues › Action/decision › Action

What the record says

a pattern, not a findingacross the 8 closest cases · 8 carry coded findings · 8 have a probable cause
Findings the Board cited in those cases
Occurrences it coded
  • 5 of 8Tailstrike
Set against the Board’s own findings for this case
Cited here, and common in the precedents
  • Action/decision › Action
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
  • 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.
  • 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.
  • DCA18CA2662018-07-31 · Boeing 757 · American Airlines
    The captain's improper control of the airplane during the landing flare.  
  • DCA19CA1862019-07-23 · Boeing 757 · United Airlines
    failure of the ground crew to maintain clearance from the parked airplane during pushback.
  • DCA22LA0022021-09-27 · BOEING 757-224 · United Airlines Inc.
    The nose high attitude on landing resulted in a tailstrike.

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).