FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14LA476 · Piper PA-46-350P

3 Sept 2014 · Cortez, CO, United States

Philburto Aviation Piper PA-46-350P · Accident: aerodynamic stall/spin during landing

From Cortez Municipal Airport (CEZ) to Cortez Municipal Airport (CEZ)

Report a problem

Event

NTSB case
CEN14LA476
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-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
N747TH
Onboard fatalities
Unknown
Route
From Cortez Municipal Airport (CEZ), Cortez, COTo Cortez Municipal Airport (CEZ), Cortez, CO
Aircraft age
About 15 years (built 1999)
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
Landing
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
Aerodynamic stall/spin
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 oper/perf/capability
  • Aircraft › Aircraft propeller/rotor
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The accident occurred during a local instructional flight to satisfy the commercial pilot's annual insurance currency requirements in the accident airplane. The flight instructor reported that the pilot was demonstrating a simulated loss of engine power during initial climb and return for a downwind landing. During initial climb, upon reaching 1,200 ft above ground level (agl), the flight instructor reduced engine power to flight idle and feathered the propeller. In response, the pilot reduced airplane pitch and entered a left, 45-degree-bank turn back toward the airport. The flight instructor stated that, upon rolling wings level, the airplane appeared to be lower than he had expected as it glided toward the runway; however, he believed there was sufficient altitude remaining to safely land on the runway and told the pilot to continue without increasing the engine power. The flight instructor ultimately decided to abort the maneuver as the airplane crossed over the runway threshold at 40 ft agl. The flight instructor advanced the engine power lever to the full-forward position and increased airplane pitch to arrest the descent; however, he did not perceive an increase in engine thrust. Without an increase in engine thrust and with the increased pitch, the airplane's airspeed decreased rapidly, and the airplane entered an aerodynamic stall about 30 ft above the runway. The airplane impacted the runway before sliding into a grassy area.

The flight instructor reported that he did not recall advancing the propeller control when he decided to abort the maneuver, and, as such, the perceived lack of engine thrust was likely because the propeller remained feathered after he increased engine power. Additionally, the flight instructor postulated that the airplane's landing gear had not been retracted after takeoff, which resulted in a reduced climb gradient, and, as such, the airplane entered the maneuver farther away from the airport than anticipated. Further, with the landing gear extended, the airplane experienced a reduction in glide performance during the simulated forced landing. The flight instructor reported that the accident could have been prevented if he had maintained a safe flying airspeed after he took control of the airplane. Additionally, he believed that his delayed decision to abort the maneuver resulted in an insufficient margin of safety.

Probable cause

The flight instructor’s delayed decision to abort the simulated engine out maneuver, his failure to unfeather the propeller before restoring engine power, and his inadequate airspeed management, which led to an aerodynamic stall at low altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14LA476
Event ID
20140903X61913
Case number
CEN14LA476
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: 5caa58d35cc635959b8ab3d930db04fb8fa9207f837ff45472927cf2be87e085; retrieved 2026-09-16T01:42:57.812Z.