ATL85FA055 · Piper PA-32-300
Piper PA-32-300 · Accident: in flight collision with terrain/water on approach
From Humphreys County Airport (0M5) to CVG · Cincinnati, OH
Event
- NTSB case
- ATL85FA055
- 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
- Instrument Meteorological Cond
Piper PA-32-300
- Aircraft type
- Piper PA-32
- 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
- N5211S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Humphreys County Airport (0M5), Waverly, TNTo CVG · Cincinnati, OH
- 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
- Approach · IFR initial approach
- 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 › Aircraft preflight, inadequate
- Pilot in command › Decision height, inattentive
- Pilot in command › IFR procedure, not followed
- Pilot in command › Navigation receiver, not identified
- Pilot in command › Self-induced pressure
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ACFT FERRIED VFR BY OWNER. RADIOS REPAIRED BEFORE DEPARTURE, GLIDE SLOPE RECEIVER FOUND INOP. AT FUEL STOP WX WAS FORECAST IFR FOR DESTINATION. AN IFR INSTRUCTOR WAS THEN HIRED FOR THE REMAINING FLT. OWNER SHOWED WORK ORDER TO CFI WHO INCORRECTLY CONCLUDED THAT THE GLIDE SLOPE HAD BEEN REPAIRED. CFI RECALLED WX WAS FORECAST AS 600 FT CEILING AT DESTINATION. NO RECORD FOUND OF HAVING RECEIVED CURRENT WX OF 200 FT CEILING, 1-1/4 MI VIS PRIOR TO APCH. CFI STATED A 500 FPM DESCENT AT 90 KTS WAS USED FOR THE APCH. HE REPORTED FLYING THE ILS RWY 36 APCH AND POINTED OUT TO THE OWNER THAT THE LOCALIZER AND GLIDE SLOPE NEEDLES WERE CENTERED WHEN 2 MILES FROM THE RWY. POST CRASH TEST OF THE GLIDE SLOPE RECEIVER SHOWED IT WAS STILL INOPERATIVE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL85FA055
- Event ID
- 20001214X41697
- Case number
- ATL85FA055
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1984-12-14.
- API snapshot SHA-256: 07617db6adce0d415cad972b204b686ddf3052e4f04b504aeb448c892f51d375; retrieved 2026-09-21T05:12:49.506Z.