CHI02LA170

NTSB accident investigation · McDonnell Douglas DC-9-82 · Kansas City, MO · June 17, 2002

Accident · No injuriesLimited investigationFinal report
Date
June 16, 2002, 20:30 local (Jun 17, 2002, 01:30 UTC)
Place
Kansas City, MO
Injuries
123 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N140NJMcDonnell Douglas DC-9-82
Weather
Visual (VMC) · Day
Status
Completed · report November 25, 2003
Report
Approved by Office Director
Parties
Boeing Commercial Aircraft, Federal Aviation Adminstration, Vanguard Airlines
FAA report
20020616027499A
Case key
55006

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The inadequate flare by the flying pilot and the remedial action not performed by the company check airman.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Hard landingLanding
Flare - inadequatePilot in commandCause
Remedial action - not performedCheck pilotCause

Analysis

The airplane was discovered with substantial damage to its tailskid and adjacent structure during a postflight maintenance inspection. The flight served as captain initial operating experience for the first officer who was seated in the left seat. The captain and company check airman for the flight was seated in the right seat. A jump seat rider seated in the forward cabin stated that the airplane appeared to level off and start a flare a little high. A correction was then made to reduce the pitch attitude to continue the descent. There appeared to be a high sink rate, an additional pitch change was made resulting in a firm landing.

Factual narrative

On June 16, 2002, a McDonnell Douglas DC-9-82, N140NJ, operated by Vanguard Airlines as flight 313, was discovered to have substantial damage to its tailskid and adjacent structure during a postflight maintenance inspection. Flight 313 arrived at 2030 central daylight time and landed on runway 01L (10,801 feet by 150 feet, grooved concrete) at the Kansas City International Airport (MCI), Kansas City, Missouri. Visual meteorological conditions prevailed at the time of landing. The 14 CFR Part 121 passenger flight was operating on a flight plan. The 2 pilots, 3 flight attendants and 118 passengers reported no injuries. The flight departed from the Orlando International Airport, Orlando, Florida, en route to MCI.

The flight served as captain initial operating experience for the first officer who was seated in the left seat. The captain and company check airman for the flight was seated in the right seat.

The captain, who was the nonflying pilot, stated that they had been cleared for a visual approach to runway 01L. The first officer (FO) disengaged and the autopilot and the autothrottles remained engaged for the remainder of the flight. The reference landing speed (Vref) bug was set to 130 knots indicated airspeed (KIAS). At 1,000 feet above field elevation (AFE), the airplane was at 140 KIAS and half a dot below glide path. The first officer corrected to the glide path and at 500 feet AFE, the airplane was at 130 KIAS. At 100 feet above AFE, the captain made a call and checked outside to ensure that the airplane was aligned with the runway. He then brought his scan back inside and noticed the airspeed was just below Vref. He told the FO not to slow down any further. He rechecked runway alignment and then noticed the flight mode annunciator display had a blank left window, the throttles were already at idle and the auto throttle switch was in the engaged position while they were about 80 and 40 feet AFE. He decided that the engines would not be able to spool back up at this point and he shifted his attention back outside to gage the position of the airplane. He determined that the only action to take was to ensure that the nose of the airplane was not raised to cushion the landing. The airplane did not slow below Vref. The first officer said that he did not retard the throttles to idle manually.

A jump seat rider seated in the forward cabin stated that the airplane appeared to level off and start a flare a little high. A correction was then made to reduce the pitch attitude to continue the descent. There appeared to be a high sink rate, an additional pitch change was made resulting in a firm landing.

The Federal Aviation Administration, Boeing Commercial Aircraft, and Vanguard Airlines were parties to the investigation.

Aircraft

Registration
N140NJ
Reported as
McDonnell Douglas DC-9-82
Category
Airplane
Serial number
49931
Airframe hours
28,059.53
Engine
Pratt & Whitney JT8-219, 21,700 lbs thrust, turbo fan
Damage
Substantial damage
Flight
Part 121
Operator
Vanguard Airlines Inc.
Registered owner
Wells Fargo Bank Northwest NA Trustee
Airworthiness certificate
Standard, Transport
Last inspection
Continuous airworthiness · June 15, 2002 · 21.33 hours before
Departed
MCO · Orlando, FL
Destination
MCI
Flight plan
IFR
Airport
MCI · Kansas City International, runway 01, 10,801 × 150 ft, concrete

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Co-pilot
Age
36
Injuries
None
Certificates
Airline transport, Commercial
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 1, Valid Medical--w/ waivers/lim
Last flight review
May 22, 2002
Seat
Left
Flight hours
7,550 total · 6 in this make and model · 24 in the last 90 days
Role
Co-pilot
Age
48
Injuries
None
Certificates
Airline transport, Commercial
Airplane ratings
Multi-engine land
Instrument ratings
Airplane, Helicopter
Medical
Class 1
Last flight review
January 27, 2002
Seat
Right
Flight hours
10,000 total · 856 in this make and model

Weather

Conditions
Visual (VMC) · Day
Wind
60° at 6 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
73 °F, dew point 48 °F
Altimeter
29.96 inHg
Observed at
MCI

Docket · 9

The files NTSB released with the investigation on August 13, 2003, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.0 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.