DEN04LA010 · Mooney M20K
Mooney M20K · Accident: hard landing
From Grand Junction Regional Airport (GJT) to Grand Junction Regional Airport (GJT)
Event
- NTSB case
- DEN04LA010
- 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
Mooney M20K
- Aircraft type
- Mooney M20
- 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
- N5659L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Grand Junction Regional Airport (GJT), Grand Junction, COTo Grand Junction Regional Airport (GJT), Grand Junction, 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 · 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
- 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/mush
- 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 › Airspeed, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, he had completed an uneventful touch-and-go landing on runway 29 using an approach speed of 67 knots. On the second touch-and-go landing, he used an approach speed of 70 knots. He stated that the airplane's airspeed was stable around the pattern. However, just short of the runway, at approximately 30 feet agl, he encountered a slight "burble." He initiated full power, and when he dropped the nose of the airplane a few degrees, he encountered a second "burble." The pilot stated that "the airplane literally fell out of the sky" and struck the runway. The impact with the runway separated the right main landing gear and the separated right main landing gear struck the right horizontal stabilizer. The nose landing gear collapsed, the right wing tip and propeller struck the runway, and the airplane slid approximately 150 feet. The airplane sustained substantial damage to the right wing spar and the right horizontal stabilizer. The reported weather conditions at 1553 and 1604, indicated a shift in wind, from 310 degrees at 5 knots to 280 degrees at 8 knots respectively.
Probable cause
the pilot's improper flare and his failure to maintain airspeed resulting in a stall and hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN04LA010
- Event ID
- 20031020X01772
- Case number
- DEN04LA010
- 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: e30fb25eaa9e9f1ae557fc6a935d5123c1288e3f013019d53acb31b46dcb5d50; retrieved 2026-09-22T08:20:19.825Z.