CEN14FA328 · Piper PA 28-235
Piper PA 28-235 · Accident: loss of control in flight en route
From Rocky Mountain Metropolitan Airport (KBJC) to Canyonlands Regional Airport (KCNY)
Event
- NTSB case
- CEN14FA328
- 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
- 3 · 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 28-235
- Aircraft type
- Piper PA-28
- 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
- N8814W
- Operator
- Kerker James e
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (KBJC), Broomfield, COTo Canyonlands Regional Airport (KCNY), Moab, UT
- Aircraft age
- About 50 years (built 1964)
- 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 · 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 control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A customer service manager at the fixed-base operator (FBO) reported that the pilot, who was preparing for the cross-country flight, was looking for information on how to fly over the mountains. At that time, there was no one at the FBO who could provide him information on mountain flying, and no posted information was available. She later heard that the pilot planned to take off under visual flight rules and fly through the mountains along the interstate.
Radar data showed that the airplane took off to the west, turned south, and then climbed to about 10,400 ft mean sea level (msl). Once the airplane reached the interstate, it turned west toward the mountains and followed the interstate. About 25 minutes after taking off, when the airplane was at 10,200 ft msl, radar contact with the airplane was lost. Witnesses near the accident site were consistent with their accounts, which indicated that the airplane was flying between about 11,000 and 11,500 ft msl (200 to 300 ft above the ground) with the engine producing power. The airplane was in a nose-high attitude when it started turning left away from rising terrain. The airplane then turned about 180 degrees, rolled over to the left, and entered a steep dive before impacting trees and terrain. One of the witnesses indicated that, before the left turn, the airplane's path seemed pretty flat with little gain in altitude. A postimpact fire ensued, which consumed most of the airplane.
A postaccident examination confirmed flight control continuity and revealed no preimpact anomalies with the engine or airplane systems that would have precluded normal operation. The pilot did not use any weather or flight planning services. No evidence was found that the pilot had obtained training in mountain flying. A weather model determined that, at the time of the accident, the density altitude was about 12,850 ft, which would have reduced the airplane's climb rate by more than 90 percent. It is likely that, as the pilot attempted to cross over the mountainous terrain, he raised the airplane's nose such that the airplane was beyond its critical angle-of-attack, which, combined with the airplane's decreased climb performance, led to an aerodynamic stall and loss of control.
Probable cause
The pilot’s inability to maintain a climb while maneuvering the airplane in high-density altitude conditions that degraded the airplane’s climb performance and his exceedance of the airplane’s critical angle-of-attack, which led to an aerodynamic stall and loss of control. Contributing to the accident was the pilot’s inadequate preflight planning and his decision to fly into mountainous terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14FA328
- Event ID
- 20140630X24850
- Case number
- CEN14FA328
- 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: aa6aee5076dfbe97f0e0eadcd11feb57703259472da0843f86b114497b32af62; retrieved 2026-09-14T17:20:43.595Z.