Controlled Flight Into Terrain · NTSB ERA10FA029

CESSNA 172P — Bennington, VT

1 fatal Low-time pilotNightBase-to-final turn
DateOctober 25, 2009
LocationBennington, VT
AircraftCESSNA 172P
Purpose of flightPersonal
ConditionsNight · Visual Meteorological Cond
Phase / occurrenceApproach-VFR pattern base Controlled flight into terr/obj (CFIT)
Pilot age58
Pilot total time174 hrs · Low time
Time in typeUnknown
Fatalities1

Probable cause

The pilot’s failure to maintain clearance from terrain during a night approach. Contributing to the accident was the pilot’s non-standard traffic pattern over higher terrain.

NTSB findings

  • Environmental issues-Conditions/weather/phenomena-Light condition-Dark-Contributed to outcome
  • Personnel issues-Psychological-Attention/monitoring-Monitoring environment-Pilot - C
  • Personnel issues-Action/decision-Action-Incorrect action selection-Pilot - F

What happened

The pilot entered the traffic pattern at night and was observed flying in a right-hand traffic pattern to runway 13. The Airport/Facility Directory did not direct right-hand traffic for runway 13. Witnesses observed the pilot having difficulty landing the airplane; he was flying too high on final approach and performed at least two go-arounds. The airplane was last observed with its navigation lights illuminated on the base leg as the airplane impacted trees and terrain. Two witnesses stated that the engine was running at the time of impact. The wreckage came to rest on wooded terrain, at an elevation of about 1,082 feet, or about 250 feet above the airport's elevation. If the pilot had flown the same altitude on a left-hand pattern to runway 13, at the same point in the pattern where the accident occurred, the airplane would have cleared the terrain by about 300 feet. Examination of the wreckage revealed no evidence of preexisting mechanical anomalies. Inspection of the pilot’s logbook showed no evidence that he had previously flown approaches at the airport.

An editorial "what led to it / how to avoid it" analysis for this accident is generated separately and will appear here.

View the official NTSB docket →