# NTSB SEA08CA097: Piper PA-28R-201, N963WW, Phoenix, AZ, March 28, 2008 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: March 28, 2008, 12:15 local (19:15 UTC) - Place: Phoenix, AZ - Coordinates: 33.691112, -112.903335 - Nearby events: https://openairdocs.org/map.md?lat=33.6911&lon=-112.9033&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 30, 2008 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 67729 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA08CA097 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/67729/pdf - Page: https://openairdocs.org/ntsb/SEA08CA097 ## Probable cause The pilot's failure to maintain directional control of the airplane during landing. ## 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-28R-201, 3 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7102816), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Pilot; cases with it: [Piper PA-28R-201, 4 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=7102816), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md) - [Object/animal/substance: sign/marker](https://openairdocs.org/ntsb-findings/03022015): Environmental issues › Physical environment · Not specified; cases with it: [Piper PA-28R-201, 1 case](https://openairdocs.org/ntsb-findings/03022015/cases.md?model=7102816), [All aircraft, 214 cases](https://openairdocs.org/ntsb-findings/03022015/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: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Piper PA-28R-201, 3 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=7102816), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-28R-201, 8 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102816), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot, who was training for her certified flight instructor certificate, was returning to the airport. Following the first touch down on the runway, she felt that "...something was wrong with the rudder pedals." She felt a slight tugging to the right, but once the airplane was airborne again she no longer felt this tugging. She then retracted the landing gear. As she was on downwind, she extended the landing gear and the green light for the nose gear momentarily flickered but became a solid green light. As she turned onto the final leg of the traffic pattern, she verified that the landing gear were down and locked. Upon touchdown, she immediately felt the airplane tugging to the right side and decided to abort the takeoff. The pilot began to pull the power back to idle and apply braking, while leaving the flaps extended. As she applied the brakes, the airplane pulled to the right, which felt to the pilot like the right brake was locked. The pilot removed her feet from the brakes evenly and the airplane turned quickly to the right. She attempted to correct with left rudder inputs; however, the airplane collided with a sign and sustained substantial damage to the right wing. A Federal Aviation Administration inspector reported that there were marks on the runway, consistent with the airplane touching down with the landing gear not pointed directly down the runway. Inspection of the airplane did not reveal any mechanical malfunctions with the landing gear or braking system. Review of the maintenance records did not indicate any recent discrepancy reports involving the landing gear or braking system. ## Factual narrative The pilot, who was training for her certified flight instructor (CFI) certificate, was returning to the airport. Following the first touch down on runway 7R, she felt that "...something was wrong with the rudder pedals." She felt a slight tugging to the right, but once the airplane was airborne again she no longer felt this tugging. She then retracted the landing gear. As she was on downwind, she extended the landing gear and the green light for the nose gear momentarily flickered but became a solid green light. As she turned onto the final leg of the traffic pattern, she verified that the landing gear were down and locked. Upon touchdown, she immediately felt the airplane tugging to the right side and decided to abort the takeoff. The pilot began to pull the power back to idle and apply braking, while leaving the flaps extended. As she applied the brakes, the airplane pulled to the right which felt to the pilot like the right brake was locked. The pilot removed her feet from the brakes evenly and the airplane turned quickly to the right. She attempted to correct with left rudder inputs; however, the airplane collided with a sign and sustained substantial damage to the right wing. The pilot indicated that a CFI at the flight school told her that two of his students reported uneven braking in the airplane. The CFI was interviewed by the National Transportation Safety Board investigator. He indicated that during two dual, instructional flights, his students reported uneven braking. When the students reported the problem, he conducted the following landings. The CFI did not experience any braking anomalies or directional control problems with the airplane. A Federal Aviation Administration inspector responded to the accident site. The inspector indicated that there were marks on the runway, consistent with the airplane touching down with the landing gear not pointed directly down the runway. Inspection of the airplane did not reveal any mechanical malfunctions with the landing gear or braking system. Review of the maintenance records did not indicate any recent discrepancy reports involving the landing gear or braking system. ## Aircraft - Registration: [N963WW](https://openairdocs.org/aircraft/N963WW), registered now, S/N 2844023, built 2000 (OpenAirDocs) - Reported make and model: Piper PA-28R-201 - Registry model: [Piper PA-28R-201](https://openairdocs.org/model/piper-pa-28r-201) (registry code 7102816) (OpenAirDocs) - Registry engine: [Lycoming I0360 SER A&C](https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (registry code 41511, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 2844023 - Engines: Textron Lycoming IO-360-C1C6 reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: Westwind Aviation Inc. - Airworthiness certificate: Standard, Normal - Departed: DVT, Phoenix, AZ - Destination: DVT, Phoenix, AZ - Flight plan: VFR - Airport: DVT, Phoenix Deer Valley, runway 7R, 8,208 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 28; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1; last flight review December 1, 2007; flight hours: 462 total, 58 in this make and model, 18 in the last 90 days, 17 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 190° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 25 °F - Altimeter: 29.81 inHg - Observed at: DVT ## 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 20080328833339A](https://openairdocs.org/incident/20080328833339A), Mar 28, 2008: Piper PA28R201, Phoenix, AZ, Substantial damage. (-23) While performing 2nd landing on runway 7R, while performing touch and gos, pilot stated she "immediately felt the airplane tugging to the right side and… ## Other investigations on N963WW (2) 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 WPR15CA115](https://openairdocs.org/ntsb/WPR15CA115), Feb 24, 2015: Piper PA 28R-201 (N963WW), Phoenix, AZ, substantial damage. Probable cause: The pilot under instruction's inadvertent retraction of the landing gear during the landing rollout. - [NTSB WPR12LA247](https://openairdocs.org/ntsb/WPR12LA247), May 29, 2012: Piper PA28R (N963WW), Peoria, AZ, substantial damage. Probable cause: A loss of engine power for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation. 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.