ERA14FA058 · Piper PA-46-310P
Culbair Piper PA-46-310P · Accident: loss of control in flight en route
From Morristown Municipal Airport (MMU) to DeKalb Peachtree Airport (PDK)
Event
- NTSB case
- ERA14FA058
- 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
- Instrument Meteorological Cond
Piper PA-46-310P
- 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
- N87NF
- Operator
- Culbair
- Onboard fatalities
- Unknown
- Route
- From Morristown Municipal Airport (MMU), Morristown, NJTo DeKalb Peachtree Airport (PDK), Atlanta, GA
- Aircraft age
- About 26 years (built 1987)
- 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
- En route
- Defining eventThe 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Psychological
- Personnel issues › Task performance
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 filed an instrument flight rules flight plan for the flight and was communicating with an air route traffic control center controller en route. The controller verified that the pilot had the local weather information for the intended destination and then he queried the pilot about the airplane's heading (which was north of the direct heading), and the pilot reported that he was having trouble with the autopilot. He then asked the pilot if he was able to hold the assigned altitude of 8,000 ft mean sea level (msl), and the pilot responded that he could; however, the airplane descended below 8,000 ft msl, and the controller then issued an altitude of 7,000 ft msl and a heading of 200 degrees. There was no response from the pilot, and radar contact was lost. Shortly after, the airplane wreckage was found.
According to air traffic control radar data, the airplane turned left and then right before entering a descending left turn. A trajectory and performance study determined that, during the flight's final 18 seconds, the airplane descended from about 8,000 to 2,200 ft msl, accelerated to about 300 knots indicated airspeed, and then broke up. According to the Pilot's Operating Handbook, the airplane's maximum operating limit speed was 172 knots.
Examinations of the airframe, engines, and autopilot revealed no preimpact mechanical malfunctions that would have precluded normal operations, and there was no evidence of medical impairment that would have affected the pilot's performance. The pilot held an instrument rating; however, investigators were unable to determine the extent of the pilot's recent night or instrument flight experience.
Although postaccident testing did not reveal any anomalies with the autopilot system, the pilot should have been able to disable the autopilot if it was experiencing a problem and then continue to fly the airplane. However, given the available data and his conversation with the controller, it is likely that the pilot became focused on the autopilot system and diagnosing the reported problem. Dark (moonless) night conditions prevailed for the flight, and, about the time of the accident, instrument meteorological conditions with restricted visibility due to rain prevailed. Given the pilot's distraction, the weather conditions encountered during the flight, and the sustained descending left turn, it is likely that the pilot experienced spatial disorientation and then lost control of the airplane.
Probable cause
The pilot’s in-flight loss of airplane control due to spatial disorientation while operating in dark night instrument meteorological conditions, which resulted in the exceedance of the airplane’s design stress limitations and a subsequent in-flight breakup. Contributing to the accident was the pilot’s distraction by the reported malfunction of the autopilot system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14FA058
- Event ID
- 20131202X13615
- Case number
- ERA14FA058
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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 2013-12-03.
- API snapshot SHA-256: 49b8d42ec7c99b1443ce58b2e1322ce724bc64152098fd4801af9c0513b245dd; retrieved 2026-09-14T16:08:10.888Z.