FlarePath
Cases › DCA17LA122 · Part 121 airline

BOEING 757Delta Air Lines

Raleigh, NC, USA · 2017-05-21·N633DL

0
fatal
0
serious
No injury
highest injury
Substantial
damage

What happened

NTSB summary, verbatim

The crew of the Part 121 scheduled passenger flight reported that the landing approach at the destination was stable. The first officer, who was the pilot flying, stated that the airplane was slightly high and fast when he began the landing flare and he pushed the nose down to correct. He then determined that he had overcorrected and began to recover by pulling the control column aft when the airplane landed firmly on the main landing gear and the aft fuselage impacted the runway. Postflight inspection revealed an area of abrasion damage to the aft fuselage and the underlying stringers and frames and damage to the aft pressure bulkhead.

Photographs

1the aircraft, and what the investigators found
The aircraft before the accident
Delta N633DL Boeing 757-200 (15327945456)
formulanone from Huntsville, United States · CC BY-SA 2.0 · Wikimedia Commons

Probable cause

the Board's determination
the first officer's failure to attain a proper landing flare, which resulted in a tail strike.

Occurrence sequence

1 stepsNTSB coding · CICTT taxonomy
  1. 1 · Landing-flare/touchdown
    Tailstrike
    defining event

Findings

1 causal · 0 contributing
  • CAUSE
    Personnel issues › Action/decision › Action › Incorrect action sequence — Copilot

Sequence of events

9 timed eventsfrom the FDR factual report · claude-sonnet-5
  1. 20:24:10 EDTDeparturep.3
    the aircraft departed
  2. 20:53 EDTDescentp.3
    the aircraft began a descent out of flight level 270
  3. 21:03 EDTDescentp.3
    the aircraft began a descent out of flight level 230, with some intermediate, short duration level offs, including at 10,000 feet at about 21:08 EDT
  4. 21:17:46 EDTApproachp.3
    the computed airspeed was 140 knots, as the aircraft descended through 374 feet radio altitude
  5. 21:18:04 EDTApproachp.3
    the pitch began to increase, as the radio altitude decreased through 196 feet, and the computed airspeed began to decrease out of 141 knots
  6. 21:18:16 EDTTouchdownp.3
    the weight on wheels transitioned to ground, as the pitch angle increased through 8.1 degrees nose up, the computed airspeed fluctuated at about 120 knots, and the vertical g peaked at +1.66 g
  7. 21:18:18 EDTTouchdownp.3
    with weight on wheels still indicating ground, the pitch reached a maximum up angle of 11.4 degrees, the computed airspeed decreased through 121.5 knots, and the vertical g fluctuated between +1.5 and +0.7 g
  8. 21:18:23 EDTRolloutp.3
    the pitch decreased to a steady value of about 0.2 degrees nose up
  9. 21:18:52 EDTRolloutp.3
    the computed airspeed began to read a non-computed value (less than 40 knots)

NTSB analysis

from the final report

The crew of the Part 121 scheduled passenger flight reported that the landing approach at the destination was stable. The first officer, who was the pilot flying, stated that the airplane was slightly high and fast when he began the landing flare and he pushed the nose down to correct. He then determined that he had overcorrected and began to recover by pulling the control column aft when the airplane landed firmly on the main landing gear and the aft fuselage impacted the runway. Postflight inspection revealed an area of abrasion damage to the aft fuselage and the underlying stringers and frames and damage to the aft pressure bulkhead.