Peninsula Airways Piper PA-32-301 accident
Piper PA-32-301 · Accident: turbulence encounter en route
From False Pass Airport (PAKF) to Cold Bay Airport (PACD)
Event
- NTSB case
- ANC11LA027
- 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-301
- 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
- N81052
- Operator
- Peninsula Airways
- Onboard fatalities
- Unknown
- Route
- From False Pass Airport (PAKF), False Pass, AKTo Cold Bay Airport (PACD), Cold Bay, 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
- Turbulence encounter
- 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
- Environmental issues › Conditions/weather/phenomena
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that while descending toward his destination, the airplane encountered severe turbulence of short duration. After the turbulence passed, he made an uneventful landing at his destination airport. A postaccident examination of the airplane discovered substantial damage to the stabilator.
The wind at the destination airport was reported as 310 degrees at 9 knots, the area forecast valid at the time of the turbulence encounter forecast no significant turbulence, and there were no pilot reports of turbulence. The pilot indicated that prior to the severe turbulence; there had been no significant turbulence during the flight.
An examination of the stabilator showed that the right half was bent downward 5 to 10 degrees outboard of the fuselage attachments. No evidence of fatigue or corrosion was found.
Probable cause
An in-flight encounter with unforecast turbulence, which resulted in structural damage to the stabilator.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC11LA027
- Event ID
- 20110421X15324
- Case number
- ANC11LA027
- 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: 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 2011-04-15.
- API snapshot SHA-256: e63a055ade474e17dd295cbcb40d80e5cae9ed3033f46360cc3b70df995dbd62; retrieved 2026-09-15T16:04:59.588Z.