# NTSB WPR12CA310: Piper PA-46, N558RW, Delano, CA, July 17, 2012 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 17, 2012, 11:40 local (18:40 UTC) - Place: Delano, CA - Coordinates: 35.745555, -119.236389 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.7456&lon=-119.2364&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Landing gear not configured](https://openairdocs.org/ntsb-events/095) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report November 26, 2012 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: FAA FSDO - NTSB case key (mKey): 84365 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR12CA310 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/84365/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=84365 - Page: https://openairdocs.org/ntsb/WPR12CA310 ## Probable cause The pilot's failure to extend the landing gear before touchdown. Contributing to the accident was the pilot's failure to perform the appropriate checklist due to distractions posed by another airplane inbound to the same airport and a cluttered radio frequency. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA46-500TP, 3 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=7104622), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Use of equip/info: use of checklist](https://openairdocs.org/ntsb-findings/02063030): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA46-500TP, 1 case](https://openairdocs.org/ntsb-findings/02063030/cases.md?model=7104622), [All aircraft, 336 cases](https://openairdocs.org/ntsb-findings/02063030/cases.md) - [Landing gear system: gear extension and retract sys](https://openairdocs.org/ntsb-findings/01023230): Aircraft › Aircraft systems · Not used/operated (probable cause); cases with it: [Piper PA46-500TP, 2 cases](https://openairdocs.org/ntsb-findings/01023230/cases.md?model=7104622), [All aircraft, 416 cases](https://openairdocs.org/ntsb-findings/01023230/cases.md) - [Communication system](https://openairdocs.org/ntsb-findings/03016000): Environmental issues › Operating environment · Effect on personnel (probable cause); cases with it: [Piper PA46-500TP, 1 case](https://openairdocs.org/ntsb-findings/03016000/cases.md?model=7104622), [All aircraft, 5 cases](https://openairdocs.org/ntsb-findings/03016000/cases.md) - [Attention/monitoring: attention](https://openairdocs.org/ntsb-findings/02021510): Personnel issues › Psychological · Pilot (probable cause); cases with it: [Piper PA46-500TP, 3 cases](https://openairdocs.org/ntsb-findings/02021510/cases.md?model=7104622), [All aircraft, 226 cases](https://openairdocs.org/ntsb-findings/02021510/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: Landing gear not configured](https://openairdocs.org/ntsb-events/095) (defining event); cases with it: [Piper PA46-500TP, 4 cases](https://openairdocs.org/ntsb-events/095/sequence.md?model=7104622), [All aircraft, 584 cases](https://openairdocs.org/ntsb-events/095/sequence.md) - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Piper PA46-500TP, 3 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=7104622), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA46-500TP, 6 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7104622), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The owner-pilot was the only person on board and was flying the turboprop airplane on a personal business trip. When he was about 10 miles south-southeast of the non-towered destination airport, he heard the pilot of a twin-engine airplane report that he was approaching the same airport from the north. The wind favored a landing on runway 32, and the turboprop pilot planned to fly a straight-in approach for landing on that runway. When the turboprop pilot was on final approach for runway 32 about 5 miles from the airport, he heard the twin-engine pilot announce that he was on the left base leg of the traffic pattern for runway 14. As the turboprop pilot continued the approach about 2 miles from the airport, he observed the twin-engine airplane on his traffic display; at that time, the twin-engine airplane was still about 6 miles from the airport. Constant radio transmissions from aircraft at two other non-towered airports in the vicinity precluded the turboprop pilot from communicating clearly with the twin-engine pilot to coordinate their arrivals. Based on the information from his traffic display, the turboprop pilot continued his straight-in approach for runway 32. Due to the distractions of the twin-engine airplane and the radio communication difficulties, the turboprop pilot did not perform the approach checklist and forgot to extend the landing gear, which he did not realize until touchdown. The airplane came to rest upright and intact about 50 feet off the side of the runway. The pilot was uninjured. Examination revealed substantial damage to the fuselage and wings. The pilot reported that he had traveled internationally in the preceding weeks and that he experienced some "mental fatigue." It was not determined whether or when the twin-engine airplane landed at the same airport. ## Factual narrative The owner was the only person on board, and was using the turboprop airplane for a personal business trip. When he was about 10 miles south-southeast of the non-towered destination airport, he heard the pilot of a twin-engine airplane report that he was approaching the same airport from the north. The winds favored a landing on runway 32, and the turboprop pilot planned to fly a straight-in approach for landing on that runway. When the turboprop pilot was on about a 5-mile final for runway 32, he heard the twin pilot announce that he was on a left base leg for runway 14. When the turboprop pilot was on about a 2-mile final for runway 32, he observed the twin on his traffic display; at that time the twin was still about 6 miles out from the airport. Constant radio transmissions from aircraft at two other non-towered airports in the vicinity precluded the turboprop pilot from communicating clearly with the twin pilot, in order to coordinate their arrivals. However, based on the information from his traffic display, the turboprop pilot continued his straight-in approach for runway 32. Due to the distractions of the other airplane and the radio communication difficulties, the turboprop pilot forgot to extend the landing gear, which he did not realize until touchdown. The airplane came to rest upright and intact, about 50 feet off the side of the runway. The pilot was uninjured. Examination by a Federal Aviation Administration inspector revealed substantial damage to the fuselage and wings. The pilot reported that he had traveled internationally at least twice in the preceding weeks, and that he experienced some "mental fatigue." It was not determined whether or when the twin landed at that same airport. ## Aircraft - Registration: [N558RW](https://openairdocs.org/deregistered/N558RW-2019-07-16), registration cancelled 2019-07-16, S/N 4697346, built 2008 (OpenAirDocs) - Reported make and model: PIPER PA-46 (500TP) - Registry model: [Piper PA46-500TP](https://openairdocs.org/model/piper-pa46-500tp) (registry code 7104623) (OpenAirDocs) - Registry engine: [Pratt & Whitney Canada PT6A-42A](https://openairdocs.org/engine/pratt-whitney-canada-pt6a-42a) (registry code 52268, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 4697346 - Airframe hours: 875 - Engines: Pratt & Whitney PT6 500 horsepower turbo prop - Damage: Substantial damage - Flight: Business, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, February 15, 2012, 22 hours before - Departed: TRM, Thermal, CA - Destination: DLO, Delano, CA - Airport: DLO, Delano Municipal, runway 32, 5,659 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, unknown; last flight review February 18, 2012; seat: left; flight hours: 2,646 total, 788 in this make and model, 33 in the last 90 days, 12 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 300° at 4 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 72 °F, dew point 54 °F - Altimeter: 29.97 inHg - Observed at: PTV, 18 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 20120717016629A](https://openairdocs.org/incident/20120717016629A), Jul 17, 2012: Piper Aircraft Inc PA46-500TP, Delano, CA, Substantial damage. The aircraft approached the Delano airport for landing and landed with the landing gear fully retracted. When questioned after the touchdown the pilot said he… ## Docket (5 files) The files NTSB released with the investigation on September 11, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=84365. 2.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40376104&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Additional Pilot Responses (item 2, .PDF, 40 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40376105&FileExtension=.PDF&FileName=Additional%20Pilot%20Responses-Redacted.PDF - METARs (item 3, .PDF, 125 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40376106&FileExtension=.PDF&FileName=METARs-Master.PDF - Photo 1. Overview of Airplane (item 4, .PDF, 235 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40376120&FileExtension=.PDF&FileName=Photo%201.%20Overview%20of%20Airplane-Master.PDF - Photo 2. Underside of Fuselage (item 5, .PDF, 405 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40376121&FileExtension=.PDF&FileName=Photo%202.%20Underside%20of%20Fuselage-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.