NYC05FA028 · Piper PA-31-350
Piper PA-31-350 · Accident: in flight collision with object on approach
From McGhee Tyson Airport (TYS) to James M. Cox Dayton International Airport (DAY)
Event
- NTSB case
- NYC05FA028
- 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
- Charter & commuter
- 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-31-350
- Aircraft type
- Piper PA-31
- 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
- N54316
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From McGhee Tyson Airport (TYS), Knoxville, TNTo James M. Cox Dayton International Airport (DAY), Vandalia, 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 135: Air Taxi & Commuter
- 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
- 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
- Object › Tree(s)
- Pilot in command › Altitude/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 pilot was conducting a cargo flight in night instrument meteorological conditions, and was cleared for the ILS Runway 6L approach. The pilot reported that he was established on the localizer, and the control tower stated that the touchdown and mid-point "RVR" was 1,800 feet, and the roll-out "RVR" was 1,600 feet. The pilot also was instructed, and acknowledged, to make a right turn off the runway, after landing. There were no further communications from the airplane. The airplane's last radar target was observed at an altitude of 1,200 feet msl, and a ground speed of 130 knots. The airplane impacted trees, and came to rest inverted on airport property, on a bearing of 053 degrees, and a distance of 1/2 mile to the runway. Examination of the airplane did not reveal any pre-impact mechanical failures. A weather observation taken at the airport about the time of the accident included, winds from 140 degrees at 9 knots, 1/8 mile visibility, runway 6L visual range variable between 1,800, and 2,000 feet in fog, vertical visibility 100 feet, and a temperature and dew point 54 degrees F. The airport elevation was 1,009 feet msl. Review of the approach diagram for the ILS Runway 6L approach revealed a decision height of 1,198 feet msl, and an approach minimum of 1,800 feet runway visual range (RVR), or 1/2 mile visibility. The pilot had accumulated about 3,800 hours of total flight experience, which included about 350 hours in the same make and model as the accident airplane, and 250 total hours logged in instrument meteorological conditions.
Probable cause
The pilot's failure to maintain adequate altitude\clearance while on approach, which resulted in an in-flight collision with trees. Factors in the accident were the fog and low ceiling conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC05FA028
- Event ID
- 20041214X01985
- Case number
- NYC05FA028
- 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: a9fbab39bf970575b54dd630a6580817dd6c5aeea8e2975235dc1752374072cf; retrieved 2026-09-18T12:59:34.473Z.