FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL93FA107 · Cessna TP206

10 Jun 1993 · EPWORTH, GA, United States

Cessna TP206 · Accident: in flight collision with object while maneuvering

From Martin Campbell Field (1A3) to McMinn County Airport (MMI)

Report a problem

Event

NTSB case
ATL93FA107
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
2 · all aircraft and ground
Ground fatalities
0
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 TP206

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
N5719J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Martin Campbell Field (1A3), COPPERHILL, TNTo McMinn County Airport (MMI), Athens, TN
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
Maneuvering
First occurrenceThe 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
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Clearance, misjudged

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

ACCORDING TO THE PILOT'S WIFE, THE PILOT WOULD CUSTOMARILY OVERFLY HIS HOME UPON RETURNING FROM A FLIGHT. BUT, AT THE TIME OF THIS ACCIDENT, THE PILOT WAS ON THE DEPARTURE LEG OF THE FLIGHT AND HIS WIFE WAS NOT EXPECTING A FLYBY. THE PILOT'S WIFE WAS IN THE FAMILY'S GARDEN WHEN SHE OBSERVED THE AIRPLANE AS IT APPROACHED FROM THE NORTH; THE AIRPLANE FLEW OVER HER POSITION AND SHE WAVED AT HER HUSBAND. THE PILOT'S WIFE ALSO REPORTED THAT THE AIRPLANE WAS SEVERAL FEET ABOVE THE TREES WHEN THE PILOT STARTED A LEFT TURN. THE AIRPLANE WAS OBSERVED UNTIL IT COLLIDED WITH TREES ON A RIDGE SOUTHEAST OF THE PILOT'S WIFE'S POSITION. SUBSEQUENTLY, THE AIRPLANE FELL TO THE GROUND AND BURST INTO FLAMES. EXAMINATION OF THE AIRFRAME FAILED TO DISCLOSE A MECHANICAL MALFUNCTION OR A COMPONENT FAILURE.

Probable cause

THE PILOT'S FAILURE TO MAINTAIN VERTICAL CLEARANCE ABOVE THE TREES WHILE MANEUVERING WHICH RESULTED IN THE COLLISION WITH TREES.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL93FA107
Event ID
20001211X12523
Case number
ATL93FA107
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 22abd43abab430fa8c5bcbe2174f78ab9057d78af458c84ef3b4ce1962ee99de; retrieved 2026-09-21T00:31:45.705Z.