WPR10CA035

NTSB accident investigation · Piper PA-28-140 · Angwin, CA · October 30, 2009

Accident · No injuriesData collectionFinal report
Date
October 29, 2009, 19:31 local (Oct 30, 2009, 02:31 UTC)
Place
Angwin, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N1721TPiper PA-28-140
Defining event
Takeoff: Wrong surface or wrong airport
Weather
Visual (VMC) · Night
Status
Completed · report March 3, 2010
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
Federal Aviation Administration
FAA report
20091029021689A
Case key
74976

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 properly identify the runway surface for takeoff and his subsequent failure to abort the takeoff when he realized he was not on the runway. Contributing to the accident was the pilot’s failure to select the appropriate radio frequency to activate the runway lights.

Findings · 6

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.

Action: incorrect action performancePersonnel issues › Action/decision · PilotPiper PA-28-140: 15 casesAll aircraft: 1,386 casesProbable cause
Action: lack of actionPersonnel issues › Action/decision · PilotPiper PA-28-140: 8 casesAll aircraft: 792 casesProbable cause
Object/animal/substance: fence/fence postEnvironmental issues › Physical environment · Contributed to outcomePiper PA-28-140: 6 casesAll aircraft: 313 cases
Airport facilities/designEnvironmental issues › Operating environment · Awareness of conditionPiper PA-28-140: 1 caseAll aircraft: 52 casesProbable cause
Use of equip/info: use of equip/systemPersonnel issues › Task performance · PilotPiper PA-28-140: 16 casesAll aircraft: 1,391 casesProbable cause
Airport facilities/design: runway lightingEnvironmental issues › Operating environment · Use of related infoPiper PA-28-140: 1 caseAll aircraft: 18 cases

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 reported that he positioned the airplane for the night takeoff approximately 1/4-mile from the start of Runway 34. He attempted to activate the runway lights using the radio; however, he had selected an incorrect frequency. He used his landing light and positioned the airplane where he believed the runway was located. As the airplane approached 65 miles per hour, he saw grass and dirt. His passenger requested that he stop the airplane; however, the pilot felt that his options were better if he continued the takeoff. The passenger continued to request that he stop the airplane and the groundspeed was about 80 miles per hour. The pilot further reported that the passenger’s seat was positioned further back than his and that the passenger was pulling the yoke aft and her feet were pushing on the rudder pedals. The airplane then impacted a fence. Later activation of the airport lighting system revealed no operational anomalies when the correct radio frequency was selected.

Factual narrative

The pilot reported that he positioned the airplane for the night time takeoff approximately 1/4-mile from the start of runway 34. He attempted to activate the runway lights using the radio; however, he had selected an incorrect frequency. He used his landing light and positioned the airplane where he believed the runway was located. As the airplane approached 65 miles per hour, he saw grass and dirt. His passenger requested that he stop the airplane but in his opinion, he felt his options were better if he continued the takeoff. The passenger continued to request that he stop the airplane and the groundspeed was about 80 miles per hour. The pilot further reported that the passenger’s seat was positioned farther back than his and that the passenger was pulling the yoke aft and her feet were pushing on the rudder pedals. The airplane then impacted a fence. Later activation of the airport lighting system revealed no operational anomalies when the correct radio frequency was selected.

Aircraft

Registration
N1721T
Reported as
Piper PA-28-140
Category
Airplane
Serial number
28-7125034
Airframe hours
2,300
Engine
Lycoming O-320 SERIES, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Lee Mize
Registered owner
Lee Mize
Airworthiness certificate
Standard, Normal
Last inspection
Annual · December 1, 2008
Departed
2O3 · Angwin, CA
Destination
AUN · Auburn, CA
Airport
2O3 · Angwin-Parrett Field Airport, runway 34, 3,217 × 50 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
75
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Seat
Left
Flight hours
3,800 total · 1,600 in this make and model

Weather

Conditions
Visual (VMC) · Night
Wind
Calm
Visibility
10 statute miles
Lowest ceiling
None
Temperature
57 °F, dew point 48 °F
Altimeter
30.07 inHg
Observed at
STS, 19 nm away

Docket · 4

The files NTSB released with the investigation on November 17, 2009, on NTSB’s docket system: statements, records, photos and specialists’ reports. 966 KB in all.

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 N1721T · 1

Matched to the same aircraft by N-number and date.