MIA99FA269 · Piper PA-31P
Piper PA-31P · Accident: in flight collision with object on approach
From Tupelo Regional Airport (TUP) to Louisville Winston County Airport (LMS)
Event
- NTSB case
- MIA99FA269
- 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
- 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-31P
- 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
- N100EE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tupelo Regional Airport (TUP), Tupelo, MSTo Louisville Winston County Airport (LMS)
- 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
- 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 › Minimum descent altitude, disregarded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot received a weather briefing before departure and when near the destination airport, cleared for the NDB approach. The pilot reported the procedure turn inbound; published MDA is 1,300 feet msl. Witnesses on the airport reported heavy low fog and heard the pilot announce over the UNICOM frequency, 'Oh there is fog rolling into Starkville too?' One of the witnesses advised the pilot they could go to another airport due to the fog; the pilot responded he would execute the approach. The witnesses heard the engines operating at full power then heard the impact and saw a fireball. The airplane impacted the runway inverted, slid across the runway, and came to rest in grass off the runway. A postcrash fire destroyed the airplane. Tree contact approximately 972 feet northwest of the runway impact location separated approximately 51 inches of the left wing. Examination of the engines, propellers, and flight controls revealed no evidence of preimpact failure or malfunction. The pilot had twice failed his airline transport pilot checkride. The designated examiner of the second failed flight test indicated the pilot was marginal in all flight operations. The NDB was checked after the accident; no discrepancies were noted.
Probable cause
The pilot's disregard for the published minimum descent altitude resulting in tree contact and separation of 51 inches of the left wing. Findings in the investigation were the pilot's two failures of the ATP checkride in a multiengine airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99FA269
- Event ID
- 20001212X19825
- Case number
- MIA99FA269
- 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: cc9e409399439908f062aca4b960549a6ff1029b03f70e00553b24c409b03853; retrieved 2026-09-20T21:45:10.253Z.