CHI07CA025

NTSB accident investigation · Cessna 172G · Ankeny, IA · November 17, 2006

Accident · No injuriesData collectionFinal report
Date
November 16, 2006, 18:00 local (Nov 17, 2006, 00:00 UTC)
Place
Ankeny, IA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1374FCessna 172G
Weather
Visual (VMC) · Night
Status
Completed · report February 26, 2007
Report
Approved by Office Director
Parties
FAA-Des Moines FSDO
FAA report
20061116024559A
Case key
65002

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

On ground/water encounter with terrain/waterLanding
In-flight planning/decision - improperPilot in commandCause
Unsuitable terrain or takeoff/landing/taxi area - selectedPilot in commandCause
Proper touchdown point - not attainedPilot in commandCause
Light condition - nightFactor
Terrain condition - ditchFactor

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
Reported as
Cessna 172G
Category
Airplane
Serial number
172-54869
Airframe hours
2,052
Engine
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

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
66
Injuries
None
Certificate
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.

Other investigations on N1374F · 1

Matched to the same aircraft by N-number and date.