# Accident 19991121031819A: Cessna R172K, Philippi, WV, November 21, 1999 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: November 21, 1999, 14:30 local time - Place: Philippi, WV - Airport: Philippi/Barber County Regnl - Damage: Substantial damage - Phase of flight: Level Off Touchdown - Operating rules: General operating rules (Part 91) - Location: 39.1502° N, 80.0400° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=39.1502&lon=-80.0400&mi=10 - Aircraft: N758LR, registered now (https://openairdocs.org/aircraft/N758LR) (OpenAirDocs) - Registry model: Cessna R172K (registry code 2072431, https://openairdocs.org/model/cessna-r172k) (OpenAirDocs) - Registry engine: Continental IO-360 series (registry code 17025, https://openairdocs.org/engine/continental-io-360-series) (OpenAirDocs) - Reported make and model: CESSNA R172K - Reported engine: CONT IO360KB - People aboard: 1 - Fatal injuries: 0 - Pilot flight hours: 143 total, 7 in this make and model, 40 in the last 90 days - NTSB investigation: [NTSB IAD00LA007](https://openairdocs.org/ntsb/IAD00LA007) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/19991121031819A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (.19) 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. (.4)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.' (-23)PILOT STATED THAT LANDING ON RUNWAY 26 AT (79D) BARBOUR COUNTY AIRPORT HE FLET A SLIGHT BIND IN THE YOKE CONTROLS UPON TRYING TO FLARE FOR LANDING. HE THEN PULLED THE CONTROLS BACK FOR THE LANDING AND REALIZED HE WAS TOO HIGH. THE AIRCRAFT THEN BOUNCED UPON LANDING AND HE TRIED TO RECOVER WHEN THE AIRCRAFT HIT NOSE FIRST UPON THE RUNWAY. HE WAS ABLE TO TAXI THE AI RCRAFT HANGER AND THEN UPON INVESTIGATION HE SAW DAMAGE TO THE ONE PROP BLADE AND THE LOWER FIREWALL AREA AND ALSO TH LOWER FUSELAGE WHERE THE ENGINE COWLING ATTACHES TO THE AICRAFT WAS SEVERELY BUCKLED. PLEASE NOTE: WHEN TRYING TO CHECK THE CONTROLS FOR BINDING, THEY COUNLD NOT BE MOVED DUE TO THE DAMAGE IN THE TUNNEL AREA. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB IAD00LA007](https://openairdocs.org/ntsb/IAD00LA007), Nov 21, 1999: Cessna 172XP (N758LR), Phillipi, WV, substantial damage. Probable cause: The pilot's improper flare that resulted in a hard landing. From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.