IAD00LA007

NTSB accident investigation · Cessna 172XP · Phillipi, WV · November 21, 1999

Accident · No injuriesLimited investigationFinal report
Date
November 21, 1999, 14:30 local (19:30 UTC)
Place
Phillipi, WV
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N758LRCessna 172XP
Weather
Visual (VMC) · Day
Status
Completed · report April 18, 2001
Report
Approved by Office Director
FAA report
19991121031819A
Case key
47801

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 pilot's improper flare that resulted in a hard landing.

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/touchdown
Flare - improperPilot in commandCause

Analysis

The pilot said he entered the traffic pattern, performed his base and final turns, and configured the airplane for landing. The pilot said that on short final, he began his level off and flare prematurely. He said, 'I just ballooned high and had a hard landing. That's all there is to it.'

Factual narrative

On November 21, 1999, at 1430 eastern standard time, a Cessna 172XP, N758LR, was substantially damaged during a hard landing to the Phillipi/Barbour County Airport (79D), Phillipi, West Virginia. The certificated private was not injured. Visual meteorological conditions prevailed for the personal flight that originated at Morgantown, West Virginia (MGW), approximately 1400. No flight plan was filed for the flight conducted under 14 CFR Part 91.

In a telephone interview, the pilot stated he flew to MGW, serviced the airplane with fuel, and returned to his home airport at Phillipi/Barbour County. He said he entered the traffic pattern for runway 26, performed his base and final turns, and configured the airplane for landing. The pilot said that on short final, he began his level off and flare prematurely. He said:

"I just ballooned high and had a hard landing. That's all there is to it."

In a telephone interview, a Federal Aviation Administration (FAA) Aviation Safety Inspector said the airplane sustained damage to the propeller, nose gear, and firewall. He said the flight control tunnels aft of the firewall were crushed and prevented the movement of the flight controls.

When questioned about the performance of the airplane, the pilot said, "It was performing very well. No problems."

The pilot purchased the airplane November 6, 1999. An annual inspection was performed on the airplane prior to its purchase on October 5, 1999.

The pilot reported 143 hours of flight experience, of which 7 hours were in the Cessna 172.

Winds reported at Clarksburg, West Virginia, 10 miles northwest of 79D, were from 240 degrees at 7 knots.

Aircraft

Registration
N758LR
Reported as
Cessna 172XP
Category
Airplane
Serial number
R1723185
Airframe hours
1,830
Engine
Continental IO-360-KB, 195 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Michael T. Johnson
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
Annual · October 5, 1999 · 12 hours before
Departed
MGW · Morgantown, WV
Destination
79D
Airport
79D · Phillipi/Barbour Airport, runway 26, 3,200 × 50 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
44
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Valid Medical--no waivers/lim.
Seat
Left
Flight hours
143 total · 7 in this make and model · 112 as pilot in command · 40 in the last 90 days · 12 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
240° at 7 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
68 °F, dew point 54 °F
Altimeter
30.00 inHg
Observed at
CKB, 10 nm away

FAA reports on this event · 1

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