WPR09CA348 · Cessna 172M
Round Top Flyers Cessna 172M · Accident: controlled flight into terrain/object (CFIT) en route
From Hunt Field (KLND) to KTHP · Thermopolis, WY
Event
- NTSB case
- WPR09CA348
- 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 172M
- 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
- N5461Q
- Operator
- Round Top Flyers
- Onboard fatalities
- Unknown
- Route
- From Hunt Field (KLND), Lander, WYTo KTHP · Thermopolis, WY
- 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 · descent
- 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
- Controlled flight into terrain/object (CFIT)
- 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 › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot and his instructor were returning to their home airport after a visual flight rules (VFR) night cross-country instructional fight. During the last segment of the flight, as the student was descending toward the airport, the airplane's wheels contacted the terrain on a ridge about nine miles from the planned destination, and about 1,650 feet higher than the airport elevation. Although the airplane initially rolled across the terrain at a high rate of speed, it soon encountered the elevated edge of a dirt road. The contact with the road edge resulted in a loss of control of the airplane and further contact with the terrain. The sequence of events resulted in substantial damage to the airplane's fuselage. Although the sky was clear with no restrictions to visibility, it was a dark night with no moonlight, and neither pilot saw the terrain prior to the accident. Although the instructor pilot did not specifically remember an unusual rate of descent or any sense of the airplane sinking, it was his opinion that a "mountain wave downwash" may have contributed to the accident.
Probable cause
The instructor pilot's failure to ensure that his dual student maintained clearance from the terrain during a dark night visual flight rules descent.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09CA348
- Event ID
- 20090716X53746
- Case number
- WPR09CA348
- 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 2009-07-16.
- API snapshot SHA-256: 59ec14a494ee76181cb62fa6e7931e27a4076a97d7beac8f6e5bb3f088918b52; retrieved 2026-09-15T11:53:40.807Z.