FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC01FA089 · Cessna 182Q

24 Mar 2001 · Dixon, KY, United States

Tri-State Aero Cessna 182Q · Accident: in flight collision with terrain/water during an uncontrolled descent

From Evansville Regional Airport (EVV) to an unrecorded destination

Report a problem

Event

NTSB case
NYC01FA089
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
1 · 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 182Q

Aircraft type
Cessna 182
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
N4752N
Onboard fatalities
Unknown
Route
From Evansville Regional Airport (EVV), Evansville, INTo not recorded
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
Uncontrolled descent
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 terrain/water
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, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The accident site was located on the pilot's brother-in-law's property. The brother-in-law stated, "I was in the house and heard the plane buzz the house. It sounded very low at the time. The plane didn't get outside hearing distance as I could hear it banking. Shortly, [thereafter] I heard it hit the ground. Looking out, it was totally engulfed in flames. Power was 'ON' at impact. I did not hear the engine under stress or missing." The airplane came to rest upright in a field approximately 495 feet west of two trees that were about 75 feet tall and located on a hill. Several freshly broken branches were observed near the top of the tree to the north. Additionally, the airplane's left wing tip, strobe light and strobe light power supply were observed on the ground near the tree, along with several broken branches of varied thickness. Examination of the wreckage did not reveal any pre-impact malfunctions. The pilot reported 600 hours of total flight experience on his most recent FAA second class medical certificate, which was issued about 6 weeks prior to the accident. Additionally, at that time he reported he had flown 90 hours in the previous 6 months. Winds reported at an airport about 22 miles north of the accident site were from 340 degrees at 12 knots, with 16 knot gusts.

Probable cause

The pilot's failure to maintain adequate clearance while maneuvering, which resulted in an in-flight collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC01FA089
Event ID
20010329X00668
Case number
NYC01FA089
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, 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: d3bea568f5540533ccc7fc1b827fd16726e9b0cead6ede970921c710e63f217e; retrieved 2026-09-20T20:37:48.814Z.