ASN Wikibase Occurrence # 305306
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: | Monday 26 December 2022 |
| Time: | 20:35 LT |
| Type: |  Cessna 177B Cardinal |
| Owner/operator: | Private |
| Registration: | N177D |
| MSN: | 17702012 |
| Year of manufacture: | 1973 |
| Total airframe hrs: | 5102 hours |
| Engine model: | Lycoming O-360-A1F6D |
| Fatalities: | Fatalities: 0 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Franklin Municipal Airport (FKN/KFKN), VA -
 United States of America
|
| Phase: | |
| Nature: | Private |
| Departure airport: | Zephyrhills Airport, FL (ZPH/KZPH) |
| Elizabethtown-Curtis L Brown Jr Field, NC (KEYF) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The private pilot departed with full fuel tanks for the cross-country flight with a planned fuel stop en route. As the pilot neared the fuel stop airport, the fuel gauges indicated 3/4 capacity remaining, so he elected to continue to his destination airport. When the flight was 38 miles from the destination, with the fuel selector on the right tank position, the engine “started sputtering.' He then moved the fuel selector to the left tank position and turned the airplane towards a diversion airport. He checked the weather and NOTAMs for the diversion airport and noted nothing that concerned him. As he approached the diversion airport, he keyed the airplane's radio transmitter 5 times and then 7 times on the common traffic advisory frequency to turn on the runway lights, but they did not turn on (the end of civil twilight had occurred about an hour prior). Concerned about the airplane's fuel level, he landed but did not know how far down the runway he had landed. He described that the approach was “too fast' and the airplane bounced. After touching down, he applied the brakes but realized he would be unable to stop the airplane on the remaining portion of the runway. He added full power, started to climb, and thinking that the airplane had climbed higher than it actually had, he then banked left. The airplane's left wing then collided with trees substantially damaging it and bringing the airplane to a stop. The pilot stated that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation. He also stated that had he known the runway lights were inoperative, he would have diverted to a different airport.
Postaccident examination of the airplane revealed the airplane's radios were tuned to the correct frequency to activate the runway lights. According to the airport manager the, pilot-controlled lighting system at the airport was normally checked on the 1st day of every month and had been last checked 25 days before the accident. Following the accident, he discovered that they were inoperative. Given this information, it is possible that the pilot could have performed a successful landing had the runway lights been operational.
Probable Cause: The pilot's failure to maintain clearance from trees during the initial climb following an aborted precautionary landing. Contributing to the outcome were the inoperative runway lights, which reduced the likelihood that the pilot could successfully land the airplane on the runway at night.
Accident investigation:
 |
|
Sources:
NTSB ERA23LA094
Location
Media:
#NEW: A local pilot was injured after his plane crashed at Franklin Municipal Airport Monday evening.https://t.co/l27OgkmIWs
— WAVY TV 10 (@WAVY_News) December 27, 2022
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 16-Jun-2023 06:26 | ASN Update Bot | Updated |
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