# NTSB WPR10LA207: Piper PA-22-160, N9019D, Fruitland, UT, April 17, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: April 17, 2010, 14:35 local (20:35 UTC) - Place: Fruitland, UT - Coordinates: 40.214443, -110.838058 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.2144&lon=-110.8381&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report August 12, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration FSDO - NTSB case key (mKey): 75774 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10LA207 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75774/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75774 - Page: https://openairdocs.org/ntsb/WPR10LA207 ## Probable cause The pilot’s improper landing flare. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Piper PA-22-160, 1 case](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=7102214), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Landing gear system: main landing gear attach sec](https://openairdocs.org/ntsb-findings/01023211): Aircraft › Aircraft systems · Capability exceeded; cases with it: [Piper PA-22-160, 3 cases](https://openairdocs.org/ntsb-findings/01023211/cases.md?model=7102214), [All aircraft, 66 cases](https://openairdocs.org/ntsb-findings/01023211/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible; cases with it: [Piper PA-22-160, 16 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7102214), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-22-160, 2 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=7102214), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Piper PA-22-160, 3 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=7102214), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Piper PA-22-160, 9 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=7102214), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-22-160, 11 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102214), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The pilot reported that the windsock indicated light winds straight down the runway and he encountered some light headwind gusts on short final. During the flare, the airplane ballooned and he applied power to smooth the descent. The pilot stated that the landing was a full stall hard landing, which was the only type of landing he ever performed. The left main landing gear subsequently collapsed, the left wing dropped, and the airplane veered to the right. Despite the pilot's control inputs, the airplane exited the right side of the runway surface and impacted a drainage berm. Federal Aviation Administration inspectors examined the airplane and observed that the landing gear shock cord’s retainer lug fractured and separated. The cords released, which caused them to lose all of the tension required to perform their intended function. The structure had no indication of previous cracking or fatigue, and there were 45-degree shear lips around the entire circumference of the fracture surface indicative of an overload condition. ## Factual narrative On April 17, 2010, about 1435 mountain daylight time, a Piper PA-22-160 Pacer, N9019D, veered off the runway following a landing gear collapse at Fruitland, Utah. The owner was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The certificated private pilot and one passenger were not injured. The airplane sustained substantial damage by impact forces to the left wing and left elevator. The cross-country personal flight departed West Jordan, Utah, at 1350, with a planned destination of Fruitland. Visual meteorological conditions prevailed, and no flight plan had been filed. The pilot reported that the windsock indicated light winds straight down runway 31. The airplane passed through short final at 73 knots, and he noticed some light headwind gusts. During the landing flare, the airplane ballooned, and he applied power to smooth the descent. The pilot stated that the touchdown sound and feel were different, and that the left main landing gear had collapsed. The left wing dropped below the horizon followed by a hard “non-bounce.” The airplane veered to the right, and despite his left rudder and brake control inputs, the airplane exited the right side of the runway surface. The left wing impacted a drainage berm. Several Federal Aviation Administration (FAA) inspectors examined the wreckage and interviewed the pilot. The pilot indicated to them that the landing was hard; a full stall landing was the only type of landing he ever did, and they are all somewhat hard. However, he felt that this was no harder than many of his other landings. The FAA accident coordinator and another maintenance inspector examined the landing gear shock cords and the separation of the structure. They made the following observations. The shock cords were intact; there was no degradation of the cords themselves. The cord retainer lug had fractured and separated; this allowed the cords to release and lose all of the tension required to perform their intended function. The cords appeared quite new and in excellent condition. A mechanic verified that they were replaced at the annual inspection on September 1, 2009. The airplane had about 40 hours of flight time since the annual. The landing gear structure itself had no indication of previous cracking or fatigue, and there were 45-degree shear lips around the entire circumference of the fracture surface. ## Aircraft - Registration: [N9019D](https://openairdocs.org/aircraft/N9019D), registered now, S/N 22-6154, built 1958 (OpenAirDocs) - Reported make and model: PIPER PA-22-160 - Registry model: [Piper PA-22-160](https://openairdocs.org/model/piper-pa-22-160) (registry code 7102214) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 22-6154 - Airframe hours: 3474 - Engines: Lycoming O-320-B2B 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Ventana Air LLC - Registered owner: Ventana Air LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 1, 2009, 18 hours before - Departed: U42, West Jordan, UT - Destination: UT83, Fruitland, UT - Airport: UT83, Fruitland, runway 31, 4,000 × 48 ft, dirt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 57; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review February 13, 2009; seat: left; flight hours: 378 total, 268 in this make and model, 265 as pilot in command, 19 in the last 90 days, 7 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 310° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 66 °F, dew point 19 °F - Altimeter: 30.05 inHg - Observed at: K36U, 36 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 20100417031919A](https://openairdocs.org/incident/20100417031919A), Apr 17, 2010: Piper PA-22-160, Fruitland, UT, Substantial damage. Pilot was landing on runway 31 into a headwind, aircraft ballooned, he added power and touched down hard on the runway. Pilot heard loud noise on touchdown and… ## Other investigations on N9019D (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 WPR25LA206](https://openairdocs.org/ntsb/WPR25LA206), Jul 7, 2025: Piper PA-22-160 (N9019D), Page, AZ, substantial damage. Probable cause: The pilot's failure to maintain directional control during the landing roll with a quartering tailwind. ## Docket (2 files) The files NTSB released with the investigation on May 11, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75774. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40329523&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Inspector record of Conversation (item 2, .PDF): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40329524&FileExtension=.PDF&FileName=FAA%20Inspector%20record%20of%20Conversation-Master.PDF 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.