FlarePath
Cases › DCA11FA035 › The analyst

AIRBUS F4-622RUnited Parcel Service Company

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.

5
timed facts
8
precedents
18
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

5 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. 19:45:00 MDTFDRtakeoffp.3
    Start of plotted flight data (figures 1-3 cover 19:45:00 to 20:35:00 MDT)
  2. 20:24:41-20:24:46 MDTFDRlandingp.3
    Vertical acceleration oscillated between 0.5 g and 1.5 g during the attempted landing
  3. 20:24:42.04-20:24:42.54 MDTFDRlandingp.3
    Right main gear weight-on-wheels transitioned from Air to Ground and back to Air; pitch about 6.68 degrees, computed airspeed about 128.5 knots, ground speed about 139 knots
  4. 20:24:43.79-20:24:46.29 MDTFDRgo-aroundp.3
    Left main gear WOW transitioned Air to Ground and back to Air; the right gear WOW did the same between 20:24:44.31 and 20:24:45.79 (bounced landing / go-around with tail strike)
  5. 20:33:54 MDTFDRlandingp.3
    Nose gear WOW transitioned from Air to Ground and remained Ground for the rest of the recording (landing after the go-around, about 9 minutes 8 seconds later)
Flight Data Recorder 10 - Specialist's Factual Report · 5 events extracted by claude-fable-5-1 (in-session)
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
  • DCA13FA1312013-07-22substantialmatch 63
    BOEING 737 7H4 · SOUTHWEST AIRLINES CO
    Flushing, NY
    • ●Personnel issues › Task performance › Use of equip/info
    Hard landing
  • DCA25LA0152024-10-29substantialmatch 62
    AIRBUS A300 F4-622R · United Parcel Service Co
    Louisville, KY
    • ●Personnel issues › Task performance › Use of equip/info
  • DCA14FA1222014-06-20substantialmatch 60
    BOEING 767 36N · OMNI AIR INTERNATIONAL INC
    Kabul, AF
    • ●Personnel issues › Task performance › Use of equip/info
  • DCA23LA2782023-05-05substantialmatch 59
    AIRBUS A321-231 · AMERICAN AIRLINES INC
    Charlotte, NC
    • ●Personnel issues › Task performance › Use of equip/info
  • DCA09FA0472009-05-04substantialmatch 56
    AIRBUS A320 · NORTHWEST AIRLINES INC
    Denver, CO
    • ●Personnel issues › Task performance › Use of equip/info
  • DCA23LA1722022-12-19no fatalitiesmatch 53
    BOEING 777 · UNITED AIRLINES INC
    Kahului, HI
    • ●Personnel issues › Task performance › Use of equip/info
  • ANC19LA0452019-08-01substantialmatch 50
    DOUGLAS C 118A · Tatonduk Outfitters Limited
    Buckland, AK
    • ●Personnel issues › Task performance › Use of equip/info
  • DCA16CA1132016-03-05substantialmatch 50
    BOEING 767 34AF · UNITED PARCEL SERVICE CO
    Albuquerque, NM
    • ●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 cause
Findings the Board cited in those cases
Occurrences it coded
  • 5 of 8Tailstrike
  • 2 of 8Landing gear collapse
Set against the Board’s own findings for this case
Cited here, and common in the precedents
  • 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
  • Action/decision › Action
  • 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
  • DCA13FA1312013-07-22 · BOEING 737 7H4 · SOUTHWEST AIRLINES CO
    The captain's attempt to recover from an unstabilized approach by transferring airplane control at low altitude instead of performing a go-around. Contributing to the accident was the captain's failure to comply with standard operating procedures.
  • 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.
  • DCA14FA1222014-06-20 · BOEING 767 36N · OMNI AIR INTERNATIONAL INC
    the early reduction of engine thrust that resulted in an excessive sink rate and nose high pitch attitude during the landing flare. Contributing to the accident was a significant change in the vertical and horizontal wind components just prior to touchdown.
  • 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.

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