ERA10CA447 · Cessna T206H
Otter Creek Aviation Cessna T206H · Accident: landing area overshoot
From Fulton County Airport Brown Field (FTY) to Clayton, GA (no airport)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA10CA447
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna T206H
- Aircraft type
- Cessna 206
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N6075M
- Operator
- Otter Creek Aviation
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Fulton County Airport Brown Field (FTY), Fulton County, GATo Clayton, GA (no airport)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Landing area overshoot
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, he circled and surveyed the private grass strip three times prior to his approach. The airplane touched down approximately midfield and bounced airborne. It touched down again about two-thirds of the way down. He applied full brake pressure, although it was ineffective due to the wet grass landing surface. The airplane continued off the departure end of the runway, through a wooden fence, and came to rest 25 feet beyond the fence. The pilot reported that there were no mechanical anomalies with the airplane and that he chose not to abort the landing due to rising terrain at the departure end of the landing strip.
Probable cause
The pilot's improper touchdown point while landing on the wet grass.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA447
- Event ID
- 20100827X75916
- Case number
- ERA10CA447
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 644df46ecb3d0f4b0f088bdd91165173df79547a72a5f3d85fe5237fb8b95387; retrieved 2026-09-15T14:59:03.843Z.