# NTSB NYC99LA117: Piper PA-11, N78659, Leesburg, VA, May 21, 1999 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: May 21, 1999, 14:12 local (18:12 UTC) - Place: Leesburg, VA - Location: 39.0780° N, 77.5575° W: Placed by OpenAirDocs at LEESBURG EXEC (JYO), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=39.0780&lon=-77.5575&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report August 3, 2000 - Report: Approved by Office Director - NTSB case key (mKey): 46437 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC99LA117 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/46437/pdf - Page: https://openairdocs.org/ntsb/NYC99LA117 ## Probable cause The pilot-in-command's (CFI) failure to maintain control of the airplane. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - roll - aircraft control - not maintained, pilot in command(cfi) (cause) - On ground/water collision with object, landing - roll ## Analysis The certified flight instructor was introducing the commercial pilot to tailwheel operations. The commercial pilot had accomplished approximately six landings in the airplane. During the next landing, the pilots experienced a crosswind, followed by a tailwind. The airplane stalled, bounced, and traveled off the left side of the runway. The instructor stated that he took control of the airplane, prevented a ground loop, but was unable to keep the airplane on the runway. The airplane struck a runway sign, causing substantial damage to the empennage. ## Factual narrative On May 21, 1999, about 1412 Eastern Daylight Time, a Piper PA-11, N78659, was substantially damaged during a landing at Leesburg Municipal/Godfrey Field Airport (JYO), Leesburg, Virginia. The certificated flight instructor and commercial pilot were not injured. Visual meteorological condition prevailed for the flight that originated from York Airport, York, Pennsylvania. No flight plan was filed for the instructional flight conducted under 14 CFR Part 91. The instructor was introducing the commercial pilot to tailwheel operations, and the commercial pilot had accomplished approximately six landings in the airplane. The instructor stated that during the next landing, they experienced a sudden crosswind, followed by a tailwind. The airplane stalled, bounced, and traveled off the left side of the runway. The instructor further stated that he took control of the airplane, prevented a ground loop, but was unable to keep the airplane on the runway. The airplane struck a runway sign, causing substantial damage to the empennage. The commercial pilot stated "...upon touchdown, the plane veered sharply to the left, going onto the grass and hitting a sign with the horizontal stabilizer. There was a slight crosswind on final, touchdown was normal, then the wind appeared to shift to a tailwind." Examination of the wreckage by a Federal Aviation Administration Inspector did not reveal any pre-impact mechanical malfunctions, nor did the pilots report any. The approach was flown to Runway 35, a 5,500 foot long, 100 foot wide, asphalt runway. The reported winds at JYO, at 1400, were from 270 degrees at 5 knots. ## Aircraft - Registration: [N78659](https://openairdocs.org/aircraft/N78659), registered now, S/N 11-1420 (OpenAirDocs) - Reported make and model: Piper PA-11 - Registry model: [Piper PA-11](https://openairdocs.org/model/piper-pa-11) (registry code 7101102) (OpenAirDocs) - Registry engine: [Continental C90 series](https://openairdocs.org/engine/continental-c90-series) (registry code 17009, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 11-1420 - Airframe hours: 5227 - Engines: Continental C90-12F 95 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: David Pearce - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 25, 1998, 30 hours before - Departed: THV, YORK, PA - Destination: JYO - Airport: JYO, Leesburg Municipal, runway 35, 5,500 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 65; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: left; flight hours: 16,350 total, 2,500 in this make and model, 15,106 as pilot in command, 40 in the last 90 days, 30 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 270° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 48 °F - Altimeter: 30.00 inHg - Observed at: JYO ## 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 19990521028529A](https://openairdocs.org/incident/19990521028529A), May 21, 1999: Piper PA11, Leesburg, VA, Substantial damage. (-23) While landing with a crosswind on runway 35 at Leesburg, VA. The wind shifted to a tailwind. Aircraft departed the runway striking a runway marker doing… ## Other investigations on N78659 (2) 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 WPR24LA107](https://openairdocs.org/ntsb/WPR24LA107), Mar 9, 2024: Piper PA-11 (N78659), Death Valley, CA, substantial damage. Probable cause: The pilot’s failure to maintain directional control during the landing rollout, resulting in a ground loop and runway excursion. - [NTSB CEN10IA447](https://openairdocs.org/ntsb/CEN10IA447), Jul 27, 2010: Piper PA-11 (N78659), Ripon, WI, incident, minor damage. Probable cause: The inability of either pilot to see the other airplane due to the blind spot created by their respective airplane's wings. 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.