# NTSB WPR11CA413: Cessna 172F, N8698U, Atlanta, ID, August 29, 2011

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Data collection · Final report
- Date: August 29, 2011, 09:00 local (15:00 UTC)
- Place: Atlanta, ID
- Coordinates: 43.81361, -115.135002 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=43.8136&lon=-115.1350&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Defining event: [Approach-VFR pattern final: Miscellaneous/other](https://openairdocs.org/ntsb-events/900)
- Highest injury: Minor injuries
- Injuries: 2 minor
- Status: Completed, report December 1, 2011
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: Federal Aviation Administratin
- NTSB case key (mKey): 81625
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR11CA413
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/81625/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=81625
- Page: https://openairdocs.org/ntsb/WPR11CA413

## Probable cause

The pilot’s misjudgment of his final approach path. Contributing to the accident was the pilot’s inadequate preflight planning.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: altitude](https://openairdocs.org/ntsb-findings/01062012): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172F, 3 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md?model=2072414), [All aircraft, 1,310 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md)
- [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172F, 8 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072414), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md)
- [Experience/qualifications](https://openairdocs.org/ntsb-findings/02031000): Personnel issues › Experience/knowledge · Pilot; cases with it: [Cessna 172F, 1 case](https://openairdocs.org/ntsb-findings/02031000/cases.md?model=2072414), [All aircraft, 18 cases](https://openairdocs.org/ntsb-findings/02031000/cases.md)
- [Terrain: high elevation](https://openairdocs.org/ntsb-findings/03021025): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 172F, 1 case](https://openairdocs.org/ntsb-findings/03021025/cases.md?model=2072414), [All aircraft, 16 cases](https://openairdocs.org/ntsb-findings/03021025/cases.md)
- [Aircraft capability: climb capability](https://openairdocs.org/ntsb-findings/01061010): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Cessna 172F, 1 case](https://openairdocs.org/ntsb-findings/01061010/cases.md?model=2072414), [All aircraft, 183 cases](https://openairdocs.org/ntsb-findings/01061010/cases.md)
- [Performance/control parameters: climb rate](https://openairdocs.org/ntsb-findings/01062035): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172F, 2 cases](https://openairdocs.org/ntsb-findings/01062035/cases.md?model=2072414), [All aircraft, 265 cases](https://openairdocs.org/ntsb-findings/01062035/cases.md)
- [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172F, 5 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2072414), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Approach-VFR pattern final: Miscellaneous/other](https://openairdocs.org/ntsb-events/900) (defining event); cases with it: [Cessna 172F, 2 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=2072414), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md)
- [Approach-VFR go-around: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 172F, 3 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=2072414), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md)
- [Approach-VFR go-around: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 172F, 9 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2072414), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md)
- [Landing-flare/touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172F, 22 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072414), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

According to the pilot, on short final approach in his low performance airplane, he realized that his approach path was too high, so he attempted to go around. After full engine power was applied, he recognized that he had insufficient distance from the approaching trees and terrain to perform a go-around. Therefore, he aborted the maneuver and forced the airplane onto the ground in a clearing beyond the departure end of the runway. The airplane impacted the ground hard, breaking the wing and fuselage structure. The pilot reported that he was unfamiliar with the airport, and he had not read the Federal Aviation Administration’s published remarks for the airport in its Airport Facility Directory. The remarks state, in part, that the airport is recommended for use by “mountain proficient pilots using high performance aircraft.” It also states “no go-around due to rising terrain and trees.” Nine-thousand foot mountains are located within 5 miles from northwest through southeast of the 5,500-foot mean sea level airport.

## Factual narrative

According to the pilot, on short final approach to runway 34 in his 145-horsepower Cessna 172F, he realized that his approach path was too high, so he attempted to go around. After full engine power was applied, he recognized that he had insufficient distance from the approaching trees and terrain to perform a go-around. Therefore, he aborted the maneuver and forced the airplane onto the ground in a clearing beyond the departure end of the runway. The airplane impacted the ground hard, breaking wing and fuselage structure. The pilot reported to the National Transportation Safety Board investigator that he was unfamiliar with the airport, and he had not read the Federal Aviation Administration’s published remarks for the airport in its Airport Facility Directory. The remarks state, in pertinent part, that the airport is recommended for use by “mountain proficient pilots using high performance aircraft.” It also states “no go-around due to rising terrain and trees.” Nine thousand foot mountains are located within 5 miles from northwest through southeast of the 5,500-foot mean sea level airport.

## Aircraft

- Registration: [N8698U](https://openairdocs.org/deregistered/N8698U-2017-06-22), registration cancelled 2017-06-22, S/N 17252602, built 1965 (OpenAirDocs)
- Reported make and model: CESSNA 172F
- Registry model: [Cessna 172F](https://openairdocs.org/model/cessna-172f) (registry code 2072414) (OpenAirDocs)
- Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17252602
- Engines: CONT MOTOR O-300 SER 145 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Utility; Standard, Normal
- Last inspection: Annual, August 27, 2011
- Departed: S78, Emmett, ID
- Destination: 55H, Atlanta, ID
- Airport: 55H, Atlanta, runway 34, 2,460 × 75 ft, dirt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 57; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review January 24, 2010; seat: left; flight hours: 181 total, 140 in this make and model, 135 as pilot in command, 4 in the last 90 days, 2 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 70 °F

## 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 20110829019029A](https://openairdocs.org/incident/20110829019029A), Aug 29, 2011: Cessna 172F, Atlanta, ID, Substantial damage. Private pilot attempted to land at 55H, a high density altitude airport, recommended for experienced mountain pilots and high performance aircraft, with a…

## Docket (2 files)

The files NTSB released with the investigation on October 11, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=81625. 467 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 427 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40354863&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- FAA AFD Atlanta Airport (item 2, .PDF, 40 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40354860&FileExtension=.PDF&FileName=FAA%20AFD%20Atlanta%20Airport-Master.PDF

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.
