CEN20LA402 · Piper PA46 310P
KMAC Braco Piper PA46 310P · Accident: loss of engine power (total) en route
From Horseshoe Bay Resort Airpark (KDZB) to Natchitoches Regional Airport (KIER)
Event
- NTSB case
- CEN20LA402
- 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
- 4 · 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
- Visual Meteorological Cond
Piper PA46 310P
- Aircraft type
- Piper PA46
- 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
- N236KM
- Operator
- KMAC Braco
- Onboard fatalities
- Unknown
- Route
- From Horseshoe Bay Resort Airpark (KDZB), Horseshoe Bay, TXTo Natchitoches Regional Airport (KIER), Natchitoches, LA
- Aircraft age
- About 36 years (built 1984)
- 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 engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft power plant
- 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
While in cruise flight at 19,000 ft mean sea level (msl), the pilot declared an emergency to air traffic control and stated that the airplane had lost engine power and that he needed to divert. The pilot elected to divert to an airport that was about 5 miles south of his position. Archived automatic dependent surveillance-broadcast data and commercially available flight track data showed that a descent was initiated from 19,000 ft and the airplane proceeded directly to, and circled around, the airport one time while descending. The last data point showed the airplane at 1,250 ft msl (about 750 ft above ground level) and about 1 mile north of the approach end of the runway. From the cruise altitude of 19,000ft until the last data point, about 12 minutes and 45 seconds had elapsed, which equated to an average descent rate of about 1,392ft per minute.
Witnesses located about 1/4 mile south of the end of the runway on a miniature golf course noticed the propeller on the airplane was not turning. They stated that they saw the airplane in a “really hard” left bank; the nose of the airplane dropped, and it impacted the ground in a near vertical attitude. The airplane came to rest along a road about 200 ft south of the airport property. The airplane impacted the terrain in a nose low, near vertical attitude and sustained substantial damage to fuselage and both wings. It is likely that, based on the location of the runway, relative to the miniature golf course, the pilot initiated the left bank to avoid bystanders on the ground and inadvertently exceeded the wing’s critical angle of attack, which resulted in an aerodynamic stall.
The airplane was equipped with an engine trend monitor (ETM), which captured various events concerning the accident flight, including engine start, operating limit exceedances, and power checks. The ETM captured a power check while the airplane was at 19,100 ft. About 3 minutes 32 seconds later, an engine off event was recorded. The ETM further captured a logon message, which was consistent with the power being cycled, at an altitude of 3,542 ft, 9 minutes, 52 seconds later. The ETM did not record any start attempts between the logged engine off event and when power was lost to the unit. A postaccident examination of the airframe, engine, and accessories did not reveal any mechanical malfunctions or anomalies that would have precluded normal operation. Although it cannot be determined whether a restart attempt would have been successful, the data were consistent with a restart not being attempted.
Both the engine failure and power off landing checklists contained instructions for the pilot to establish the airspeed at 90 knots; however, when the winds aloft were applied to the reported groundspeeds, it was evident this did not occur. Furthermore, the power off landing checklist instructed the pilot to be about 1,500 ft above the airport on the downwind leg; however, data indicate that the airplane was about 5,000 ft above the airport on the downwind leg. The rapid descent from 5,000 ft on the downwind leg to about 750 ft above ground level on the final leg resulted in an unstabilized approach.
Probable cause
The loss of engine power for reasons that could not be determined and the pilot’s failure to maintain control of the airplane which resulted in an aerodynamic stall and spin. Contributing to the accident was the pilot’s failure to establish and maintain a proper glidepath.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20LA402
- Event ID
- 20200920X30723
- Case number
- CEN20LA402
- 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: investigation status, coordinates, cause areas. 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: 31950a71344460f2e35cae3117b5dc47ecfb55ebc630b233fe297cf91b49c186; retrieved 2026-09-15T07:20:11.130Z.