Skip to content

CHI07CA025

2006-11-16 · Ankeny, Iowa, United States · None · 1 aircraft · Status: Completed

Airport ROS

Current FAA registration · N1374F

Make / Model
CESSNA 172G
Year of manufacture
1966 · 40 years old at event
Engine
CONT MOTOR 0-300 SER (145 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19660712
ADS-B equipped
Yes — Mode-S A0981C

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

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.

Factual 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. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2006_CHI07CA025.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.