DEN05LA005 · Cessna 172N
Wyoming Air Cessna 172N · Accident: hard landing
From Casper-Natrona County International Airport (CPR) to an unrecorded destination
Event
- NTSB case
- DEN05LA005
- 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 172N
- 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
- N73764
- Operator
- Wyoming Air
- Onboard fatalities
- Unknown
- Route
- From Casper-Natrona County International Airport (CPR), Casper, WYTo not recorded
- 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 · flare/touchdown
- 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
- Hard landing
- 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
- Pilot in command › Flare, 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 solo student pilot was performing her fourth touch-and-go landing when she allowed the airplane to touchdown hard on the runway. The pilot said everything was fine until she got into the flare. She said that she felt she was going to float so she "put in some power." She said she felt she had things under control, so she reduced the throttle to idle. When the airplane touched down, it bounced. The pilot said she released a little back pressure. "The second time it [the airplane] came back to the ground, it bounced hard, and this time I think the propeller hit. It bounced hard 3 or 4 times after that. Back and forth." The pilot said she finally got the airplane stopped. She contacted the tower and received permission to taxi back to the ramp. An inspection of the airplane showed substantial damage to the firewall, and minor damage to the nose gear and propeller. No other anomalies were found.
Probable cause
the student pilot's improper flare resulting in a hard landing. A factor contributing to the accident was the student pilot's improper recovery from the bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN05LA005
- Event ID
- 20041012X01611
- Case number
- DEN05LA005
- 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: c3298eed5bacd246e547e43aae2dc1339044aba8d6409485d86425c3e36f1f7f; retrieved 2026-09-22T06:38:51.904Z.