FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN04FA119 · Cessna 172P

9 Aug 2004 · Monarch Crest, CO, United States

Pittsburgh Flight Training Center Cessna 172P · Accident: loss of control in flight while maneuvering

From Montrose Regional Airport (MTJ) to McCook Ben Nelson Regional Airport (MCK)

Report a problem

Event

NTSB case
DEN04FA119
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
2 · 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 172P

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
N911JR
Onboard fatalities
Unknown
Route
From Montrose Regional Airport (MTJ), Montrose, COTo McCook Ben Nelson Regional Airport (MCK), McCook, NE
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
Maneuvering · turn to reverse direction
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 in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › In-flight planning/decision, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The two pilots we en route home after a trip to the west coast. Two witnesses, hiking near the Continental Divide, heard an airplane approaching. They saw the airplane coming towards them "at eye level." It seemed to be stationary, then it banked hard to the right and went straight down. The accident took place at an elevation of 11,418 feet msl. The elevation of that portion of the Continental Divide is 11,530 feet msl. Later engine disassembly and examination disclosed no anomalies. Weather observed at a remote AWOS facility, located approximately 1 mile east of the accident site, was used to compute an estimated density altitude of 14,300 feet msl. According to the 1984 Cessna 172P Skyhawk "Information Manual," the airplane's service ceiling is 13,000 feet.

Probable cause

the pilot's failure to maintain airspeed which resulted in a stall, and his decision to conduct flight beyond the performance capability of the aircraft. A contributing factor was the high density altitude, and an inadvertent stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN04FA119
Event ID
20040816X01228
Case number
DEN04FA119
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, coordinates. 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: fce54e21415e2ede9e4eb75718c24429157cb781df032cdb59b9df0c9875bead; retrieved 2026-09-20T18:23:05.086Z.