DEN05CA007 · Mooney M20E
Mooney M20E · Accident: loss of control in flight during landing
From Rocky Mountain Metropolitan Airport (BJC) to an unrecorded destination
Event
- NTSB case
- DEN05CA007
- 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 M20E
- 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
- N14DV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (BJC), Broomfield, COTo 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 · aborted
- 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
- 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
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While performing a touch and go maneuver, the pilot failed to maintain control of the airplane during the landing. On the approach, the pilot configured and stabilized the airplane for landing and "all seemed to be in order." After crossing the runway threshold, the pilot felt the speed and sink rate were too fast. The airplane touched down and bounced twice. At that point, the pilot added power to abort the landing. The airplane drifted to the left and began to porpoise. Subsequently, the airplane skipped across the grass adjacent to the runway, went down an embankment, and came to rest upright against a chain-linked fence. The pilot reported no mechanical problems with the airplane prior to the accident.
Probable cause
the pilot's improper flare and recovery from a bounced landing during a touch and go maneuver. Contributing factors were the excessive airspeed and descent rate during the approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN05CA007
- Event ID
- 20041104X01753
- Case number
- DEN05CA007
- 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: 764f2cb3b806794e5d9a72fac56523f32064eaf2c04fff9383c8136cb2458980; retrieved 2026-09-22T06:38:16.621Z.