# NTSB WPR10CA342: Piper PA32RT, N36402, Sedona, AZ, July 10, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 9, 2010, 22:00 local (Jul 10, 2010, 05:00 UTC) - Place: Sedona, AZ - Coordinates: 34.842224, -111.786392 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.8422&lon=-111.7864&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 4 uninjured - Status: Completed, report October 21, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: FAA FSDO - NTSB case key (mKey): 76579 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA342 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76579/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76579 - Page: https://openairdocs.org/ntsb/WPR10CA342 ## Probable cause The pilot’s failure to maintain runway alignment during approach and subsequent loss of directional control during landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: heading/course](https://openairdocs.org/ntsb-findings/01062047): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-32RT-300T, 1 case](https://openairdocs.org/ntsb-findings/01062047/cases.md?model=7103216), [All aircraft, 82 cases](https://openairdocs.org/ntsb-findings/01062047/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-32RT-300T, 2 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7103216), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Piper PA-32RT-300T, 3 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7103216), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32RT-300T, 11 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103216), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that he had flown the approach at a shallow angle causing him to lose sight of the runway lighting system during the landing flare. During the flare the airplane drifted to the left resulting in the left main landing gear touching down in the dirt next to the runway. Subsequently the airplane veered to the left, and struck a runway sign. The pilot reported that he was unaware that he had struck the sign and was able to correct back to the center of the runway. The remainder of landing roll and taxi were uneventful. The damage to the underside of the left wing and the sign was not found until the following day. The pilot reported that there were no known mechanical malfunctions or failures prior to the accident. ## Factual narrative The pilot reported that he had flown the approach at a shallow angle causing him to lose sight of the runway lighting system during the landing flare. During the flare the airplane drifted to the left resulting in the left main landing gear touching down in the dirt next to the runway. Subsequently the airplane veered to the left, and struck a runway sign. The pilot reported that he was unaware that he had struck the sign and was able to correct back to the center of the runway. The remainder of landing roll and taxi were uneventful. The damage to the underside of the left wing and the sign was not found until the following day. The pilot reported that there were no known mechanical malfunctions or failures prior to the accident. ## Aircraft - Registration: [N36402](https://openairdocs.org/deregistered/N36402-2018-03-12), registration cancelled 2018-03-12, S/N 32R-7887041, built 1978 (OpenAirDocs) - Reported make and model: PIPER PA32RT (300T) - Registry model: [Piper PA-32RT-300T](https://openairdocs.org/model/piper-pa-32rt-300t) (registry code 7103216) (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-7887041 - Airframe hours: 3146 - Engines: Lycoming TIO-540 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: RAD Aviation LLC - Registered owner: RAD Aviation LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 20, 2009, 100 hours before - Departed: KRHV, San Jose, CA - Destination: KSEZ, Sedona, AZ - Flight plan: Unknown - Airport: KSEZ, Sedona, runway 03, 5,132 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 49; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review September 15, 2009; seat: left; flight hours: 898 total, 431 in this make and model, 785 as pilot in command, 13 in the last 90 days, 11 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Night/dark - Wind: 300° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 111 °F - Altimeter: 30.19 inHg - Observed at: KSEZ ## 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 20100709038729A](https://openairdocs.org/incident/20100709038729A), Jul 9, 2010: Piper PA-32RT-300, Sedona, AZ, Substantial damage. On July 10, 2010 the pilot of N36402 was landing on runway 03 at the sez airport and stated he did not see the PAPI lights illuminated. Pilot stated he thought… ## Other investigations on N36402 (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 WPR16FA041](https://openairdocs.org/ntsb/WPR16FA041), Dec 19, 2015: Piper PA 32RT-300T (N36402), Bakersfield, CA, destroyed, 5 fatal. Probable cause: The noninstrument-rated pilot's decision to conduct and continue the flight despite forecast and en route instrument meteorological conditions (IMC), which were not conducive to safe operation under… ## Docket (1 files) The files NTSB released with the investigation on August 3, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76579. 499 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 499 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333563&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.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.