Air Excursions Piper PA-32-300 accident
Piper PA-32-300 · Accident: loss of engine power (total) en route
From Juneau International Airport (PAJN) to Gustavus, AK
Event
- NTSB case
- ANC12LA058
- 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
- Charter & commuter
- 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-32-300
- Aircraft type
- Piper PA-32
- 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
- N8908N
- Operator
- Air Excursions
- Onboard fatalities
- Unknown
- Route
- From Juneau International Airport (PAJN), Juneau, AKTo Gustavus, AK
- 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 135: Air Taxi & Commuter
- 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 · cruise
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The scheduled passenger flight was about 11 miles from its destination airport when the airplane's engine began to lose power and vibrate. After completing the "Engine Power Loss In-Flight" emergency checklist, and with no improvement in engine power or the vibration, the pilot elected to shut down the engine and performed a forced landing on a beach. During the landing, the airplane's nose landing gear folded back under the airplane, and the engine firewall sustained substantial damage.
An examination of the engine revealed that the crankshaft fractured forward of the #6 bearing journal on the crankshaft through the counterweight web. The fracture surfaces were all consistent with fatigue; however, the cause of the fatigue crack initiation could not be determined.
Probable cause
The fatigue failure of the engine crankshaft for reasons that could not be determined during postaccident metallurgical examination.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC12LA058
- Event ID
- 20120627X90622
- Case number
- ANC12LA058
- 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: 9ca418d455962717dc6c27c8e0110c594df05068ce939bd593805543dbaba6b8; retrieved 2026-09-15T18:38:57.249Z.