MIA02FA044 · Piper PA-46-350P
Piper PA-46-350P · Accident: loss of control in flight on approach
From Dothan Regional Airport (DHN) to Raleigh-Durham International Airport (RDU)
Event
- NTSB case
- MIA02FA044
- 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
- 3 · 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
- Instrument Meteorological Cond
Piper PA-46-350P
- Aircraft type
- Piper PA-46
- 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
- N41003
- Operator
- Thomas D. Motley · private individual
- Onboard fatalities
- Unknown
- Route
- From Dothan Regional Airport (DHN), Dothan, ALTo Raleigh-Durham International Airport (RDU), Raleigh, NC
- 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 missed 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
- Loss of control in flight
- 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 › Aircraft control, not maintained
- Pilot in command › Spatial disorientation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight was cleared for the ILS approach to runway 5R. The flight was at mid runway, at 2,100 feet, heading 049 degrees, at a speed of 163 knots, when the pilot stated "...missed approach." He was instructed to maintain 2,000, and to fly runway heading. Radar showed N41003 started a right turn, was flying away from the airport/VOR, descending. At a point 0.57 miles from the airport/VOR, the flight had descended to 1,500 feet, was turning right, and increasing speed. The flight had descended 400 feet, and had traveled about 0.32 miles in 10 seconds. When radio and radar contact were lost, the flight was 2.35 miles from the airport/VOR, level at 1,600 feet, on a heading of 123 degrees, and at a speed of 169 knots. The published decision height (DH) was 620 feet mean sea level (msl). The published minimum visibility was 1/2 mile. The published Missed Approach in use at the time of the accident was; "Climb to 1,000 [feet], then climbing right turn to 2,500 [feet] via heading 130 degrees, and RDU R-087 [087 degree radial] to ZEBUL Int [intersection] and hold." A witness stated that the aircraft was flying low, power seemed to be in a cruise configuration, and maintaining the same sound up until the crash. The reported weather at the time was: Winds 050 at 5 knots, visibility 1/2 statute mile, obscuration fog and drizzle, ceiling overcast 100, temperature and dew point 11 C, altimeter 30.30 in HG. At the time of the accident the pilot had 10 total flight hours in this make and model airplane; 33 total night flight hours; and 59 total instrument flight hours.
Probable cause
the pilot's failure to maintain control of the airplane, due to spatial disorientation, while performing a missed approach, resulting in an uncontrolled descent, and subsequent impact with a tree and a house. Factors in this accident were dark night, fog, drizzle, the pilot's lack of total instrument time, and his lack of total experience in this type of aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA02FA044
- Event ID
- 20011218X02406
- Case number
- MIA02FA044
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2001-12-13.
- API snapshot SHA-256: 8b7317fe8b63d7e0df1baefcd4e3cb5c30723e7a42f9a6dfbbc4036d481fe3fe; retrieved 2026-09-20T20:15:54.667Z.