# NTSB WPR09CA054: Piper PA-28-161, N268ML, Goodyear, AZ, December 5, 2008 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: December 5, 2008, 14:00 local (21:00 UTC) - Place: Goodyear, AZ - Coordinates: 33.428333, -112.379722 - Nearby events: https://openairdocs.org/map.md?lat=33.4283&lon=-112.3797&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report June 11, 2009 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 69543 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR09CA054 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/69543/pdf - Page: https://openairdocs.org/ntsb/WPR09CA054 ## Probable cause The failure of the student pilot to maintain directional control during takeoff. ## 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: [Piper PA-28-161, 27 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7102803), [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: [Piper PA-28-161, 40 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102803), [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. - [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Piper PA-28-161, 20 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7102803), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-28-161, 30 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7102803), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The student pilot had been performing touch-and-go takeoffs and landings. On the accident landing, the pilot reported touching down left of centerline. He corrected back to runway centerline and reconfigured the airplane for takeoff. As he applied full power the airplane pulled to the left. He corrected back to runway centerline, did not see any abnormalities, and decided that he had enough remaining runway to safely take off. He applied full power and the airplane pulled to the left again. The right wing dropped and the airplane traveled to the left of the runway. The pilot reduced power to idle and applied right rudder. As the airplane was departing the runway surface, he applied the brakes. The pilot stated that there was no noticeable response from the airplane and braced himself as the airplane struck a taxiway sign and spun across the dirt between the runway and taxiway. A Federal Aviation Administration inspector examined the airplane and reported that there were no preimpact mechanical anomalies that would have caused a loss of aircraft control. ## Factual narrative According to the pilot, he was practicing touch-and-go takeoffs and landings as part of his flight training curriculum. The pilot reported that the two previous takeoffs and landings were performed with no issues; he also noted an existing crosswind during the takeoffs and landings. He took off again, and noted that when he turned downwind the airplane was a little "fast." He was able to slow the airplane down to 75 knots, but felt that he was a little high, so he applied full flap and slowed to 70 knots. He reported that there was a slight left crosswind and he corrected with left aileron and right rudder to maintain the approach on runway centerline. The airplane touched down to the right of the runway centerline, he applied left rudder to return to centerline and "verbally confirmed his checks," 'aircraft under control, flaps zero,' and reduced the flap setting to zero. The pilot applied full power and as he was about to check the instrument panel the airplane pulled to the left, which he felt was abnormal. He reduced the power in order to regain aircraft control back to centerline. There were no other anomalies encountered, and the pilot indicated he had enough remaining runway to safely takeoff. He rechecked the instruments, applied full power, and right rudder. About 3 seconds later, the airplane pulled "violently" to the left. The right wing dropped and the airplane rotated to the left. He reduced the throttle to idle and applied full right rudder to no effect. As the airplane was departing the runway surface, he applied brakes. A Federal Aviation Administration inspector examined the airplane, and reported that there were no mechanical anomalies that could have caused the loss of control. The total distance traveled from the onset of skid marks on the runway to where the airplane stopped on a taxiway was about 800 feet. The pilot reported to the FAA inspector that he landed hard to the left of the runway centerline. As he powered up, the airplane pulled to the left approximately 45 degrees. Skid marks from the nose wheel and right main tires were evident for about 300 feet arching to the left. He applied full power, and the airplane pulled to the left again. The left wing rose as the airplane turned abruptly left on the runway. The airplane continued off the runway where it hit a runway marker sign with the right wing. Witnesses reported that the airplane disappeared in a cloud of dust and traveled another 485 feet leaving only one tire mark before it struck a drainage ditch and came to a stop on a paved taxiway. The right main landing gear separated and was located about 200 feet from the point where the airplane departed the runway surface. ## Aircraft - Registration: [N268ML](https://openairdocs.org/deregistered/N268ML-2019-11-21), registration cancelled 2019-11-21, S/N 2842068 (OpenAirDocs) - Reported make and model: PIPER PA-28-161 - Registry model: [Piper PA-28-161](https://openairdocs.org/model/piper-pa-28-161) (registry code 7102803) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 2842068 - Airframe hours: 6988 - Engines: Lycoming O-320-D3G 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Oxford Airline Training Center Inc - Registered owner: Oxford Airline Training Center Inc - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: AAIP, October 4, 2008, 3 hours before - Departed: GYR, Goodyear, AZ - Destination: GYR, Goodyear, AZ - Airport: GYR, Phoenix Goodyear Airport, runway 21, 8,500 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 26; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; flight hours: 199 total, 19 in this make and model, 19 in the last 90 days, 19 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 5 knots - Visibility: 30 statute miles - Lowest ceiling: none - Temperature: 72 °F, dew point 30 °F - Altimeter: 30.14 inHg - Observed at: GYR ## 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 20081205853939A](https://openairdocs.org/incident/20081205853939A), Dec 5, 2008: Piper PA28161, Goodyear, AZ, Substantial damage. Pilot was performing touch and go operations when powering up after a hard landing to the left of the centerline. The pilot reported that aircraft pulled to… 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.