# NTSB CEN10CA228: Piper PA-32R-300, N5868V, Jamestown, ND, April 26, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 26, 2010, 17:00 local (22:00 UTC) - Place: Jamestown, ND - Coordinates: 46.929721, -98.678054 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=46.9297&lon=-98.6781&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Landing gear not configured](https://openairdocs.org/ntsb-events/095) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report July 22, 2010 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA Fargo FDSO - NTSB case key (mKey): 75873 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN10CA228 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75873/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75873 - Page: https://openairdocs.org/ntsb/CEN10CA228 ## Probable cause The pilot's failure to lower the landing gear, resulting in a gear-up landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-32R-300, 3 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=7103213), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Landing gear system: gear position and warning](https://openairdocs.org/ntsb-findings/01023260): Aircraft › Aircraft systems · Malfunction; cases with it: [Piper PA-32R-300, 1 case](https://openairdocs.org/ntsb-findings/01023260/cases.md?model=7103213), [All aircraft, 37 cases](https://openairdocs.org/ntsb-findings/01023260/cases.md) - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined; cases with it: [Piper PA-32R-300, 5 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7103213), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Landing gear not configured](https://openairdocs.org/ntsb-events/095) (defining event); cases with it: [Piper PA-32R-300, 6 cases](https://openairdocs.org/ntsb-events/095/sequence.md?model=7103213), [All aircraft, 584 cases](https://openairdocs.org/ntsb-events/095/sequence.md) ## Analysis The pilot reported that he was approaching the airport with the intention of performing three touch and go landings. He went over the landing checklist as he was nearing the field, but he did not put the landing gear down because he was not on the downwind leg, where he would normally complete the checklist. He reported, “As I turned final, I thought I had the gear down but didn’t.” He reported that the gear up warning horn never sounded. The airplane touched down in a wings level attitude on the runway, which resulted in a bent propeller and substantial damage to the “hat” assemblies, which are U-shaped structural channels on the belly of the airplane. The landing gear handle was found in the UP position. The inspection of the airplane revealed that the landing gear extended and retracted when the airplane was put on jacks. The “Warning Gear Unsafe” light illuminated when the throttle was pulled to the idle position with the landing gear in the retracted position. The “Warning Gear Unsafe” light is about a 1-inch square red light located directly in front of the pilot on the instrument panel. However, the “Gear Warning Horn” did not sound. ## Factual narrative The pilot reported that he was approaching the airport with the intention of performing three touch and go landings. He went over the landing checklist as he was nearing the field, but he did not put the landing gear down because he was not on the downwind leg, where he would normally complete the checklist. He reported, “As I turned final, I thought I had the gear down but didn’t.” He reported that the gear up warning horn never sounded. The airplane touched down in a wings level attitude on the runway, which resulted in a bent propeller and substantial damage to the “hat” assemblies, which are U-shaped structural channels on the belly of the airplane. The landing gear handle was found in the UP position. The inspection of the airplane revealed that the landing gear extended and retracted when the airplane was put on jacks. The “Warning Gear Unsafe” light illuminated when the throttle was pulled to the idle position with the landing gear in the retracted position. The “Warning Gear Unsafe” light is about a 1-inch square red light located directly in front of the pilot on the instrument panel. However, the “Gear Warning Horn” did not sound. ## Aircraft - Registration: [N5868V](https://openairdocs.org/aircraft/N5868V), registered now, S/N 32R-7780369, built 1977 (OpenAirDocs) - Reported make and model: PIPER PA-32R-300 - Registry model: [Piper PA-32R-300](https://openairdocs.org/model/piper-pa-32r-300) (registry code 7103213) (OpenAirDocs) - Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 32R-7783069 - Engines: Lycoming IO-540-K1G5D 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Silas Liechty - Registered owner: Robert Frey - Airworthiness certificate: Standard, Normal - Departed: JMS, Jamestown, ND - Destination: JMS, Jamestown, ND - Airport: JMS, Jamestown Regional Airport ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 78; private; airplane ratings: multi-engine land, single-engine land, single-engine sea; instrument ratings: airplane; medical: class 3; flight hours: 5,000 total, 100 in this make and model ## Weather - Conditions: Visual (VMC), Day ## 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 20100426033409A](https://openairdocs.org/incident/20100426033409A), Apr 26, 2010: Piper PA-32R-300, Jamestown, ND, Substantial damage. Pilot stated he failed to extend the undercarriage prior to landing. ## Docket (3 files) The files NTSB released with the investigation on May 26, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75873. 885 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 753 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330009&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - NTSB Record of Interview (item 2, .PDF, 33 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330270&FileExtension=.PDF&FileName=NTSB%20Record%20of%20Interview-Master.PDF - Excerpt from PA-32R-300 Service Manual (item 3, .PDF, 98 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330271&FileExtension=.PDF&FileName=Excerpt%20from%20PA-32R-300%20Service%20Manual-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.