FlarePath
Cases › DCA14FA122 › The analyst

BOEING 767 36NOMNI AIR INTERNATIONAL 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.

0
timed facts
8
precedents
16
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

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 report

No timed facts: this docket has no extracted recorder sequence and no transcript.

Recorder events without a clock time
  • approachAccident approach to runway 29 at Kabul began at approximately 9,600 ft pressure altitude; Kabul airport elevation approximately 5,900 ft MSL
  • about 3 seconds before touchdownTAWS generated a Mode 1 'Sink Rate' alert
  • touchdown, about 1937 local (1507 UTC)Tail strike during landing on runway 29; maximum pitch during landing approximately 9.5 degrees, maximum vertical acceleration approximately 2.5 g, touchdown at approximately 140 knots computed airspeed; aircraft substantially damaged, 4 of 16 crew with minor injuries
Flight Data Recorder - Specialist's Factual Report · 3 events extracted by claude-fable-5-1 (in-session)
How the Board coded the sequence
  1. Landing-flare/touchdown: Tailstrike→
  2. Landing-flare/touchdown: Abnormal runway contact

Precedents

8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded
  • DCA26LA1392026-02-26no fatalitiesmatch 70
    BOMBARDIER INC CL-600-2C10 · Endeavor Airlines
    College Park, GA
    • ●Environmental issues › Conditions/weather/phenomena › Wind
    • ●Personnel issues › Task performance › Use of equip/info
    Abnormal runway contact
  • DCA25LA2512025-07-02substantialmatch 66
    BOEING 737-924ER · UNITED AIRLINES INC
    Las Vegas, NV
    • ●Personnel issues › Task performance › Use of equip/info
    Tailstrike
  • DCA19LA1932019-08-08substantialmatch 63
    Airbus A321 · Frontier Airlines
    Orlando, FL
    • ●Environmental issues › Conditions/weather/phenomena › Wind
    Tailstrike
  • DCA23LA2782023-05-05substantialmatch 61
    AIRBUS A321-231 · AMERICAN AIRLINES INC
    Charlotte, NC
    • ●Personnel issues › Task performance › Use of equip/info
    Tailstrike
  • DCA25LA0152024-10-29substantialmatch 61
    AIRBUS A300 F4-622R · United Parcel Service Co
    Louisville, KY
    • ●Personnel issues › Task performance › Use of equip/info
    Tailstrike
  • WPR18MA0872018-02-115 fatalmatch 61
    EUROCOPTER EC130 · Papillon Airways, Inc.
    Peach Springs, AZ
    • ●Environmental issues › Conditions/weather/phenomena › Wind
    • ●Personnel issues › Task performance › Use of equip/info
  • DCA23LA2212023-03-22substantialmatch 60
    AIRBUS A320-232 · UNITED AIRLINES INC
    Houston, TX
    • ●Personnel issues › Task performance › Use of equip/info
    Tailstrike
  • ANC23FA0422023-06-162 fatalmatch 60
    CESSNA 180 · JAMES B. TWETO
    Shaktoolik, AK
    • ●Environmental issues › Conditions/weather/phenomena › Wind
    • ●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
Set against the Board’s own findings for this case
Cited here, and common in the precedents
  • Conditions/weather/phenomena › Wind
  • 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

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
  • DCA26LA1392026-02-26 · BOMBARDIER INC CL-600-2C10 · Endeavor Airlines
    The captain’s inadequate compensation for gusting crosswind wind conditions while attempting to land and a subsequent go-around.
  • DCA25LA2512025-07-02 · BOEING 737-924ER · UNITED AIRLINES INC
    The first officer’s failure to maintain proper pitch attitude during flare which resulted in a bounced landing and a tailstrike.
  • DCA19LA1932019-08-08 · Airbus A321 · Frontier Airlines
    Encountering gusty conditions at a low altitude during landing and the crew’s decision to do a go-around at a low altitude with an excessive rotation rate.
  • 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.
  • 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.

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