# NTSB IAD99LA053: Piper PA-28-235, N235TL, Zanesville, OH, July 18, 1999 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 18, 1999, 15:00 local (19:00 UTC) - Place: Zanesville, OH - Coordinates: 39.94947, -82.009529 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.9495&lon=-82.0095&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 4 uninjured - Status: Completed, report June 21, 2000 - Report: Approved by Office Director - NTSB case key (mKey): 46939 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD99LA053 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/46939/pdf - Page: https://openairdocs.org/ntsb/IAD99LA053 ## Probable cause The pilot not maintaining a proper descent rate and an inadequate flare. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Hard landing, landing - flare/touchdown - proper descent rate - not maintained, pilot in command - flare - inadequate, pilot in command ## Analysis The pilot added power to clear the trees at the approach end of the runway and, once past the trees, reduced power and attempted the landing flare. The pilot reported the control surfaces were ineffective, the airplane fell straight down, and struck the runway 'extremely hard.' According to the pilot, 'The accident was caused by approaching the runway too slowly, combined with a high density altitude resulting from extremely high temperatures.' ## Factual narrative On July 18, 1999, at 1500 eastern daylight time, a Piper PA-28-235, N235TL, was substantially damaged during a hard landing at the Parr Airport (42I), Zanesville, Ohio. The certificated private pilot and three passengers were not injured. Visual meteorological conditions prevailed for the local personal flight that originated at Dayton, Ohio, approximately 1410. No flight plan was filed for the flight conducted under 14 CFR Part 91. In a telephone interview, the pilot reported the purpose of the flight was to return to his home airport in Zanesville. He said he listened to a traffic advisory and entered the traffic pattern for landing on runway 28. The pilot said there were trees at the east end of the airport and that he had to adjust his approach angle to accommodate them whenever he landed on runway 28. He said: "When I turned base to final I started to drop. I put the power back in and crawled over the trees. I didn't check my airspeed so when I pulled the power back and flared, nothing worked. I pulled back and there was nothing there. The airplane struck the ground about 30 degrees nose down. The nose gear and the prop hit the ground." The pilot said the landing was hard but that he was able to taxi clear of the runway. He further stated that he took his two children to the hospital for examination, but they were not injured. The owner/manager of the airport was at the east end of the airport as the airplane approached for landing. He said: "He was a little shallow...on final. Then he put the power on. Then he reduced power after he cleared the trees. When he began his flare the airplane fell right on through. The airplane sounded good until it hit, then it went 'bing, bing, bing.' I guess that was when the prop hit." The airport manager's son, a flight instructor, witnessed the approach from the airport office. He said: "He was slow coming in over the trees. I got up to grab the microphone, to tell him to add power, but it was too late. He fell in from about 25 feet. Flat." In a written statement, the pilot said, "In my opinion, the accident was caused by approaching the runway too slowly combined with high density altitude resulting from extremely high temperatures." The pilot said he had approximately 112 hours of total flight experience, 58 hours of which were in make and model. When questioned about the performance of the airplane, he said, "The airplane was performing fine. I went from a [Cessna] 150 that kind of floats, to this, which is a heavy airplane, that you kind of have to power onto the runway. The accident was simply not having the plane fast enough." The winds reported at Zanesville at the time of the accident were from 260 degrees at 9 knots. ## Aircraft - Registration: [N235TL](https://openairdocs.org/aircraft/N235TL), registered now, S/N 28-10769 (OpenAirDocs) - Reported make and model: Piper PA-28-235 - Registry model: [Piper PA-28-235](https://openairdocs.org/model/piper-pa-28-235) (registry code 7102810) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-10769 - Airframe hours: 2682 - Engines: Lycoming O-540-B4B5 235 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Thomas A. Lewis - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 21, 1998, 52 hours before - Departed: I19, DAYTON, OH - Destination: 42I - Airport: 42I, Parr Airport, runway 28, 2,600 × 26 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 51; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 112 total, 57 in this make and model, 24 in the last 90 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 260° at 9 knots - Visibility: 7 statute miles - Lowest ceiling: 9,000 ft broken - Temperature: 90 °F, dew point 66 °F - Altimeter: 30.00 inHg - Observed at: ZZV, 7 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 (OpenAirDocs). - [Accident 19990718009269A](https://openairdocs.org/incident/19990718009269A), Jul 18, 1999: Piper PA28235, Zanesville, OH, Substantial damage. Low airspeed, density altitude problem. Hard landing on runway. (-23)aircraft landing on runway 28, tree's on approach end of runway required short field… 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. --- 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.