# NTSB CHI07CA025: Cessna 172G, N1374F, Ankeny, IA, November 17, 2006

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: November 16, 2006, 18:00 local (Nov 17, 2006, 00:00 UTC)
- Place: Ankeny, IA
- Coordinates: 41.691387, -93.56639
- Nearby events: https://openairdocs.org/map.md?lat=41.6914&lon=-93.5664&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report February 26, 2007
- Report: Approved by Office Director
- Parties: FAA-Des Moines FSDO
- NTSB case key (mKey): 65002
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI07CA025
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/65002/pdf
- Page: https://openairdocs.org/ntsb/CHI07CA025

## 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.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- On ground/water encounter with terrain/water, landing
  - in-flight planning/decision - improper, pilot in command (cause)
  - unsuitable terrain or takeoff/landing/taxi area - selected, pilot in command (cause)
  - proper touchdown point - not attained, pilot in command (cause)
  - light condition - night (contributing factor)
  - terrain condition - ditch (contributing factor)

## Analysis

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.

## 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.

## Aircraft

- Registration: [N1374F](https://openairdocs.org/aircraft/N1374F), registered now, S/N 17254869, built 1966 (OpenAirDocs)
- Reported make and model: Cessna 172G
- Registry model: [Cessna 172G](https://openairdocs.org/model/cessna-172g) (registry code 2072420) (OpenAirDocs)
- Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 172-54869
- Airframe hours: 2052
- Engines: Lycoming O-360-A4M 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, May 1, 2006
- Departed: ROS, Rush City, MN
- Destination: IKV, Ankeny, IA
- Airport: ROS, Rush City Regional, runway 18, 5,500 × 100 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 66; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review August 1, 2006; seat: left; flight hours: 520 total, 469 in this make and model, 478 as pilot in command, 30 in the last 90 days, 17 in the last 30 days, 2 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Night
- Wind: 0° at 0 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 30 °F, dew point 27 °F
- Altimeter: 29.86 inHg
- Observed at: IKV

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20061116024559A](https://openairdocs.org/incident/20061116024559A), Nov 16, 2006: Cessna 172G, Ankeny, IA, Substantial damage. (-23) Aircraft was attempting to land at the Ankeny, IA airport (ikv) at approximately 1800 local time. The pilot was unable to get the pilot controlled runway…

## Other investigations on N1374F (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CEN23LA396](https://openairdocs.org/ntsb/CEN23LA396), Sep 3, 2023: Cessna 172G (N1374F), Neola, IA, substantial damage. Probable cause: The pilot’s inadequate fuel planning and improper in-flight decision-making, which resulted in a total loss of engine power due to fuel exhaustion.

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
