FlarePathAir-accident investigation intelligence
Investigation brief · generated 2026-10-09 · source: NTSB public docket and accident database

BOEING DC-10 — Baltimore, MD, USA, 2009-05-06

NTSB number
DCA09FA048
Operator
World Airways
Registration
N139WA
Highest injury
Serious injury
Regulation
Part 121
Damage
Substantial
Cohort
Part 121 airline
Recorder data
Tier 1 — decoded recorder tables
Every sentence below is taken directly from NTSB records — the accident database, the docket's recorder reports and the Board's findings — with its source noted. Nothing is paraphrased or inferred.

NTSB summary

The flight was conducting a straight-in approach during visual meteorological conditions. The approach was backed up by an ILS and was stable at 500 feet above touchdown. The initial touchdown was firm and main landing gear rebounded, possibly bouncing slightly off the runway. Control column input and possibly momentum from the touchdown resulted in a rapid pitch down and hard nose gear impact with the runway. Wing spoilers likely did not deploy due to the main gear bounce and/or throttle position. Following the nose gear impact, the airplane pitched up as expected and the column was held in a slightly forward position. Airspeed rapidly decayed, and engine power began to increase as the airplane pitch reversed to a downward motion for a second time. One of the crew, likely the FO, called “flare flare” and the column recorded a rapid nose up input, followed by a rapid nose down input, and the nose gear again struck the runway very hard, likely causing the majority of the damage at that point. Following the second nose gear impact, column inputs stabilized at a slightly nose up command, power was set on all three engines, and the go-around was successfully executed. A slight lag in the power increase on engine number 3 may have contributed to the nose down motion leading to the second nose gear impact, although the large forward (airplane nose down) column movement appears to be a much more significant contributor. It is unclear why the engine was slower to increase. Throttle lever angle was not recorded, but the engine operated as expected for all other phases of the flight, including after the impact, therefore it is possible the pilot did not advance the number 3 throttle concurrently with the others. The captain’s flight and duty schedule complied with Federal Aviation regulations, but he experienced a demanding 10-day trip schedule prior to the incident involving multiple time zone crossings and several long duty periods, and reported difficulties sleeping prior to the accident leg. The captain was likely further affected by a digestive system upset during the accident flight. It is likely that the captain’s performance was degraded by fatigue and some degree of physical discomfort brought on by a short-term illness. The captain had recently completed upgrade training to DC-10, having previously been flying as an MD-11 first officer. The training program was fragmented over approximately ten months, and while in accordance with FAA regulations, may have adversely affected his consolidation of skills and experience.
Verbatim, NTSB aviation accident database (narratives.narr_accf).

Probable cause

the captain’s inappropriate control inputs following a firm landing, resulting in two hard nose-gear impacts before executing a go-around. Contributing to the inappropriate control inputs was the captain’s fatigue and physical discomfort; and a possible lack of practical consolidation of skills and experience due to a protracted and fragmented training period.
Verbatim, NTSB determination.

Flight data recorder

— 51,492 samples, 42 parameters, 12:36:02.0 to 12:58:20.0.

ParameterMaxatMinatFinalat
Computed airspeed kts250.812:36:02.30.012:57:48.30.012:58:19.3
Pitch attitude deg171.612:58:05.8-180.012:47:57.8-172.012:58:19.8
Roll attitude deg170.712:48:44.2-180.012:48:10.2-129.912:58:19.2
Vertical acceleration g3.312:45:07.90.312:45:03.11.012:58:19.9
Magnetic heading deg359.612:48:25.00.512:48:24.012.812:58:19.0
Computed from the docket's tabular attachment; times as recorded (local or SRN as published).

Sequence of events (FDR factual report)

TimeEventPage
12:45:00 EDTInitial touchdown at about 6 degrees nose up (time correlated to an airport security camera); vertical acceleration about 1.6 g; the control column then commanded nose down and the aircraft rotated nose down5
about 12:45:02 EDTControl column began commanding nose up5
about 12:45:03 EDTSecond ground contact: column at a local maximum of 8 degrees aft while pitch reached about 2 degrees nose down; vertical acceleration about 3.0 g; first data dropout5
12:45:03-12:45:05 EDTPitch rebounded to about 10 degrees nose up while the column commanded nose down to about 7-8 degrees forward5
about 12:45:05 EDTNose began dropping; column returned toward neutral without commanding nose up until just before the third contact5
about 12:45:07 EDTThird ground contact at about 1 degree nose down; vertical acceleration about 3.4 g5
about 12:45:08 EDTSecond and third data dropouts; pitch, roll and heading became invalid for the rest of the flight4
laterGo-around and landing on runway 33L (plots 3 and 4, without attitude parameters)5
Extracted by claude-fable-5-1 (in-session); 8 of 8 stated events verified against the raw recorder data.

Cockpit voice recorder

603 transcribed utterances from 12:00:23 to 14:01:26, 26 sources. Final entries:

14:00:26CAM-3maybe you should get up and stretch out a little bit ya know.
14:00:43CAM-3I couldn't get that bathroom door open man. it took two of us.
14:01:07CAM-3I think she did herself in this time.
14:01:25CAM-1did you pull that?
14:01:26CAM-3aw #. no I never did.
The NTSB cautions that a CVR transcript is not a precise science and should not be used as the sole source of information.

Recorder documents in the docket

GroupTitlePagesType
fdrFlight Data Recorder 10 - Specialist's Factual Report9pdf
fdrFlight Data Recorder 10 - Attachment 1 - Tabular FDR Datacsv
cvrCockpit Voice Recorder 12 - Factual Report of Group Chairman53pdf
performanceAircraft Performance 13 - Boeing Study6pdf

Docket: data.ntsb.gov/Docket/?NTSBNumber=DCA09FA048. This brief is an analytical aid assembled from public records; it is not an investigative finding.