LAX03LA302 · Piper PA-34-220T
Piper PA-34-220T · Accident: loss of engine power on approach
From Flagstaff Pulliam Airport (FLG) to Show Low Regional Airport (SOW)
Event
- NTSB case
- LAX03LA302
- 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-34-220T
- Aircraft type
- Piper PA-34
- 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
- N4167B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Flagstaff Pulliam Airport (FLG), Flagstaff, AZTo Show Low Regional Airport (SOW), Show Low, AZ
- 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 · VFR go-around
- 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 engine power
- 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
- Pilot in command(cfi) › Wrong runway, selected
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During a go-around attempt from a downwind approach for landing the airplane descended to ground impact on the runway. The certified flight instructor (CFI) said that after turning inbound from the procedure turn during a practice NDB-A approach he idled the left engine to simulate an engine failure. The student executed the emergency procedures for a simulated engine out approach. The CFI set the power on the left engine to simulate zero thrust. The airplane was configured with the landing gear up and the flaps were set at 10 degrees, for an intended circle to land approach to runway 03. Upon entering the traffic pattern the student was too close to the runway on the downwind leg and overshot the runway and was high turning base to final. The student pulled the engines to idle, extended the flaps to 25 degrees, lowered the landing gear, and completed the landing checklist. The CFI called for a go-around and the student applied both throttles forward but the CFI noticed they "weren't really climbing." The CFI confirmed that both throttles were forward and then retracted the landing gear and the flaps; the airplane was not climbing and the student in the back seat told them to "watch the airspeed." They pushed the nose forward attempting to maintain the airspeed above 66 knots. The airplane continued to descend until contacting the ground. The airplane came to rest in the dirt area between the taxiway and runway 6/24. Runway 24 was the active runway at the time. The winds were from 280 degrees at 12 knots, and the density altitude was calculated at 9,080 feet. The runway selected by the CFI, runway 3, was 3,930 feet long and 60 feet wide; it was not the active runway, and was not equipped with runway lighting. Post accident examination of the airplane revealed that the left propeller signatures were consistent with rotation at ground impact, but not at a significant power level. The right propeller signatures were consistent with high power. After substituting another propeller, the left engine was placed onto a test stand; it started within a few propeller blade revolutions, responded to throttle operation, and ran smoothly without hesitation. The pilot operating handbook for the airplane calls for the flaps to be raised on both normal and single engine go-arounds; however, a cautionary note says that a loss of altitude may result until a climb is established. The manufacturer calculated that the airplane should have had a positive climb rate of 90 feet per minute with the gear and flaps retracted and the left engine at zero thrust.
Probable cause
The pilot-in-command's (CFI) selection of the wrong runway (downwind) for the approach and landing. The failure of the left engine to respond to throttle application for undetermined reasons during the go-around was also causal. The high density altitude was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03LA302
- Event ID
- 20031009X01696
- Case number
- LAX03LA302
- 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 2003-10-01.
- API snapshot SHA-256: 00aae31b1c72ab757b070c776a8794f0b057db3fea131d965d2f87485cb03a60; retrieved 2026-09-22T08:25:24.527Z.