- Date
- March 28, 2008, 12:15 local (19:15 UTC)
- Place
- Phoenix, AZ
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N963WWPiper PA-28R-201
- Defining event
- Landing-flare/touchdown: Loss of control on ground
- Weather
- Visual (VMC) · Day
- Status
- Completed · report April 30, 2008
- Report
- Approved by Office Director
- Parties
- Federal Aviation Administration
- FAA report
- 20080328833339A
- Case key
- 67729
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The pilot's failure to maintain directional control of the airplane during landing.
Findings · 3
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
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
- Reported as
- Piper PA-28R-201
- Category
- Airplane
- Serial number
- 2844023
- Engine
- 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
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 28
- Certificate
- 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.
Other investigations on N963WW · 2
Matched to the same aircraft by N-number and date.