DEN02LA015 · Piper PA-28-235
Piper PA-28-235 · Accident: loss of control on ground/water during landing
From Grand Junction Regional Airport (GJT) to Crested Butte Airpark (0CO2)
Event
- NTSB case
- DEN02LA015
- 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-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
- N8704W
- Operator
- Jerry W. Elliott · private individual
- Onboard fatalities
- Unknown
- Route
- From Grand Junction Regional Airport (GJT), Grand Junction, COTo Crested Butte Airpark (0CO2), Crested Butte, 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
- Landing · landing roll
- 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
- Loss of control on ground/water
- 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
- Landing gear, normal brake system › Frozen
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said the runway was covered by a thin layer of snow that had recently been plowed. The airplane touched down, rolled about 10 feet, and began "pulling" to the left. The pilot applied right rudder but to no avail. He applied full right aileron and lifted the left wing to clear an 18-inch snow bank on the side of the runway. The airplane traveled another 100 feet before the left wing lost lift and settled back down to the runway. The airplane "went through snow," spun around, and stopped 20 feet off the side of the runway. The pilot found a skid mark on the runway made by the left wheel. He suspected the wheel may have gotten wet when he had taxied for takeoff and the brake froze. He said the temperature at 12,000 feet was -20 degrees F.
Probable cause
a wet brake that later froze resulting in a loss of directional control on landing. A contributing factor was the snow bank.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN02LA015
- Event ID
- 20011220X02430
- Case number
- DEN02LA015
- 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. 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: 98d4e608dc452c31c793f1f5473a9ba3582cc7ad151c8160df910a1402293459; retrieved 2026-09-22T11:14:23.106Z.