ASN Wikibase Occurrence # 149384
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: | Tuesday 2 October 2012 |
| Time: | 20:24 |
| Type: |  Piper PA-28-180 Cherokee |
| Owner/operator: | Private |
| Registration: | N7895W |
| MSN: | 28-1923 |
| Year of manufacture: | 1964 |
| Engine model: | Lycoming O&VO-360 SER |
| Fatalities: | Fatalities: 0 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Beatty, NV -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Reno-Stead, NV (RTS) |
| Henderson Exec, NV (HND) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot reported that a temporary flight restriction (TFR) was in effect for his intended destination airport and that he was unclear on whether the TFR would prevent him from landing at that airport. The TFR stated that transit operations were allowed only if a discrete code was assigned by air traffic control (ATC) before the airplane’s departure. The pilot mistakenly thought he could pick up the discrete code while airborne. Because the pilot was unable to contact ATC at his intended destination during the flight and the airplane was running low on fuel, he diverted to an alternate airport. At the alternate airport, the pilot initiated a straight-in approach to the runway in darkness, over flat, featureless terrain; the pilot reported that the only airport lighting he saw was the airport beacon. During the approach, the airplane struck high tension power lines about 1 mile south of the runway. Further, according to an applicable notice to airmen, the airport that the pilot diverted to was closed when the accident occurred. The pilot most likely flew a lower than desired approach altitude due to the night time conditions and featureless terrain. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane or engine that would have precluded normal operation.
Probable Cause: The pilot’s inadequate flight planning, subsequent loss of situational awareness, and failure to maintain clearance from the power lines during a dark night approach to a closed, unlit runway.
Accident investigation:
 |
|
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 03-Oct-2012 06:51 | gerard57 | Added |
| 03-Oct-2012 09:56 | TB | Updated [Aircraft type, Operator, Location, Destination airport, Narrative] |
| 03-Oct-2012 10:03 | TB | Updated [Aircraft type, Narrative] |
| 03-Oct-2012 11:00 | Alpine Flight | Updated [Time, Aircraft type, Registration, Cn, Operator, Destination airport, Source] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 28-Nov-2017 13:44 | ASN Update Bot | Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
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