ANC18LA016 · Piper PA 23-250
Piper PA 23-250 · Accident: loss of control in flight on approach
From Knoxville Downtown Island Airport (DKX) to Knoxville Downtown Island Airport (DKX)
Event
- NTSB case
- ANC18LA016
- 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
- 0 · 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 PA 23-250
- Aircraft type
- Piper PA-23
- 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
- N40285
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Knoxville Downtown Island Airport (DKX), Knoxville, TNTo Knoxville Downtown Island Airport (DKX), Knoxville, TN
- Aircraft age
- About 44 years (built 1973)
- 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 · VFR go-around
- 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
- 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
- Substantial
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a simulated single-engine instrument approach in a multi-engine airplane, the flight instructor, who was seated in the right seat, told the multi-engine rated pilot receiving instruction, who was seated in the left seat, to go around. The pilot applied full power to the right engine and attempted to fly the pattern with a simulated left engine failure. Shortly after, while the airplane was in a left crosswind turn, the left engine lost total power. The instructor observed that the left propeller was stationary and took control of the airplane.
The instructor chose to fly at minimum controllable speed (Vmc) rather than the recommended best single-engine rate of climb speed (Vyse) and attempted to restart the failed engine rather than perform the airplane manufacturer's approved engine-out procedures. Unable to restart the left engine, he attempted to maneuver the airplane for a landing but was unable and flew toward rising terrain. Approaching a residential area, the instructor maneuvered the airplane to avoid a house, and the airplane subsequently impacted trees, fell to the ground, and came to rest on top of an automobile. The instructor stated that after the accident, he returned to the airplane to shut off the fuel and electrics when he noticed the left fuel selector was between the on and off position.
A postaccident examination revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. However, a lack of fuel was observed in the left engine's fuel system forward of the fuel injection servo.
Based on the observed intermediate position of the left fuel selector after the accident, the lack of fuel in the fuel system forward of the fuel injection servo, and the lack of mechanical malfunctions or failures noted during the wreckage examination, it is likely that the left engine lost total power due to fuel starvation. The manufacturer's approved procedures for an engine failure during takeoff included, among other things, maintaining a best rate of climb airspeed. A review of the manufacturer's pilot's operating manual indicated that even with a total loss of engine power on the left engine, the airplane would have been able to climb about 520 ft per minute had the required pilot inputs been made. The instructor failed to comply with the published engine-out procedures and recommended airspeeds, which led to the lack of directional control, collision with trees, and impact with the ground.
Probable cause
The flight instructor’s failure to comply with published engine-out procedures and recommended airspeeds, which resulted in a lack of directional control, collision with trees, and impact with the ground; the left engine lost total power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC18LA016
- Event ID
- 20171219X65947
- Case number
- ANC18LA016
- 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. 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: a9ba56c345977cb07d75f8c7732231deacc9ba8796156e54812ebc9f54ad538c; retrieved 2026-09-16T06:11:46.193Z.