ASN Wikibase Occurrence # 286448
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Thursday 29 October 2009 |
| Time: | 18:31 LT |
| Type: |  Piper PA-28-140 |
| Owner/operator: | Private |
| Registration: | N1721T |
| MSN: | 28-7125034 |
| Year of manufacture: | 1970 |
| Total airframe hrs: | 2300 hours |
| Engine model: | Lycoming O-320 SERIES |
| Fatalities: | Fatalities: 0 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Angwin, California -
 United States of America
|
| Phase: | Taxi |
| Nature: | Private |
| Departure airport: | Angwin, CA (2O3) |
| Auburn Municipal Airport, CA (AUN/KAUN) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
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.
Accident investigation:
 |
|
Sources:
NTSB WPR10CA035
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 03-Oct-2022 11:00 | ASN Update Bot | Added |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation