Accident Cessna 172G N1374F,
ASN logo
ASN Wikibase Occurrence # 291641
 
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 16 November 2006
Time:18:00 LT
Type:Silhouette image of generic C172 model; specific model in this crash may look slightly different    
Cessna 172G
Owner/operator:
Registration: N1374F
MSN: 172-54869
Total airframe hrs:2052 hours
Engine model:Lycoming O-360-A4M
Fatalities:Fatalities: 0 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:Ankeny, Iowa -   United States of America
Phase: Unknown
Nature:Private
Departure airport:Rush City Regional Airport, MN (KROS)
Destination airport:Ankeny Regional Airport, IA (IKV/KIKV)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The airplane was substantially damaged when it encountered a ditch after over running the runway pavement during a night landing. The pilot reported that the runway lights did not come on when she attempted to activate them via the airplane radio prior to landing. She attempted to activate them a total of 3 times. She subsequently overflew the airport in order to identify the runway. She stated that she "flew downwind to where [she] estimated the end of the runway would be [and] turned to final." She noted that she flew over the runway "low" to see the centerline and decided to land. She then realized that the airplane had touched down "well down [the] runway." She was unable to stop before the end of the pavement and the airplane rolled into the grass. She stated that as the airplane slowed she attempted to turn back; however, she encountered a drainage ditch causing the nose landing gear to collapse and damaging the firewall. The pilot reported that after the accident she realized that the radio was set to the incorrect frequency. The radio was set to 120.9 instead of the correct Common Traffic Advisory Frequency (CTAF) for the destination airport of 122.9. The airport manager reported that the runway lights functioned properly when activated after the accident. He also noted that the lights are normally off until activated by a pilot via the CTAF.

Probable Cause: The pilot's improper decision to land on an unlighted runway at night, and her resulting failure to attain a proper touchdown point leading to the landing over run. Contributing factors were the night (low light) condition and the ditch encountered during the overrun.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: CHI07CA025
Status: Investigation completed
Duration: 3 months
Download report: Final report

Sources:

NTSB CHI07CA025

Revision history:

Date/timeContributorUpdates
07-Oct-2022 17:09 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org