# NTSB ERA10CA288: Cessna 182H, N8311S, Oliver Springs, TN, May 31, 2010

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Data collection · Final report
- Date: May 31, 2010, 13:00 local (17:00 UTC)
- Place: Oliver Springs, TN
- Coordinates: 36.037498, -84.306945 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=36.0375&lon=-84.3069&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300)
- Highest injury: Minor injuries
- Injuries: 2 minor
- Status: Completed, report April 12, 2011
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA Nashville FSDO
- NTSB case key (mKey): 76149
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10CA288
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76149/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76149
- Page: https://openairdocs.org/ntsb/ERA10CA288

## Probable cause

The pilot's failure to execute a go-around, which resulted in a long landing, runway overrun, and the airplane's subsequent descent into a stream.

## Findings

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

- [Object/animal/substance](https://openairdocs.org/ntsb-findings/03022000): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 182H, 1 case](https://openairdocs.org/ntsb-findings/03022000/cases.md?model=2072718), [All aircraft, 224 cases](https://openairdocs.org/ntsb-findings/03022000/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 182H, 4 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2072718), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md)
- [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 182H, 2 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=2072718), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md)

## Sequence of events

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

- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cessna 182H, 3 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072718), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Approach-VFR go-around: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 182H, 2 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=2072718), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md)
- [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 182H, 13 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072718), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

According to the pilot, she contacted the operator of the private airport several days before the accident to obtain permission to land. The operator informed the pilot that the runway was comprised of turf and briefed her on the hazards associated with runways 15 and 33. He recommended the pilot make her approach to runway 15 due to a 15-foot drop-off into a stream at the end of runway 33. The pilot configured the airplane for landing to runway 15. Her approach was fast and high and she made a go-around when the airplane was halfway down the runway. She climbed out on the runway heading, made a 180-degree turn and initiated an approach to runway 33. The airplane touched down on the last third of the runway and she immediately applied heavy brakes. She realized that she would be unable to stop and applied full power; however, the airplane went off the drop-off and into the stream. The pilot stated that she did not experience any mechanical problems with the airplane. A Federal Aviation Administration inspector examined the runway and stated that he observed tracks up to but no further than 250 to 300 feet before the runway edge of the creek.

## Factual narrative

According to the private pilot, she contacted the operator of the private airport several days before the accident to obtain permission to land. The operator informed the pilot that the runway was a 2,800-foot turf runway and briefed her on the hazards associated with runway 15 and 33. He recommended the pilot make her approach to runway 15 due to a 15-foot drop off into a stream at the end of runway 33. The pilot and her husband, who was a passenger, departed on an instrument flight rules (IFR) flight plan. Once they were cleared to a lower altitude by an air traffic controller and had a visual sighting of the airport, the pilot cancelled the IFR flight plan and proceeded on a visual approach straight in to runway 15. She reduced all power and extended the flaps to 40 degrees. Her approach was fast and high and she made a go-around when the airplane was half way down the runway. She climbed out on runway heading, made a 180-degree turn, checked the winds at a local airport 3 miles away on her global positioning system, and initiated a straight in full flap approach to runway 33. Her husband reported power lines and she increased power to clear the lines. The airplane touched down on the last third of the runway and she immediately applied heavy brakes. She realized she would be unable to stop and applied full power. The airplane went off the drop off into the stream. The pilot stated she did not experience any mechanical problems with the airplane. A Federal Aviation Administration inspector examined the runway and stated he observed tracks up to but no further than 250 to 300 feet before the runway edge of the creek.

## Aircraft

- Registration: [N8311S](https://openairdocs.org/deregistered/N8311S-2010-11-22), registration cancelled 2010-11-22, S/N 18256411, built 1965 (OpenAirDocs)
- Reported make and model: CESSNA 182H
- Registry model: [Cessna 182H](https://openairdocs.org/model/cessna-182h) (registry code 2072718) (OpenAirDocs)
- Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 18256411
- Airframe hours: 4334
- Engines: CONT MOTOR O-470 SERIES 230 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Elizabeth A. Fiala
- Registered owner: Fiala Thomas
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, February 1, 2010, 2 hours before
- Departed: M02, Dickson, TN
- Destination: TN08, Oliver Springs, TN
- Flight plan: IFR
- Airport: TN08, Oliver Springs Airport, runway 33, 2,800 × 200 ft, grass/turf

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 57; injuries: minor; private; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review November 18, 2009; seat: left; flight hours: 1,519 total, 660 in this make and model, 1,482 as pilot in command, 35 in the last 90 days, 19 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 200° at 3 knots
- Visibility: 10 statute miles
- Lowest ceiling: 6,000 ft broken
- Temperature: 73 °F, dew point 66 °F
- Altimeter: 30.05 inHg
- Observed at: OQT, 3 nm away

## 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 20100531035949A](https://openairdocs.org/incident/20100531035949A), May 31, 2010: Cessna 182H, Oliver Springs, TN, Substantial damage. N8311S touched down beyond the last 1/3 of runway 33 @ TN08 (pvt) Oliver Springs, TN. Heavy braking was applied on the grass airstrip up to a point…

## Other investigations on N8311S (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 CHI67D0583](https://openairdocs.org/ntsb/CHI67D0583), Sep 4, 1966: Cessna 182 (N8311S), Macomb, IL, substantial damage

## Docket (10 files)

The files NTSB released with the investigation on October 21, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76149. 8.3 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 669 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40331113&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Statements (item 2, .PDF, 248 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330561&FileExtension=.PDF&FileName=Statements-Redacted.PDF
- DUATS Flight Plan and Weather Briefing (item 3, .PDF, 2.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40331254&FileExtension=.PDF&FileName=DUATS%20Flight%20Plan%20and%20Weather%20Briefing-Redacted.PDF
- FAA Inspector Statement (item 4, .PDF, 59 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330841&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement-Redacted.PDF
- Sheriff Report (item 5, .PDF, 237 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330657&FileExtension=.PDF&FileName=Sheriff%20Report-Redacted.PDF
- Photo 1 View looking towards approach end of runway 15. Photo FAA (item 6, .PDF, 903 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330665&FileExtension=.PDF&FileName=Photo%201%20View%20looking%20towards%20approach%20end%20of%20runway%2015.%20Photo%20FAA-Master.PDF
- Photo 2 View Looking down runway 33. Photo FAA (item 7, .PDF, 924 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330667&FileExtension=.PDF&FileName=Photo%202%20View%20Looking%20down%20runway%2033.%20Photo%20FAA-Master.PDF
- Photo 3 View looking at top of right wing of airplane down in the ditch. Photo FAA (item 8, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330668&FileExtension=.PDF&FileName=Photo%203%20View%20looking%20at%20top%20of%20right%20wing%20of%20airplane%20down%20in%20the%20ditch.%20Photo%20FAA-Master.PDF
- Photo 4 View of airplane in water in the ditch. Photo FAA (item 9, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330669&FileExtension=.PDF&FileName=Photo%204%20View%20of%20airplane%20in%20water%20in%20the%20ditch.%20Photo%20FAA-Master.PDF
- Photo 5 Close up view of structural damage to right wing. Photo FAA (item 10, .PDF, 585 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40330670&FileExtension=.PDF&FileName=Photo%205%20Close%20up%20view%20of%20structural%20damage%20to%20right%20wing.%20Photo%20FAA-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.
