CEN12LA414 · Cessna 172S
Rocky Mountain Flight School Cessna 172S · Accident: low altitude operation/event en route
From Sumers Airpark (GWS) to Rocky Mountain Metropolitan Airport (BJC)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN12LA414
- 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
Cessna 172S
- Aircraft type
- Cessna 172
- 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
- N917SA
- Operator
- Rocky Mountain Flight School
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Sumers Airpark (GWS), Glenwood Springs, COTo Rocky Mountain Metropolitan Airport (BJC), Broomfield, 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
- 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
- Low altitude operation/event
- 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 oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A pilot with 56 hours of pilot-in-command time was on the return leg of a cross-country flight over mountainous terrain. The pilot did not note any airplane anomalies during the startup, engine run-up, or takeoff. The pilot reported that it was a clear, calm morning, and he made the decision to fly on the left side of a canyon. The pilot indicated that when he wanted to climb out of the canyon, power increases did not seem to help, so he slowed the airplane to 70 knots indicated airspeed to minimize the turnaround radius to exit the canyon. He stated that he slowed the airplane a little more to make the turnaround and remembered feeling/seeing the airplane hit a tree. A postaccident examination of the wreckage revealed no anomalies with the flight controls or engine. A camera in the cockpit, which recorded video of the accident flight, also revealed no airplane or engine anomalies. The airplane was observed impacting trees on rising terrain. Warmer-than-standard temperatures on the day of the accident resulted in a high density altitude and reduced climb performance of the airplane.
An FAA publication, "Tips on Mountain Flying," indicated that pilots should carefully consider their experience and background before beginning a flight into mountainous terrain. It urged pilots to consider attending a recognized mountain flying course to attain the knowledge and skills needed for safe flying. The publication further stated that pilots should wait until they have at least 150 hours of pilot-in-command time before taking mountain training, as more experienced pilots have had time to become more familiar and comfortable with the airplane and with flight planning.
The pilot stated that he had received instruction on assessing canyons from a previous mountain flight. The pilot did not indicate that he attended a recognized mountain flying course.
Probable cause
The pilot's decision to fly into a mountainous area where conditions were such that the airplane was unable to climb above rising terrain. Contributing to the accident was the pilot's insufficient pilot-in-command experience and inadequate training in mountain flying.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12LA414
- Event ID
- 20120703X85443
- Case number
- CEN12LA414
- 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: 5b7b96d33760aeeda137d65c61b2ff85915acca3c8147f0352b764a428e5740f; retrieved 2026-09-15T18:43:58.042Z.