# NTSB WPR09CA127: Cub Crafters PA-18-150, N324A, Buckeye, AZ, February 23, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: February 23, 2009, 12:45 local (19:45 UTC) - Place: Buckeye, AZ - Coordinates: 33.370277, -112.584724 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.3703&lon=-112.5847&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report May 12, 2009 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 73382 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR09CA127 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/73382/pdf - Page: https://openairdocs.org/ntsb/WPR09CA127 ## Probable cause The pilot's failure to maintain directional control. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cub Crafters PA18-150, 1 case](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2470000), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cub Crafters PA18-150, 2 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2470000), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cub Crafters PA18-150, 1 case](https://openairdocs.org/ntsb-events/230/sequence.md?model=2470000), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Cub Crafters PA18-150, 1 case](https://openairdocs.org/ntsb-events/096/sequence.md?model=2470000), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md) ## Analysis While preparing to land at the destination airport, the pilot extended his downwind leg to yield to traffic ahead of his position. He observed the windsock and noted a light crosswind. While on final approach, he configured the airplane with a little left rudder in an effort to compensate for the wind conditions. Following touchdown, and while on the landing roll with the engine at idle, the airplane began to yaw to the left of runway centerline. The pilot added full right rudder deflection and then applied right brake. The airplane nosed over, coming to rest inverted. The propeller and left wing sustained damage. The pilot stated there were no preimpact mechanical malfunctions or failures with the airframe or engine. He stated during the accident sequence the winds were light and variable with no gusts. ## Factual narrative In a written statement, the pilot reported that after departure he practiced configuring the airplane for slow-flight and performed numerous stalls. As the airplane approached the destination airport, he entered the traffic pattern on a 45-degree angle. He extended his downwind leg to yield to traffic ahead and observed the windsock indicating a light crosswind. While on final approach, he configured the airplane with a little left rudder in an effort to compensate for the wind conditions. Following touchdown, and while on the landing roll with the engine at idle, the airplane began to yaw to the left of runway centerline. The pilot added full right rudder deflection and then applied right brake. The airplane nosed over, coming to rest inverted; the propeller and left wing sustained damage. The pilot stated there were no preimpact mechanical malfunctions or failures with the airframe or engine. He stated during the accident sequence the winds were light and variable with no gusts. ## Aircraft - Registration: [N324A](https://openairdocs.org/aircraft/N324A), registered now, S/N 9962CC (OpenAirDocs) - Reported make and model: Cub Crafters PA-18-150 - Registry model: [Cub Crafters PA18-150](https://openairdocs.org/model/cub-crafters-pa18-150) (registry code 2470000) (OpenAirDocs) - Registry engine: [Lycoming O-360 series](https://openairdocs.org/engine/lycoming-o-360-series) (registry code 41575, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 9962CC - Engines: Lycoming O-360 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Departed: GEU, Glendale, AZ - Destination: BXK, Buckeye, AZ - Flight plan: Unknown - Airport: BXK, Buckeye Municipal Airport, runway 35, 5,500 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 52; injuries: none; foreign, private; airplane ratings: single-engine land; medical: class 3; seat: front; flight hours: 514 total, 5 in this make and model ## Weather - Conditions: Visual (VMC), Day - Visibility: 20 statute miles - Lowest ceiling: none - Temperature: 75 °F ## 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 20090223003899A](https://openairdocs.org/incident/20090223003899A), Feb 23, 2009: Piper PA18150, Buckeye, AZ, Substantial damage. (-23) [privacy data omitted] was flying a cub crafters super cub. After landing roll out the aircraft veered left, the pilot corrected with right rudder pedal,… 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.