DEN08IA044 · Piper PA-46-310P
Piper PA-46-310P · Incident: total loss of engine power (mechanical failure) en route
From Aspen-Pitkin County Airport (Sardy Field) (ASE) to Denver International Airport (DEN)
Event
- NTSB case
- DEN08IA044
- 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
- Incident
- 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-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
- N47BC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aspen-Pitkin County Airport (Sardy Field) (ASE), Aspen, COTo Denver International Airport (DEN), Denver, CO
- 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
- En route · climb to cruise
- 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
- Total loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Engine assembly, crankshaft › Failure, total
- Engine assembly, crankshaft › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During initial climb at 16,000 feet, the pilot noticed oil droplets forming on his windscreen. On seeing the oil, he contacted air traffic control, declared an emergency, and began a standard rate, 180-degree turn, back to the airport. As he completed the turn, he heard a "boom," felt a shutter, and then the windscreen was covered with oil. The pilot said he may have noted a pitch up with the bang, but he immediately got on the best glide speed, 90 knots, and began retracing his ground track via the global positioning system (GPS) back to the airport. The airplane landed uneventfully back to the airport. An examination of the airplane showed minor damage to the front of the cowling, and the engine showed the crankshaft fractured aft of the flange. The propeller and spinner, and the forward part of the crankshaft were missing. Several months after the incident, the separated propeller assembly and crankshaft were located. Examination of the engine revealed the crankshaft was fractured through, aft of the propeller flange. The fracture of the crankshaft was caused by a fatigue crack that stemmed from the aft relief radius of the propeller flange. The surface of the aft radius contained no evidence of mechanical damage and the fatigue crack emanated from multiple origins over a wide area, indicating that a great amount of stress was necessary to initiate the fatigue crack. The reason for the crack initiation could not be determined. The fatigue crack origin area was located in the relief radius in line with the axis of the propeller blades, consistent with forward and aft bending stresses imposed by the blades during flight. The location indicates a possibility that the blades were out of balance while rotating or that the crankshaft was somehow damaged in the past. No evidence of fretting was noted between the faces of the crankshaft propeller flange and the alternator pulley. The propeller assembly was attached firmly to the crankshaft.
Probable cause
The failure of the crankshaft due to fatigue. The fatigue crack initiation was not determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN08IA044
- Event ID
- 20071231X02008
- Case number
- DEN08IA044
- 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: investigation status, coordinates. 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: 2715b080ee7b996ea47f75ca53e781468f1b2d2d6d4c030be33b9ce418cf6046; retrieved 2026-09-22T03:12:50.938Z.