N1721T accident
NTSB WPR10CA035 · 2009-10-30 · Angwin, CA · near 2O3
Docket — crew, injuries and powerplant
Summary
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.
Full 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.
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. The National Transportation Safety Board determined the probable cause of this accident.
Circumstances
- Event type
- Accident
- Highest injury
- None
- Weather conditions
- Visual Meteorological Cond
- Light condition
- Night
- Sky condition
- NONE
- Ceiling (ft)
- 0
- Visibility (sm)
- 10
- Wind direction
- 0
- Temperature (F)
- 57
- Nearest airport
- Angwin-Parrett Field Airport
- Distance from field
- 0.0
- Airport elevation
- 1848
Aircraft
| Registration | Make | Model | Damage | FAR part |
|---|---|---|---|---|
| N1721T | — | — | SUBS | 091 |
Sequence of events
| # | Occurrence | Phase |
|---|---|---|
| 1 | Taxi-into takeoff position Miscellaneous/other | Taxi |
| 3 | Takeoff Wrong surface or wrong airport defining | Takeoff |